A CHECKLIST FOR CHECKLISTS

(1) Development (2) Drafting (3) Validation

 Do you have clear, concise Does the Checklist: Have you:

objectives for your checklist?  Use natural breaks in  Tested/trialed the checklist
workflow (pause points)? with front line users (either in
Is each item: a real or simulated situation)?
 Use simple sentence structure
 A critical safety step and in and basic language?  Modified the checklist in
great danger of being response to repeated trials?
 Have a title that reflects its
missed?
objectives?
 Not adequately checked by Does the checklist:
 Have a simple, uncluttered,
other mechanisms?  Fit the flow of work?
and logical format?
 Actionable, with a specific  Detect errors at a time when
 Fit on one page?
response required for each they can still be corrected?
item?  Minimize the use of color?
 Designed to be read aloud as  Can the checklist be
Is the font: completed in a reasonably
a verbal check?
 Sans serif? brief period of time?
 One that can be affected by
the use of a checklist?  Upper and lower case?
 Have you made plans for
 Large enough to be read
Have you considered: future review and revision of
easily?
the checklist?
 Adding items that will improve  Dark on a light background?
communication among team
members?  Are there fewer than 10 items
 Involving all members of the per pause point?
team in the checklist creation Source: Gawande, A. (2009), The checklist
process?  Is the date of creation (or manifesto: how to get things right.
revision) clearly marked?

Caution: A checklist is NOT a teaching tool or an algorithm. Page 1 of 1 Last updated: 14 Jan 2010