Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Checklist
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Effectiveness of checklists== Ranapurwala et al. (2017) found:<ref name="Hodges et al 2019" /> {{quote|The use of memorized checklists was similar to not using any checklist at all; hence the use of written checklists should be encouraged, instead.}} Characteristics of effective checklists include:<ref name="Courtnell 2019" /> * Checklists should be simple and convenient to use. Each listed item should be necessary and together they should be sufficient.<ref name="Courtnell 2019" /> * Checklists focused on the responsibilities of a specific person, or a group who will work together, are less likely to have items left out.<ref name="Courtnell 2019" /> * Grouping items which can be done at the same time or place, or by the same person, often improves efficiency.<ref name="Courtnell 2019" /> ** A group may have a checkbox to indicate completion of the group. This is more likely to be helpful if there are several groups. * Where reasonably practicable the items to be checked by a specific person can be grouped on the list. This makes it easier for them to keep track of what they have done and must still do. In some cases it may help to split them off as a separate checklist.<ref name="Courtnell 2019" /> * Items should not be over-detailed in description nor ambiguous. A checklist should not try to define or describe procedures which should be familiar to the checker, though critical steps may usefully be listed in order when order is important.<ref name="Courtnell 2019" /> * Ordering of the list should be logical. Where chronological order is important, it should be indicated by order on the list. Where items to be checked are spatially distributed, an order minimising travel or search time is efficient.<ref name="Courtnell 2019" /> * The most convenient and reliable checklists are normally completed from top to bottom in a single session. It should be easy to recover from any interruption without risking missing an item or redoing a check unnecessarily.<ref name="Courtnell 2019" /> * The physical checklist must be convenient to use on site. It should not require special effort to read, or protect it from the environment.<ref name="Courtnell 2019" /> * It may be useful to cross-reference the checklist to the standard procedure, where the process is definitively described in detail, particularly for training and audit purposes. This makes it easy to check if there is any doubt.<ref name="Courtnell 2019" /> * Some checklists must be signed off and kept as evidence, others may be re-usable. This may affect the format and materials.<ref name="Courtnell 2019" /> * Checkboxes at the beginning of each item are easier to find and follow to the next incomplete check. A keyword at the beginning of the text will help ensure that the correct box is ticked.<ref name="Courtnell 2019" /> * When several checklists are used, due to complexity of the task, or the need for several people to make checks at different places, a master checklist indicating the completion of each subordinate checklist may be used.<ref name="Courtnell 2019" /> * If instructions are necessary, they should be included. If not, they should be left out as they will distract the user.<ref name="Courtnell 2019" />
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)