Blog

Employee onboarding checklist: bringing new people up to speed when you've been explaining everything yourself

New employee onboarding is the period in which someone new learns to do their job without having to ask. In many businesses with a small team, there's no HR department and no program for it. There's the owner. Whoever starts needs weeks to learn the workflows, and who explains them? Usually you. In this article, we share an employee onboarding checklist for the first weeks, the method we use to train people on workflows, and why the real work happens before day one: writing the workflows down, so that every question doesn't land on your desk.

What belongs to hiring someone from an employment law, data protection or workplace safety point of view isn't covered here. Those are questions for your payroll provider, your tax advisor or a lawyer. This article is about how someone new takes over your workflows.

Why onboarding in a small business depends on the owner

In a business with 3 to 15 people, onboarding often happens on the side. The owner hires, shows the new person their desk and answers whatever questions come up over the next few weeks. That works as long as people rarely start. But it has three consequences many owners will recognize:

  • Your time is the bottleneck. Every question from the new colleague interrupts your work. And because you usually know the answer, it's quicker to give it than to write it down.
  • Onboarding is different every time. What one person gets explained depends on which cases happen to come up in their first weeks. Rare special cases only get learned the first time they go wrong.
  • Knowledge moves from head to head. After onboarding, part of your knowledge sits in the new person's head. If they leave, everything starts over.

It's the same dependence described in When the business depends on its owner, just showing up in a different place.

What good onboarding has to achieve

By the end of onboarding, a new person should be able to do three things:

  1. Know the people and roles. Who does what, who approves what, whom do I ask about which topic? That includes the AI employees, if your business has any.
  2. Run their own processes. The workflows they were hired for, with the usual variants, without asking.
  3. Know where an unclear case goes. No workflow is described completely. What matters is that the new person knows who gets a case they can't place with certainty, and that a new rule comes out of it.

The third point is missing from most onboarding. Without it, every unclear case lands back with you. We call this route the escalation path: the case goes to a named person, and in the feedback conversation afterwards, the new variant is saved as a rule.

The four phases of onboarding

We suggest splitting onboarding into four phases. How long the last one takes depends on the scope of the job, so we don't give a fixed number.

Before day one. The workstation, the logins and the documents the new person should read are ready. Above all: for every process they're supposed to take over, there's a process profile, our word for a process description.

Day one. The new person meets the team, gets a fixed buddy, sees the map of all processes and learns which of them are theirs.

The first week. They watch their processes being done, read the process profiles and ask questions. At the end of the week, there's a short conversation: what's clear, what isn't?

The weeks until sign-off. One process at a time, they take over the work, first with someone next to them, then on their own with feedback. Once a process runs cleanly, it's signed off, and the next one is up.

An employee onboarding checklist to copy

Copy this list into a text file or a spreadsheet and adapt it to your business. How to build a checklist so it actually gets used is covered in How to create a checklist your team actually uses: structure, template and the step to an AI employee.

Before day one

  • Workstation and devices are set up.
  • Access to email, filing and industry-specific software is set up, only as far as the job requires.
  • A buddy from the team is named and has blocked out time.
  • The processes the new person will take over are decided.
  • For each of these processes, there's a process profile, or it's planned when it will be written.

Day one

  • Introduction to the team, with roles and not just names.
  • The process map has been shown, and their own processes are marked.
  • The escalation path has been explained: who gets an unclear case, and how?
  • If there are AI employees: which ones, what they do, which reports they send and who looks after them.

First week

  • Watched each of their own processes once.
  • Read the process profiles and noted questions.
  • Conversation at the end of the week: what's clear, what's missing from the process profile?
  • Gaps in the process profile filled in by the person who has run the process so far.

Until sign-off, per process

  • Did every usual variant once with someone next to them.
  • Walked through the escalation path once.
  • Several runs on their own, with feedback afterwards.
  • Sign-off noted: from now on, they run the process alone.

After that

  • A feedback conversation after the first weeks: what would have made onboarding easier?
  • The answers go into the process profiles and into this checklist.

Training in four steps

For the last phase, we use the same method we use to train AI employees. It has four steps: watch how the team does it; sit next to them and walk through each variant once; note and ask through the escalation path and the feedback conversation; sign off once several runs were clean.

That's no coincidence. In our approach, an AI employee is hired like a new employee: with a job description, a trial task and a permanent position. The reverse holds too: whatever gets written down for an AI employee helps a new person just as much. Both need the same answers to the same questions. What the first phase looks like for an AI employee is covered in Autonomy Level 1, Assisted: when your team checks every run.

What to write down beforehand

The biggest lever for good onboarding comes before day one. The more is written down, the less onboarding depends on your time. Three things are enough to start:

You don't have to write everything at once. Onboarding itself is a good moment: the person who has run a process so far adds to the process profile at every point where the new person asks a question. That way, every onboarding gets a little easier than the one before. Where all of this should live so it actually gets found is covered in Business systems: how the knowledge in your head becomes something your team can use.

New employees and AI employees on the same team

If AI employees already work in your business, that's part of onboarding. The new person should know which processes an AI employee handles, which report it sends after every run and what to do when a case lands with them through the escalation path.

Sometimes the new person becomes the contact person for an AI employee. Then they approve, handle the unclear cases and teach it new variants. In our approach, every AI employee has a contact person like this on the team. It's a role of its own that has to be handed over just like a process. How to divide up tasks and decisions clearly is covered in Delegating tasks without them coming back to you as questions.

What this looks like for us

We onboard every AI employee the way described above. First, the job description is fixed: role, task, rights and limits, plus a contact person on the team. Then comes the trial task. First we watch the team at work, then we train the AI employee, each variant once with someone next to it. It's only signed off after several clean runs and a period in which the team monitors side by side.

At a tax advisory firm, this is how it went for filing digital tax assessment notices: Kevin watched the office team to see which types of assessment there are and how each one gets filed. Then the AI employee was trained, one type of assessment at a time. It was signed off after four clean runs, followed by a period of side-by-side monitoring. At that firm, it was 2 weeks from the first observation to sign-off; that's a value from this one case, not a target. Since then, filing runs on its own, at Autonomy Level 2, Autopilot, as of September 2026.

In Kevin's own business, each of his 14 AI employees has a personnel file, a fixed role and clear limits. At its core, the personnel file is what a new person would need for onboarding: what the role is, what it may do and what it never does.

We don't yet have our own documented experience with onboarding new people in client businesses that we could show here. The method is the same.

Frequently asked questions

How long does new employee onboarding take?

There's no reliable number that holds for every business. It depends on how many processes the person takes over, how many variants they have and how much of it is written down. The more is in process profiles beforehand, the less the timeline depends on your time.

Who should handle onboarding?

Ideally a fixed buddy from the team who runs the processes themselves. The owner doesn't have to answer every question. The owner makes sure the answers are written down.

What goes on an employee onboarding checklist?

Preparation before day one, introducing the team and roles, the person's own processes with process profiles, the escalation path and, for each process, the sign-off. A template is above in this article.

Can I onboard new employees and AI employees the same way?

The method is the same: job description, watching, sitting next to them, sign-off. The difference is in the content. A person also gets to know the team and often takes on tasks that need judgment. An AI employee gets the routine work that simply has to get done.

Read more

What exactly an AI employee is and how it differs from a tool is explained by Kevin in What Is an AI Employee?

Your next step

When every onboarding crosses your desk, what's usually missing is the written-down workflows. On the call, we look at whether Owner Autonomy is a fit for your business and which process is worth starting with. That's also where we go over how it works and what it costs.