Features

Everything a venue runs on, by job

Every feature is included at every venue. What is listed here is in the product today.

Keep the building running

One register of what the venue is made of, and the work that keeps it working.

Buildings, floors and spaces: Build the venue by clicking: buildings, floors and the spaces on them, with a plan per level and a measured scale so areas can be computed.
Asset register: Plant, services and fabric, sorted by criticality with statutory items first. Criticality carries a review date and a written rationale.
Planned maintenance: Task definitions written once and applied to many assets, banded by the SFG20 criticality scale, from a shared task library each venue can add to.
Work orders: Completed is not closed: the technician completes, the supervisor accepts. Every state change is written to a history the database keeps, and a work order cannot be deleted.
Cleaning: Routine cleaning plus the turnarounds the diary implies between one booking and the next. Cleaning specs can scale with the size of the room.
Drawing register: The DWG and DXF set, with revisions, kept as controlled documents.

Know what is due, what has lapsed, and who signed it off.

Statutory compliance register: Obligations for the venue’s jurisdiction, each with a default interval that can be overridden with a written reason. Every certificate is kept, newest first.
Corrective actions: One list whether the action came from an inspection, an incident, a certificate or an audit. Closing one needs a named verifier.
Inspections: Walk-rounds against a template, answered item by item so an interrupted inspection is not lost. A show-stop failure raises an urgent corrective action.
Risk register: Hazards grouped by category, each with an owner and controls. The score is calculated from likelihood and severity, and accepting a risk needs a named person.
Standards library: The statutory regimes the product knows, the injury-reporting rules per jurisdiction, and the capacity methods, quoted rather than summarised.

Four gates, checked in order, and a permit that is refused when one fails.

Approved contractors: Pre-qualification with insurance held as a date, so “are they insured” is answered for today.
Method statements: Risk assessments and method statements accepted for a specific task and a specific contractor.
Site inductions: Per person, per site. Every named worker on a permit is checked against a current induction covering the whole permit window.
Permits to work: Issued only when the first three gates pass; otherwise refused with the failing gate named. Permit types carry a maximum duration and a fire-watch period, and a suspended permit records why.

One log, kept as a log, with the medical side behind its own lock.

Incident log: Safety, security, medical, crowd and near-miss in one log. Incidents cannot be deleted; an entry made in error is closed with an explanation.
Casualty records: Anyone who can log an incident can record a casualty. Reading the casualty’s identity and clinical notes needs a dedicated permission and a re-entered password, and every look is logged.
Statutory injury reports: Where Venuesta knows the jurisdiction’s injury-reporting regime, the report names the authority and the filing deadline.

Safe capacity with the working shown, and who is on site right now.

Safe capacity: Holding, entry, exit and emergency evacuation capacities calculated separately, the lowest one named as binding, with every component stored. Approval is a separate, named act.
Published against safe: The commercial capacity chart side by side with the safety calculation, per space and layout.
Crowd plans: Per event, with stewarding positions and the safety officer’s name. Occupancy is counted in and out, with where each reading came from.
Security operations: Zones drawn over the venue’s own spaces, security posts, a key register, and patrol routes walked checkpoint by checkpoint with the time taken when each is reached.
On site now: Who has signed in and not signed out: the fire roll call. Sign-ins cannot be deleted, only signed out.
Lost property: A reference and a retention date on the way in; a return needs a named claimant, and retention rules apply per category.

From the first enquiry to the order the kitchen works from.

Function diary: Ranked provisional holds and definite bookings, with get-in and get-out shown as part of the occupied window, and an “is this space free?” check over the same window.
Enquiries: Every enquiry carries its source, and one cannot be marked lost without a reason.
Rate cards: Separate cards for separate markets, with rate lines that carry day-of-week loading.
Event orders: The document that turns a sale into delivery, versioned, with lines split by category: setup, catering, AV, staffing, security and cleaning.
Event workspace: Per event: the venue’s private brief, a handover log between duty managers, the incident log, permits, inspections, lost property and cleaning for that event.

The facts a buyer asks for, kept once.

Venue profile: Identity, location, spaces and a capacity chart per layout, with features and amenities from one shared vocabulary.
Photos and plans: Attached space by space. A published photo must carry alt text; the database refuses one without.
Brand kit: The venue’s marks, colours and usage rules, with retired assets kept and marked as replaced.
Listing preview: See how your venue reads as a listing, including the schema.org EventVenue data generated from the same records.

Several venues, one operator, one set of roles.

Portfolio views: Compliance across every venue, worst first; utilisation; and a quarterly board pack against the quarter before. Money is never summed across currencies.
Roles and permissions: Template roles are read-only; clone one to make your own. Sensitive areas such as incidents, security and rates each need their own permission to read.
Invitations: Invite a colleague with the role they will hold; they accept with a link and arrive with it.
Tasks, people and activity: Tasks assigned across the team, a roster of everyone inducted or signed in, and a feed of who changed what.
Nine languages: The interface and the manual in English, Czech, German, Spanish, French, Hungarian, Polish, Romanian and Slovak. Light, dark or system theme.

Start a free trial, or book a demo and we will walk you through it with your own venue in mind.