Skip to content
Night record

Planning here works on its own. Once a night starts, it travels between the three tools by itself.

Kitchen planner

Something runs out first. Usually the oven.

Quantities, a shopping list and a prep clock for your menu — checked against your racks, burners, fridge space and hands, so you find out what gives first while the menu is still a draft.

Starting points

Real nights, ready to load

Load one, then change a single fact to see what it costs you. Your own setups can be saved, pinned and renamed on this device.

Open the dish library →
Table
Crowd
Constrained
Outdoor
Your saved setups

Nothing saved yet. Build a night, name it in the box beside the plan, and it lands here — on this device, for the next time these same eight people come over.

Start here

Five facts. First plan.

Give Occasion the facts that change the route most. Everything else sits at a default until you refine it, and anything still on a default is marked as one.

01

What kind of night is this?

02

How many people?

8
03

How does food reach the table?

How will food reach the table?
Seats availableseated service cannot exceed this

Nothing is invented in the meantime. Seated service stops rather than guess a chair.

04

When does food need to land?

05

What can the kitchen heat at once?

Ovens

Usable burners

normal fridge · medium counter · dishwasher · no grill

Until that is ticked these are the form's opening numbers, not yours, and every timing built on them is marked as such.

Refine this night

The rest of what changes the plan

Prep window, fridge, counter, helpers, food needs, budget, drinks and the full operating surface. None of it is required for a first plan. All of it moves one.

Start here

Set up the night

Start with the facts that change the plan most. The deeper choices stay out of the way until you need them.

1 · Essentials

What are you hosting?

8 guests · seated · service 19:00

Occasion
How will food reach the table?
Guests
8
Seats availableimportant for seated service

That is fine. The plan will flag seating as something to confirm rather than guess.

optional
How much cooking time do you have that day?
5 h available
2 · Kitchen & help

What can the room actually support?

1 oven · 4 burners · 1 helper

Ovens
Usable burners
Fridge space
Counter space
Extra equipment
Who is helping?
3 · Food & feel

Shape the menu

Considered · winter · no food filters

How ambitious should the menu be?
Season
Budget
Would you like leftovers?
Drinks
Room notes
Food needsUse these for menu planning; always confirm allergies directly with guests.
Cuisines you want to lean towardLeave blank to mix freely.
4 · Ask the guests

What the table told you

No guest link yet · nobody has been asked

Send a link and the people coming tap closed-list chips — no name, no email, no free text. The counts land here, and go into the plan only when you say so.

One link for the whole table. Everyone answers on the same one.

Dietary chips are planning filters, not an allergen-safety guarantee. Anything serious is still a conversation with that guest.

Only if it matters

More hosting details

Table setup, crowd flow, special limits and outdoor logistics. Most dinners can skip this.

Open only the questions that change this night. Skip the rest.

Seats have not been declared and nobody has surveyed the kitchen. The plan will still build, on placeholder figures, and will be marked as built on them. .

Set the night, then build the plan.

Tonight’s plan

Tonight’s plan

Hands picking thyme over a board of charred lemon halves, beside stacked containers labelled Lemon, Chervil, Tarragon and Thyme and a handwritten timing list

No plan yet, because you have not said anything yet

This side of the page stays blank until it has been told who is coming and what you cook on. Nothing is guessed and nothing is filled in from a default that flatters you — an oven you do not have would produce a night you cannot run.

Do not start from a blank form if you would rather not. The ready-made nights above load a real guest count, a real kitchen and real timings in one click; change the guest number and rebuild, and watch where it starts to strain. That loop is the whole product. The kitchen sheet falls out of the end of it.

Load a night that already exists

Occasion is a planning tool. Starter menus are not kitchen-tested recipes unless a Salty & Clever link says so. Food-need tags are planning filters, not allergy safety.

Live host

Dinner is at 19:00. Something slipped.

The plan is the route. Live Host is what you use when the roast is twenty-five minutes behind: mark Done, or take a recovery — the remaining sequence rebuilds against the actual oven, burners, fridge and hands.

How this plan decidesWhat it will not guess, what it promises, and the step-by-step build console.
The house rule

We stop rather than guess.

Most planners will answer whatever you ask them. This one will tell you that the night you have described does not fit the kitchen you have described, and it will tell you while the invitations are still unsent.

When something has to give, it names what runs out first — the oven at four o’clock, or your own hands between six and seven — instead of quietly shrinking a dish until the arithmetic closes. It will not read seats off a guest count. It will not certify an allergen, and no amount of tidy output from this page is a substitute for asking the person who has to eat.

Where it cannot answer honestly it stops, says which fact is missing, and hands the question back to you.

What this plan honours

Line by line

Each row is a fact you declared and what the plan did with it. Anything still open says so here.

  • GuestsSet

    8 counted

  • SeatingStopped

    Not declared — will not invent chairs

  • EquipmentSet

    1 oven · 4 burners · normal fridge

  • Dietary filtersSet

    None declared — confirm ingredients yourself

  • DrinksNeeds input

    wine declared

  • Shopping listNeeds input

    Built after you evaluate

  • Prep clockNeeds input

    Built after you evaluate

  • Wine and drink pairingsNeeds input

    Filed against each dish

  • Recipe cardsNeeds input

    One card per dish on the route

  • Tight spotsNeeds input

    Named after you evaluate — or the plan stops

Build the plan

Four steps

Building the plan happens in four steps. Each one shows what it found. Step through, or let it run.

  1. 01Ready

    Choose the dishes

    Waiting

  2. 02Ready

    Kitchen load

    Waiting

  3. 03Ready

    Timing

    Waiting

  4. 04Ready

    Cost and balance

    Waiting

Earlier plans

No completed plans on this device yet.