WEBVTT

00:00:00.000 --> 00:00:04.309
In Records, the New Record form has Training selected in Definition.

00:00:04.780 --> 00:00:08.909
This built-in form provides course information, a narrative, participant

00:00:08.909 --> 00:00:11.010
rows and optional unit times.

00:00:11.430 --> 00:00:15.420
Our fictional Chicago Fire exercise demonstrates the record lifecycle.

00:00:15.770 --> 00:00:19.209
It does not represent a physical training session or attendance.

00:00:19.659 --> 00:00:23.899
Enter a distinct Course, Training Only, Records Software Entry,

00:00:24.059 --> 00:00:25.620
followed by the exercise date.

00:00:26.040 --> 00:00:30.139
The Course code is Academy Rec Twenty-Nine, and External ID carries

00:00:30.139 --> 00:00:31.870
a separate exercise reference.

00:00:32.259 --> 00:00:34.840
Location says Fictional Software Workspace.

00:00:35.270 --> 00:00:38.189
Review Start and the empty End before continuing.

00:00:38.450 --> 00:00:43.079
The initial Narrative explains that this is a software record-entry exercise and

00:00:43.079 --> 00:00:47.269
that no physical training, attendance or operational response occurred.

00:00:47.849 --> 00:00:50.650
Write enough context for someone reading the record later.

00:00:51.200 --> 00:00:55.180
Below it, Participants provides a person selector, an optional

00:00:55.180 --> 00:00:56.750
assigned unit and a role.

00:00:57.299 --> 00:00:59.219
We leave the participant unselected.

00:00:59.699 --> 00:01:03.379
A blank chooser is not an attendance entry, and adding a name would

00:01:03.379 --> 00:01:04.910
make a different factual claim.

00:01:05.350 --> 00:01:08.029
The exercise therefore keeps this section empty.

00:01:08.189 --> 00:01:13.370
The Units section offers a checkbox for each unit and columns for Dispatched, En

00:01:13.370 --> 00:01:16.809
route, On scene, Released and In quarters.

00:01:17.269 --> 00:01:19.779
These fields belong to the record’s response data.

00:01:20.170 --> 00:01:23.229
They are not instructions to change a unit’s live status.

00:01:23.630 --> 00:01:26.889
We leave all unit selections and time entries untouched

00:01:26.940 --> 00:01:28.420
because no response happened.

00:01:28.860 --> 00:01:32.180
Review the displayed rows and preserve those empty selections

00:01:32.260 --> 00:01:35.950
rather than entering invented times to make a record appear complete.

00:01:36.109 --> 00:01:40.360
At the bottom, no file is selected and the attestation is unchecked.

00:01:40.880 --> 00:01:44.359
Choose Save draft to retain an editable record for review.

00:01:44.960 --> 00:01:48.380
The separate Save and finalize control is visible, but this

00:01:48.380 --> 00:01:50.019
first step saves the draft.

00:01:50.479 --> 00:01:56.940
The fresh View Record page shows Training in Draft, with reference D, Y, X, S,

00:01:57.129 --> 00:01:59.920
Nine, Three and no final record number.

00:02:00.299 --> 00:02:02.299
Author and Owner are Wallace Boden.

00:02:02.670 --> 00:02:06.909
Station and group resolved to Command after the initial field was left blank.

00:02:07.299 --> 00:02:10.910
Read the returned group and keep the actual reference before proceeding.

00:02:11.149 --> 00:02:14.429
Use Edit on this saved draft to revise its content.

00:02:14.889 --> 00:02:19.060
Continue with the existing record rather than opening another New Record form.

00:02:19.580 --> 00:02:23.750
The revised Narrative states that this is software record entry, no physical

00:02:23.750 --> 00:02:28.829
training or operational response occurred, and no personnel or unit times were added.

00:02:29.329 --> 00:02:32.829
Course, code and Location remain the exercise values.

00:02:33.370 --> 00:02:37.400
Read the complete text in the visible editor after typing; the content

00:02:37.400 --> 00:02:41.240
on screen must match the intended statement before you rely on it.

00:02:41.389 --> 00:02:45.030
A fresh View Record readback now contains the corrected narrative on

00:02:45.030 --> 00:02:47.280
the same draft and the same reference.

00:02:47.709 --> 00:02:50.259
It remains Draft, with no final number.

00:02:50.719 --> 00:02:54.200
Checking a separate readback is valuable even when a draft supports

00:02:54.200 --> 00:02:58.550
automatic saving: text visible in an editor is not sufficient evidence

00:02:58.550 --> 00:03:00.370
that the intended version is stored.

00:03:00.749 --> 00:03:04.269
If the result is unexpected, inspect this existing draft

00:03:04.269 --> 00:03:06.189
before repeating a create action.

00:03:06.610 --> 00:03:10.390
Here the software-only revision is present and ready for the next step.

00:03:10.710 --> 00:03:13.790
In Attachments, choose the public software handout and

00:03:13.790 --> 00:03:17.770
select Unrestricted operational content in File classification.

00:03:18.170 --> 00:03:22.570
Use this classification because the file contains only the fictional exercise.

00:03:22.890 --> 00:03:24.759
Then use Add attachment.

00:03:25.190 --> 00:03:28.890
After a fresh readback, academy-record-entry-handout dot

00:03:28.890 --> 00:03:32.769
text appears in the attachment list with three hundred fifty-eight bytes.

00:03:33.099 --> 00:03:36.459
The upload selector has reset to Restricted for another file.

00:03:36.799 --> 00:03:39.760
That reset does not describe the file already stored.

00:03:40.099 --> 00:03:43.849
We will check the stored classification in the finalized revision, rather than

00:03:43.849 --> 00:03:45.869
inferring it from the new-upload control.

00:03:46.139 --> 00:03:48.980
Read the narrative and stored handout before signing.

00:03:49.439 --> 00:03:52.690
The attestation says the record is accurate and complete to

00:03:52.690 --> 00:03:53.969
the best of your knowledge.

00:03:54.359 --> 00:03:59.159
In this exercise, accuracy means accurately documenting a software practice

00:03:59.199 --> 00:04:01.439
with no physical training or response.

00:04:01.869 --> 00:04:04.409
Check the attestation and use Finalize.

00:04:04.879 --> 00:04:09.440
The fresh result shows Finalized and the actual issued number, T R N,

00:04:09.659 --> 00:04:12.170
Twenty Twenty-Six, Zero Zero Zero Two.

00:04:12.680 --> 00:04:14.260
The draft reference remains.

00:04:14.690 --> 00:04:18.879
Amend is now available for later corrections; a finalized revision

00:04:18.879 --> 00:04:22.519
is preserved rather than overwritten by ordinary draft editing.

00:04:22.779 --> 00:04:27.169
History now contains revision one, transition Finalized, with Wallace

00:04:27.169 --> 00:04:28.730
Boden and the recorded date.

00:04:29.120 --> 00:04:30.580
The handout remains listed.

00:04:31.070 --> 00:04:35.470
Use View on that history row to inspect what this first signature preserved.

00:04:35.909 --> 00:04:39.420
The resulting HTML page identifies the complete department

00:04:39.449 --> 00:04:41.090
record and revision one.

00:04:41.519 --> 00:04:45.869
Its Details section contains the Course, Course Code, Location and

00:04:45.869 --> 00:04:47.830
exact software-only Narrative.

00:04:48.209 --> 00:04:51.490
This gives a specific version to review, rather than relying

00:04:51.539 --> 00:04:53.310
only on the latest record header.

00:04:53.499 --> 00:04:57.800
The same revision lists the handout’s filename, byte size, checksum

00:04:57.840 --> 00:04:59.809
and Unrestricted classification.

00:05:00.229 --> 00:05:03.259
This is the stored attachment metadata, separate from the

00:05:03.259 --> 00:05:04.910
reset chooser we saw earlier.

00:05:05.269 --> 00:05:07.809
The checksum matches the retained public handout.

00:05:08.419 --> 00:05:13.040
Farther down, Draft Reference, External Id and Record Number connect the

00:05:13.040 --> 00:05:15.290
original draft to the finalized record.

00:05:15.649 --> 00:05:19.390
Keep those identifiers together when reviewing an exercise or resolving a

00:05:19.390 --> 00:05:21.550
question about which version was signed.

00:05:21.830 --> 00:05:25.819
Returning to Records shows the new finalized Training row alongside

00:05:25.819 --> 00:05:29.299
the earlier Work draft and older finalized Training example.

00:05:29.850 --> 00:05:34.739
Read the number, type, state and summary together to choose the intended row.

00:05:35.299 --> 00:05:40.469
The original Work draft remains D, Four Six Nine K P; the older Training

00:05:40.469 --> 00:05:42.860
record ends Zero Zero Zero One.

00:05:43.450 --> 00:05:47.010
This exercise created and finalized only its own entry.

00:05:47.460 --> 00:05:51.059
Leave the other records untouched, and use the actual issued number

00:05:51.059 --> 00:05:52.669
when finding this example again.

00:05:52.800 --> 00:05:56.619
Chicago Fire can use this pattern for a software orientation record.

00:05:57.050 --> 00:06:01.159
Community care and mental-health teams can document an operational software

00:06:01.159 --> 00:06:03.310
exercise without client histories.

00:06:03.709 --> 00:06:06.629
Search-and-rescue teams can keep practice documentation

00:06:06.629 --> 00:06:08.529
distinct from a mission response.

00:06:08.910 --> 00:06:13.080
Security teams can retain a fictional platform exercise; wildland

00:06:13.080 --> 00:06:17.570
coordinators can document seasonal software familiarization; industrial

00:06:17.570 --> 00:06:21.050
teams can preserve a system-training example and public handout.

00:06:21.480 --> 00:06:26.489
Across all six settings, use accurate narrative, actual participants and times

00:06:26.630 --> 00:06:30.950
only when they occurred, a verified attachment, and the saved revision that

00:06:30.950 --> 00:06:32.800
supports the statement being reviewed.
