How to document a contractor dispute

Contractor disputes follow a familiar pattern: work was agreed to, something went wrong, and now the two sides disagree about what was promised, what was delivered, and who owes what. The homeowner says the deck was supposed to be cedar. The contractor says composite was always the plan. Neither can point to a written confirmation.

Good documentation doesn't prevent all disputes, but it prevents the ones that come down to "my word against yours." And when a dispute does happen, organized records make mediation, small claims, or insurance claims far more straightforward.

Before work begins

The best time to create a paper trail is before anything goes wrong. Once a dispute starts, both sides remember the original agreement differently. Written records from the beginning anchor the facts.

Get the scope in writing. This means more than a signed contract, though a contract matters. It also means confirming specific details via text or email: materials, dimensions, colors, finishes, brand names if applicable. "Per our conversation, you'll be using the same Hardie board siding as shown in the sample - color: Evening Blue" is the kind of message that resolves arguments before they start.

Confirm the payment schedule. When is each payment due? What triggers each payment - a milestone, a date, a percentage of completion? If the contractor asks for a deposit, document the amount and what it covers.

Note the timeline. When does work start? When is the expected completion date? Are there conditions that could change the schedule (permit delays, weather, material availability)? Get these in writing, even informally.

During the project

The project phase is where most documentation gaps happen. Work is underway, things seem fine, and no one feels the need to write anything down. Then something changes and there's no record of when or why.

Document change orders. Any deviation from the original scope - different materials, additional work, altered timeline - should be confirmed in writing before the work happens. "You mentioned today that the electrician needs an extra day and the additional outlet will cost $280. That works for us - please go ahead." This protects both you and the contractor.

Take photos. Before, during, and after. Photograph the work area before demolition or construction begins. Photograph work in progress, especially anything that will be covered up (framing, plumbing, wiring behind walls). Photograph the completed work. Use your phone's timestamp or a photo app that records dates automatically.

Pair photos with messages. If you notice a problem during construction, photograph it and mention it in a message: "Noticed the tile grout color looks different from what we chose - can you take a look?" This creates a record that you raised the issue at the time, not months later.

Note site visits and verbal conversations. If the contractor makes a promise or explains a decision during an in-person visit, follow up in writing afterward: "Thanks for stopping by today. You mentioned the permit inspection is scheduled for Thursday and the countertops will be installed the following week."

When things go wrong

Disputes typically start with a concern, escalate through failed attempts to resolve it, and eventually reach a point where formal action seems necessary. Your documentation at each stage matters.

Raise concerns in writing. Even if you first mention something in person or by phone, follow up with a text or email. "Following up on what I mentioned yesterday - the cabinet doors aren't aligned and the paint is peeling near the window trim. Can we schedule a time for you to take a look?" This establishes when you first raised the issue.

Keep communication factual. It's tempting to express frustration, and some frustration is natural. But for documentation purposes, messages that stick to specifics are more useful than emotional ones. "The deck boards have a visible gap of about half an inch between them and several boards are warped" is more useful than "the deck looks terrible and I'm furious."

Document non-response. If the contractor stops returning messages, the messages themselves - sent and unanswered - are evidence. Don't delete your side of the thread. The sequence of attempted contact followed by silence is a documented pattern.

Get repair estimates. If the work is defective and the contractor won't fix it, get written estimates from other contractors to repair or complete the work. These estimates quantify the damage and become evidence of the cost to correct the problem.

Building a case for mediation or small claims

If the dispute can't be resolved directly, organized documentation is the foundation of your case. The structure is straightforward:

1. The original agreement: contract, scope confirmations, price and payment terms
2. Change orders: any modifications to the original scope, with dates and written confirmation
3. Payment records: what you've paid, when, and the payment method (checks, transfers, receipts)
4. The problem: photos and messages documenting defective work, delays, or unfinished items
5. Attempts to resolve: messages showing your efforts to address the issue and the contractor's response
6. Cost to correct: estimates from other contractors for completion or repair

Arrange everything chronologically. A judge or mediator reviewing your case should be able to follow the timeline from agreement to dispute without needing you to explain the sequence.

A note on what this isn't

This article covers practical documentation approaches. It's not legal advice. If significant money is involved, if the contractor has filed a lien, or if the dispute involves licensing or permit issues, consult an attorney.

The documentation practices themselves - confirming details in writing, photographing work, keeping organized records - are useful whether or not a dispute ever arises. They're the habits that make projects go smoothly and make problems resolvable when they don't.

Receipts helps organize communication records into clear, chronological timelines - turning scattered texts and emails into structured documentation for disputes.