Photograph it, date it, keep the envelope. Building a complaint file that holds up

Start the file on the day you notice the problem, not on the day you decide to complain. Those are usually weeks apart, and everything gathered in between is worth more than anything assembled afterward.

What follows is the whole method. It takes about ten minutes a week.

Photographs, and the two mistakes people make

The first mistake is photographing only the defect. A close-up of a crack proves there is a crack somewhere. Take three shots of everything: a wide shot establishing the room, a medium shot showing where in the room, and the close-up.

The second mistake is not establishing scale or date. Put a tape measure, a coin or a common object in the frame. Leave the camera's date settings alone and do not crop or edit, because an unedited original with intact metadata answers a question a cropped copy raises.

Photograph the good state too. Before work starts, walk the space and photograph everything. It costs five minutes and it is the only way to prove what a wall looked like before someone worked on it.

Written communication, kept whole

Three rules.

• Move the conversation to writing early and politely. After any significant phone call, send a short message confirming what was agreed. This is not aggressive. It reads as organized, and it converts a conversation into a record without anyone objecting.
• Export whole threads. Not screenshots of the useful part. A complete thread is credible; a cropped one invites a question about what was removed.
• Keep the envelope. A postmark establishes when something was sent, and delivery confirmation establishes when it arrived. Both matter where a notice period or a deadline is in play.

The documents that carry the most weight

1. The signed contract, complete. Every page, including the back of the page and any attached specification. Amendments and change orders with signatures.
2. The original estimate, because the difference between the estimate and the invoice is frequently the entire dispute.
3. Invoices and proof of payment. Card statements, canceled checks, transfer confirmations. Cash payments with no receipt are the single hardest thing to prove.
4. Permits and inspection records. Public documents, obtainable from the building department, and they establish independently whether work was permitted and whether it passed.
5. Any manufacturer documentation for materials, particularly installation instructions, because failure to follow them is a specific and provable defect.

The running log

One page, one line per event, added to the same day it happens. Date, what happened, who was present, and where the supporting document lives.

A log written contemporaneously is treated differently from a narrative written afterward. That is the reason to keep it, and it is why the entries should be short and factual. Save the assessment for later; record the observation now.

What weakens a file

Four things, all avoidable.

• Gaps. A file that stops for six weeks in the middle raises the question of what happened during those weeks.
• Edited images. Enhancing a photograph to show a defect more clearly destroys its value.
• Anger in writing. A single intemperate message becomes the exhibit the other side leads with, regardless of how justified it was.
• Payment without protest. Paying a disputed invoice in full without a written statement that it is paid under protest weakens the argument that it was disputed at all.

Storage

Two copies, one of them somewhere other than the house the dispute is about. Photographs backed up automatically off the phone. Paper scanned as it arrives. Name files by date first, so they sort chronologically without any effort.

Keep the originals of anything signed. Hand over copies to anyone who asks, including an attorney, an adjuster or a board.

What the file is actually for

Most disputes never reach anyone who will read it. The file's real work happens earlier: a complaint that arrives with dated photographs, the relevant contract clause quoted, and a clear log tends to be resolved at a lower level of the other organization, because the person receiving it can see how it would look further up.

Ten minutes a week while the work is happening produces that. Assembling the same material afterward takes days and produces something visibly weaker.