When a static post is covering a hazard site, accident scene, natural disaster, or other active emergency, the job stops being just guard coverage. Critical Sites adds a dedicated incident UI for command, live map coordination, gate control, tracked assets, company access, and export-ready documentation.
A standard static post handles presence, deterrence, access control, and incident response. Critical Sites is what you add when that same property becomes a command problem: multiple gates, multiple vendors, moving hazards, tracked equipment, live announcements, linked reports, and stakeholders who need the same operational picture.
FRO-trained security personnel can isolate affected areas, deny entry, and support chemical spills, hazmat staging, contamination zones, damaged storage, and defensive scene operations with live boundaries, notes, and exportable history.
Vehicle collisions, loading-yard incidents, industrial mishaps, and other scenes where gates, escorts, evidence, and activity logs all matter.
Rail yards, derailments, damaged rail infrastructure, railcar recovery, controlled contractor access, and changing equipment locations that require one shared operational picture.
Storm damage, flooding, wind events, wildfire-adjacent operations, or any property emergency that needs real-time coordination and clear access control.
Fires, utility failures, security incidents, evacuations, and other fast-moving events where a dedicated command board reduces confusion and speeds decisions.
The Critical Sites board is built around the real workflows shown in the Full Sail product and demo environment: live map coordination, linked incident reporting, service-company control, gate logging, role-based access, and export-ready scene history.
Draw boundaries, mark hazards, define ground-zero zones, tag gates, and attach image-backed notes that stay tied to the site record.
See clocked-in officer positions on the site map when coverage is active, so command can understand who is where without chasing updates across separate tools.
Track gate rules, arrivals, exits, escort notes, and changing access instructions as the site evolves minute by minute.
Keep response gear, sealed storage, monitoring equipment, and other site-critical assets tied to location, status, and note history.
Record railcar photographs, GPS coordinates, timestamps, condition, risk level, and field notes from a mobile device. AI-assisted OCR extracts the reporting mark for officer review, while later observations update the same railcar record instead of creating duplicates.
Maintain the approved company list, role, gate assignment, and access restrictions for cleanup crews, waste haulers, monitoring teams, and other vendors.
Generate reviewable exports that consolidate site summary, map state, incident history, assets, gate activity, finance, and the export audit into one artifact.
Critical Sites is a premium add-on for qualifying clients and situations. Standard static post service covers officer presence, reporting, patrol coordination, and portal visibility. Critical Sites adds a dedicated operational UI with more moving parts, more structured control, more documentation surfaces, and more stakeholders.
The live workflow is simple in concept: create the site, coordinate the scene, and preserve the record. What matters is that everyone who should see the same operational picture can work from the same board.
Create the Critical Site with the owner, linked post, incident type, status, location, and the first operational notes. The board exists first, then better information can be added as it arrives.
Use live map layers, announcements, linked reports, company access, gate events, and tracked assets to manage the scene without scattering information across texts, calls, and spreadsheets.
When leadership, insurance, counsel, or an agency needs the record, the system can package site context, timeline, map state, assets, gate activity, and billing into a reviewable export.
Critical Sites is built for real client-side visibility, but it still respects operational boundaries. Access is role-based, exports are auditable, and scene data is shown only to the people who should have it.
Publish site updates, tie Special Incident Reports back to the Critical Site, and keep the event timeline coherent instead of fragmented.
Owners, approved reviewers, and other invited users inherit only the visibility they need, including map, communications, finance, or export rights.
Labor, equipment, materials, and packet-prep costs can remain tied to the same site record so the operational and financial story stay aligned.
We can help you decide whether this should be planned into a standing coverage model or activated for special-risk events and emergency situations only.
Important: Critical Sites Command is sold separately from standard static post coverage.
Quoting depends on site complexity, users, workflow needs, duration, and whether you want it available as a standing capability.