Top Table, what it is
A seating planner for a wedding. The user is the couple, or a planner working for them.
The journey
| # | Step | Screen |
|---|---|---|
| 1 | Land on an empty setup screen | Setup |
| 2 | Import a scenario, or set the room up by hand | Setup |
| 3 | Check the capacity maths. Adjust tables if needed | Setup |
| 4 | Review the guest list. Add, edit or remove people | Guests |
| 5 | Move to the plan | Plan |
| 6 | Place the guests that matter. Placing pins them | Plan |
| 7 | Auto-allocate. Fills every empty seat around the pins | Plan |
| 8 | Read the violations | Plan |
| 9 | Adjust a placement, re-run, repeat | Plan |
Pinning is the idea the product turns on
You know the best man sits next to the groom and nan needs to be near a door. You do not care where the rest go.
Placing someone by hand pins them, and auto-allocate works around the pins rather than over them. The tool is not replacing judgement, it is doing the boring ninety percent around the decisions already made.
The room
Three numbers: round tables, seats each, top table seats. Total seats is
roundTables × seatsEach + topTableSeats.
Seats may exceed guests. Seats may fall short of guests, which is a warning and never a block. A plan can never seat more people than there are seats.
Everything is local
No accounts, no server, no sharing. Data lives in the browser and a scenario import replaces it.
Being hosted does not change that. The site is a file copy with nothing behind it, so two people opening the same URL get two empty, unrelated browsers. KB-7 has the shape of it.
Not in the MVP
Drag and drop. Undo. Catering output. Export, print, sharing, accounts.
These are on the board under TT-23, TT-25 and TT-31 to TT-34. Do not build ahead of them.
Every rule on KB-2 is in scope, at the severity KB-2 gives it. Auto-allocate satisfies the hard ones. The soft ones are surfaced for a person to decide on and are never auto-resolved.