Use a staged checklist, preboarding, day one, first week, and 30/60/90 milestones, and assign an owner and deadline to every task on it. Prioritize three things above all else: compliance paperwork, IT provisioning, and role clarity backed by regular manager check-ins. A written plan with templates and a tracking system, not a mental list, is what actually keeps a new hire from falling through the cracks.
TL;DR:
Over 90 days, managers should verify new hires complete core training, handle at least one task independently, and demonstrate measurable contributions.
Ensure compliance paperwork, including I-9 and W-4 forms, is submitted within strict deadlines, with a tracker highlighting progress.
IT provisioning must begin immediately after offer acceptance, with accounts created and equipment shipped early to prevent delays on day one.
Building clear role expectations with specific goals and success metrics for 30, 60, and 90 days optimizes performance and reduces ambiguity.
Establish strong connections with buddies and team rituals early to boost retention and create a culture of engagement from day one.
Table of Contents
-
Employee Onboarding Checklist by Phase: Before Day One Through 90 Days
-
How Do You Provision IT Equipment and Accounts Before Day One?
-
How Do You Give a New Hire Role Clarity in Their First 90 Days?
Employee Onboarding Checklist by Phase: Before Day One Through 90 Days
The strongest onboarding programs are built in four stages, not one long undifferentiated list. SHRMβs onboarding research recommends a documented plan that runs from the offer letter through at least the 90 day mark, with milestones checked off along the way. Hereβs what belongs in each phase.
1. Preboarding (offer acceptance to day one). This window, often one to three weeks, is where most small companies lose ground because nobody owns it. Send the welcome email with a first day agenda attached. Push all e-signature paperwork, including the I-9βs Section 1 and tax forms, through an e-signature tool so nothing arrives on day one as a surprise. Trigger equipment orders immediately: a laptop with a two-week lead time ordered on offer acceptance arrives on time; ordered the week before start date, it doesnβt. Send a benefits preview so the new hire isnβt blindsided by enrollment deadlines later.
2. Day one. Structure the morning around three things: orientation, a manager one-on-one, and a working login. Trainualβs 30-day framework recommends a 90-minute manager conversation on day one that covers role expectations, team introductions, and immediate questions, not a rushed 15-minute welcome squeezed between meetings. Confirm the workstation actually works: email, VPN, shared drives, and any tools specific to the role. Cover safety and building access basics if the role involves physical space. None of this should be improvised; write the agenda in advance.
3. First week. This is where role training starts and the buddy relationship becomes real rather than symbolic. Schedule two or three short touchpoints with the assigned buddy, not just an introduction email. Give the new hire one small deliverable they can finish by Friday, something low-risk that produces a visible result. Finishing a real task in week one does more for confidence than a week of shadowing ever will.
4. The 30/60/90 milestones. Moxoβs onboarding framework treats these as checkpoints with owners, not vague aspirations. At 30 days, the manager should confirm the new hire has completed core training modules and owns at least one recurring task independently. At 60 days, look for a measurable contribution, a closed ticket, a shipped feature, a client call handled solo, and a documented skills gap if one exists. At 90 days, the new hire should be evaluated against the original role brief with a formal check-in and a written summary of whatβs working and what needs adjustment. Assign a specific manager or HR owner to each checkpoint, not βthe team.β
What US Compliance Paperwork Do You Need for New Hires?
Compliance is the part small employers most often get wrong, usually not from negligence but from missed deadlines buried in a busy first week.
-
Form I-9: Section 1 must be completed by the employeeβs first day of work, and Section 2 within three business days of the start date. Some employers now qualify for remote document examination alternatives under specific federal conditions tied to E-Verify participation, but the default rule still requires physical document review unless you meet those conditions. Retain I-9 forms for three years after the hire date or one year after termination, whichever is later.
-
Form W-4: The IRS requires a completed W-4 before the first paycheck; without one, you must withhold at the higher single rate with no adjustments. State withholding certificates vary by state and sometimes by locality, so donβt assume the federal form covers your obligations.
-
New-hire reporting: Most states require employers to report new hires within 20 days of the start date, though a handful require reporting within 10 days. Youβll typically need the employeeβs name, address, Social Security number, and start date, plus your employer identification number.
-
Benefits notices: If you offer group health coverage, federal rules require a Marketplace notice within 14 days of hire, and COBRA-eligible plans carry their own separate notice timeline once someone is enrolled.
Pro Tip: Build a compliance tracker with hard deadlines, not just task names. βComplete I-9β doesnβt tell you if youβre on day one or day three of your three-day window.
How Do You Provision IT Equipment and Accounts Before Day One?
IT delays are the single most preventable reason a new hire sits idle on day one. Start provisioning the moment the offer is signed, not the week before start date.
-
Order and image laptops during preboarding; standard procurement and imaging can take one to two weeks depending on your vendor.
-
Create accounts before day one: email, SSO, Slack or Teams, VPN, and any code repositories the role requires, with a named approver for each so nothing waits on a single bottlenecked manager.
-
Set up MFA and device policies before shipping, and tag every asset with a serial number tied to the employeeβs record for future returns.
-
For remote hires, ship equipment with enough lead time to run a test login before day one, ideally with the buddy or IT contact on a call to troubleshoot in real time.
Pro Tip: Have the new hire log in from home the day before their official start. Fixing a broken VPN connection on their own time beats discovering it during their first scheduled meeting.
Centralizing device assignments and account ownership in one system, rather than a spreadsheet someone forgot to update, is what keeps this phase from becoming the thing that derails an otherwise good remote onboarding checklist.
How Do You Give a New Hire Role Clarity in Their First 90 Days?
A one-page role brief consistently beats verbal explanation for setting expectations, and it takes fifteen minutes to write.
-
List three core responsibilities, not ten. A long list of duties dilutes focus in the first month.
-
Set three 30-day goals that are specific and measurable, βcomplete onboarding training and shadow five customer callsβ rather than βget up to speed.β
-
Define success metrics for 60 and 90 days, tied to actual output: tickets closed, deals sourced, code merged.
-
Set a manager check-in cadence, weekly for the first month, biweekly through day 90, with a short written agenda each time so the conversation isnβt improvised.
-
Assign training ownership to a specific person for each skill area, and confirm completion with a short knowledge check rather than assuming attendance equals competence.
How Do You Build Culture and Connection Into Onboarding?
Compliance and IT get a new hire working. Connection is what makes them stay. SHRMβs onboarding guidance ties assigned buddies and consistent manager check-ins directly to lower early-stage turnover.
-
Assign a buddy before day one, not during it, and schedule two structured check-ins in week one.
-
Write a one-page βhow we workβ guide covering meeting norms, response-time expectations, and communication tools.
-
Add low-cost rituals: a team Slack intro thread, a virtual coffee in week one, a group lunch by week two.
-
Send a two-question pulse check at day seven asking whatβs confusing and whatβs going well.
How Do You Measure Whether Onboarding Is Working?
Track a small set of numbers rather than relying on gut feel. Watch 90-day retention, time-to-productivity against the role briefβs goals, training completion rates, and a short new-hire satisfaction pulse.
-
Run a pulse survey at day 7 and again at day 30, two or three questions, nothing longer.
-
Have managers submit a short debrief at each 30/60/90 checkpoint.
-
Audit checklist completion rates monthly; a task thatβs consistently late or skipped points to a broken step, not a careless employee.
-
Feed what you learn back into the templates so the next hire doesnβt hit the same gap.
How Do You Turn a Checklist Into a Repeatable System?
A checklist only works if every task has four fields: the task itself, an owner, a due date, and a way to confirm itβs done. Add a status column and youβve got something a manager can actually audit.
-
Build in automated reminders for tasks nearing their due date.
-
Gate later steps behind earlier ones, donβt let account creation start before the I-9 is signed.
-
Escalate automatically to a manager or HR lead when a task goes overdue.
-
Once youβre hiring regularly or managing a distributed team, a shared spreadsheet starts breaking down. Thatβs the point to centralize onboarding in a single system rather than patching together five disconnected tools.
The CentriOps Perspective on Onboarding Friction
Most onboarding failures arenβt training failures, theyβre tracking failures. A laptop order gets missed because it lived in someoneβs inbox instead of a system. An I-9 deadline slips because nobody flagged it. SHRMβs research notes that technology helps track progress at scale, but the underlying problem for most small teams isnβt a lack of tools, itβs too many disconnected ones. Spreadsheets donβt tell you when a device shipment is overdue. Email threads donβt preserve compliance evidence for an audit. A single system that ties tasks, assets, and user records together doesnβt just save admin time, it removes the guesswork about who dropped the ball.
β CentriOps Team
Put the Checklist on Autopilot With CentriOps
Every checklist in this article works better with a system behind it instead of a shared spreadsheet nobody updates consistently. CentriOps turns the tasks above, paperwork tracking, device orders, into assigned items with owners, due dates, and evidence attached, so a missed I-9 deadline or a delayed laptop shipment shows up before it becomes a first-day problem.
A team running five or six hires a quarter typically loses hours reconciling spreadsheets, chasing signatures, and tracking down who has which laptop. Centralizing that in CentriOpsβs asset and task features means reminders fire automatically, device assignments stay tied to the employee record, and managers can see checklist completion at a glance instead of asking around. If youβre managing onboarding for a distributed team without a dedicated IT department, start a free trial and run your next hire through the system instead of a spreadsheet.
