Run the sequence.
Protect the table.
Turn the approved menu into quantities, shopping, preparation, equipment, holding, drinks, service, and recovery for a real meal under real kitchen constraints.
The plan is only useful when it survives delay.
Occasion OS receives the approved menu and exposes quantities, dependencies, holding limits, service collisions, and the next corrective move without duplicating the menu intake.
- 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.
Scale quantities
Keep yield, portions, buffer, units, and uncertainty attached to the actual guest count.
Use it in the application → 02Sequence dependencies
Protect chilling, resting, reheating, plating, beverage, and arrival windows.
Use it in the application → 03Read the kitchen
Match the plan to equipment, surfaces, hands, holding, table flow, and cleanup capacity.
Use it in the application → 04Plan the save
Define cuts, substitutions, holds, and fallback service patterns before they are needed.
Use it in the application →Use the planning tool right here.
The tool does the work. Everything around it is here to say what the tool will not tell you, and where to go once it has given you an answer.
OCCASION OPERATING SYSTEM / THE ROUTE
Four dishes, three of them wanting the oven at 6:40, and one of you.
Choosing the menu is the fun part. What actually wrecks an evening is arithmetic — two temperatures and one oven, a sauce that needed both your hands at the precise moment the doorbell went. Occasion Operating System takes a finished menu, yours or a clean handoff out of Menu Builder, and turns it into the thing almost nobody bothers writing down: the route from an empty fridge to food on a table. Shop, prep, serve, in that order, on a timeline that assumes there is exactly one of you.
You give it the guest count, the service style, your capacity, and how much hosting attention you are honestly bringing rather than the amount you would bring in a better week. The route builds around what is true instead of what would be impressive. Got a mood and no menu? Start from the scene and come back once it has a shape.
Open Occasion OS on Salty Desk →
When the route is built, send it back. Look for Continue on saltnotes.blog in Architecture or Plan — it lands on the Reading Desk with the dishes that survived and the pieces on this site that belong next to them. No guest names travel. No invented chairs.
Dietary tags are a filter. They are not a promise.
Said plainly, because it matters more than anything else on this page. Dietary categories inside Occasion OS are planning filters, not allergy-safe guarantees. The app will help you plan around a declared need. It will not stand in a kitchen and enforce cross-contact control, because it is a piece of software and not, in fact, in your kitchen. That confirmation stays a human conversation — the one you have out loud with your guest, before the invitation becomes a commitment.
A filter narrows a list. It does not clean a board, change a pan, or remember which knife went into which bowl. The route can take a dish off your list. It cannot tell you that the kitchen is safe, and no amount of software is going to get closer to that than it already is.
The shop happens once
Written from a town where the store is not around the corner and a forgotten ingredient is not a five-minute problem, so the list gets treated as a single shot rather than three casual trips. The prep block is where the honesty lives: what can be done two days out and hold, what has to happen the morning of, and the short list of things that cannot be touched until the guests are already in the house. Most hosting disasters are not cooking failures. They are sequencing failures.
The prep block is also the part people argue with. Two days out feels far too early, right up until the morning of arrives carrying six jobs and one sink. Very little genuinely improves for being made later. A great deal of it gets worse for being made at four in the afternoon on the day.
The Menu Builder handoff
Nothing arrives here by magic. You carry a menu over yourself, the receiver picks it up, and there is a version number attached for anyone who finds version numbers reassuring. If you are not that person, ignore that sentence entirely and the plan still works. The same food-safety boundary shows up on every route, every time, rather than sitting in a footnote you will read after something has already gone sideways.
What it will not do
No silent inference between apps. No star ratings and no manufactured social proof. No account demanded of you just to build a plan, because the point was never to collect you, it was to get dinner on the table on time.
The last one is the only item on that list that costs anything to hold to. An account would make a plan easier to save and easier to sell back to you afterwards, and the second of those is why most sites ask for one. Dinner at seven thirty does not need it.
WHEN THE NIGHT GOES OUT INSTEAD
Sometimes the correct route is: do not host.
If the plan reveals that this particular night is better off-site — too many guests, not enough runway, an oven schedule that cannot be untangled — that is a legitimate outcome and not a defeat. Book a table, pour something good, and let the night be somebody else’s problem.
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