System
Venue and event management system
An enquiry, a held date, a signed contract, a delivered event.
A venue's operational risk is concentrated in two places: the calendar and the handover. A date held on someone's phone and a run sheet that lives in a WhatsApp thread are how a wedding and a corporate dinner end up on the same Saturday.
The system makes availability authoritative — a hold is a record with an expiry, not a promise — and carries the event from enquiry through contract to the run sheet the floor team works from on the night.
- Core model
- Enquiry · Hold · Booking · Event · Invoice
- Availability
- Per space, with holds that expire
- Conflicts
- Setup and breakdown time counted as occupancy
- Quoting
- Packages, per-head pricing, and add-ons
- Contracts
- Generated from the quote, with deposit tracking
- Staffing
- Shift planning against the event schedule
- Run sheet
- Timed schedule for the floor team, on a phone
- Settlement
- Deposits, balances, extras, and final invoice
- Deployment
- Cloud, with mobile access on the floor
How it runs
Every stage, in order.
Each stage produces something the next one needs. Where a stage can fail, it fails visibly rather than passing bad data forward.
- 01
Enquire
An enquiry captures the date, space, and headcount, and checks availability immediately.
- 02
Hold
A hold is a record with an owner and an expiry, so provisional dates release themselves.
- 03
Contract
The quote becomes the contract becomes the invoice schedule, without re-entry at any step.
- 04
Plan
Staffing, suppliers, and equipment are allocated against the event, and conflicts surface early.
- 05
Deliver
The floor team works from a timed run sheet on a phone and captures extras as they happen.
- 06
Settle
Extras from the night flow into the final invoice while the event is still fresh.
Scope
In detail.
Modules
14- Enquiry capture and pipeline
- Space availability and expiring holds
- Quotations and package pricing
- Contracts, e-signature, and deposits
- Event brief and requirements
- Menu, bar, and dietary requirements
- Supplier and vendor coordination
- Staff rostering against events
- Equipment and inventory allocation
- Run sheet and timings
- On-the-night extras capture
- Final settlement and invoicing
- Post-event feedback
- Occupancy and revenue reporting
Deliverables
What you get.
Written into the scope document before work starts, and used as the acceptance test when it finishes.
- 01Configured system covering the spaces and packages in scope
- 02Import of the existing forward booking calendar
- 03Quote and contract templates in your branding
- 04Team training for sales and operations
- 05Documentation and handover
- 06Support agreement with a defined response time
Questions
Asked before.
Can it stop double bookings?
That is the point of the availability model. Setup and breakdown count as occupancy, and a hold is an explicit record with an expiry rather than an informal promise.
We run several spaces that combine. Does that work?
Yes. Spaces can be composed, so booking the combined room correctly blocks its components.
Does the floor team need laptops?
No. Run sheets and extras capture are built for a phone held in one hand during service.
Also in Systems
Schools
Admissions, attendance, timetabling, fees, examinations, and parent communication in one system, modelled on how the school actually runs.
SystemProduction
Order-to-dispatch tracking for production operations — batches, machines, wastage, stock, and dispatch — built for a factory floor rather than an office.
Next step
Scope it before you commit to it.
The first step is a short written scope: fields, volume, schedule, delivery, and acceptance criteria. It is quick, it is concrete, and it tells you whether this is worth doing at all.