New Hire First Day Checklist: Who Does What, Hour by Hour
A first day checklist works when every task has one owner: HR, IT, the hiring manager, or you. Here are four role-based lists and one hour-by-hour schedule for day one.
A good first day checklist gives every task one owner: HR, IT, the hiring manager, or you, the new hire. This post splits the work into four role-based lists, then assembles all four into one hour-by-hour schedule for a single first day. Everything after day one belongs in a 30-60-90 day plan, not here.
Key takeaways
- A first-day checklist works only when every task has one of four owners: HR, IT, the hiring manager, or the new hire.
- HR and IT tasks belong in the 9:00 to 11:00 block, because equipment and access block everything else.
- IT should smoke-test the hire's logins and core workflow before day one, not troubleshoot on the first morning.
- The manager's day-one job is a one-sentence reason you were hired, two or three purposeful introductions, and a 15-minute end-of-day check-in.
- The new hire should start a win log on day one, so the 90-day review is a read-through instead of a scramble.
What should be on a new hire first day checklist?
A new hire first day checklist is every task that has to happen on day one, assigned to a specific owner: HR, IT, the hiring manager, or you.
Splitting tasks by owner beats one consolidated list because it makes gaps visible. If the badge never arrives, you know whose list it was on.
Why most first-day checklists fail the new hire
Most templates are written for the company, not for you, so they cover paperwork and skip the parts that reduce new job nerves. Structured onboarding improves retention and time-to-productivity, which is why SHRM recommends a deliberate first-day plan rather than improvisation.
What should HR do before the new hire arrives on day one?
Before day one
Finish the paperwork early so day one isn't a form-filling marathon. Send the offer letter, tax forms, and direct deposit setup in the week before the start date, and confirm payroll is loaded so the first paycheck lands on time.
Then send a welcome email with the logistics that actually matter: where to park, what time to arrive, who to ask for at the front desk, and the dress code. Include your phone number in case anything goes wrong that morning. Order the badge and confirm building access is active before they walk in.
On the day itself
Greet them personally in the first ten minutes. A quick face-to-face welcome, a tour of where they'll sit, and a handoff to their manager or onboarding buddy covers it. HR's job on day one is presence, not process.
What should IT prepare for a new hire's first day?
IT's job on day one is simple to state: the laptop works, the accounts work, and someone tested both before the hire sat down.
Hardware and accounts
Ship the laptop early enough to arrive before the start date, or have it waiting at the desk with the charger. Pre-create the email account, SSO login, and chat account so the hire never hits a "check your email for your temporary password" loop on an inbox that doesn't exist yet. A one-page sheet with the wifi password, VPN instructions, and who to ping when something breaks beats a ticket queue.
Access and a day-one smoke test
Grant access to the core tools the role actually uses, not the full company catalog. Then have someone log in with the hire's credentials and click through the main workflow before day one. Gallup's workplace research links weak onboarding to lower engagement and early attrition, and a broken login on the first morning is the fastest way to signal nobody planned for you.
What is the hiring manager's first-day checklist?
Your new hire's first day is mostly other people's logistics. Yours is the part they'll judge the whole job by.
Morning: welcome and context
Meet them at the door or the video call, not five minutes late. Say why you hired them specifically, in one sentence. Then give context: what the team is working on this quarter, where your priorities sit, and what a good first month looks like. Keep it to 20 minutes, then let them breathe.
Midday: people and expectations
Introductions work best in small doses, not a parade. Send them to two or three people they'll work with daily, with a reason for each ("Sam owns the deploy pipeline you'll touch on day three"). Assign an onboarding buddy before day one, not after. Set first-week expectations out loud: what to read, what to ship, and permission to ask obvious questions.
End of day: the check-in that matters
Block 15 minutes. Ask two questions: what's unclear, and what surprised you. Answer the first, log the second. Then preview tomorrow so they arrive knowing the plan instead of guessing it.
What should the new hire accomplish on their first day?
Before you walk in
Arrive with three things noted: how your role is measured in the first 90 days, the names of your manager and onboarding buddy, and one question about how the team actually works. You won't learn any of this from a generic template.
Notion, Coda, and Asana all publish checklist templates you can adapt, but a blank template isn't a plan, so spend 30 minutes the night before filling in the specifics for your job.
During the day
Capture names and context as you go. Every person you meet, make note of their name, what they own, and one thing they told you. Then ask the three questions that set up week one: what does success look like at 30 days, who should I talk to first, and what is the one thing you wish someone had told you?
Start your win log on day one
Day one counts as a win. You accepted the offer, showed up, and got through orientation without embarrassing yourself, and that's where your log starts. Make note of every task you complete, every name you learn, and every small problem you solve, in one running list.
This matters because of how memory works under new-job nerves. By week six, the details of week one are gone, and when your 90-day review arrives you'll be reconstructing your ramp from vague impressions instead of a dated record. A win log you start on day one turns that review into a read-through rather than a scramble.
How should you structure the first day hour by hour?
An hour-by-hour schedule turns four separate checklists into one day. Each block has one owner, so nobody waits around wondering who does what.
- 9:00 Meet at the lobby or reception desk and pick up the badge. Owner: HR.
- 9:15 Paperwork wrap-up and benefits questions. Owner: HR.
- 10:00 Laptop, logins, email, and 2FA setup. Owner: IT.
- 11:00 Welcome, team intro, and role expectations. Owner: the manager.
- 12:00 Team lunch. Owner: the manager.
- 1:30 1:1 with your manager on first-week priorities. Owner: the manager.
- 2:15 Meet your onboarding buddy and walk through the tools. Owner: the buddy.
- 3:15 Read team docs and set up your win log. Owner: the new hire.
- 4:15 Ask leftover questions and confirm tomorrow's start time. Owner: the new hire.
- 5:00 End of day.
The 9:00 to 11:00 stretch is deliberately HR- and IT-heavy, because that's what blocks everything else. The afternoon shifts to people and context, which is what you actually remember.
Adjusting for remote first days
Remote flips the order. Ship hardware before day one so IT setup becomes a 30-minute morning check-in call, not a two-hour scramble. Replace the lobby meeting with a 9:00 manager call, and make the lunch a 30-minute optional video coffee with two teammates instead of the whole team. Keep the buddy intro, but book it as a calendar invite with an agenda so it actually happens. Everything after 2:00 stays the same: read docs, start your win log, end on time.
What first-day mistakes make new hires regret accepting the offer?
Five failure modes account for most first-day regret, and each has a clear owner.
- No working equipment or accounts: IT dropped it.
- An empty calendar: the manager never blocked time.
- No manager time in the first hour: the manager again.
- Information overload: HR or the manager dumped a week of policy reading into day one instead of spreading it out.
- No end-of-day wrap-up: the manager skipped a 15-minute check that would have caught the other four.
The pattern behind all five is handing a new hire a generic list instead of a plan built for them. One reviewer of Microsoft's Employee Onboarding Hub asked how its onboarding list template "makes any sense and can actually be used," noting you'd have to rebuild the whole list for each employee (Microsoft Tech Community). A checklist nobody personalized is how day one goes wrong.
How does a first-day checklist differ from a full onboarding checklist?
Day one is a subset. It covers access, introductions, and one meaningful task. Everything that actually determines whether you ramp up in your first 90 days lives after it: learning the domain, shipping early wins, building relationships, and logging accomplishments for your 90-day review. A first-day checklist that stops there is doing its job. A plan that stops there isn't.
Where do template tools fit?
Notion, Coda, and Asana are blank canvases. You can build a 30-60-90 day plan in any of them, and many people do, especially if your new team already lives in one. The cost is assembly: you find a template, adapt it to your role, and keep updating it yourself while you're also learning the job. That works if you enjoy structuring your own ramp-up. It's friction if you just want to know what to do tomorrow morning.
Where does a guided plan fit, and where doesn't it?
A guided plan gives you the structure pre-built: a daily checklist for each phase, a running win log, and a report ready for your 90-day review. Soar90 is built for exactly that individual use case, at $9.99 one-time.
The trade-off is worth naming. It doesn't handle HR paperwork or IT setup tasks, and it isn't a shared workspace your manager collaborates in. If you need either of those, a template tool or your company's own process is the better fit. If you want the after-day-one plan handled for you, it's the narrower, more opinionated tool.
FAQ
How long should a new hire's first day actually be?
Plan a standard 9-to-5 day and end it on time. The morning covers HR logistics and IT setup, since those block everything else, and the afternoon shifts to people, context, and a 15-minute end-of-day check-in. Anything longer usually means information overload, one of the five failure modes that cause first-day regret.
What should a remote new hire's first day look like?
Remote flips the order: hardware ships before day one so IT setup becomes a 30-minute morning call instead of a two-hour scramble. Start with a 9:00 manager call instead of a lobby meeting, make lunch a 30-minute optional video coffee with two teammates, and book the buddy intro as a calendar invite with an agenda. After 2:00, the schedule matches in-person.
Who is responsible if the new hire's equipment isn't ready on day one?
IT owns it. The checklist assigns hardware, accounts, and access to IT, including a smoke test where someone logs in with the hire's credentials and clicks through the main workflow before day one. If the laptop or logins fail on the first morning, the gap sits on IT's list, which is why splitting tasks by owner makes failures visible instead of ambiguous.
What should I bring on my first day of a new job?
Arrive with three things noted: how your role is measured in the first 90 days, the names of your manager and onboarding buddy, and one question about how the team actually works. Spend 30 minutes the night before filling in the specifics, because a blank template isn't a plan. Also bring something to capture names and context as you meet people.
How soon after day one should a new hire have a 30-60-90 day plan?
It should already exist before day one ends. The first-day checklist deliberately stops at day one, and everything after it, from learning the domain to logging early wins, belongs in a 30-60-90 plan. Ask your manager on day one what success looks like at 30 days, then build the plan that week so week one has direction.
References
- Essential ingredients for an effective onboarding program, Gallup
- SHRM onboarding guidance, Society for Human Resource Management
- Microsoft Tech Community, Microsoft Employee Onboarding Hub discussion
- Notion templates, Notion
