Multi-site operators hire every week. Whether a new starter becomes useful on their fifth shift or their twentieth is decided almost entirely at site level, by one manager, on a busy day. Head office rarely sees the difference until it shows up in the rota or in the leaver figures.
This guide is written for anyone running the same onboarding across many addresses: franchise networks, retail chains, distribution centres, production sites, facility teams. The structure below is deliberately the same everywhere; what changes per site is only the schedule.
Five parts, run in parallel rather than in sequence
Onboarding that works has five components: welcome and company context, role-specific operational instruction, safety and compliance, application on shift with a named coach, and structured feedback across the first ninety days.
The operators who do this well run those in parallel, not one after the other. The welcome happens on day one. Role instruction starts in week one. Safety and compliance run across the first two weeks, front-loaded on whatever the person will touch first. The coach is assigned from shift one, not from week three.
The weak point is almost always component two. Role-specific instruction is usually the SOP binder plus a site manager who walks the new hire through it on the floor while also running the shift. That produces three problems at once: the content varies by whoever was on duty, the quality depends entirely on how busy that hour was, and head office has no idea what was actually covered.
Sequence follows the work, not the filing cabinet
Order the first two weeks the way the job unfolds: company and welcome, then the core tasks of the role, then the adjacent tasks they will be asked to cover, then the safety and compliance layer attached to each, then independent shifts.
A new starter who gets the compliance module before any context loses the reason for it, and a rule without a reason is the first thing to go when the site gets busy. Compliance content lands better when it is attached to the task it protects: the lifting instruction with the stocking task, the hygiene rule with the prep station, the equipment instruction on the day they first use the equipment.
For a multi-site operator the sequence has to be defined once, centrally, so every site executes the same order and head office can see where each starter is inside it.
In Belgium the buddy is a legal appointment
Most onboarding guides describe a buddy system as good practice. In Belgium it is not optional, and the wording is worth quoting because it settles arguments.
Codex art. I.2-15 obliges the employer to organise the onthaal (structured reception and introduction) of every worker and to entrust it to a member of the hierarchical line. Codex art. I.2-11, second paragraph, 9° goes further: the employer must organise the onthaal of every starting worker and designate an experienced worker charged with guiding them. The designated member of the hierarchical line then signs a document under his own name showing that the necessary information and instructions on welzijn op het werk were provided.
That is three hard elements, not one: every starting worker, a designated ervaren werknemer as peter or meter, and a signed document per person. The buddy system stops being a nice cultural practice and becomes an assignment with a name attached to it, and the file that proves the onthaal happened is a per-person document, not a group attendance sheet.
Two practical consequences. If your site rota is built without a named experienced colleague on the starter's first shifts, you cannot deliver the onthaal as described. And if the signed document is generated after the fact, at the end of the week, it says something different from what it is supposed to say.
What Dutch law does not ask for, and still expects
Be honest about the difference across the border, because the honesty is what makes the rest credible.
Arbowet art. 8 lid 1 requires the employer to inform workers effectively about the work to be done and its risks, and lid 2 requires instruction adapted to their distinct tasks. Art. 8 lid 4 requires the employer to supervise compliance with those instructions.
What the Arbowet does not do is prescribe a form of proof. There is no Dutch signature requirement for an induction, and anyone who tells you there is has invented it. But the practical position is unchanged: without a record you cannot demonstrate art. 8, and supervision under lid 4 of something you never registered is an assertion. So the Belgian rule tells you what the document must look like, and the Dutch situation leaves the format to you while still making the absence of one a problem.
Design one onboarding record that satisfies both: per person, per topic, dated, with the name of whoever delivered it.
Days 1 to 30, 31 to 60, 61 to 90
Days 1 to 30 establish the operational baseline: the tasks the person performs unsupervised, the safety instruction tied to those tasks, and enough context to understand why the standard is the standard. The goal of this block is the first independent shift, not a full curriculum.
Days 31 to 60 deepen the role. This is where the exceptions live: the shift that goes wrong, the delivery that arrives short, the customer or the machine that does not behave. Scenario-based content earns its keep here, because the baseline is already in place to hang it on.
Days 61 to 90 shift towards coaching and adjacent skills: the tasks that make someone useful across the roster rather than at one station. This is also where the first honest retention conversation belongs, while there is still time for it to change something.
That cadence holds regardless of sector. What varies is the length of the first block, which is set by how much of the job is safety-critical.
The four numbers to review weekly
Completion by location. Completion by role. Time to first independent shift. Ninety-day retention.
The first two tell you where onboarding is being skipped and which role has content that does not fit the shift. The third is the operational number, because it converts onboarding quality into rota capacity, which is the language a site manager already speaks. The fourth is the one that pays for the programme: sites with a long time to first independent shift and low ninety-day retention are usually the same sites, and the causality is not mysterious.
Review them weekly, per site, and resist adding a fifth.
How the first two weeks run in Aristotl
Build the programme once, from documents you already have. The handbook, the site rules, the role SOPs and the onthaal checklist go in and come back as one onboarding path in short modules with knowledge checks. Edit the welcome module in your own voice, approve it, and it is the version every site uses.
Assign it when the person is added, not when someone remembers. When a member is added to a site or role, the courses assigned to that site or role are assigned automatically and the welcome goes out. Set the deadline against the first shift rather than a calendar date.
Deliver it on the phone they already carry. Mobile-first in the browser, no app install, three to five minute modules, progress carried across shifts. Content is translated per worker, which matters on a floor where the starter and the peter do not share a first language.
Verify before the first solo shift. The site manager sees each starter's progress and knowledge-check results on their own dashboard, and incomplete starters are visible before they are scheduled alone. Head office sees the rollup across all sites, and the record exports per person, per topic, with dates: the file the onthaal document belongs in.
Start with the next person who starts
Take one role at one site and the documents you already use to induct for it. In a demo we turn that into the first two weeks of an onboarding path and show you what the record looks like on the morning of the first independent shift.