Onboarding process

This page is about the process a company runs: the sequence of steps, the person who owns each one, and the event that triggers the next. If what you need is the new hire experience and whether the hire holds, that is the employee onboarding page, and it is a different job. Run as a process, onboarding starts earlier than most companies run it, at the accepted offer rather than at day one, and the weeks in between are where the hire is most often lost.

The onboarding runbook, phase by phase

Five phases. Every step has an owner and a trigger, because an onboarding process fails at the handoffs rather than at the steps. Adapt the contents; keep the ownership column.

Accepted offer to the day before joining | Owner: recruiting, with HR operations

Pre-boarding

The phase most companies do not have. Acceptance is a stage change, not a closure, and the requisition stays open in your tracker until somebody is at a desk.
- Document collection and background checks start immediately, because they are the only part of this gap you control
- Equipment ordered against a lead time you have actually measured, not the one procurement quotes
- Accounts, mail and system access raised with the start date attached, so they exist before day one rather than on day three
- Payroll and statutory registration initiated, with the candidate told precisely which documents are still outstanding
- A personal note from the hiring manager, from the manager rather than from a system
- A named contact the person can reach who is not the recruiter
How this phase fails: The requisition is closed on acceptance, ownership passes to nobody, and the next contact the candidate receives is an email telling them where to report.
Owner: hiring manager

Day one

One rule decides most of day one: if the manager is travelling, move the start date.
- A working machine, credentials, and access to the two or three systems needed in week one, rather than to everything
- One hour of context: what the company sells, to whom, and what is currently hard, delivered by somebody senior enough for it to be true
- The compliance and paperwork block scheduled and finished, so it does not leak across the first fortnight
- Lunch with the team, with a named owner so it actually happens
- A first task that can be finished by the end of day two
How this phase fails: Access arrives late, so the first two days are spent waiting politely, and the new hire learns on day one that things here take a while.
Owner: hiring manager, with a named buddy

Week one
- A written statement of what the person owns and, just as usefully, what they do not
- A buddy chosen because they will answer, not because they had capacity
- Five specific introductions booked in the calendar rather than suggested
- Read access to the artefacts that explain the last two years: the decision log, the postmortems, the roadmap that got cut
- A first shipped contribution, however small
- A short manager check-in at the end of the week with one question: what has been confusing?
Owner: hiring manager

Weeks two to four
- Ownership handed over in whole units of work rather than in tasks
- The person presents something back to the team, which is the fastest available way to find out what they have misunderstood
- Feedback in both directions at the end of week two and week four, on a schedule rather than on a feeling
- Access gaps closed. Most onboarding friction after week one is a request that nobody escalated
- The onboarding itself reviewed with the new hire while they still remember it, because within a month they will have normalised whatever went wrong
Owner: HR operations

Handover out of onboarding

Onboarding needs an end, declared out loud, or it dissolves and the probation review arrives as a surprise to both sides.
- Probation review scheduled for the point the offer letter promised, rather than when somebody remembers
- The checklist closed formally, with exceptions listed rather than quietly dropped
- What broke this time written back into the template, so the next hire inherits the fix

An onboarding process fails at the handoffs, not at the steps

Almost every company can list the steps, so the list is not the problem. The failures sit at the seams: recruiting assumes HR operations owns document collection, HR operations assumes IT owns access, IT is waiting on a ticket recruiting was meant to raise, and the new hire spends week one being polite about it. Three seams account for most of it.

Acceptance to pre-boarding

The recruiter's job ends at acceptance and nobody's job begins. This is the most expensive gap in the process, because it is also the window in which accepted offers are lost.

Pre-boarding to day one

Equipment and access have lead times nobody has measured. The fix is not urgency on day minus two, it is ordering against a real lead time on the day the offer is accepted.

Month one to probation

Onboarding ends without anybody deciding whether it worked, so nothing is written down, and the same failure is rediscovered by the next hire.

What belongs in the checklist and what does not

Checklists are good at things that are pass or fail and bad at things that require judgement. Mixing the two produces a document where cultural immersion sits next to laptop issued, and only one of them is ever honestly ticked.

Belongs in the checklist: Anything with a document, an account, a deadline or a legal consequence. These have owners, they are auditable, and two different people running the step would produce the same result.
Does not belong in the checklist: Whether the person understands the business, whether the team trusts them, whether the manager has set a real bar. Ticking a box does not produce any of the three, and having a box makes it look like it did.
The test: If two people running the same step would produce the same result, it is a checklist item. If not, it is a management responsibility, and it needs a name against it rather than a tick.

What changes when the hire is remote or distributed

Equipment lead time becomes the critical path, because a courier delay is now a day-one failure rather than an inconvenience.
Nothing important is learned by osmosis. Every piece of context a co-located hire would absorb in a corridor has to be either written down or scheduled.
The buddy relationship needs a standing calendar slot. A remote buddy who is available on request is not available.
Day one runs on a different clock. If the manager is six hours ahead, the first day has three usable hours and should be planned as three.
Access problems become invisible. A remote hire who cannot get into a system waits most of a day before asking, where a co-located one turns around and asks.

A seat that is filled but not yet productive carries much of the cost of an empty one for as long as the ramp lasts. Work out what the ramp period is costing.

Four things worth measuring, and one that is not

Time from accepted offer to first contact from the hiring manager. The most controllable number in the whole process, and usually the worst.
Share of day ones where equipment and access were both ready. Track it as a binary, because partial readiness is a failure the new hire experiences as total.
Time to first shipped contribution, by role. This is the number that distinguishes onboarding from orientation.
Thirty-day and ninety-day voluntary exits, tracked by hiring manager rather than only by department, because the finding is always a concentration.
Not worth measuring: an onboarding satisfaction survey collected in week one. Everybody is polite in week one.

The reason to fix the process is downstream: what a first-year exit costs once search, ramp and re-search are counted.

How Continuity1 runs this funnel

The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.

Onboarding inherits whatever the hiring process handed it. These are the numbers on the stage before this one.

1 in 3: Shortlisted candidates you meet who become the hire; Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.; Continuity1 tracked engagements
~3: Interviews your team sits in, per hire; Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.; Ashby talent-trends report
1 in 9: Accepted offers that ghost before joining; Indian employers report nearly 4 in 10 offers dropped. We lose 1 in 9.; nasscom community
95%: Offers that close inside your stated band; 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.; Continuity1 tracked engagements

Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.

You review a scored shortlist and make the calls. The filtering never lands on your calendar.

Share a role See the workings and the citations

Questions teams ask

When does the onboarding process actually start?

At the accepted offer, not at day one. Every step in the pre-boarding phase is possible from the moment somebody signs, and the period between signing and joining is both the longest unmanaged stretch in hiring and the one with the highest failure rate.

Who should own the onboarding process, HR or the hiring manager?

Split it by type of step. HR operations owns anything auditable: documents, payroll, access, compliance, and the formal close. The hiring manager owns anything requiring judgement: context, the first piece of work, the feedback, and the decision at the end. Processes fail when one side is asked to own both.

How long should an onboarding process run?

The process, as a checklist with owners, should be finished inside the first month, and it needs a declared end. The ramp continues well past that, but the ramp is a management responsibility rather than a process, and keeping a checklist open for ninety days is what turns it into something nobody updates.

What is the difference between onboarding and orientation?

Orientation is a block of information delivered to the person: policies, systems, introductions, the tour. It is a subset, usually a day, and it can be completed perfectly by a company whose new hires still leave in month five. Onboarding is the whole sequence, including the part where somebody decides whether it worked.

Do senior hires need a different onboarding process?

The checklist is the same and the sequence is not. Senior hires need access to the history early, including the decisions that went badly, and they need the people who did not choose them brought into the first fortnight deliberately. Skipping the process for a senior hire because they will figure it out is the most common way a leadership hire fails quietly.