How-to: Pre-Day-One Setup for Accounts, Access, and Calendar
The best day one starts before day one. Pre-day-one setup clears identity checks, device logistics, calendar holds, and the first wave of accounts so your first hours are about people and context, not password resets. You cannot control every IT queue, but you can remove every delay that is yours to remove.
Time box: 60–90 minutes across the days before your start date (split into two short sessions if forms arrive late). Stop when the checklist is green or clearly waiting on someone else.
Use this with the New hire hub. It feeds directly into your day-one checklist. Hiring managers can hand this link to inbound hires from the New Manager hub.
When to use / when not
Use when:
– You have a signed offer and a start date
– HR or IT has sent paperwork, device options, or background-check links
– You will be remote or hybrid and need a quiet setup day before kickoff
– You want your manager’s first impression to be “ready,” not “scrambling”
Do not use when:
– You have been told not to access systems until a formal start (honor that; do paperwork only)
– Legal or immigration steps are incomplete and you were asked to wait
– You are trying to unofficially start project work unpaid before day one
– You are rewriting the company’s onboarding program; this is a personal runbook
Pre-day-one is logistics and learning posture. It is not unpaid labor on the roadmap.
Prep
Gather in one folder (digital is fine):
- Offer letter / start date / manager name and email
- Personal email and phone you used in recruiting
- Government ID details needed for payroll or badge forms (enter only in official portals)
- Home address for shipping a laptop if applicable
- List of tools mentioned in interviews (CRM, design suite, cloud consoles, ticketing)
- Empty calendar for start week mornings so you can accept orientation holds
If your role touches budget, revenue, or cross-functional delivery soon, keep later reading queued: finance for non-finance managers, how sales works, how departments work together. Do not binge them instead of finishing forms.
Steps
- Confirm logistics in writing (10 min). Reply to the recruiter or coordinator: start date, time, location or video link, dress code, who greets you, parking or building entry, device plan.
- Complete HR and identity paperwork (20–30 min). Tax forms, direct deposit, emergency contact, handbook acknowledgments. Screenshot confirmation pages. Calendar any benefits deadlines you see.
- Drive account creation, do not assume it (15–20 min). Check for IT tickets or welcome portals. If nothing arrived 3–5 business days before start, send a polite nudge with start date and manager cc’d.
- Prep your workspace and devices (15 min). Quiet room for video, headset test, charger, notepad. If using a personal machine temporarily, update OS and install only what IT approved.
- Build a starter calendar skeleton (10–15 min). Block day-one orientation, a lunch break, and a 20-minute end-of-day wrap. Accept known welcome meetings. Create a private “First 90 days” calendar or tag.
- Draft your questions and intro scraps (10 min). Three questions for your manager; a three-line team intro draft you can edit on day one (introduce yourself to the team).
- Send a pre-start note if appropriate (5 min). Short message to manager: excited, logistics confirmed, anything still blocked. Ask if there is pre-reading that is truly worth an hour.
Track open loops in a single checklist. Waiting on IT is fine; losing the thread is not.
Script (what to say / send)
Logistics confirmation:
Confirming my start on [date] at [time], [location / Zoom]. I will meet [name]. Please flag anything I should complete before then (IT, badging, pre-reads). Thanks.
IT / access nudge:
My start date is [date] for [role], manager [name]. I have completed [forms done]. I have not yet received [account / laptop / VPN instructions]. Who owns next steps, and is there anything you need from me?
Pre-start note to manager:
Looking forward to [day]. Logistics are confirmed with [recruiter/IT]. I am set up for [remote/on-site]. If there is one short pre-read or channel you want me in on day one, send it over. Otherwise I will follow your plan.
If asked to do real project work before start:
Happy to skim public or approved pre-reads. I will wait until my official start for system work and commitments so we stay clean on access and timekeeping.
Benefits / HR clarification:
I see a deadline for [item] on [date]. Is that actionable before day one or during week one? I want to hit it without guessing. (Context on owners: how HR works.)
Output artifact
Pre-day-one setup board:
| Item | Status | Owner | Next ping date |
|---|---|---|---|
| HR paperwork | |||
| Payroll / direct deposit | |||
| Laptop / device | |||
| Email / SSO | |||
| Badge / building | |||
| Calendar holds | |||
| Manager pre-start note |
Plus:
- Confirmed day-one plan (time, place, greeter)
- Draft intro blurb
- Question list for manager
- Folder of confirmation emails and ticket numbers
ICs can keep this light. Leaders joining with wider scope may also map early stakeholder chats using the Director / VP hub, still without doing unpaid delivery work.
Watch-outs
- Entering sensitive data into unofficial forms. Use company portals and known HR contacts only.
- Installing random “productivity” software on a future work machine against IT policy.
- Over-preparing by building a 90-day strategy deck nobody asked for. Curiosity beats a premature manifesto.
- Letting silence ride when access is missing. One clear nudge with dates beats anxious waiting.
- Filling the first week with vanity meetings before you know priorities. Leave white space.
- Skipping rest the night before. A tired day one feels like a failing day one.
Done looks like: paperwork complete or clearly owned, logistics confirmed, calendar skeleton set, manager pinged once, and your energy saved for people on day one. Setup is invisible when it works. That is the point.