Editing Checklist (section)

===Mode of use===
A checklist may be used to identify the action, after which it is done, then checked off as complete and the next item identified, known as the ''read–do'', ''do–list'' or ''call–do–response''  process, or the tasks may be done, and then the checklist consulted to ensure that nothing has been left out, the ''do–confirm'' procedure, in which the status of tasks must be remembered until checked off, which may result in more errors,<ref name="Hodges et al 2019" /> or ''challenge, verification, and response'' process, in which the checklist is used after the tasks have been completed.  Both methods have merit and suitable applications, and the most suitable type of checklist will depend on the type of operation.<ref name="Lau 2023" />

In the ''call–do–response'' system, the checklist is used to lead the operators through a step-by-step procedure where one operator directs the others, following the list. Each item requiring configuration is listed on the checklist and all relevant operators must be present while the checks are done. This method tends to be more detailed and time-consuming. It may be more appropriate for systems which are less familiar to the operators.<ref name="Lau 2023" />

In the ''challenge–verification–response'', the operators prepare the system following a standard sequence of actions performed from memory, then use the checklist to verify that the critical items have been correctly configured. One operator reads the challenge part of the checklist, the designated parties verify the status, and one of them provides the appropriate response. This is done in sequence until the list is complete. It may be ticked or signed off as specified. This method is efficient, as each operator can get on with their checks and then when the checklist is run through, all the relevant crew are updated on the system status.<ref name="Lau 2023" />