Employee onboarding

This page is about whether the hire holds: the first ninety days, the manager part in them, and the signals that tell you in week six what you would otherwise find out in month nine. If what you need is the operational sequence with owners and triggers, that is the onboarding process page. Employee onboarding in this sense is not an HR programme. It is the period in which a hiring decision is either confirmed or quietly proved wrong, and it is run by the person the role reports to.

The 30-60-90 plan, written from the manager side

Written by the manager before the start date, handed over on day one, and reviewed out loud at each boundary. Each phase states what the hire should be able to do, and what the manager owes them for it to be possible.

The bar is comprehension, not output

Days one to thirty: understand
- Can describe what the company sells, to whom, and why those customers chose it over the alternative
- Has met the five people whose work touches theirs, by name and by what each one needs from them
- Has shipped one small thing end to end, including whatever review or approval step it required
- Can explain the two or three constraints that make this job harder than it looks from outside
- Has asked at least one question that made somebody on the team stop and think
What the manager owes: The written version of this list, handed over on day one rather than assembled in month two, and a first month protected from whatever was on fire when the person joined.
The bar is independent judgement inside a defined area

Days thirty-one to sixty: own
- Owns a defined area, and the team routes questions about it to them without being told to
- Has made a decision inside that area without escalating, and can explain the reasoning
- Has found something that is wrong and raised it, which is the first real evidence they are reading the business rather than only their tasks
- Is producing at a rate the manager can extrapolate from
What the manager owes: The first genuinely corrective piece of feedback. If nothing hard has been said by day sixty, either the hire is exceptional or the manager is avoiding it, and the second is considerably more common.
The bar is the standard the role was opened to get

Days sixty-one to ninety: contribute at level
- Delivers at the standard the role was opened for, without the allowances made in month one
- Has improved something outside their brief, which is the difference between a competent hire and the hire you actually wanted
- Can be left alone for a fortnight without the work degrading
- Has an opinion about what the team should stop doing
What the manager owes: An explicit decision: confirm, correct with a written plan and a date, or end it. A ninety-day review that concludes settling in well is a decision not to decide, and it costs a year.

The plan is worth writing before the offer goes out. A manager who cannot describe what good looks like at ninety days has not finished defining the role, and the interview process was assessing an unfinished definition.

What week six tells you that month nine cannot

Ramp and misfit look identical in week two and completely different in week six. These are the four early shapes, and all of them are visible long before a performance cycle would surface them.

The questions stop

A hire who has stopped asking questions in week six has usually stopped trying to reconcile what they were told with what they found. Silence reads as growing confidence and is more often quiet resignation.

The work is correct and inert

Tasks are completed, nothing is questioned, nothing is proposed. This is the most common shape of an inadequate hire, and it survives review cycles for a year because nothing is technically wrong with any of it.

They keep re-describing their last company

Reasonable in week two, a warning in week eight. It means they are applying a template rather than reading this business, and it is the signal that most often precedes an expensive process being rebuilt for no reason.

The team stops routing work to them

Teams reroute around a weak hire silently, and long before anybody raises it with a manager. Look at who is actually being asked rather than at the org chart.

The part only the manager can do

Everything on this list is uncomfortable, none of it can be delegated to a programme, and it is where the difference between a hire that holds and a hire that drifts is actually made.

Say what good looks like in this specific job, with one example of work that met the bar and one that did not.
Give the first corrective feedback early enough that it reads as instruction rather than as a verdict.
Protect the first month from whatever was urgent on the day they joined. The work always available on day one is almost never the work you opened the role for.
Introduce the person by what they own rather than by their title. It changes how the team routes work to them for the next year.
Decide at ninety days, out loud, in writing, and tell them what you decided.

Ramp is not the same for every role, and the plan should say so

A single ninety-day template applied across functions produces either a bar nobody can clear or a bar that proves nothing. Four common shapes.

Engineering: Ramp is gated by the codebase and the deploy path. The measurable milestone is a change in production, and much of the manager's job is removing approval friction that would otherwise disguise a slow start as a process delay.
Sales: Ramp is gated by the length of your sales cycle. Nothing conclusive can be measured before one full cycle has elapsed, so ninety-day evidence has to be activity quality and pipeline shape rather than closed revenue, and a manager who judges on revenue at ninety days will fire the wrong person.
The first hire in a function: There is nobody to learn from and no process to inherit. The ninety-day bar is a working plan the rest of the company agrees with, not output, and holding this hire to an output bar is how a first marketing or first finance hire is set up to fail.
Senior and leadership hires: The risk is landing rather than capability. The measurable thing at ninety days is whether the people who did not choose them have started bringing them problems unprompted.

First-year exits concentrate, and the concentration is the finding

A first-year exit is the most expensive kind, because you pay the full cost of the search, the full cost of the ramp, and then the cost of the search again. They also cluster. A manager whose hires leave inside a year tends to keep having hires who leave inside a year, and a role whose brief was written as a tool list tends to keep producing people who arrived expecting a different job. Both are findings about the organisation rather than about the market.

Split first-year exits three ways: could not do the job, could do the job and it was not the job they were sold, could do the job and were never given the conditions to start.
The second category is the largest and the most preventable, and it is created during the hiring process rather than after it.
Track by hiring manager and by joining cohort. Departmental averages hide every useful version of this number.

The size of the number is usually what makes it worth acting on: put a figure on a hire that does not hold.

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.

No onboarding rescues a hire that was wrong on the day the offer went out. The cheapest ninety days start with the right person, and that is decided upstream in how the shortlist was built.

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

What should a 30-60-90 day plan actually contain?

Two columns rather than one. What the hire should be able to do at each boundary, and what the manager owes them for it to be possible. Plans with only the first column read as a test the new person is being set, and they are usually written after the person has already started.

Should the new hire write their own 30-60-90 plan?

They should rewrite it in week two, not write it in week one. A plan authored entirely by the new hire tells you what they think the job is, which is useful information and a poor standard, because if their understanding of the role were already correct you would not need the ninety days.

How early can you tell that a hire is not working out?

Usually week six, and almost always well before the formal review. The tell is rarely output, because output in month two is unreliable for everybody. It is the shape of the questions, whether anything has been challenged, and whether the team has started routing work around the person.

What do you do when the ninety-day answer is no?

Decide which of the three failures it was before deciding what to do about it. A selection failure is a hiring problem and the process needs changing. An expectation failure is a briefing problem and it is often recoverable in a conversation. An onboarding failure is a management problem and firing the person fixes nothing.

Does onboarding actually reduce first-year attrition, or is that the hire?

Both, and they are separable. Exits inside probation are usually a selection failure and onboarding cannot repair them. Exits between month four and month twelve are usually expectation failures created during hiring and then confirmed by a weak first ninety days, and that band is where onboarding earns its keep.