Resgrid: from the first alert to the next shift
Audience: All department roles

Ready for the next call
Welcome to Resgrid Academy. Resgrid brings dispatch, people, apparatus, and department management into a connected system. This series explains what each feature does, how to prepare it, and how to tell whether it is helping your department.

One incident. A connected workflow.
Picture a fictional department with two stations, an engine, and a rescue unit. First, administrators organize members, groups, roles, and units. A dispatcher creates a training call and selects the intended resources. Members respond through their assigned devices. After closeout, officers complete records and follow up on equipment, supplies, and staffing.

Build the foundation
Start with the foundation. Set the department address and time zone. Build the roster, home stations, personnel roles, and unit types. Review who can dispatch, manage information, and administer the department. Prepare account recovery as you set up stronger sign-in protections. These choices influence later schedules, recipients, maps, and reports.

Coordinate the response
For operations, learn call intake, types, priorities, recipient routing, run cards, and response statuses. Mapping adds location and site context. Messaging and notification rules keep the intended audience informed. Verify communications on actual devices. A saved call or provider handoff is different from confirmed receipt by a member.

Keep the department ready
Between calls, shifts help plan coverage. Training and certification records make learning and renewal work visible. Checklists record routine inspections. Maintenance gives defects an owner and a documented repair process. Inventory records where equipment and supplies are stored, issued, and replenished. Documents, contacts, protocols, and calendars give members a shared reference point.

Make the back office reviewable
Records connect incident reporting, prevention, investigation, evidence, review, and disclosure. Deployments keep extended response activity and supporting documents together. Business Operations adds commercial and costing workflows where enabled. Teach the source activity, review decisions, and recorded outcomes together, rather than treating an export or prepared claim as a completed external submission.

Availability is part of configuration
Feature availability depends on the deployed release and department access. Some features need an enabled module, a permission, an add-on, or protection enrollment. The source catalog marks Enhanced AI as planned. Buying an add-on is separate from configuring it. Setup Report helps review configuration evidence; it does not prove that every operational workflow or notification has succeeded.

Learn by doing
Choose the learning path that matches your responsibility: administrator, dispatcher, member, or specialist. Each chapter explains a department problem, the relevant features, setup decisions, and a practice task.

Examples for your department
Community paramedicine and mental health response: Choose the appropriate EMS or mobile-crisis operating pack and review visit coverage and notification setup.
Search and rescue: Choose Search and rescue, then review mapping, training, inventory and deployments.
Security companies and departments: Choose Security and facilities, then review site groups, patrol staffing and activity records.
Wildland contractors: Use the Fire context with Contract workforce mix; review seasonal crews and deployment dates.
Industrial emergency response teams: Choose Industrial response and applicable HazMat context; review facility groups, equipment and qualifications.