A useful construction quality report lets a facility manager or contracting officer’s representative trace a condition from the governing requirement to the evidence of correction. That traceability supports acceptance decisions and gives the operations team a usable record after turnover.

The contractor’s quality control record and the government’s quality assurance record have different responsibilities behind them. FAR 52.246-12 requires an adequate contractor inspection system and complete inspection records. Government inspection does not relieve the contractor of those responsibilities. [^1]

Begin with the awarded contract. Unified Facilities Guide Specifications are templates tailored for individual projects; a current guide is not automatically the specification governing every active contract.

Document the three phases

The current UFGS 01 45 00, Quality Control, is dated August 2023 with Change 4, August 2026. Section 1.8 describes preparatory, initial, and follow-up controls for definable features of work. [^2]

Preparatory records should show what the team reviewed before starting: applicable requirements, approved information, work readiness, and planned inspection or testing. Initial records establish the workmanship standard and confirm that the first work meets the requirements. Follow-up records document continuing checks and correction of deficiencies. Read the project’s repeat-phase and notification requirements rather than treating the first meeting as permanent authorization to proceed.

For a report reader, the important connection is between the feature of work, the activity performed, the location, and the evidence. “Inspected” alone leaves too many questions unanswered.

Confirm the system of record

Reporting instructions changed in 2026. UFGS 01 45 00.15 10, Resident Management System Contractor Mode, now carries Change 1, August 2026. Its section 1.3 describes a phased FY2027 transition from RMS to the Construction Management Platform, with the contracting officer identifying the applicable system and transition schedule. This is not a statement that every USACE contract has already moved to CMP. [^3]

While RMS remains the applicable system, the guide’s sections 1.7.3.1 and 1.7.3.2 address signed daily reports within 24 hours after the covered date, same-day deficiency entry, QC/QA tracking numbers, and government concurrence before a deficiency is considered corrected. These replace the older section numbers quoted in many summaries. [^3]

Use the contract-designated platform and instructions on NAVFAC and other agency projects as well. Do not assume an undated handbook proves a universal current software requirement.

Make every deficiency actionable

As a reporting practice, give each finding a stable identifier and connect it to five things: the requirement, the location, the observed condition, the assigned corrective action, and the evidence supporting its status.

A practical entry might identify an equipment tag and room, reference the relevant specification or approved drawing, describe the observed mismatch, and link the applicable test record. After correction, preserve the original finding and add the retest result and required government concurrence. Avoid overwriting the history.

Photographs should include enough context to locate and understand the condition. A close-up can document a detail; a wider view can show where it belongs. Location labels, dates, and links to the finding improve their usefulness. A missing label does not automatically make a photograph legally worthless.

A closed status is useful only when the record explains what was corrected and how that correction was verified.

Build the turnover record during construction

UFGS 01 78 00, Closeout Submittals, was reissued in August 2026, superseding its May 2019 edition. It addresses as-built and record information, warranty management, and O&M submissions through project-specific options and related sections. The older guide’s section references and deadlines should not be copied into a current article as universal requirements. [^4]

For the active project, maintain a closeout register tied to the actual contract. Include the responsible party, required submission, review status, due date, and dependency for each deliverable.

Review as-built information before affected systems are concealed. Connect equipment data with the installed asset identifiers. Check that test reports identify the equipment, method, acceptance criteria, results, and unresolved conditions. Confirm training records describe the systems covered and the materials provided.

Plan seasonal or otherwise deferred testing explicitly where the contract permits it. Beneficial occupancy, completion of testing, acceptance, and final payment should not be treated as interchangeable milestones.

Keep authority and evidence clear

The government’s QA record should add its own observations and assessments. A discrepancy between QA and QC reports warrants investigation; it does not automatically establish that the entire QC program has failed.

Acceptance also does not eliminate every possible remedy. FAR 52.246-12 preserves specified exceptions, including latent defects and warranty or guarantee rights. That is another reason to retain accurate records rather than make categorical claims about what happens after turnover. [^1]

At each project meeting, review unresolved findings, approaching document deadlines, and items awaiting verification. The objective is a record that explains the work clearly enough for the next responsible person to act.