“Progress reporting earns trust when it records observable work, location, date, and next dependency instead of an unsupported percentage.
Diagnosis
A percentage compresses different work into one apparently precise number. It cannot tell a buyer whether the entrance is accessible, whether a finish is approved, or whether an earlier package changed. Empty progress language also ages badly: an old figure remains online after site conditions move on.
Decision framework
Report by work package and observable milestone: structure, envelope, services, public realm, interiors, testing, or handover preparation. For each, record evidence date, exact area, current status, next dependency, and what the image cannot prove. Use percentage only when its denominator and calculation owner are defined internally.
Hypothetical property example
Implementation and measurement
Create a monthly evidence card with a site photo, location tag, date, status, change note, and reviewer. Archive superseded cards but keep the publication date visible. Measure whether sales can answer status questions from the card, whether old assets are withdrawn, and whether a technical reviewer finds any claim stronger than its evidence. A sequence of dated observations is more useful than a dramatic announcement because it lets the reader understand change while preserving the boundary between evidence and forecast.
Put it to work
- Replace one headline percentage with a dated evidence card.
- Name the work package and its dependency.
- Run a monthly withdrawal check on outdated assets.
Sources and visual credits
- Trustworthiness in Web Design: 4 Credibility Factors
- Creating helpful, reliable, people-first content
Illustrative photograph: Tour Silex 2 (construction site) and tower cranes from the train station. It does not depict the hypothetical example. Benoît Prieur · CC0 · Wikimedia Commons