The drought also exposed a weakness in our public dashboard. It displayed current readings, but it did not explain what a seasonal decline looked like. A resident saw the falling line and assumed the pond was failing. Another saw the same line and said the system was working because the decline was gradual. Both were reacting to a graph without enough context.
We asked the district hydrologist to help us create a short guide to interpreting the data. It explained normal seasonal ranges, the limits of a single gauge, and the difference between a warning threshold and a regulatory violation. We added a shaded band showing the expected range, based on the available historical record, and a note whenever the data set was too short to support a strong conclusion.
The guide was not exciting. It was useful.
At the next committee meeting, a resident asked why we did not use red whenever the water dropped. The hydrologist said color should not turn every ordinary seasonal change into an emergency.
“People need to know when to act,” she said, “and when to keep watching.”
That sentence became the dashboard's guiding principle. We would not hide bad news. We would not manufacture panic. We would show what we knew, explain what we did not, and make the next step clear.
In October, the developer completed the final section of the access road. The crossing passed inspection, the buffer was replanted, and the temporary construction fencing came down. A few residents from the new homes began using the trail. At first, they stayed near the entrance, uncertain whether they were welcome.
Denise suggested a neighborhood walk. We invited the new residents, explained the easement, and showed them the signs marking the protected area. One family brought a toddler who insisted on calling every frog a “pond puppy.” Another resident, a nurse who worked nights, asked whether she could volunteer for early-morning observations.
I watched people who had once been separated by a dispute exchange phone numbers over a map. It was not a grand reconciliation. Some people still distrusted the developer. Some homeowners still resented the costs. But the trail had become a place where practical questions could be asked without immediately becoming accusations.
At the end of the walk, Mercer arrived with the contractor's final inspection certificate. He handed a copy to Denise and said the company would maintain the crossing for the remainder of the required period.
“Thank you,” she said.
He looked toward the pond. “It turned out to be a more complicated site than we expected.”
“It was always complicated,” I said. “We just had to get the plans to admit it.”
He considered that, then nodded.
A few weeks later, I received a call from the state reviewer who had attended the field delineation. She was preparing a training session for local officials and wanted permission to use the Blue Heron case as an example of how public records, field observations, and local knowledge could improve a review.
I said yes, provided the presentation included the mistakes as well as the successful outcome.
“Especially the mistakes,” she said. “People learn more from those.”
She asked whether we could provide the original drainage exhibit, the revised map, and the monitoring agreement. I scanned the documents and sent them with a timeline. As I assembled the packet, I noticed how different the first and last pages looked. The first was an order written in absolute terms. The last was a set of conditions written with room for observation, correction, and review.
I did not want the case to become a morality play in which one side was entirely right and the other entirely wrong. That would make it easy to admire and useless to learn from. The county had made a mapping error. The developer had begun with an incomplete understanding of the site. The HOA had confused authority with ownership. We had sometimes mistaken suspicion for proof. The process improved when each of us was forced to deal with the actual record.
That was the story I wanted the training to tell.
The presentation took place in a county conference room with bad coffee and a projector that refused to recognize the first laptop. Officials from three neighboring counties attended. Some asked about the legal framework. Others wanted to know how we had persuaded residents to keep paying for monitoring after the immediate crisis ended.
I spoke about the public dashboard, the student observers, and the importance of publishing the limits of the data. Mara described the easement and the value of keeping a clear record of where people were allowed to go. Alvarez, now well into his seventies, held up the old paper map and said that digital systems were powerful but only as reliable as the information entered into them.