Why documentation matters

Nine months into the Westgate Branch Library and Community Hub, the mass-timber package arrived three weeks late. Brightwater Builders' superintendent, Marcus Bell, knew exactly what that had cost the job: crews standing down, a crane kept on rent, a winter enclosure that had to be bought because the roof would not be closed before the cold. Knowing it and proving it are different things. When project manager Elena Vasquez sat down to prepare the claim, the first question from the owner's project manager, Robert Kaminski, was simple: show me. What Brightwater could recover depended almost entirely on what had been written down, photographed and sent at the time.

This course is about that discipline: creating, sending, organizing and keeping the records that run a construction project and protect everyone on it. We follow Brightwater through the Westgate project, a four-story public library and community hub with a concrete podium and a mass-timber superstructure, from the first submittal to the day the keys are handed over. Along the way you will meet project coordinator Jun Park, who runs document control; field engineer Hannah Lowe, who handles requests for information and submittals; Simone Achebe of Arden Moss Architects, the architect; and Owen Grady, project manager for the mechanical subcontractor, Tallis Mechanical.

Brightwater is building Westgate in Pittsburgh under an AIA A101 stipulated sum agreement with the A201-2017 General Conditions, worth about $49 million, with the Westgate Public Library Board. Pennsylvania's Contractor and Subcontractor Payment Act shapes how payments and withholding must be documented, and the A201 sets strict rules for written notice and claims.

What counts as project documentation

Project documentation is every record created or received in the course of delivering the project. It is far broader than the drawings and specifications. A useful way to think about it is in five families, each with its own owner on the project team and its own rules for how it is created and kept.

The contract documents set the baseline. Everything else records how the project moved away from or along that baseline. When people argue on a construction project, they almost always argue about the difference between what the contract documents said would happen and what the field records show did happen. The administrative records sit in between: they show who knew what, and when.

The four jobs that records do

Good records are not paperwork for its own sake. On a busy site every record should be doing at least one of four jobs, and the best ones do several at once.

• They coordinate the work. A clear RFI answer, an approved shop drawing or a well-written set of minutes tells forty trades what to build and in what order. Most rework traces back to someone working from an outdated or misunderstood document.
• They prove what happened. Months later, nobody will remember which day the crane was idle or which grid line was flooded. The daily report, the photo and the delivery ticket will.
• They protect entitlement. Contracts give extra time and money only when the contractor gives written notice within set periods and supports the request with records. A valid claim can be lost entirely on a missed notice.
• They hand over the asset. The owner will operate the building for fifty years or more. As-built drawings, manuals and warranties are part of what the owner paid for.

The figure shows the chain that turns a site event into a resolved change or claim. Something happens: a design error, an owner decision, unexpected ground conditions, late information. Someone records it at the time. Someone gives written notice to the right person within the contract's time limits. The effect on time and cost is measured using records. Finally the parties agree, or a decision maker decides. A break at any link, such as no record, late notice or costs that cannot be traced, weakens or destroys what follows.

Why records made at the time carry weight

Judges, arbitrators and adjudicators prefer evidence created when events happened, by people with a duty to record them, over recollections assembled after a dispute has begun. Such records are called contemporaneous records. A daily report signed by the superintendent on the evening of a rain day is far more persuasive than a summary written a year later by a claims consultant.

US evidence law recognizes this. Under the business records exception in Federal Rule of Evidence 803(6), and similar state rules, a record made at or near the time by someone with knowledge, kept in the course of a regularly conducted activity, is generally admissible as evidence of the facts it records. The weight a court gives a record depends on how regular, complete and unaltered it is.

That has practical consequences for the way Brightwater writes its records. A record is strongest when it is made routinely, on the day, by the person who saw the event, in a consistent format, and stored where it cannot be quietly edited. A record created only when something goes wrong, or edited months later, invites the question of why.

Where the contract asks for documentation

The construction contract itself requires much of the documentation in this course. The general conditions require written notices, set out how changes are ordered and priced, and say how payment is applied for. The specifications, usually in Division 01 of the MasterFormat structure, add detailed procedures.

Under the A201-2017, the contractor's documentation duties appear throughout: keeping a record set of drawings and specifications at the site (Section 3.11), submitting shop drawings and product data (Section 3.12), following the change procedures in Article 7, applying for payment under Article 9, and giving notice of claims within 21 days under Section 15.1.3. Section 1.6 requires notices to be in writing and delivered in person, by mail, by courier, or electronically only if the parties have agreed a method.

Brightwater's first step on every project is a documentation matrix: a table of every record the contract and specifications require, who produces it, who receives it, how often and in what format. Jun builds it from the contract during preconstruction, and it becomes the checklist for the whole job.

Who reads the records

It helps to remember that construction records have many readers, and that most of them were not on site when the record was made.

Because of this, Brightwater writes records for a stranger. Daily reports avoid shorthand that only the crew would understand. Photos have dates, locations and descriptions. Emails say which drawing revision they refer to. A good test is whether an intelligent person who has never visited the site could understand the record a year from now.

The qualities of a good record

Objectivity deserves a special word. Records are often read by the very people they describe. A daily report that says the electrician was 'useless again' helps nobody and may embarrass Brightwater in front of an adjudicator. A report that says 'electrical crew of four arrived 09:40, two hours after the agreed start; level 2 rough-in in rooms 214 to 220 not started' is factual and far more useful.

Roles on the Brightwater team

Brightwater assigns every record family to an owner. Ownership does not mean the person writes every document; it means they make sure the record exists, is complete and is filed.

The same check can be automated. Jun keeps the daily report data in a spreadsheet, and a short script flags days in a delay window that lack the details needed to support a claim.

# Flag delay-window days whose daily reports would not support a time claim
reports = {
    '2026-03-02': {'filed': True,  'standby_logged': True,  'cause_noted': True},
    '2026-03-03': {'filed': True,  'standby_logged': True,  'cause_noted': True},
    '2026-03-04': {'filed': False, 'standby_logged': False, 'cause_noted': False},
    '2026-03-05': {'filed': True,  'standby_logged': False, 'cause_noted': True},
    '2026-03-06': {'filed': True,  'standby_logged': True,  'cause_noted': False},
    '2026-03-09': {'filed': True,  'standby_logged': True,  'cause_noted': True},
}
daily_cost = 4850
weak = [d for d, r in reports.items() if not all(r.values())]
strong = len(reports) - len(weak)
print('Days in window:', len(reports))
print('Well-supported days:', strong, ' value $', strong * daily_cost)
print('Weak days:', ', '.join(weak))
print('Value at risk: $', len(weak) * daily_cost)

Days in window: 6
Well-supported days: 3  value $ 14550
Weak days: 2026-03-04, 2026-03-05, 2026-03-06
Value at risk: $ 14550

Running a check like this weekly, not at the end of the job, gives the superintendent a chance to fix gaps while memories are fresh, for example by adding a dated addendum to a report that explains the standby. An addendum must be marked as added later; quietly editing the original would destroy its value.