Ask any attorney who handles property disputes what wins cases and they will not say passion, fairness, or being right. They will say the file. Dates, photos, and a clean chain of communication. Owners who document like lawyers get treated differently by carriers, contractors, and everyone else, because everyone can see the file would hold up if things went sideways.
You do not need a law degree to build that file. You need a system and the discipline to feed it from day one.
Photograph like the photos will be exhibits
- Wide, medium, close. Every damaged area gets three shots: a wide shot establishing where you are, a medium shot showing the damage in context, and a close up showing detail. A close up of a crack means nothing if nobody can tell what building it is on.
- Use your phone, leave metadata on. Modern phones stamp date, time, and GPS location into every image. That metadata is quiet corroboration for your entire timeline.
- Include scale. A tape measure, a coin, a gloved hand. Hail dents and crack widths need reference.
- Shoot before and after mitigation. The tarped roof matters, but the untarped damage underneath matters more. Capture both.
- Do not delete anything. Blurry shots, duplicates, keep it all. Gaps in a photo sequence invite questions you do not want.
Build the timeline as it happens
Memory reconstructs. Contemporaneous notes record. Keep a running log, a simple note on your phone works, with an entry for every event: the date of loss, the date you discovered it, every inspection, every phone call, every visitor to the site. Write entries the same day. A timeline built in real time reads completely differently than one assembled under pressure eight months later, and everyone who reviews it can tell the difference.
Control the chain of communication
- Move everything to writing. Phone calls are fine for speed, but every call gets a same day follow up email: per our conversation today, you said the engineer report is expected Friday. Now it exists.
- One thread per party. Keep carrier communication, contractor communication, and tenant communication in separate, continuous threads. Do not scatter decisions across texts, calls, and hallway conversations.
- Save everything inbound. Letters, estimates, reports, denial language. Never accept a summary of a document in place of the document.
- Names and roles. Every person you deal with goes in the log with their company, title, and contact info. Adjusters rotate. Your log should not.
Preserve the physical evidence
Do not discard damaged materials until the carrier has inspected or told you in writing they do not need to. If something must be removed for safety, photograph it thoroughly first and keep samples where practical: a section of membrane, a damaged panel, a saturated piece of insulation. A sample in a bag has ended more arguments than any email I have written.
Why this works
None of this is about being adversarial. It is about being unignorable. A carrier reviewing five hundred storm claims gives the organized file a different level of attention because it is easy to pay and hard to dispute. A contractor who knows the owner photographs everything installs differently. This documentation discipline is the core of how I run Overwatch engagements, and it is the single highest return habit an owner can build. It costs minutes a day and it changes outcomes.
Store the file somewhere that survives disasters, because the same storm that damaged your roof can kill the office computer holding your photos. Cloud storage, or at minimum a second copy off site, and share access with one other trusted person in your organization so the file never depends on a single phone or a single memory.
Photograph in sequence, log every contact the same day, keep everything in writing, and your file will do the fighting for you.