Department example
Resgrid: from the first alert to the next shift
Use a fictional fire or EMS department for this exercise. 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.
Explore this topic →Department example
Build a roster dispatch can use
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Invite one sample member, assign a station and role, and have that member sign in. Track unaccepted invitations. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Configure a department and protect access
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Complete Setup Wizard, save on each owning screen, then Verify again. Keep unknown checks visible and assign follow-up owners. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Represent apparatus, crews, and GPS devices
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Create Engine 1 in the demo department and verify the assigned crew from the dispatcher view. Measure incomplete unit records. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Put the right Resgrid app on each device
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Use a sample member, unit tablet, dispatcher, and station display to follow the same training incident. Record which devices complete the test. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Take an incident from intake to closeout
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Create a Medical training call for Station 1. Confirm the location, recipients, status transitions, closeout, and archived record. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Make alerts reach the intended audience
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Send only to the demo audience. Record recipients, observed receipts, failures, and follow-up actions; compare with the expected audience. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Make location information useful and current
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Follow a sample unit and compare a recent position with a stale position. Record missing POIs and outdated reference layers. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Plan coverage and keep dispatch aligned
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Schedule a weekend duty crew, change one assignment, and verify the expected roster. Track unfilled slots and unresolved trades. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Assign learning and track qualifications
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Assign a refresher to the demo group and complete it as a member. Review overdue learning and certifications approaching renewal. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Give members a dependable reference library
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Find the hospital contact and current procedure as a sample member. Track outdated material and items without a responsible owner. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Record routine checks and missed work
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Complete a daily Engine 1 check and leave a second demo check overdue. Confirm that the compliance view distinguishes both. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Turn defects into accountable repairs
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Track a demo pump-test defect through assignment, repair, review, and documented return to service. Measure unresolved work-order age. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Know what is available, issued, and expiring
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Receive ten demo supplies, transfer two, and issue one durable item. Reconcile the resulting balances and inspect expiry alerts. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Keep incident and prevention records reviewable
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Prepare one complete training incident report and one incomplete draft. Use the work queue to assign corrections and compare analytics scope. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Keep deployment activity and cost evidence together
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Record a two-day demo strike-team deployment and reconcile the participating people and units with the supporting documents. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Connect service activity to costs and billing
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Prepare a standby estimate and draft invoice from sample activity. Compare recorded cost with the billed amount and explain any difference. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Automate a repeatable task with visible outcomes
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Create a demo-only new-call workflow and inspect its run. Record successful and failed execution evidence, owner, and recovery steps. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Set up voice channels for team coordination
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Run a two-device training-channel check and record which members can transmit and receive. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Plan protected-data access and recovery
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Document who owns enrollment, key recovery, and disclosure review. Use only synthetic protected content for the recording. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Match subscription capacity to the roster
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Compare current counts with a proposed roster expansion. Document headroom and optional add-ons without purchasing anything. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Understand AI availability and human review
Use a fictional fire or EMS department for this exercise. Your practice task is simple. Ask a configuration question through an available tool, inspect its evidence, and identify any unknowns before making a change. Record the result, who owns the follow-up, and when it should be reviewed.
Explore this topic →Department example
Relay: bring an audio dispatch feed into Resgrid
Use a fictional fire or EMS department for this exercise. Retain the synthetic audio fixture, selected release, approved configuration, and observed test result. Use the supported Relay application and an audio test setup to verify the workflow.
Explore this topic →Department example
Self-hosting: configuration and operating responsibilities
Use a fictional fire or EMS department for this exercise. Choose the deployment layout you will verify: Linux Compose, Windows, Kubernetes or k3s, or an Incident Command Kit. Record the supported release and verify installation, endpoint connectivity, backup, and recovery in that environment. Use the linked official guides for the matching layout.
Explore this topic →No examples match your search.