The Water Loss Claim File a DC Condo Board Should Hold

Condo board water damage claim documentation is the record a managed building produces while the work is happening, not the packet somebody assembles once the last fan is gone. A single supply-line failure in a vertical pipe run can touch a corridor, a stairwell and four units on three different levels, and the association and each affected unit owner may be looking at separate policies. The file has to be readable by people who were never in the building and will form their whole picture of the loss from paper.

Nothing in District law hands a board a document list. What does exist is a set of expectations you can read for yourself. The standard homeowners form contemplates keeping an accurate record of expenses and handing over records on request. The water damage restoration standard treats documentation as part of the work, not as paperwork bolted on afterward. Between those two, the shape of a defensible file is clear enough.

A loss in a detached house has one owner, one policy and one scope. A loss in a District condominium or cooperative has an association, a managing agent, a board, several residents, and at least two insurance programs pointed at the same wet drywall. The physical event is one event. The paperwork is not: each unit's questions get asked and answered separately.

Keeping the records separate from day one costs an hour of setup. Separating them afterward is close to impossible, because readings taken as one sweep of the whole building cannot be split back into units, and an equipment list that only totals the machines on site cannot tell anyone which unit carried which load for how long. That is how a multi-unit file ends up reading thin.

Which part of the loss belongs to the association and which part belongs to a unit owner is a question for the building's governing documents and for both carriers, and this post does not answer it. Our post on co-op and condo water damage in DC walks through how those structures differ, and the answer for any particular building comes from its own declaration and bylaws, read with an agent, a licensed public adjuster or counsel.

A scope that only names rooms is not a scope. For each affected unit, the record should carry measured dimensions of every affected room, the material and assembly that got wet, where the moisture stopped, and a plain sentence for each activity explaining why it was necessary. The last part is what separates a scope from an inventory of labor: a reader who was not there needs the reason, not just the quantity.

Photographs are part of the scope, not a separate hobby. Each image should be keyed to the unit and the date, taken before work starts in that unit, again during demolition, and again at completion. Where a flood cut, meaning drywall cut away to a set height above the floor, crossed from common element into unit property, the photograph showing that boundary is worth more later than any sentence about it.

A unit that does not open is part of the record, not a hole in it. An unexplained gap in a drying log invites a question nobody can answer six weeks later, while a documented sequence of attempts answers it before it is asked.

Record the date and time of each attempt, how notice was given, who made it, and what the crew could observe from the corridor without entering. Keep it factual. Do not write anything about why a resident declined, and do not characterize a motive. If the delay changed the drying plan for neighboring units, note that consequence in the building-level log on the day it happened rather than in a summary written at the end.

The drying record is the part of the file that shows a decision being made rather than asserted. For each day of active drying, it should carry the outside conditions, the conditions inside the affected space, readings from the wet materials themselves, and the machines running in each unit at that point. Read in sequence, those numbers explain why equipment stayed and why it came out.

The equipment record is the companion to it. A total count of machines on the property tells a reader almost nothing. A record that gives the unit, the room, the machine type, the quantity and the date it went in and came out tells them everything, and it can be checked against the readings on the same page.

Most of what goes wrong in a multi-unit file is not a missing photograph. It is a hand-off nobody wrote down. A board authorizes emergency work by text and nobody keeps the text. A resident lets a crew in and no one records who. Drying ends in one unit before the rest and the release is never noted. Each of those is a two-line entry on the day, and an unanswerable question afterward.

The table below is the set of hand-offs worth treating as events in their own right. It is a documentation habit, not a rule from any statute.

Four parties end up holding a version of this file, and not the same version. The managing agent holds the building-level record and the access log. Each unit owner should hold their own unit's set, because their insurance conversation is theirs. The board holds what it acted on. The contractor holds the technical record it produced: the line-item estimate, the daily logs, the equipment record, the photographs and the written scope narrative.

Restoration Doctor invoices whoever signed the work authorization, the association or a unit owner, rather than either insurer. That party owes the entire invoice when the work is finished, not only a deductible, and what either carrier reimburses is settled between the policyholder and that carrier. We hand over the technical package so the policyholder can submit it and hold their own claim. We do not adjust a claim, we do not negotiate one, and we are not public adjusters. The trade body for our industry makes a related point worth a board knowing. Absent a direct contract with an insurer, a restoration contractor is under no legal obligation to that insurer, its adjuster or a third party. Unless an insurer's consultant's opinions are agreed by the contractor and the customer and written into the restoration contract or the scope of work, the trade body's position is that they have no effect on the contractor's duties and are not binding on it.

Minutes do not need the technical detail, and they are not the place for it. What minutes can usefully show is that the board saw the scope, understood what it was authorizing and when, and recorded the decision or the delegation that authorized it. The form those minutes take is a matter for the association's governing documents and its counsel.

The District's unfair claim settlement practices section sets out two lists of practices, and the opening words of each list matter as much as the items on it. Two of the items are about explanations. One is failing "promptly upon request to provide a reasonable explanation of the basis for a denial of a claim". The other is failing, on a denial or an offer of compromise settlement, "to promptly provide a reasonable and accurate explanation of the basis for such action".

Read the opening words of both lists before relying on either, because they change what the section is. Each subsection begins: "No person shall commit or perform with such frequency as to indicate a general business practice any of the following". That threshold is about a pattern of conduct, not a single event. One letter a board finds thin is not a violation of this section, and the Commissioner rather than the policyholder is the enforcer. The section also sets no number of days for anything.

What the list is genuinely useful for is shaping written requests. It tells a board and a unit owner which questions an insurer should expect to answer on paper, and a file organized unit by unit can hold the answers next to the scope they refer to. The two explanation items reach a denial and an offer of compromise settlement. Neither list requires an insurer to hand over its own estimate, and no District regulation requiring that was located, so the requests below are requests rather than entitlements. What to do when a claim is actually denied is covered in our post on who pays the restoration company in DC.

The last day on site is the cheapest moment to close every open question, and an easy one to waste. Once the crew has moved to another job, every unanswered item becomes a phone call, and the file freezes in whatever state it was in. Ten minutes with the site supervisor and the managing agent settles most of it.

Ask for the close-out packet in writing before the crews leave, and ask which items are still open. A contractor that documents well will have most of it assembled already.

What this post is not: Restoration Doctor is a restoration contractor, not a public adjuster and not a law firm, and nothing here is legal or insurance advice. We do not interpret anyone's policy and we do not tell a reader what theirs covers or what it requires of them. For a specific building or a specific claim, the sources below are the primary material, and an agent, a licensed public adjuster or counsel is the right reader of your own documents.

Two documents are worth reading directly. The standard homeowners form published by Insurance Services Office, in its conditions after a loss, asks the insured to protect the property and, where repairs are required, to "Keep an accurate record of repair expenses". It also contemplates providing the insurer with "records and documents we request". That is standard form text, not District law, and the policy an association or a unit owner actually holds is the one that governs. The water damage restoration standard lists "Administrative procedures, project documentation, and risk management" among the components of the work it describes.

Sources referenced in this article: