Learn from a checklist example
Compare sections, stage assignments, optional and required readings, and separate approval before building your own.
Create an editable example draft
- In Admin, open Checklist Editor → Example setups and select an example.
- Use Check reviewer setup. The preview shows whether its example departments exist and have enabled members.
- Choose Use example as new draft, give it a name and confirm. This does not overwrite the selected checklist, publish it or copy answers.
- Review every item and its stage. Add users in Users & access; assign membership in Departments. On a draft item, choose another active department or a named person where needed. Missing departments and accounts are never created automatically.
- Save draft. After review, Publish revision. New records start with every item Pending. Existing records stay unchanged.
Department and reviewer setup · Manual checklist creation
Examples on this page are read-only. Use the Windows editor to create the editable draft.
Build your first checklist — example
Checklist · 1 stage(s) · 5 items
Example departments: Party Chief, Processing. An assigned reviewer may also have checked the item; both actions are recorded.
01 · Setup basics
| Item | Stage | Reading setup | Separate approval |
|---|---|---|---|
| 01 · Example: confirm the job reference and responsible team are recorded. | Checklist | No reading field | Not required |
| 02 · Example: record a document or evidence reference. | Checklist | Evidence / document reference (text; required) | Not required |
| 03 · Example: enter a practice numeric value to learn how a bounded reading works. | Checklist | Practice value (demonstration only) (number; required; demonstration range 0–100; not an operational limit) | Not required |
02 · Review and approval
| Item | Stage | Reading setup | Separate approval |
|---|---|---|---|
| 01 · Example: submit the prepared evidence for Processing review. | Checklist | Handover evidence (text; required) | Processing |
| 02 · Example: record the Party Chief review of the agreed task scope. | Checklist | Agreed scope reference (text; required) | Party Chief |
Vessel mobilisation — setup example
Mobilisation · 1 stage(s) · 4 items
Example departments: Party Chief. An assigned reviewer may also have checked the item; both actions are recorded.
01 · Scope and evidence
| Item | Stage | Reading setup | Separate approval |
|---|---|---|---|
| 01 · Example: record the vessel mobilisation scope reference. | Mobilisation | Approved scope reference (text; required) | Not required |
| 02 · Example: record the relevant equipment documentation reference. | Mobilisation | Document reference (text; required) | Not required |
02 · Review and handover
| Item | Stage | Reading setup | Separate approval |
|---|---|---|---|
| 01 · Example: submit mobilisation evidence for Party Chief review. | Mobilisation | Review package reference (text; required) | Party Chief |
| 02 · Example: record that the agreed handover information was shared with the team. | Mobilisation | Handover note (text; optional) | Not required |
Data handover — setup example
Prepare → Receive · 2 stage(s) · 4 items
Example departments: Processing. An assigned reviewer may also have checked the item; both actions are recorded.
01 · Prepare handover
| Item | Stage | Reading setup | Separate approval |
|---|---|---|---|
| 01 · Example: record the data package identifier. | Prepare | Package identifier (text; required) | Not required |
| 02 · Example: submit the package evidence for Processing review. | Prepare | Review evidence (text; required) | Processing |
02 · Receive and record
| Item | Stage | Reading setup | Separate approval |
|---|---|---|---|
| 01 · Example: record the receiving team handover reference. | Receive | Receipt reference (text; required) | Not required |
| 02 · Example: request Processing review of the receipt evidence. | Receive | Evidence reference (text; required) | Processing |
Stage order and optional fields
The first two examples have one stage. Data handover has Prepare and Receive; finalise Prepare before finalising Receive. The Stage column identifies every item’s assignment.
A required reading must be supplied before completing its item. An optional reading may stay blank. Justified N/A entries still require any configured separate approval.
Checking is separate from approval
The technician checks and synchronises an item; its required approval remains outstanding until an assigned reviewer acts online, including the checker when assigned. Being an administrator is not an approval override. Approval is required only for the selected items.
Live editing is enabled separately on each record and is off by default. Loading an example does not enable it automatically.