Skip to main content
Regulaxy

Checklist forms

Building the form an operator fills in at the end of a window, how the form shown is chosen, and why saved answers do not change when the form is edited.

A checklist is what an operator fills in at the end of a maintenance window: what was checked, what went out, what stayed open. It sits in the Checklist tab of the event card, and it is built in settings under Checklist forms with no code.

Building the form

Five question types:

TypeWhen
Single choiceOne answer from a closed list
Multiple choiceSeveral answers from that list
Short textA line
Long textA paragraph
Yes / NoA toggle

Each question has a title, an optional Required mark, and drag to reorder. Choice questions take their options as rows. A Preview toggle shows the form as the operator will see it.

Saving is blocked until the form has a name, at least one question, a title on every question, and at least one option on every choice question. The message names the question that is missing something.

Which form is shown

One active form per update type, and beside them a Default (global) one. An event gets its update type's form; if there is none, it gets the global form; if there is no global form either, there is no checklist.

Deleting a type-specific form returns that type to the global form, and the dialog says so before confirming: "Delete the custom form? Events of this type return to the global form."

Filling it in

At the top of the form is Execution status, and saving requires choosing Completed or Failed — a checklist cannot be saved while leaving the event planned. Choosing Failed opens a Failure reason field, which is itself required.

Required fields that were not filled in block the save, and the message names them.

After the first save the form stays open for updating, and the screen states who filled it in and when, with the note "It can be updated and saved again."

The email summary

Once every required field is filled in, a checklist summary goes out to the event's coordination circle: the contacts, the system manager, and the person who created the event. Saving again on a form that was already complete sends an updated summary, marked as such.

Sending is best-effort only: if it fails, the checklist is saved regardless and the screen says the summary did not go out. Answers a user typed are not discarded because of a mail problem.

Why editing a form does not change old answers

In the history table, the Checklist column summarizes each event as Complete · Partial n/m · Empty · None, and can be searched by the wording of a question or by the answer itself. See Events and history.

Updated

This page is the file content/docs/en/v1/plan/checklists.mdx