The employee onboarding checklist.

The gap between offer acceptance and the first day is onboarding’s most neglected phase, and its most consequential. The new hire has decided but not arrived; the employer has won but not yet delivered. Everything that makes day one calm happens here: the contract signed, the record created, equipment ordered, access requested, the first week planned. Handled well, preboarding also steadies the person through the period when counter-offers and second thoughts do their quiet work.

The preboarding list is short and unforgiving of delay: contract and signed paperwork returned, right to work and any required checks completed, payroll details captured before the cutoff, equipment ordered with lead times respected, accounts requested, and a welcome message that tells the person where to be, when, and what their first day will hold. Every one of these has a deadline that expires before day one, which is exactly why a checklist beats goodwill.

A working onboarding checklist has three owners, not one. HR owns documents, policy and the record: contract, checks, payroll data, handbook. IT owns equipment and access: hardware, accounts, permissions matched to the role. The manager owns the work: a planned first week, a first task with real purpose, introductions arranged, and time protected in their own calendar. Most onboarding failures are not missing items but missing ownership, where each team assumed another had it covered.

Give every item an owner, a due date anchored to the start date, and visibility across all three teams. The anchoring matters: "laptop ordered" is not a task, "laptop ordered ten working days before start" is. Shared visibility matters because the checklist is a relay, and relays fail at the handoffs: HR cannot request accounts until the record exists, IT cannot grant access until accounts exist, and the manager cannot plan a first task around equipment that has not arrived.

The day-one standard is simple to state: the person can work. Equipment on, accounts live, badge functioning, somewhere to sit or a working remote setup, a manager who is present and has cleared the morning, and one real task waiting. The paperwork burden should already be near zero because preboarding absorbed it. What remains should be human: introductions, context, lunch with actual colleagues, and an unhurried conversation about what the first month looks like.

Day one is also disproportionately memorable, which cuts both ways. Waiting three days for a laptop tells the new hire the company improvises; a first day that visibly expected them tells them it keeps its promises. Neither message is ever fully unsaid later. It is worth a manager’s hour to walk the day in advance: log in as if new, check the access, and read the plan through the new hire’s eyes.

The first week converts orientation into motion. The new hire should meet the people their work touches, ship something small but real, and hear the same expectations from their manager that the job advert promised. A daily check-in costs the manager ten minutes and catches small confusions before they compound. By the end of the week the person should be able to answer three questions unaided: what am I here to do, who do I go to for what, and how will my work be judged.

The first month is where mandatory training, systems depth and the first piece of independent work belong. It is also when the questions change character, from "where is the coffee" to "why do we do it this way", and those second questions are valuable: a new hire sees the broken process that everyone else has stopped noticing. Schedule a structured one-month conversation that asks for those observations while they are still fresh, and act on at least one of them visibly.

By day 30 the scaffolding should be coming down; by day 90 the person should be doing the job they were hired for, at a standard both sides recognise. That requires goals set in week one, reviewed at 30 and 60 days, and an honest probation conversation held before the deadline rather than after it lapses. Probation reviews that slide by default are a quiet failure of management: they convert a decision into an accident, and they are unfair in both directions.

The 90-day mark deserves a deliberate close: a review against the goals, feedback in both directions, and an explicit welcome into the ordinary rhythm of the company. If it has gone badly, the kindest version is also the clearest one, delivered with specifics and before the formal machinery makes everything harder. Either way, the outcome should be recorded, because probation outcomes are workforce data that later decisions rely on.

Onboarding is measurable, and the measures are mostly simple counts. Before day one: the percentage of checklist items complete on time, equipment ordered by the deadline, documents returned. Early weeks: time to first real contribution, training completion, check-ins actually held. Later: probation outcomes, and retention at six and twelve months by joining cohort. None of these need a data team; they need the checklist to live somewhere that records completion instead of assuming it.

The most honest measure is asking the new hire directly, twice. At the end of week one: was everything ready, and did you know what to do? At day 90: did the job match what you were told when you accepted it? The second question audits recruiting as much as onboarding, and the pattern of its answers across hires is one of the cheapest early warnings a company can buy.