AI assistant · N5 Complete system
Role Manual Builder for Restaurants
You pick the role and the assistant hands you its full manual in a printable .html file: twenty-one sections —from what the post moves in money, with the arithmetic in plain sight, to the authority matrix with cash caps and the signable training milestones, safety, escalation and the shift annexes— with a control cover, acknowledgement of receipt and a self-audit. Twenty-one loose documents in a single one that prints with the button it carries inside.
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
- In most restaurants roles live in the owner's head and on no paper, and that is paid for three times: at hiring, because nobody knows what is being looked for; on shift, because two people each think the same task belongs to the other; and in the hard conversation, because there is nothing to measure anyone against.
- This assistant writes the manual for the role you choose, with the layer almost nobody writes — authority, with cash caps — and duties that carry a clock, so they can be demanded.
- It is not an org chart nor an employment contract: it is the document that makes two different people in that seat perform alike, and turns a performance conversation into something other than an opinion.
What you end up with
The manual_de_cargo.html file, printable on A4 with its print button inside and with the twenty-one sections of the standard: control cover with code, version and next review; purpose with its absence line; the place in the organisation with the neighbouring roles; eight to fourteen duties with a clock; the typical day of the shift; the authority matrix with a cash cap and a reason on every line; THE ECONOMICS OF THE ROLE —what the section bills, what each target is worth and which lever is worth most, with the arithmetic written beside every figure and every input stating whether it is measured or proposed—; the indicators with baseline and owner; the boundaries table; the profile as observable behaviour; the 1·7·30·90 training plan with proof and signature per milestone; safety with the reason for each rule; the escalation routes; the appraisal rubric with the 4 and the 2 in writing; the career path with measurable thresholds; the five interview questions; the opening and closing checklists to hang; the open items; change control; the acknowledgement of receipt; and the self-audit, computed on generation.
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 24 people across two locations and I am finally going to name a head chef in Laureles. The guy has been with me three years and cooks well, but every time something has to be decided — an emergency purchase, dumping a product, sending someone home — he calls me. I need the role manual before I name him.»
Role: Head chef · Location: Laureles · Direct manager: you (owner) · Leads: 4 line cooks and 1 kitchen assistant · Shift: split, 10:00–15:30 and 18:00–22:00
Purpose, in one sentence: hold the line so that the plate leaving at 13:20 on a full Friday is the same one that left at 12:05, at the same cost and the same portion weight.
If nobody fills this seat tomorrow, Sazón de Origen stops doing this: nobody decides what gets bought in an emergency when an ingredient runs out at 11:00, nobody signs off that the day's waste had a cause, and food cost stops having a responsible person with a name — it becomes a number that shows up at month end and that everyone explains away.
That second line is the test of the role. If writing it changed nothing concrete, the seat would be redundant or tangled with the executive chef's.
Eleven duties. The three starred are the ones that, if dropped, show up in same-day sales.
| Duty | Frequency | Weight in the 12:00–14:30 peak | Critical |
|---|---|---|---|
| \* Opens the line and checks mise en place against the covers forecast | Daily, 10:00 | High | Yes |
| \* Controls the pass and returns any plate off standard | Every service | High | Yes |
| \* Decides the emergency purchase when a menu ingredient runs out | As it happens | High | Yes |
| Signs off the day's waste with its written cause | Daily, at close | Medium | No |
| Reconciles protein inventory | Weekly, Monday | Low | No |
| Updates recipe cards when a supplier or a price changes | Monthly | Low | No |
| Schedules next week's kitchen shifts | Weekly, Thursday | Medium | No |
| Trains the new cook against the recipe card, not against memory | On each hire | Medium | No |
| Places supplier orders | Twice weekly | Medium | No |
| Checks and logs cold room temperatures | Daily, open and close | Low | No |
| Reports weekly food cost with its variance to the owner | Weekly, Monday | Medium | No |
None says «support». Each has verb, object and clock — without a clock it cannot be demanded, and what cannot be demanded is not in the role.
This is the layer that solves the problem you described: the phone calls.
| Decides alone (with cap) | Consults then decides | Does not decide |
|---|---|---|
| Emergency purchase up to 180,000 COP per event and 600,000 COP per week | Changing a category supplier | A dish's selling price |
| Dumping spoiled product, no cap | Pulling a dish off the menu for more than 2 days | Hiring and firing |
| Refiring a plate for a guest, up to 2 plates per service | Hiring a temp for an event | Guest discounts at table |
| Sending a cook home for low volume, up to 1 per shift | Changing a recipe card's portion weight | Equipment purchases |
| Reordering the shift within the published week | Approving overtime beyond 4 weekly hours | Pay conditions |
The caps were calculated like this: 180,000 COP is roughly 4.6 % of an average day's sales (3,900,000 COP) — enough to save lunch without one judgement error eating the day's margin. Illustrative figures: set them against your real sales.
The left column has five lines. If it had zero, you would not have written a role: you would have written a pair of hands that phone you.
The `manual_de_cargo.html` closes by measuring itself against its own standard, and the figure is computed on generation — never written by hand:
| What the standard demands | Expected | This document | Verdict |
|---|---|---|---|
| No duty without a frequency | all | 11 of 11 with a clock | ✔ meets |
| No duty says «support» | 0 | 0 | ✔ meets |
| «Decides alone» with cap and reason | ≥ 3 with a cap | 4 lines, 0 without a cap, 0 without a reason | ✔ meets |
| Every target with a baseline, or the absence declared | declared | 2 of 4 with a measured baseline; the rest say «not measured» | ✔ meets |
| Proposed figures labelled | all | 5 labelled | ✔ meets |
A document that says «meets» without a number is an opinion. And the file opens without internet, prints on A4 with the button it carries inside, and every section starts on its own sheet with the code and version at the foot — because sheets get photocopied on their own.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 4 of 6 parts. Behind the wall are the **remaining thirteen sections** of the file, the ones that turn the manual into a management tool: **the economics of the role** —what the section bills in one service and in a year, what each target is worth and which lever is worth most, with the arithmetic written beside every figure—, the four indicators with their baseline and their owner, the profile translated into observable behaviour, the boundaries table with the three neighbouring roles, **the 1·7·30·90 training plan with proof and signature at every milestone**, safety with the reason for each rule, the escalation routes, the appraisal rubric with the 4 and the 2 in writing, the career path with its two measurable thresholds, the five interview questions, the opening and closing checklists to hang, the open items and the acknowledgement of receipt that gets signed.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 14 of the 23 fields in «My Restaurant», among them Restaurant name, Business type and Cuisine or concept. 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.0.12026-08-27The response-ladder doctrine is stated in English with the house phrase —«continue with a marked assumption»— and not with a synonym. The migration probe caught it: 34 migrated bodies in Spanish and 27 in English, and the seven-card gap were the ones I wrote today. A doctrine said two ways stops being greppable.v1.0.02026-08-27Born by merging the twenty-one role cards in c21 — description, duties, responsibilities, authority, KPIs, targets, routines, competencies, experience, relationships and career plans — which were not twenty-one tools but the chapters of one manual. The role is picked with the selector.v1.1.02026-09-21The deliverable stops being a text and becomes a printable OPERATING DOCUMENT: a single manual_de_cargo.html with the print button inside, twenty sections and the five governance pieces a franchise never omits —identity with code and version, owners with signature, change control, acknowledgement of receipt and self-audit. Eight sections that did not exist before come in: place in the organisation, typical day of the shift, signable 1·7·30·90 training, safety and hygiene with the reason for each rule, escalation routes, appraisal rubric, printable shift annexes and open items. And the four gaps found by reviewing two real outputs are closed: a target now runs against its BASELINE (and one without it says «not measured» rather than being padded), a declared yardstick outside the trade range is questioned before targets are set on it, a role that does not reach three «decides alone» lines says so instead of padding the column, and the three neighbouring roles become a minimum input because without them the boundaries table is guesswork. The format numbered with letters and the example with circles: both now number 1 to 20. · SAME-DAY AUDIT: measured on the first version, 84 % of the ficha data appeared but eight of those only once, in the cover table — and ZERO derived figures, ZERO figures showing their arithmetic. Section 7, THE ECONOMICS OF THE ROLE, turns the ficha into money and shows the arithmetic of every result, with each input labelled measured / proposed / computed; plus the `comprobar_consultoria.py` probe.v1.1.12026-09-21The duel against the baseline caught what the body rewrite had degraded: turning the BEFORE YOU DELIVER block from checks into counts dropped the verification signal from 6 to 3 and the card from 91.7 to 87.7, under the 90 threshold. A count with no floor is not a check. Every point gets its verb back and keeps its count. And the trade yardsticks get their working ranges, which the body demanded and never supplied.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.
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
