WEBVTT

00:00:00.029 --> 00:00:03.779
Numbering helps people connect an item with its operational process.

00:00:04.150 --> 00:00:08.310
In our Chicago Fire demonstration department, calls, records and

00:00:08.310 --> 00:00:10.140
work orders have separate settings.

00:00:10.569 --> 00:00:15.699
From Department Settings, open Calls & Dispatch, then Call Settings for calls.

00:00:16.059 --> 00:00:18.430
Document Numbering is under Customization.

00:00:18.889 --> 00:00:23.360
For records, open Records, expand Manage and choose Settings.

00:00:23.790 --> 00:00:28.520
Work orders, invoices, bids and daily time reports share Document Numbering.

00:00:28.950 --> 00:00:33.259
Check the page before editing: saving an invoice pattern does not change

00:00:33.259 --> 00:00:35.169
call or incident-record numbering.

00:00:35.399 --> 00:00:38.219
Open Call Settings and scroll to Call Numbering.

00:00:38.729 --> 00:00:48.719
Our saved pattern is FD51-{YYYY}-{SEQ}: a department prefix, full year and sequence.

00:00:49.089 --> 00:00:50.630
Sequence digits is four.

00:00:51.059 --> 00:01:01.450
The inline example uses sample sequence 153, so it reads FD51-2026-0153; that

00:01:01.450 --> 00:01:03.700
sample is not the next issued number.

00:01:04.079 --> 00:01:07.030
The sequence token must appear exactly once.

00:01:07.459 --> 00:01:11.369
Letters, digits and supported separators form the fixed text.

00:01:11.830 --> 00:01:16.200
Review the example, choose Update and reopen the page to check the stored

00:01:16.200 --> 00:01:18.330
format before creating a training call.

00:01:18.539 --> 00:01:21.099
Read the token guidance under Call number pattern.

00:01:21.610 --> 00:01:24.269
A year pattern restarts each numbering year.

00:01:24.670 --> 00:01:28.969
Adding month makes a monthly scope; adding day makes a daily scope.

00:01:29.389 --> 00:01:32.229
A month needs a year, and a day needs a month.

00:01:32.570 --> 00:01:36.379
Without a date, the sequence continues without a date-based restart.

00:01:36.799 --> 00:01:44.389
For example, AC-{YYYY}{MM}{DD}-{SEQ} is a daily format.

00:01:44.820 --> 00:01:48.170
We keep the saved yearly FD51 pattern here.

00:01:48.549 --> 00:01:51.700
Dates follow the department time zone, so check that setting

00:01:51.700 --> 00:01:53.310
before choosing a reset rule.

00:01:53.519 --> 00:01:55.439
Review Numbering year starts.

00:01:55.869 --> 00:02:00.030
Our saved month is January and the day is one, so this example

00:02:00.030 --> 00:02:01.440
follows the calendar year.

00:02:01.919 --> 00:02:05.879
A yearly format starts a new sequence at its numbering-year boundary.

00:02:06.309 --> 00:02:10.530
Before using a different boundary, review the intended year label and the page's

00:02:10.530 --> 00:02:12.710
help against your department's convention.

00:02:13.220 --> 00:02:16.190
Monthly and daily call patterns use calendar dates.

00:02:16.560 --> 00:02:19.370
We are leaving the fiscal settings unchanged and checking

00:02:19.370 --> 00:02:20.839
the displayed next number.

00:02:20.989 --> 00:02:24.430
Next call number is the next value for a call logged now.

00:02:24.900 --> 00:02:30.730
Saving our new FD51 format started its own scope at 0001; older

00:02:30.730 --> 00:02:32.449
call numbers remained intact.

00:02:32.890 --> 00:02:37.459
After the training call received 0001, this page shows 0002.

00:02:38.080 --> 00:02:42.800
Raise next sequence to is for carrying forward numbers issued before Resgrid.

00:02:43.209 --> 00:02:44.699
It can only move forward.

00:02:45.119 --> 00:02:50.259
Save pattern or year-boundary changes first, reopen, then review any separate

00:02:50.259 --> 00:02:52.529
carry-forward value against the new scope.

00:02:52.969 --> 00:02:57.169
Leave this field blank when the displayed next number is correct, as we do here.

00:02:57.319 --> 00:03:01.810
In an authorized training exercise, open the saved call and compare its issued

00:03:01.810 --> 00:03:03.529
number with the format you reviewed.

00:03:04.010 --> 00:03:10.139
Our disposable training call received FD51-2026-0001.

00:03:11.269 --> 00:03:15.370
An older call keeps its original 26-format number because a pattern

00:03:15.370 --> 00:03:17.550
change never rewrites issued numbers.

00:03:17.960 --> 00:03:20.839
Mixed historical formats can therefore be expected.

00:03:21.359 --> 00:03:24.939
If a result differs from what you expected, check the local date,

00:03:25.259 --> 00:03:27.070
numbering-year boundary and scope.

00:03:27.529 --> 00:03:32.009
Do not create repeated calls merely to force a counter toward the inline sample.

00:03:32.199 --> 00:03:35.110
In Records Settings, find Record numbering.

00:03:35.529 --> 00:03:40.000
We preserve {PREFIX}-{YYYY}-{SEQ}

00:03:40.000 --> 00:03:42.279
with four digits and January first.

00:03:42.710 --> 00:03:44.989
PREFIX uses the record type prefix.

00:03:45.340 --> 00:03:49.059
Training defaults to TRN when its override box is blank.

00:03:49.420 --> 00:03:56.760
The next-number table shows TRN-2026-0002 after the existing training record.

00:03:57.239 --> 00:04:02.459
Prefixes shared by types share a sequence; GROUP can create group-specific scopes

00:04:02.500 --> 00:04:04.389
and must be followed by a separator.

00:04:04.770 --> 00:04:07.520
Calls month and day tokens do not belong here.

00:04:07.869 --> 00:04:11.150
Review stored settings and each relevant next row before

00:04:11.150 --> 00:04:12.669
changing this separate family.

00:04:12.850 --> 00:04:14.609
Open the existing training record.

00:04:15.040 --> 00:04:23.890
Its issued number is TRN-2026-0001, its station is Firehouse 51

00:04:24.180 --> 00:04:25.930
and its state is Finalized.

00:04:26.480 --> 00:04:30.170
The register also has a separate Work draft with a draft reference.

00:04:30.580 --> 00:04:33.009
These are different types and lifecycle states.

00:04:33.420 --> 00:04:38.000
A number identifies an item; it does not by itself establish review,

00:04:38.179 --> 00:04:40.099
approval or external submission.

00:04:40.500 --> 00:04:42.619
Check the state and history separately.

00:04:43.119 --> 00:04:46.930
Use an existing safe example when one is available, preserving its

00:04:46.930 --> 00:04:48.880
original contents and audit trail.

00:04:49.079 --> 00:04:50.510
Open Document Numbering.

00:04:50.959 --> 00:04:55.809
Each row controls work orders, invoices, bids or daily time reports.

00:04:56.170 --> 00:05:02.100
For our training work request we saved MNT-{YY}-{SEQ} with

00:05:02.100 --> 00:05:03.949
four digits, using Update.

00:05:04.319 --> 00:05:10.000
The sample reads MNT-26-0153, while the

00:05:10.000 --> 00:05:12.710
saved next value initially read 0001.

00:05:13.259 --> 00:05:19.140
After the request was issued, it advanced to MNT-26-0002.

00:05:19.830 --> 00:05:23.789
Invoice, bid and time-report rows retain their built-in formats.

00:05:24.179 --> 00:05:28.359
This page has its own numbering-year boundary, separate from Calls and Records.

00:05:28.729 --> 00:05:32.630
Reopen after saving and inspect every row you intended to change.

00:05:32.749 --> 00:05:36.810
The work-order wizard asks what the request is for, its unit or group,

00:05:37.129 --> 00:05:40.219
costs, safety details and a final review.

00:05:40.719 --> 00:05:44.650
Our fictional numbering demonstration uses Other, Low priority,

00:05:44.919 --> 00:05:46.969
no assignment and no costs.

00:05:47.449 --> 00:05:53.359
Saving creates MNT-26-0001 in Requested state.

00:05:53.779 --> 00:05:56.000
Reopen its detail and compare the

00:05:56.000 --> 00:05:57.549
register: older WO

00:05:57.549 --> 00:05:59.189
numbers remain unchanged.

00:05:59.549 --> 00:06:04.049
This request is software practice, not a completed repair or safety clearance.

00:06:04.490 --> 00:06:09.530
Records Settings separately holds request, occupancy, inspection, permit,

00:06:09.740 --> 00:06:11.999
investigation and evidence numbers.

00:06:12.479 --> 00:06:15.699
Verify actual saved items for the families you change and

00:06:15.699 --> 00:06:17.530
retain the chosen reset rules.

00:06:17.969 --> 00:06:22.519
A community care or mental health team can use a clear follow-up record prefix while

00:06:22.519 --> 00:06:24.260
keeping service work orders separate.

00:06:24.740 --> 00:06:28.679
Search and rescue teams can distinguish mission records from equipment requests.

00:06:29.139 --> 00:06:32.679
Security teams can separate patrol records, work requests

00:06:32.740 --> 00:06:33.949
and client documents.

00:06:34.420 --> 00:06:38.120
Wildland contractors can check fiscal-year rules for time reports.

00:06:38.569 --> 00:06:42.380
Industrial teams can distinguish incident, inspection, permit

00:06:42.469 --> 00:06:43.840
and maintenance references.

00:06:44.309 --> 00:06:48.499
In each setting, the identifier describes the item; review its actual

00:06:48.499 --> 00:06:50.849
contents and lifecycle state separately.
