Do Your Crews Actually Know What They Are Installing?

There is a simple question at the heart of every quality control conversation: does the crew know what to build, and are they building it? That is it. Everything else in quality management flows from those two questions. Jason Schroeder breaks this down in one of his most practical episodes yet, drawing on years of field experience to show how a simple three artifact system can replace the complexity that is failing most projects today.

Where This System Came From

Jason learned quality control at Hensel Phelps, one of the most disciplined builders in the industry. Their process, adapted from an Army Corps of Engineers framework, was systematic and regimented. The principle he took from it was straightforward: if people follow the process, the process works. Every time. The problem most organizations face is not that quality control is too complicated to execute. It is that the systems they have built are too complicated to scale. A 65-page manual that no one finishes reading is not a quality control system. It is a liability document sitting on a shelf.

The solution is to shrink the system down to what can actually be followed, understood, and used in the field by the people doing the work.

Three Artifacts, One System

Quality control at its foundation requires only three things. A trigger, a process, and an output. Jason frames these as three artifacts.

The first artifact is your team weekly tactical meeting with a quality agenda. This is where the system gets activated each week. Every scope of work that is approaching or in progress passes through a quality point of release chart during this meeting. Each scope moves through defined stages, and it cannot advance to the next stage until the previous one is verified. This keeps the entire project team accountable without requiring individual heroics.

The second artifact is the quality process itself. Jason organizes this around a principle he has used throughout his career: plan it first, build it right, finish as you go. In practice this means the process runs through six defined stages. Teaming and scope selection ensures the right contractor has the right scope. The pre-mobilization meeting introduces the contractor to the deliverables they will need before work starts. The pre-construction meeting collects those deliverables, reviews drawings and specifications, sets safety and quality expectations, and leaves the foreman fully prepared. The initial inspection confirms the crew is heading in the right direction from the very first installation. Follow-up inspections keep the work on track throughout the scope. And the rolling completion list closes out every item before the contractor demobilizes.

The third artifact is the feature of workboard. This is the most important output of the entire system and the one most often missing from project sites. It is a visual, single-page document that shows the crew exactly what a correct installation looks like, step by step.

What a Feature of Workboard Actually Contains

A feature of workboard is not a lengthy specification document. It is a visual installation guide designed to be used in the field by the people doing the work. On the left side are the key items for the installation: safety requirements, substrate acceptance criteria, installation methods, and the specific quality checkoff items that must be verified before the work is concealed or completed. In the middle and to the right are pictures showing what each stage of the installation should look like when done correctly.

The power of this document is that it puts the answer to “am I doing this right?” directly in the hands of the person doing the work. Before a ceiling gets closed, before a trench gets backfilled, before drywall gets covered, the crew checks the list. If every item is verified, the work can proceed. If it is not, the work stops until it is.

Here are the key questions every feature of workboard should answer for the crew doing the work:

• Do we know what materials are required and have they been inspected on arrival?
•  Have submittals been approved and are drawings on site?
•  Do we know the installation sequence and what each step looks like?
•  What are the specific checkoff items that must be verified before concealment?
•  Has the substrate been accepted before we start?

A note worth carrying: if a crew does not have this document in front of them, they are guessing. And guessing on a construction project is how rework happens.

Connecting Quality to the Schedule

One of the most important points Jason made is that quality control does not operate in isolation from the schedule. In a well-run Takt plan, the schedule itself triggers the entry of each scope into the quality process. There is a buffer built in before any scope begins, and that buffer is what allows the pre-mobilization meeting and the pre-construction meeting to happen at the right time. If those meetings are skipped or compressed, the quality process collapses before the work even starts.

This is the connection most organizations miss. They treat quality control as a separate program that runs alongside the schedule. Jason builds it directly into the schedule so that the system runs automatically as the project flows forward. The team weekly tactical reviews which scopes are entering the system, which are in progress, and which need to be closed out. Thirty minutes of that meeting dedicated to this process keeps the entire quality system running without a separate quality manager chasing people down.

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

The Challenge

If your crew is in the field right now without a feature of workboard, the first step is straightforward. Build one for the next scope entering the system and use it as the template for every scope that follows. If your team weekly tactical is not currently spending thirty minutes reviewing the quality point of release chart, add it to the agenda this week. Quality does not require complexity. It requires a trigger, a process, and a visual output that gives the crew what they need to build it right the first time.

“Quality is everyone’s responsibility.” W. Edwards Deming

On we go.

FAQ

Why is a 65-page quality manual a problem?

Because no one finishes reading it, and even if they do, they cannot use it in the field. Jason’s point is that a quality system has to be as accessible and usable as the tools the crew is already using. If the system cannot be understood quickly and applied visually, it will not be followed. The goal is a system that can scale across every scope on the project without requiring a specialist to interpret it every time.

What is a point of release chart?

It is a tracking tool used in the team weekly tactical to manage every scope of work through the quality process. Each scope enters the chart when the schedule triggers it and cannot advance to the next phase until the previous phase is completed and verified. The stages run from work order execution through pre-mobilization, pre-construction, initial inspection, follow-up inspections, and final closeout. It functions like a visual scoreboard for quality across the entire project.

How does quality control connect to Takt planning?

The schedule buffers built into a Takt plan are what create the space for quality meetings to happen at the right time. When a scope is three weeks from starting, the pre-construction meeting needs to happen. If the foreman has not reviewed the drawings and specifications by that point, the meeting gets cancelled and rescheduled with enough lead time to fix it. The Takt schedule makes this possible because it gives everyone visibility into what is coming and when. Without that visibility, quality meetings get compressed or skipped entirely.

What if a trade partner resists the pre-construction meeting process?

Jason’s answer to this is embedded in the system itself. The pre-mobilization meeting happens weeks before the pre-construction meeting and sets the expectation for what the contractor needs to bring. By the time the pre-construction meeting arrives, the deliverables are already requested and the contractor knows what is expected. Resistance usually comes from surprise. The system eliminates surprise by building in enough lead time that no contractor can reasonably claim they were not prepared.