Events App Starter · Industry version
Venue Event Template
Run your rooms, not just your events — spaces, private bookings, and function sheets in code your venue owns.
A venue's calendar is its inventory: the same room is a wedding Saturday, a corporate dinner Tuesday, and dark on Monday. This starter models spaces, private bookings, and the function sheets that make event nights run — generated into a codebase your venue owns and operates.
- 6 core entities
- No per-ticket fees
- Code you own
- Vibe + Governed modes
01 · The problem
Why a generic Events falls short
Ticketing platforms model events; venues sell rooms. The scarce resource is the space-date-daypart combination, and double-booking the ballroom is the catastrophic failure mode. A system where events float free of physical spaces can't even express the constraint, let alone enforce it while two coordinators quote the same Saturday.
Private events don't have ticket buyers — they have a client, a contract, and a balance schedule. A wedding books eighteen months out with a deposit, a headcount that moves four times, and a final payment due before load-in. Registration-shaped software has nowhere to put any of that.
And execution runs on the function sheet: the timeline, room setup, catering counts, AV needs, and staffing that the kitchen, floor, and vendors all work from. When that document lives outside the event system, every headcount change has to be re-communicated by hand — and the version in the kitchen is always one revision old.
02 · Data model
The data model, adapted
Everything in the base Events starter —
eventsticket_typesregistrationsattendeescheck_inspromo_codes— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
spaces | Bookable rooms and areas — capacity by layout, minimum spends, and availability that blocks conflicts. |
event_orders | The function sheet as data: timeline, setup, catering counts, AV, and staffing, versioned per event. |
client_contracts | The commercial spine — client, quoted amount, deposit schedule, payments received, balance due. |
03 · Screens
Modules through the industry lens
Space-aware event calendar
01The public side lists your open-ticket nights; the operational side is a grid of spaces and dates that makes conflicts impossible to save. A hold, an option, and a confirmed booking are distinct states, so the sales pipeline for a room is visible on the calendar itself.
Bookings that carry money
02Private bookings track deposit schedules, payments, and balances alongside guest counts, and the numbers roll into a revenue view by space and month. The awkward call about an unpaid balance happens two weeks out, not at load-in.
Check-in and the guest list
03Ticketed nights use the standard door screen; private events use client-supplied guest lists with plus-ones and table notes. Either way, the door works from the live list — including the change the client texted an hour before doors.
04 · In practice
Workflows it models
Inquiry to confirmed booking
01An inquiry becomes a tentative hold on a space and date, visible to every coordinator. The quote goes out from the contract record; the deposit confirms the hold; the calendar was never wrong at any step.
The Friday function-sheet run
02Every event in the next week publishes its current function sheet to kitchen, floor, and AV. A Tuesday headcount change versions the sheet and flags what changed — catering count up eight, one more high table — so nobody preps to stale numbers.
Month-end space performance
03Revenue by space, occupancy by day of week, average spend per event type — read from contracts and bookings you own. The case for turning Monday dark-nights into a comedy residency writes itself from your own data.
Venue Events template — frequently asked questions
Can it manage multiple rooms and prevent double-booking?
Yes — spaces are first-class, every booking claims a space and time, and conflicts are blocked at the data level. Holds and options appear on the same calendar, so sales and operations see one truth.
Does it handle private events as well as ticketed ones?
Both, as different shapes on the same tables: ticketed nights sell capacity through the public flow, private events run on contracts, deposits, and guest lists. Most venues run a mix, which is exactly why one owned system beats two subscriptions.
What about function sheets and event orders?
They're structured data, not attachments — timeline, setup, counts, AV, staffing — versioned per event and publishable to your teams. When the headcount moves, the sheet updates once and everyone reads the same revision.
We also take restaurant-style reservations — is that this?
Table reservations for service are a different rhythm and belong with your reservation flow — see the restaurant ordering starter. This starter owns functions, private hires, and ticketed nights; the two can share your customer data because you own both schemas.
Related
Dual7 App Starters
Build your Venue Events on your terms
Run your rooms, not just your events — spaces, private bookings, and function sheets in code your venue owns. Describe your version to start — the output is a project you own.