Industry Watch: Documentation Before Rework Is a Discipline, Not a Legal Tactic

I’ve lost count of how many times I’ve walked a site, seen a condition that clearly needed corrective work, and heard a project leader say, “Let’s just fix it and be done.” There’s a natural urge to get a bad condition behind you. I get it — you’re protecting budget, schedule, and reputation.

But the instinct to just fix it is exactly what puts owners and project teams at risk — legally and operationally.

A recent piece from Koley Jessen (via Lexology) makes the legal risk plain: repairing too quickly can trigger spoliation arguments because evidence has been altered before all parties could inspect it. In their words, “acting too quickly can lead to unintended legal consequences.” (“Don’t Spoil It!” )

My takeaway is broader than litigation.
Documentation before rework is a project-management discipline. It protects the property, preserves contractual rights, and keeps “amicable” resolutions from turning ambiguous later.

The Problem Isn’t the Defect. It’s the Rush to Erase It.

When a defect is discovered, time pressure takes over.
Owners want operations protected. Contractors want momentum. Designers want the record to stay clean.

But “fix it now” can erase the very facts needed to determine:

what failed,
why it failed,
who owned the risk, and
what the right corrective scope actually is.

This is where many teams unintentionally create future conflict. Not because anyone is acting in bad faith, but because they skip the steps that establish a shared factual baseline.

A construction-law commentary puts it bluntly: “failure to preserve the ‘scene’ can be fatal to either a valid claim or a strong defense.” (Lewis Thomason )

What’s Being Missed

Most teams document the condition.
Fewer document the process.

If rework happens before the contractor (and their expert) has a reasonable opportunity to inspect, you don’t just lose evidence—you lose alignment. That is what turns solvable field problems into positional disputes.

Lewis Thomason also captures the procedural core: secure the scene and “notify…entities… and provide them with reasonable opportunity to inspect.” (Lewis Thomason )

Best Practice: A Rework Protocol Owners Can Actually Execute

1) Document the condition like it may be questioned later

This is not paranoia. It’s competence.

Capture:

dated photos/video (wide + detail)
field notes describing location, extent, and suspected cause
weather and active operations (when relevant)
contract references (spec section / drawing detail) if obvious

Koley Jessen’s framing is a useful reminder: spoliation can arise when a defect is repaired “before all parties have had an opportunity to inspect it.” (Koley Jessen via Lexology )

2) Document that you gave notice and a real opportunity to inspect

This is the part teams skip.

Your file should show:

written notice to the contractor (and designer if implicated)
a reasonable inspection window
the contractor’s response (or lack of one)
the agreed next steps, even if informal

This is as much about fairness and clarity as it is about legal posture.

3) Bring in an independent third-party inspection before corrective work

If you think things will stay amicable, this step is still valuable.

A neutral inspector creates a shared record.
It also reduces the chance that the corrective plan becomes a proxy fight over fault.

4) Separate “stabilize” from “correct”

This is where disciplined contracts pay off.

In my agreements, I always include language that allows the Architect or PM to issue written field directives for minor work when a condition poses a risk to life or property. That’s not meant to bypass change management. It’s meant to buy time.

It aligns with how the AIA framework treats minor changes: “The Architect may order minor changes in the Work… and… shall be in writing.” (Faegre Drinker summarizing A201 §7.4 )

Think: temporary roof protection to stop active intrusion—stabilize now.
Then document, inspect, and plan the true corrective scope—correct later.

5) Keep the collaboration—but don’t rely on it

I’ve also been fortunate to resolve deficiencies collaboratively more often than not. That’s always preferable.

But even “friendly” projects can change tone when:

budgets tighten,
schedules slip,
personnel rotate,
or insurers show up.

Documentation and independent inspection keep the work grounded in facts, not memories.

GOA Perspective

At GOA, we treat documentation as part of owner-side control, not bureaucracy.

We’ve seen owners reduce downstream dispute risk simply by standardizing:

notice templates,
inspection invitations,
photo protocols, and
a written distinction between stabilization and correction.

It’s the same mindset you’ve emphasized in past writing: owners need disciplined protections before work proceeds, because urgency is where rights get traded away.

Close

How are you handling rework when a defect is discovered midstream?
Do you have a written “stabilize vs. correct” rule your team follows?
Who do you rely on for independent inspection when the stakes rise?