/Aristotl
Language
Demo

Training a crew before a new site opens

Updated

Short answer

Train a crew before a new site opens by separating what is the same everywhere from what belongs to that building. Send the reusable pack four weeks out, before anyone has walked the floor, add the site-specific layer two weeks out once the layout is real, and spend the last week checking readiness, not delivering training.

A brand-new shop in the week before opening: half-unpacked boxes and empty shelves, two new crew members completing a lesson on their phones while a manager walks the floor with a clipboard.
Nobody on an opening crew can ask the colleague who has been there four years. That colleague does not exist yet.

A new site differs from every other operational project in one way: the date does not move. The lease starts, the customer has been promised, the equipment is installed. Whatever is not ready on opening day opens anyway.

This guide covers all of them, not just shops: a new distribution centre, a new line in an existing hall, a branch acquired with its people in it, a relocated depot, a new store. The commercial detail differs; the training problem is the same.

A countdown to opening day at eight, four, two and one weeks: split the reusable content from the site-specific, send the standard pack to the new crew, write the site layer, verify in the last week, then keep the same system for the second wave.
Most of an opening's training is the same at every site and can go out four weeks early. Only the site layer waits for the building.

The site exists on paper long before it exists

For months the new site is a floor plan, an equipment list and a set of procedures copied from the site it most resembles. Everything written about how it will run is a prediction. Then the racking goes in two metres from where it was drawn, the goods-in door is on the wrong side for the yard, and the line runs at a different speed from the identical one in the other plant. The procedures the crew was going to learn describe a building that does not quite exist, which is why induction material built in month one is wrong by opening week, and why the site manager rewrites it in the evenings during the fortnight he has least time.

Everyone is new at once

At an ordinary site a starter joins a working system: people who have done the job for years, an obvious person to ask, a rhythm to copy. At an opening none of that exists. Nobody can ask the colleague who has been there four years, because that colleague does not exist. Everything normally picked up by watching has to be delivered on purpose: opening and closing, cash or stock handling, deliveries, escalation, the local safety instructions for that building.

An acquired branch inverts the problem without solving it. Those people know the work; they do not know your procedures, systems or standards, and they carry habits from a previous owner that nobody wrote down.

The law makes the volume visible. In Belgium every new worker is owed a structured onthaal, with an experienced colleague designated to guide them and a document signed by a member of the line; in the Netherlands the Arbowet requires effective instruction on the work and its risks (see the instruction law guide). At a normal site that is one or two records a month. At an opening it is dozens in one week, produced by a manager who is also commissioning equipment. Something gives, and it is the paperwork rather than the equipment.

The people who know how it runs are somewhere else

The knowledge you need sits with people working at the sites that already run well. You can send two of them for a fortnight, which is expensive and leaves a hole behind, or send a trainer who explains it once to whoever is present. Either way the transfer is verbal and disappears when those people leave. The second wave of hires, four weeks after opening, gets a diluted version from someone who heard it once. Write it down once, in a form every opening can reuse.

The countdown, and what belongs in each part

WhenWhat happensWhy then
About 8 weeks outSplit what is genuinely site-specific from what is not: company standards, product knowledge, safety or hygiene basics and system instruction are the same everywhereThe reusable part is built once and serves every opening after this one
About 4 weeks outThe crew exists on paper: the reusable pack goes to them, before there is a building to walk them roundIt lands ahead of the start dates, when the onthaal duty begins
About 2 weeks outThe site-specific layer becomes writable: actual layout, actual equipment, actual local rulesA short addition to the standard pack, not a new pack
Last weekVerification, not delivery: who is short, in which team, on whatIf someone is still learning the basics now, the opening is already soft
After openingThe second wave of hires gets exactly what the first wave gotNot a summary from someone who heard it once

The crew arrives with the general layer done, so the days on site go to what genuinely needs the building: walking the fire routes, running the equipment, practising the opening sequence at the real counter or the real dock.

Retail openings: one moment in a longer calendar

For a store chain an opening is one of six recurring change moments, next to range changes, promo weeks, seasonal hiring, till changes and recalls (the retail change calendar covers the rest). It is the only one where a whole team starts without institutional memory, which is why an opening-readiness checklist for the store belongs next to the training: the till works, the safe is set, the first delivery has a named receiver, the escalation numbers are on the wall.

Running an opening in Aristotl

An opening, step by step

  • Set the new site up as its own location, so its completion picture reads on its own rather than inside the network total.
  • Put managers, shift leads and frontline crew in their own teams at that site, each with its own set from the pack built once and reused for every opening. Nothing is rebuilt.
  • Send each new starter the site's link or QR code, so they join on their own phone without a company email and finish the general layer before they walk in: short modules, translated per person, with knowledge checks.
  • Add the site-specific modules once the site is real, built from the documents the site manager writes anyway: layout, equipment, local rules.
  • Check readiness before opening day, not on it: completion per team and version for that location shows who is short while there is time to fix it.
  • Keep the same system after opening, so the second wave in week five gets exactly what the first wave got.

Nothing reaches the new crew until you review and publish it, and the opening checklist for the building can run on the phone next to the training, with a photo, signature or choice where it counts.

Bring the next site in your pipeline and the induction pack you used for the last one. We will show what the countdown looks like, and what the readiness view looks like on the morning of opening day.

Sources

  1. Codex over het welzijn op het werk, art. I.2-11 and I.2-15 (onthaal) and I.2-21 (training on entry into service)
  2. Arbeidsomstandighedenwet, artikel 8

Frequently asked questions

Around eight weeks out, sort the content into what is the same at every site and what belongs to this building. The reusable pack can go to the new crew about four weeks out. The site-specific layer follows two weeks out, once the real layout and equipment are known. The last week is for checking readiness.

The people already know the work but not your procedures, systems or standards, and they carry habits from a previous owner that nobody wrote down. Give them the same reusable pack as a new crew, then spend the site-specific effort on the places where your way differs from theirs.

The same as for one starter, multiplied: every new worker gets a structured onthaal, with an experienced colleague designated to guide them and a document signed by a member of the line. At an opening that means dozens of records inside one week, which is why they need a plan, not a spare evening.

Read next

Ready when you are

Raise the standard at every location.

See how Aristotl fits into your operations stack in a 30-minute call.