A practical venue guide
Change the diary.
Keep the service steady.
Use this checklist with your team and whoever looks after your website. Rehearse with made-up guests before moving a real service onto new software.
1. Write down the rules you already use
- List every table, its seats, area and allowed combinations.
- Agree lunch and dinner arrival times, table duration and reset time.
- Decide how many guests the kitchen can accept in each rolling arrival window.
- Record your large-party, pre-order, deposit and cancellation arrangements.
- Decide who can change a booking, close a service or see customer details.
Do not copy every unusual request into a rule. Identify the routine service first and keep exceptions staff-led.
2. Rehearse on a separate installation
Community needs its own server, private database and mail configuration. Follow the installation guide; the public website cannot host your real bookings. Begin with synthetic records.
- Book a table from a phone and find it in the staff diary.
- Try a party that needs tables joining.
- Check that a full kitchen window cannot accept too many arrivals.
- Enter a phone booking and a walk-in.
- Amend, cancel and mark a booking as seated or completed.
- Try a session closure when reservations already exist.
- Print a service sheet and check it with the team.
3. Prove email and recovery work
A queued message is not a delivered confirmation. Send a controlled test through your own mail service and check the result. Take a consistent backup and rehearse restoring it in an isolated environment with email and payments disabled. Keep a protected backup away from the live server.
Have a fallback: a printed service sheet, a person who knows the recovery steps and a way to handle new requests during an outage.
4. Choose one clear handover
Pick a quiet point in service. Check every future booking against the old diary, including party size, arrival time, special arrangements and deposits already taken. The current CSV import is for customer contacts; it does not import future reservations.
Choose which diary is authoritative after handover. Two independently edited diaries create conflicting promises. Keep the old records safely for reconciliation, and enter remaining future bookings with staff tools before opening the new booking link.
Only import marketing consent when you have evidence. A past booking does not automatically mean someone wants promotional email.
5. Review the first services
Ask the team where they hesitated, whether arrivals were paced sensibly, whether any bookings needed manual correction and whether confirmations arrived. Record setup and support time as well as bookings. Adjust the rules from actual service experience.
Guest self-service changes, online card deposits, SMS and POS integrations are not available in this pilot. Keep a clear human process for those needs.