Skip to main content

Web Application

Comprehensive documentation for all features and operations available in the Resgrid web application User Area.

📄️ Run Cards & Automatic Dispatch

A run card is a pre-planned response package: "for a high-priority structure fire in District 1 send two engines, a truck, a rescue and a chief; on the second alarm add a tender and a brush unit." Resgrid matches every new call against your run cards by priority and call type, works out which specific units and people should go — by station response area or by closest available unit — and either dispatches them automatically or pre-populates the New Call page for the dispatcher to confirm. Optional move-up / backfill recommendations keep station coverage intact.

📄️ Custom Statuses

Custom statuses replace the built-in status words with your own. There are three sets: personnel statuses (Responding, On scene, Available at station …), staffing levels (Available, On duty, Off duty, Light duty …) and unit statuses per unit type (En route, On scene, Transporting, Out of service …). Each status has a colour, whether it needs a destination (a station or a call), what it counts as (responding / available), and how it looks on the apps and the Big Board.

📄️ Workflows

Workflows are Resgrid's automation engine: when X happens, do Y. Pick a trigger (a call is created, a unit goes out of service, a record is finalized, a checklist fails, a work order is overdue, a form is submitted …), add optional conditions, and chain actions — send an email or SMS, post to Slack/Teams/Discord, call a webhook or REST API, upload a file, create a call, attach a Records export. Templates use the event's data, credentials are stored encrypted, and every run is logged with retries and a health view.

📄️ Advanced Data Protection

Advanced Data Protection encrypts the sensitive content of your department's data — call names, natures, notes and addresses; call notes and attachments; contact details; member sensitive data; and the protected fields of Records, Checklists, Work Orders and Inventory — with keys owned by your department and held in a hardened key service. Once enrolled, protected values stay hidden until a signed-in member confirms who they are with a second factor, and they remain encrypted in exports, notifications and reports.