A handover that outlives the seasonal dining menus project
For seasonal dining menus, the team operates the site from its own reference document. Updates no longer wait on anyone's memory or calendar.
- Client
- Mexican cantina restaurant
- Region
- Columbia, South Carolina
- Size
- 15 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
Earlier projects had delivered pages and departed. Routine questions about maintaining seasonal dining menus content depended on people who no longer answered email.
02 · What was going wrong
Day to day with seasonal dining menus, staff were unsure how to request an update, test a form or establish who had approved a change. Routine website tasks stalled whenever the usual contact was away.
03 · What we built
Alongside the site, the team received a page inventory, maintenance instructions, contact details and a guided check of the route to a reservation discussion with the host team. Responsibility for the current menu and staff-reviewed dietary guidance is assigned to a named owner with a backup.
04 · What changed
For seasonal dining menus, the team operates the site from its own reference document. Updates no longer wait on anyone's memory or calendar.
What went into it
- Page inventory
- Maintenance notes
- Backup reviewer
- Form check instructions
- Support contacts
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 demoGood seasonal dining menus pages matter; knowing how to maintain them matters more. The handover lets anyone here pick it up.
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?
Page inventory, Maintenance notes, Backup reviewer, Form check instructions, Support contacts. On this site that work sits under revisions built for a menu that changes and hosting, security and uptime, handled, which are 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 mexican cantina restaurant in Columbia, South Carolina, 15 staff; one locally managed operation. The quote is credited to Susan Tolliver, table bookings administrator. 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.