8.2 Supervision, Subcontractors & Quality Control

The Qualifying Party and On-Site Supervision

Arizona law requires every contractor to designate a qualifying party — a person regularly employed and actively engaged in the work who is responsible for the contractor's operations in the licensed classification. The qualifying party's experience (minimum 4 years, with at least 2 years within the last 10) underpins the license itself. On the project, the qualifying party, foreman, or superintendent translates the contract documents into built work and is the person the AZ ROC holds accountable for code compliance and proper trade practice.

Quick Answer: The qualifying party is the person regularly employed and actively engaged in the licensed work; Arizona holds that individual responsible for the contractor's on-site operations.

Supervision Responsibilities

Subcontractor Management and Agreements

A subcontractor is a specialty contractor hired by the general contractor to perform a defined portion of the work — for example, plumbing, electrical, roofing, or drywall. The GC-sub relationship is governed by a subcontract agreement that defines scope, price, schedule, payment terms, and insurance or bonding requirements.

Key Subcontract Provisions

• Scope of work — tied to the prime contract documents; the sub is bound to the same drawings and specs the GC owes the owner
• Schedule milestones — matching the CPM so sub start and finish dates support the critical path
• Payment terms — pay-when-paid or pay-if-paid clauses (subject to Arizona law), with retainage typically withheld
• Insurance and licensing — subs must hold their own AZ ROC license for any work over the $1,000 threshold and carry required insurance
• Lien rights — subs must serve the preliminary 20-day notice under A.R.S. § 33-992.01 on the owner, GC, and construction lender within 20 days of first furnishing labor or materials to preserve their mechanics' lien rights
• Change-order clause — how scope changes are priced and approved before the changed work begins

Coordination of Trades

Coordination failures are the most common cause of schedule slips and defects. The GC must sequence framing, rough-in, insulation, drywall, and finish trades so each can complete and be inspected before the next starts. The supervision sequence typically follows:

1. Framing — structural walls, floors, roof
2. Rough-in — plumbing, electrical, HVAC within framed cavities
3. Insulation — after rough-in inspection passes
4. Drywall — after insulation and air-sealing inspections
5. Finish — trim, paint, flooring, cabinets
6. Final trade inspections — each sub's work verified against code and submittal

Quality Control and Inspections

Quality control (QC) is the system of inspections and tests that verifies installed work conforms to the contract documents and the adopted building code. A typical QC program includes:

1. Pre-construction meeting — review submittals, tolerances, and inspection hold points with each sub before work begins
2. Submittals — shop drawings, product data, and samples submitted by the sub to the GC, who forwards them to the architect or engineer for approval before fabrication or installation
3. RFI (Request for Information) — a formal written question from the contractor to the architect/engineer when the documents are ambiguous or conflicting; the RFI response often becomes the basis for a change order
4. Inspections — by the building department for code compliance and by the architect/engineer for conformance to the design intent
5. Punch list — a list of defective or incomplete items generated near substantial completion; each item must be corrected before final payment

The RFI and Submittal Cycle

The submittal process ensures that what the sub intends to install matches what the design professional specified. The RFI process resolves ambiguities the submittal or field conditions reveal. Together they form the primary documentation loop between the field and the design team:

Dealing with Defective Work

When installed work does not conform to the contract documents or the adopted code, the GC must act promptly:

1. Issue a written notice of defective work to the responsible subcontractor, describing the defect and the required correction
2. Set a correction deadline tied to the schedule impact
3. Verify correction — re-inspect after the sub reports the fix
4. Document — photograph before and after, retain correspondence

If the sub fails to correct within the stated time, the GC may back-charge the cost of correction, call the sub's performance bond (if bonded), or terminate the sub for cause. Under A.R.S. Title 32, the AZ ROC can also discipline licensees for code violations, so correcting defects promptly protects the contractor's license as well as the project.