WEBVTT

00:00:00.070 --> 00:00:04.170
Resgrid Dispatch brings calls, units, personnel, the map,

00:00:04.309 --> 00:00:06.190
and notes into one console.

00:00:06.610 --> 00:00:10.130
This walkthrough is for dispatchers and other authorized coordinators

00:00:10.130 --> 00:00:13.689
who need to find the right resource and maintain its recorded state.

00:00:14.100 --> 00:00:17.889
We use a fictional firehouse, but the same console pattern can support

00:00:17.889 --> 00:00:22.709
community response teams, search and rescue, security operations, wildland

00:00:22.709 --> 00:00:25.229
contractors, and industrial response.

00:00:25.360 --> 00:00:28.949
Start in the call panel and enter Community in its search field.

00:00:29.350 --> 00:00:32.410
The list now shows the fictional community medical standby.

00:00:33.039 --> 00:00:36.920
Notice that the top summary still reports three active calls while

00:00:36.920 --> 00:00:38.500
the searched panel shows one.

00:00:38.939 --> 00:00:42.419
Search helps find an incident in the list; check the incident

00:00:42.419 --> 00:00:43.849
name before selecting it.

00:00:44.080 --> 00:00:45.820
Select the intended call card.

00:00:46.300 --> 00:00:51.599
The blue Filtering by call banner identifies DEMO-0002, and the

00:00:51.599 --> 00:00:55.540
resource panels now say Units on Call and Personnel on Call.

00:00:55.989 --> 00:00:58.170
Call Notes is also scoped to that incident.

00:00:58.649 --> 00:01:00.510
Read this banner before acting.

00:01:00.930 --> 00:01:03.860
An On Call assignment label and the resource status are

00:01:03.860 --> 00:01:05.590
separate pieces of information.

00:01:05.759 --> 00:01:08.650
Use Clear Filter to leave the incident context.

00:01:09.000 --> 00:01:11.560
The banner is gone and the resource headings return to

00:01:11.560 --> 00:01:13.740
Units, Personnel, and Notes.

00:01:14.119 --> 00:01:18.110
Community is still in the call search field, so that panel remains narrowed.

00:01:18.480 --> 00:01:21.449
Clear its search separately when you want the full call list.

00:01:21.790 --> 00:01:25.409
This distinction helps explain why a panel can still look filtered

00:01:25.450 --> 00:01:26.870
after leaving an incident.

00:01:26.989 --> 00:01:31.079
With the call search cleared, turn on Available only at the top.

00:01:31.599 --> 00:01:36.270
In this recorded example, the unit panel contains four units instead of six.

00:01:36.720 --> 00:01:39.319
Engine 51 is listed as Available.

00:01:39.810 --> 00:01:43.289
Read the resulting list and its count when filtering resources.

00:01:43.710 --> 00:01:47.640
A recorded availability value still needs to be interpreted using your

00:01:47.640 --> 00:01:49.599
organization’s dispatch procedure.

00:01:49.709 --> 00:01:54.129
Turn Available only off, then enter Engine in the unit search.

00:01:54.480 --> 00:01:59.509
Two matches are visible: Engine 51, marked Available, and Reserve

00:01:59.560 --> 00:02:02.060
Engine 51, marked Out of Service.

00:02:02.480 --> 00:02:04.900
Check the full unit name and displayed state.

00:02:05.270 --> 00:02:08.960
Similar names make it especially useful to select from the unit panel

00:02:08.960 --> 00:02:13.370
deliberately and verify the selected resource before submitting an update.

00:02:13.519 --> 00:02:16.170
Select Engine 51 in the unit panel.

00:02:16.650 --> 00:02:21.300
Its Actions area now identifies Engine 51 and exposes Status,

00:02:21.500 --> 00:02:23.269
Select Status, and Note.

00:02:23.629 --> 00:02:26.019
Check that identity before entering an update.

00:02:26.580 --> 00:02:28.349
This is the unit action form.

00:02:28.759 --> 00:02:32.120
Leave unrelated fields alone when the task only requires a

00:02:32.120 --> 00:02:33.940
status and its supporting note.

00:02:34.119 --> 00:02:35.589
Open Select Status.

00:02:35.999 --> 00:02:41.599
The displayed choices include Responding, Available, Committed, and On Scene.

00:02:42.060 --> 00:02:46.229
The chooser also describes their destination support: Responding shows

00:02:46.229 --> 00:02:51.209
Call destination, while Available shows Station destination in this department.

00:02:51.649 --> 00:02:54.139
Choose the state that matches the intended action.

00:02:54.510 --> 00:02:57.350
For this software exercise, we choose Available.

00:02:57.590 --> 00:03:00.379
Open Destination and review the current selection.

00:03:00.809 --> 00:03:02.519
No Destination is selected.

00:03:02.969 --> 00:03:07.749
The Stations section contains rows named No Station and Firehouse 51.

00:03:08.219 --> 00:03:12.259
A row named No Station and the separate No Destination choice are

00:03:12.259 --> 00:03:14.169
distinct entries in this example.

00:03:14.489 --> 00:03:17.019
We retain No Destination for the exercise.

00:03:17.440 --> 00:03:21.079
Check the selected destination before sending any status update.

00:03:21.330 --> 00:03:27.029
Review the prepared values: Engine 51, Available, and No Destination.

00:03:27.430 --> 00:03:31.389
The note says Training only, Dispatch status practice.

00:03:31.819 --> 00:03:36.279
Once the intended resource and values are correct, choose Update Status.

00:03:36.759 --> 00:03:40.140
The note provides context for this fictional software exercise.

00:03:40.480 --> 00:03:44.099
For actual operations, enter the information your organization

00:03:44.099 --> 00:03:45.870
requires for the status change.

00:03:46.059 --> 00:03:50.699
After submission, the Activity Log reports Unit status updated, and

00:03:50.869 --> 00:03:53.530
Engine 51 still displays Available.

00:03:54.010 --> 00:03:57.850
We deliberately submitted the existing Available value as practice.

00:03:58.210 --> 00:04:01.359
Read the result rather than expecting a different status color.

00:04:01.859 --> 00:04:06.209
Next, inspect the unit’s separate details page to check the stored values.

00:04:06.470 --> 00:04:09.850
Open Engine 51’s details using its details icon.

00:04:10.360 --> 00:04:15.339
Status Information shows Available, Destination shows None, and Status

00:04:15.389 --> 00:04:17.649
Updated provides a recorded timestamp.

00:04:18.139 --> 00:04:20.790
Assigned Roles still lists Christopher Herrmann.

00:04:21.259 --> 00:04:25.020
This readback lets a coordinator check the saved unit state and see the

00:04:25.020 --> 00:04:26.879
crew assignment on the same record.

00:04:27.039 --> 00:04:30.059
Scroll within the same unit details page to Note.

00:04:30.559 --> 00:04:34.250
The exact training note is now visible as stored record text.

00:04:34.570 --> 00:04:36.970
Compare it with the note entered before submission.

00:04:37.430 --> 00:04:40.819
Checking the saved note is useful when another coordinator needs to

00:04:40.819 --> 00:04:42.850
understand the context of an update.

00:04:43.019 --> 00:04:46.329
Return to the console and search for Boden in Personnel.

00:04:46.799 --> 00:04:50.499
The matching Wallace Boden card shows Command and Chief, along

00:04:50.499 --> 00:04:52.880
with Standing By and Available.

00:04:53.300 --> 00:04:56.590
Read these fields separately: the card presents a response

00:04:56.590 --> 00:04:58.510
status and a staffing value.

00:04:58.880 --> 00:05:01.919
Confirm the person’s name before opening their actions.

00:05:02.080 --> 00:05:03.580
Select Wallace Boden.

00:05:04.089 --> 00:05:08.690
The Actions area now identifies that person and shows the response-status form

00:05:08.690 --> 00:05:10.840
with Select Status and its note field.

00:05:11.229 --> 00:05:14.010
Staffing has its own controls lower in this area.

00:05:14.350 --> 00:05:18.019
For this exercise, leave the response-status form unchanged and

00:05:18.019 --> 00:05:19.870
continue to the staffing selector.

00:05:20.039 --> 00:05:21.720
Open Select Staffing Level.

00:05:22.220 --> 00:05:27.690
This department offers Available, Delayed, Unavailable, Committed, and On Shift.

00:05:28.090 --> 00:05:31.390
These are the staffing choices shown by this training configuration.

00:05:31.869 --> 00:05:34.649
Choose the level your organization intends to record.

00:05:35.060 --> 00:05:39.870
Our exercise uses Available, preserving the member’s existing response status.

00:05:40.059 --> 00:05:44.199
Review Wallace Boden, Staffing Available, and the note Training

00:05:44.260 --> 00:05:46.460
only, Dispatch staffing practice.

00:05:46.900 --> 00:05:49.829
Choose Update Staffing when those values are correct.

00:05:50.250 --> 00:05:53.720
Check the action’s label before submitting: this exercise

00:05:53.720 --> 00:05:55.100
sends the staffing form.

00:05:55.430 --> 00:05:58.879
It does not submit the separate response-status form above it.

00:05:58.989 --> 00:06:02.630
The Activity Log now reports Personnel staffing updated.

00:06:03.050 --> 00:06:06.309
Wallace Boden’s card shows Standing By and Available.

00:06:06.650 --> 00:06:10.399
Read both values after submission, then use the personnel details

00:06:10.399 --> 00:06:11.689
view for a separate readback.

00:06:12.300 --> 00:06:15.289
The update event confirms the software action shown here;

00:06:15.660 --> 00:06:19.019
the next view identifies which fields are available to inspect.

00:06:19.149 --> 00:06:20.999
Open Wallace Boden’s details.

00:06:21.489 --> 00:06:25.810
Status and Staffing shows Standing By and Available in separate rows, with

00:06:25.900 --> 00:06:29.189
update timestamps, and Roles lists Chief.

00:06:29.609 --> 00:06:33.540
This page verifies the displayed response and staffing values; it

00:06:33.540 --> 00:06:35.189
does not display the staffing note.

00:06:35.660 --> 00:06:39.640
The same careful readback helps coordinators of community paramedicine,

00:06:39.849 --> 00:06:43.880
mental health response, search teams, security shifts, wildland

00:06:43.880 --> 00:06:47.820
crews, and industrial teams keep recorded staffing understandable.
