How-to: Day-One Checklist for Your First 8 Hours
Day one is not the day you prove you were the right hire. It is the day you get oriented without drowning. An 8-hour checklist keeps you moving through setup, introductions, and clarity on how work actually runs here. You leave with notes, names, and a short list for tomorrow instead of a fog of Slack pings and half-finished logins.
Time box: one working day (about 8 hours) with built-in buffers. Treat blocks as soft fences. If IT takes longer, protect the people conversations and move admin to gaps.
This lives in the New hire hub and fits the first stretch of your first 90 days. Managers onboarding someone can pair it with the New Manager hub. If you are joining as an IC, keep the Individual Contributor hub nearby for how to manage up from day one.
When to use / when not
Use when:
– It is your first day (or first day back after a long leave with a new team)
– You have a manager or buddy who can unblock access and introductions
– You want a default plan so you do not invent the day under stress
– Hybrid or remote day one where structure matters more than hallway luck
Do not use when:
– You are mid-crisis coverage and already know the systems (use a role-specific runbook instead)
– HR or Legal has told you to pause certain contacts or systems (follow that guidance)
– Your company already issues a mandatory day-one schedule; follow theirs and use this only to fill gaps
– You are tempted to skip people time to “look productive” in tools you do not yet understand
Day one is intake. Hero projects can wait.
Prep
Do as much as you can the night before (see also pre-day-one setup):
- Confirm start time, location or video link, dress norms, and who greets you
- Charge devices; bring ID if badge pickup is required
- Open a private notes doc titled “Day one” with sections: Access, People, Norms, Questions, Tomorrow
- List the 5–7 people you most need to meet (manager, buddy, closest collaborators)
- Skim any welcome packet once; do not try to memorize policies overnight
If finance, sales, or cross-team workflows will matter soon, bookmark finance for non-finance managers, how sales works, and how departments work together for later reading, not for day-one cramming.
Steps
- Arrive / log on and ground yourself (first 30–45 min). Greet your manager or buddy. Confirm the day’s plan. Get badge, desk, or remote setup basics. Write down who to ping for IT.
- Clear critical access (60–90 min). Email, calendar, chat, VPN, HRIS, laptop standards. Test send/receive. Screenshot errors for IT instead of thrashing alone. Park “nice to have” tools for later.
- Manager orientation conversation (45–60 min). Goals for week one, success signals for month one, meeting norms, preferred channels, and who else to meet. Ask what not to break. Schedule recurring 1:1 before you leave the room or call.
- Buddy or peer walkthrough (45–60 min). How requests get done, where truth lives (docs, tickets, tribal knowledge), and unwritten rules. Capture jargon in your notes.
- Team intro touchpoint (20–30 min). Live standup hello or a short written intro if remote and async-first. Keep it human and brief; fuller intro can follow (introduce yourself to the team).
- Shadow or light work (60–90 min). Sit with one real workflow: a ticket queue, a customer thread, a planning doc. Observe more than you opine.
- Admin and benefits pass (30–45 min). Payroll, benefits enrollments deadlines, time tracking. Note due dates. For policy questions that feel sensitive, use how HR works as your map of who owns what.
- Close the day (20–30 min). Send a short end-of-day note to your manager. List blockers, meetings set, and your top three questions. Block tomorrow’s first deep-work or learning hour on your calendar.
Protect lunch. A skipped meal makes afternoon fog feel like incompetence.
Script (what to say / send)
Opening with manager:
“Thanks for having me. I want to use today for access, introductions, and clarity on week-one priorities. Where should we start, and who else should I meet before end of day?”
Access escalation to IT / buddy:
“I am blocked on [system]. Error text: [paste]. I need it for [reason]. Happy to hop on a 10-minute screenshare.”
Team hello (live):
“I am [name], joining as [role]. I will spend this week listening and learning how work moves here. Glad to be on the team. I will send a short intro note with how to reach me.”
End-of-day note to manager:
Day one close-out:
– Access done: [list] / still blocked: [list]
– Met: [names]
– 1:1 cadence: [day/time]
– Top questions for tomorrow: 1) … 2) … 3) …
– I will [one concrete next step]
If someone dumps a huge project on you today:
“I can take a briefing now and propose a first step by [day]. Today I am still finishing setup so I do not commit dates I cannot keep.”
Output artifact
Day-one packet (private notes + short manager note):
- Access checklist with status (done / blocked / owner)
- People map: names, roles, how they prefer contact
- Norms captured: meetings, response times, decision forums
- Question log (parking lot)
- Tomorrow plan: top three actions and one learning block
- Recurring 1:1 on the calendar
Optional: a one-page “how work ships here” sketch after you shadow a workflow. Directors joining a new org can expand the people map using patterns from the Director / VP hub, but day one still favors listening over redesign.
Watch-outs
- Performing competence by skipping questions. Smart day-one behavior is asking crisp questions early.
- Boiling the ocean in Slack. Broadcast sparingly. Prefer targeted asks with context.
- Accepting every meeting invite blindly. Hold a light filter; decline or ask purpose when your calendar is already packed with setup (see cancel or decline a meeting).
- Oversharing personal history in intros. Warm and short beats a TED talk.
- Ignoring physical or remote ergonomics. Fix chair, lighting, and audio on day one so week one is sustainable.
- Leaving blockers fuzzy overnight. Name owners and next pings before you sign off.
Done looks like: critical access working or clearly owned, manager 1:1 scheduled, a few real humans met, norms noted, and a calm written close-out. You do not need an early trophy on day one. You need a clean runway into week one.