Build the menu.
Pressure-check the work.
Three dishes, one oven, two temperatures, and one of them wants the broiler. Menu Builder finds that collision on paper instead of at 6:42 with people in the next room.
A menu is not complete merely because every dish fits.
The work has to fit too. Appetite, the guest who is not drinking, the one who cannot eat dairy, the burners, and whatever attention you have left in the final thirty minutes are all the same decision. The final thirty minutes is where menus actually fail.
- Planning mode
- Hands-on
- Checks
- Built in
- Output
- Print ready
- Status
- Available
The good idea survives. The wishful thinking does not.
A menu can be wrong for reasons that have nothing to do with taste — a shelf, a temperature, a hand you do not have at seven. Better to meet those now than during service.
One menu, not four good ideas
Dishes and drinks get built together. A loose collection of individually attractive possibilities is how you end up with three creamy things and nothing sharp.
Use it in the application → 02Where the oven runs out
Every dish wants a burner, a shelf, or a pair of hands. The tool counts all three, and it counts them before seven rather than at seven.
Use it in the application → 03Zero-proof planned first, not poured last
Not an afterthought for whoever is driving home. Same planning status as everything else, from the beginning.
Use it in the application → 04What actually carries over
Only the settled menu goes on to Occasion OS for quantities, sequence and recovery. The half-decisions stay here.
Use it in the application →Go straight to the working tool.
All Tools is the directory for the whole suite. Menu Builder runs inside Occasion OS, so launching from here drops you straight onto the planning surface.
Build first. Pressure-check second.
Put in the menu you are already thinking about. Occasion OS argues with it — whether it balances, what can be done a day early, what has to happen at the last second, and whether you end up at the table or at the stove.
What it checks
- Whether the menu balances, or is three soft beige things in a row
- What can be made the day before without dying overnight
- What genuinely has to happen in the last ten minutes
- Two dishes that want the oven at two different temperatures
- Whether you ever actually get to sit down
What it will not do: this is planning support. It does not guarantee allergen safety, and it does not give you recipes, pricing, or nutrition advice.
Carry the plan into Occasion OS.
The menu decision sits upstream of everything else. Occasion OS takes it from there — what to buy, what to do when, and what the kitchen looks like afterward.
A plan that hides its assumptions is not a plan.
- 01How many people, what kind of service, and the time you actually said
- 02Which equipment it assumed would be free, and when
- 03Quantities, units, and the places it is frankly guessing
- 04What to do when something slips, because something will
- 05What it looks like printed and taped to a cabinet door