A guide for owners, managers and the team
Your Coverstead
user manual.
This guide covers setting up a venue and using Coverstead through a service: customer bookings, the staff diary, walk-ins, service sheets, customer records and team tools.
Practise with sample bookings before your first real service. Check email delivery and backup recovery on your own installation. The hosted subscription checkout is test-only; it does not create a hosted venue.
Try the customer demo → Try the staff demo →
The public demo is a browser-only walkthrough of core booking and diary tasks, using fictional data. It does not show every feature. To explore the complete installation locally, follow the installation guide and use the source package's demo command.
Need to install the software, configure HTTPS or connect email? Use the separate installation manual. This user manual focuses on using the app once it is running.
To save or print this manual, use your browser’s Print command and choose A4 or Save as PDF. Expand any sections you want to keep.
1. Create your owner account
Open your own installation’s Venue setup page. Enter the private installation token supplied during setup, your name, email address and a password of at least 16 characters. Keep the token and password private.
The token can create only the first owner account. After that, sign in with your staff account. Your booking page stays closed until the venue setup has been completed.
Each venue needs its own installation. The product website at coverstead.net is not a shared staff desk for all venues. A Stripe test billing account is separate from a venue owner account.
2. Configure your venue
The guided setup saves drafts on the server so you can return to unfinished work. Review every step before opening bookings.
- Venue identity: name, contact details, address, branding, guest notes and accessibility information. Upload your own logo if needed.
- Tables and areas: give each table a capacity and area. Add only the table combinations you can actually use. Set the overall seating cap.
- Dining times: configure the days and lunch/dinner periods you serve, the last arrival, dining duration and reset buffer.
- Booking rules: choose how far ahead guests can book, minimum notice, arrival intervals, online party limits and kitchen arrival capacity.
- Groups and seasonal events: set the group threshold, deposit record and pre-order requirements. One seasonal event type is supported.
- Menus and communication: add public menu links or upload PDFs. Check guest-facing information and sender readiness.
- Review: inspect the summary, complete setup, and rehearse a guest booking and a staff change.
If someone else changes the settings while you are editing, reload and review their changes before saving again. Table changes that would invalidate future bookings are rejected: reassign those reservations first.
3. Understand availability
A free chair alone does not make a booking available. Coverstead checks service times, booking notice, table capacity, permitted combinations, the venue seating cap, overlapping bookings and kitchen arrivals.
The kitchen rule limits arrivals within a rolling window. Dining duration and the reset buffer determine when a table can be offered again. Cancelled reservations release their space.
Accessibility details are operational notes, not an automatic table-allocation rule. Read guest requirements and check the arrangement with the customer when needed.
If a guest cannot find a slot, check the date and service, closures, notice period, party size and kitchen pace before changing settings. Do not raise limits unless the team can deliver the service.
4. The customer booking journey
- The guest opens your venue’s booking link and chooses a regular or available seasonal booking.
- They select a date, party size and an available arrival time.
- They provide contact details and any dietary needs or requests, then acknowledge your booking conditions.
- Email marketing consent is a separate choice; it is not required for the reservation.
- On success, the guest sees a booking reference and the reservation appears in your diary.
Availability is checked again when the booking is submitted. A slot may have filled since it was first displayed; the guest must then choose another time.
Confirmation messages enter the email outbox. They are delivered only when SMTP and sender readiness are configured. A queued email is not proof that the guest received it.
Guest self-service changes and cancellations are not implemented in this release. Ask customers to contact the venue, then make the change in the staff desk.
5. Use the staff diary
Sign in to your venue’s Staff desk. Choose a day, week, month or all bookings, then narrow the view by service, booking type or search. Search can help find a guest, telephone number, email address or booking reference.
Use the cancelled-bookings option when you need to review cancelled records. Diary filters change what you see; they do not alter the reservations.
Open Manage beside a reservation to inspect contact details, guest requirements, table assignment, deposits, pre-orders and private staff notes. Read the requirements before moving guests or arranging tables.
Booking statuses include confirmed, awaiting deposit for seasonal bookings, seated, completed, no-show and cancelled. Mark completed visits accurately because customer history and loyalty eligibility depend on them.
6. Change or cancel a booking
- Find the reservation and choose Manage.
- Change the arrival time, party size, assigned tables, status or staff notes as needed.
- Review any new deposit or pre-order requirement. Changing party size can clear the pre-order received tick so the revised order can be checked.
- Choose Save booking changes. Capacity and table conflicts are checked again.
To cancel, choose Cancel booking & remove from diary and confirm. The cancelled record stays in customer history, while its tables and kitchen capacity are released. Applicable cancellation emails are queued when an email address is recorded.
A recorded deposit is not refunded automatically. Handle any refund separately and make a clear staff note. Staff notes are private operational information and are not included in guest messages.
7. Phone bookings and large parties
Choose Add a booking. Select an existing customer or enter new details, then choose the date, time and party size. Telephone is required; staff can leave email blank when the guest does not supply one.
For ordinary bookings, allow automatic table allocation or choose a suitable permitted arrangement. For a party above your online limit, select the tables you have arranged and explicitly confirm the seating and kitchen plan.
That large-party confirmation can override the normal kitchen arrival limit, but it does not remove table overlaps or the overall seating cap. The team must agree the practical arrangement first.
If you accept a pre-order booking with less than the configured notice, record the agreed kitchen exception. Record marketing permission only when the customer has explicitly agreed.
8. Seat a walk-in
- Choose Add Walk-in during the appropriate service.
- Enter the number of people and select the tables you are seating them at.
- Check that the selected arrangement is suitable, then choose Seat walk-in.
The walk-in occupies those tables from the current time for the configured dining duration. Overlapping reservations prevent the table from being selected. Contact details and guest emails are not required.
If a kitchen warning appears after the walk-in is seated, the record has already been saved. Coordinate with the kitchen rather than entering it again. Update its status when the visit is complete.
9. Deposits, pre-orders and seasonal events
Your venue settings determine the group threshold, deposit amount, pre-order notice and seasonal dates. Do not assume the example venue’s values apply to yours.
Record deposits taken by phone or in person by ticking Deposit received. Tick Meal pre-order received only after the team has checked the order. Deposits are records in this release; guest card collection is disabled.
A seasonal booking may remain Awaiting deposit while holding its tables and arrival capacity. It does not expire automatically. If the guest is not proceeding, cancel it to release the space.
One seasonal event type is supported. Keep its dates, menus and guest instructions current. Refunds, unpaid-booking expiry and SMS reminders are not automated.
10. Block a dining session
Use Block a dining session for a private event or a closure affecting the whole dining area. Choose the date, Lunch, Dinner or All day, and enter a clear reason.
If reservations already exist, Coverstead warns you and asks for acknowledgement. Existing bookings remain in the diary and guests are not automatically contacted or cancelled. Review them and make arrangements separately.
The block prevents new bookings for the whole selected service, rather than just a particular arrival time. Use Reopen session on its notice to accept bookings again.
11. Print service sheets
Choose Print service sheet, then select a date and Lunch, Dinner or both. Open the printable sheet and use the browser’s Print command. The layout is designed for A4.
The sheet includes all bookings for the selected service regardless of diary search filters, with service slots and room for notes. Cancelled bookings are excluded. Selecting both services produces separate sheets.
Private staff comments are included for the team. Keep printed sheets secure and dispose of them according to your venue’s data-handling policy; do not leave guest contact details on public display.
12. Customer records and consent
Open Customers & loyalty. Search by name, email or telephone, then open a profile to see contact details, notes, completed visits and booking history.
Marketing permission is separate from messages needed to manage a reservation. When granting email-offer permission, record when and how the customer agreed. Remove permission when it is withdrawn.
Use Add customer / paper record to add a contact or a completed visit from a paper diary. Supply an email address or telephone number so matching details can reuse a profile. Future bookings, cancellations and no-shows do not count as completed loyalty visits.
Owner/manager users can export permission-based email contacts. The export is not permission to contact everyone in the database; respect the saved consent and the purpose for which it was given.
13. Loyalty and CSV imports
A loyalty gift becomes available after ten qualifying completed visits within a rolling twelve months. Staff choose whether and when to issue it; no gift is sent automatically.
In the customer profile, choose a money-off or percentage gift, its value, terms and print or email delivery. Email delivery requires recorded permission and an email address. Issuing a gift uses ten qualifying visits. Vouchers are single-use and expire six months after issue; mark them redeemed when used.
For imports, download the CSV template, use one row per customer or completed visit, then choose Preview import. Correct flagged rows and check consent evidence before choosing Confirm import. Duplicate completed visits are skipped. An import preview by itself does not change customer records.
Import/export access depends on the staff role. Keep downloaded spreadsheets private and do not attach them to public GitHub issues.
14. Team access and reports
The optional Enterprise interface provides individual team accounts, service reports and an activity log. These modules are included in the MIT source; enabling the interface on a self-hosted installation is separate from purchasing managed hosting.
- Owner: venue configuration, team administration and operational tools.
- Manager: service work, reports, permitted imports/exports and the activity log.
- Staff: everyday booking and customer tasks, with restricted administration and export access.
Use a separate account per team member. Disable access when someone leaves; do not share the owner password. Disabling an account ends its access, including existing sessions.
Reports show reservations, covers, completed visits and no-shows across the stored records. The activity log helps identify who made changes; it is not a substitute for backups.
15. Keep the service dependable
Before service: review the diary, closures, large parties, dietary requests, deposits and outstanding pre-orders. Print the service sheet if the team uses one. Check that email delivery has been tested.
During service: add phone bookings and walk-ins promptly, update seated/completed statuses and check the kitchen before accepting exceptions.
After service: record cancellations and no-shows accurately, follow up on message failures and confirm the agreed backup routine has run.
If email fails, check sender configuration and SMTP with your operator before retrying the outbox. A retry may send previously queued messages. If you have restored an older backup, the operator must check for messages already delivered before restarting email.
Backups must include the database, venue assets and private configuration. Keep a protected copy off the server and rehearse recovery in a separate installation. Follow the backup instructions; do not copy an actively written database or delete its lock to make a second process start.
16. Frequently asked questions
Why is the booking page closed?
Complete owner and venue setup first. Then check opening/service times, booking notice and closures.
Why can’t I change a table or accept a booking?
Check future reservations, table combinations, dining duration, the seating cap and kitchen arrivals. The app protects existing commitments when settings change.
A booking succeeded, but no email arrived.
Check the reference and diary first. Email may still be queued, disabled or failing. Contact the venue/operator to verify delivery; do not submit a second booking just to obtain an email.
How do I reset a forgotten password?
Ask your installation operator. There is no self-service password recovery in this pilot. The operator can use the password-reset helper described in the installation guide.
Does the Stripe page collect guest deposits?
No. It is a separate, test-only rehearsal for Coverstead managed-service subscriptions. No live money is taken, and a test subscription does not create a hosted venue.
Where can I report a problem or suggest an improvement?
Use the GitHub issue templates with a synthetic example. Never include passwords, tokens or guest records. Report vulnerabilities through the repository’s private security reporting channel.
Where can developers find the source?
Coverstead on GitHub includes the source, MIT licence, contribution guide and roadmap.