Construction claim documentation is almost never created for that purpose. It is assembled, eighteen months late, out of records that were kept for accounting, for the lender, or for nobody in particular, and the gaps in it decide the outcome more often than the merits do.
Why the record decides the argument
A construction dispute is rarely about what the contract says. Both sides have read it and both readings are usually defensible.
It is about what happened, in what order, and who knew what on which date. Those are questions of fact, and questions of fact are decided by whoever can show a contemporaneous record.
Contemporaneous is the word that matters. A note written on the day carries weight. A reconstruction written eleven months later, from memory, in the knowledge that a claim is coming, carries very little, and an experienced reader can tell the difference in a paragraph.
This produces a result that owners find unfair and that is nonetheless consistent. The party with the better records usually wins the factual argument, and the party with the better records is usually the contractor, because the contractor has a full time team on site whose job includes writing things down.
The owner has one or two people with a portfolio, and the record they keep is the one their internal process requires: invoices, approvals, board papers. None of that answers the question a claim asks.
There is a second asymmetry underneath the first. The contractor records are created by the same people who will later be asked what happened, working on a single project, in a routine that produces a daily report whether or not anything notable occurred. The owner records are created by different people at different moments for different reasons, and no single person on the owner side holds the whole sequence.
That is why owner side reconstruction takes weeks and produces a chronology with holes in it, while the contractor produces one in days.
What construction claim documentation actually consists of
Six categories, and an owner can hold all six without a document management system.
The baseline. The schedule accepted at signature, the schedule of values, the allowance schedule, the qualifications list and the drawing set the price was built on, each stored as it stood on the day of signature and never overwritten.
The updates. Every monthly schedule update as issued, kept as separate files. The value is in the sequence, not in the latest one. A revision that moves an activity by three weeks is visible only when you can put two updates beside each other.
The correspondence that changes something. Not every email. The ones that give an instruction, grant an extension, waive a requirement, approve a substitution or acknowledge a delay.
The decisions and their dates. When you were asked, what you were asked, what you said and when. This is the record owners most often lack, and it is the one that answers the accusation of owner caused delay.
The change order file. Each change with its cause, its pricing basis and the date it was raised, which the cause of a change order turns into a question of who pays.
Site conditions. Photographs with dates, weather records, and anything unusual that was found rather than expected.
The three records owners almost always lack
The decision log. Most delay claims against an owner are built from a list of requests that sat unanswered. The contractor can produce the request with a date. The owner, often, cannot produce the response with a date, because the answer was given in a meeting or on a call.
A one line entry per decision, written the day it is made, defeats most of that claim. Date asked, date answered, what was decided.
The schedule updates as a series. Owners routinely keep only the current schedule. When a claim arrives asserting that an activity was always going to take longer, the only way to test it is to look at what that activity looked like eight months earlier, and that file has been overwritten.
The as sold scope. The exact qualifications list and drawing set attached to the price. Not the current set. The set at signature. Every scope argument reduces to whether something was in the price, and that is answered by a document that exists on one day and is superseded thereafter.
A worked example
Illustrative figures. Not taken from any client project and not a quotation.
A hotel project, nineteen months in, receives a delay claim of 84 days with associated costs of $1.9 million. The stated cause is late owner decisions on interior finishes.
The claim lists 31 requests for information and selection, with dates, and asserts that the average response took 24 days against a contractual 10.
The owner believes most were answered quickly. The owner cannot show it. Selections were made in design meetings and communicated verbally, then confirmed in shop drawing approvals weeks later. The approval date is the only date on record.
Of the 31 items, 22 had in fact been decided within a week. There is no document that says so.
The claim settles at $740,000 and 38 days. On the owner side nobody believes the exposure was real. Nobody can demonstrate that it was not.
A decision log costing perhaps twenty minutes a week over nineteen months would have removed most of it.
Keeping it without a system
A dated folder structure and a single spreadsheet does the work.
One folder per month for schedule updates and applications, never overwritten. One folder, created once, for the signature set: price, schedule, qualifications, allowances, drawings. One spreadsheet with four columns for the decision log.
The habit that matters is refusing to overwrite. Every time a schedule is replaced rather than added, a future argument loses its evidence.
The second habit is writing the answer down on the day it is given, even when it was given verbally. One line, sent as an email to the contractor, creates a dated record and a shared one.
Neither requires software and neither requires a consultant. What they require is somebody whose job it is, which on most owner side teams is nobody, and that is the actual reason the records are missing.
The third habit is the hardest and the most valuable: writing down the reason for a decision, not only the decision. An instruction to proceed with a substitution is a fact. An instruction to proceed because the specified product carried a 26 week lead time and the alternative was approved by the design team is a defense, and it takes one extra sentence.
A useful test of whether the record is adequate is to pick a month at random, eighteen months old, and try to answer three questions from the files alone. What was the critical path that month, what decisions were outstanding, and what had changed in the contingency. If that takes more than twenty minutes, the record will not survive a claim.
What a review does with the record
A pre signature review sets the baseline that everything afterwards is measured against, which is why the notice deadlines and the record keeping obligations belong in the same reading as the price.
We name, at signature, the specific documents to freeze and the specific decisions to log, based on what the contract makes the owner responsible for. Contracts differ in what they require an owner to do and by when, and the log should follow the contract rather than a generic template.
Where the reading continues after signature, the log is maintained against the register built before it. That is the monthly assurance package, and it exists because a register nobody reads afterwards is a document rather than a tool.
What we do
We read the contract for what it obliges the owner to do, by when, and with what evidence, then set out the short list of records that answer those obligations. Most owners need six folders and one spreadsheet, not a system. The reading is part of the readiness review. Where a claim is already on the table, dispute and claims support works from the same records under the direction of your counsel.
Questions people ask
How long should records be kept after completion?
At least through the statute of limitations that applies to the contract in the relevant state, which is commonly six to ten years for written agreements and longer for latent defects. Storage is cheap and reconstruction is impossible, so the sensible answer is to keep the signature set and the monthly series permanently.
Is email enough on its own?
Email is evidence but it is not organized evidence. A mailbox with forty thousand messages proves very little until somebody spends two weeks building a chronology out of it, and that expense arrives at the worst moment. The point of a log is that the chronology already exists.
Does the contractor see the decision log?
Only what you choose to send. The useful practice is to confirm decisions to the contractor in writing as they are made, which creates a shared dated record and removes the argument entirely. The internal log is yours and covers decisions that were never communicated.
This is general information about construction contracts and is not legal advice.