New hire onboarding plan: a template for the first 72 hours
Published Friday 13 November 2026 by 3D CODED LIMITED
Most onboarding plans describe the first few months. This one covers the first 72 hours, when small gaps (a missing login, nobody to ask, no real work) are easiest to spot and quickest to fix. Each phase ends at a checkpoint and is either passed or not.
The three phases
The plan splits the first 72 hours into three 24-hour phases. In working-days mode these are the first three working days.
- Hours 0–24, initial orientation and system access: every account they need works, they know who does what and where the work lives, and they have met their buddy.
- Hours 24–48, first deliverable assignment: one real piece of work is assigned in writing, with the checks that decide whether it passes, and work has started.
- Hours 48–72, output validation and pass/fail: the work is checked against each criterion and the result is recorded as pass or fail.
What to decide before day one
A 72-hour plan only works if the preparation happens before the start date. Four decisions cover most of it:
- The accesses. List every system, account, device and physical pass the role needs in its first week, and who sets each one up. “Access works” means signed in and used, not just requested.
- The buddy. Name one person, other than the line manager, who is the first port of call for questions, and block time in both diaries for the first check-in.
- The first deliverable. Pick a piece of genuine work that someone in the team would otherwise do, small enough to finish in about a day of effort.
- The checks. Write two to five pass/fail criteria for that work, and name who will check it.
Writing pass/fail criteria that work
A criterion is useful if two different people would reach the same answer when they check it. Compare:
- Vague: “Good understanding of the order system.” Checkable: “All 10 orders updated in the order system with no errors.”
- Vague: “Shows initiative.” Checkable: “Note names at least two specific things that slowed the work down.”
- Vague: “Gets up to speed.” Checkable: “Handed in by the Day 3 checkpoint.”
A fail is information about the plan as much as the person. If access was not ready on day one, the deliverable had less time, and the record will show it.
Running the checkpoints
Put the three checkpoints in the calendar of whoever signs them off. At each one, go through the lines for that phase and tick only what is actually done. A phase with one line missing has not passed yet; note what is missing and when it will be fixed.
At the end, record when the first real output arrived. If it landed by the hour-72 checkpoint, it was inside the window.
Using the free template
The planner on this site turns those decisions into a one-page plan with a checklist, a calendar file for the three checkpoints and a plain-text copy. It runs in your browser and keeps the plan there.