Running a lunch menu that updates itself, every week

The weekly lunch menu is the part of the menu that changes the most and gets the least care — because it's the same tedious task every single week: retype five dishes, re-export a PDF, re-upload it, and hope nobody notices the version from two weeks ago is still cached somewhere. The fix isn't discipline. It's a structure that needs less redoing in the first place.

Split the menu into two things, not one

Most of what's on a lunch menu doesn't actually change day to day. The house salad, the daily soup base, the drink included with lunch — these are standing dishes, and they show up under every active day automatically once you've entered them. You type them once.

What actually changes is a shorter list: the one or two daily dishes — the actual dish of the day — that rotate. Splitting the menu this way means a weekly update is genuinely just typing the daily specials, not rebuilding the whole thing from scratch.

Only build the days you run

If your lunch menu runs Monday to Friday, there's no reason to have empty weekend slots sitting in the structure. Pick the weekdays a given menu applies to, and you only ever add dishes for those days — which keeps the editing screen, and the published menu, from carrying dead weight nobody's going to read.

One menu per week, on purpose

Each week has exactly one menu. That's a constraint, but it's a useful one: it means there's never a question of which version is the "real" one, and copying last week's menu as your starting point is faster than rebuilding from nothing when the specials are similar. Switch to the week you're planning, copy if it helps, then only touch what's actually different.

Order matters more than it seems

The order dishes appear in is the order guests read them in, and that's a small lever most restaurants leave unused. Whatever you'd want a hesitant guest to see first — the dish with the best margin, the one that's easiest to say yes to — put it first. It's a drag-and-drop change, not a rebuild.

Draft, then schedule

Saving a weekly menu doesn't publish it immediately — it saves as a draft and moves you to scheduling, where you decide exactly when it goes live. That gap is useful: you can build Monday's menu on a Thursday afternoon without it appearing early, and you can prep several weeks ahead during a quiet moment instead of scrambling every Sunday night.

What "automatic" actually buys you

None of this removes the work of deciding what's on the menu — that's still a kitchen decision. What it removes is the retyping, the re-exporting, and the gap between "we decided this" and "guests can see it." Once the menu's built for a week, it's live everywhere the moment you schedule it — no separate step for the website, because that part is already connected.

Next steps

The full walkthrough of building a weekly menu — including field-by-field detail — is in creating your weekly menu. And once a few weeks of menus are live, understanding your analytics shows you which weeks actually got opened the most.