AI assistant · N5 Complete system
Pre-Shift Meeting Builder for Restaurants
The timed script for the ten minutes before service —the pre-shift—, in six timed blocks: yesterday's number, today's target, what is 86'd, the single push of the day with its selling line, the section split and the reminder that cost money yesterday. With the two-minute prep sheet and the kitchen and floor variants.
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
- The pre-shift meeting is the highest-return-per-minute routine a restaurant has, and also the first one to die: it starts at ten minutes, stretches to twenty, turns into a telling-off, and within three weeks nobody calls it.
- This assistant writes it as a piece of operation and not as a motivational moment: six timed blocks, each with its figure or a first name, a single push of the day with the literal line it is sold with, and a prep sheet that whoever runs it fills in two minutes from data they already have.
- The menu-state block justifies the whole meeting on its own, because it is the one that prevents the ticket the kitchen cannot fill.
- It teaches nothing: it aligns.
What you end up with
The meeting clock as a table, with the six blocks, their minutes, who speaks and which figure each one brings; the literal script to be read aloud, with the figure blanks marked; the two-minute prep sheet in five boxes with each figure's source; the push of the day with its template and three examples with a selling line under fifteen words and its business reason; the two variants —kitchen and floor— with what changes in each; the four closing questions; the record and how it links to the shift handover; and the fifteen-day test with two indicators and their cut-off.
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: «We do a pre-shift when I remember, and when I do it runs twenty minutes talking about attitude. We are 9 on the floor and 6 in the kitchen, and the Tuesday-to-Friday lunch is what pays the payroll. I want the script so my captain can read it without me.»
11:35, standing, by the pass. Not 11:00 —set-up is half done— and not 11:55, by which time nothing can be fixed.
| # | Block | Seconds | Who speaks | Which figure |
|---|---|---|---|---|
| 1 | Yesterday's number | 90 | Captain | Sales, covers, check and % against last Tuesday |
| 2 | Today's target | 60 | Captain | Target lunch covers |
| 3 | State of the menu | 180 | Head chef | 86'd, those under 10 portions, new items |
| 4 | The push of the day | 90 | Captain | The literal line and its reason |
| 5 | The split | 120 | Captain | Sections, expected covers per channel, who is missing |
| 6 | The one reminder | 60 | Whoever runs it | What cost money yesterday |
Total: 600 seconds. Block 3 is the longest on purpose: it is the only one that prevents the ticket the kitchen cannot fill, and that is the one that pays for the meeting.
① Yesterday's number — «Yesterday we did ____ on ____ covers, check of ____. Against last Tuesday we are ____ %.»
② Today's target — «Today we go for ____ covers. That is ____ more tables than yesterday between the three of us.»
③ State of the menu (kitchen speaks) — «____ is 86'd. There are fewer than ten portions of ____ left, tell me before you sell it. ____ is new: ____ grams, out in ____ minutes. If they ask for the 86'd one, the authorised swap is ____, no price difference.»
④ Today's push — «Today we push ____. It is said like this: «____». It is on because ____.»
⑤ The split — «____ takes the main room, ____ the terrace, ____ the bar. When the peak lands, ____ backs up ____. ____ is missing today, ____ covers.»
⑥ One single thing — «Yesterday ____. Not today.»
Close — «What is not clear?» — and wait. Really wait, three seconds of awkward silence, because whoever does not ask walks into the shift with the doubt.
It is written to be read aloud and not read on screen. Scripts read off a screen sound like memos.
The five boxes the captain fills at 11:33, before calling the team:
| Box | Where it comes from |
|---|---|
| Yesterday's sales and covers | Yesterday's till close, first line |
| % against the same weekday | Same sheet, previous week's column |
| 86'd and running low | Called out by the head chef at 11:30 |
| Push of the day | The rule below — it is not improvised |
| Who is missing | The shift's WhatsApp group |
The push of the day: one, and with its literal line. Three examples from your menu:
| Dish | Selling line (< 15 words) | Business reason |
|---|---|---|
| House platter | «The platter comes with the blood sausage we make here. Nobody else has it.» | Contribution margin 9 points above average |
| Sancocho | «There is sancocho today and it is Tuesday: it is not back until Saturday.» | Real scarcity, rotates the day's pot |
| House dessert | «The dessert is made by Doña Rosa every morning. Twelve left.» | Lifts the check ~12 % with no kitchen work |
Two pushes are zero pushes. If the captain names two, the team pushes neither.
Six cut-out cards, one per star dish. Whoever runs the meeting takes the first unmarked card, reads the line exactly as written and returns it with the date on it. The push rotates instead of being whatever the boss likes best.
| # | Dish | The line, literal | Business reason | Margin | Used on |
|---|---|---|---|---|---|
| 01 | Osso buco cappelletti | «The cappelletti are filled this morning.» | Fresh pasta: what does not sell in two days is thrown out | 68 % | ____ |
| 02 | Burrata with focaccia | «The burrata came in yesterday, eight left.» | Shared starter: it does not compete with the main | 74 % | ____ |
| 03 | House malbec | «We pour the house malbec by the glass.» | Highest margin, and it takes no kitchen time at peak | 81 % | ____ |
No line runs past 15 words, and all six pass the house's human-writing contract before they are printed: it is the only part of this document a guest will hear.
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 two pieces that make the meeting survive its third month. The two variants: the kitchen script, where menu state and ticket times take half the time and the split barely exists, and the floor script, where the section split and the push rule, with what changes block by block and who speaks in each. And the close with its follow-up: the exact four questions it ends with —one per person if the team is small— and the rule for what happens to whatever surfaces there; the pre-shift record, where it lives and how it links to the closing handover so the morning's news is not lost by night; and the fifteen-day test, with its two indicators measured against their baseline —the push sold on at least 15 % of tables and zero tickets for an 86'd dish across the whole week—, its cut-off and the dated verdict box: works, or it is already a ritual and the script needs reviewing. And the file: one reunion_preturno.html with the print button inside, the 16 sections each on its own sheet, the cut-out deck and the step-by-step procedure for running the meeting, with a measurable standard, so it does not depend on who runs it that night.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 16 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 at Diego's request (2026-08-27): «check whether we have a tool for creating daily pre-shift meetings». Measured: nothing was published and the card had been sitting in the pipeline from the start. It is written as a piece of operation —six timed blocks, one single push, a two-minute prep sheet— and not as a motivational moment, which is how these meetings die.v1.1.02026-09-21The deliverable stops being a 6-block text plan and becomes a printable OPERATING DOCUMENT: one reunion_preturno.html with the print button inside, 16 sections and THE CUT-OUT DECK OF PUSH CARDS —one per dish, with its line, its margin and the «used on ___» box—, which is what makes the push rotate instead of being whatever the boss likes best. The procedure for running the meeting arrives too, with a measurable standard, so it does not depend on who runs it that night. The clock is now stated in SECONDS: 600, split 90/60/180/90/120/60, because the menu status takes three times the target block for a reason. And the deck lines go through the house's human-writing contract: the selling line is the only part of this document a guest hears.Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.
