What the restaurant needed before launch
The client was a busy neighbourhood restaurant in Table View serving dine-in guests, bookings for small groups, weekend functions, and online enquiries from surrounding suburbs. The team needed a simple way to set out booking rules, explain promotional offers properly, and handle customer information without causing confusion at the table or in the reservation process.
The brief was practical. The restaurant wanted wording that could be used on the website, in booking confirmations, and on special offer pages without sounding stiff or overly legal. They also needed the privacy wording to match how enquiries were handled day to day, especially for name, contact number, dietary notes, and event details. With load-shedding, last minute changes, and peak service times, the copy had to be clear enough for staff to rely on when things got busy.
- Table View location with bookings from surrounding Cape Town areas
- Online reservations, promo specials, and enquiry handling
- Customer privacy wording for names, contact details, and booking notes
- Plain language that staff could use without constant rewording
The constraints we had to work around
Restaurant websites often have one foot in operations and one foot in marketing, so the wording has to do both jobs without creating disputes. In this case, the team needed to protect table availability during peak periods, make promo conditions easy to understand, and explain what happens if a booking is late, changed, or cancelled. They also wanted their terms to cover practical matters like deposit requests for functions, allergens raised by guests, and no-show situations.
There was also the issue of customer data. Booking forms can collect more than just a name and time. Once you add phone numbers, email addresses, special requests, and event notes, the restaurant needs a clean privacy position that tells customers how that information is used and stored. We kept the wording direct and short enough for a hospitality setting, while still covering the key points needed for compliance. No fluffy language, just usable copy.
- Clear booking cut-off times for busy service periods
- Promo rules that set out dates, availability, and exclusions
- Privacy wording for booking details and guest communications
- Function and group booking conditions where deposits may apply
What TsAndCs supplied for the project
We prepared a focused compliance pack for the restaurant, with wording tailored to the way the team actually takes bookings and runs offers. The work included booking terms, promo rules, customer privacy wording, and a launch readiness check so the pages could go live with fewer gaps. We also reviewed the practical flow from enquiry form to confirmation message, because the user journey matters just as much as the legal text.
TsAndCs then adjusted the document set so it fit the restaurant's tone of voice. The copy had to sound like a real hospitality business speaking to guests, not a law firm writing to another lawyer. The result was a set of terms that could be placed on the website, copied into confirmations, and referred to by staff during high traffic periods when quick answers are needed.
- Booking terms for reservations, late arrivals, cancellations, and no-shows
- Promo rules for special offers, limited availability, and exclusions
- Customer privacy wording for enquiry and booking data
- Launch check covering links, form wording, and policy visibility
Delivery timeline and how the work moved
The project ran over three weeks from first brief to final handover. Week one was the discovery and wording stage, where we mapped the booking flow, the promo rules, and the types of customer information being collected. Week two focused on drafting and checking the wording with the restaurant team, especially around terms that affect table management during busy evenings and weekend sittings.
In week three we completed the final review and handover. That included checking the policy links, making sure the wording matched the customer journey, and confirming the sections that staff would use most often. The process was steady and practical, with one main round of changes and a final tidy-up once the team had tested the pages on their side.
- Week 1: brief, booking flow, data collection review
- Week 2: drafting, revisions, promo and reservation checks
- Week 3: final review, handover, live-page confirmation
What changed once the wording was in place
Once the booking terms and promo rules were added, the restaurant had fewer back-and-forth questions from guests about what was included and what was not. Staff could point to one clear set of terms instead of explaining each offer separately. That matters in hospitality, where the front of house team is already managing walk-ins, specials, timing, and kitchen updates.
The privacy wording also gave the team a cleaner way to deal with guest details. Customers could see what information is collected and why, which helped reduce uncertainty around reservation forms and event enquiries. The final result was not about making the site look busier. It was about making the business easier to run, with less confusion around bookings, promotions, and customer data handling.
- Fewer questions about offer conditions and booking rules
- Clearer handling of guest data in forms and confirmations
- Better support for staff during peak service hours
- More confidence when running online specials and functions
What we would repeat on a similar restaurant project
We would handle a similar project the same way again: start with the real booking process, write for staff as well as guests, and keep the policy set short enough to stay useful. In a restaurant setting, the best compliance copy is the kind that works on a Friday night when the place is full and the phones are busy. That means plain language, visible links, and rules that match the way the business actually operates.
We would also keep the privacy wording tightly linked to the enquiry form and booking confirmation. If a restaurant collects dietary information, event notes, or promotional sign-up details, those points should be dealt with clearly from the start. For this Table View project, that approach made the launch more manageable and gave the team a clean reference point for future updates.
- Start with the actual booking and promo workflow
- Keep the wording short enough for busy service teams
- Match privacy language to the forms and confirmations used
- Review the policies again when offers or booking rules change
Key facts
| Project type | Restaurant website compliance pack |
|---|---|
| Town | Table View, Cape Town |
| Timeline | 3 weeks |
| Core documents | Booking terms, promo rules, customer privacy wording |
| Main compliance focus | POPIA alignment and reservation handling |
| Delivery | Online policy pack with launch readiness review |
