Quality Documentation Best Practices

Quality documentation has three functions that are worth distinguishing, because they are served by different records. It establishes what was agreed, so acceptance is a comparison rather than a negotiation. It establishes what was done, including the elements that cannot be seen in the result. And it establishes what changed over time, which is what calibrates a program.

The Record Set

Photographic Practice

• Shoot from repeatable positions. A before-and-after comparison is only meaningful if the frame is similar. Noting the position makes the next cycle comparable.
• Daylight, dry surfaces, for condition records. Wet pavement darkens uniformly and hides what you are trying to record.
• Low angle for uniformity. Striping is visible along a surface and nearly invisible from directly above.
• Include scale where extent matters.
• Photograph before altering anything — particularly after an incident, before graffiti removal, and before any remedial work.
• Keep the metadata. Automatic date and location data is frequently the most useful part of the record.

What Each Record Prevents

• Pre-work condition record — prevents an unresolvable dispute about whether cleaning caused a crack that soiling was concealing.
• Substrate inventory — prevents a night crew treating EIFS as stucco or sealed concrete as unsealed.
• Outcome categories — prevents a successful clean being judged a failure over a stain that was never going to clear.
• Test area approval — prevents acceptance becoming a contest between two impressions.
• Containment records — prevents an unanswerable question if a discharge inquiry arises.
• Acceptance record — prevents an engagement being reopened weeks later.

Documentation on Recurring Programs

The record set front-loads: the condition baseline, substrate inventory, and outcome categories are created once and reused. What accumulates per visit is the work record and the condition reporting, and what accumulates per cycle is the calibration observation — condition immediately before each scheduled service.

That last item is the one properties skip and the one that drives cost, because it is what tells you whether each zone's interval is right. Over two or three cycles it converges a schedule that was guessed into one that is calibrated. See quarterly planning.

Organization and Retention

Retention periods depend on jurisdiction, insurance requirements, and organizational policy — confirm with your insurer and counsel rather than adopting a general rule. What is generalizable is the organizing principle: records should be findable by location and by date, because those are the only two axes along which they are ever searched.

A folder per property, subfolders per zone, files named by date is unglamorous and works. See the maintenance documentation guide.

What to Require From a Contractor

These are scope deliverables rather than favors, and specifying them means they arrive without being chased: date, areas worked, and methods applied; photographs of representative areas; evidence of containment in place during the work; the disposal path used; products applied with data sheets available; condition observations from the site; and any incident with the response taken.

The condition reporting item is the one most often omitted and the most valuable. A crew that spent six hours on a property has seen things a quarterly inspection will not.