If It Is Not Written, It Never Happened: Why Emails Are Not a Construction Audit Trail

Construction teams use a simple rule for a reason: if it is not written, it never happened.

A direction may be discussed in a meeting. An approval may appear in a Teams message. A change may be accepted verbally on site. Months later, the project still needs to establish who directed the work, what information was available, when the decision occurred and whether cost or schedule was affected.

Digital contract records should create that chain. A large collection of emails does not automatically create an audit trail.

UK procurement rules show why record quality matters

A recent PBC Today article examined contract administration under the UK Procurement Act 2023. The statutory requirements apply to UK public procurement, not to every construction project, but they demonstrate how project records can become part of formal supplier-performance and payment reporting.

UK government guidance states that Section 71 contract-performance notices took effect on January 1, 2026. Where key performance indicators are required for applicable public contracts above £5 million, contracting authorities must publish a performance notice every 12 months and at termination. Certain breaches and failures to improve performance can also require notices.

Section 70 applies to qualifying new-regime public contracts where procurement commenced on or after April 1, 2026. It requires contracting authorities to publish specified information at least quarterly for individual payments exceeding £30,000 including VAT.

Those are jurisdiction-specific requirements. The wider construction lesson is relevant everywhere: records that may affect payment, performance or future decisions cannot be treated as informal paperwork.

Communication needs a contractual home

Email and Teams are useful for discussion, but the contract or project-management plan may require a notice, instruction, submittal response or change record to pass through a specific system.

The conversation and the contractual record are not always the same thing.

If a superintendent sends a message asking a trade contractor to move work, the message may explain urgency but still fail to identify the formal instruction, affected drawing, response deadline or commercial impact. If an architect provides an informal answer before issuing the formal response, the team may later confuse the preliminary direction with the approved decision.

The governing contract and project procedures determine what constitutes valid notice. Teams should not assume that a message is contractually sufficient merely because everyone saw it.

A useful record connects the full decision

For an instruction, approval or change, the project record should make it possible to reconstruct the decision without searching through several inboxes.

Depending on the contract and project requirements, the record may need to identify:

• the sender and authorized recipient;

• the date and time;

• the required notice or communication type;

• the affected area, system, equipment or work package;

• the relevant drawing, specification, model, RFI or submittal revision;

• the direction or decision in clear language;

• the response, acceptance or rejection;

• the potential cost and schedule consequence;

• the current status and responsible owner; and

• any later document that supersedes the original record.

Not every conversation needs every field. The point is to preserve the information that establishes authority, scope, sequence and consequence.

BIM teams are part of the contract-information chain

Contract administration is not separate from BIM coordination.

An RFI response may change equipment clearance. An ASI may reroute a feeder or change a ceiling. A bulletin may add devices after an area was coordinated. A submittal response may approve equipment with dimensions that differ from the design model.

If the change record does not reach the BIM team, the model can remain coordinated to obsolete information. If the model is updated without a link to the authorizing record, the team may be unable to explain why the installation drawing changed.

At DDG, we treat current RFIs, submittals, ASIs, bulletins and revision status as part of model reliability. The geometry should not become the only evidence of a decision.

Centralization does not mean one giant folder

A central record is useful when the project can find the current item, understand its status and follow its relationships. It does not require every file to live in one undifferentiated location.

A dependable system needs naming rules, revision control, permissions, required metadata and clear ownership. It should also preserve superseded information without allowing an obsolete document to appear current.

Search and AI can help retrieve information, but they do not repair a broken approval chain. The source record must first show which communication was contractual, which was preliminary and which document now governs the work.

Write it down while the decision is still clear

The easiest time to create a reliable record is when the instruction or decision occurs. Reconstructing it months later invites disagreement and missing context.

Good digital contract administration gives the next person a continuous trail from question to direction, from direction to action, and from action to project consequence. That trail supports compliance, coordination and dispute avoidance because the team does not have to rely on memory when the stakes become higher.

For related guidance, see DDG’s article on why connected construction records depend on better handoffs.