The brand is executed by people you do not employ
A franchise network is one standard and many employers. Head office writes the manual, negotiates the suppliers and owns the name above the door. The person who actually applies the standard at 07:30 on a Tuesday is on somebody else's payroll, hired by an operator who runs two units in Limburg or five across Wallonia. You carry the reputation for what happens on that floor without carrying the employment relationship that would normally let you instruct it.
That gap is where most franchise training systems fail. Not because operators are unwilling, but because the tooling assumes an employer talking to employees, and a franchise is neither.
What a manual update actually has to survive
A revision to the opening routine, the allergen procedure, the complaint script or the build spec starts as a document in a brand portal. Between there and the counter it has to pass through an operator who may or may not open the portal that week, a site manager who has a shift to run, and a team that changed by a third since the last update. Every step in that chain is a place the revision quietly stops.
The usual instruments do not close it. A portal shows that an account downloaded a PDF, not that the crew works differently. Field visits reach a handful of units and are a snapshot by design. A brand audit tells you about last quarter. A newsletter moves information and proves nothing. None of that is negligence: it is a network being managed with tools built for a single employer.
The Benelux version of the problem
Three things make this harder here than the generic version. Units are small and close together, so a customer who has a poor experience in Gent compares it with the one in Antwerpen the same week. Teams are multilingual: the standard is written in Dutch or French and executed by people who read Polish, Romanian, Arabic or English. And the frontline is part-time and seasonal, so the population that received your last rollout is not the population that will execute the next one.
Add the regulatory layer that applies regardless of who signs the contract. In Belgium the onthaal of a new worker is the employing operator's duty under the Codex, with a signed document per person. In the Netherlands the Arbowet puts the instruction duty on whoever the worker is made available to. The franchisor is not the employer in either case, but a network where nobody can show what was instructed is a network exposed on both reputation and evidence.
What good looks like
A working franchise training layer has four properties. The standard exists once, so there is one current version rather than a version per operator. It reaches the floor on the phone the worker already carries, because a frontline crew has no laptop and no corporate email address. It arrives in the language the worker actually reads. And head office can see, per unit, whether it landed, without asking an operator to fill in a status sheet.
The last property is the one that changes conversations. A franchisor enforces through the agreement, not through a manager. That conversation is a different one when the gap is visible and specific rather than anecdotal.
How Aristotl handles it
Aristotl takes the documents your network already maintains, the operations manual, the opening and closing routines, the build spec, the safety steps, the service protocol and the complaint procedure, and converts them into short mobile courses of a few minutes each with a knowledge check. Nothing goes live without your review, and content is translated per worker, so the same rule reaches the whole crew in the language each person reads.
Assignment follows the structure you already run: by site, by region, by role. One procedure update goes to company-owned units, franchised units and a territory in the same action. Completion comes back per site, so head office, the field team and a master franchisee each see what landed and what is still outstanding. HQ keeps the standard while a local manager works within their own scope, which is the balance a franchise agreement is written around in the first place.
Bring your operations manual to a demo
Pick the last revision you sent out to the network: a menu change, a new opening checklist, a revised complaint script. In a demo we build it into courses for your units and show you the completion view per site the next morning.