AI assistant · N5 Complete system
Multi-Location Dashboard Builder for Restaurants
Every location on one screen: the same formulas for all (or the comparison lies), the per-location standings table, the gap turned into transferred practice and the escalation rule — in a multisede.html read every Monday.
N5Complete system
Several chained pieces you install and operate over time, with their review cadence. It changes how the business runs, not one decision.
◆ This assistant 110 of the 164 published assistants are at this levelIs this for you?
What it does and what you get
- Multi-location owners live off reports that can't be compared: each manager measures their own way, the «good» location is good because nobody audits it the same, and best practice dies where it was born.
- This assistant builds your multi-location board in one file: the SAME formulas for every location, the standings table with traffic lights — sales, margin, service —, the gap between the best and the rest turned into practice transferred with a name and a date, and the escalation rule: which figure rises to the owner on its own, without waiting for a meeting.
- The executive board summarizes one operation; the location analyzer audits the money once; THIS one compares them all, every week, under the same rules.
What you end up with
The common dictionary with a single formula per indicator, source, frequency and per-location owner; the multisede.html file with the standings table, the per-location traffic lights, the gap in money and the practice in transfer — and the Monday managers' routine written into the file, with the owner-escalation rule.
EXAMPLE This is what you getAn example built with Sazón de Origen, the house's fictional restaurant.Not your data: your result is built with YOUR restaurant's.See the full example →Sample result
The owner asked this: «I have three locations and three managers reporting however they like. Downtown “does well”, North “so-so” and nobody knows about the new one. I want them on one screen.»
| Indicator | SINGLE formula | Source | Frequency | Owner | Target |
|---|---|---|---|---|---|
| Sales per cover | weekly sales / covers served | POS | weekly | location manager | ≥ the mean of the 3 |
| Operating margin | (sales − prime cost) / sales | POS + payroll | weekly | location manager | ≥ 27% |
| Food cost | cost of ingredients consumed / sales | inventory + purchasing | weekly | location manager | the one declared by the house |
| Team turnover | 12-month exits / average headcount | payroll | monthly | owner | falling, 2 quarters running |
Today's verdict: the three locations calculate margin differently —North leaves kitchen payroll out of prime cost— so the current table compares nothing. SUPUESTO: no «industry» food cost ceiling is hard-coded; the one declared by Sazón de Origen is used and, if the real figure changes, the ranking is recalculated and said out loud in the meeting.
| Location | Sales/cover | Margin | Service | Light |
|---|---|---|---|---|
| Downtown | 118,000 | 31% | 4.6 | Green |
| North | 96,000 | 24% | 4.4 | Yellow |
| New (3 months) | 74,000 | 18% | 4.7 | On ramp: against ITS plan, not against Downtown |
The honest reading: Downtown's corner explains much of its sales per cover —that is market, not merit—. The 7 margin points over North are management: Downtown produces in batches and North does not, and North also carries a sales mix leaning on high-commission delivery. The gap in money: if North closed half that distance, it is 2.3 million more per month.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 2 of 3 parts. Behind the wall are **the tested multisede.html file** and **the Monday routine**: the managers' 25 min, the single transfer with its accompaniment and confirming figure, and the escalation rule with its thresholds as figures.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 9 of the 23 fields in «My Restaurant», among them Restaurant name, Cuisine or concept and Number of locations. It does not ask out of curiosity: these are what make the answer speak about YOUR scale instead of an industry average — the same calculation on a business of another size returns a number you cannot decide with. You fill them once and they apply across the library, so the second assistant you open already starts with them in place. Whatever you leave blank, the assistant asks for one thing at a time instead of inventing it, and says so before answering, so you know what it is working from.
Always up to date
Every assistant carries a visible version and date. When an AI changes how it works, the assistant's version goes up and you see what changed.
v1.1.02026-08-25Body rewritten to pay down duelo debt: it scored 66.1 out of 90.0. The `lexico` signal sat at 1 out of 10 —a board that compares locations named «prime cost» and nothing else— and the common dictionary now says what gets compared: sales per cover, average ticket, food cost, labor cost, contribution margin, occupancy, team turnover and the weight of delivery inside the sales mix per channel. `cifras` sat at 3 because windows and thresholds were spelled out in words; the routine's 25 min, the 10 min of per-location loading and the deadlines are now figures. `verificacion` sat at 2 and BEFORE YOU DELIVER was a row of questions: it is now five imperative checks on things that genuinely go wrong. And the TASK came as running prose («One… Two… Three…»), so `metodo` counted 3 of 6 on a method that was already good: it is now six numbered steps, with seven of the restaurant's «fields» entering the working sections, which is what arraigo requires since its cutoff —the nine fields were declared under YOUR RESTAURANT and none appeared again—. A SUPUESTO line is added so the AI declares its own reference ceiling instead of the house hard-coding one. Rises to 94.2.v1.0.02026-08-15Initial version. Born in batch 10 of the artifact titles, the tenth c19 area board — it closes the board series. With the full lead-magnet kit and a three-location Sazón de Origen example. Its golden rule: one single formula per indicator across locations — comparison under different rules is politics, not measurement.Same method, another variant
Inside the app this is a single control: you press it and the assistant reframes itself, including the variants that don't appear here because they don't have their own page yet.
More assistants in this category
Pick the area above and whether you watch one location or the network, and the assistant builds THAT board: th…
N5 · Complete systemThe «sábana» —Latin American kitchen slang for the wide sheet where everything fits at once— is the master mea…
N5 · Complete systemThe PASS on one board: ticket times per dish against their standard, kitchen returns with fixed reasons, 86'd …
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.