· Codemax · 6 min read
Same dish, every branch: fixing consistency across outlets
Dishes rarely drift because of one bad cook. Six places where variation enters, what a standard recipe card needs, and how to measure consistency across outlets.
TL;DR
Multi-outlet consistency means serving the same dish, to the same weight, look and temperature, at every branch within defined tolerances. Drift enters through six sources: specification, ingredients, method, equipment, people and holding time. Control each with a versioned standard recipe card, approved ingredients, visual SOPs, calibrated equipment and holding rules, then measure portion weights, plating photos, temperatures, complaint tags and mystery visits.
- Most drift is built into the system before a cook touches the food.
- Define tolerances: consistency is measured against a specification, not a chef's memory.
- A standard recipe card needs a version, weights, equipment settings, a plating photo and holding time.
- Check recipe version, ingredients, equipment and holding times before retraining staff.
- Tag complaints by dish and cause so patterns by outlet become visible.
Multi-outlet consistency comes from controlling the six places where variation enters a dish (the specification, the ingredients, the method, the equipment, the people and the holding time) and from measuring the plate, not just publishing the recipe. Most drift between branches is built into the system before a cook touches the food. Fix the source, then measure weight, look, temperature and complaints the same way at every outlet.
The question came up plainly at the media launch of TT360 (Taste & Trade 360) on 3 October, ahead of the show at KLCC on 5–7 November. Ethan Choong, CEO of Ping Edge Technology Bhd, the show’s main sponsor, put the operator’s problem in three sentences: “I can’t find people. My costs keep going up. How do I keep my food the same across five outlets?” Brian Ding of Gene Tech pointed to inconsistent food quality, training challenges and food waste, as reported by the New Straits Times and DagangNews. This post takes the third of Choong’s questions.
What is multi-outlet consistency?
Multi-outlet consistency is the ability to serve the same dish, to the same weight, taste, temperature and appearance, at every branch and on every shift, within tolerances defined in advance. The tolerance matters. Food is never identical; a consistent chain decides how much variation is acceptable (say, a protein portion of 120g, plus or minus 5g) and measures against that, rather than against a chef’s memory of how it should taste.
That moves quality control in F&B from opinion to evidence. “It tasted off at outlet seven” is hard to act on. “Portion weights at outlet seven ran under spec on the evening shift” is not.
Where does drift enter?
Inconsistency is usually blamed on people. In practice, people are often the last link in a chain of smaller causes. The table lists six sources, what each looks like on the floor, and the control that addresses it.
| Drift source | What it looks like | Control |
|---|---|---|
| Specification | Outlets working from different recipe versions; “a handful” or “to taste” where a weight should be | One governed recipe per dish, versioned and dated, pushed to every outlet at once |
| Ingredient | Different brand or grade at different outlets; local substitutions when stock runs out | Approved ingredient specifications with named alternatives; substitutions recorded, not improvised |
| Method | Steps in a different order; shortcuts at peak hour | Step-by-step SOP with photos or short videos at the station; critical steps flagged |
| Equipment | An older fryer or oven running hotter or cooler; different scoop and ladle sizes between branches | Standard equipment list, calibrated thermometers, portioning tools issued centrally |
| People | New staff learning from whoever is on shift; each senior cook’s version becomes the local standard | Training against the card, sign-off before working a station alone, regular refreshers |
| Holding time | Fries, rice or sauces served long after they were cooked | Maximum holding times and temperatures on the card; timers and discard rules |
Two rows are easy to miss. Equipment drift looks exactly like a people problem: a fryer that runs cool produces limp fries whoever is on station. And holding time explains why one outlet can serve a perfect dish at 12.15pm and a tired one at 2.30pm from identical prep.
Anatomy of a standard recipe card
A standard recipe card is the specification every other control depends on. A recipe in a chef’s notebook or a WhatsApp photo is a suggestion. A useful card has ten parts:
- Name, version and effective date. Everyone can see which version they are using, and old copies can be retired.
- Yield and portion. How many portions a batch makes, and the portion weight with its tolerance.
- Ingredients by weight, with specification. Grams, not cups; the brand or grade; approved alternatives named.
- Sub-recipes referenced, not rewritten. The card says “house chilli sauce, 30g” and points to that recipe, so a change to the sauce reaches every dish that uses it.
- Equipment and settings. Which pan, fryer or oven, at what temperature, for how long.
- Method, step by step. In order, with critical steps flagged: the ones that change taste, texture or safety if skipped.
- Build and plating. Assembly order and a reference photo of the finished plate.
- Holding and service. Maximum holding time and temperature, and when to discard.
- Allergens. Declared on the card, so front-of-house gives the same answer at every branch.
- Theoretical cost. Cost per portion at current prices, so drift has a ringgit value.
A kitchen SOP sits alongside the card. The card says what the dish is; the SOP says how the station runs: set-up, cleaning, hand-washing, glove changes. Both need to be usable at the station, which in practice means pictures and video rather than paragraphs. Our piece on recipe management and costing covers the costing side in more depth.
How do you measure food consistency across a restaurant chain?
Consistency you don’t measure is consistency you assume. Five measures, used together, give a fair picture:
- Portion weights. Weigh a sample each shift, such as three portions of each of your top five dishes, and log them against tolerance.
- Plating photos. A photo of a finished plate at set times, compared with the reference on the card. Cheap, quick and hard to argue with.
- Temperatures. Core temperatures at cooking and holding temperatures during service, by item. They speak to safety as much as quality.
- Complaint tags. Tag every complaint by dish and cause (cold, small, salty, slow, wrong) instead of filing it under “food quality”. Patterns by outlet appear within weeks.
- Mystery visits. Scored against the card for weight, look, temperature and time, not against the visitor’s taste.
Behind these sits one system-level signal: actual ingredient usage against what the recipes say should have been used. If an outlet keeps using more rice per plate than the card allows, portions are drifting even if nobody has complained. Portion control is where that gap usually shows first.
Fix the system before retraining the people
When an outlet drifts, the instinct is to retrain staff. Work down the table first. Does the outlet have the current recipe version, the approved ingredients and calibrated equipment? Do holding times survive the lunch peak? Only then look at method and people.
The order matters when turnover is high. If specification and equipment are right, training means teaching one clear standard rather than correcting a dozen local versions, which is also what makes onboarding in a high-turnover kitchen workable.
Where RMS and VisionAI fit
Codemax RMS (Resource Management System) handles the specification. Recipes, sub-recipes, yields and multi-level BOMs, with approved ingredient alternatives, are governed centrally and pushed to every outlet without version drift, so no branch cooks from last month’s card. Image and video SOPs give staff step-by-step instructions on mobile at the station. Actual consumption is measured against theoretical usage outlet by outlet, so a drifting portion shows up as a variance on a named item at a named outlet.
Codemax VisionAI adds a view of the line itself, using the CCTV cameras a business already has. Its checks include portion consistency, and SOP and PPE compliance such as masks, gloves and hairnets, reported by shift and by station. A detection can become a task for the right person, and each outlet has a compliance dashboard. Models are calibrated to each site’s lighting, layout and policies before go-live, and VisionAI is anonymous by default, with no face recognition. It gives supervisors evidence by station and shift; it doesn’t replace them, and it works best rolled out as coaching, not surveillance.
Questions worth asking this week
- Can every outlet tell you the version of the recipe card for your best-selling dish?
- When an outlet runs out of an ingredient, what happens, and is it recorded?
- Who checks fryer and oven temperatures, and when were thermometers last calibrated?
- What is the maximum holding time for your top five items, and is it written at the station?
- Could you list last month’s complaints by dish, cause and outlet?
Where two outlets give different answers, you have found where the next inconsistency will come from.
Frequently asked questions
How do restaurant chains keep food consistent across outlets?
Restaurant chains keep food consistent across outlets by controlling where variation enters: one versioned recipe per dish, approved ingredients, step-by-step SOPs at each station, standard calibrated equipment and maximum holding times. They then measure the result with portion weights, plating photos, temperature logs, tagged complaints and mystery visits, and compare actual ingredient usage with what the recipes say should have been used.
What should a standard recipe card include?
A standard recipe card should include the dish name, version and effective date, yield and portion weight with a tolerance, ingredients by weight with specifications and approved alternatives, referenced sub-recipes, equipment settings, a step-by-step method with critical steps flagged, a plating photo, holding time and temperature, allergens and the theoretical cost per portion.
What is the difference between a standard recipe and a kitchen SOP?
A standard recipe defines a dish: its ingredients, quantities, method, plating and holding rules. A kitchen SOP defines how a station or task is run: set-up, cleaning, hand-washing, glove changes, opening and closing. Consistent multi-outlet kitchens need both, kept short and visual enough for staff to use at the station during service.
How do you measure food consistency in a restaurant?
Food consistency in a restaurant is measured by sampling portion weights each shift against the recipe's tolerance, comparing plating photos with a reference image, logging cooking and holding temperatures, tagging customer complaints by dish and cause, and scoring mystery visits against the recipe card. Comparing actual ingredient usage with theoretical usage shows drift even before customers notice it.
Why does the same dish taste different at different branches?
The same dish tastes different at different branches usually because of differences built into the operation: an older recipe version, a substitute ingredient, equipment running hotter or cooler, a shortcut in the method, or food held too long before service. Staff training matters, but checking specification, ingredients, equipment and holding time first usually finds the cause faster.
One recipe, one standard, every branch.
See how Codemax RMS governs recipes and SOPs centrally, and how Codemax VisionAI checks portions and SOPs by station and shift.
Sources
- Kitchen robots set to reshape F&B operations — New Straits Times, 4 Oct 2026
- TT360 2026 ketengahkan robot dapur ketika sektor F&B Malaysia berdepan kekurangan pekerja, kenaikan kos — DagangNews, 4 Oct 2026
Related reading
- Kitchen robots by 2028? What AI can already do in your kitchen today Cooking robots will draw the crowds at TT360 next month. Most of the AI a Malaysian kitchen can use today doesn't cook at all. It runs on the cameras and records you already have.
- What the Lenggong food poisoning case means for central kitchens The cause hasn't been established, so this isn't about blame. It's about why bulk catering is different, the control at each stage, and the records to have ready if the health office calls.
- Going to TT360? Questions to ask any kitchen tech vendor Three days, 260 booths and a lot of demos. How to walk into TT360 2026 with your problems defined, ask every vendor the same questions, and leave with a shortlist you can defend.