10/08/2026
I wonder how many architects, engineers, and construction managers actually have a standardized Construction Inspection and Verification Process, supported by structured QA/QC forms, that they consistently use across their projects.
And perhaps the more interesting question is this:
If you had one, what could you actually do with it?
Those who have worked with me know that, at the heart of how we define and understand construction scope, two things are fundamental:
(1) the building element, and
(2) its specific location.
This is closely aligned with how the Construction Management Association of America (CMAA) approaches work for scheduling and programming, where an activity is generally defined by an action applied to something at a particular location.
But scope and work, while closely related, are not completely synonymous.
Scope can move up and down the different levels of decomposition.
Work, on the other hand, begins at the level where resources can actually be defined, assigned, scheduled, measured, and controlled.
For me, work should at the very least be defined at Level 5 – Assembly Groups, but ideally at Level 6 – Individual Assemblies / Work Package Assemblies (WPA).
We call these Work Package Assemblies.
I have always advocated moving away from defining scope primarily at Levels 8 and 9—Parts and Materials—which is where many professionals tend to focus.
At those levels, we are no longer really defining the scope itself.
We are already describing the resources contained within the scope.
That distinction is important.
Scope is ultimately what we have to define and control if we are to truly deliver projects successfully.
And at minimum, that control should reach the WPA.
If quality is fundamentally about conformance to scope and requirements, then inspection, verification, review, and acceptance should also be structured around the WPA.
A WPA should always be traceable.
Think of the WPA as the basic container of construction scope.
Inside that container are its components, parts, materials, and material properties or metadata.
This is also why I have never been comfortable with QA/QC systems that begin and end with generic material checklists.
The better question is not simply:
“Was the material acceptable?”
The better questions are:
What assembly is this material part of?
Where is that assembly located?
What requirements govern it?
What exactly was inspected or verified?
What was the result?
And where is the evidence?
Two of the basic forms we have historically used are the PPD and the RDS—and I hope some of my former apprentices and interns still remember them.
Both follow the same fundamental logic:
Building element + actual location.
Our current inspection and verification process builds on that same thinking.
The process is aligned with the logic of the ASTM Property Condition Assessment process, but adapted specifically to the construction stage of the asset life cycle.
Some versions of these tools are used during planning. The versions I have been developing more recently are intended specifically for construction-stage inspection, verification, and quality control.
The objective is actually very simple:
The same structure used to define scope should carry through planning, ex*****on, inspection, verification, acceptance, turnover, and eventually the asset record.
That means quality should never become a disconnected checklist.
Quality must remain traceable to scope.
And this is where it becomes interesting.
If every inspection, verification, nonconformance, correction, acceptance, photo, test result, and record were tied to a specific Work Package Assembly at a specific location, what else could you do with that information?
Could you use it for quality control?
Progress measurement?
Punchlisting?
Payment validation?
Claims?
Turnover?
Defects management?
Maintenance?
Asset records?
Contract administration?
Project closeout?
That is the part I am interested in exploring further.
Because once scope becomes structured and traceable, QA/QC may be only one of the things the same system can control.
So here is the question:
If you had a standardized, assembly-based and location-specific Construction Inspection and Verification system on your projects, where would you find the greatest use for it?