WEBVTT

00:00:00.029 --> 00:00:03.279
This lesson maintains an existing IC command board in a

00:00:03.279 --> 00:00:05.059
fictional warehouse exercise.

00:00:05.440 --> 00:00:09.310
The screens come from the same saved exercise across browser sessions.

00:00:09.720 --> 00:00:12.899
Begin in Call Details and verify the Warehouse alarm

00:00:12.899 --> 00:00:14.380
name and training location.

00:00:14.880 --> 00:00:18.299
Active Command and Open Command Board identify the available

00:00:18.299 --> 00:00:19.620
route into this incident.

00:00:20.040 --> 00:00:21.579
Choose Open Command Board.

00:00:22.059 --> 00:00:25.049
Check the incident name again on Command Board, along with

00:00:25.049 --> 00:00:26.649
Wallace Boden as commander.

00:00:27.059 --> 00:00:31.450
Before practicing, make this identity check a habit; similar lane names

00:00:31.450 --> 00:00:33.150
can appear on different incidents.

00:00:33.309 --> 00:00:36.270
Command Structure shows Search Division and Staging.

00:00:36.730 --> 00:00:41.630
Squad 3 is already in Search Division; Staging has no assigned resource.

00:00:42.160 --> 00:00:45.519
Rotate and Requirements are review cues on the saved assignment.

00:00:45.819 --> 00:00:47.899
They do not move the unit automatically.

00:00:48.389 --> 00:00:49.790
Scroll to Resources.

00:00:50.159 --> 00:00:53.950
All is selected, with Unassigned and Assigned available beside it.

00:00:54.300 --> 00:00:59.450
The pool contains Squad 3, Engine 51 and the fictional Exercise Gate Marshal.

00:00:59.929 --> 00:01:04.579
Engine 51 names Christopher Herrmann in its Officer or Team Lead position while

00:01:04.579 --> 00:01:06.610
the unit remains unassigned to a lane.

00:01:07.090 --> 00:01:10.419
Crew membership and command allocation describe different things.

00:01:10.780 --> 00:01:14.120
For practice, explain that difference before proposing a move.

00:01:14.439 --> 00:01:16.949
In Tactical Objectives, choose Add.

00:01:17.439 --> 00:01:20.119
The empty section gives us a clear starting point.

00:01:20.559 --> 00:01:24.960
In Add Objective, select Benchmark under Type and enter the training

00:01:24.960 --> 00:01:26.420
primary-search objective.

00:01:26.769 --> 00:01:28.210
Choose Add to save it.

00:01:28.580 --> 00:01:32.670
A specific objective name gives the next operator something concrete to review.

00:01:33.199 --> 00:01:36.690
Open the objective and use Progress to set fifty percent.

00:01:37.020 --> 00:01:39.760
The returned details show fifty percent selected.

00:01:40.219 --> 00:01:43.859
Outcome, Close-out note and Complete Objective describe a

00:01:43.859 --> 00:01:45.309
separate close-out decision.

00:01:45.670 --> 00:01:48.240
This exercise leaves the objective incomplete.

00:01:48.629 --> 00:01:51.379
Practice updating progress without treating an estimate

00:01:51.409 --> 00:01:52.740
as a completed search.

00:01:52.950 --> 00:01:56.590
In the Needs section, use Add to open Add Need.

00:01:57.079 --> 00:01:58.990
Choose Medical under Category.

00:01:59.430 --> 00:02:04.459
Enter the training rehab need, set Qty to two, and use Details to explain

00:02:04.459 --> 00:02:08.949
the gap: two fictional rehab positions at staging, for internal tracking.

00:02:09.420 --> 00:02:12.050
Choose Add after checking the name and quantity.

00:02:12.459 --> 00:02:16.619
This example records a quantified need; it does not request a provider

00:02:16.650 --> 00:02:18.289
or demonstrate anyone arriving.

00:02:18.789 --> 00:02:19.900
Open the saved need.

00:02:20.330 --> 00:02:24.259
Its heading still shows an open medical need with zero of two filled.

00:02:24.740 --> 00:02:28.769
For practice, describe what remains outstanding before entering a fill.

00:02:29.030 --> 00:02:32.079
In the need details, set Fill to one of two.

00:02:32.650 --> 00:02:38.029
Enter an explicit training explanation in Note or Reason, then choose Save Fill.

00:02:38.409 --> 00:02:42.939
The number is a tracking entry; it is not evidence of a person reaching staging.

00:02:43.319 --> 00:02:44.310
Reopen the need.

00:02:44.709 --> 00:02:48.230
Partial Fill and one of two now describe the saved result.

00:02:48.609 --> 00:02:52.800
History attributes the change to Wallace Boden and retains the training reason.

00:02:53.150 --> 00:02:57.779
The board also shows the need at one of two beside the objective at fifty percent.

00:02:58.130 --> 00:02:59.779
Leave the remaining gap visible.

00:03:00.130 --> 00:03:04.209
For practice, explain why a partial fill should remain distinguishable

00:03:04.209 --> 00:03:06.160
from completing or closing the need.

00:03:06.370 --> 00:03:08.810
Scroll to Notes and choose Add Note.

00:03:09.290 --> 00:03:12.309
Give the next operator a concrete location and scope.

00:03:12.729 --> 00:03:16.590
Our note keeps staging at the fictional west gate and explicitly says

00:03:16.590 --> 00:03:18.469
there is no operational deployment.

00:03:18.969 --> 00:03:21.349
Under Visibility, select Internal.

00:03:21.750 --> 00:03:24.809
The helper says the note is visible to command staff only

00:03:25.059 --> 00:03:28.250
and that the log records who added it, rather than its text.

00:03:28.649 --> 00:03:30.190
Public is a different choice.

00:03:30.600 --> 00:03:33.459
Check the intended audience, then choose Save.

00:03:33.869 --> 00:03:37.879
After reopening the board, the note retains its Internal badge and body.

00:03:38.240 --> 00:03:42.820
Below it, ICS Role Assignments names Matthew Casey as Safety Officer.

00:03:43.180 --> 00:03:46.029
That existing command role is separate from a unit riding

00:03:46.029 --> 00:03:47.500
position or lane assignment.

00:03:47.889 --> 00:03:51.619
Practice checking the note audience before using a shared command device.

00:03:51.760 --> 00:03:56.499
Timers and PAR shows the existing Training PAR reminder as overdue,

00:03:56.740 --> 00:03:58.169
with Acknowledge available.

00:03:58.560 --> 00:04:02.180
Its elapsed time reflects the saved exercise across sessions.

00:04:02.510 --> 00:04:05.159
This recording does not acknowledge or restart it.

00:04:05.539 --> 00:04:10.489
A reminder needs a deliberate operational response; its badge alone says nothing

00:04:10.489 --> 00:04:11.880
about a crew member's condition.

00:04:12.510 --> 00:04:14.040
Now read Accountability.

00:04:14.440 --> 00:04:18.589
The call says check-in timers are active, but no timers are configured.

00:04:18.950 --> 00:04:23.059
Refresh is visible, but this empty configuration cannot demonstrate a

00:04:23.059 --> 00:04:25.559
successful check-in or a PAR result.

00:04:25.870 --> 00:04:29.750
For practice, explain which information is missing before asking

00:04:29.750 --> 00:04:31.500
a crew to rely on this display.

00:04:31.600 --> 00:04:36.170
On Incident Map, check the actual Chicago street map and Squad 3 marker

00:04:36.170 --> 00:04:37.719
with its Search Division label.

00:04:38.139 --> 00:04:42.770
These are fictional training positions, not a demonstration of device GPS.

00:04:43.249 --> 00:04:46.799
Pan to frame the surrounding streets, then choose Save View.

00:04:47.320 --> 00:04:50.659
Here the manual pan moves the marker to the right of center.

00:04:51.050 --> 00:04:53.690
Reopening the incident map retains that framing.

00:04:54.100 --> 00:04:56.270
A full browser reload retains it too.

00:04:56.770 --> 00:04:59.729
Pan and Save View were verified in this web recording.

00:05:00.110 --> 00:05:04.989
Line, Area and Text are visible, but annotation placement was not verified.

00:05:05.390 --> 00:05:09.789
Native touch, location and offline behavior need separate device checks.

00:05:10.120 --> 00:05:13.239
Practice saving a useful view and checking the returned map.

00:05:13.410 --> 00:05:16.030
Return to the board and scroll to Incident Log.

00:05:16.570 --> 00:05:21.140
Read the timestamped objective addition, progress update and need-fill entry.

00:05:21.530 --> 00:05:24.280
They connect the working cards to attributed actions.

00:05:24.719 --> 00:05:28.679
The internal note has a non-public log marker with its author; its

00:05:28.679 --> 00:05:30.630
body stays out of this log entry.

00:05:31.030 --> 00:05:34.239
The map-created entry is also present after Save View.

00:05:34.700 --> 00:05:39.280
For handover practice, compare this history with the saved cards, identify

00:05:39.280 --> 00:05:43.759
the remaining one-of-two gap, and state that the objective is still incomplete.

00:05:44.230 --> 00:05:46.010
Leave this training command active.

00:05:46.450 --> 00:05:51.110
This lesson verifies recorded application state; it does not establish a field

00:05:51.110 --> 00:05:55.069
deployment, delivered notification or completed accountability check.
