Platform
Everything behind your events,
in one system.
VenueCommand connects the work behind each event: bookings and the calendar, contracts, payments and deposits, event-day modules and staff, and the people on your team.
Illustrative example. The event shown is fictional.
01
Bookings and calendar
The challenge
Holds, tentative dates and confirmed events end up in different places, and it’s easy to double-book a space when the details are spread out.
In VenueCommand
- Events across one or more spaces, with categories and linked contacts.
- Load-in and load-out times kept separate from the event window.
- A clear status for every event: Hold, Confirmed, Completed or Cancelled.
- Conflict checks for each space. Overriding a conflict requires a written reason.
- Holds with expiry dates and reminder emails. Expired holds are released automatically, and you get a nudge when a hold is ready to confirm.
- A calendar by space in month, week, agenda and list views.
- Copy Event to rebook a repeat client, plus an iCal feed and .ics downloads.
The result
Your team works from one calendar, holds don’t linger past their expiry, and a conflict needs a stated reason before an event goes ahead.
See how your bookings would look in VenueCommand.
We’ll walk through holds, conflicts and the calendar with your spaces in mind.
02
Contracts
The challenge
Contract wording drifts between versions, details change after a contract goes out, and signed copies end up scattered across email threads and folders.
In VenueCommand
- Rental Agreement PDFs generated from your venue’s own versioned template.
- An approval step for contract wording.
- Terms and pricing are frozen when a contract is issued. When details change, use Reissue.
- Signed copies stored on the event.
The result
Each event carries the contract that was actually issued, on wording your team approved, with the signed copy alongside it.
03
Payments and deposits
The challenge
Pricing, payments, refunds and damage deposits are hard to keep straight when they’re recorded somewhere other than the event.
In VenueCommand
- A service catalog and line items, with a tax rate for each venue.
- Rental packages priced flat or hourly, by weekday and time of day.
- Nonprofit pricing.
- A payments ledger with refunds, voids and an audit trail.
- Damage deposits tracked from collection through settlement.
The result
The price of each event, every payment recorded against it and the status of its damage deposit sit together on the event.
04
Event-day modules and staff
The challenge
Bar, catering and security each bring their own details, and the people working the event need the right information in front of them.
In VenueCommand
- Optional Bar, Catering and Security modules, turned on for each venue.
- Bar staffing, bar totals and an OK-to-bill lock.
- A catering checklist of the documents you need to collect.
- Security modes: none, in-house or outsourced.
- A staff pool with positions, shared across your venues.
- Event documents with versions and per-role visibility.
The result
Each venue uses only the modules it needs, and event-day details live on the event instead of in separate notes.
05
Team and roles
The challenge
Not everyone on the team needs the same access, and bringing in a new person shouldn’t mean sharing a login.
In VenueCommand
- Owner, Manager, Staff and Read-only roles.
- Email invitations to add people to your organization.
- Event documents visible by role.
- Strict data separation between organizations.
- Built-in help.
The result
Each person joins with their own invitation and role, and your organization’s data stays separate from every other organization’s.
Take command
Spend less time chasing details. More time running your venue.
See how VenueCommand could fit the way your team manages events, people and properties.