The platform

Eight modules. One live readiness picture.

Standby is one operational system, not a folder of tools. Every module writes to the same readiness board — so what the field does shows up where officers decide, without re-keying.

What is Standby?

Standby is an operational readiness platform for volunteer emergency services — coastguard, lifeboat, mountain and cliff rescue, flood response and retained fire crews. It brings availability, training currency, equipment status and incidents into one live readiness board an officer-in-charge can read at a glance. Volunteers update their own state from a native mobile app; Standby recalculates currency, routes approvals and reflects it on the board with no double entry — and lapsed currency is blocked from tasking, not just flagged.

Who it's for: Volunteer emergency and rescue services
What it replaces: Spreadsheets, group chats and paper currency logs
Modules: 8, under one login
Currency model: Tri-state per category — current, expiring, lapsed
Platforms: Web console + native iOS/Android app
Hosting: Per-tenant, EEA, ISO 27001-aligned

Availability & leave Training, qualifications & currency Equipment & defects Incidents & payments Exercises & events Reporting & analytics Approvals & notifications Audit & access control

Availability & leave

Who can be tasked — the moment it changes

Every volunteer sets their own on-call state and books leave from their phone. Recurring unavailability (a weekly shift, a standing commitment) is set once. The readiness board reflects the change instantly — no message to a coordinator, no waiting for a spreadsheet to be updated.

On-call / off-area toggles that write straight to the duty board
Recurring unavailability patterns set once, applied every week
Leave requests routed OIC → CUSM, with decline and appeal
An outbound webhook keeps an external alerting system in sync

Availability & leave · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Training, qualifications & currency

Tri-state currency, recomputed as hours are logged

Each qualification category carries a status — current, expiring or lapsed — against the hours and expiry its role requires. When a report is filed, currency recalculates automatically. A training officer approves new records in a dedicated queue, and lapsed currency is blocked from tasking, not merely flagged.

Per-category currency: shore, afloat, cliff, drone and more
Expiry and required-hours tracked against each role's standard
Training-officer approval queue for new qualification records
Lapsed currency blocks tasking at the source — a hard gate

Training, qualifications & currency · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Equipment & defects

A grounded asset shows on the board, not in a binder

Every asset carries a QR code. Scan it in the field to run the inspection checklist, log a reading, or raise a defect. The full inspection history stays with the asset, and a live defect register means a grounded piece of kit is visible to officers immediately — the same place they read crew readiness.

Asset register with QR-scanned inspection checklists
Complete inspection history retained per asset
Live defect register with severity and status
Maintenance schedules that surface what's due

Equipment & defects · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Incidents & payments

From call-out roster to allowance run

Log a call-out, roster who attended, capture per-date hours and record scene voice-notes from the phone. Two independent approvals — one for attendance, one for payment — keep the audit clean and feed both currency and allowance calculations without re-keying.

Call-out roster with per-date attendance and hours
Scene voice-notes captured on the native app
Separate attendance and payment approvals
Hours flow into currency and allowance runs automatically

Incidents & payments · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Exercises & events

Volunteer-raised exercises, approved records for everyone

Volunteers propose Additional CGU exercises; officers approve and mark them complete. A post-exercise report then writes an approved training record back to every attendee — so a single evening on the water updates the whole crew's currency at once.

Volunteers raise Additional CGU exercises for approval
Officer approval and completion in one queue
Post-exercise reports write records to every attendee
Attendee currency updates from a single filed report

Exercises & events · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Reporting & analytics

The numbers your audit and your board both need

Incident analytics break down by status and month. Pre-defined reports — user activity, defects, compliance — are one click to CSV. When an inspection or funding review lands, the paperwork is a download, not three weeks of chasing across units that each do it differently.

Incident analytics by status and by month
Pre-defined user-activity, defect and compliance reports
One-click CSV export on every report
Consistent figures across every unit and sector

Reporting & analytics · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Approvals & notifications

One queue for every decision your role owns

Leave and availability decisions that need your role land in a single queue. As records move through the chain, in-app and native push notifications keep everyone informed — no chasing, no decisions lost in a thread.

A single queue scoped to your role's decisions
In-app and native push notifications on state changes
Full decision chain with decline and appeal paths
Nothing waits in someone's inbox or a group chat

Approvals & notifications · sample view

Ready to task●Current

Cert expiring●14 days

Blocked from tasking●Lapsed

Audit & access control

Every change logged, every view scoped

Membership roles scope every view and action, enforced at the API by per-tenant policies — not merely hidden in the UI. Multi-factor sign-in sits on top of single sign-on, and an immutable audit trail records every state change and record view with actor and timestamp.