The command layer
for field operations.
FieldOps is a single operational layer that reconciles everything happening in the field — signals, people, shifts, patrols, incidents, evidence — against the operation as it was planned. It is built to be the authoritative system of record for operators that cannot afford ambiguity.
live operations
- SBS IVA
Three layers.
One operational surface.
FieldOps is structured as three distinct layers of operational control. Each one is independently useful — together they form the command picture.
Structured capture from the field
Voice-first reports in any language, photo and video evidence, GPS traces, checkpoint acknowledgements, alarm streams and external integrations — all captured in a consistent, time-attributed, tamper-evident format. No more free-form logs, no more reconciliation.
Your SOPs, codified and enforced
Shift plans, patrol routes, incident escalations, handover rules and client SLAs are expressed as explicit protocols. The platform enforces them — and surfaces drift the moment behaviour diverges from plan.
Decision-grade picture, in real time
The command view is the authoritative operational picture: what is happening, where it is drifting, who owns it, and what the system is about to do next. Designed for dispatch, supervision and management — not marketing.
From field signal
to command decision.
Median latency · 38 seconds
A free-form voice report does not end as text. Within the same loop it becomes an owner, an SLA timer, a piece of attributable evidence and an audit record — closed inside the shift that opened it, visible to the manager accountable for the site and, where contracted, to the client on the other end.
Five roles.
Five surfaces. One system of record.
Each role sees the operation at the level of detail it needs — and no more. The underlying record is the same.
Guard
Mobile field app. Voice reports, checkpoint scanning, task acknowledgement, photo evidence, shift sign-on.
Day-to-day actions
- Report incident — voice, photo and GPS
- Scan checkpoint — NFC, QR or GPS
- Confirm task with evidence on close
- Attach photo or note to an open record
- Start, hand over and end shift
Supervisor
Live coverage, handovers, exception queue, patrol verification, task assignment across a site or area.
Day-to-day actions
- Verify handover between outgoing and incoming shift
- Resolve absence, lateness or no-show
- Approve swap requests with audit trail
- Assign corrective task on open exception
- Sign off on incident close
Dispatcher
Incoming signal triage, routing, escalation decisions, communication with guards, alarm handling.
Day-to-day actions
- Triage inbound alarm, call or guard report
- Escalate event by protocol and owner
- Re-route response across sites or units
- Track unresolved queue against SLA
- Coordinate voice comms with field
Manager
Multi-site command view, SLA and drift oversight, operational reviews, protocol tuning, compliance reporting.
Day-to-day actions
- Compare sites on drift, load and incident mix
- Review drift inbox and coverage exceptions
- Export audit pack for client, insurer or authority
- Tune protocol, thresholds and SLA rules
- Generate monthly operational review pack
Client
Scoped, read-only visibility into activity, incidents and evidence on their sites. Same truth, fewer privileges.
Day-to-day actions
- View live activity on contracted sites
- Review patrol completion and deviation
- Access evidence with access-audit trail
- Confirm SLA performance against contract
- Escalate an event into operator dispatch
A category cluttered with
the wrong analogies.
Field operations is not a guard-tracking app, not a report form with AI on top, not a dashboard, not a seat-licensed productivity suite. Four negations to remove the common misreads.
Not a guard-tracking toy
Attribution without protocol is surveillance. We track people only because actions, evidence and accountability need an owner — not to measure presence.
Not a reporting form with AI on top
Structure without operational consequence is paperwork. A report that does not trigger a task, an escalation or an evidence record is not an operational artefact.
Not a dashboard disconnected from operations
Visibility without authority is a status page. The command view exists so decisions can be made against it — not so that numbers can be watched.
Not a seat-licensed productivity suite
This is infrastructure, not a tool. It replaces the gap between supervisor memory, WhatsApp threads and Excel reconciliation — not a document editor.
The operation and its record are the same thing.
Everything else is recollection.
Principles the system refuses
to compromise on.
Reality before report
Nothing enters the system of record unless it is grounded in an actual field event. Free-form narrative is not a substitute for structured evidence.
Protocol over improvisation
Every operational action corresponds to a protocol. Deviation is allowed, but explicit, justified and attributable — never invisible.
Attribution by default
Every record is tied to a person, a shift, a site and a moment. Reconstructing what happened is the default state, not a forensics exercise.
One truth across layers
Guard, supervisor, manager and client operate against the same record, scoped differently and never duplicated.
Speed at the edge
The field app works offline, on low-end devices, in cold, rain and gloves. Command latency is measured end-to-end — not inside a datacentre.
Built for the field,
not the datacentre.
Remote sites, weak coverage and harsh conditions cannot wait for a perfect connection. FieldOps captures at the edge and reconciles when the link returns — so the operation does not stop when the network does. It is the difference that decides whether a system of record survives a real deployment in the field, far from a datacentre.
Works offline, reconciles on return
Voice reports, checkpoints, tasks and evidence are captured with no connection and sync automatically when the device is back in coverage. Nothing is lost at the edge.
Runs on the hardware guards already carry
Designed for low-end devices and used in cold, rain and gloves — not a flagship phone, not a dedicated terminal.
Latency measured end-to-end
Command latency is measured from the field to the command layer and back — not inside a datacentre. The number that matters is the one the operator feels.
The operation outlasts the connection
For remote sites and multi-region operations where connectivity is not a given, the record stays continuous — a coverage gap becomes a sync detail, not an operational blackout.
What this means in
day-to-day operation.
Principles describe the system. These are the changes operators feel during an ordinary shift.
Fewer silent handover failures
Instructions become tracked tasks with an owner and a deadline — not sentences repeated at shift change and forgotten by the next one.
Shorter time from signal to accountable action
Between field event and named owner executing a protocol there is a timer — not a phone tree. Reports are already structured when the shift ends.
Reduced protocol drift between shifts
Missed checkpoint, stretched cadence or skipped route is flagged while it can still be corrected — protocol variance is visible across shifts and sites, not discovered at audit.
Client-visible auditability without manual collation
No PDFs, no reconciled dashboards — a scoped view into the same operational truth, in real time, with access audit. Monthly reporting stops being a task.
Less manager dependence on supervisor memory
Exceptions surface themselves. The operation stops living in people's heads and starts living on the record — management runs against evidence, not recollection.
FieldOps core remains
the command layer.
Around it, operators deploy additional operational surfaces — shaped by the contract, the site and the operational envelope. Not features, not modules. Extensions of the same record.
Ops & command augmentation
Surfaces the command layer leans on when the operation is running hot — signal intake, routing, review.
- OPS Hub — central dispatch and operational picture
- Alarm and response intake
- Exception routing and escalation
- Operational review surfaces
- Audit and log visibility
Protocol & field guidance
Keeps the guard, supervisor and dispatcher inside protocol without depending on memory or improvisation.
- SOP library — versioned, scoped per site and role
- SOP chatbot — protocol lookup in the moment
- WhatsApp field agent for structured exchanges
- Role-guided workflows across shift surfaces
Site operations
Reception-facing and site-level flows that live alongside the command layer on a typical contract.
- Visitor flow and access record
- Tenant records and building-level context
- Parcel and mail intake with tenant notification
- Key control — issuance, return, chain of custody
- Reception-facing operational flows
The core command layer does not change with scope. These surfaces are deployed where the contract requires them — and operate against the same record, under the same ownership model, with the same audit trail.
Connected into the systems
the site already runs on.
FieldOps does not replace every system around the operation. It becomes the command layer between them — calendars, inboxes, voice paths, courier flows already carrying operational signal on site.
Microsoft ecosystem
For operators whose coordination already runs through Microsoft on the site or at the client.
- Microsoft 365 — document and workflow context
- Teams — internal object communication and escalation
- Outlook — monitored shared inboxes and site mail flows
- Calendars — task, shift and service coordination
- Identity (Entra) where scope and access require it
Google ecosystem
Where site operations and client reporting live inside Google Workspace instead.
- Gmail — monitored site and shared inboxes
- Google Calendar — shift, patrol and service scheduling
- Drive / Docs in workflow context where operationally used
Communication layer
Structured voice and message paths when the operation requires direct, logged escalation.
- Twilio — two-way voice and messaging
- Structured outbound and inbound communication
- Voice escalation flows with logged exchange
- Message escalation where response time is measured
Parcel & logistics
Where parcel handling is part of site operations — reception, tenant mail, outbound shipping.
- DHL — labels and shipping workflows
- UPS — parcel intake and outbound handling
- FedEx — courier exchanges tied to the site record
Connected systems extend the record. They do not replace it. Integrations are deployed after the core protocol holds, and operate as controlled extensions of the command layer — never as first-layer dependencies.
One record,
four domains on it.
All capabilities →
See the system run against your reality.
We begin with your operation — then show where FieldOps reduces the gap between plan and field.