Describing Local Conditions in Consistent Terms

Community observation logs are only as useful as they are comparable. If one entry says "the water looked bad" and another says "strong smell near the bank," an editor reviewing them months later has almost nothing to line up side by side.

Our Community Monitoring Plan includes guidance built specifically to close that gap — not to make residents sound clinical, but to make their entries usable alongside the technical readings we publish.

Anchor the observation to a place and time

The single most useful habit is naming a fixed point — a jetty, a bridge, a specific bend in the creek — and returning to describe conditions from that same point each time. Add the date and, where possible, the time of day. A description without those anchors is difficult to compare against anything, including itself.

Describe what you observe, not what you conclude

There's a meaningful difference between "the water had a grey film near the edge" and "the water is contaminated." The first is something anyone reading the log can verify by going to look. The second is a conclusion that belongs to a lab result, not a field note, and stating it prematurely can undercut a report's credibility later.

"Write what you can see, hear, and smell — leave the conclusions to the readings that back them up."

Our field recording sheet, included with the Community Monitoring Plan, walks through prompts for color, smell, wildlife activity, and any visible changes since the last visit — all phrased as observations rather than verdicts.

Every quarter, our environmental editor reviews the submitted log entries with the group, flagging anything that would benefit from a follow-up technical reading. It's a modest process, but over a year it builds a record that holds up.