Checklist

Last updated
Checklists are useful for displaying main points. Man checklist.jpg
Checklists are useful for displaying main points.

A checklist is a type of job aid used in repetitive tasks to reduce failure by compensating for potential limits of human memory and attention. Checklists are used both to ensure that safety-critical system preparations are carried out completely and in the correct order, [1] and in less critical applications to ensure that no step is left out of a procedure. they help to ensure consistency and completeness in carrying out a task. A basic example is the "to do list". [2] A more advanced checklist would be a schedule, which lays out tasks to be done according to time of day or other factors, or a pre-flight checklist for an airliner, which should ensure a safe take-off. [3]

Contents

A primary function of a checklist is documentation of the task and auditing against the documentation. [4] Use of a well designed checklist can reduce any tendency to avoid, omit or neglect important steps in any task. [5] For efficiency and acceptance, the checklist should easily readable, include only necessary checks, and be as short as reasonably practicable. [6]

History

It is widely accepted that checklists appeared after the crash of the Boeing B-17 plane on October 30th, 1935 [7] . Possibly, the source of such common knowledge is The Checklist Manifesto book by Atul Gawande. However, the Oxford English Dictionary states that the word appeared in 1853 [8] .

The earliest discovered evidence of the “check-list” usage is seen in the “Journal of the House of Representatives of the State of New Hampshire at Their Session Holden at the Capitol in Concord” issued in 1841 and describing the elections-related events of the autumn of 1840 [9] .

Purpose

In general, a checklist is a quality management tool, an aid to completing a complex task correctly and completely. It is an aid to recall, provides a reminder of the correct sequence, and uses the operator's knowledge and skill efficiently to ensure that no critical steps are omitted, even when the operator is under stress or has degraded attention due to fatigue or other distractions, It allows cross checking, keeps team members informed of the status of readiness, and can provide a legal record of a sequence of events to indicate due diligence. [10] [3] It differs from an instruction manual or operating manual in that it does not normally provide details on how to perform the steps, as it assumes that the operator is competent and familiar with each step.

Applications

A pilot of a DC-10 consulting his checklist DC10Checklist.jpg
A pilot of a DC-10 consulting his checklist

Checklists are used both to ensure that safety-critical system preparations are carried out completely and in the correct order, and in less critical applications to ensure that no step is left out of a procedure, or that all components have been accounted for, or as a means of recording biodiversity.

Safety critical systems

Checklists are used to help avoid accidental omission of important preparation of equipment and systems. These may be routine operations like pre-flight checks on an airliner or relatively infrequent occasions like commissioning a nuclear power station or launching a spacecraft. The value of checklists is proportional to the complexity of the system and the consequences of a system failure. They may also aid in mitigating claims of negligence in public liability claims by providing evidence of a risk management system being in place. A signed off checklist with a document describing the listed checks may be accepted as evidence of due diligence. Conversely, the absence of a mandatory checklist may be considered evidence of negligence.[ citation needed ]

Aviation and space flight safety

Checklists have long been a feature of aviation safety to ensure that critical items are not overlooked. [1] The best known example is the cockpit Pre-flight checklist, which is intended to ensure that the crew correctly configures the aircraft for flight on every flight. A normal checklist is used before critical flight segments, such as takeoff, approach and landing, which are the phases in which the highest incidence of accidents occur due to procedural error. Checklists are also used for troubleshooting, to identify and where practicable, correct malfunctions. They cannot substitute for pilot skill and learned and practiced immediate response to critical malfunctions, but are useful for mitigation attempts when time allows. [3]

Health care

In health care, particularly surgery, checklists may be used to ensure that the correct procedure is carried out on each patient. [11] Checklists have been used in healthcare practice to ensure that clinical practice guidelines are followed. An example is the WHO Surgical Safety Checklist developed for the World Health Organization and found to have a large effect on improving patient safety. [11] According to a meta-analysis after introduction of the checklist mortality dropped by 23% and all complications by 40%, but higher-quality studies are required to make the meta-analysis more robust. [12] Checklist use in healthcare has not always met with success and transferability between settings has been questioned. [13] A survey found them to have no statistical effect in a cohort of hospitals in the Province of Ontario in Canada. [14] In the UK, a study on the implementation of a checklist for provision of medical care to elderly patients admitting to hospital found that the checklist highlighted limitations with frailty assessment in acute care and motivated teams to review routine practices, but that work is needed to understand whether and how checklists can be embedded in complex multidisciplinary care. [15]

Underwater diving

In professional diving, checklists are used in the preparation of equipment for a dive, and to ensure that the diver and life support systems are fully prepared before they enter the water. To a lesser extent, checklists are used by a minority of recreational divers, and by a larger proportion of technical divers during pre-dive checks. [5] [16] Studies have shown checklists to be effective at reducing the number of errors and consequent incidents. [16]

Quality assurance applications

For information

Effectiveness of checklists

Ranapurwala et al. (2017) found: [16]

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: [20]

Types

Design

The design of a checklist should fit the purpose of the list. If a checklist is perceived as a top-down means to control behaviour by the organisational hierarchy it is more likely to be rejected and fail in its purpose. A checklist perceived as helping the operator to save time and reduce error is likely to be better accepted. This is more likely to happen when the user is involved in the development of the checklist. [16]

Rae et al. (2018) define safety clutter as "the accumulation and persistence of 'safety' work that does not contribute to operational safety", and state that "when 'safety' rules impose a significant and unnecessary burden on the performance of everyday activities, both work and safety suffer". [16]

An objective in checklist design that it should promote a positive attitude towards the use of the checklist by the operators. For this to happen it must be realistic, convenient and not be regarded as a nuisance. A checklist should be designed to describe and facilitate a physical procedure that is accepted by the operators as necessary, effective, efficient and convenient. [10]

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, [16] 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. [10]

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. [10]

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. [10]

Physical characteristics

Physical characteristics are things such as the actual size of the document, contrast, colour, and typography. The main factors in typography are legibility of text and readability in the conditions in which the document is expected to be used. [10]

Legibility of text involves the selection of characters to enable the reader to identify them quickly and positively discriminate them from other characters. Readability is the quality of the word or text which allows rapid recognition of single words, word groups, abbreviations, and symbols. [10]

Thousands of fonts are available, in two major groups: Roman (with serifs) and sans-serif. Research has shown that sans-serif is more legible than Roman as the absence of serifs presents simple and clean typeface. Arial or Helvetica are preferred. [10]

The consensus of researchers is that lowercase is more legible because the pattern of the whole word is more familiar, and the pattern of ascenders and descenders is helpful for recognition. The occasional use of uppercase words for emphasis or in acronyms is acceptable, particularly where this is the common usage. [10]

Font size is important for readability, especially for older operators. A font size between 14 and 20 points is recommended for reasonably well illuminated situations. Font size less than 10 points is not recommended. Checklists for use in poorly illuminated conditions should use a larger font for improved readability. Black text on a white background is generally preferred for best contrast, though in some cases a yellow background is acceptable. [10]

Other factors influencing readability and reducing error include both horizontal and vertical character spacing, stroke width and character height to width ratio, and line length. Italics reduce readability of large areas of text but are acceptable for emphasis of a few words. Bolding does not affect readability significantly, but is useful for emphasis, and is best used with discretion. The use of multiple type faces in body text can be confusing and significantly reduces readability, so should be avoided. Contrast is more useful than colour to provide visibility of characters. White on black can be useful if dark adaptation must be preserved, but is not optimum when illumination is good. If checklists are plastic laminated, an anti-glare finish should be used to prevent disruption by highlights. Opacity of the paper is important if printed on both sides or there is a possibility of backlighting. [22]

Content and layout

The workload and time available should be considered. [6] Each listed item should be necessary and together they should be sufficient. Only necessary instructions should be included. [20] A checklist should be as brief as possible without compromising clarity. [6] 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. [20] Numbering the items usually helps with place-keeping. [6] It may be useful to cross-reference the checklist to the standard procedure document, 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, but does not distract the user. Version number and date may be required to ensure that the current authorised version is in use. [20]

Ordering of the list should be logical. Where chronological order is important, it should be indicated by order on the list. 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. Grouping items which can be done at the same time or place, or by the same person, often improves efficiency. Where items to be checked are spatially distributed, an order minimising travel or search time is efficient. [20]

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. [20]

Format

Example checklist Closing a business checklist.svg
Example checklist

Checklists are often presented as lists with small checkboxes down the left hand side of the page. A small tick or checkmark is drawn in the box after the item has been completed. If practicable a check should not be split over two pages.[ citation needed ]

Other formats are also sometimes used. Aviation checklists generally consist of a system and an action divided by a dashed line, and lack a checkbox as they are often read aloud and are usually intended to be reused.[ citation needed ]

Some checklists must be signed off and kept as evidence, others may be re-usable. This may affect the format and materials. [20]

Errors

Long or confusing items, an inconvenient order, or any other characteristic that causes the users to perceive it as an obstacle will increase the chances that when constrained for time, the operators will revert to alternative methods, omit items or disregard the checklist entirely. [6]

Error conditions that may occur include:

History

During the National Transportation Safety Board (NTSB) hearings into the crash of Northwest Airlines Flight 255, human factors specialist Earl Wiener testified that he "did not know of any human factors research on how a checklist should be designed". NASA research into the matter concluded that as of 1989, there was basically no human factors research available anywhere specific to aircraft checklists. [10]

The NTSB recommended that the FAA investigate ways of presenting checklists that produce better performance. The Safety Board also recommended that the FAA should specify typography criteria for checklists for commercial operators. Researchers found problems with both the physical design and social issues associated with the use of checklists which degrades effective use. Two documents were produced by NASA, Degani, Asaf; Wiener, Earl L. (May 1990). Human Factors of Flight-Deck Checklists: The Normal Checklist. NASA Contractor Report 177549 (Report). NASA. and Degani, Asaf (December 1992). On the Typography of Flight-deck Documentation. NASA Contractor report # 177605 (Report). NASA.. This was followed by a document from the UK CAA: "CAP 676: Guidance on the Design, Presentation, and Use of Emergency and Abnormal Checklist". [10]

Use

Excessive dependence of checklists may hinder performance when dealing with a time-critical situation, for example a medical emergency or an in-flight emergency. Checklists should not be used as a replacement for common sense or necessary skill. Intensive training including rote-learning of checklists can help integrate use of checklists with more adaptive and flexible problem solving techniques.[ citation needed ]

Experimental work has shown that memorised checklists are less effective than written checklists in identifying unsafe conditions when time is not critical. [5]

See also

Related Research Articles

<span class="mw-page-title-main">Buddy check</span> Pre-dive safety checks carried out by two-diver dive teams

The buddy check is a procedure carried out by scuba divers using the buddy system where each dive buddy checks that the other's diving equipment is configured and functioning correctly just before the start of the dive. A study of pre-dive equipment checks done by individual divers showed that divers often fail to recognize common equipment faults. By checking each other's equipment as well as their own, it is thought to be more likely that these faults will be identified prior to the start of the dive. The correct use of a well designed written checklist is known to be more reliable, and is more likely to be used by professional divers, where it may be required by occupational health and safety legislation, and by technical divers, where the equipment checks are more complex.

Radiotelephony procedure includes various techniques used to clarify, simplify and standardize spoken communications over two-way radios, in use by the armed forces, in civil aviation, police and fire dispatching systems, citizens' band radio (CB), and amateur radio.

A cycle count is a perpetual inventory auditing procedure, where you follow a regularly repeated sequence of checks on a subset of inventory. Cycle counts contrast with traditional physical inventory in that a traditional physical inventory ceases operations at a facility while all items are counted. Cycle counts are less disruptive to daily operations, provide an ongoing measure of inventory accuracy and procedure execution, and can be tailored to focus on items with higher value, higher movement volume, or that are critical to business processes. Although some say that cycle counting should only be performed in facilities with a high degree of inventory accuracy, cycle counting is a means of achieving and sustaining high degrees of accuracy. Cycle counting can be used to identify root causes of problems in control processes and then monitor the effectiveness of the actions to eliminate the root causes. In contrast, identifying root causes of inventory errors, agreeing on actions to eliminate them to the point of perfecting control processes is virtually impossible with traditional inventory audit approaches.

In software project management, software testing, and software engineering, verification and validation is the process of checking that a software engineer system meets specifications and requirements so that it fulfills its intended purpose. It may also be referred to as software quality control. It is normally the responsibility of software testers as part of the software development lifecycle. In simple terms, software verification is: "Assuming we should build X, does our software achieve its goals without any bugs or gaps?" On the other hand, software validation is: "Was X what we should have built? Does X meet the high-level requirements?"

<span class="mw-page-title-main">Failure mode and effects analysis</span> Analysis of potential system failures

Failure mode and effects analysis is the process of reviewing as many components, assemblies, and subsystems as possible to identify potential failure modes in a system and their causes and effects. For each component, the failure modes and their resulting effects on the rest of the system are recorded in a specific FMEA worksheet. There are numerous variations of such worksheets. A FMEA can be a qualitative analysis, but may be put on a quantitative basis when mathematical failure rate models are combined with a statistical failure mode ratio database. It was one of the first highly structured, systematic techniques for failure analysis. It was developed by reliability engineers in the late 1950s to study problems that might arise from malfunctions of military systems. An FMEA is often the first step of a system reliability study.

Reliability engineering is a sub-discipline of systems engineering that emphasizes the ability of equipment to function without failure. Reliability is defined as the probability that a product, system, or service will perform its intended function adequately for a specified period of time, OR will operate in a defined environment without failure. Reliability is closely related to availability, which is typically described as the ability of a component or system to function at a specified moment or interval of time.

<span class="mw-page-title-main">Pilot error</span> Decision, action, or inaction by an aircraft pilot

In aviation, pilot error generally refers to an action or decision made by a pilot that is a substantial contributing factor leading to an aviation accident. It also includes a pilot's failure to make a correct decision or take proper action. Errors are intentional actions that fail to achieve their intended outcomes. The Chicago Convention defines the term "accident" as "an occurrence associated with the operation of an aircraft [...] in which [...] a person is fatally or seriously injured [...] except when the injuries are [...] inflicted by other persons." Hence the definition of "pilot error" does not include deliberate crashing.

<span class="mw-page-title-main">5S (methodology)</span> Workplace organisation method

5S is a workplace organization method that uses a list of five Japanese words: seiri (整理), seiton (整頓), seisō (清掃), seiketsu (清潔), and shitsuke (躾). These have been translated as 'sort', 'set in order', 'shine', 'standardize', and 'sustain'. The list describes how to organize a work space for efficiency and effectiveness by identifying and sorting the items used, maintaining the area and items, and sustaining the new organizational system. The decision-making process usually comes from a dialogue about standardization, which builds understanding among employees of how they should do the work.

Software assurance (SwA) is a critical process in software development that ensures the reliability, safety, and security of software products. It involves a variety of activities, including requirements analysis, design reviews, code inspections, testing, and formal verification. One crucial component of software assurance is secure coding practices, which follow industry-accepted standards and best practices, such as those outlined by the Software Engineering Institute (SEI) in their CERT Secure Coding Standards (SCS).

The system safety concept calls for a risk management strategy based on identification, analysis of hazards and application of remedial controls using a systems-based approach. This is different from traditional safety strategies which rely on control of conditions and causes of an accident based either on the epidemiological analysis or as a result of investigation of individual past accidents. The concept of system safety is useful in demonstrating adequacy of technologies when difficulties are faced with probabilistic risk analysis. The underlying principle is one of synergy: a whole is more than sum of its parts. Systems-based approach to safety requires the application of scientific, technical and managerial skills to hazard identification, hazard analysis, and elimination, control, or management of hazards throughout the life-cycle of a system, program, project or an activity or a product. "Hazop" is one of several techniques available for identification of hazards.

Human error assessment and reduction technique (HEART) is a technique used in the field of human reliability assessment (HRA), for the purposes of evaluating the probability of a human error occurring throughout the completion of a specific task. From such analyses measures can then be taken to reduce the likelihood of errors occurring within a system and therefore lead to an improvement in the overall levels of safety. There exist three primary reasons for conducting an HRA: error identification, error quantification, and error reduction. As there exist a number of techniques used for such purposes, they can be split into one of two classifications: first-generation techniques and second generation techniques. First generation techniques work on the basis of the simple dichotomy of 'fits/doesn't fit' in the matching of the error situation in context with related error identification and quantification and second generation techniques are more theory based in their assessment and quantification of errors. HRA techniques have been used in a range of industries including healthcare, engineering, nuclear, transportation, and business sectors. Each technique has varying uses within different disciplines.

Functional safety is the part of the overall safety of a system or piece of equipment that depends on automatic protection operating correctly in response to its inputs or failure in a predictable manner (fail-safe). The automatic protection system should be designed to properly handle likely systematic errors, hardware failures and operational/environmental stress.

<span class="mw-page-title-main">Preflight checklist</span> List of tasks performed prior to takeoff

In aviation, a preflight checklist is a list of tasks that should be performed by pilots and aircrew prior to takeoff. Its purpose is to improve flight safety by ensuring that no important tasks are forgotten. Failure to correctly conduct a preflight check using a checklist is a major contributing factor to aircraft accidents.

The World Health Organization (WHO) published the WHO Surgical Safety Checklist in 2008 in order to increase the safety of patients undergoing surgery. The checklist serves to remind the surgical team of important items to be performed before and after the surgical procedure in order to reduce adverse events such as surgical site infections or retained instruments. It is one affordable and sustainable tool for reducing deaths from surgery in low and middle income countries.

Human factors are the physical or cognitive properties of individuals, or social behavior which is specific to humans, and which influence functioning of technological systems as well as human-environment equilibria. The safety of underwater diving operations can be improved by reducing the frequency of human error and the consequences when it does occur. Human error can be defined as an individual's deviation from acceptable or desirable practice which culminates in undesirable or unexpected results. Human factors include both the non-technical skills that enhance safety and the non-technical factors that contribute to undesirable incidents that put the diver at risk.

[Safety is] An active, adaptive process which involves making sense of the task in the context of the environment to successfully achieve explicit and implied goals, with the expectation that no harm or damage will occur. – G. Lock, 2022

Dive safety is primarily a function of four factors: the environment, equipment, individual diver performance and dive team performance. The water is a harsh and alien environment which can impose severe physical and psychological stress on a diver. The remaining factors must be controlled and coordinated so the diver can overcome the stresses imposed by the underwater environment and work safely. Diving equipment is crucial because it provides life support to the diver, but the majority of dive accidents are caused by individual diver panic and an associated degradation of the individual diver's performance. – M.A. Blumenberg, 1996

Permit-to-work (PTW) refers to a management system procedure used to ensure that work is done safely and efficiently. It is used in hazardous industries, such as process and nuclear plants, usually in connection with maintenance work. It involves procedured request, review, authorization, documenting and, most importantly, de-conflicting of tasks to be carried out by front line workers. It ensures affected personnel are aware of the nature of the work and the hazards associated with it, all safety precautions have been put in place before starting the task, and the work has been completed correctly.

<span class="mw-page-title-main">Scuba gas management</span> Logistical aspects of scuba breathing gas

Scuba gas management is the aspect of scuba diving which includes the gas planning, blending, filling, analysing, marking, storage, and transportation of gas cylinders for a dive, the monitoring and switching of breathing gases during a dive, efficient and correct use of the gas, and the provision of emergency gas to another member of the dive team. The primary aim is to ensure that everyone has enough to breathe of a gas suitable for the current depth at all times, and is aware of the gas mixture in use and its effect on decompression obligations, nitrogen narcosis, and oxygen toxicity risk. Some of these functions may be delegated to others, such as the filling of cylinders, or transportation to the dive site, but others are the direct responsibility of the diver using the gas.

Diving safety is the aspect of underwater diving operations and activities concerned with the safety of the participants. The safety of underwater diving depends on four factors: the environment, the equipment, behaviour of the individual diver and performance of the dive team. The underwater environment can impose severe physical and psychological stress on a diver, and is mostly beyond the diver's control. Equipment is used to operate underwater for anything beyond very short periods, and the reliable function of some of the equipment is critical to even short-term survival. Other equipment allows the diver to operate in relative comfort and efficiency, or to remain healthy over the longer term. The performance of the individual diver depends on learned skills, many of which are not intuitive, and the performance of the team depends on competence, communication, attention and common goals.

Diving procedures are standardised methods of doing things that are commonly useful while diving that are known to work effectively and acceptably safely. Due to the inherent risks of the environment and the necessity to operate the equipment correctly, both under normal conditions and during incidents where failure to respond appropriately and quickly can have fatal consequences, a set of standard procedures are used in preparation of the equipment, preparation to dive, during the dive if all goes according to plan, after the dive, and in the event of a reasonably foreseeable contingency. Standard procedures are not necessarily the only courses of action that produce a satisfactory outcome, but they are generally those procedures that experiment and experience show to work well and reliably in response to given circumstances. All formal diver training is based on the learning of standard skills and procedures, and in many cases the over-learning of the skills until the procedures can be performed without hesitation even when distracting circumstances exist. Where reasonably practicable, checklists may be used to ensure that preparatory and maintenance procedures are carried out in the correct sequence and that no steps are inadvertently omitted.

<span class="mw-page-title-main">Pan Am Flight 799</span> 1968 airplane crash

Pan Am Flight 799 was an international cargo flight from Los Angeles International Airport to Cam Ranh Airport in South Vietnam that crashed on December 26, 1968, near Anchorage, Alaska. The aircraft involved was a Boeing 707-321C aircraft operated by Pan American World Airways. All three crew members died in the crash.

References

  1. 1 2 Higgins, W.Y.; Boorman, D.J. (2016). "An analysis of the effectiveness of checklists when combined with other processes, methods and tools to reduce risk in high hazard activities". Boeing Tech J.
  2. Puscasu, Alex (14 December 2020). "Checklist, what is it and why use it? – Ape" . Retrieved 2021-07-23.
  3. 1 2 3 Degani, Asaf; Wiener, Earl L. (May 1990). Human Factors of Flight-Deck Checklists: The Normal Checklist (PDF). NASA Contractor Report 177549 (Report). NASA.
  4. "Schedule". dictionary.cambridge.org. Archived from the original on 2015-08-15. Retrieved 2021-07-23.
  5. 1 2 3 Ranapurwala, Shabbar Ismailbhai (2014). Prevention of scuba diving mishaps using a predive checklist:A cluster randomized trial (PDF). PhD dissertation (Report). University of North Carolina.
  6. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Safety Regulation Group (30 August 2006). Guidance on the Design, Presentation and Use of Emergency and Abnormal Checklists (PDF). CAP 676 (Report). CAA. ISBN   0-11790-637-9.
  7. Ludders, John W.; McMillan, Matthew (2016-11-18). Errors in Veterinary Anesthesia (1 ed.). Wiley. doi:10.1002/9781119259749.app5. ISBN   978-1-119-25971-8.
  8. "checklist, n. meanings, etymology and more | Oxford English Dictionary".
  9. "Pilots did not invent checklists in 1935. When did they appear?". So List. 2024-04-12. Retrieved 2024-10-23.
  10. 1 2 3 4 5 6 7 8 9 10 11 12 Lau, Stuart "Kipp" (1 March 2023). "Best Practices in Checklist Design Account for Human Limitations". AINonline: Business aviation. Retrieved 13 March 2023.
  11. 1 2 Haynes, A.; Gawande, A. (January 2009). "A surgical safety checklist to reduce morbidity and mortality in a global population". New England Journal of Medicine. 360 (5): 491–499. doi: 10.1056/NEJMsa0810119 . PMID   19144931. S2CID   2639397.
  12. Bergs, J.; Hellings, J.; Cleemput, I.; Zurel, Ö.; De Troyer, V.; Van Hiel, M.; Demeere, J.L.; Claeys, D.; Vandijck, D. (Feb 2014). "Systematic review and meta-analysis of the effect of the World Health Organization surgical safety checklist on postoperative complications". The British Journal of Surgery. 101 (3): 150–8. doi: 10.1002/bjs.9381 . PMID   24469615.
  13. Dixon-Woods, Mary; Leslie, Myles; Tarrant, Carolyn; Bion, Julian (20 June 2013). "Explaining Matching Michigan: an ethnographic study of a patient safety program". Implementation Science. 8 (1): 70. doi: 10.1186/1748-5908-8-70 . PMC   3704826 . PMID   23786847.
  14. Urbach, D.R.; Govindarajan, A; Saskin, R.; Wilton, A.S.; Baxter, N.N. (March 2014). "Introduction of surgical safety checklists in Ontario, Canada". N. Engl. J. Med. 370 (11): 1029–38. doi: 10.1056/NEJMsa1308261 . PMID   24620866.
  15. Papoutsi, Chrysanthi; Poots, Alan; Clements, Jake; Wyrko, Zoe; Offord, Natalie; Reed, Julie E (5 January 2018). "Improving patient safety for older people in acute admissions: implementation of the Frails afe checklist in 12 hospitals across the UK". Age and Ageing. 47 (2): 311–317. doi:10.1093/ageing/afx194. PMC   6016694 . PMID   29315375.
  16. 1 2 3 4 5 6 7 8 9 10 Hodges, Vallorie J.; Middleton, Crispin; Lock, Gareth. Côté, I.M.; Verde, E.A. (eds.). Capturing the Stupid Stuff: Using Checklists to Improve Performance in Scientific Diving. Diving for Science 2019: Proceedings of the American Academy of Underwater Sciences 38th Symposium. via thehumandiver.com.
  17. "Janitorial Cleaning Checklist". www.brcompany.com.au. Retrieved 14 March 2023.
  18. "World Checklist of Selected Plant Families". apps.kew.org. Retrieved May 18, 2016.
  19. "Catalogue of Life - 2019 Annual Checklist : Taxonomic tree". www.catalogueoflife.org. Retrieved 14 March 2023.
  20. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Courtnell, Jane (18 December 2019). "Making Checklists: Our Top 5 Tips From Pros Around The World". www.process.st.
  21. 1 2 3 4 5 Fox, Justin (23 February 2010). "What Sort of Checklist Should You Be Using?". Harvard Business Review.
  22. Degani, Asaf (December 1992). On the Typography of Flight-deck Documentation (PDF). NASA Contractor report # 177605 (Report). NASA.