Chef menu approval: the law of two signatures
Updated September 15, 2026.
The law of two signatures is Banquette’s banquet menu approval workflow: a private event’s menu becomes sellable only when two different chefs have signed it from their own chef seats, and changing any course voids their signatures.
It is chef sign-off on event menus, built into the private dining software rather than kept in a binder by the pass. The kitchen or the general manager writes the menu, two chefs sign for it, and the event contract’s first send is refused until they have. The rule was written inside a working restaurant, where the kitchen that cooks the party is the one that should promise it.
- A party’s menu is sellable only when two different chef-seat accounts have signed it.
- Each signature is bound to a fingerprint of the courses. Change a course and the earlier signatures are void.
- The general manager can set a menu but cannot sign one.
- A contract’s first send is refused while the party’s menu lacks two chef signatures. A party with no menu yet can still be sent.
- A change of price does not reopen the signatures. The chefs sign for the courses.
- Kept house menus live in Menu Studio. A menu taken onto a party is a copy, and the copy is what the chefs sign.
How does chef sign-off on an event menu work?
A menu arrives on a party, written for it or taken from the house’s kept menus. At that moment it is unsigned. One chef opens it and signs. A second chef, on a different account, signs as well; one chef signing twice does not count. With two signatures on it the menu is sellable, and the contract can go out.
Who can sign a menu, and who cannot?
| Seat | Part in menu approval |
|---|---|
| Chef seat | Signs the menu; two different chef accounts are needed. Writes kept menus. |
| General manager | Sets a menu on a party and writes kept menus. Cannot sign. Countersigns the contract. |
| Events manager | Countersigns the contract. |
| Coordinator | Drafts and sends the contract; its first send is refused until the chefs sign. Cannot countersign. |
| Host | Reads the menu by course and dish. Writes to the office for changes. |
The seat decides, not the title on it. At a club we can title the second chef seat Director of Food & Beverage when we set the house up; the rule underneath still asks for two chef-seat signatures. More on event management for golf and country clubs.
What voids the chefs’ signatures?
A change to the courses. Each signature is bound to a SHA-256 fingerprint of the courses as they stood when the chef signed. Change any course and the fingerprint no longer matches, so the earlier signatures are void and the menu waits for two chefs again.
A change of price does not. The fingerprint covers the courses and nothing else, so the office can adjust what a party pays and the ink stands. The chefs sign for the food; the money is the office’s.
Why does the contract wait for the menu?
Because a contract is a promise, and the food is most of it. When the office sends a party’s contract for the first time, Banquette checks the menu. If it lacks two chef signatures, or part of it is unreadable, the send is refused.
Two things the rule does not do. A party with no menu yet can still be sent its contract, so the paper can go out while the kitchen is still writing. And the check sits on the first send only; it does not recall a contract already out. Once the host signs from their private page, with no login, the general manager or events manager countersigns and the party is contracted.
Where do the menus come from? Menu Studio
Menu Studio is where a house keeps the menus it sells again and again. Each has a title, a line beneath it, a price per guest, the courses, the kitchen’s notes and, if it belongs to one, a room. A blank price means not priced, never $0. The composer draws from the plates already on the house’s books, or takes a dish in the kitchen’s own words.
Taking a kept menu onto a party makes a copy. The studio records where it came from and warns before replacing a menu the party already has, and the two-signature rule applies to the copy. Each kept menu lists the parties served from it. Menus retire; they are never deleted. The kitchen and the general manager write, and every seat reads. A kept menu prints as a one-page letter guest sheet with the house’s masthead, no prices and no software branding.
Who reads the party’s menu?
Everyone the evening touches. The host sees it on their own page, as course labels and dish names. Each guest sees the same on their RSVP page, with no account. The kitchen reads it on the BEO and the printed kitchen sheet; the sheet sets it beside the count to cook to and every guest’s dietary note. New to the term? Here is what a banquet event order is.
How do other event platforms handle menu sign-off?
What four vendors’ own pages document. A help article that is silent on approval is not proof the feature is absent.
| Platform | Menu sign-off, as documented |
|---|---|
| Banquette | Two different chef seats sign; a course change voids the signatures; the contract’s first send is refused until both have signed. |
| Tripleseat | Menus built from items, packages and modifiers. The Menus Overview documents no approval workflow. |
| Perfect Venue | Clients pick menu choices on the proposal; proposal locking can stop changes at signing or one to three weeks out. Its menu guide does not mention approval. |
| Planning Pod | Documented sign-off: the client e-signs the BEO. No internal chef or kitchen approval step is documented. |
| Northstar Banquet & Catering | Menus as reusable templates, integrated with F&B inventory. No menu-approval workflow is described. |
Where they go further: Perfect Venue and Planning Pod let the client choose from the menu, and Northstar is integrated with F&B inventory. Banquette does neither. Side by side: Banquette and Tripleseat, compared; Banquette and Perfect Venue, compared; Banquette and Planning Pod, compared.
Sources: Tripleseat help center, Menus Overview; Perfect Venue help center, All Things Menu; Perfect Venue help center, Proposal locking; Planning Pod help center, the client portal; Planning Pod, food and beverage tools; Northstar, Banquet & Catering. Checked September 15, 2026.
Questions about chef menu approval
What is a banquet menu approval workflow?
It is the step between writing a private event’s menu and selling it. In Banquette it is the law of two signatures: a party’s menu becomes sellable only when two different chefs have signed it from their own chef seats, and the contract’s first send is refused until they have.
Does it have to be the executive chef and the banquet chef?
No. Banquette checks for two different chef-seat accounts, not particular titles. We set seat titles when we set a house up, so at a club the second chef seat can read Director of Food & Beverage; the rule underneath is still two chef-seat signatures.
Can the general manager sign a menu?
No. Only chef seats sign. The general manager can set a menu on a party and write kept menus in Menu Studio, and countersigns the contract, as the events manager can.
What happens when a course changes after the chefs have signed?
The signatures are void. Each one is bound to a SHA-256 fingerprint of the courses as they stood when it was given, so any change to a course breaks the match, and the menu waits for two chefs to sign it again.
Does a price change reopen the signatures?
No. The fingerprint covers the courses only, so a change of price leaves the chefs’ signatures standing. A change of course is what voids them.
Can the contract go out before the menu is signed?
Not if the party has a menu. The contract’s first send is refused while the menu lacks two chef signatures or any part of it is unreadable. A party with no menu yet can still be sent its contract, and the check applies to the first send only.
Does the host approve the menu?
No. The host reads the menu, by course label and dish name, on their private page and writes to the office for any change. Banquette has no host approval of a BEO; the sign-off belongs to the kitchen.
The party’s menu on the event order and on the printed sheet the line cooks from.
A client portal with no login, where the host reads the order and signs the contract.
From the inquiry to the kitchen sheet, on one book, for a restaurant’s private dining.
Flat monthly, per property: Solo is $249, House is $499. Never a percentage of revenue.