WEBVTT

00:00:00.000 --> 00:00:02.809
Begin on Calls in an authorized Responder session.

00:00:03.279 --> 00:00:08.350
The cards bring together a call number, name, location and assigned resources.

00:00:08.739 --> 00:00:11.640
Read those details before choosing any response.

00:00:12.069 --> 00:00:15.710
In this fictional department, enter Warehouse in Search calls.

00:00:16.149 --> 00:00:21.379
The list narrows to TRAINING — Warehouse alarm, numbered DEMO-0001,

00:00:21.690 --> 00:00:23.540
at Training site one in Chicago.

00:00:23.950 --> 00:00:27.540
Check the name, number and address together; a familiar

00:00:27.540 --> 00:00:31.069
word in a search result is not enough to identify an incident.

00:00:31.500 --> 00:00:33.540
The search changes the displayed list.

00:00:33.900 --> 00:00:38.400
It does not rename a call, dispatch anyone or change your personal status.

00:00:38.610 --> 00:00:40.849
Open that card to reach Call Details.

00:00:41.280 --> 00:00:45.369
The same name and number remain at the top, followed by the nature of the call.

00:00:45.759 --> 00:00:50.150
Here it describes reported smoke at an unoccupied training warehouse and

00:00:50.150 --> 00:00:52.089
a Squad Three search demonstration.

00:00:52.629 --> 00:00:55.619
The map provides context for the stored incident location.

00:00:55.869 --> 00:00:59.830
It does not establish where your device is or whether a crew has arrived.

00:01:00.260 --> 00:01:04.209
Route is available beside Notes, Images and Files, but we leave

00:01:04.209 --> 00:01:07.260
it untouched while reviewing the information already supplied.

00:01:07.440 --> 00:01:12.539
On Info, scroll until Priority, Timestamp, Type, Address and

00:01:12.539 --> 00:01:14.030
Note are visible together.

00:01:14.440 --> 00:01:17.049
This example shows Urgent and Structure Fire.

00:01:17.370 --> 00:01:21.769
Its timestamp is October twenty-fifth at eleven forty-nine in the morning; that

00:01:21.769 --> 00:01:24.319
displayed time is not an arrival report.

00:01:24.720 --> 00:01:27.319
Check the address against the intended training site.

00:01:27.700 --> 00:01:31.929
The note explicitly identifies a fictional Academy exercise and says

00:01:31.929 --> 00:01:34.019
not to dispatch real resources.

00:01:34.370 --> 00:01:37.530
Read qualifiers like this along with the headline, rather than

00:01:37.530 --> 00:01:40.640
carrying an assumption from the call list into your next action.

00:01:40.770 --> 00:01:43.960
Choose Dispatched and bring all the resource rows into view.

00:01:44.519 --> 00:01:49.499
Kelly Severide and Joe Cruz appear as User entries associated with Squad Three.

00:01:49.930 --> 00:01:54.570
Squad Three also has its own Unit entry, associated with Firehouse Fifty-one.

00:01:55.119 --> 00:01:59.869
The Group and Type labels help distinguish a person from a vehicle or team resource.

00:02:00.279 --> 00:02:02.879
This is the recorded dispatch assignment for the call.

00:02:03.310 --> 00:02:07.789
A name in this list does not, by itself, prove that person acknowledged the call,

00:02:07.990 --> 00:02:12.400
changed status, reached the location or received an external notification.

00:02:12.720 --> 00:02:15.559
Protocols and Activity answer different questions.

00:02:15.930 --> 00:02:20.820
In Protocols, this call currently returns No protocols attached to this call.

00:02:21.280 --> 00:02:24.499
Activity returns No timeline events available.

00:02:24.999 --> 00:02:28.060
Read each result in the context of the selected incident.

00:02:28.570 --> 00:02:32.439
Neither message supplies a missing procedure or confirms an arrival.

00:02:32.910 --> 00:02:36.849
An empty activity view is not a reason to invent a response history.

00:02:37.279 --> 00:02:40.929
If important guidance or chronology is missing, resolve that through your

00:02:40.929 --> 00:02:45.159
authorized coordination process before treating the information as complete.

00:02:45.330 --> 00:02:47.000
Choose Notes to inspect

00:02:47.000 --> 00:02:50.580
Call Notes. This example says No notes found.

00:02:51.019 --> 00:02:54.490
The search box can help find an existing note when there are entries.

00:02:54.769 --> 00:02:59.099
Below it, Add a new note and Add Note belong to the writing workflow.

00:02:59.530 --> 00:03:02.679
We leave the field blank and use Cancel, so this inspection

00:03:02.720 --> 00:03:04.159
adds nothing to the incident.

00:03:04.540 --> 00:03:08.710
Reading the original note on Info and checking the separate Call Notes list are

00:03:08.710 --> 00:03:13.460
useful complementary checks; do not assume they are the same piece of information.

00:03:13.600 --> 00:03:17.050
The Images and Files buttons open separate supporting views.

00:03:17.510 --> 00:03:20.650
Call Images currently says No images available.

00:03:21.040 --> 00:03:24.919
Call Files says No files available and explains that none

00:03:24.919 --> 00:03:26.310
have been added to this call.

00:03:26.700 --> 00:03:30.970
These are the results shown for this incident, not demonstrations of uploading,

00:03:31.040 --> 00:03:32.929
downloading or taking a photograph.

00:03:33.280 --> 00:03:37.690
Check the call identity before relying on an attachment from any source, and

00:03:37.690 --> 00:03:42.089
use only approved material when a later task genuinely requires adding one.

00:03:42.240 --> 00:03:46.899
On Home, this example shows three Active Calls and zero Calls I’m On.

00:03:47.350 --> 00:03:49.299
Those counts answer different questions.

00:03:49.759 --> 00:03:54.450
The Status controls include Responding, Not Responding, On Scene and

00:03:54.450 --> 00:03:58.549
Standing By; the Standing By choice remains outlined during this review.

00:03:58.949 --> 00:04:00.830
We do not press a response button.

00:04:01.399 --> 00:04:05.990
Use the same read-before-response pattern for fire and EMS, community-care

00:04:05.990 --> 00:04:10.799
or mental-health teams, search and rescue, security patrols, wildland

00:04:10.799 --> 00:04:12.879
contractors and industrial teams.

00:04:13.280 --> 00:04:17.530
Find the correct incident, read its context and assignments, and identify

00:04:17.530 --> 00:04:21.550
missing information before making an authorized operational response.
