Checklists and You!!!

Why Checklists Are Not Optional: The Case Every Construction Leader Needs to Hear

There is a version of the checklist conversation in construction that goes like this: we are professionals, we have been doing this for years, we do not need a piece of paper to tell us what to do. That version of the conversation ends with inconsistent quality, preventable rework, and a project team that is relying on tribal knowledge and individual memory to execute work that a simple written standard could have protected. The argument against checklists in construction is not actually an argument for expertise. It is an argument for hoping that experienced people never have bad days, get distracted, skip steps under pressure, or forget what they learned before handing off to the next crew. That hope is not a quality system. It is a wish.

The Problem That Repeats When Checklists Disappear

The pattern is familiar to anyone who has managed field quality on a construction project. The crew installs the in-wall rough-in. The work looks complete. The area is closed up. Three weeks later, during a ceiling inspection, someone notices that putty pads were missed on a portion of the in-wall conduit runs. The drywall is already in. Remediation begins. The schedule absorbs the hit. The cost absorbs the hit. And the team has a conversation about how to prevent this from happening again. The conversation usually ends with a verbal reminder, not a checklist. And six months later, on a different floor with a different crew, the same type of miss occurs because the verbal reminder did not travel with the work.

The root cause of that failure is not a careless crew. It is an absent system. The in-wall inspection did not have a written checklist because someone decided that experienced electricians know to install putty pads without being reminded. That decision sounds reasonable and it produces rework. Every time.

The System Failed, Not the Crew

This is worth stating plainly because the instinct when a quality miss is discovered is to look for who did not do their job. The question to ask instead is whether the crew had a written standard that specified every step required for a complete and correct installation. If the answer is no, the system failed the crew. Experienced workers know how to do the work. What checklists protect against is not incompetence. They protect against the natural human tendency to skip steps under time pressure, to rely on memory in conditions that are not ideal for memory, and to assume that the person who precedes you on a task covered everything that needed to be covered. Those vulnerabilities exist at every skill level, in every industry, in every person who has ever worked under pressure.

The Industries That Already Proved It

Aviation figured this out through painful experience. Early in the development of complex aircraft, Boeing encountered failures and accidents that traced back to the lack of standard work and standardized checklists for operating aircraft that were too complex to be managed from memory alone. The response was to develop and mandate checklists for every phase of operation: preflight, takeoff, cruise, approach, landing, and emergency procedures. The result, combined with other improvements in training and engineering, has produced a commercial aviation safety record in the United States that is remarkable by any standard. The discipline of the checklist is not a small contributor to that record.

Medical practice tells the same story from a different angle. Hospital-acquired infections, surgical errors, and medication mistakes dropped significantly in facilities that adopted standardized checklists and standard work protocols for procedures that experienced practitioners had been performing for years without written guidance. One specific example that Jason Schroeder cites directly: inclining a pneumonia patient’s bed is a step that dramatically reduces the risk of the patient’s lungs being overwhelmed by fluid. That knowledge existed in medicine long before it became a standard item on a pneumonia care checklist. The difference between it being known and it being done consistently was a checklist.

The question every construction leader should sit with is this: if you would want your pilot to use a checklist, and your surgeon to use a checklist, and your pharmacist to use a checklist, and the people who handle your food to use a checklist, what exactly is the argument for your installation crews not using one?

What Good Checklists Actually Do

The objection to checklists is usually not that they are wrong in principle but that they are burdensome in practice. Too many items. Rarely referenced. Recreated from scratch every time instead of being standardized and reused. Formatted in a way that makes them feel like paperwork rather than tools. All of those are real problems with how checklists are often implemented, and none of them are arguments against the concept. They are arguments for doing checklists well rather than abandoning them.

A good checklist in construction does several specific things. It captures the lessons that were learned the hard way by the people who came before, so that the crew doing the installation today does not have to relearn them through a quality miss. It creates a shared definition of done that the foreman, the superintendent, the inspector, and the downstream trade can all reference and confirm against the same standard. It makes quality a crew accountability rather than a management inspection, because the crew has the checklist in hand and knows exactly what complete looks like before the next crew enters the space. And it creates a repeatable standard that can be improved over time as new lessons emerge, rather than relying on the individual knowledge of whoever happens to be working that day.

What These Look Like on a Construction Site

The crew that enters a zone with a clear feature of workboard and a relevant checklist is a crew that does not have to reconstruct the definition of right from memory or from the foreman’s verbal instructions at the start of the shift. The checklist does not replace the foreman’s expertise. It protects against the parts of the installation that expertise alone cannot guarantee under field conditions.

Here are examples of where checklists directly protect quality in construction:

• In-wall rough-in inspections: conduit fastening, putty pads, back box installation, firestopping, circuit labeling, and any penetration sealing required before drywall can proceed
• Concrete placement: slump testing, form inspection, reinforcing bar inspection, pre-pour checklist items required by the structural drawings, and wet weather or temperature protocols when applicable
• Ceiling inspections: overhead coordination clearances, hanger wire installation at required intervals, main runner and cross-tee connections, tile or panel placement before accessible areas are completed
• Preflight checks for heavy equipment and temporary power systems: safety devices, fluid levels, inspection documentation, and operator certification confirmation

None of those lists are long. None of them are complicated. All of them represent the difference between work that closes out clean and work that comes back for rework.

The CFO Who Never Misses Payroll

Jason tells the story of a leadership team meeting where the company’s chief financial officer listened to the conversation about checklists and had a visible moment of recognition. She had never in ten years been late with payroll. Never missed a name. Never made a material error. And then she realized, out loud in that meeting, that she uses a checklist every single time she processes payroll. Every time. Not because she is not expert at her job. Because the checklist is what makes her expertise reliable rather than variable. Her process includes confirming every employee’s name, verifying hours against her established system, and running through a sequence of steps that she has followed consistently for a decade. The checklist is not a crutch. It is what makes a decade of error-free performance possible.

That is the point. The checklist does not replace the professional. It makes the professional’s performance reproducible regardless of the conditions on any given day.

The Art That Construction Cannot Afford to Lose

The risk in construction right now is that checklists are being dismissed in favor of digital tools that claim to replace them, or in favor of the confidence that comes with years of experience, or simply because the pace of work does not feel like it leaves time to reference a written standard at the end of every installation. All of those feel like reasonable trade-offs in the moment and they cost projects significantly over time.

Jason Schroeder grew up at Hensel Phelps where checklists were part of the professional culture. Port inspection checklists. In-wall inspection checklists. Checklists for each critical phase of work, embedded in the field and office guide that new team members were expected to read and use. That culture produced a generation of superintendents and project managers who understood quality at the source as a discipline rather than an aspiration. When that culture disappears from a company or a project, the quality that depended on it disappears with it, quietly and gradually, until a rework problem or an inspection failure makes the cost visible.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Bring the Checklist Back

The challenge from this episode is simple. Identify one scope of work on your current or upcoming project that would benefit from a written checklist and does not have one. Build it by working backward from what a failed installation looks like and specifying the steps that prevent each failure mode. Make it short, specific, and relevant to the work your crew is actually doing. Put it on the feature of workboard where the crew can reference it during the installation, not in a file on someone’s computer. And then use it consistently, every time, on every floor, with every crew, without exception. As Atul Gawande wrote in The Checklist Manifesto: under conditions of complexity, not only are checklists a help, they are required for success. Construction is one of the most complex endeavors human beings undertake. The checklist is not optional.

On we go.

FAQ

Why do experienced construction professionals sometimes resist using checklists?

Because expertise creates the feeling that a written standard is redundant. When someone has installed the same scope of work dozens of times, referencing a checklist can feel unnecessary and even slightly insulting, as if the checklist implies they do not know what they are doing. That feeling is understandable and it is also incorrect. What checklists protect against is not incompetence. They protect against the natural human tendency to skip steps under time pressure, to rely on memory in suboptimal conditions, and to assume that everything was covered when some element was missed during a moment of distraction or fatigue. Those vulnerabilities exist at every skill level, including expert level.

What makes a checklist effective in a field construction setting?

Effective construction checklists are short, specific, and relevant to the actual work the crew is performing in the actual conditions of the current project. They capture the specific failure modes that have occurred before, so the crew can confirm those steps are covered before moving on. They are formatted for field use, laminated if possible, and posted at the point of work rather than filed in an office. They are reviewed and updated when new lessons emerge. And they are used consistently, by every crew, every time, without exceptions made for experience level or time pressure. The most useless checklist is one that exists as a document but is never referenced during the work it is meant to govern.

How do checklists connect to the concept of quality at the source?

Quality at the source means that the entire production team is oriented toward installing work correctly the first time rather than inspecting defects out after the fact. Checklists are one of the primary tools that make quality at the source operational rather than aspirational. When a crew has a checklist that specifies every step required for a complete and correct installation, they have the ability to confirm their own work against the standard before closing up the area or moving to the next zone. The checklist is what makes quality the crew’s accountability rather than the superintendent’s inspection task. It also allows any worker on the crew to stop the work and confirm something is correct, which is the field application of the Andon stop-and-signal principle.

What is the connection between checklists and standard work?

Standard work defines the best known method for a given installation, made visible and consistent for every crew member. A checklist is one of the primary expressions of standard work in the field: it captures the sequence of steps, the quality criteria for each step, and the confirmation that each step was completed before the next one begins. The feature of workboard that Jason Schroeder describes in other episodes combines cycle time, work sequence, and standard inventory with quality checkpoint confirmation. The checklist portion of that board is what allows the crew to execute the standard work consistently rather than relying on each crew member’s individual interpretation of what complete looks like.

How should a construction team get started if they do not currently use checklists?

Start with one scope and one phase. Identify the installation that creates the most rework or the most downstream problems when it is not done correctly. Work backward from the specific failure modes: what was missed, what was installed incorrectly, what was skipped under time pressure. Build a checklist that specifies the steps that prevent each of those failures. Keep it to a single page or less. Put it on the feature of workboard for that scope. Use it for the next three installation cycles and refine it based on what the crew actually references versus what they already do automatically. Expand from there to other scopes as the habit develops. The goal is not a hundred-item master document. It is a short, useful, field-relevant tool that the crew actually picks up and uses at the end of each installation sequence.