Persistent unit identities
Alpha / Bravo / Charlie / Delta unit slots survive between bookings.
OVERWATCH CAMPAIGNCOMMAND THE EVENT.
COMMAND THE EVENT.
KEEP THE HISTORY.
Overwatch Campaign connects bookings, persistent callsigns, SENSE, transparent scoring, command views, approved sensors and post-event media into one campaign state.
CAMPAIGN STATEALPHA 1-0Persistent unit slot8–10 player rosterTeam history retainedEvent score + objective recordAuthorised comms roles
Players change. The unit history can remain.
Every point has a reason
Objective, intel, logistics, territory and rule events are recorded transparently.
Need-to-know interfaces
Player, Team Lead, Faction Command, Marshal and Overwatch views.
Observation assets
Record approved game observations and asset state rather than claiming automated identification of people.
Game-state inputs
Objective, checkpoint and event sensors can feed controlled status changes.
Role-based channels
Team and authorised command access are configured per event.
Return to your callsign — or go back into the pool.
Campaign units such as Alpha 1-0, Alpha 2-0 and Bravo 1-0 remain persistent even when the player roster changes. Returning players can be offered their previous unit first; unused places return to the event booking pool.
8–10 player team
The callsign carries the campaign history, score and event record.
First refusal
Eligible returning members can choose to retain the same unit at the next event.
Fill remaining places
Vacancies can be made available to new players without resetting the unit history.
Every point should have a recorded reason.
Mission completion
Capture, recovery, protection and scenario objectives.
Information found or verified
Game intelligence and organiser-defined discovery events.
Resupply and asset tasks
Campaign-defined logistics, recovery and support actions.
Zone and control state
Time-bounded control events when used by the scenario.
Rule-linked deductions
Only recorded when the organiser's published scoring rules support them.
Who changed what and why
Score changes retain timestamp, event, reason and authorised operator.
Plan. Configure. Equip. Dispatch. Run.
The managed deployment model uses the planning period to configure software and reusable hardware for the first event. The box can include Starlink or other approved connectivity, command devices, field tablets, power, sensors and optional media modules. Every deployed device should have a unique asset ID, assigned event, configuration state, check-out record and return/check condition. Hardware capability remains market-by-market.
PAY / PLANCONFIGURETESTDISPATCHRUN / RETURN
Starlink / approved network
Configured for the event where coverage, local rules and support allow.
Preconfigured tablets / laptops
Asset-labelled and assigned to defined command or marshal roles.
Game-state inputs
Objective and checkpoint devices feed authorised event-state changes.
Local-record cameras
Static, 360 and approved player capture modules with return/ingest workflow.
Charging and field continuity
Power planning is part of the event configuration, not an afterthought.
Check-in, wipe, reconfigure
Reusable hardware is checked, reconciled and prepared for the next deployment.
Return the kit. Turn the event into the campaign that sells the next one.
Static and 360 cameras, approved player cameras, compatible digital-NVG recordings and drone footage can record locally. After return, media is ingested, time-synchronised and indexed against event markers so AI-assisted editorial workflows can propose films, reels, sponsor edits and website media for human approval.
Full quality stays on device
Connectivity is not relied on for continuous full-resolution upload.
One event timeline
Camera IDs and time markers align footage with campaign events.
Human-approved outputs
Reels, highlights, event films, captions and campaign promotion.
One campaign. Multiple formats.
Compressed arc
Core story beats and decisive missions.
Expanded campaign
More role continuity, intelligence, scoring and faction development.
Persistent season
Longer-running campaign state with team history and recurring content.
Record locally. Build the story afterwards.
RECORDRETURNINGEST + SYNCAI-ASSISTED EDITHUMAN APPROVAL
Static/360 cameras, approved player cameras, compatible digital-NVG recordings and drone footage can be indexed against event markers before films, reels and website media are prepared for the organiser.