WEBVTT

00:00:00.090 --> 00:00:02.529
Open Shifts and find the Calendar section.

00:00:03.130 --> 00:00:07.239
Add Static Shift creates a dated coverage window for selected units.

00:00:07.650 --> 00:00:12.229
Use this when you need a fixed commitment, such as a community standby, a security

00:00:12.229 --> 00:00:14.510
detail or a search support period.

00:00:14.899 --> 00:00:17.239
The calendar in this exercise is November.

00:00:17.649 --> 00:00:20.379
Select Add Static Shift to open the form.

00:00:20.860 --> 00:00:24.579
Use a separate training unit while you learn the save and update process.

00:00:24.810 --> 00:00:26.829
Give the shift a recognizable Name.

00:00:27.289 --> 00:00:30.189
The example uses Verified static coverage.

00:00:30.669 --> 00:00:34.970
Choose a light Color so the calendar’s black text stays readable; the help

00:00:34.970 --> 00:00:36.549
beside the field calls this out.

00:00:37.100 --> 00:00:41.029
Add a Description explaining the work and any coordination instructions.

00:00:41.459 --> 00:00:45.140
This fictional description also reminds the editor to verify dates

00:00:45.170 --> 00:00:47.269
and retained units before updating.

00:00:47.699 --> 00:00:51.090
A clear title and description help people recognize the commitment

00:00:51.119 --> 00:00:52.699
when they open it from the calendar.

00:00:52.800 --> 00:00:57.319
Set Start Date and Time to November twelfth at nine in the morning, and End

00:00:57.319 --> 00:00:59.280
Date and Time to five that afternoon.

00:00:59.760 --> 00:01:04.300
The start help describes when entities are committed; the end help describes

00:01:04.329 --> 00:01:05.589
when they are available again.

00:01:06.070 --> 00:01:11.099
Under Units, select the fictional static demo unit and confirm its selected tag.

00:01:11.529 --> 00:01:15.379
Check both dates and the chosen unit before Create Static Shift.

00:01:15.740 --> 00:01:19.910
Dismiss the date picker so it does not cover the unit selection or save control.

00:01:20.119 --> 00:01:24.739
Select Create Static Shift, then open the matching event from the calendar.

00:01:25.199 --> 00:01:29.489
View Static Shift Day shows November twelfth at nine, the shift title and

00:01:29.489 --> 00:01:31.760
description, and the selected unit.

00:01:32.119 --> 00:01:35.239
This is the saved result, not the preparation form.

00:01:35.649 --> 00:01:40.170
The training unit has no configured unit-role slots, so this example does not

00:01:40.170 --> 00:01:42.190
claim that any person has been assigned.

00:01:42.610 --> 00:01:46.690
Compare the saved day and unit with the intended commitment before moving on.

00:01:46.880 --> 00:01:48.789
Select Edit Static Shift.

00:01:49.239 --> 00:01:53.099
The reopened dates retain nine in the morning through five in the afternoon.

00:01:53.610 --> 00:01:57.400
Read the yellow warning before Update: editing clears the shift’s

00:01:57.400 --> 00:02:00.880
assignments or signups and rebuilds them from the new settings.

00:02:01.350 --> 00:02:05.170
In this version, the Units selection is initially empty on Edit.

00:02:05.589 --> 00:02:08.560
Deliberately select every unit you intend to retain.

00:02:09.019 --> 00:02:12.179
Coordinate the change before updating a staffed operational

00:02:12.179 --> 00:02:16.810
shift; do not assume a saved date change preserves existing signups.

00:02:16.959 --> 00:02:21.690
For this disposable exercise, move the window to November thirteenth, ten in

00:02:21.690 --> 00:02:23.440
the morning through six in the evening.

00:02:23.909 --> 00:02:26.980
Reselect the same training unit and verify its tag.

00:02:27.459 --> 00:02:30.180
Review the warning and select Update once.

00:02:30.569 --> 00:02:32.499
Open the saved calendar event again.

00:02:32.970 --> 00:02:36.220
Its day detail now shows November thirteenth at ten,

00:02:36.349 --> 00:02:38.119
with the same unit still listed.

00:02:38.519 --> 00:02:42.419
That readback checks both the new date and the unit submitted with the update.

00:02:42.630 --> 00:02:47.320
Reopen Edit to check the persisted start and end values: ten A M and

00:02:47.320 --> 00:02:49.409
six P M on November thirteenth.

00:02:49.820 --> 00:02:53.410
The Units picker is empty again in this editor, even though the saved

00:02:53.410 --> 00:02:55.120
day detail just showed the unit.

00:02:55.539 --> 00:02:58.289
Do not submit another update while merely reviewing.

00:02:58.740 --> 00:03:01.709
Select Cancel to leave the stored shift unchanged.

00:03:02.090 --> 00:03:05.830
Use the saved day detail to verify the current unit commitment, and

00:03:05.830 --> 00:03:09.250
review the edit warning whenever a change is actually required.

00:03:09.469 --> 00:03:14.679
Use this same create, verify and carefully update process for search and rescue,

00:03:14.860 --> 00:03:19.410
security companies, wildland contractors and industrial emergency teams.

00:03:19.790 --> 00:03:24.299
Community paramedicine, mental health response, fire and E M S teams can

00:03:24.299 --> 00:03:26.099
plan fixed support windows as well.

00:03:26.519 --> 00:03:29.829
Choose a meaningful unit and coverage period, keep calendar

00:03:29.829 --> 00:03:33.870
labels readable, and verify the saved result after every change.

00:03:34.280 --> 00:03:38.099
This lesson covers a fixed unit commitment; recurring rotations

00:03:38.099 --> 00:03:40.980
and personnel signup workflows have their own walkthroughs.
