Case study No. 16
No more telephone edits on the restaurant reservations page
Day to day with restaurant reservations, the person asking, the person approving and the person publishing all look at the same words. Routine changes stop generating meetings.
Case docket
- Restaurant Chinese restaurant with banquet room, Lexington, Kentucky
- The team 12 staff; one locally managed operation
- Built with Structured change request, Named approver, Before-and-after preview, Publication check 4 parts
Working days after content approval, including staff review and handover.
Before
Where the restaurant started
The starting point
Update requests for restaurant reservations arrived as casual notes: something needs changing, somewhere, somehow. The precise text was rarely included.
What it cost the team
For restaurant reservations, publishers guessed intent and approvers signed off unseen wording. When the published text surprised someone, there was no record to consult.
What we built
The fix, in plain terms
A compact change-request format now records the page, the current wording, the proposed replacement and the approving contact. Reference updates concerning reservation guidance and the current food menu pass through the same review before publication.
The parts that went in
- Structured change request
- Named approver
- Before-and-after preview
- Publication check
Timeline
25 working days, from sign-off to handover
Content approved
The working-day count starts once the restaurant has signed off the content that goes on the page.
Built
A compact change-request format now records the page, the current wording, the proposed replacement and the approving contact.
Staff review
The restaurant's own team checked the work against how they actually take inquiries before anything went live.
Handed over
Live and handed over 25 working days after content approval.
After
What changed
Day to day with restaurant reservations, the person asking, the person approving and the person publishing all look at the same words.
Routine changes stop generating meetings.
There is a record of every restaurant reservations edit and its approver. The informality we used to call flexible, we now call risky.
Is your inquiry form costing you mornings too?
Show us your current site on a live walk-through and we will point at the first thing we would fix, and say so if it is not the website at all.
Questions about this project
How long did this project take?
25 working days after content approval, including staff review and handover. On our plans a new site goes live in 7 days on The Daily Menu, 10 on The Full Menu and 15 on The Tasting Menu, counted from the onboarding call.
What exactly did the Chinese restaurant with banquet room get?
A compact change-request format now records the page, the current wording, the proposed replacement and the approving contact. Reference updates concerning reservation guidance and the current food menu pass through the same review before publication. The pieces, in the restaurant's own list: structured change request, named approver, before-and-after preview, publication check.
Would the same fix suit my restaurant?
It fits any restaurant whose starting point sounds like this one: Update requests for restaurant reservations arrived as casual notes: something needs changing, somewhere, somehow. The quickest way to tell is a demo call, where we look at your current site and say plainly whether this is the fix it needs or whether something else matters more.
Is this part of a plan, or an extra?
It is part of building and running the site. The site features this project used: weekly updates so specials and hours never go stale (on every plan). Plans start at $117 a month, the $647 build fee is invoiced only after launch, and 5 revisions a month are included.
More case files
Related case studies
More projects for casual and family dining and restaurants that had the same problem.
- Thai family restaurant, Santa Rosa, CaliforniaEnding the restaurant reservations version confusionWhen it comes to restaurant reservations, the business maintains key information in one place and has a practical method for checking related pages.Read the case study
- Neighborhood bistro restaurant, Newark, DelawareShowing the working behind restaurant reservationsDay to day with restaurant reservations, the site now argues with evidence the business chose to publish.Read the case study
- Lebanese mezze restaurant, Harrisburg, PennsylvaniaOld restaurant reservations links, new destinationsWith restaurant reservations, old links resolve to sensible destinations instead of error pages.Read the case study
Related services
- Restaurant website redesignRestaurant website redesign that keeps your search rankings through redirects, replaces the old menu PDF and hands you a managed, custom-coded site.
- Websites for casual and family restaurantsA website for a casual or family restaurant that keeps hours, kids menus and specials current
See the site you would get
About 30 minutes, on your screen, built around your menu and how your team takes bookings. Plans from $117 a month, with the $647 build fee invoiced only after launch.