I have hired the binder consultant. More than once, in more than one F&B operation. You know the engagement: a firm walks the floor for a few days, pulls your sales mix, sits with your GM, and three or four weeks later hands you a bound document. Tabbed. Heavy. Five figures, and genuinely good work.
Then it goes on a shelf. And fourteen months later someone asks whether it is time to do another one.
The problem was never the quality of the analysis. The people doing this work are sharp and the frameworks are sound. The problem is the interval. A menu review is a photograph of a moving thing, and an annual one is already months stale on the day it is bound.
What moves between the reviews
Sit with what actually changes inside a working operation over a year.
Your costs move — not in a tidy annual step, but continuously. A supplier renegotiation here, a seasonal spike there, a protein that quietly climbs eight percent over a quarter while nobody is watching the line. The food cost percentages in a March review are not the ones in September.
Your sales mix moves. Every cover rewrites it. The dish that was your third-best seller in spring is your seventh by autumn — guests responded to a competitor’s new menu, or a price you nudged, or nothing you can name. The mix is being rewritten in your POS as you read this.
Your comp set moves. The restaurants you compete with adjust prices and rotate dishes all year. An annual review captures their position on one day; by the time you act, your pricing sits relative to a market that no longer exists.
None of this is dramatic. That is exactly why it is dangerous. There is no single bad day — just a slow accumulation of drift. A Plowhorse that should have been repriced in May still bleeding margin in November. A Puzzle still buried in the wrong position. A dish that turned into a Dog two seasons ago still holding a line and a prep station.
The interval is the bug
Here is what took me too long to see as an operator. The annual review is not a smaller version of the right thing. It is the wrong shape entirely.
When the cadence is annual, the review has to be exhaustive, because it gets no second look for a year. So it is long. Because it is long, it is a project — a thing you brace for and recover from. Because it is a project, you do it rarely. The binder is heavy because it is annual, and annual because it is heavy.
That structure also forces a particular kind of recommendation. An annual review cannot say “watch this dish for four weeks and we will revisit” — there is no revisit. So every recommendation is a standalone bet, made once, with no feedback loop. You change the price, reprint the menu, and find out whether it worked from your own P&L months later, with no analyst in the room.
That is not how good operating decisions get made. Good decisions are small, frequent, and checked: you move one thing, watch what the floor does, adjust. The annual review structurally cannot work that way.
What the cadence should be instead
The frameworks do not need fixing. Plot every item by contribution margin and popularity, layer in food cost and the time-and-space view, classify, and act — that logic has held for decades, and the methodology is built on it. What needed fixing is how often you run it.
Most of the inputs already refresh inside a day. Sales mix is in your POS in real time. Costs are knowable as fast as you choose to look. Comp-set pricing is public and moves in days. The two-week data-gathering phase that justified an annual project in 1985 does not exist anymore. The only thing still on an annual clock is the analysis itself — and that is a habit, not a constraint.
So the answer is not a better binder. It is a continuous cadence: the same rigour the binder consultant brings, running every week instead of once a fiscal year, so drift never gets more than seven days to accumulate before someone names it and acts. That is the whole idea behind Couverte. A Verdict gives you the deep first read, and the cadence keeps it from going stale the moment it lands.
The binder consultant was never wrong about the menu. They were wrong about the calendar. A menu is not an annual problem. It drifts every week, so it has to be read every week. Anything slower is archaeology — accurate about a restaurant that has already moved on.