Skip to main content

Setting Up Resgrid for Your Organization

Resgrid started as computer-aided dispatch for fire departments, but the same building blocks — calls, people, units, groups, statuses, schedules, records, checklists, inventory, maps and notifications — configure into very different organizations. These guides give you a recipe for each kind, with concrete values to enter, which modules to switch on or off, and which mobile app each person should use.

Every guide assumes you have already created your department (hosted at resgrid.com or self-hosted) and are signed in as its administrator. The generic, screen-by-screen walk-through is in How-tos → Setup department; the guides below tell you what to put in.

Pick the guide closest to you

OrganizationGuideTypical modules
Volunteer, combination or career fire departmentFire departmentDispatch, run cards, personnel/units, shifts, checklists, work orders, inventory, Records + NERIS, prevention
Ambulance service, fire-based EMS, community paramedicineEMS agencyDispatch, units, shifts, checklists (narcotics), inventory (lots/expiry), records, ADP
Search and rescue team, mountain / cave / swiftwater / K9Search & rescueDispatch to roles, mapping & custom maps, routes, records (SAR pack), calendar, inventory
County / city emergency management, EOCEmergency managementCalls as activations, groups per section/ESF, records (EOC pack, ICS forms), weather alerts, links, resource orders
Incident management team, wildland / all-hazardsIncident management teamCommand definitions, records (ICS 201–225, OF/SF forms), deployments, IC app
CERT / community response / auxiliaryCERT & community responsePersonnel, calendar, trainings, messages, records (CERT pack), simple dispatch
Private security, campus / healthcare security, facilitiesSecurity & facilitiesCalls by client site, custom statuses, patrol routes, indoor maps, records (patrol log / incident report), checklists
Industrial fire brigade, plant emergency response teamIndustrial emergency responseDispatch, units, hazmat protocols, checklists, work orders with safety holds, inventory (serialized), records (industrial pack), indoor maps
Delivery, courier, field service, bus / transit operatorDelivery, transit & field serviceUnits as vehicles, routes, calls as jobs, records (delivery run / route EOD), hardware GPS tracking
Central dispatch centre serving several agenciesMulti-agency dispatch centreDepartment links, resource orders, run cards, Dispatch app, Big Board

The order that works for everyone

Whatever the guide, this order avoids rework:

  1. Department settings — name, time zone, address, map centre, 24-hour time.
  2. Types — unit types, call types, call priorities, certification types (guides list them).
  3. Groups & stations — the physical places first, organisational groups second; draw geofences.
  4. Roles — what you dispatch by and report on.
  5. Custom statuses — from a template; adjust wording.
  6. Units — with unit roles (seats).
  7. Personnel — invite in bulk; ask everyone to verify email and phone and install the app.
  8. Security & permissions — tighten what the defaults leave open (delete calls, view PII).
  9. Dispatch settings — how groups/units/shifts dispatch; email/SMS import; run cards.
  10. Everything else — records, checklists, inventory, shifts, calendar, workflows, notifications — one module at a time, with a champion for each.

Which app for whom

AppWho uses it
ResponderEvery member: receive calls, set status and staffing, chat, checklists, records in the field.
UnitThe apparatus / vehicle / team tablet: unit status, crew, AVL, checklists, unit records.
DispatchDispatchers and duty officers: create and manage calls, see everything.
Incident CommandIncident commanders: command boards, accountability, incident channels, ICS records.
Big BoardStation and EOC wall displays.

Getting help

The support portal, the community Discord and GitHub issues are linked under Help in the web app.