Checklists that work

In many situations, professional negligence claims arise not from ignorance of the law, but from preventable omissions – the step that was always done, until the day it wasn’t.

Examples from claims data include:

• the limitation period that slipped past during a busy month
• the document that wasn’t executed correctly
• failure to ask if the purchaser is an Australian citizen or a foreigner.

These are not failures to acknowledge, but failures of process. And process failures are precisely what checklists are designed to prevent.

In his 2009 book The Checklist Manifesto, surgeon and public health researcher Atul Gawande documented how aviation and surgery dramatically reduced errors by committing to disciplined checklist use. In these high-stakes, highly complex fields, Gawande noted that it was not that professionals lacked skill or training but that, under pressure, even expert practitioners missed steps. A simple, well-designed checklist changed the outcomes in these fields. The same logic applies to legal practice.

Checklists are among the most powerful and accessible risk management tools available to lawyers. They are also one of the most underused. While most firms have them, far fewer use them consistently. Checklists often sit at the front of a paper file, unmarked, or they live in a digital folder that no one opens. Good intentions at the point of creation do not necessarily translate into good habits at the point of practice.

A paper checklist pinned inside a physical file serves a different function to one embedded in a practice management system, but each carries its own risks of neglect. Whatever the format, the core problem remains the same: a checklist only reduces risk when it is actively used, regularly reviewed and genuinely embedded in how a matter is run and how a practitioner operates.

Lawyers operate in an environment of competing demands, tight deadlines and complex, overlapping matters. In that context, human memory is not a reliable system. Cognitive load, interruptions and time pressure all increase the likelihood that a step will be skipped or an issue will be missed. This is not a reflection of competence. It is a feature of how the human brain works under pressure, and it affects experienced practitioners as much as junior ones.

A well-designed checklist removes reliance on memory at critical points in a matter and replaces it with a reliable, repeatable activity that embeds a professional standard. As the law and the practice of law become more complex, the systematic approach built into checklists becomes a critical risk management control that protects both the practitioner and the client.

That said, a checklist that sits unused in a file or folder provides no protection at all. The risk management value of a checklist is entirely dependent on it being actively and intelligently used. Checklists should not be completed as an afterthought, ticked without reading or treated as a bureaucratic formality. A checklist is a powerful tool when completed in good faith, at the right point in a matter, by someone who has genuinely engaged with each item.

At the root of most checklist failures are the same few problems. Ruthless prioritisation at the drafting stage produces a checklist that practitioners will pick up and complete. The following is a list of issues to consider when designing your checklists.

Length

Problem: The checklist is too long to be practical. If working through a checklist takes more than a few minutes, it will be deferred, abbreviated or abandoned when a matter is busy, which is when the risk of omission is highest. The goal is not to document every conceivable step or issue in a matter, but to capture the critical ones, where failure has consequences and where memory alone is not a sufficient safeguard.

Specificity

Problem: The checklist is too generic to be meaningful. A generic checklist that applies loosely to every matter type is a checklist that fits none of them well. Checklists should be designed for specific matters and issues, and should reflect the scale and structure of the firm. A sole practitioner and a large corporate team will have different workflows, supervision structures and risk profiles. Likewise, a checklist designed for a senior solicitor will be different to one for a paralegal, even when those two checklists appear at the same juncture of a workflow. A checklist that ignores these differences will feel irrelevant to the people expected to use it.

Embeddedness

Problem: The checklist is not connected to the workflow of the matter. It is critical to be precise about when in the process a checklist is designed to be used. Consider the outcome required from the checklist and the risk that the checklist is created to avoid. Knowing which type of checklist you are designing (read-do [process-oriented] or do-confirm [safetyoriented]) helps clarify the language, the timing, and where in the workflow the checklist should appear.

Language

Problem: The checklist requires interpretation and usability friction. Checklists should be written in plain, direct language that tells the reader exactly what to do, check or consider. This removes ambiguity and speeds completion. Each item should be a clear action or a clear question, not a topic heading that leaves the practitioner to work out what is actually required. Internal shorthand, firm-specific acronyms or procedural jargon should be avoided in a checklist.

Reflection

Problem: The checklist is just a list of tasks. Checklists should contain decision points. A task item confirms that something was done. A decision point requires the practitioner to ask:

• Has the client’s capacity been confirmed?
• Has the scope of the retainer been reviewed considering what has emerged?
• Is there anything on this file that needs to be escalated?

These types of prompts cannot be ticked without genuine engagement, and that engagement is where the real risk management value lies.

While the unused checklist is ineffective, the next trap is the checklist that is completed but not genuinely engaged with. Items are ticked in a few seconds at the end of a matter or populated from memory rather than by checking the file. The document looks complete, but the risk it was designed to manage remains unaddressed. This is arguably more dangerous than an unused checklist, because it creates a false record of process.

The key ingredient for engagement is that every checklist should include a version of the question: “Am I advancing the client’s interests?” This reflective question functions as a warning system. At its core, this question reconnects the practitioner to the purpose of the matter. Checklists can, if poorly designed, reduce legal practice to a series of administrative steps. The reflective question insists on something more – that behind every item on the list is a client, with real interests, who is depending on the practitioner to do more than complete the paperwork. Even checklists used on file reviews can generate reflection and engagement towards the client.

A checklist is only as good as the habit behind it. The firms that get the most value from checklists are those where checklists are treated as a genuine part of practice, not a formality to be satisfied. That means keeping them short enough to use under pressure, tailored enough to be meaningful, and visible enough to be consulted at the right moment.

Checklists that work include both procedural steps and reflective questions that consider whether the client’s interests are honestly being advanced. Ultimately, getting the most out of checklists requires a culture where the checklist is truly valued for the advantages that they provide.