Copy or create the setup
Take roles, locations, shifts, briefings, run sheets and templates from a previous event, or build them fresh.
CrewOps
Shifts, briefings, run sheets, incidents and equipment in one operational layer — with a personal staff hub so every team member sees only what concerns them.
In short
Shift planning, check-ins and time tracking
Incident command with escalation and SLAs
Ops analytics and post-event review
Capabilities
- 01
Shift planning
Create, assign and manage shifts in a calendar view, backed by reusable shift templates and crew availability reporting.
- 02
Crew profiles
Skills, certificates, qualifications, preferences and tags per person, so the right people end up on the right posts.
- 03
Briefings & run sheets
Versioned briefing documents with target audiences and mandatory acknowledgement, plus structured run sheets with time slots and live status.
- 04
Incident command
A dedicated command centre with its own queue, an extended status model, escalation levels, response and resolution SLAs, command notes, evidence links and automatic timeline logging.
- 05
Equipment & automations
Asset tracking with condition logs and check-out/return, plus rule-based triggers that fire on shift start or check-in.
- 06
Staff hub
A personal dashboard per team member: self check-in and check-out, my shifts, my tasks, announcements, briefings to acknowledge and personal timesheets.
How it works
01 02 Assign the crew
Match availability and crew profiles to shifts, then publish the plan to the staff hub.
03 Brief and run
Publish briefings for acknowledgement, work the run sheet live and handle incidents from the command centre.
04 Review
Read the ops analytics snapshot, the incident heatmap and the lessons-learned block before the next event.
CrewOps
Ops analytics reports fill rate, no-show rate, punctuality, average check-in deviation, planned versus actual hours, briefing confirmation rate, run-sheet punctuality and task resolution rate — with incident heatmaps, worked-hours breakdowns and a lessons-learned block derived from the KPI thresholds.
Specifications
- Planning
- Shifts with calendar view, templates, availability and crew profiles
- Incident statuses
- OPEN, ACKNOWLEDGED, IN_PROGRESS, MONITORING, RESOLVED, CLOSED
- Communication
- Announcements with priority and pinning, daily log, handover notes
- Collaboration
- WebSocket presence, cursor tracking and locking during concurrent edits
- Permissions
- Dedicated OPS_* permissions per area, including view and manage splits
Use cases
Festivals — Learn more
Hundreds of shifts across stages, gates and camping, with handovers between day and night crews.
Stadium matchdays — Learn more
A repeatable setup copied from the previous fixture, with incident command for the ninety minutes that matter.
Conferences — Learn more
Room-by-room run sheets, briefed hosts and a clean record of who confirmed what.
FAQ
- Yes. Roles, locations, shifts, briefings, run sheets and shift templates can be copied from an earlier event, so a recurring operation is configured once rather than every time.
- Incidents carry escalation levels and response and resolution SLAs, with an automatic response-due time and critical auto-follow-up tasks. Status changes and critical escalations write timeline entries automatically.
- The staff hub is a personal dashboard: self check-in and check-out, assigned and upcoming shifts, assigned tasks with a status they can advance, pinned announcements, briefings to acknowledge and their own timesheet entries.
- Yes. Every CrewOps area is governed by dedicated OPS_* permissions with separate view and manage rights, and each staff hub section checks them individually.
Plan the shifts, publish the briefing and give every team member their own view.