/Aristotl
Language
Back to use cases

Use case

Opening a new site with a crew that is ready

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 page is about all of them, not just shops: a new distribution centre, a new production line in an existing hall, a branch acquired with its people already in it, a relocated depot, a new store. The commercial detail differs; the training problem is identical.

The site exists on paper long before it exists in reality

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 than the identical one in the other plant. The procedures the crew was going to be trained on describe a building that does not quite exist. That 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.

Most of the crew is new to the company, and some are new to the work

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. Everyone is new at once, so the informal learning that normally carries half the induction has nothing to run on.

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.

Belgium makes the consequence concrete. Codex art. I.2-15 requires the employer to organise the onthaal (structured reception and induction) of every worker and to entrust it to a member of the hierarchical line. Art. I.2-11, second paragraph, 9°, requires for every beginning worker that an experienced worker be designated to guide them, and that the designated member of line management sign a document under his own name showing the necessary information and instructions on welfare at work were given.

At a normal site that is one or two documents a month. At an opening it is dozens inside 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 should run are somewhere else

The knowledge you need sits with people currently 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 gone the moment those people leave. The second wave of hires, four weeks after opening, gets a diluted version from someone who heard it once.

The countdown, and what belongs in each part of it

Roughly eight weeks out, separate what is genuinely site-specific from what is not. Company standards, product knowledge, safety or hygiene basics and system instruction are the same here as everywhere else, and can be built once and reused for every opening after this one.

Four weeks out, the crew exists on paper. That is when the reusable pack goes to them, before there is a building to walk them round in, and it is ahead of the induction duty, which starts when each person enters service.

Two weeks out, the site-specific layer becomes writable: actual layout, actual equipment, actual local rules. A short addition to the standard pack, not a new pack.

The last week is verification, not delivery. If someone is still learning the basics then, the opening is already soft.

Running an opening in Aristotl, step by step

  1. Set the new site up as its own location. The site becomes a unit you can assign to and report on separately, so its completion picture is readable on its own rather than buried in the network total.

  2. Assign the standard opening pack by role. Managers, shift leads and frontline roles get different sets, from the pack built once and reused for every opening. Nothing is rebuilt.

  3. Let people finish it before they walk in. Short modules on their own phone, translated per person, with knowledge checks. The crew arrives with the general layer done, so the on-site days go to what genuinely needs the building.

  4. Add the site-specific modules once the site is real. Layout, equipment, local rules. Built from the documents the site manager writes anyway, rather than in addition to them.

  5. Check readiness before opening day, not on it. The dashboard shows completion by role and version for that location, so whoever is short is visible while there is time to fix it. The record exports for whoever asks later.

  6. Keep the same system after opening. The second wave of hires in week five gets exactly what the first wave got, not a summary of it.

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

Bring one procedure to a demo