Assigning who tests, who pays, and who responds when results don’t come back clean
A concrete cylinder break fails. A weld doesn’t pass ultrasonic testing. A duct pressure test comes back outside tolerance. None of these are unusual events on a construction project, and none of them should be a crisis, if the scope of work already answered the basic questions: who ordered the test, who’s paying for it, and who fixes the problem if it fails.
Testing and inspection requirements are scattered across a project’s specifications in a way that makes them easy to under-scope. A structural note on one sheet, a specification section on quality assurance, a code requirement nobody wrote into the contract explicitly because everyone assumed it was obvious. That’s exactly the environment where a trade ends up disputing an inspection cost it never priced into its bid.
This article covers how to write clear testing and inspection scope language, drawing on patterns from commercial, industrial, healthcare, and infrastructure work, where testing and special inspection requirements are often extensive and easy to miss during bidding.
Key Definitions
Testing and inspection terminology varies somewhat by jurisdiction and code edition, but a handful of core terms show up on nearly every commercial project.
Table 1: Core Terminology
| Term | Definition |
|---|---|
| Special Inspection | Code-mandated inspection of specific construction elements, such as structural steel welds or high-strength bolting, performed by an inspector qualified and approved under the building code. |
| Third-Party Testing | Testing performed by an independent laboratory or agency not employed by the contractor, often required for concrete, soils, or fireproofing verification. |
| Quality Assurance (QA) | The owner’s or design team’s program for verifying the work meets contract requirements, often implemented through third-party testing and inspection. |
| Quality Control (QC) | The contractor’s own internal process for verifying its work meets contract requirements before it’s presented for QA review. |
| Retest | A repeated test following a failed initial test, typically after corrective work, with cost responsibility for the retest a frequent point of contract ambiguity. |
| Deputy Inspector | A jurisdiction-approved inspector, often provided through a third-party agency, authorized to perform special inspections on the building official’s behalf. |
QA and QC are worth separating clearly in a scope of work, because they answer different questions. QC asks whether the contractor’s own work meets the requirement before anyone else looks at it. QA asks whether an independent party agrees. A scope that conflates the two tends to leave a gap where nobody actually owns catching a defect before it becomes a failed inspection.
Table 1b: QA vs. QC Responsibility
| Attribute | Quality Control (QC) | Quality Assurance (QA) |
|---|---|---|
| Performed by | The trade contractor itself | An independent third party or owner’s team |
| Timing | Before work is presented for inspection | After work is presented, to verify conformance |
| Purpose | Catch defects before they become failures | Confirm the work meets contract requirements |
| Typical cost bearer | Included in the trade’s base scope | Usually retained and paid by the owner |
Objectives of Clear Testing and Inspection Scope
Scope language for testing and inspection needs to answer a specific set of questions for every required test, not just acknowledge that testing will happen somewhere on the project.
- Identify every test and special inspection required by code, specification, or the structural design, tied to a specific trade or work element.
- State who orders and schedules each test, and how much advance notice is required.
- Define who pays for initial testing versus who pays for a retest following a failure.
- Assign responsibility for corrective work when a test fails, and the process for re-verification.
- Clarify access and coordination obligations, since inspectors and testing labs often need scheduled access to work areas before they’re closed up.
- Establish documentation and reporting requirements so test results are captured and distributed to the full project team.
| KEY TAKEAWAY The most expensive testing and inspection disputes aren't usually about the test itself. They're about who pays when it fails. Settle that question in the scope of work before the first test is even scheduled, and most of the friction disappears. |
|---|
Why This Matters on Real Projects
Testing and inspection gaps tend to surface at the worst possible time, right when a trade is trying to close up work and move to the next area. A failed test that wasn’t anticipated in the schedule becomes a scramble, and a failed test whose retest cost wasn’t assigned in the contract becomes an argument layered on top of that scramble.
On structural steel projects, special inspection of welds and high-strength bolted connections is code-mandated and extensive, often requiring a deputy inspector on site for significant portions of erection. If the scope of work doesn’t clearly state who schedules the inspector and how erection sequencing accommodates inspection access, the steel trade can end up idling a crew waiting for an inspector who was never actually booked.
On healthcare projects, infection control and life-safety systems commissioning involves extensive testing, from duct leakage testing to fire and smoke damper verification, often tied to regulatory survey requirements the owner cannot skip. A scope gap here isn’t just a cost problem. It can delay a certificate of occupancy or a state licensing survey.
On industrial and manufacturing projects, process piping and structural welds frequently require nondestructive testing like radiographic or ultrasonic testing at a specified frequency. Because this testing is often performed by a third party the owner selects directly, coordination and scheduling responsibility needs to be explicit, or the trade ends up waiting on a testing agency it has no direct relationship with.
On infrastructure projects, materials testing for soils, concrete, and asphalt is usually extensive and tied to public agency acceptance requirements. A scope of work that doesn’t address retest cost responsibility on a large-quantity item like compacted fill can turn a single failed density test into a costly and drawn-out dispute.
Table 2: Where Testing and Inspection Gaps Are Costly
| Project Type | Common Test/Inspection | Typical Failure Mode |
|---|---|---|
| Commercial / Structural Steel | Weld and bolt special inspection | Inspector scheduling not coordinated with erection sequence |
| Healthcare | Duct leakage, damper, infection control testing | Tied to regulatory survey without schedule buffer |
| Industrial / Manufacturing | Nondestructive weld testing | Third-party lab coordination not assigned to a trade |
| Infrastructure | Soil density, concrete strength | Retest cost responsibility undefined |
| Data Centers | Raised floor load testing, containment leakage | Testing sequence conflicts with commissioning |
| Institutional | Fire alarm and life-safety acceptance testing | AHJ witness scheduling not built into schedule |
Stakeholders and Their Roles
Table 3: Roles and Responsibilities Matrix
| Stakeholder | Typical Responsibility |
|---|---|
| Owner | Typically retains and pays for third-party special inspection and QA testing agencies, per code requirements. |
| General Contractor | Coordinates test scheduling across trades, tracks results, and manages retests within the overall project schedule. |
| Trade Contractor | Performs QC, prepares work for testing, provides access and notice, and corrects failed work at its own cost unless the failure is attributable to design or another party. |
| Testing Agency / Special Inspector | Performs the test or inspection, documents results, and reports to the building official and design team as required. |
| Architect / Engineer of Record | Establishes testing requirements in the specifications and reviews results for conformance with design intent. |
| Authority Having Jurisdiction (AHJ) | Requires and may witness certain tests directly, particularly for life-safety systems and structural special inspections. |
| FIELD REALITY Trades frequently assume testing costs are entirely the owner's responsibility because the owner hires the testing agency. That's only true for the initial test in most contract structures. Retesting after a failure is very often billed back to the trade whose work failed, and that distinction needs to be spelled out, not assumed. |
|---|
Construction Workflow
A functioning testing and inspection process follows a consistent sequence, and skipping steps is how a routine test turns into a schedule-threatening dispute.
This workflow has two distinct failure points, and they require different fixes. The first failure point is coordination, where a test simply wasn’t scheduled with enough notice and a crew ends up waiting around. The second failure point is quality, where the test was scheduled correctly but the work wasn’t actually ready to pass. A project tracking only pass and fail rates misses the coordination failures entirely, since a test that never got scheduled doesn’t show up in that data at all. Tracking notice compliance separately from pass rates gives a much clearer picture of where the process is actually breaking down.
- Identify every required test and special inspection during preconstruction, cross-referenced against the specifications, structural notes, and applicable code.
- Assign scheduling responsibility for each test to a specific party, with a defined notice period before the work is ready.
- Perform trade-level quality control before requesting third-party inspection, so work is genuinely ready when the inspector arrives.
- Coordinate site access and sequencing so testing doesn’t hold up downstream trades unnecessarily.
- Conduct the test or inspection, with results documented and distributed to the GC, trade, and design team.
- If the test fails, determine root cause and assign corrective work responsibility per the scope of work terms.
- Schedule and perform the retest, with cost responsibility applied per the contract.
- File all test and inspection reports in the project’s closeout documentation, tied to the specific location or element tested.
Required Documentation
Table 4: Documentation Matrix
| Document | Purpose | Responsible Party |
|---|---|---|
| Testing and Inspection Schedule | Master list of every required test, frequency, and responsible party | GC, developed during preconstruction |
| Test Notification Request | Formal notice that work is ready for inspection or testing | Trade contractor to GC and testing agency |
| Test Report | Documents results, pass/fail status, and location tested | Testing agency or special inspector |
| Nonconformance Report | Documents a failed test and required corrective action | GC or QA representative |
| Retest Report | Confirms corrective work resolved the original failure | Testing agency |
| Special Inspection Final Report | Summarizes all special inspections for code compliance at closeout | Special inspection agency, submitted to AHJ |
Technology Integration
Testing and inspection status is one of the more valuable things to track digitally, since it directly gates whether work can be closed up, covered, or moved past. A trade that closes a wall before an inspection result comes back creates exactly the kind of rework that a simple status tracker would have prevented.
Digital inspection request and tracking tools let a trade submit a test notification directly tied to a location on the drawings, and let the GC and testing agency see outstanding requests in one place instead of chasing them through email or phone calls. This matters most on projects with high testing volume, like structural steel erection or large concrete pours, where dozens of individual tests are happening in parallel.
Document control platforms that link test reports directly to the specification section and drawing location they apply to make closeout dramatically faster, since the alternative, reconstructing which test applies to which wall or connection months later, is a genuinely painful process on a large project.
| INDUSTRY INSIGHT Projects that track outstanding test and inspection requests in a shared digital log, visible to every trade and the GC in real time, close out special inspection reports measurably faster at the end of the job, largely because nothing gets lost waiting for someone to remember it was scheduled. |
|---|
AI-Assisted Opportunities
Testing and inspection requirements are exactly the kind of scattered, cross-referenced content that’s easy to miss during manual scope review. A single testing requirement might be stated once in a structural general note, referenced again in a specification section, and implied a third time by a code reference nobody traced back to its actual testing obligation.
iFieldSmart’s Scope Gap Analysis platform can extract testing and inspection references across an entire drawing and specification set and flag cases where a required test is mentioned but not clearly assigned to a trade’s scope of work, or where a testing requirement referenced in the specifications doesn’t appear anywhere in the trade’s bid scope. This kind of cross-referencing is tedious and error-prone when done manually across a large document set, and it’s precisely the pattern automated scope review is built to catch.
The same extraction capability supports drafting a trade’s Exhibit B with testing and inspection obligations stated explicitly, including who schedules each test, who pays for retesting, and what advance notice is required, so this scope isn’t left to be discovered mid-construction.
- Automated extraction of testing and special inspection requirements from structural notes and specification sections.
- Cross-referencing of code-mandated inspections against each trade’s stated scope to catch unassigned obligations.
- Structured Exhibit B language covering scheduling, cost, and retest responsibility for each identified test.
- Flagging of testing requirements that changed between design development and construction documents.
Implementation: Writing the Scope Language
Effective testing and inspection scope language addresses each test individually rather than relying on a blanket statement that “all required testing will be performed.”
- List each required test or special inspection by name, referencing the applicable code section or specification.
- State who schedules the test and the required advance notice period.
- State who pays for the initial test versus a retest following a failure.
- Assign responsibility for corrective work when a test fails, and the timeline for completing it.
- Define access and coordination obligations the trade must meet, such as keeping a work area open until testing is complete.
- Require test reports to be distributed to the GC and design team within a specified timeframe.
- Address what happens if a test result is disputed, including any right to an independent third-party review.
| EXPERT TIP Build test notification lead time into the schedule as a real activity, not a same-day assumption. Testing agencies and special inspectors often need several days of notice, and a trade that assumes next-day availability regularly ends up idling a crew waiting on an inspector who couldn't be booked in time. |
|---|
Best Practices
Table 5: Best Practices
| Practice | Why It Works |
|---|---|
| Build a master testing schedule during preconstruction | Surfaces the full testing scope and cost early, instead of discovering it mid-construction |
| State retest cost responsibility explicitly | Removes the single most common source of testing-related disputes |
| Require trade-level QC before requesting inspection | Reduces failed inspections and wasted inspector visits |
| Track outstanding test requests in a shared log | Prevents work from being closed up before results are confirmed |
| Set defined notice periods for each test type | Keeps the schedule realistic and avoids idle crew time waiting on inspectors |
| Distribute test reports to the full project team promptly | Keeps design and ownership informed without requiring a specific request |
Common Mistakes
Table 6: Common Mistakes
| Mistake | Consequence |
|---|---|
| No stated retest cost responsibility | Every failed test becomes a negotiation instead of a routine correction |
| Testing treated as automatically included without scheduling detail | Crews idle waiting on inspectors who were never actually booked |
| No trade-level QC before third-party inspection | High failure rates waste inspector time and delay the schedule |
| Test reports not distributed promptly | Design team and owner discover issues late, after work has progressed further |
| Testing requirements missed during bidding | Trade discovers a significant unpriced cost only after award |
| COMMON MISTAKE Assuming a specification section's general testing language covers every trade adequately is how testing scope gets missed. Each trade needs its own specific list of required tests, not a shared reference to a QA section nobody has fully read. |
|---|
Industry Examples
On a mid-rise structural steel project, the erector’s scope of work required it to coordinate special inspection scheduling directly with the owner’s deputy inspector, with a two-day notice requirement built into the erection sequence. This kept the inspector consistently available during critical bolt-up operations rather than trailing several days behind erection progress.
A hospital project’s mechanical scope explicitly assigned duct leakage retest costs to the trade if the failure was due to workmanship, but to the owner if caused by a design deficiency in the ductwork layout. When a leakage test failed due to an undersized duct specified in the drawings, the clear language avoided a dispute over who paid for the retest after redesign.
An industrial piping project required radiographic testing on a percentage of all field welds, performed by a third-party agency the owner selected. Because the scope of work required the piping trade to maintain a running weld log cross-referenced to test results, a cluster of failures traced back to a single welder was caught early, before that welder’s other work needed to be retested at much greater expense.
A commercial curtain wall project required water infiltration testing on a sample of completed units, with the scope of work specifying that a failed test triggered testing of two additional adjacent units at the trade’s expense. This escalating retest structure gave the curtain wall installer a strong incentive to maintain consistent quality across the whole building, rather than treating each unit as an isolated pass-or-fail event.
A transportation infrastructure project tied compacted fill acceptance to a specific density testing frequency per lift, with retest costs assigned to the earthwork contractor only if the failure resulted from inadequate compaction effort rather than unsuitable material the owner had directed be used. This distinction, spelled out clearly in the unit price and testing scope, resolved a significant fill quantity dispute without escalation.
Frequently Asked Questions
Who typically pays for special inspections required by code?
In most jurisdictions and contract structures, the owner retains and pays for the special inspection agency, since these inspections are a code requirement tied to obtaining a certificate of occupancy. The trade’s obligation is usually to prepare work for inspection and provide access, not to pay the inspector directly, though this should be confirmed against the specific contract.
Who pays for a retest after a failed inspection?
This varies by contract, but it’s common for the trade responsible for the failed work to bear the retest cost, since the failure typically reflects a workmanship issue within that trade’s control. The scope of work should state this explicitly rather than leaving it to be negotiated after the failure occurs.
What's the difference between QA and QC testing?
QC is the contractor’s own internal verification that its work meets requirements before presenting it for review. QA is typically an independent, often owner-retained, verification that the work meets contract requirements. Strong QC reduces QA failures, which is why requiring trade-level QC in the scope of work matters.
How much advance notice should a trade give before requesting an inspection?
This depends on the testing agency and inspection type, but many require at least twenty-four to forty-eight hours, and some specialty testing requires significantly more. The scope of work should state a specific notice period for each major test category rather than leaving it as a general assumption.
What happens if a trade disagrees with a failed test result?
The scope of work should address this, typically through a right to request an independent third-party review or a second test using an agreed alternate method. Without this provision, a disputed result can stall progress indefinitely while the parties argue about the test’s validity rather than resolving the underlying issue.
Should testing requirements be included in the trade's bid documents?
Yes, explicitly. A trade that isn’t told about a testing requirement during bidding has no reason to price the coordination time, retest risk, or schedule impact into its number, and discovering the requirement after award almost always leads to a change order dispute.
Who's responsible for life-safety system acceptance testing, like fire alarm testing?
This is typically the fire alarm trade’s responsibility to perform and document, often witnessed by the authority having jurisdiction. The scope of work should specifically address AHJ witness scheduling, since these tests frequently require significant advance coordination with a public agency that doesn’t operate on the contractor’s schedule.
Can testing and inspection requirements change after the contract is signed?
They can, particularly if code officials interpret a requirement differently during construction than the design team anticipated, or if an addendum adds a requirement during bidding. The scope of work should include a mechanism for addressing added testing scope through the standard change order process rather than absorbing it silently.
Does the trade need to keep the test area accessible until results come back?
In most cases, yes, and the scope of work should say so directly. Closing up or covering work before test results are confirmed is one of the most common causes of rework in this category, since a passed visual check isn’t the same as a passed test, and a trade that covers a weld or a duct joint before results return risks having to open it back up.
How should testing be sequenced with other trades' work?
Testing sequencing should be built into the master schedule as its own set of milestones, particularly for tests that gate downstream work, such as a pressure test that must pass before insulation or drywall can proceed. The scope of work should identify which tests are schedule-gating so the whole project team understands the consequence of a delay.
Expert Recommendations
- Build a complete testing and inspection schedule during preconstruction, tied to specific trades and code references.
- State retest cost responsibility explicitly for every test category, before the first test is ever scheduled.
- Require documented trade-level QC ahead of third-party inspection to reduce avoidable failures.
- Set specific notice periods for each test type and build them into the master schedule as real activities.
- Track outstanding test requests and results in a shared, visible log rather than scattered email threads.
- Include a dispute resolution mechanism for contested test results directly in the scope of work.
| LESSONS LEARNED Testing and inspection scope disputes almost always trace back to a requirement that existed in the documents but was never translated into a specific trade obligation with a named party responsible for scheduling, paying, and correcting. Naming those parties before work begins is what keeps a failed test a minor event instead of a major one. |
|---|
Conclusion
Testing and inspection requirements exist to protect the owner, the public, and the building’s long-term performance, and no experienced construction professional argues against that purpose. The friction comes entirely from scope language that doesn’t translate those requirements into clear, trade-specific obligations for scheduling, cost, and correction.
A scope of work that lists every required test by name, assigns scheduling and payment responsibility, and defines what happens when a test fails turns testing and inspection from an unpredictable schedule risk into a routine, well-managed part of quality construction delivery.
