Have you ever built an onboarding checklist and still scrambled as the start date approached?
The welcome kit is ready but account setup is missed; the team intro meeting is booked but nobody owns setting the first work goals. Equipment and paperwork are prepared, yet the new hire spends an awkward first week not knowing what to actually start with.
Onboarding underperforms not because there is no onboarding program. Most companies already run orientations, welcome kits, team introductions and mentor schemes. The problem is that what, when and who is not clear.
Why a checklist matters
An onboarding checklist isn't a list of tasks. It's an operating standard that helps a new hire settle in and begin performing, from before the start date through day 90.
It reduces variance in the onboarding experience across owners and teams, and makes the responsible party for each stage explicit.
The cost of failed onboarding
Early attrition costs more than people assume — job postings, screening, interviews and re-training, plus the resources existing team members spent supporting the new hire.
SHRM emphasises that structuring onboarding is critical to successful settling in, and Gallup found only a very low share of employees felt their onboarding experience was sufficiently positive.
Repeated small omissions confuse a new hire quickly. A systematic checklist, by contrast, builds the trust that "this organisation prepared for me."
What happens without one
Onboarding depends on the owner's memory and experience. It looks fine while a familiar HR person runs it, but when that person changes or several hires start at once, items get missed. A busy team leader pushes back introductions; a mentor helps only nominally without knowing their role.
Onboarding stops being an operating process and becomes an informal one that varies with how well someone happens to take care of it.
Stage-by-stage
| Stage | Purpose |
|---|
| Preboarding (before start) | Reduce uncertainty, build anticipation |
| Day 1 | Belonging and basic environment setup |
| 30 days | Understanding the work, forming relationships |
| 60 days | Working independently |
| 90 days | Performance review and forward goal setting |
Preboarding
The most commonly missed window is between offer acceptance and the start date. With no contact, the new hire wonders whether they chose correctly.
The point of preboarding isn't information delivery. It's reducing pre-start uncertainty.
HR should handle:
- Start time and location, documents to bring, dress code, first-week schedule — everything the hire will wonder about
- Laptop, ID card, email, messenger and collaboration tool accounts set up in advance
- Sharing the start date and role with the team leader and mentor
Only then can day one be spent understanding the organisation rather than on admin and device setup.
Day 1
The goal isn't to deliver a lot of information. Creating the feeling that "this organisation welcomes me" and the confidence that "I can work here" matters more.
The one thing a team leader must do on day one is briefly share the expected role. Detailed performance targets aren't needed, but the new hire needs a reference point for which direction to adapt in.
30 days: the month of understanding
The new hire starts learning how the company works, the team's workflow, collaboration relationships and systems. Check understanding and relationships rather than output. For HR it's the first mid-point check that onboarding is running as planned.
The point isn't only checking whether something went wrong, but confirming how the hire understands the work and the organisation and aligning on the direction of adaptation.
60 days: the month of trying
Beyond learning, the hire begins working independently, and the leader's support shifts from guidance to coaching.
The 60-day check-in acts as a pre-review for day 90 — finding a mismatch in expectations or a support gap here creates time to fix it before the formal evaluation.
90 days: probation review and the shift to performance management
The formal end of onboarding and the start of performance management.
Treating this purely as "probation ends" makes onboarding a one-off. Running a performance review and forward goal setting together brings the new hire naturally into the organisation's performance cycle.
Roles: the mentor is what gets neglected
Overlapping HR, leader and mentor roles create confusion; gaps mean nobody handles something.
The mentor role is the easiest to under-design. Defined only as "a friendly colleague," the mentor doesn't know what to do and the new hire doesn't know what to ask for.
Give mentors a separate one-page role guide:
- At least one coffee chat in the first week
- Explaining the team's informal communication norms
- Supporting daily adaptation — lunch, meetings, collaboration tool conventions
- Passing to HR or the leader the things a new hire finds hard to ask
- Not evaluating performance, but listening for friction in adaptation
Seven commonly missed items
Admin and equipment usually make the list. The items that actually drive adaptation often don't.
1. Documented role expectations — verbal explanation in week one is common, but scope, priorities, expected outcomes and collaboration norms in a short shared document orient a hire far faster.
2. 30- and 60-day check-ins — with only a 90-day review, problems surface too late. Schedule short check-ins in advance.
3. A mid-onboarding satisfaction survey — many ask afterwards, few ask briefly at two weeks or 30 days. Equipment, accounts, information access, team fit and task comprehension are best checked early.
4. A mentor role guide — assigning a mentor without defining the role makes the scheme nominal. A mentor is a connector, not an evaluator.
5. Informal cultural norms — where people sit before meetings, emoji reaction conventions, team lunch habits, pre-decision sharing practices are the hardest tacit rules to pick up, and are conveyed better through a mentor or teammates than formal orientation.
6. Hands-on time with tools and systems — issuing accounts without explaining usage costs the hire a lot of solo learning time. Schedule short practical sessions in week one.
7. A retrospective after onboarding ends — HR, leader, mentor and the hire together, recording what helped, what was missing, and what to improve for the next hire.
Connecting it to performance management
| Point | Performance link |
|---|
| 30 days | Agree initial goals based on role and team objectives |
| 60 days | Record feedback from actual work to identify strengths and development areas |
| 90 days | Connect probation results into the regular performance cycle |
What matters is keeping the information generated during onboarding from scattering. If one-on-one conversations, check-in results, feedback and probation reviews live in different documents and chat threads, connecting them to performance management after day 90 is difficult.
In closing
The more granular the stages, the fewer omissions. The clearer the roles, the better HR, leaders and mentors perform them. The more 30/60/90 check-ins exist, the more systematically adaptation and growth are managed.
You don't need a perfect checklist from the start. Simply holding a short retrospective after this onboarding — HR, leader, mentor and the hire — and recording it develops the checklist to fit your organisation.
References: SHRM, Onboarding New Employees: Maximizing Success / Gallup, Why the Onboarding Experience Is Key for Retention
(Adapted from an article provided through a partnership between CLAP and Mobiinside. Product promotion has not been carried over.)
Practical takeaways
The gap isn't the program, it's the who and when. Orientation, welcome kits and mentor schemes already exist; ownership and timing are what's missing.
Fill the preboarding gap first — the most-missed window is between acceptance and day one, and it costs the least to fix.
Attach a subject and a time to every item. Write "on day 1 the team leader introduces team members and their roles," not "conduct team introduction."
Give mentors a one-page guide. Assign-and-abandon is the most common failure; state the boundary explicitly — connector, not evaluator.
Add a survey at two weeks and 30 days. A satisfaction survey run after onboarding ends only helps the next hire.
Convey tacit norms through people, not documents — precisely the items that don't fit formal orientation.
Accumulate onboarding records in one stream. Scattered one-on-ones, feedback and reviews never connect to post-90-day performance management — on handling such records with AI, see How Baedal Minjok Turned an AI Agent Into a Problem-Solving Colleague.
Turn repeated explanation into an asset — the same concern as Marketers Who Re-Explain Their Brand Every Time vs Those Who Don't.