A grown-up way to change the seasonal dining menus page
For seasonal dining menus, both parties review the same explicit version of a change. Routine updates are checked against an approved request rather than reconstructed from a chain of clarifying messages.
- Client
- Neighborhood bistro restaurant
- Region
- Worcester, Massachusetts
- Size
- 18 staff, one locally managed operation
- Timeline
- 25 working days
How it went, course by course
Four stages, in the order they happened, in the words the project was recorded in.
01 · Where they started
Edit requests for seasonal dining menus content arrived without the text they referred to. Interpretation filled the gap, sometimes wrongly.
02 · What was going wrong
Day to day with seasonal dining menus, publishers guessed at intent; approvers signed off wording they had not properly seen. Errors slipped through a process with no shared reference point.
03 · What we built
A short request format now records page, current wording, proposed wording and approver. Changes touching the current menu and staff-reviewed dietary guidance clear the same review before going live.
04 · What changed
For seasonal dining menus, both parties review the same explicit version of a change. Routine updates are checked against an approved request rather than reconstructed from a chain of clarifying messages.
What went into it
- Structured change request
- Named approver
- Before-and-after preview
- Publication check
25working days
The time it took
After content approval, including staff review and handover. A new site goes live in 7 days on The Folio; work like this runs through your monthly revisions or alongside the build.
Book a demoI see precisely what will change on the seasonal dining menus page before it does. The informality has been replaced with a record.
Questions about this project
How long did this project take?
25 working days after content approval, including staff review and handover. The clock starts once the restaurant has approved the content, so the time is spent building and checking rather than waiting on copy.
Which parts of the offer did it use?
Structured change request, Named approver, Before-and-after preview, Publication check. On this site that work sits under revisions built for a menu that changes, which is included on every plan from The Folio up.
Why is the restaurant not named?
We describe each client by the kind of restaurant it is and where it is: here, a neighborhood bistro restaurant in Worcester, Massachusetts, 18 staff; one locally managed operation. The quote is credited to Wilfred Westfield, bookings coordinator. We never publish a trading name, address, logo or photograph.
Could the same work fit our restaurant?
If guests read your pages or send you inquiries before they visit, most likely. Nothing here was a custom add-on: plans start at $117 a month, the $647 build fee is invoiced only after launch, and a walk-through on your own menu shows what the equivalent would look like for you.
See what this would look like on your menu
A live walk-through of the site you would get, in about 30 minutes. Plans from $117 a month, the $647 build fee invoiced only after launch, domain and hosting included.
Or compare the plans and pricing first.