Documenting a Construction Project for Disputes and Change Order Claims

Almost every construction dispute eventually comes down to a disagreement about what was said, agreed to, or instructed, weeks or months earlier. "The owner told us to proceed" against "we never approved that" is a common standoff, and a dated written record from the time is generally far more persuasive than either side's memory of the conversation. That's not a guarantee of who prevails, outcomes still depend on the contract's own requirements, the applicable law, and the specific facts, but a written record gives whoever's evaluating the dispute something concrete to weigh, where recollection alone gives them nothing to check it against.

A note written the same day a conversation happened is treated very differently from a summary written three weeks later after a dispute has already started, even if both describe the same event accurately. The gap matters because a contemporaneous record has no reason to be shaped by hindsight, while a record created after a disagreement begins almost always looks, fairly or not, like it was written to support a position. This is the single biggest reason to build documentation habits into daily work rather than treating documentation as something you do once a problem shows up.

Verbal instructions happen constantly on a job site, an owner approves an upgrade during a walkthrough, a PM tells a foreman to proceed with extra work before the paperwork catches up. The fix isn't to refuse verbal direction, that's unrealistic, it's to follow up in writing immediately afterward confirming what was said. A short email sent the same day, "Confirming our conversation this morning: you approved substituting the quartz countertop at the price difference we discussed," creates a record even when the original instruction was never written down.

• Send the confirmation the same day, not days later
• State specifically what was approved, by whom, and any price or schedule impact
• Ask for a reply confirming agreement, or at minimum note that no objection was raised

A photo with no date, no location, and no note about what it's showing is weak evidence even when it's exactly the picture you need. The same photo paired with a dated caption identifying the location, what condition it shows, and why it was taken is far more useful months later when nobody remembers the specifics on their own. Consistency matters too: photos taken from the same angle at different points in a project, before work started, mid-progress, and finished, demonstrate a timeline far more convincingly than a single photo taken after a dispute already exists.

A dispute usually isn't about one moment, it's about a sequence: a request, a delay, a follow-up, a response, another delay. Correspondence that preserves that order, emails, written RFIs, formal notices, shows the sequence of events far better than anyone's after-the-fact account of how things unfolded. This is part of why text messages and verbal check-ins, while convenient day to day, are weaker records than anything with a clear timestamp and an unambiguous audience; a text thread can be hard to produce completely and easy to dispute the context of.

Not every disputed fact comes from a conversation. Weather delays, crew counts, equipment on site, and work actually performed on a given day are often the real substance of a schedule or payment dispute, and a daily log is usually the only record that captures them at all. A brief daily entry, who was on site, what got done, anything unusual, is far less work to maintain than it sounds, and it becomes disproportionately valuable the moment a dispute actually requires reconstructing a specific week months after the fact.

The pattern behind most lost disputes is familiar: a verbal approval that was never confirmed in writing, a photo with no date or context, a change in scope that was discussed in a meeting but never summarized afterward, a text exchange that's partially missing because someone changed phones. None of these failures happen because anyone was trying to hide something. They happen because documentation felt unnecessary in the moment the work was actually being discussed, and by the time it mattered, the moment had already passed.

The practical fix for all of this is the same regardless of project size: write things down close to when they happen, confirm verbal agreements in writing the same day, caption photos when you take them, and keep a running log rather than reconstructing one later. None of this requires specialized tools, a dated email and a habit of sending it are often enough. What it requires is treating documentation as part of doing the work, not as a separate task that only matters once something has already gone wrong.

The project, people, and company below are fictional and for illustration only. They do not describe a real ConstruDo customer or project.

During a kitchen remodel, the homeowner asked the general contractor's project manager, during a Saturday site visit, to upgrade the backsplash tile to a more expensive option. The contract required a signed change order for any price change, so the PM didn't treat the verbal request as approval by itself. She sent a short email that evening summarizing what was discussed, "Confirming today's conversation: you'd like to upgrade the backsplash tile to the Carrara marble we discussed, additional cost of $640, no schedule impact. I'll bring a change order by Monday for your signature," and followed up two days later with a one-page change order describing the substitution, the price, and the schedule impact, which the homeowner signed before the tile was ordered.

At final payment, the homeowner's spouse, who hadn't been present for the site visit, questioned the $640 charge. The project manager pulled up the signed change order, dated and specific about the item and price, and the question was resolved in minutes. There was no need to reconstruct a verbal conversation from memory or argue about what silence might have meant, because the actual approval existed in writing with a signature on it.

The same-day email mattered too, not as a substitute for the signature, but because it created an immediate, dated record of what was discussed while the signed change order was still being prepared. If the homeowner's recollection of the Saturday conversation had differed from the PM's once the written change order arrived, the email would have surfaced that mismatch within days, while it was still easy to sort out, rather than weeks later at final payment. This isn't a ConstruDo-specific recommendation; it's the same practice the American Institute of Architects describes as the standard for change orders generally: a written description and cost, signed by the parties, before it's treated as binding. For what a change order needs to include, see our guide on documenting and tracking construction change orders.