Free template
First 30 days onboarding handoff
The hiring process learns a great deal about a person, and most of it is lost the day they accept. This template moves what you know — the accepted risks, the gaps, the things they were promised — into a first month with owners and dates.
Who fills it in
Hiring manager, handed to whoever runs onboarding.
How long it takes
Twenty minutes at offer acceptance, reviewed weekly for a month.
Reviewed by
Joseph Edney, 29 October 2026
When to use it
Use it when
- An offer has been accepted and the start date is set.
- The decision scorecard recorded risks or untested areas to address early.
- The manager who hired is not the person who will onboard them.
What good looks like
- The accepted risks from the decision record appear here with a named owner and a date.
- Week one has something real to do, not only reading and introductions.
- The promises made during the process are written down, so they are kept.
- There is a scheduled honest conversation in the first month, booked before the start date.
Common mistakes
- Starting the first day with no accounts, hardware or first task ready.
- Assuming the new starter will ask when they are stuck. Most will not, early on.
- Forgetting what was promised at offer stage, which is the fastest way to lose a new hire.
- Treating a quiet first month as a good sign rather than checking.
The template
Anything you type stays in this browser tab, so reloading the page keeps it. It is not sent to us or added to the link, so it is safe to put real salary numbers and colleagues’ names in. Closing the tab clears it — copy or print before you go.
Handoff summary
Use it early. People do their best work when the first task plays to it.
Scope, tools, budget, progression, working pattern — anything said out loud.
Ready before day one
The first month
What should be true at each point, who owns it, and how you will know. Keep it small enough to actually happen.
| Row | What should be true | Owner | How you will know |
|---|---|---|---|
| End of week 1 | |||
| End of week 2 | |||
| End of week 4 | |||
| Honest review conversation (date booked) |
A worked example
Illustrative example. The company, role and answers are fictional, written to show a finished template. It is not a client, a quote or a result. The fictional clinic-scheduling startup from the earlier examples, the week Candidate B accepted the platform engineer offer. The CTO hired and will also onboard, so the product engineer is the buddy. One item is honestly not ready yet.
Handoff summary
- New starter and role
- Candidate B, platform engineer (first infrastructure hire). A reference only; no personal details in this record.
- Start date and first-week owner
- The start date in the signed offer. First-week owner: the CTO, with the product engineer from stage 2 as buddy.
- What the process showed they are strong at
- Owning on-call and fixing noisy alerts, and changing a shared process by starting from what it means for the people who use it. The first task plays to the first: rewrite the alert that wakes the CTO most often.
- Accepted risks and untested areas from the decision record
- Carried over from the decision record. Debugging under pressure was seen in one outage story, not two, so the CTO stays on the rota alongside them and they review any early incident as a pair. Their runbooks were written for experts, so a product engineer releases from their first one. Nobody tested whether they can own the cloud bill: they write a brief spending summary this month, and it is looked at properly when the quarter ends.
- Promises made during the process
- That they would join the rota straight away but never hold it alone at first. That they decide how releases reach customers and how the service stays up. That they help interview the next engineers. That they lead the answers to the clinic group's security questions. Pay and equity exactly as the written offer states; nothing else was promised out loud.
Ready before day one
- Done: Hardware, accounts and access requested and confirmed
- Done: Contract signed and payroll set up
- Done: Named buddy or first point of contact who is not the manager
- Done: A real, small first task identified
- Done: Week-one meetings booked in the diary
- Not yet: Context pack: what the company is doing this quarter and why
The first month
| Row | What should be true | Owner | How you will know |
|---|---|---|---|
| End of week 1 | The rewritten alert is live, and they have shadowed the CTO on call and can say who to contact for each service. | CTO | The change is in production, and they walk the CTO through the on-call map without notes. |
| End of week 2 | Their first runbook exists, and the product engineer has run a release from it with them watching but not helping. | New starter, with the product engineer | Every question the product engineer had to ask is listed and answered in the runbook, not in chat. |
| End of week 4 | They hold the rota jointly with the CTO, any incident so far has a review they wrote as a pair, and the spending summary is written. | CTO | Both names are on the rota, and the CEO has read the summary and asked their questions. |
| Honest review conversation (date booked) | Booked before the start date, CTO and new starter only. Each says what is and is not working, and each promise above is checked. | CTO | Every promise is marked kept, in progress or changed with a reason, and the new starter has said one thing they would change. |
The thinking behind it
- What happens to recruitment fees when a hire leavesRebates, tapers, replacement clauses and monthly models explained, with the exact questions to ask any recruiter before you sign.
- When not to hireThe cases where a permanent hire is the wrong answer, the alternatives worth testing first, and the signals that a role is genuinely ready.