Three kinds of chicken burger
The burger brand's chicken burger has lettuce, mayo and pickles. The chicken brand's version has slaw and hot sauce. The limited-time brand's version has cheese and a special sauce in a different bun. On the grill, at speed, with a new starter on a Saturday, they all start to look the same. A customer who ordered the hot one gets the mild one, and the brand's rating takes the hit.
The head chef wrote specs for each brand when it launched. They are in a ring binder, and in some cases on a laminated sheet stuck to the wall, which is now out of date because the sauce changed in spring. Weekend staff rely on whoever is next to them.
Why dish consistency slips across brands
Virtual brands are deliberately built from the same ingredients, which means the differences between dishes are small and easy to forget: a sauce, a garnish, a portion size. In a single-brand restaurant, chefs learn one menu well. In a dark kitchen they need to know several menus that overlap, and staff turnover means someone is always learning.
Specs on paper cannot keep up with changes. When a sauce changes, the binder is updated, maybe. The laminated sheet is not. And no chef checks a binder mid-service. The spec needs to be where the chef is already looking, which is the ticket.
Portion sizes drift in the same way. A handful of cheese more on one brand's fries and less on another's does not look like much on one plate, but it changes food cost and it changes what the customer expects the next time they order from that brand.
When builds drift
| Drift | Effect |
|---|---|
| Wrong sauce or garnish for the brand | Complaints and lower brand ratings |
| Portion sizes varying by chef | Food cost creeping up, or customers short-changed |
| Old specs still in use | Dishes that no longer match the menu description |
| New starters guessing | Slower service while they ask |
| Allergen-relevant differences missed | Risk to customers your own procedures are meant to prevent |
Your own allergen and food safety procedures decide what must happen in the kitchen. What we fix is making sure the right, current spec for each brand's dish is in front of the chef who is building it.
Specs attached to the ticket
- Each menu item on each brand gets a build spec: photo of the finished dish, components in assembly order, portion sizes, sauce and garnish, and any notes your procedures require.
- Specs are linked to the kitchen products behind them, so shared components are described once and the brand differences stand out.
- When a ticket appears on a kitchen screen, each item can be tapped to show its spec, or new starters can have specs showing by default.
- The differences between similar items on different brands are highlighted, such as this is the hot version, slaw not lettuce.
- When the head chef changes a spec, it is updated everywhere at once, with a note on screen for the next few shifts so everyone sees the change.
- Specs can be printed as a pack for training or kept as a reference on a tablet.
The specs are written and approved by your head chef. We build the system that holds them and puts them in front of the right person at the right time.
A Saturday with specs on the screen
The new starter sees a ticket for the chicken brand's burger. The spec shows slaw and hot sauce, highlighted as different from the burger brand's version. They build it right the first time without asking. The head chef updated the special sauce last week, and every screen shows the new version.
- The current spec for each brand's dish on the ticket
- Differences between similar dishes made obvious
- Changes rolled out to every station at once
- New starters building dishes properly from their first shift
Is this happening on your line?
- Similar dishes on different brands get mixed up.
- Specs are in a binder or on the wall and not always current.
- Portion sizes vary from chef to chef.
- New starters learn by asking during service.
- A spec change takes weeks to reach everyone.