StandbyStandby
Sign inRequest a demo
How it works

The field keeps the board honest.

Standby closes the loop between what happens on the water and what an officer sees on screen — with no double entry in between. Three stages, one live picture.

01
In the field

The people doing the work update their own state

There is no coordinator re-typing what happened. A volunteer toggles on-call, logs the hours from a call-out, scans an asset's QR code to run its checklist, records a scene voice-note, or files a post-exercise report — all from the native app, between jobs, offline-tolerant.

  • Availability and leave, set from the phone
  • Incident hours and scene voice-notes at the scene
  • QR-scanned equipment inspections and defects
  • Post-exercise reports filed on the night
In the field
Crew A · ready●Current
Crew B · expiring●14 days
Crew C · blocked●Lapsed
02
In Standby

The picture recomputes itself — no double entry

Filed reports recalculate currency against each role's requirement. Approved leave, defect status and live call-outs flow onto the readiness board. Approvals route through the correct chain automatically, and every change lands in the audit trail with actor and time.

  • Currency recalculated from logged hours
  • Leave and availability reflected the instant they're approved
  • Approvals routed OIC → CUSM with decline and appeal
  • Every state change written to an immutable audit log
In Standby
Crew A · ready●Current
Crew B · expiring●14 days
Crew C · blocked●Lapsed
03
On the board

Officers task with confidence, in seconds

One glance shows who is ready, current and available. Expiring currency is amber before it bites; lapsed currency is blocked from tasking, not just flagged. The board is not a report you run — it is the live state of the unit.

  • Ready / expiring / lapsed at a glance, per volunteer
  • Lapsed currency is a hard gate on tasking
  • Equipment defects visible next to crew readiness
  • No refresh — the board is live
On the board
Crew A · ready●Current
Crew B · expiring●14 days
Crew C · blocked●Lapsed
Questions

Frequently asked

Does anyone have to re-enter what the field reports?

No. That's the point. A volunteer files once from the app; Standby recalculates currency, updates the board and routes approvals from that single entry. There is no coordinator re-typing returns into a spreadsheet.

What stops a volunteer with lapsed currency being tasked?

Lapsed currency is a hard gate, enforced in the platform — not a colour an officer might miss. Expiring qualifications show amber in advance so there's time to act before anyone is blocked.

Does it work without signal at the scene?

The native app is built for field use — voice-notes, hours and inspections are captured on the phone and sync when a connection returns.

How do approvals work?

Leave and availability decisions route through the correct chain for your organisation — for example OIC → CUSM — with decline and appeal paths. Each decision lands in a single queue scoped to your role, with in-app and push notifications.

Where does the data live?

Each organisation is an isolated tenant hosted in the EEA, encrypted at rest, aligned to ISO 27001 controls. See the Trust & security page for detail.

Watch the loop close on your own data.

A 30-minute walkthrough with your readiness model, units and currency rules.

Request a demo