Water intrusion response: a step-by-step protocol for apartment maintenance

Mold needs moisture, an organic surface, and time. You cannot remove the drywall and you cannot remove the water fast enough to matter unless you start immediately.

Time is the only variable you control, which is why water intrusion is the maintenance event where a protocol earns its keep.

The protocol, and what each step will not let you past

Three timed phases inside the 24 to 48 hour window, then a close that has to be earned.

Hour one
Stop the water at whatever is upstream of the leak. Then photograph before any remediation, including the units below and any resident property in the area.
before photos exist, and the source is off
Hours one to four
Assess whether it travelled. Water moves along framing and through floors, so the affected area is almost always larger than the visible stain.
adjacent and below units checked, not assumed dry
Hours four to 24
Extract, dry, and keep recording. The record during drying is what shows the response stayed inside the window.
moisture readings logged over time, not once
Close
Supervisor approval, after photos, and the incident report number captured at the time rather than reconstructed from memory a week later.
supervisor signs off, no single person decides it looked fine

The gates are the protocol. A checklist with the same four steps and no gates gets pencil-whipped at 2am, which is the only time this event happens.

Hour one: stop the source, then document before you touch anything

Two actions, in this order, and the order is the part people get wrong.

Stop the water. Shut off the supply, the riser, or the unit, whatever is upstream of the leak.

Then photograph before remediation begins. This is the step that gets skipped under pressure and it is the one an insurer will ask for. Photographs after the water is extracted prove nothing about the extent, and "we know it was bad" is not a claim position.

Photograph the source, the affected area with something for scale, the ceiling and walls of any unit below, and any resident property in the area. That last one prevents a later dispute about what was damaged.

Hours one to four: assess whether it travelled

Water moves down and sideways along framing, and the unit that reported it is often not the extent of it.

Check the unit below, the units either side, and the common corridor. Moisture readings matter more than visual inspection here, because drywall can look dry and read wet.

Record the readings with locations. A number without a location is not evidence eight months later.

Hours four to 24: extract, dry, and keep recording

Extraction and air movement, with dehumidification if the volume warrants it.

The part that matters for the file: daily moisture readings until dry, at the same locations. A drying log is the difference between a defensible position and a recollection. Three readings over three days showing a downward trend is proof the remediation worked. Nothing is proof of nothing.

The incident report number is the hinge, and it should be required

Every water intrusion event needs an incident report, and the number needs to exist while the event is happening rather than being reconstructed later.

GetDone requires the incident report number on a water intrusion work order and auto-creates the incident report on close. That is deliberate: the most common documentation failure is not that nobody filed a report, it is that the report was filed a week later from memory and the timestamps do not line up with the work order.

Gating high-risk closure on the incident report number is on our roadmap rather than shipped, and until it is, the requirement is enforced by the workflow rather than by the system refusing to close. Worth being straight about which is which.

Why the workflow has to force the photos

A tech under pressure with water on the floor is not thinking about a claim in September. That is the correct priority in the moment and it is exactly why the process has to carry the memory.

Guided steps that cannot be skipped or reordered. Mandatory before-and-after photos, not optional attachments. Supervisor approval before the order can close, so no single person decides it looked fine.

The failure mode this prevents is specific: a year later, defending a mold claim, nobody can produce the photograph that would have settled it in an hour.

What consistency was worth in our own portfolio

Before these workflows were enforced across 24,000 units and 100+ properties, 116 high-risk work orders were open with 90 of them aged past two days.

Not because anyone was careless. Because a high-risk order looked like every other order in the queue, so it was treated like one.

The risk figure attached to consistent documentation across the portfolio is $810K in potential claims exposure mitigated. Worth labeling that precisely: it is the exposure the risk team attributed to documentation being consistent rather than inconsistent. It is not claims paid and it is not losses avoided, and we would not present it as either.

The resident conversation is part of the protocol

Two things, both of which reduce escalation.

Tell the resident what is happening and when you will be back. Ambiguity is what turns an inconvenience into a complaint, and a complaint into a habitability claim.

Record consent to enter and every entry. If remediation runs four days, that is four entries, and each should be on the record.

Build the checklist once, then let the system carry it

Nothing above is unusual knowledge. Any experienced maintenance supervisor knows it.

The difficulty is that it has to happen identically at 100+ properties, at 2am, by whoever is on call, while the water is still running. That is a systems problem rather than a training problem, which is why the guided workflow exists and why the photos are required rather than recommended.

Pull your most recent water intrusion file. Does it have before photos, moisture readings with locations, a drying log, and an incident number dated the same day?