New hires most often leave in the first six months. Gallup finds that only about one in ten employees strongly agrees their employer did a good job of onboarding them. If the first 90 days lack structure, HR pays for replacement instead of growth.
Most EU jurisdictions treat this first quarter as more than an intro course. Probation periods commonly stretch to six months, so the first 90 days sit as half of that decision window. It is the only realistic time for a manager to gather evidence, not impressions. The checklist below splits the window into three phases and sets measurable milestones for each.
Why 30-60-90, not one long checklist
One long list creates two patterns. HR ticks admin items in week one, then the structure dissolves. The employee also loses the sense of what they should be able to do today.
The 30-60-90 model gives each phase its own purpose:
- Days 1–30 — orientation. The hire understands the product, the team, key processes, and mandatory obligations (workplace safety, GDPR).
- Days 31–60 — supervised autonomy. Takes a first micro-task end to end, with weekly reflection from a mentor.
- Days 61–90 — measurable contribution. Delivers at least one business outcome you could also measure against a colleague with two years on the job.
Each phase gets 3 to 5 verifiable goals — not activities. "Finish the safety module" is an activity. "Identify 6 hazards in a sample office and report them verbally in an exercise" is verifiable. If you cannot grade a goal without discussion, rewrite it until you can.
Days 1–30: orientation checklist
The first month covers hard admin and structured familiarisation. It is not the time for large projects.
- Day 0 (pre-arrival). IT prepares equipment, access, and email. The mentor receives the onboarding plan for this specific hire, not a generic template.
- Day 1. Short intro (2 hours), office tour, lunch with the team. Not a full day of slides.
- Week 1. Mandatory modules: workplace safety (before starting work, as most EU labour law requires), GDPR basics, code of conduct. Each module ≤15 minutes.
- Week 2. Industry and product — 3 short modules of 5–7 minutes, each paired with a practical task.
- Week 3. Shadowing in three roles (sales, support, engineering) for 90 minutes each.
- Week 4. First independent micro-task (e.g. answering a typical support ticket, reviewed by the mentor).
30-day checkpoint. A 30-minute conversation: what the hire understands, what they don't. The manager does not grade performance — only checks comprehension. If completion of mandatory modules is <100 %, they must be finished before the next phase. For how to write verifiable checkpoint goals, see learning objectives that work.
Days 31–60: supervised autonomy
The second phase shifts focus from learning to practice. Goals get narrower, milestones more frequent.
- Week 5–6. The hire takes on a recurring task from the team's daily work. The mentor reviews the output, not the process.
- Week 7. First written weekly status (5 lines: what I did, where I got stuck, what I need). This is not bureaucracy — it is a self-reflection habit.
- Week 8. The hire presents a 10-minute review of one customer or project they handled. Mentor and manager present.
A quiz mid-phase helps: 10 scenario questions ("What would you do if…"), not definitions. If the pass rate is <70 %, the module gets repeated, not pretended-understood.
60-day checkpoint. Manager and HR review milestones, quiz results, mentor notes. Decision: continue as planned, add mentoring, or resolve the probation (where the contract sets a probation term, this checkpoint is the fair point to decide).
Days 61–90: measurable contribution
The last third demands an outcome, not effort.
- Week 9–10. The hire takes one project end to end — limited scope, but real. For an HR assistant: rewrite the onboarding questionnaire. For a developer: one independent PR that ships to production.
- Week 11. A role-specific metric falls into target (e.g. ticket response time <4 hours, or 5 completed sales calls per day).
- Week 12. A 60-minute conversation: self-review, mentor review, plan for the next 6 months.
90-day checkpoint. Three results: 100 % completion of mandatory modules, at least one quantified role metric hit, mentor sign-off that the hire is no longer under weekly supervision. If any of the three doesn't hold, probation should not convert to regular employment.
Two worked examples
Example 1: HR assistant at a 45-employee company.
- Days 1–30: finishes workplace safety, GDPR, code of conduct, plus 3 modules on the HRIS. Shadows payroll and the sales lead (contracts).
- Days 31–60: independently drafts a fixed-term contract from a template. Reads three existing exit-interview transcripts and writes a 1-page summary on what departing hires under 12 months tenure had in common.
- Days 61–90: rewrites the onboarding questionnaire. Runs the first version on two new hires. KPI: average onboarding case processing time <3 working days.
Example 2: junior full-stack developer on a team of 12 engineers.
- Days 1–30: mandatory modules plus 5 technical ones (git flow, code review rules, deploy pipeline, test framework, on-call basics). First PR: a small UI change.
- Days 31–60: takes two bug tickets from the backlog, both closed within two days. Participates in two code reviews per week.
- Days 61–90: one independent feature (a small API endpoint extension). Metric: 90 % of PRs merged with no more than two review rounds.
What is worth documenting
Don't log every step — only the three things that vanish otherwise:
- Completion of all mandatory modules (safety, GDPR, any industry-specific courses). This is legal evidence, not HR aesthetics.
- The 30, 60, 90 milestones. Date, attendees, agreed goals for the next phase.
- Deviations. If the hire exceeded plan or missed a mark — write it, don't say it. Probation ends with a document, not a feeling.
An LMS like Mentor holds this structure together: the 30-60-90 milestones live inside the template, mandatory modules automatically lock the transition into the next phase, and the report for leadership generates without manual collation. HR time then goes into the conversation with the new hire, not into ticking a list.