From the Local Government edition of October 16, 2026
Fairhaven, Massachusetts Select Board adopts an IT-drafted staff AI policy with five principles, pending public works board and town counsel review
Town of Fairhaven, Massachusetts · Municipal governance and staff AI use · Fairhaven, Massachusetts, United States
- Publisher
- Fairhaven Neighborhood News
- Original publication
- October 15, 2026
- Source retrieved
- 2026-10-17
- Event date
- 2026-10-13
What happened
On Oct 13 the Fairhaven Select Board adopted the IT director's more comprehensive draft AI policy over a board member's earlier draft, adding her preamble and excluding school employees, who have their own policy. Adoption is pending review by the autonomous Board of Public Works and town counsel. The policy sets security requirements, acceptable use and approved tools chosen by data sensitivity. Five principles: the employee owns the output; tool choice follows data sensitivity, not convenience; no AI system makes the final determination affecting a resident; transparency by default so residents know when AI shaped something affecting them; and anything entered into a public AI service is treated as disclosed. The IT director said answers must be vetted because AI is not always accurate and called the policy a living document.
Why it matters
Shows a small New England town adopting a principle-based policy where resident transparency and data-sensitivity tool selection are explicit, and where autonomous boards and school departments fragment who is covered.
Evidence and measured results
Neighborhood News article opened in full via curl HTML save; both draft policies are said to be in the 9/28 and 10/13 meeting packets, which were not opened.
Limitations and uncertainty
Local weekly report; policy text and packet not opened; final adoption pending review; no list of approved tools reported.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-16; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Town needs safe staff AI use with resident transparency but little dedicated capacity.
- Stakeholders
- Select Board
- Town Administrator
- IT Director
- Board of Public Works
- Town counsel
- Discovery questions
- How will residents be told AI shaped a decision?
- Which tools pass security vetting?
- Will BPW adopt the same policy?
- Who updates the living document?
- Value hypothesis
- Clear tiers and disclosure rules may reduce risky public-AI use; no outcome data.
- Potential engagement
- Short engagement producing a data-sensitivity tool matrix, disclosure template and staff briefing.
- Unsupported claims
- Time or cost savings
- That the policy is final
- That disclosure is already practiced
Pre-sales engineering
Role takeaway
- Fit
- Small municipalities choosing tools by data sensitivity.
- Architecture and integration
- Two-tier tool allowlist with labeling of AI-assisted resident-facing outputs.
- Prerequisites
- Data classification scheme
- Department vetting criteria
- Inventory of tools in use
- Constraints
- Schools and BPW governed separately
- No resident-affecting final AI determinations
- Public AI inputs treated as disclosed
- Security
- Security vetting gates tool approval; specific controls not described.
- Proof of value
- Vetted tool list mapped to data classes
- Disclosure label used on sample documents
- Spot-check of staff verification
Delivery
Role takeaway
- Work
- Finish legal and BPW review, publish tools, train staff, set review cadence.
- Dependencies
- Town counsel
- Board of Public Works
- IT Director
- Department heads
- Ownership
- IT Director with Town Administrator.
- Skills and adoption
- Staff must vet AI answers; training approach not reported.
- Governance checkpoints
- Counsel sign-off
- BPW decision
- Periodic living-document review
- Acceptance criteria
- Proposed: final adoption recorded after counsel review
- Proposed: approved-tool list published
- Proposed: disclosure practice documented for resident-facing outputs
- Risks
- Coverage gaps across boards
- Policy drift
- Disclosure duty not operationalized
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Tool selection by data sensitivity implies at least two tiers (public AI services for public information, vetted tools for sensitive data) and department-level vetting of software.
Governance
Who approves, reviews and stays accountable for outcomes?
Adoption is conditional on Board of Public Works and town counsel review; school department and BPW coverage are separate, so a single town-wide policy is not yet in force.
Security and privacy
What data, permissions and controls need testing?
Treat public AI inputs as disclosed; security vetting determines approved tools; no technical controls described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Employees personally accountable for AI output; training not described.
Procurement
What should contracts, pricing and exit terms secure?
Departments must vet software; approved-tool list based on security review.
Operating model
Which teams own the service once it runs?
Resident-affecting final determinations stay human; transparency by default creates a disclosure duty when AI shapes resident-facing work.
Publication history
- 2026-10-16Local Government · Issue 416 resources
Stable resource ID: fairhaven-ma-select-board-ai-policy-five-principles-20261015