Core · Video walkthrough

Find and compare nearby personnel and units on New Call

Use the actual Core dispatch lists to compare availability, ETA, position, staffing and scope.

Audience: Dispatchers and supervisors

Before you begin

Chapters

  1. Prepare a useful comparison
  2. Give the call a location
  3. Read the unit lists
  4. Separate response time from distance
  5. Read crew and role mix
  6. Inspect the position source
  7. Compare personnel separately
  8. Understand areas and scope
  9. Move the pin and compare again
  10. Make and verify the dispatch decision

Watch the walkthrough

Download video · Download captions

Step 1

Prepare a useful comparison

In the Chicago Fire demonstration department, we will compare Engine 51, Truck 81 and Reserve Engine 51. These are fictional training resources. Before opening a call, inspect each unit's type, station assignment and current status. A nearby unit in maintenance is different from an available unit. Check that station coordinates are correct and that crews have usable current assignments. This preparation makes the nearest list an operational comparison instead of a collection of unexplained distances.

Prepare a useful comparison: screen 1
Prepare a useful comparison · Screen 1
Prepare a useful comparison: screen 2
Prepare a useful comparison · Screen 2
Prepare a useful comparison: screen 3
Prepare a useful comparison · Screen 3

Practice

Compare Engine 51, Truck 81 and Reserve Engine 51: record their visible status, station and crew context.

Step 2

Give the call a location

Open New Call and enter a training name and nature. Choose the intended type and priority, then place a pin at the exercise location. You can enter latitude and longitude and use Set Pin On Map, or use the location tools your department makes visible. Confirm the pin represents the incident rather than a station or destination. Without a usable incident location, Resgrid cannot compare response distances. Wait for the lists to finish refreshing after the point changes.

Give the call a location: screen 1
Give the call a location · Screen 1
Give the call a location: screen 2
Give the call a location · Screen 2
Give the call a location: screen 3
Give the call a location · Screen 3

Practice

Set one clear incident pin and confirm the written coordinates describe the same point.

Step 3

Read the unit lists

Scroll to the unit dispatch lists. The Units tab compares the units you may dispatch. The Firehouse 51 tab shows our station resources. This training department has all six units assigned to that station. Read the current status alongside ETA and position. Nearest badges identify the first available resources with measurable distance in the ranked result. They do not certify equipment readiness or crew capability. Compare the named unit and its situation before ticking a recipient, even when it carries the first nearest badge.

Read the unit lists: screen 1
Read the unit lists · Screen 1
Read the unit lists: screen 2
Read the unit lists · Screen 2
Read the unit lists: screen 3
Read the unit lists · Screen 3

Practice

Explain why the first ranked available unit is or is not appropriate for your exercise.

Step 4

Separate response time from distance

The response comparison can include turnout as well as travel. In Call and Dispatch Settings, set In-quarters turnout to 120 seconds for this exercise, save, and reopen the page. Mobile turnout stays at zero. Return to New Call and set the training pin again. The unit rows now show an estimated two-minute response including 120 seconds of turnout. Here the origin is the station; this does not establish the unit's physical location. The distance measures separation from the incident. An estimated time uses an approximation, while a provider-derived drive time depends on the positions and route information available at that moment.

Separate response time from distance: screen 1
Separate response time from distance · Screen 1
Separate response time from distance: screen 2
Separate response time from distance · Screen 2
Separate response time from distance: screen 3
Separate response time from distance · Screen 3
Separate response time from distance: screen 4
Separate response time from distance · Screen 4

Practice

Compare the saved 120-second station allowance with the literal incl. 120 s turnout annotation, and explain why 0.0 km does not mean an instant response.

Step 5

Read crew and role mix

Inspect Shift Coverage and Role Mix as well as response time. Initially, our unit rows show No crew assigned. Open Units, then Unit Staffing. In this exercise, choose Christopher Herrmann for Engine 51's Officer or Team Lead seat, save, and reopen the page. Engine 51 now says Fully Staffed because its one configured seat is filled. That is not proof of a complete operational engine crew. Define the seats and qualification requirements your department actually needs. Return to New Call and refresh the incident comparison. Read the resulting crew and role mix rather than inferring them from group membership, a vehicle's seats or its nearest badge.

Read crew and role mix: screen 1
Read crew and role mix · Screen 1
Read crew and role mix: screen 2
Read crew and role mix · Screen 2
Read crew and role mix: screen 3
Read crew and role mix · Screen 3
Read crew and role mix: screen 4
Read crew and role mix · Screen 4
Read crew and role mix: screen 5
Read crew and role mix · Screen 5
Read crew and role mix: screen 6
Read crew and role mix · Screen 6
Read crew and role mix: screen 7
Read crew and role mix · Screen 7

Practice

Compare the one saved training seat with the resulting crew and role mix; distinguish configured staffing from your real operational minimum.

Step 6

Inspect the position source

Click Station location for Engine 51. The position panel compares its response origin with the call. Here Resgrid uses the station origin. That can happen for an In Quarters unit or when no usable GPS fix is available; it does not confirm the unit's physical whereabouts. Check the displayed source and any stale warning. If a location is hidden from you, distance and ETA can also be withheld. Do not fill that gap by assuming the unit is somewhere else on the map.

Inspect the position source: screen 1
Inspect the position source · Screen 1

Practice

Describe the visible position source and freshness for one suggested unit.

Step 7

Compare personnel separately

Open Personnel and inspect the same response context for Christopher Herrmann, our fictional officer. Personnel have their own status and staffing information. The positions in this exercise are simulated training fixes. Read any stale label before relying on an estimate. A person can be close to the incident without being available for assignment, and an available person may have no usable position. A unit assignment gives useful crew context, but it does not establish that this person shares the unit's position. Read the actual row rather than transferring a unit's ranking to every crew member or assuming a role name proves current qualification.

Compare personnel separately: screen 1
Compare personnel separately · Screen 1
Compare personnel separately: screen 2
Compare personnel separately · Screen 2

Practice

Compare a person and a unit without treating their availability or positions as interchangeable.

Step 8

Understand areas and scope

Open Call and Dispatch Settings and review Group-Scoped Dispatch. Response area boundaries describe which area contains an incident. The Group Boundary editor under Stations and Groups is where those areas are drawn. Our New Call comparison reports that the incident is not inside any group boundary. We will inspect the controls without saving a boundary. Dispatch scope controls the candidates used for nearest comparisons. These are separate settings. This demonstration uses a department administrator with department-wide scope. A unit can remain in the dispatch list without a nearest comparison, so a missing estimate does not establish that the unit is unavailable. When a comparison is missing, check the permitted scope, current status, and usable position before deciding what resources are available. We will return to New Call without changing permissions.

Understand areas and scope: screen 1
Understand areas and scope · Screen 1
Understand areas and scope: screen 2
Understand areas and scope · Screen 2
Understand areas and scope: screen 3
Understand areas and scope · Screen 3
Understand areas and scope: screen 4
Understand areas and scope · Screen 4

Practice

Identify whether the current operator has department-wide comparison scope, and distinguish a missing estimate from an unavailable unit.

Step 9

Move the pin and compare again

Move the incident pin to a second training location and wait for the refreshed response values. Compare the same named units and personnel before and after the move. Engine 51's distance changes from less than a tenth of a kilometer to 98.8 kilometers, while its estimate rises from two to 195 minutes. These are straight-line estimates, not a routed drive time. A change in distance or turnout-adjusted time may change the order. Check that the labels and pin still describe the intended exercise. The system can retain the view you manually chose, so use the visible coordinates and final list values as evidence instead of expecting every refresh to zoom the map automatically. In this station-based example, several units share an origin, so their distances can change together without changing their order.

Move the pin and compare again: screen 1
Move the pin and compare again · Screen 1
Move the pin and compare again: screen 2
Move the pin and compare again · Screen 2
Move the pin and compare again: screen 3
Move the pin and compare again · Screen 3
Move the pin and compare again: screen 4
Move the pin and compare again · Screen 4

Practice

Record how one named resource changes between two incident locations.

Step 10

Make and verify the dispatch decision

Return the incident pin to the original near training location and wait for the values to refresh. Select the resources that fit the exercise. Here we choose Christopher Herrmann, the first nearby officer, and Engine 51. Engine 51 is third in the overall list, but it is the available engine; the reserve engine is out of service. Check that the unit selection agrees across its station and Units tabs. If a run card also suggests resources, inspect that panel and the final checkboxes together. Ranking does not send anyone by itself. Before saving, review the call, recipients and notification arrangements. After the training save, open the resulting call, 26-4 in this example, and its Dispatched tab. Check Engine 51 and Christopher Herrmann against the intended recipients. This proves the saved assignment; it does not establish that a device received an alert. Confirm member receipt separately. Finish by closing only the training call with Send Notification off, and keep its history. Keep the location source, freshness and estimated-time limits in your decision, even when the first-ranked choice appears obvious. The same review helps a mobile crisis team choose an available clinician, a search and rescue team find a nearby qualified member, or a security supervisor compare patrols. Wildland contractors and industrial teams should also compare crew capability and access to the incident before choosing the first-ranked resource.

Make and verify the dispatch decision: screen 1
Make and verify the dispatch decision · Screen 1
Make and verify the dispatch decision: screen 2
Make and verify the dispatch decision · Screen 2
Make and verify the dispatch decision: screen 3
Make and verify the dispatch decision · Screen 3
Make and verify the dispatch decision: screen 4
Make and verify the dispatch decision · Screen 4
Make and verify the dispatch decision: screen 5
Make and verify the dispatch decision · Screen 5
Make and verify the dispatch decision: screen 6
Make and verify the dispatch decision · Screen 6
Make and verify the dispatch decision: screen 7
Make and verify the dispatch decision · Screen 7
Make and verify the dispatch decision: screen 8
Make and verify the dispatch decision · Screen 8
Make and verify the dispatch decision: screen 9
Make and verify the dispatch decision · Screen 9

Practice

Make one justified selection and compare the saved call list with your intended recipients.

Examples for your department

Fire / EMS
Chicago Fire training: compare a station engine and mobile rescue using response time and current crew context.
Community response
Mobile crisis teams: compare clinicians by actual availability, permitted location and operational role.
Search and rescue
Search and rescue: inspect stale remote positions and staging origin before selecting a team.
Security
Security: compare patrol locations within site and supervisor dispatch scope.
Wildland
Wildland contractors: include turnout and remote travel limits when comparing crew units.
Industrial
Industrial response: check facility access, equipment status and qualified role mix alongside proximity.

Transcript

Download transcript
Read the complete transcript
Find and compare nearby personnel and units on New Call
Audience: Dispatchers and supervisors

Prepare a useful comparison
In the Chicago Fire demonstration department, we will compare Engine 51, Truck 81 and Reserve Engine 51. These are fictional training resources. Before opening a call, inspect each unit's type, station assignment and current status. A nearby unit in maintenance is different from an available unit. Check that station coordinates are correct and that crews have usable current assignments. This preparation makes the nearest list an operational comparison instead of a collection of unexplained distances.
Practice: Compare Engine 51, Truck 81 and Reserve Engine 51: record their visible status, station and crew context.

Give the call a location
Open New Call and enter a training name and nature. Choose the intended type and priority, then place a pin at the exercise location. You can enter latitude and longitude and use Set Pin On Map, or use the location tools your department makes visible. Confirm the pin represents the incident rather than a station or destination. Without a usable incident location, Resgrid cannot compare response distances. Wait for the lists to finish refreshing after the point changes.
Practice: Set one clear incident pin and confirm the written coordinates describe the same point.

Read the unit lists
Scroll to the unit dispatch lists. The Units tab compares the units you may dispatch. The Firehouse 51 tab shows our station resources. This training department has all six units assigned to that station. Read the current status alongside ETA and position. Nearest badges identify the first available resources with measurable distance in the ranked result. They do not certify equipment readiness or crew capability. Compare the named unit and its situation before ticking a recipient, even when it carries the first nearest badge.
Practice: Explain why the first ranked available unit is or is not appropriate for your exercise.

Separate response time from distance
The response comparison can include turnout as well as travel. In Call and Dispatch Settings, set In-quarters turnout to 120 seconds for this exercise, save, and reopen the page. Mobile turnout stays at zero. Return to New Call and set the training pin again. The unit rows now show an estimated two-minute response including 120 seconds of turnout. Here the origin is the station; this does not establish the unit's physical location. The distance measures separation from the incident. An estimated time uses an approximation, while a provider-derived drive time depends on the positions and route information available at that moment.
Practice: Compare the saved 120-second station allowance with the literal incl. 120 s turnout annotation, and explain why 0.0 km does not mean an instant response.

Read crew and role mix
Inspect Shift Coverage and Role Mix as well as response time. Initially, our unit rows show No crew assigned. Open Units, then Unit Staffing. In this exercise, choose Christopher Herrmann for Engine 51's Officer or Team Lead seat, save, and reopen the page. Engine 51 now says Fully Staffed because its one configured seat is filled. That is not proof of a complete operational engine crew. Define the seats and qualification requirements your department actually needs. Return to New Call and refresh the incident comparison. Read the resulting crew and role mix rather than inferring them from group membership, a vehicle's seats or its nearest badge.
Practice: Compare the one saved training seat with the resulting crew and role mix; distinguish configured staffing from your real operational minimum.

Inspect the position source
Click Station location for Engine 51. The position panel compares its response origin with the call. Here Resgrid uses the station origin. That can happen for an In Quarters unit or when no usable GPS fix is available; it does not confirm the unit's physical whereabouts. Check the displayed source and any stale warning. If a location is hidden from you, distance and ETA can also be withheld. Do not fill that gap by assuming the unit is somewhere else on the map.
Practice: Describe the visible position source and freshness for one suggested unit.

Compare personnel separately
Open Personnel and inspect the same response context for Christopher Herrmann, our fictional officer. Personnel have their own status and staffing information. The positions in this exercise are simulated training fixes. Read any stale label before relying on an estimate. A person can be close to the incident without being available for assignment, and an available person may have no usable position. A unit assignment gives useful crew context, but it does not establish that this person shares the unit's position. Read the actual row rather than transferring a unit's ranking to every crew member or assuming a role name proves current qualification.
Practice: Compare a person and a unit without treating their availability or positions as interchangeable.

Understand areas and scope
Open Call and Dispatch Settings and review Group-Scoped Dispatch. Response area boundaries describe which area contains an incident. The Group Boundary editor under Stations and Groups is where those areas are drawn. Our New Call comparison reports that the incident is not inside any group boundary. We will inspect the controls without saving a boundary. Dispatch scope controls the candidates used for nearest comparisons. These are separate settings. This demonstration uses a department administrator with department-wide scope. A unit can remain in the dispatch list without a nearest comparison, so a missing estimate does not establish that the unit is unavailable. When a comparison is missing, check the permitted scope, current status, and usable position before deciding what resources are available. We will return to New Call without changing permissions.
Practice: Identify whether the current operator has department-wide comparison scope, and distinguish a missing estimate from an unavailable unit.

Move the pin and compare again
Move the incident pin to a second training location and wait for the refreshed response values. Compare the same named units and personnel before and after the move. Engine 51's distance changes from less than a tenth of a kilometer to 98.8 kilometers, while its estimate rises from two to 195 minutes. These are straight-line estimates, not a routed drive time. A change in distance or turnout-adjusted time may change the order. Check that the labels and pin still describe the intended exercise. The system can retain the view you manually chose, so use the visible coordinates and final list values as evidence instead of expecting every refresh to zoom the map automatically. In this station-based example, several units share an origin, so their distances can change together without changing their order.
Practice: Record how one named resource changes between two incident locations.

Make and verify the dispatch decision
Return the incident pin to the original near training location and wait for the values to refresh. Select the resources that fit the exercise. Here we choose Christopher Herrmann, the first nearby officer, and Engine 51. Engine 51 is third in the overall list, but it is the available engine; the reserve engine is out of service. Check that the unit selection agrees across its station and Units tabs. If a run card also suggests resources, inspect that panel and the final checkboxes together. Ranking does not send anyone by itself. Before saving, review the call, recipients and notification arrangements. After the training save, open the resulting call, 26-4 in this example, and its Dispatched tab. Check Engine 51 and Christopher Herrmann against the intended recipients. This proves the saved assignment; it does not establish that a device received an alert. Confirm member receipt separately. Finish by closing only the training call with Send Notification off, and keep its history. Keep the location source, freshness and estimated-time limits in your decision, even when the first-ranked choice appears obvious. The same review helps a mobile crisis team choose an available clinician, a search and rescue team find a nearby qualified member, or a security supervisor compare patrols. Wildland contractors and industrial teams should also compare crew capability and access to the incident before choosing the first-ranked resource.
Practice: Make one justified selection and compare the saved call list with your intended recipients.

Examples for your department
Fire / EMS: Chicago Fire training: compare a station engine and mobile rescue using response time and current crew context.
Community response: Mobile crisis teams: compare clinicians by actual availability, permitted location and operational role.
Search and rescue: Search and rescue: inspect stale remote positions and staging origin before selecting a team.
Security: Security: compare patrol locations within site and supervisor dispatch scope.
Wildland: Wildland contractors: include turnout and remote travel limits when comparing crew units.
Industrial: Industrial response: check facility access, equipment status and qualified role mix alongside proximity.