Standardizing recipes, checklists and training across restaurant locations

This is part 2 of 7 in our series Running a multi-location restaurant group. Earlier: what changes for the owner.

A regular who buys an oat latte at your first store and then tries the second one across town expects the same drink. If it's sweeter, smaller or served in a different cup, they don't think "a different store". They think "they've gone downhill".

At one store, consistency is mostly about people: the right specs, measured, and checked. We covered that in making coffee and food consistent. With two or more stores, you need three more things: one master copy of every standard, a way to change it that reaches every store at once, and checks that compare the stores with each other.

One master copy of everything

Copies drift. A recipe card gets a handwritten note at one store, a checklist gets a task crossed out at the other, and six months later you have two menus with the same names. The fix is a single master copy of every standard, with one person who owns it.

Standard	Master copy	Owner	What each store has
Recipes and specs, with weights and photos	One shared folder	Owner or head chef	The current version at each station
Opening, closing and food safety checklists	One template	Owner or operations lead	The checklist, created from the template every day
The allergen matrix	One file (allergen matrix template)	Whoever owns the recipes	A copy at the counter and the pass
Station training and sign-offs	One sign-off sheet per station	Owner or lead trainer	Each person's signed sheet
Service standards	One page (service standards)	Owner	The same page, trained the same way
Cash count and over/short limits	One count sheet	Owner	The same sheet, every close

Three rules make the library work:

Every page has a version date. "Oat latte, version of March 4" settles any argument about which card is right.
No local edits. A store that needs something different asks for it, and the difference is written into the master as an approved local note ("North uses the 12 oz cup for small, because the 8 oz doesn't fit its lids").
Old copies are thrown away the day a new version arrives. Two versions at one station is worse than one wrong version.

Recipes: the same spec, the same tools, the same ingredients

A recipe spec is only as good as the conditions it's made in. Across stores, three things break it:

Different equipment. A different grinder, oven or scoop changes the result even with the same spec. Buy the same equipment for anything that touches a spec, or write the store-specific settings into the master (a dial-in target per store, for example).
Different ingredients. If one store switches milk brands because the usual vendor was short, the drink changes. The main ingredients are a group decision, not a local one. Part 6 of this series covers ordering across stores.
Different measures. "A handful of greens" means something different to every cook. Grams, portion tools and a photo of the finished plate travel between stores; handfuls don't.

Allergens follow the recipe. A local substitution that adds an allergen has to change the allergen matrix at that store, on the same day. That's the strongest argument for keeping ingredients the same everywhere.

Changing a standard across stores

Standards should improve. The risk is that one store improves them and the other doesn't hear about it. Use one route for every change:

Anyone can suggest it. The people closest to the work often see the problem first.
The owner of the standard decides.
Test it at one store for a week or two.
Update the master with a new version date.
Train every store before the go-live date, with a short tasting or demo.
Go live on the same day everywhere, and remove the old copies.
Check the first week at each store.

For a menu change, our menu change rollout checklist has the full list, including the POS, signage and the allergen check.

Checklists: one template, every store

The same job gets the same checklist. An opening checklist for the espresso bar should be the same at every store with an espresso bar. Write store-specific tasks (the second store's patio, for example) as extra tasks that run only there.
The same proof everywhere. If the first store photographs the cleaned grinder, the second store does too.
Compare completion across stores every week. A store that's always at 80% has a staffing or training problem, not a checklist problem.

Our guide to checklists staff actually follow covers writing tasks two people do the same way.

Training that travels with the person

Train new hires where the standards are strongest. One way is to train every new hire at one store, or with one trainer, before they start at their own store. Whichever store or trainer you choose, every new hire should learn the same standard.

Certify your trainers. Each store needs at least one person who is signed off on teaching each station, not just on doing it. A trainer who learned the job "the way we do it here" passes on the local habits along with the standard.

Sign-offs belong to the person, not the store. A barista signed off on espresso at one store can cover espresso at another after a short check on that store's equipment. Keep one training matrix for the whole group, with a column for each station and a row for each person, and you can see at a glance who can cover where.

Check consistency across stores

Order the same three items at every visit, and compare each with its spec and photo. Write down what matched and what didn't.
Swap audits. Once a month, the manager of one store walks the other with the same checklist. Fresh eyes spot what the home team has stopped seeing, and each manager brings ideas back.
Ask why before you fix. When two stores differ, either one store isn't following the standard (fix the training) or the standard doesn't work there (fix the standard, or approve a written local note).

Where Mays fits

One checklist template for every store. In a template's Assignments tab, 1. Where does this run? takes every location that should get it. Assigned to a role or department, each store gets its own shared checklist on every day it runs, created for that store's own date. Managers see a template that runs at several locations as read-only and can Duplicate it for their own stores. See Scheduling and assigning checklists.
One library for the specs. A Knowledge Base folder can be shared with Everyone in org, A location, A role or A specific person, with Can view or Can edit. Someone who works at two stores sees what's shared with either. See Sharing and visibility.
The same training everywhere. A Learning module is assigned to Branches, Roles, Departments or People, and works like a rule: people who join later get it too. Only admins assign modules, and nobody is notified when one is assigned, so tell the team. See Assigning training.
Certificates follow the person. Training certificates and food safety certificates belong to the team member, not to a store.
Recipe costs per store. Inventory → Recipes costs each recipe with that store's own vendor prices. A recipe made on the web belongs to one location; recipes shared by every location come from an import. A recipe can't hold its method or photo yet, so keep the written spec in the Knowledge Base.

Your standards checklist

One master copy of each standard, with an owner and a version date
Local differences written into the master, not onto the station copy
The same equipment and main ingredients wherever a spec depends on them
One route for every change, live on the same day at every store
The same checklist and the same proof for the same job
Certified trainers at each store, and one training matrix for the group
The same three items checked at every visit, and a monthly swap audit

Make every store taste like the first one

Run one checklist at every store, share the specs from one library, and assign the same training everywhere.

Start your free trial: 30 days, every module, no card needed. Or book a walkthrough and we'll set up your shared checklists with you.