Glossary

The language of readiness, defined.

The core concepts behind Standby, in plain terms. These are the product's universal vocabulary — the words mean the same thing in every organisation that runs it.

Operational readiness
The live answer to "who and what can respond right now" — the combination of available people, current qualifications and serviceable equipment. Standby's core job is to keep this answer true at all times, not just at audit time.
Readiness board
The single live view of a unit's readiness: who is available, whose currency is current, expiring or lapsed, and which equipment is grounded. It is not a report you run — it reflects the unit's state as it changes.
Currency
Whether a volunteer meets the training and hours a role requires, per qualification category. Currency is recomputed automatically from logged hours and expiry dates rather than tracked by hand.
Tri-state status
The status system that never changes between organisations: current (ready), expiring (action needed soon) and lapsed (no longer qualified). Lapsed currency is blocked from tasking, not merely flagged.
Availability
A volunteer's own declaration of whether they can be tasked — on-call, off-area or on leave — including recurring unavailability. Set from the mobile app and reflected on the readiness board the moment it changes.
Tasking
Assigning a volunteer or crew to a call-out or duty. Standby gates tasking on readiness so a volunteer with lapsed currency cannot be tasked.
Defect register
The live list of equipment faults with severity and status. When an asset is grounded by a defect, it appears on the readiness board next to crew readiness — not buried in a maintenance binder.
Inspection checklist
A structured check run against an asset, typically opened by scanning the asset's QR code in the field. Each inspection is retained in the asset's history.
Incident
A logged call-out with its roster, per-date attendance and hours, and any scene voice-notes. Incident hours feed both currency and allowance calculations.
Post-exercise report
The record filed after a training exercise. Once approved it writes a training record back to every attendee, updating the whole crew's currency from a single submission.
Approval chain
The route a decision (such as leave or a new qualification record) follows through the responsible roles, with decline and appeal paths. Decisions land in a single queue scoped to each approver's role.
Tenant
One organisation's isolated space in Standby — its own crest, units, sectors, roles and reference data. Data never crosses between tenants; the platform is multi-tenant with per-tenant access policies.
Role scope
What a person can see and do, decided by their membership role and enforced at the API. An officer sees their unit, a sector manager their sector, a national manager every unit.
Audit trail
The immutable log of every state change and record view, each stamped with actor and time. It is the evidence base for inspections and reviews.

See these ideas working on a live board.

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

Request a demo