Somewhere in your organisation a date is circled. On it a recipe changes, a machine goes live, a new range hits the shelf, a procedure is replaced, or a label requirement takes effect. On that date, each site is either doing the new thing correctly or it is not.
A change is not a gradual improvement each site can adopt at its own pace. It is a switch, thrown centrally, that has to be caught locally by people who were not in the room when it was decided.
Five changes that share one deadline
A new product or range: new handling, new customer questions, new claims that have to be right.
A changed recipe or specification: the item looks the same and behaves differently, the most dangerous form because nobody notices they need to relearn it.
A new machine or system: a different till, scanner, wrapper or piece of line equipment.
A revised procedure: cleaning, changeover, opening checks, handover, escalation, usually written after something went wrong.
A packaging or labelling change: a new declaration, format or rule about what appears where.
Different departments own them and different budgets pay for them, but from the floor they are indistinguishable. Someone doing X on Friday does Y on Monday, correctly, first time.
Ready is binary on the date
Most operational metrics tolerate an average. This one does not. If eighteen sites out of twenty-two are executing the new spec, you do not have most of a launch. You have four sites producing something that is not the product, in front of customers, with your name on it. There is no partial credit.
The failure mode is predictable. Site managers are genuinely told. What breaks is the last twenty metres: the manager passes it on at a handover to whoever is present, people on holiday and on nights get a shortened version, and the agency workers arriving on Tuesday get none of it. Nobody withheld anything; the message degraded on its way to the person who would act on it.
When the change is equipment or method, instruction is the legal position
For most changes this is an execution question. For some it is a duty.
Codex art. I.2-21 requires the employer to ensure every worker receives sufficient and appropriate training on welfare at work, aimed at the worker's own workpost or function, and it names the triggers: entry into service, a change of function, new work equipment, and new technology. Training is repeated and adapted to evolving risks, at the employer's cost, during working time. A new machine that arrives without renewed instruction is therefore not just a rollout that went badly. It is a gap against a named obligation, which makes it an exposure rather than an execution problem.
In the Netherlands, Arbowet art. 8 requires effective information and instruction adapted to each worker's tasks, and art. 8 lid 4 adds the duty to supervise compliance. Certified food sites carry the same logic: IFS Food version 8, clause 3.3.4 requires training content to be reviewed and updated with particular attention to, among other things, product and process changes.
The menu change, as one worked example
A menu change is the version most people have lived through, which is why it belongs here as an example rather than as the frame.
Two items change and one is new. The kitchen learns the build and the prep. The counter learns what it is, what it costs and what is in it. The allergen information changes, and under Regulation (EU) 1169/2011, art. 44(1)(a) that information has to be correct for non-prepacked food, given by whoever the customer asks. Every site goes live the same Wednesday.
The usual approach is a spec sheet emailed to managers and a briefing at Tuesday's shift start. It works where a strong manager runs a real briefing and degrades everywhere else, and you cannot tell which is which until a complaint arrives. Swap the nouns and it covers a new pick method in a DC, a changed cleaning validation in a plant, or a new till in retail.
Getting a dated change to every floor
-
Start from the document that already exists. The spec sheet, the revised work instruction, the machine manual extract, the label brief. Nothing is written specially: that document is the source.
-
Build a module about what changed. Not the whole procedure again: the delta, the reason for it, and the part people get wrong, in three to five minutes.
-
Assign by role, not by site. The counter, the kitchen, the line and the technicians need different things from the same change. Send everyone everything and nobody reads their part.
-
Track completion against the go-live date, and let people finish on their phone, in their own language, on shift, with a knowledge check on the point that matters: the allergen call, the setting, the sequence.
-
Watch the sites that are behind before the date, not after. The dashboard shows completion per site, role and version, so a manager can run five targeted minutes on the item their people scored worst on.
-
Keep the version in the record. When someone asks in six months who was instructed on the new equipment, the answer has to name a version, not a topic.
Bring the change you are shipping next and the document that describes it. We will build the module from it in the demo and show what the site view looks like the evening before go-live.