Onboarding: not leaving the first 30 days to chance

How to structure new-joiner onboarding — task lists, named owners, the first-day experience, buddy systems and measuring whether the process actually works.

A new employee's first week determines their lasting impression of the company. Despite that, in most organisations the week is left to chance: the laptop isn't ready, they don't know who does what, and half the first day goes on asking "who do I ask about this?"

The point of an onboarding module is to turn that week into a process — without reducing a warm welcome to a document.

Onboarding is three separate jobs

When they're mixed, none of them runs properly:

  1. Preparation — everything before the person arrives: hardware, accounts, access, desk.
  2. Introduction — the company, the team, the processes, the tools.
  3. Ramp-up — starting to do the job itself; usually the first 90 days.

The module's real contribution is in steps one and two. The third belongs to the manager and can't be templated.

The task list: who, when, what

A good onboarding template has three columns: task, owner and timing (days before or after the start date). For example:

  • Laptop preparation — IT — 3 days before start
  • Account creation and access — IT — 1 day before
  • Welcome and team introduction — Manager — day 1
  • Safety and data-protection training — HR — first week
  • Day 30 check-in — Manager — day 30

The critical part is that owners are people. Not "IT" but a named person. Collective responsibility turns into no responsibility here too.

The first-day experience

The goal of day one isn't to transfer information; it is for the person to feel expected and prepared for. Three small things produce that: their computer is ready when they arrive, the team was told in advance, and they don't eat lunch alone.

On the intranet side the equivalent is this: new joiners appear on the homepage, and the person sees their own onboarding list at first sign-in. Showing the three items for day one instead of a twenty-item list markedly raises completion.

The buddy system

One of the lowest-cost, highest-impact practices: assign the new joiner a "companion" who isn't their manager. They become the address for questions people are shy to ask.

The buddy's job isn't to train, only to be reachable. Recording the assignment in the system means the person knows who to ask and the buddy sees the responsibility.

Access to information: teach searching

What a new employee needs most isn't a document but the ability to find documents. Instead of making them read five policies during onboarding, showing them how to find what they need lasts longer: how search works, how to reach someone through the directory, which question goes to whom.

That's why the onboarding module gains meaning alongside the document centre and the employee directory — we cover the latter in a separate article.

Differentiate for remote and frontline

Onboarding someone who never comes to the office doesn't run on the same template. A remote starter needs hardware shipping, a digital welcome and more frequent check-ins. In a store or field team most of onboarding happens on site; there the system has to work on a phone and stay short.

Most companies that run a single template see completion rates drop in the second group.

Match the template to the role

One onboarding template is either too much or too little for different roles. A software engineer's first week and a store assistant's first week have little in common beyond a few items.

The practical answer is a two-layer template: common items (accounts, safety and data-protection training, company introduction) and role-specific items (vehicle access, field training, till authorisation). The common layer is defined once; the role layer is added by the relevant manager. Standard is preserved and the template still fits the real job.

Think about offboarding too

The mirror of onboarding is the exit process, and it is usually neglected: returning assets, closing access, handover notes, the exit interview. The same task-list logic works here, and it matters for data protection — how long which data is kept is defined in this process. Details are in our compliance article.

Measurement

Three indicators are enough:

  • Completion rate — what share of assigned onboarding tasks finished on time?
  • Day-one readiness — were hardware and accounts ready when the person arrived?
  • Day 30 feedback — a short survey: what couldn't you find, what was missing?

The third writes the next onboarding template directly. We cover process ownership and regular review in our operations article.