Free checklist · Onboarding

90 Day Onboarding Checklist

A ninety day onboarding checklist is about ramp and performance rather than setup. It asks an employer to define what full productivity looks like for the role, withdraw support deliberately rather than by neglect, gather evidence from more than the manager's own impression, hold a documented review, and set goals that continue after onboarding formally ends.

By ninety days the practical questions are long settled and a different set applies. Is this person operating at the level the role requires, or at the level a supported new joiner requires? Has the support scaffolding been taken down deliberately, or has it simply been forgotten? Does anyone other than the direct manager have a view? This phase closes the onboarding programme and hands the relationship over to ordinary performance management, and doing that transition badly is why some hires quietly stall in month four.

Define what full productivity means for this role

Fully ramped is an undefined phrase in most organisations, which makes the ninety day review a matter of opinion. Write the definition before the review, ideally at the point of hiring: the volume, the quality bar, the complexity of work handled without help, and the proportion of the role now covered.

Different job families ramp at genuinely different speeds. A support role may be near full output well inside a quarter while a specialist role with a long approval cycle may not be. Use a per role definition rather than a company wide assumption.

  • Write a role specific definition of full productivity before the review
  • State the quality bar as well as the volume expectation
  • Define what complexity the person should handle without escalating
  • Note which parts of the role are still deliberately out of scope
  • Compare the ramp against others hired into the same job family
  • Share the definition with the new hire rather than assessing against a private standard

Withdraw the support scaffolding deliberately

Onboarding support usually ends by fading out rather than by decision, which leaves the new hire unsure whether they are still allowed to ask. Naming the change is better for both sides: the buddy arrangement concludes, pairing on routine work stops, and check-ins move to the standard team cadence.

Withdrawal should be matched by an equivalent increase in scope. Removing the support without expanding the responsibility just reduces contact, which is how a well onboarded hire drifts.

  • Formally close the buddy arrangement and thank the buddy
  • Move the one to one to the standard team cadence and say that is what has changed
  • Stop routine pairing and review, keeping it only for genuinely new work
  • Expand scope at the same time as support is reduced
  • Confirm the new hire knows who to ask now that the buddy has stepped back
  • Give the new hire something to lead where they are the most senior person involved

Gather evidence before the review rather than during it

A review built only on the manager's recollection is weighted toward the last three weeks and toward whatever was visible. Collect input from the colleagues this person actually works with, look at the completed work directly, and note where they have started to be asked for rather than assigned to.

Keep the peer input structured and light. Two or three specific questions to four colleagues gives a usable picture without turning a ninety day check into a full review cycle.

  • Ask three or four working colleagues two specific questions each
  • Review a sample of completed work rather than relying on impressions
  • Note where other teams now approach this person directly
  • Check the outcomes agreed at thirty days and whether they were met
  • Separate observations about the person from observations about the conditions
  • Prepare specific examples for both the strengths and the gaps

Run this checklist inside your hiring pipeline

Free 1-user plan · No credit card

Run the ninety day review as a performance conversation

This is the first proper assessment, and it should feel different from the earlier check-ins. Cover what the person is doing well with examples, where the gap to full performance sits, what will change on both sides, and where things stand against any contractual milestone.

Nothing raised here should be a surprise. If the review contains information the person is hearing for the first time, the failure is in the preceding eleven weeks of management rather than in the review itself.

  • Confirm nothing in the review is new information to the new hire
  • State clearly whether the person is where the role requires them to be
  • Give examples for every strength and every gap raised
  • Ask what the organisation should be doing differently to support them
  • Address any contractual milestone explicitly rather than letting it pass unremarked
  • Record the outcome in writing and store it with the employee record

Set goals that outlive onboarding

Onboarding goals are about learning and ramp. The goals set at ninety days should be ordinary objectives of the kind every established employee has, aligned to the team's actual plan and running to the normal review cycle rather than to an onboarding timetable.

This is also the moment to talk about development for the first time in a serious way. What this person wants to be doing in a year influences the work you route to them now, and asking at ninety days is considerably more useful than asking at their first annual review.

  • Set objectives on the same cycle as the rest of the team
  • Align at least one goal to a current team or company priority
  • Agree a development area and a concrete way to work on it
  • Ask where the person wants their role to go over the next year
  • Confirm the reporting line, scope and title are all still accurate
  • Book the next review as part of the normal cycle rather than an onboarding step

Read the retention signals while there is still time to act

The end of the first quarter is when early doubts either resolve or harden. The signals worth watching are concrete: a role that turned out to be materially different from what was described, a manager relationship that has not developed, no visible path beyond the current job, or persistent friction with a process nobody has fixed.

Ask directly. A specific question about whether the job matches what was described in the interview process gets a much more honest answer at ninety days than at any point afterwards.

  • Ask whether the role matches what was described during hiring
  • Ask what the new hire would change about how the team works
  • Check whether the compensation and level discussion left anything unresolved
  • Look for withdrawal from optional forums and informal contact
  • Act on any process friction the person has raised more than once
  • Feed anything learned about the role back into how it is advertised next time

Close the onboarding programme and hand over

Onboarding should end on a stated date rather than trailing off. Close the task list, confirm nothing is outstanding, and record what the programme delivered so the next hire in this role gets a better version.

The handover is to normal management: the same one to one cadence, the same objective cycle and the same development conversations as everyone else. Leaving someone permanently classified as a new joiner is its own problem.

  • Confirm every outstanding onboarding task is closed or explicitly dropped
  • Run a short retrospective with the new hire on the programme itself
  • Record which parts of the programme worked and which were skipped
  • Update the role template for the next hire based on what was learned
  • Move the person onto the standard management and review cycle
  • Tell the person plainly that onboarding is complete

Get this checklist emailed to you

We'll send this checklist plus the rest of the onboarding pack — and the occasional hiring tip. No spam, unsubscribe anytime.

No spam — just the resource and the occasional hiring tip. Unsubscribe anytime.

FAQ

90 Day Onboarding Checklist — FAQs

What should be covered in a ninety day review? +
Performance against the role definition with specific examples, progress since the thirty day conversation, input from working colleagues, the person's own view of the role and the support they received, and objectives for the coming period. It should also address any contractual milestone directly rather than leaving it implied.
Should the ninety day review decide whether someone passes probation? +
Where a probationary period exists it will have its own dates and process defined in the employment contract and shaped by local law, and those may not align with ninety days at all. Run the performance conversation on its own merits and handle any contractual decision according to the terms that actually apply to that employee.
How do we know if someone is ramping too slowly? +
Compare against a written definition of full productivity for that role and against others hired into the same job family, rather than against a general impression. Slow ramp with clear expectations and delivered support is a performance signal. Slow ramp where expectations were never documented is a management signal, and the fix is different.
Is ninety days the right length for onboarding? +
It suits many individual contributor roles. Roles with long sales cycles, heavy regulatory training or deep domain complexity often need longer, and some operational roles are fully ramped well before it. The important thing is that the length is chosen and stated for the role rather than inherited as a default.
Should peers give feedback on a new hire at ninety days? +
Light structured input from a few working colleagues is valuable because it catches things a manager cannot see, particularly around collaboration. Keep it to two or three specific questions and be clear how it will be used. A full multi rater review at this stage is disproportionate for most roles.
What if the role has changed since the person was hired? +
Say so explicitly and rewrite the role definition. Silent scope drift is a common cause of early departures, because the person accepted one job and is being assessed against another. Where the change is significant, revisit level, title and compensation rather than hoping the mismatch resolves itself.
How do we stop support dropping off after ninety days? +
Move the person onto the same cadence as everyone else at the point onboarding closes, rather than letting contact decay. If your standard cadence is itself thin, the ninety day handover will look like abandonment regardless of how good the onboarding was, and the underlying problem is the management routine rather than the programme.
Pitch N Hire ATS

Run this checklist inside your hiring pipeline

Pitch N Hire is an applicant tracking system. The steps on this page become stages in a pipeline, so nothing is skipped and everyone can see where each candidate stands.

  • Turn process steps into pipeline stages the team follows
  • See exactly where every candidate is, without status meetings
  • Keep notes, feedback, and documents on the candidate record

Free for 1 user · No credit card · Talk to a real hiring expert

Built for recruiters & hiring teams

Onboard new hires from the same system you hired them in

Pitch N Hire keeps the offer, the paperwork trail, and the candidate record in one place — so nothing is retyped between hiring and day one. Start free with the 1-user plan.

Prefer to talk? Book a demo · Talk to sales · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo