AI assistant · N5 Complete system
Operational Checklist Builder for Restaurants
Pick the area above, the moment in the shift and how often it runs, and the assistant writes THAT checklist: the list that gets ticked with a pen at close, with its owner per line, the standard that defines «done», and what happens when something is not met. One builder for twelve areas and three periods instead of one card per combination.
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 117 of the 170 published assistants are at this levelIs this for you?
What it does and what you get
- The manager ends the day exhausted and unable to say what he decided.
- This assistant separates his job from what the station already signs: it does not check fridges or portion weights, it checks the people who check, and it forces every NO on somebody else's sheet to carry an action closed inside 24 hours.
- The day's numbers always arrive with their comparison, because sales without the same weekday last week beside them send nobody to do anything.
- And the day does not close with a summary: it closes with three decisions that have an owner and a date.
What you end up with
Five chained blocks: the day's header with its target, the cross-check table of other people's checklists, the numbers table against the same weekday last week, the people table with today's conversations, and the three signed decisions with their boundary matrix.
EXAMPLE This is what you getAn example built with Sazón de Origen, one of the house's fictional businesses.Not your data: your result is built with YOUR restaurant's.See the full example →Sample result
The owner asked this: "I have two locations in Medellín and 24 people. My managers end up stuck on the grill at the lunch peak, and at the end of the day nobody knows what was decided. I need the site manager's daily sheet for one day of operation."
Daily site manager checklist · CHK-DIR-01 · the sheet printed every morning is FOR-DIR-13. It applies to the manager of each of the two Medellín locations, Tuesday to Sunday, during the 09:45 to 17:15 working day. It does not measure temperatures, grams or banknotes: it checks the people who measure them, reads the numbers against the target and closes the day with three decisions.
| Phase | Hour | What you do | What does NOT belong here |
|---|---|---|---|
| Before service | 09:45 to 11:15; hands counted at 11:15 | Read the closing handover before 10:00, yesterday's and today's checklists; run the 11:00 meeting | Taking temperatures or counting the till float |
| During the peak | 12:00 to 14:30 (Sunday, until 15:00) | Watch from the door and the pass: lost tables, 86s, platform wait, complaints, comps | The grill, the pass, the till and the phone |
| After the peak | 14:30 to 15:00 | Partial sales, covers, check, cancellations and voids, while memory is fresh | Waiting for close to write it down |
| Close of your day | 16:30 to 17:15 | Three decisions and tomorrow's script; hand the house to the afternoon lead | The night: the closing lead signs it |
The manager works 42 of the 86 hours the location is open. The 21:45 close is not theirs: it is read the next morning, which is why the sheet closes at 17:15 and not at night. Whoever operates stops directing: every hour on the grill is four decisions nobody made.
The manager does not repeat the measurement. They read the checklists other people sign and check that every NO carries an action. Someone else's NO without an action closed within 24 hours is a missed shift duty, not an observation.
| Checklist | Who signs | When it arrives | What the manager looks at |
|---|---|---|---|
| CHK-COC-02 · kitchen opening | Prep cook from 06:45; the head chef verifies at 10:30 | 10:45 | ▲ on NO with action; real signing time |
| CHK-COC-01 · daily kitchen | Head chef and afternoon lead | Yesterday's, at 10:45 | Food safety NO with the dish held |
| CHK-SAL-01 · daily service | Floor manager; the close, the closing lead | Yesterday's, read before 10:00 | NO with action; lost tables logged |
| CHK-CAJ-01 · daily till | Morning and afternoon cashiers | Yesterday's, at 10:00 | Difference of each till count in % and double signature |
| FOR-COC-12 · allergen dockets | Head chef at the pass | Yesterday's, before 11:00 | Rows against the system report |
The boundary. Temperatures, protein portion weight (180 g ± 10 g) and banknote counting are signed at the station, by the head chef and the cashier. Whoever measures signs: if the manager measures again, the kitchen stops measuring and waits for them. And a signature without facts reassures more than an empty box; the manager's job is to ask for the action, not the signature.
A figure without a comparison does not go in. Every number is read against the same day last week, 7 days back, and the deviation is written in COP and in %.
| Indicator | Read against | Target | What a deviation means |
|---|---|---|---|
| Average check | 48,000 COP and 7 days back | 48,000 COP or more | Below it: nobody is suggesting |
| Sold-out dishes (86) with the hour | 7 days back | None before 14:00 | Production was planned on habit, not on sales |
| Turned-away or lost tables | 7 days back | 1 or fewer per peak | 48,000 COP of sales and 31,680 of contribution each |
| Voided dockets and comps | The caps in Volume 4 | Voids up to 0.5 % and comps up to 1 % of sales; 0 without a code | The theft the till count does not see |
What is worth watching instead of operating. The five levers add up to 5,819,320 COP a month, 45.3 % of the 12,840,000 COP target. The first two cannot be seen from the grill: the suggested drink on the floor, 2,162,160 COP a month (illustrative), and one lost table per peak and location, 1,330,560 COP a month. The two managers cost 8,988,000 COP a month, 4.2 % of sales: the sheet has to move more than that. This month, attention goes to the door and to order-taking at the peak.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 3 of 5 parts. Behind the wall are the pieces that get carried out. The complete FOR-DIR-13 day sheet, ready to print: the items of the five blocks with their hour, the ▲ items with the escalation rule, the Yes, No and N/A boxes with the measured value, and the reading of the total as day directed, day with a plan or day not directed. The example's three decisions with owner, date and the figure that closes them at 14 days. The minute-by-minute script of the 11:00 standing meeting. And annex A, FOR-DIR-14, the log of deviations and decisions stapled to the sheet.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 11 of the 24 fields in «My Restaurant», among them Restaurant name, Business type 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.3.02026-08-27The title drops «Daily». Diego's brief: «these names must not carry monthly, because the time selector is what sets the period». And its own gate now catches it: `motor/titulo_vs_control.py` fails when a card is named after a value its chip changes IN PLACE — the owner picked «weekly» and walked away with a deliverable titled «daily». With the period axis inside, the name can only state what does not change: that this is the house's operational checklist. The URL is untouched: it stays alive and the registry keeps the old name as an alias.v1.0.12026-08-26The body stops contradicting the answer ladder. It used to say «do not move on until it arrives», the very order the ladder was born to replace: the assistant asked the owner for what the owner does not have and stalled. It now says what the house doctrine says — ask one at a time, and if they do not know, continue with a marked assumption. FORMAT OF THE RESULT was not touched, so the example still corresponds and its seal moves up with the card.v1.0.02026-08-25The assistant is born.v1.3.12026-09-21The deliverable stops being an analysis in blocks and becomes a printable OPERATING DOCUMENT: one checklist_diario.html with the print button inside, sixteen sections and THE DAY SHEET, blank and landscape. The three layers of the family arrive: the day written as a PROCEDURE with measurable standards and out-of-standard cases, the ECONOMICS OF THE DAY with the arithmetic beside every figure, and the five governance pieces.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
Builds the checklist your restaurant opens with: the walk through the venue in blocks, every box with its meas…
N4 · Executable planWrites your restaurant's closing checklist in five named phases —product, money, premises, station and shift h…
N4 · Executable planWrites the daily method for your restaurant's money in four named phases —desk opening, control during service…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
