Imran Khan Open the demo

TableKeep

Restaurant reservations and dining-room operations in one workflow.

Guests reserve a table in a few taps. Staff manage reservations, walk-ins, phone bookings, and table assignments from one dashboard.

TableKeep is shown through Lantern & Oak, a fictional restaurant.

Open the demo

Sample. Made-up restaurant. The dining room, menu, guests, and bookings are sample content.

The problem

An independent dining room often runs on phone calls, a handwritten list, and whoever is standing at the host stand.

The guest has to call to learn whether a time is open. The person who answers has to remember the party size, the table, and the note. A walk-in and a web request do not land in the same place. The room and the list drift apart.

The goal

A guest should reserve without calling. Staff should see the room as it is right now: who is coming, who is seated, and which table is free.

A reservation from the website, a phone call, and a walk-in should move through the same list. The workflow is for one independent restaurant, not a chain.

The guest experience

The guest site is the front door. The steps are party size, day, time, name and phone, then a confirmation code the host can look up.

Guest homepage where a reservation starts, for the fictional restaurant used to demonstrate TableKeep.
A guest starts a reservation from the homepage.
Party size step of a reservation, with sizes from 1 to 8.
The guest chooses a party size. Parties of 9 or more are asked to call.
Date step with open days selectable and closed days still visible.
Open days are selectable. Closed days remain visible and cannot be booked.
Time step with lunch and dinner openings in 15-minute steps.
Times come from open tables, listed for lunch and dinner in 15-minute steps.
Guest details step with a sample name and a 555 phone number.
The guest gives a name and a phone number. Email and a note are optional.
Confirmation for a sample guest, party of 2, with a confirmation code.
Confirmation shows the party, time, and code given to the host.

The owner experience

The dashboard is where the dining room is run. Today shows booked covers, who is seated, and who is still to arrive. Each reservation can be seated, cancelled, or marked as a no-show.

A phone booking and a walk-in are entered on that same page, so they join the list instead of living on a notepad. The full list can be searched by name, phone, or code.

The calendar places those reservations on tables across the day. Opening one reservation shows the confirmation code, the party, and the assigned table.

Today view of booked covers, seated guests, and reservations still to arrive.
Today shows booked covers, who is seated, and who is still to arrive. A reservation can be seated, cancelled, or marked as a no-show.
Phone booking and walk-in entry in the same dashboard workflow.
Phone bookings and walk-ins enter the same workflow. A walk-in can be seated at a free table immediately.
Searchable list of sample reservations with confirmation codes.
Reservations can be searched by guest, phone number, or confirmation code.
Day calendar with reservations placed on tables across the hours.
The calendar shows reservations on tables throughout the day.
One sample reservation with its confirmation code, party size, and assigned table.
Opening a reservation shows the code, the party, and the table. The host can seat the party, move the table, or cancel.

What was built

For guests

  • Homepage
  • Menu, about, gallery, and contact
  • Reservation flow and confirmation code

For the dining room

  • Today dashboard
  • Reservation management
  • Calendar
  • Table assignment
  • Walk-in seating
  • Phone booking

What this demonstrates

A workflow, from the guest’s first tap to the host’s list.

A database-backed reservation system, a business dashboard, and the administrative screens that keep a dining room in order. The guest site and the dashboard are both responsive web applications.

Honest disclosure

TableKeep is demonstrated through Lantern & Oak. The restaurant is fictional. The guests, reservations, tables, and dining-room data on these screens are sample content.

This page does not report customer results, reviews, or business outcomes. Lantern & Oak is not a client.

Interested in a system like this?

TableKeep is a sample project, but the workflow demonstrates the kinds of systems I build for local businesses.

Start a Project