Technical Audit Rights at Project Closeout: What to Check in Your Contract

Your project is approaching handover. The owner wants additional test records, a consultant asks to review technical evidence, and the contractor asks whether those records were ever part of the agreed scope.

Before arguing about the request, establish what the contract says.

"Technical audit rights" is a broad phrase. On one project it means inspection of quality records. On another it refers to access to commissioning results, verification of equipment compliance, or a defined review of deliverables. Access to financial records is a separate question, although some contracts handle both in one clause.

The practical task is to identify the right being exercised, the records it covers and the process for using it.

Find the relevant clauses

Review the executed agreement and incorporated project documents. Look for provisions on inspection, testing, access to records, quality assurance, commissioning, handover and record retention.

Read them together. A testing clause may describe the evidence required, while a separate section names the reviewing party or the submission procedure. In the public DFW Airport package we use as an example (PA1971, bid March 2026), two clauses do most of the work.

The first makes clear that inspection during the job is not acceptance:

Inspections and tests by the Owner or its representatives are for the sole benefit of the Owner and do not: (1) relieve the Contractor of responsibility for providing adequate quality control measures; (2) relieve the Contractor of responsibility for damage to or loss of the Work or any material before acceptance; (3) constitute or imply acceptance; or (4) affect the continuing rights of the Owner after acceptance of the Work.

What it means: An owner's inspection does not close the question. The owner keeps its rights after acceptance, so your records still matter at closeout.

The second is a records clause that reaches technical documents as well as accounts:

…the Owner and its representatives shall be afforded full access to and shall have the right to examine books, records, documents, accounting procedures and practices, correspondence, instructions, drawings, receipts, subcontracts, purchase orders, vouchers, memoranda, and any other supporting evidence deemed necessary by the Owner and in the format reasonably requested by the Owner to substantiate compliance with the Contract…

What it means: Drawings, instructions and correspondence are in scope, not just invoices, and the right runs for four years after final payment.

Record the source of every provision you rely on, and any amendment. An isolated clause from an earlier draft is not a reliable basis for a closeout request.

Define what is being reviewed

A focused technical evidence review starts with specific questions:

• Does the submitted test record cover the installed equipment?
• Does it address the applicable acceptance criterion?
• Is the referenced specification revision the governing one?
• Are the required approvals or witness records present?
• What remains unresolved?

Write the scope in terms of systems, requirements and document categories. "Send all project records" creates a very different burden from "provide the specified test records for these three systems."

Confirm access and authority

Identify who may request records, who supplies them and who can make acceptance decisions. These roles may sit in different organizations.

Also check any agreed limits on confidentiality, document handling, timing and access. Establish whether the review is limited to existing records or includes further inspection or testing.

A reviewer should distinguish between "not found in the records reviewed" and "never performed." The first describes the evidence available. The second is a broader conclusion that may need more investigation.

Can you impose new audit rights at closeout?

A closeout request does not automatically create a new contractual obligation.

First determine whether an existing provision or legal requirement supports the request. If the parties want broader access than the contract provides, document that agreement through the appropriate contractual process.

For future projects, define the review scope earlier: covered records, authorized reviewers, access arrangements, review periods, retention requirements and how unresolved findings are handled. Have contract counsel review proposed terms.

Turn findings into a reviewable record

For each finding, keep:

1. The requirement and its source.
2. The evidence reviewed.
3. The issue or limitation.
4. The party responsible for responding.
5. The response and supporting records.
6. The authorized reviewer's decision.

For example, a report might reference a superseded specification but still contain relevant test data. Flag the applicability question, link both records and ask the authorized reviewer to decide what further evidence is needed.

The same structure works for the whole closeout record. We cover it in construction closeout documentation: how to build an audit trail, and the documents owed before final payment in the construction closeout checklist.