Who is this assistant for?

You know money leaks in an area but not where. When something fails, nobody knows whose it was. Everything is done «the usual way» and nothing is recorded. A key person leaves and the area collapses.

An area is not put in order by writing down what people do: it is put in order by drawing where the thing travels —the ingredient, the plate, the cash, the data— and placing a control at every point where it can be lost. This assistant builds the area you choose by the journey and not by the hierarchy: what comes in, what is done, what leaves, who signs each stage, what record proves it, and how much is lost per month when a control point drifts out of tolerance. And it asks the question almost nobody asks out loud: which two things in this area is nobody signing today. It is not one person's shift —that is the operating manual by role—: it is the area's system, which stays when people rotate.

AI assistant · N5 Complete system

◆ Included in the annual plan📘 Manuals, SOPs and Documentationv1.3.0 · 2026-09-23

📷 Works best with an AI that sees photos (invoices, dishes, screens) · optional

Operating Manual Architect by Area for Restaurants

Pick the area above, WHICH manual you want and the size of your operation: the processes, the house culture, internal communication, the staff house rules, performance reviews, shift scheduling, the emergency and evacuation plan, brand standards or opening a new location. With processes you get the area's system: the route map with who signs each stage, six to twelve processes with the record that proves them, where money leaks with its tolerance in figures, and the fifteen-check internal audit. With culture you get the purpose, the values and the observable behaviour for each, with its ritual and its date.

Depth

14/24

Your data

Compatible AIs

Steps to use it

Depth of the resulttap a level to see what you get

◀ Put out today's fireRun the year ▶

🏛️

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 level

Is this for you?

What it does and what you get

An area is not put in order by writing down what people do: it is put in order by drawing where the thing travels —the ingredient, the plate, the cash, the data— and placing a control at every point where it can be lost.
This assistant builds the area you choose by the journey and not by the hierarchy: what comes in, what is done, what leaves, who signs each stage, what record proves it, and how much is lost per month when a control point drifts out of tolerance.
And it asks the question almost nobody asks out loud: which two things in this area is nobody signing today.
It is not one person's shift —that is the operating manual by role—: it is the area's system, which stays when people rotate.

What you end up with

The chosen area's system: the journey map in numbered stages with the signing role and typical time; six to twelve processes with trigger, output and the record that proves them, with where it lives and how long it is kept; three to five control points with standard, tolerance, who measures, how often and what is lost per month when it drifts; the boundary table with what does not belong to the area and the gaps nobody signs; the fifteen-check internal audit with its evidence and percentage cut-off; the update rule; and the first three things to fix, with owner and date.

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

Sazón de OrigenFictional contemporary Colombian restaurant in Medellín, 2 locations, 6 years in business. Every sample result in the library comes from this same case. Fictional house

The owner asked this: «I want every plate to come out the same at both locations and to bring kitchen food cost down from 34 % to 32 % without touching menu prices. I need the kitchen manual: who signs each step, what gets measured and where our money is going.»

What the kitchen handles is the ingredient, from the supplier to the plate. The clock is set against the window that rules: lunch from Tuesday to Friday, 12:00 to 14:30, and Sunday midday. The map has ten stages; these are six:

Stage	What leaves	Signing role	Typical time
1. Scheduling and ordering (16:00 the day before)	Production plan and purchase need (FOR-COC-01)	Head chef	20 min
2. Receiving (07:00 to 10:00)	Goods accepted and labelled, or rejected (FOR-COC-02)	Production cook	10 min per delivery
4. Base production (08:00 to 11:00)	Stocks, sancocho, beans, rice and sauces, labelled	Production cook	180 min
6. Service and the pass (12:00 to 14:30)	Plate portioned at the pass	Head chef at the pass	8 min the starter, 15 min the main (proposal)
8. Cooling (from 14:30)	Product at 5 °C or less, labelled, or discarded (FOR-COC-03)	Production cook	6 h at most
10. Cleaning and close	Clean kitchen, gas shut, cold checked (CHK-COC-03)	Head chef	45 min

The slowest dish sets the start. The Sancocho de tres carnes takes 60 minutes of prep and 90 of cooking. That is why base production starts at 08:00: the stock is ready at 10:30, with half an hour of margin before the mise en place deadline, 11:00.

The kitchen buys 72,760,000 COP a month in ingredients (34 % of 214,000,000 COP in sales). Each point of waste on that cost is 727,600 COP a month. Each food-cost point on sales, 2,140,000 COP a month.

Point	Standard	Tolerance	Who measures	Lost per month
1. Receiving	Chilled at 4 °C or less; weight against invoice	2 % by weight	Production cook, every delivery	654,840 COP for each undetected 2 % shortfall (illustrative)
2. Portioning	Protein at 180 g	± 10 g	Head chef, 5 plates per service	802,500 COP for each extra 10 g (illustrative)
3. Waste	Under 3 % of the week's ingredient cost	3 %	Head chef, on Mondays	727,600 COP for each point above
5. Cooling (CCP)	From 60 °C to 21 °C in 2 h and to 5 °C in 4 h more	None	Production cook, every batch	360,000 COP per discarded 40-litre batch of base stock (illustrative)

Point 4, the peak starter in 8 minutes, carries no figure. It is measured over one week: the system's ticket time against the exit time logged in FOR-COC-06. What is lost is the lunch table that does not come back.

What looks like the kitchen's	Who actually signs it	Reason
Buying and negotiating with the supplier	Storeroom and purchasing (Volume 5)	Whoever receives does not buy: splitting the two roles prevents the agreed shortfall
Delivery temperature at the customer's door	Delivery (Volume 3)	The kitchen hands over sealed and at temperature; the road belongs to whoever carries it
Repairing equipment	Maintenance (Volume 6)	The kitchen reports and does not dismantle: a badly repaired fridge is a lost CCP
Changing the menu or a dish's price	Management, with the recipe card	The kitchen proposes with the cost in hand; it does not set prices

The gaps nobody signs today (the finding):

The allergen matrix per dish. The dining room asks about the allergen and the kitchen complies, but the document does not exist. Proposal: the head chef writes it into each recipe card and the dining room uses it.
Moving preparations between locations, if it happens. Nobody signs the arrival temperature. Proposal: the receiving kitchen logs it in FOR-COC-02, like any delivery.

Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.

This is 3 of 5 parts. The full version holds three sections of the volume. The table of the kitchen's eleven processes, each with its trigger, its output, the record that proves it, where it lives and how long it is kept. The area's indicators with their source, target and baseline, and the internal audit of fifteen checks with their evidence and pass cut-off. And the rule that says which change forces the volume to be reopened and who approves it, with the first three things to fix, ordered by what they cost, with owner and date.

See the full example — free account

Works with these AIs

Claude — the best for this assistant The best fit here: it holds the line between a process and a step, and does not fill an orphan stage with an invented role. Demand the ownerless gap in the boundary table; if it found none, it did not look.

How to use it

Pick the area at the top. The assistant changes the journey, the processes and the control points, not just the label.

Fill in My Restaurant with peak windows, team size and your yardsticks: what is at stake at each control point comes from there.

Have at hand which roles work in that area today and with what system or notebook their work is recorded.

Copy the whole assistant and paste it into your AI of choice. Answer its questions one at a time.

Walk the map with whoever works the area and mark the stages that in reality happen in another order: that corrects the manual in an hour.

Run the internal audit in the first week, note the percentage and repeat it monthly with the same list.

Which of your data it uses

of 24

This assistant works with 14 of the 24 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.

Restaurant nameBusiness typeCuisine or conceptCity and countryNumber of locationsYears in businessTeam sizeStrong and slow daypartsActive sales channelsAverage check (with currency)Average monthly salesApproximate food cost (%)Approximate labor cost (%)Main goal this year

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-09-23Diego's instruction (2026-09-23): the documents every professional or chain restaurant needs and no prompt produced enter as options of THIS selector instead of new prompts —«it is easier for people to find and use them this way»—: staff house rules, performance reviews, shift scheduling, the emergency and evacuation plan, brand standards and opening a new location, each with its own contract. The summary names them so search finds them.

v1.2.02026-09-23Diego's instruction (2026-09-23): «review especially the operations manual, which tends to be a long and detailed document for each restaurant. Professional, deep and expert». The area volume stayed at six blocks and lacked what no franchise operations manual omits: the food safety plan with its critical points, the prerequisite programmes (cleaning and sanitising, pests, waste, calibration, maintenance) and contingencies. They enter as task 5 and blocks G and H, and the volume says where it sits in the house Operations Manual. The controlled-document anatomy —cover, control sheet, paginated contents, common volume, master list, guardians— travels in the professional document block.

v1.1.02026-08-27Diego's brief on document 41: «we already have a manual builder; check which of these topics are missing and put them in that one, do not make more». It absorbs FIFTEEN culture cards and two purchasing ones, and two axes are born with it: `tema_del_manual` -processes, culture or internal communication- and `tamano_del_negocio`. Without the first, the absorption would have been a pretence: the AREA axis cannot have a «culture» option, because culture is not an area of the restaurant. A culture manual is proven by a behaviour you can see on the shift, not by a signed record.

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 ten «Manual Architect for ___» cards in c26 —general, kitchen, service, bar, till, purchasing, inventory, HR, marketing, maintenance and quality—, which were the `area` axis written ten times, together with the manual auditor and updater, which here are two blocks and not two cards.