Most observations that never get fixed were not ignored. They were written as a description of a condition, handed to nobody in particular, with no date attached. A good observation reads like a work order: where, what, why it matters, what to do, and who does it by when.
Look at a typical site walk write-up and you will find lines like "housekeeping poor near loading dock" or "ladder issue, 2nd floor." They are accurate. They are also almost impossible to act on, because the reader has to go back out and rediscover what the writer saw.
The five parts
1. Where, precisely
Specific enough that someone who was not on the walk can stand in the spot. "Level 2, northeast stair, landing between 2 and 3" beats "2nd floor." On a repeat client, use the names the site uses for its own areas.
2. What you saw
The condition, stated plainly, with a photo framed so the hazard is obvious at phone size. One hazard per observation. Three hazards in one photo become three items, or two of them will be forgotten.
3. Why it matters
One line on the consequence or the standard. "Unprotected edge over 6 feet; fall protection required (29 CFR 1926.501)." Citing the standard is not about scaring anyone. It settles the "is this really a problem?" conversation before it starts.
4. What to do
The specific corrective action. "Install guardrail with midrail and toeboard, or restrict access with a controlled access zone." If there is an immediate interim control, say so separately: "Barricaded at time of walk."
5. Who, and by when
A named owner and a due date that fits the severity. An imminent hazard gets fixed before you leave the site. A housekeeping item can wait for the end of the week. Without this part, the other four are a report, not a task.
Severity should drive the due date
Pick a small, fixed scale and stick to it across clients and sites. Three or four levels is plenty. What matters is that each level maps to a response time everyone already knows, so the due date is not a negotiation every time.
- Imminent: stop work or control before leaving.
- High: within 24 to 48 hours.
- Medium: within a week.
- Low: next scheduled visit.
Write positives too
Observations are not only for hazards. Noting good practice ("all workers on L3 tied off correctly during deck pour") does two things. It gives the client a fair picture, and over time it shows which crews and sites are improving, which a list of only problems cannot.
Hand the observation to someone who was not on the walk. If they can find the spot, understand the hazard, and know what to do and by when without asking you a question, it is done.
Doing this at speed
The honest objection is time. Writing five careful parts for thirty items on a site walk is the evening gone. That is the part software should take over: capture the photo and a quick spoken or typed note on site, and let the structure (location, standard, recommended action) be drafted for you to review rather than typed from scratch.
That is how Safely Track works in the field: photo and note on the walk, a structured observation drafted with the citation and corrective action, then sent to the owner with a due date. Once it is fixed, the proof of fix comes back attached to the same item.