AI assistant · N5 Complete system
Kitchen Dashboard Builder for Restaurants
The PASS on one board: ticket times per dish against their standard, kitchen returns with fixed reasons, 86'd items and overproduction against plan, and sampled portioning — in a cocina.html that adjusts the production sheet daily.
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
- Kitchens get managed by ear: the owner knows the pass jams on Saturdays and that something comes back, but not which dish jams it, which reason repeats or how much production was left over last night.
- This assistant builds the kitchen board in one file: ticket times per dish against their standard, returns with fixed reasons that accumulate, 86'd items with their hour and overproduction against plan, plus the week's sampled portioning.
- The ops board watches the whole shift and the cost board watches inventory in money; this board watches the pass and production — where quality and waste are born.
What you end up with
The kitchen indicator dictionary with formula, source, frequency and owner; the cocina.html file with the four blocks — the pass per dish, returns with reason, production vs plan, sampled portioning — and the 10-minute pass routine written into the file, with the next day's production sheet.
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: «On Saturdays my pass jams, this week four dishes came back to the stove and yesterday I threw out half a pot of beans. I want to see my kitchen in numbers.»
| Indicator | Formula | Data source | Frequency | Owner | Numeric target |
|---|---|---|---|---|---|
| Ticket time by dish (median) | min from order ticket to pass | POS + pass clock | Daily | Head chef | Platter ≤ 14 min |
| Ticket time by dish (peak) | worst 10% of service | POS | Daily | Head chef | ≤ 22 min |
| Returns with reason | returned ÷ served | Pass log | Daily | Head chef | ≤ 1% |
| 86s and leftovers | time of the 86 · % left over | Production plan | Daily | Manager | 0 86s before 21:00 |
| Sample grammage | real weight ÷ standard recipe | Pass scale | Weekly | Head chef | ±5% |
SUPUESTO: the Platter's 14 min standard does not come from an industry reference — none exists that fits this menu. The median of this kitchen's last 4 weeks is taken and set as a provisional ceiling. If measuring at peak hour showed a real median of 18 min, the standard rises and what changes is not the target but the bottleneck that has to be opened.
The pass this week: the Platter runs at a 13 min median and a 26 min peak. Saturday's jam IS the Platter — the star dish, as usual — and the bottleneck is the pork crackling cut to order at peak hour. Measurable change proposed: cut in short batches between 12:30 and 14:00 and read the peak again the following Saturday.
Returns with FIXED reasons (names do not change, or the frequency does not accumulate):
| Reason | This week | 4 weeks | Trend |
|---|---|---|---|
| Doneness of the protein | 3 | 9 | ▲ most frequent — THIS one gets fixed |
| Temperature | 1 | 4 | = |
| Presentation | 0 | 2 | ▼ |
| Order-ticket error | 0 | 3 | ▼ (already cross-linked to the operations board) |
Production against plan: sancocho 86'd at 20:15 on Tuesday and beans at 38% left over on Wednesday. Thursday's plan drops the beans to half a pot and raises the sancocho meat; what is left over goes out labelled into FIFO rotation. The plan recalculates on tomorrow's expected covers, with delivery counted separately because it consumes production at other hours.
The file opens from the desktop, with no connection and no libraries; the close-of-service cells are filled in under 5 min and where data is missing the cell says PENDING with its owner.
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 is **the pass routine template**: the 10 min at close, the single-correction rule with its owner and the figure that confirms it, the 5-point checklist for the sample grammage and the two cross-links written out to the operations and cost boards.
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 Best-selling dishes. 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 69.3 out of 90.0. `metodo` was at 3 of 6 and the only three numbered steps lived in the FORMAT: the TASK — where decisions are made — was a paragraph reading «One… Two… Three…», so the real method of the pass did not count; it is now six numbered steps injecting «platos_estrella», «momentos_fuertes», «nombre_restaurante», «food_cost» and «meta_principal» (required by arraigo). `verificacion` was at 2 of 5 because BEFORE YOU DELIVER was a string of questions with no checking verb: it is now five imperative checks, each on something that can genuinely go wrong. `cifras` at 3 of 12 and `lexico` at 5 of 10: the measurement windows are dated (5 min to load, a 10 min routine, 2 weeks, 4 weeks, 30 days) and the pass is stated in the trade terms that were missing — food cost variance, FIFO rotation, portioning, sales channel, covers, star dish. The SUPUESTO: line is added so the AI declares its own benchmark instead of the house hard-coding one. Rises to 95.0.v1.0.02026-08-15Initial version. Born in batch 8 of the artifact titles, the sixth c19 area board, with the full lead-magnet kit and a Sazón de Origen example. Its written boundary: the ops board watches the shift and the cost board the inventory money; this one watches the pass and production — where quality and waste are born.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 systemPurchasing on one board: key-item prices against their history, supplier compliance measured at the scale, pur…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
