Part of the Maintenance Documentation pillar guide. This article goes deeper on the photo standard the pillar references at each repair stage.
A tenant texts you a photo of “the leak.” It’s a close-up of a wet spot. You can’t tell which unit it’s in, what surface you’re looking at, when it was taken, or how big the wet area actually is.
You text back asking for more photos. By the time they send them, they’ve cleaned up some of the water. The photos you eventually get aren’t useful for anything except confirming that yes, there was, at some point, a leak.
This is the most common documentation failure in residential property management. The work happens, the issue gets fixed, but the record of what happened is too thin to do anything with later. Three months later, if a dispute arises, the photos prove nothing.
This is solvable in about five minutes per incident.
The four shots
Every maintenance issue should be photographed in four specific ways. If you have all four, you have a usable record. If you have only one or two, you have a guess.
Shot 1: Context
A wide photo that shows the room and where the issue is located within it. Not a close-up. The whole scene.
For a leak under the kitchen sink: a photo of the kitchen showing the sink, the cabinets, and any furniture or appliances nearby. The viewer should be able to orient themselves immediately.
This shot answers: “Where is this?”
Shot 2: Problem
A medium photo of the actual issue, with enough surrounding visual information to make clear what you’re looking at. Not too close, not too far.
For the same leak: a photo from a few feet back showing the open cabinet, the pipes, the water on the floor of the cabinet, and the area immediately around the cabinet.
This shot answers: “What is the problem?”
Shot 3: Scale
A close-up that shows how bad it is, with a reference object for scale if possible. A ruler, a coin, a hand, anything that gives the viewer a sense of size.
For the leak: a close-up of the wet area with a tape measure or a quarter next to it, or a hand framing it. If there’s discoloration on the cabinet floor, include it. If there’s mold, the scale shot needs to capture how widespread it is.
This shot answers: “How bad is it?”
Shot 4: Timestamp
A photo taken in a way that the time and date are recorded. Most smartphones save this automatically in EXIF metadata, but you should not rely on EXIF alone, it can be stripped when images are sent through messaging apps or compressed.
The reliable way: take one shot where the time and date are visible in the frame. A phone screen showing the time. A newspaper. A handwritten note with the date. A photo of the address numbers next to the affected area.
Better still: use a photo tool that stamps the date directly onto the image at capture. Many free apps do this.
This shot answers: “When did you take these photos?”
What to write
Photos without words are still useful, but photos with a short written note are several times more useful. The note should be entered at the same time as the photos, not reconstructed later.
A good note has five elements.
Date and time. Specific, not approximate. “March 4, 2026, 8:47 PM” not “Tuesday night.”
Location. Property address, unit number, and which room or area. “412 Maple Street, Unit 4, kitchen, under the sink in the lower cabinet.”
Description. What you see, in plain language. “Standing water on the floor of the cabinet, approximately 4 inches in diameter. Water appears to be coming from the joint where the drain pipe meets the trap. No water visible on the floor outside the cabinet.”
Cause hypothesis. Your best guess about what’s happening, with the acknowledgment that you might be wrong. “Looks like the slip nut on the trap is loose. Could be more than that.”
Action. What you’ve done or are about to do. “Tenant placed a bowl under the leak. Plumber contacted, scheduled for tomorrow morning at 9 AM. Tenant instructed not to use the kitchen sink until the plumber arrives.”
Five sentences. Two minutes. Now your record is complete enough to defend.
How to take the photos correctly
A few technical points that turn an average photo into a usable one.
Lighting
Natural light first, room lights on if natural light is poor. Don’t use flash if you can avoid it, it creates harsh shadows that hide detail. If the area is genuinely dark (under a sink, behind a water heater), use a flashlight from the side rather than a flash from the camera position. Better contrast, more visible detail.
Distance
The most common photo mistake is shooting too close. A close-up of a stain tells you nothing about where the stain is or how large the affected area is. Start farther back than you think, get the context, then move in for the close-up.
Stability
If your photo is blurry, it’s not evidence. Brace the phone against the wall, the counter, your other hand, whatever stabilizes it. Take three shots of each angle if you’re not sure.
Don’t edit
Crop only if you absolutely must. Don’t apply filters. Don’t adjust brightness or contrast. An edited photo can be challenged in a dispute. An unedited photo can be verified by metadata.
What to photograph for specific issues
A few common scenarios with the specific shot list.
Water damage
- Context: room shot showing source
- Problem: medium shot of affected area
- Scale: close-up with measuring reference
- Timestamp: visible date
- Bonus: photo of the ceiling/floor above and below if damage may have spread
Pest issue
- Context: room or area where pests have been seen
- Problem: actual pest or evidence (droppings, nests, damage)
- Scale: close-up of the evidence with measuring reference
- Timestamp: visible date
- Bonus: any tenant-supplied food storage that may be a contributing factor (relevant for assigning responsibility)
Appliance failure
- Context: appliance in its location
- Problem: front of appliance, including model/serial number plate
- Scale: close-up of the specific failure (broken handle, error code on display, leaking water line)
- Timestamp: visible date
- Bonus: any visible damage to surrounding cabinetry or floors
Structural or exterior issue
- Context: wider shot showing the side of the building or section of the property
- Problem: medium shot of the affected area
- Scale: close-up with reference, ideally including a tape measure
- Timestamp: visible date
- Bonus: photos from multiple angles if the damage is dimensional (cracks, settling, leaning)
Heating / cooling failure
- Context: thermostat showing current indoor temperature and set point
- Problem: outdoor temperature reading (weather app screenshot is fine) for comparison
- Scale: photo of the unit itself, including any error codes
- Timestamp: visible date
- Bonus: photo of filter if recently changed, to rule out tenant-side issues
Where to file it
The fastest way to lose useful documentation is to have it scattered across:
- Personal camera roll
- A text thread with the tenant
- A text thread with the vendor
- An email to yourself
- A note app
- A printout in a paper folder
- The PMS system, partially
Six months later, recovering all of that for a single repair takes an hour. Multiply by a year of repairs and the lost-information cost becomes a real number.
The fix is structural, not behavioral. Have one place where every photo, note, vendor quote, approval, invoice, and tenant sign-off for a single repair lives together. That’s what a Maintenance Record is: one record per incident, with all the artifacts attached.
If you’re using a PMS that supports this well, use that. If you’re using DiscoveryMark, every maintenance record produces a signed PDF that contains the full set. If you’re using neither, at minimum: create a folder per incident, named with the date and unit, and put everything in that folder. Never let an artifact float alone.
Documentation for tenants
If you’re a tenant, the same rules apply. Your interests in good documentation are different from your landlord’s, but they’re real.
You want a record of:
- When you reported the issue
- What the issue actually was at the time you reported it
- Your landlord’s response (or non-response)
- The condition after the repair
Take the four shots. Send them to the landlord in writing (text or email, not a phone call). Keep the originals. If the issue recurs, you have the date and condition of the first occurrence. If the landlord disputes the timeline, you have proof. If the landlord didn’t respond promptly, the timestamps make that visible.
Tenants who document well are not adversarial, they’re just protecting themselves. Most landlords appreciate it because it reduces ambiguity. The ones who don’t appreciate it are the ones you most need protection from.
What good documentation prevents
A small sample of disputes that go away when the photos exist.
The “it was already like that” dispute at move-out. Photo from move-in shows the wall was undamaged. Photo from move-out shows a foot-sized hole. Deduction stands. This is also why a thorough move-in record matters more than the move-out one.
The “I reported that months ago” dispute. Tenant claims they reported a mold issue six months earlier. Your records show the first report was last week. Photos and timestamps end the argument.
The “the vendor didn’t actually do the work” dispute. Owner sees a $480 line item and wants to know what was actually done. Before-and-after photos make it clear.
The “you waited too long to respond” dispute. Tenant claims you ignored a maintenance request for two weeks. Timestamp on the request shows it was Tuesday. Timestamp on the vendor visit shows Wednesday. Dispute over.
Each of these is a few hundred to a few thousand dollars depending on the issue. The cost of preventing them is the five minutes it takes to capture the four shots and write the five-sentence note.
The bottom line
Documentation is the lowest-skill, highest-leverage activity in property management. It doesn’t require expertise. It just requires consistency. Five minutes per maintenance incident, every time, for the rest of your career as a property manager.
Every Maintenance Record you create is one less unwinnable argument in your future. For the bigger picture on why this matters, see why every property manager needs a paper trail.
