Most onboarding plans I have seen fit on a Post-it. “Day one: HR paperwork. Day two: shadow Sarah. Week two: you should be getting the hang of it.”
Then Sarah is off sick on day two, nobody wrote down what she shows people, the new starter spends three days reading old Slack threads, and by the end of the month you have a confused colleague and a manager who is quietly wondering whether the hire was a mistake.
It probably was not a mistake. It was probably an onboarding failure. CIPD's research on the link between early-tenure experience and attrition is fairly consistent: people who feel lost in their first weeks are significantly more likely to leave inside a year. The cost of re-hiring dwarfs the cost of onboarding them properly the first time.
What follows is a structured 30-day playbook. Week by week, what the manager does and what the new starter should actually experience. It is not clever. It is repeatable - which is the point.
Before they start: the quiet week
Onboarding begins before day one. The week before your new starter arrives, three things need to be true.
- Tooling is provisioned. Laptop, accounts, building access, uniform, PPE, parking, whatever the role needs. Provisioning on day one wastes the morning that should be spent on welcome.
- A written 30-day plan exists.Not in the manager's head. Written down, shared with the new starter, with week-by-week outcomes and named people for each thing.
- The team knows they are coming. Name, role, start date, one line about background. Silence from the team on day one reads as indifference, even when it is just distraction.
The week-before step is the cheapest lever in the whole playbook. Most managers skip it. The ones who do not, almost never have a chaotic first day.
Week 1: arrival and immediate induction
The goal of week one is not productivity. It is orientation and psychological safety. A new starter should end the first week knowing where things are, who does what, what the non-negotiables are, and that it is safe to ask questions.
What the manager does
Be there on day one morning. If you cannot be there, postpone the start date. Nothing signals “you matter” like the person who hired you being present for the welcome. It also signals the opposite.
Then, across the week:
- Deliver the mandatory induction content: health and safety, fire and emergency procedures, acceptable-use policy, any role-specific statutory training. E-sign the acknowledgments so there is a record.
- Introduce the team properly. Not a drive-by “this is Tom,” but short scheduled conversations where Tom explains what he does and how his work touches the new starter's.
- Walk the physical or digital environment. Where things are stored, how the key systems hang together, which tool is used for what.
- Schedule a short daily check-in, even fifteen minutes, for the whole first week. Two questions: what have you done, and what is blocking you.
What the new starter experiences
A structured day one with a working laptop, a tour, a lunch, and three or four proper introductions. An end-of-week one-to-one where they can say “I do not understand how X works” without feeling like they have already fallen behind. A shadowing day where an experienced colleague takes them through a real task end to end, not a sanitised demo.
By Friday of week one, a new starter should be able to answer these without looking them up: who is my manager, who do I go to with an urgent problem, where do I find the SOP for task X, what are the three non-negotiable safety or compliance rules in this role, and where do I record that I completed a task.
One concrete output by end of week one.Not a deliverable in the traditional sense. A small, real, useful thing - a completed SOP run, a closed ticket, a first customer call with a senior colleague listening in. Something that lets them say “I contributed” when someone asks how the week went.
Week 2: supervised execution of core tasks
Week two is where shadowing graduates into doing. The new starter attempts the core tasks of the role, with close supervision, and with the documentation in front of them.
What the manager does
- Assign two or three of the most frequently-performed tasks as the week's focus. Not every task the role ever does - the common ones, in priority order.
- Pair them with the named SOP or work instruction for each. If the SOP does not exist in a usable form, that is a signal the task is not ready to be delegated yet. Fix the documentation before delegating.
- Require photo proof or a completion log on tasks where quality or compliance matters. This serves two purposes: it builds the habit of evidence from day one, and it gives you something concrete to review in the one-to-one.
- Assign a knowledge check after each core task - a short quiz testing judgment, not recall. “What would you do if the reading is out of spec?” beats “what is the spec?”
What the new starter experiences
Real work, with a safety net. Someone watching nearby the first few times they attempt a task. A documented procedure to follow so they are not relying on memory or on what Sarah showed them last Tuesday. Short quizzes that feel like reinforcement rather than gatekeeping. A one-to-one at the end of the week where the manager says “here are two things you are doing well, here are two things to tighten up.”
By Friday of week two, a new starter should have completed a handful of core tasks with evidence logged, passed the associated knowledge checks at least on a second attempt, and have a named list of what they will take on more independently in week three.
Week 3: lower supervision and a real feedback cycle
Week three is the transition from “watched” to “working.” The new starter owns the tasks they learned in week two, with the manager or a senior colleague available rather than alongside.
What the manager does
- Step back deliberately. If you were sitting next to them in week two, move to the next desk. If you were in the same room, move to available-on-Slack. Make the reduction visible, so they notice that you are treating them as trusted.
- Expand the task set. Introduce the next tier of responsibilities - the ones that come up weekly rather than daily. Assign the documentation, then let them attempt.
- Run a proper feedback conversation at the midpoint of the week. Not “how is it going?” which invites “fine.” Ask what was harder than expected, what felt easy, which SOPs did not match reality, and what they would change about the onboarding so far.
- Invite them to improve the documentation. If they followed an SOP and something was wrong, unclear, or missing, that is information. Fresh eyes find bugs experienced eyes no longer see.
What the new starter experiences
Ownership. Real responsibility. The confidence that comes from completing a sequence of tasks without being walked through each one. A manager who is visibly treating them as a contributing member rather than a trainee. A sense that the feedback loop goes both ways - what they think matters.
Week three is where many onboarding plans quietly collapse, because the structure of weeks one and two is not replaced by anything. The answer is not to invent ceremony; it is to keep the check-ins running and to keep expanding the task set at a deliberate pace.
Week 4: solo tasks and the 30-day review
By week four, a competent new starter should be running core tasks independently, flagging anything unusual, and starting to contribute beyond pure execution - spotting a process improvement, helping with an edge case, asking a sharper question in a team meeting.
What the manager does
- Assign genuinely solo work. Not “do this while I watch.” Assignments where the check-in happens after the work, not during.
- Prepare the 30-day review. Pull the evidence: knowledge-check scores, completed task logs, photo proof, manager notes from weekly one-to-ones, peer feedback if appropriate. Review against the plan you shared on day zero.
- Hold the review as a proper conversation, not a tick-box. Two outcomes: a calibrated view of where the new starter is, and a named 30-to-60-day plan for what comes next.
- Ask them directly: is there anything you expected by now that has not happened? Is anything worrying you? Would you recommend this onboarding to a friend who joined next month?
What the new starter experiences
A sense of having arrived. Tasks they owned, not just tried. A review that is honest about what is going well and what needs work - delivered in a tone that suggests both sides want the person to succeed. A concrete plan for the next 30 days that is not a copy-paste of the last 30.
One thing that almost always comes up in a 30-day review. A piece of tribal knowledge that nobody documented, that the new starter wasted time discovering on their own. Write it up before the next hire arrives. That is how onboarding gets better across hires instead of resetting each time.
Why shadowing alone does not work
“Just shadow Sarah for two weeks” is not a plan. It is a wish. Shadowing as the default onboarding strategy has three problems.
First, it is dependent on one person. Sarah gets sick, goes on leave, is busy with her own work, or leaves the company. The new starter's onboarding pauses.
Second, it conveys no version-controlled truth. Sarah teaches the way she does it, which may or may not match the documented procedure, and may include habits formed around equipment that was replaced two years ago. The new starter learns Sarah-flavour, not company-flavour.
Third, it has no verification. There is no test at the end of Sarah's week of shadowing that proves the new starter absorbed what she tried to convey. You find out at the first real task, which is the wrong place to discover a gap.
Shadowing has a role - it is genuinely useful for observing how an experienced person handles edge cases and how the work feels in practice. But as the whole plan, it fails more often than it succeeds.
What good 30-day onboarding earns you
When the first 30 days are structured, three things compound. New starters contribute meaningfully by week four instead of week twelve - and they know it, which changes how they feel about the job. Managers spend less time answering the same questions, because the answers live in documents rather than in heads. And attrition in the first year drops, because people who feel competent and welcomed tend to stay.
The mechanics are not complicated. A written plan. Mandatory induction done properly on day one. Supervised practice with documentation in week two. A deliberate hand-off to ownership in week three. A proper review in week four. Evidence collected along the way so the review is based on what happened, not on impressions.
If you are running onboarding without a written 30-day plan, start there. Everything else follows. See how TrainedTeam supports structured onboarding if you want to take the paperwork out of running it.