Committee cites Project Blue as cautionary tale on transparency
Oct 7, 2026
Members said Project Blue failed primarily due to lack of transparency and changing project scope; they urged clear end-user disclosure, fixed criteria, and stronger community engagement to avoid similar outcomes in Florence.
The full story
Several committee members repeatedly returned to "Project Blue" as a cautionary example of how promising proposals can collapse when developers change scope and withhold information. Members said changing project descriptions and early nondisclosure agreements eroded trust, and that transparency about end users and power/water plans is essential to maintain public confidence. "It was the lack of transparency," one member said, noting that even after unanimous public rejection some work on the project continued, which deepened mistrust.The group discussed requiring concrete developer commitments — such as a named end user or firm engineering plans — at key permitting stages and using breakout-topic outreach sessions so residents can get topic-specific information (power, water, infrastructure). Committee members also suggested considering community benefits agreements or set-term approvals so towns can hold developers to clear obligations over time.
Sign up to keep reading.
Your free newsletter brings you what your city council, county, and school board discussed and decided.
Keep reading for free
Create a free account to finish this story and see the video, transcript and key details.
Continue with GoogleContinue with emailAlready have an account? Log in →