The onboarding plan for the first 90 days

New hires decide early whether the job matches what they were told in the interview. The first weeks are also when a company is most likely to waste them: waiting for a laptop, waiting for access rights, waiting for somebody to explain what the team actually does.

A good onboarding plan is more than a welcome breakfast: it is a schedule with named owners that starts at the signed contract and ends after 90 days. What follows is a template you can copy, with the owners and the numbers worth measuring.

Preboarding: the weeks before day one

Most of the frustration on day one comes from work that should have happened earlier. Between signature and start date, run a short list.

• Send the countersigned contract, the start time, the address and the name of the person who will meet them.
• Order hardware, phone and access card so they arrive before the start date, not after it.
• Create and test the accounts: email, chat, HR system, the tools the role actually uses.
• Collect tax ID, bank details and certificates through a form, not as email attachments.
• Block the first week in the calendar: introductions, the first one-to-one, the team meeting.
• Tell the team who is joining, in which role, and from when.
• Name a buddy, and ask the buddy before the new hire hears about it.

One small thing has an outsized effect: a short message from the manager about ten days before the start. Two or three sentences are enough. The most common reason somebody pulls out before day one is silence after the signature.

Day one

Day one has a single job: the person should go home knowing where they sit, what they will work on and who to ask. Keep it short and human.

• A named person is at reception, on time.
• Desk, laptop and accounts all work before lunch.
• A tour: kitchen, meeting rooms, fire exits, quiet space.
• Lunch with the team or the buddy, not alone at the desk.
• Thirty minutes with the manager on the role, the first tasks and the expectations.
• The mandatory items: health and safety, data protection, the documents from any works agreements.

What to leave out: a full day of system demos, eight introductions back to back, and a folder of policies to read. None of it sticks.

The first week

• One-to-ones with the three to five people the role depends on most.
• A first small task that is finished inside the week.
• Walk through how the team works: rituals, tools, where things are documented.
• Explain the product or service in plain terms, ideally through one real customer case.
• A short conversation on Friday: what is unclear, what is missing?

The first completed task matters more than most managers assume. It turns a visitor into a colleague.

The first 30, 60 and 90 days

Split the first quarter into three phases with one written goal each. The goals have to be checkable, and the manager writes them down before the start date, not after it.

Days 1 to 30: understand

This phase is about orientation rather than output. By the end of it the person should be able to explain what the team is responsible for, who the customers are, and how work arrives and gets delivered. Concrete goals: the main tools used without help, mandatory training completed, a few small deliverables finished, every key contact spoken to once. Close the month with a structured conversation about what is clear and what is not.

Days 31 to 60: contribute

Now real tasks with a defined scope. The person works with less supervision, takes over a first recurring responsibility, and gives feedback on their own onboarding while the memory is fresh. This is also the moment to correct a role that looks different from the job ad.

Days 61 to 90: own

After three months the person should be doing the role at the normal standard and running one defined area on their own responsibility. Hold a proper 90-day review: goals for the next six months, development needs, and, where a probation period applies, an honest decision instead of a deadline that quietly passes.

Who owns what

Onboarding usually breaks at the handover between people, not inside a single step. Write the owners down.

HR

Contract, documents, payroll and the legally required training. Also the plan itself, the reminders and the checklist. HR runs the process and keeps a record that it happened. HR does not teach the job.

The manager

Goals for 30, 60 and 90 days, the first tasks, weekly one-to-ones in the first month, and the decision at the end of probation. This part cannot be delegated. A manager with no time in the first month pays for it later.

The buddy

A colleague at a similar level, outside the reporting line. They answer the questions nobody asks their manager: how long is lunch really, how formal is this channel, who actually decides. Plan for about two hours in the first week and one coffee a week after that, for three months.

What to measure

• Time to productivity: how long until one defined core task is done without help. Define that task per role in advance, otherwise the number means nothing.
• Early turnover: leavers within 90 days and within twelve months, counted separately for resignations and dismissals.
• Completion: how many steps of the plan and how many mandatory training items are finished on time.
• New-hire feedback at day 30 and day 90, with two or three fixed questions so cohorts can be compared.
• Manager feedback at day 90: is the person where the role needs them to be?

Measure few things and look at them per department. A single quarter already shows which teams onboard well, and those teams are usually where the company template should come from.

Common mistakes

• Everything on day one and nothing after week two.
• No named owner, so the plan lives in one person's head.
• Access rights that arrive in week three.
• A buddy who was never asked and does not know what is expected.
• Goals written after the start date and discussed for the first time in the probation review.
• The same plan for a graduate, an experienced specialist and a manager.
• No feedback loop, so the same gap repeats with the next hire.

How this looks in Persohap

In Persohap the onboarding plan is a learning path that is assigned to every new hire automatically. A path is a set of short lessons; each one is presented on video by an AI avatar and closes with a multiple-choice quiz with unlimited retries. Lessons can be generated from a topic, built from a document you upload (the file itself is not kept), suggested from a course, or written by hand. Every AI-drafted lesson is published by a person before anyone sees it.

If the person came through the recruiting module, hiring them creates the employee record, the department entry, the login invitation and the onboarding path in one step, so nothing is typed twice. Progress earns XP, levels and badges, which mainly helps because a new hire can see where they stand.

See how learning paths work