HVAC Duct Leakage Test Records: A Practical QA/QC Review Workflow

A duct leakage test record is useful only when a reviewer can connect the result to the right duct section, test setup, approved acceptance criteria, and any corrective work. A pass mark alone does not establish that connection. This workflow helps MEP engineers, commissioning teams, and QA/QC inspectors review the evidence systematically and identify gaps before records are accepted or handed over.

Use the project’s approved specifications, drawings, inspection and test plan (ITP), method statement, and applicable authority requirements as the controlling basis. The checks below are review recommendations, not universal acceptance criteria. Where documents conflict or leave a requirement unclear, raise a query rather than selecting a limit or procedure by assumption.

1. Start with the approved basis

Before checking individual readings, identify what the test was required to demonstrate and which approved documents govern it. Confirm that the submitted form or procedure is the current revision and is suitable for the system and test scope under review.

• Locate the applicable specification, approved test procedure, ITP, and referenced drawings.
• Identify the project-defined leakage class or other acceptance basis, where applicable, and the approved method for determining allowable leakage.
• Check what pressure, test configuration, stabilization approach, and reporting units the approved documents require. Do not substitute customary values for project requirements.
• Confirm required witness, hold, or review points and whether they were released or recorded before the test proceeded.
• Check that any approved deviation or clarification is traceable to the tested section.

If the acceptance basis cannot be identified, the record is not ready for a technical pass/fail decision. Record the missing reference and request the governing document or formal clarification.

2. Verify the test boundary

The test boundary is the link between the result and the installed ductwork. A record that says “Level 2 supply duct” may be too broad to identify what was actually isolated and tested. Compare the form with the latest approved drawings and any marked-up test sketch.

• Check the system, service, floor or zone, and identifiable start and end points.
• Look for duct tags, grid references, drawing references, or other project identifiers that distinguish the section from adjacent work.
• Confirm that the record or attached sketch shows the boundary, temporary closures, test connection, and relevant branches or openings.
• Check whether connected components or portions of the system were included or excluded, and whether that treatment matches the approved procedure.
• Confirm that the tested section can be reconciled with the installation inspection and current drawing revision.

Where the boundary is ambiguous, ask for a corrected sketch or marked-up drawing. Do not infer the tested extent from a label alone. If the field configuration differed from the approved drawing, request a traceable as-built clarification before accepting the record.

3. Match equipment and personnel to the record

The test setup should be identifiable enough for another reviewer to understand how the readings were obtained. Check the equipment details actually required by the approved procedure and project forms; the items below are review prompts, not a universal form specification.

• Test instrument and accessory identification: Can the instrument or relevant setup be distinguished from other equipment used on site? If not, request the missing identifier or an unambiguous equipment reference.
• Calibration or verification evidence: Does the submitted evidence meet the project’s stated requirements and cover the test date? Check the approved procedure and request applicable evidence; do not assume a validity period.
• Test arrangement: Is the connection and measurement arrangement documented as required? Request setup details or a sketch if the procedure calls for them.
• Test personnel and witness: Are required participants identified, with applicable attendance or acceptance recorded? Resolve missing names, signatures, or witness status against the ITP and approved procedure.

Equipment labels, certificates, and signatures support traceability; they do not by themselves demonstrate that the test was performed correctly. Review them alongside the boundary, conditions, and recorded results.

4. Review conditions, readings, and the calculation trail

Read the test results as a sequence, not as a single final number. Confirm that the form captures the readings and conditions needed by the approved method, and that values are legible, internally consistent, and expressed in the required units.

• Check the recorded test pressure and other required test conditions against the approved basis.
• Review the measured air flow or leakage reading, including units and instrument resolution where shown.
• Confirm that the method for calculating or comparing the measured result with the allowable value is documented when required.
• Recheck arithmetic, unit conversions, and transcription between field sheets and summary forms.
• Look for unexplained blanks, overwritten entries, inconsistent timestamps, or results that do not match attached instrument output.
• Confirm that the reported outcome follows the stated acceptance basis rather than an undocumented threshold.

A reviewer should be able to follow the calculation from source reading to reported outcome. If the form gives only “pass” without underlying data required by the approved procedure, request the missing evidence. Do not calculate a substitute acceptance limit from incomplete information.

5. Check corrective actions and retests

When a test fails or defects are found, the records should show what happened next. A later passing result is not a complete history if it cannot be tied to the affected section and corrective work.

1. Identify the original failed test and the specific boundary or defect area involved.
2. Check that the corrective action is described and linked to the relevant drawing, location, or work record.
3. Confirm that the retest covers the required extent under the approved procedure; do not assume it covers the original boundary unless the record shows that.
4. Compare retest conditions and results with the applicable acceptance basis.
5. Check that the failed result remains in the record set and that its disposition is clear, rather than being silently replaced by a passing sheet.
6. Verify required witness, approval, and closeout entries for the retest.

If a repair changes the test boundary or configuration, request documentation explaining the change and identifying the final tested extent. Keep the original and retest records cross-referenced so the quality history remains understandable.

6. Use a concise review checklist

Apply this checklist to each submitted test package. Mark an item not applicable only when the project documents support that decision.

• Scope: Correct system, service, location, and test section are identified.
• Boundary: Drawing or sketch makes the tested extent and relevant closures understandable.
• Basis: Current approved procedure and acceptance criteria are referenced.
• Setup: Test arrangement and required equipment identifiers are recorded.
• Evidence: Calibration or verification documents satisfy project-stated requirements, where required.
• Conditions: Required test conditions and units are recorded.
• Results: Source readings, calculations, and pass/fail outcome can be reconciled.
• Sign-off: Required personnel, witnesses, and review points are documented.
• Exceptions: Failures, deviations, repairs, and retests are traceable and properly dispositioned.
• Closeout: Attachments are legible, correctly referenced, and filed against the right system and drawing revision.

7. Record review comments so they can be closed

Make each comment specific, evidence-based, and actionable. Identify the record number and section, state what is missing or inconsistent, and cite the approved document or drawing that governs the check. For example: “Test sheet identifies Zone B but does not show the tested limits; provide a marked-up drawing or sketch identifying the boundary and test closures.” This is more useful than “clarify test.”

Separate administrative gaps from technical concerns. A missing attachment may be closed by submitting the required evidence; a discrepancy in the acceptance basis may require an engineering clarification. Track each comment to a response and verify revised evidence before changing its status. Avoid recording technical acceptance while a material question about scope, criteria, or results remains unresolved.

8. Assemble the closeout evidence

Before filing the package, check that the accepted record set presents a coherent history from approved basis through final disposition. Include completed forms, boundary sketches or drawing markups, required equipment evidence, source readings or outputs, witness records, corrective-action documentation, retests, and approved clarifications as applicable to the project.

Use consistent system names, test-section identifiers, drawing references, and revision information across the documents. A short index can help a future reviewer locate the evidence, but it should not replace the underlying records. This approach also supports commissioning and handover review by making it easier to connect construction testing with the relevant system dossier.

Practical rule for acceptance

Accept a duct leakage test record only when its boundary is identifiable, its method and criteria are traceable to approved project documents, its readings support the reported outcome, and any failures or retests have a clear disposition. When one of those links is missing, document the gap and request evidence or clarification. This disciplined review makes the records more useful to the installation team, commissioning team, and future handover reviewers without inventing requirements beyond the project basis.

Related reading

• Visual Testing of Fusion-Welded Joints: Inspection Records and Review Checks
• Inspection and Test Plan Hold Points: Review Checklist
• Testing and Commissioning Handover Dossier: Review Checklist
• Material Submittal Register Review: Practical Workflow

Terminology note: HVAC means heating, ventilation, and air conditioning. Use the project’s own definitions and evidence for this terminology; this note does not create project-specific acceptance criteria.