Seven consecutive public speakers unanimously opposed the board's primary action of the evening, accusing the board of misusing funds, bypassing democratic processes, and dismissing taxpayer voice — yet the board proceeded unanimously without substantively addressing the core objections, producing the clearest board-versus-community confrontation the meeting record documents.
Date Tuesday, January 6, 2026Duration 3.6hSpeakers 2Public comments 7Heated
Why this is flagged: Seven consecutive public speakers unanimously opposed the board's primary action of the evening, accusing the board of misusing funds, bypassing democratic processes, and dismissing taxpayer voice — yet the board proceeded unanimously without substantively addressing the core objections, producing the clearest board-versus-community confrontation the meeting record documents.
Public impact
Issues from this meeting with documented community impact.
01
Security Redesign Project — $750K+ Expenditure from Reserves
$440,000 from maintenance trust + $310,000 from contingency fund = $750,000 total, with Triple Construction contract at $699,500 plus optional add alternates, for a project flagged since 2022 Affected: All Hopkinton taxpayers and school district residents; funds drawn from maintenance trust and contingency reserves that would otherwise be available for emergencies or returned to taxpayers
other high impact
02
FY27 School Budget Tax Rate Increase
Projected 95-cent per $1,000 assessed value tax rate increase, bringing school rate to approximately $10.07; $29.3M total budget representing a 4.7% year-over-year increase Affected: All Hopkinton property taxpayers
tax increase
03
Contingency Fund Draw — $400K Planned for FY27 Operations
Planned $400,000 contingency fund draw in FY27 budget, compared to $119,000 drawn last year — more than 3x increase — on top of $310,000 already withdrawn this meeting for the security project Affected: All Hopkinton taxpayers; draws down reserve that cushions against future emergencies or tax spikes
other high impact
04
Declining State Aid Increasing Local Tax Burden
$90,000 decrease in special education state aid and $98,000 decrease in enrollment-based aid (ADM formula), totaling $188,000 in lost state revenue that shifts burden to local taxpayers Affected: All Hopkinton property taxpayers who must make up the shortfall through local taxation
tax increase
Controversy & dissent
Where the board, the community, or the agenda diverged.
•
Board unity: Despite significant and unified public opposition, the board voted unanimously on every major security project decision; the only recorded failed motion (benefits trust) reflected board division on a lower-stakes item.
Potentially controversial issues
01
Security Redesign Funding Without Voter Warrant Article
The board approved $750,000+ in spending from maintenance trust and contingency funds for a planned capital project without putting it to a public vote. All seven public speakers who commented opposed this approach, arguing the funds belong to taxpayers and decisions of this magnitude require democratic input via a warrant article. The project has been known as a need since at least 2016, undermining the urgency argument used to bypass the warrant process.
Board position: Board unanimously approved both fund withdrawals, asserting they have legal authority and a fiduciary obligation to act on a known security vulnerability without further delay, citing rising school shooting statistics and Homeland Security flags since 2022.
high concern
02
Appropriateness of Using Contingency and Maintenance Trust Funds for Planned Project
Multiple residents argued the maintenance trust should be reserved for emergencies (roof collapses, HVAC failures) and the contingency fund by definition covers unplanned events — not a capital project in planning for over 18 months. The board's characterization of the funds as 'savings' was also disputed; residents argued the surplus resulted from unfilled staff positions, not prudent saving.
Board position: Board maintained the funds were lawfully available, accumulated appropriately, and that using them avoids burdening taxpayers with a bond or tax increase for a legitimate safety project.
high concern
03
Triple Construction Contractor Selection and Bidding Process Integrity
Resident Tricia Lambert raised concerns about potential impropriety in awarding the contract to Triple Construction, the same firm that provided the original cost estimate. She also questioned the timing of public presentations during holidays. The board only partially addressed this by correcting a factual error about bid amounts, without substantively defending the procurement process.
Board position: Rob Nadeau corrected Lambert's figures (noting the gap between Triple's estimate and bid was $15,000, not $500) but did not directly address the conflict-of-interest concern about the estimator becoming the contractor.
medium concern
04
FY27 Budget — 4.7% Increase with 95-Cent Tax Rate Impact
The proposed $29.3M budget represents a 4.7% increase driving a projected 95-cent tax rate increase to $10.07, compounded by declining state aid (special education aid down $90K, enrollment-based aid down $98K) and plans to draw $400,000 from the contingency fund — more than three times last year's draw. Residents are already expressing tax fatigue, and this budget pressure arrives the same meeting the board spent $750K+ from reserves.
Board position: Board is presenting the budget as driven by factors largely outside their control (special education costs, state aid formulas) while acknowledging the tax rate impact is real and not yet finalized.
medium concern
05
Open Enrollment Policy Under RSA 194D
State law may require the district to designate a school for open enrollment, creating competitive pressure between districts and potential financial uncertainty. The board deferred a decision, acknowledging the complexity and unknown fiscal implications. Residents had no opportunity to weigh in as this topic surfaced mid-meeting without a formal public hearing.
Board position: Board consensus to defer, directing staff to prepare structured options with pros and cons for the next meeting.
medium concern
06
Benefits Trust Fund — Decision to Not Proceed
The motion to establish a $35,000 benefits trust to buffer unexpected health insurance cost spikes failed. This leaves the district without a financial cushion for a known volatile cost driver, potentially forcing future mid-year budget adjustments or larger tax impacts if health costs spike.
Board position: Board decided not to pursue the benefits trust warrant article this year, effectively accepting the risk of unbudgeted health cost increases.
Internal dissent
The motion failed, indicating at least some board members opposed it, though the specific vote tally and individual positions were not detailed in the summary.
low concern
Split votes
Motion to allocate $35,000 to benefits trust fund warrant article
Failed — exact tally not recorded
Community vs. board tension
⚖
Security Project Funding Method — Warrant Article vs. Board Authority Community wants: All seven public speakers demanded the project go to a town-wide warrant article vote, arguing residents have a democratic right to weigh in on $750,000+ in expenditures and that the board is making a decision too large for five elected members to make unilaterally. Board response: Board unanimously proceeded with the fund withdrawals and contract award anyway, acknowledging public opposition but asserting legal authority, safety urgency, and fiscal prudence as justifications. Many specific concerns (about the warrant process, taxpayer voice, and appropriate fund use) received no direct response during public comment.
⚖
Definition and Appropriate Use of Contingency and Maintenance Trust Funds Community wants: Residents argued the board was misusing funds designated for emergencies to fund a long-planned capital project, and disputed the 'savings' framing given the surplus stemmed from unfilled staff positions. Board response: Board explained the legal mechanics of how funds accumulated but did not substantively rebut the emergency-vs-planned-project distinction or the characterization of the surplus origin.
⚖
Public Engagement and Democratic Accountability Community wants: Multiple residents expressed broader distrust, noting that public comment feels performative since the board proceeds regardless, that many community members don't attend meetings because they feel unheard, and that the project was discussed in coffee shops and on social media reflecting wider community concern not captured in the room. Board response: Board did not directly address the democratic engagement or trust concerns. Rob Nadeau acknowledged the board's representative role but framed it as justification for acting, not a prompt for broader consultation.
⚖
Completeness of Security Solution Community wants: Tricia Lambert argued the project only addresses the front entrance while the rear of the building remains unsecured, making the investment a partial and potentially inadequate fix — 'lipstick on a pig.' Board response: Rob Nadeau indicated rear entrance security had been discussed separately but did not provide specifics on plans or timeline to address that vulnerability.
Ready to share? AI-written accountability posts about this meeting's controversies.
Lambert argued that the $440,000 maintenance trust withdrawal should be returned to taxpayers and put to a vote at March town meeting. She expressed concerns about awarding the contract to Triple Construction, who provided the original estimate, suggesting potential impropriety in the bidding process.
Key concern
Money should be returned to taxpayers and project should go to town vote; concerns about contractor selection process
Board response
Rob Naito provided clarification that the difference between Triple's estimate and bid was $15,000, not $500 as Lambert stated
Board only addressed the factual correction about bid amounts but did not respond to the core concerns about town voting or contractor selection process
Blamy praised the board for having residual funds but argued that taking $440,000 from repair and maintenance fund for a planned project was inappropriate. He stated this fund should be reserved for emergencies like roof collapses or heating system failures, not planned construction known about since 2016.
Key concern
Maintenance trust fund should be reserved for emergencies, not planned projects; poor long-term planning
Board response
Rob Naito explained the mechanics of how the money came to be available through unassigned fund balance and encumbered projects
Board explained the funding mechanism but did not address the core argument about appropriate use of emergency funds vs. planned projects
Clement argued this $750,000 project should be a warrant article since all funding came from operational expenses that were appropriated by the legislative body. She felt this represented a misappropriation of funds and that five board members shouldn't make this decision alone.
Key concern
Large capital project should go to warrant article for community vote; concerned about misappropriation of operational funds
Board response
No direct response from board during public comment period
Board did not respond to concerns about warrant article process or misappropriation during public comment
Schiavone referenced a previous $50,000 hot water heater project and argued the board should table this project. He warned that the contingency fund might be needed more in the future and suggested the board needs to learn better budgeting.
Key concern
Project should be tabled; contingency fund may be needed for other purposes; concerns about board's budgeting practices
Board response
No direct response from board during public comment period
Board did not respond to the speaker's concerns during public comment
Garden acknowledged the security need dating back to 9/11 but criticized the original yurt design as poor planning. She requested the project be put to a warrant article for voters to decide, citing rising taxes and the need for careful money management.
Key concern
Project should go to warrant article for community vote; concerns about rising taxes and fiscal responsibility
Board response
No direct response from board during public comment period
Board did not respond to the request for warrant article during public comment
Gavin briefly stated that he agreed with Lauren Clement that the decision group was too small to make this large financial decision and the project should go to the town for a vote.
Key concern
Board is too small a group to make this magnitude of financial decision; should go to town vote
Board response
No direct response from board during public comment period
Board did not respond to the concern about decision-making authority
Blamy echoed previous comments about needing a warrant article and expressed concern that the money felt "stolen from taxpayers" since there was no public voice in the decision to not return the surplus funds.
Key concern
Project should be warrant article; feels taxpayers were denied voice in surplus fund decision
Board response
No direct response from board during public comment period
Board did not respond to concerns about taxpayer voice or warrant article process
In second comment, Clement clarified that 100% of stakeholders who attended favored a warrant article and expressed concerns about the $900,000+ figure mentioned and whether the project would stay at $700,000.
Key concern
All attendees favor warrant article; concerns about potential cost overruns beyond $700,000 budget
Board response
Rob Naito clarified the $900,000 was from a different bidder and confirmed the project budget cap
Board clarified the budget confusion but did not address the warrant article request supported by all attendees
During contingency fund hearing, Clement clarified the budget committee did not have a formal vote but a straw poll, and argued the district didn't "save" money but rather had unspent funds due to unhired staff positions.
Key concern
Correction about budget committee process; disputes characterization of funds as "savings"; contingency fund not appropriate for capital projects
Board response
No direct response from board during public comment period
Board did not respond to clarifications about budget committee vote or appropriate use of contingency funds
During contingency fund hearing, Blamy defined "contingency" as an unplanned event or emergency and argued this planned project doesn't fit that definition. He suggested the contingency fund should be reserved for project overruns.
Key concern
Contingency fund being misused for planned project rather than emergencies; fund should be saved for potential cost overruns
Board response
No direct response from board during public comment period
Board did not respond to the definition and appropriate use of contingency funds
In second comment, Schiavone shared his 40 years of facilities maintenance experience, stating projects always have cost overruns and the $50,000 contingency may not be sufficient. He criticized past poor planning decisions by the district.
Key concern
Based on experience, projects always go over budget; insufficient contingency; criticism of district's planning history
Board response
No direct response from board during public comment period
Board did not respond to concerns about cost overruns or planning criticism
In second comment, Garden compared the situation to insurance driven by fear and emphasized this should go to warrant article as a "we the people" issue. She noted meeting attendance issues are partly due to people having busy lives and growing distrust.
Key concern
Project should go to warrant for democratic process; poor meeting attendance due to busy lives and distrust in government
Board response
No direct response from board during public comment period
Board did not respond to democratic process concerns or attendance issues
In second comment, Blamy noted there has been discussion about this project beyond the meeting (coffee shops, social media) and that many people don't attend meetings because they feel their input doesn't matter. She objected to the board's reasoning that warrant article shouldn't be used because "no means no."
Key concern
Public discussion exists beyond meetings; people don't attend because they feel unheard; objects to board avoiding warrant process
Board response
No direct response from board during public comment period
Board did not respond to concerns about public engagement or warrant article avoidance
In second comment, Lambert argued the security fix is incomplete as the building's rear remains unsecured, comparing it to "putting lipstick on a pig." She criticized the contractor selection process and timing of presentations during holidays.
Key concern
Security solution is incomplete; rear of building remains vulnerable; questionable contractor selection; poor timing of public presentations
Board response
Rob Naito clarified that rear entrance security has been discussed and that meetings were held in October/November, not December
Board addressed timing clarification and mentioned rear entrance discussions but did not fully address security concerns or contractor selection issues
Support coverage
Creating this report cost real money.
MeetingWatch attended, transcribed, and analyzed this meeting on its own dime. If this work is valuable to you, chip in to keep covering Hopkinton.
Follow Hopkinton
One email when a new report is published from the School Board — or one weekly digest.
Report composed by claude-sonnet-4-20250514, claude-sonnet-4-6, claude-opus-4-6 · analyzed 2026-06-01.
Show me what's happening near me.
MeetingWatch covers communities across the country. Tell us where you are and we'll surface the meetings, votes, and decisions in your town.
Request coverage
We'll let you know when MeetingWatch starts covering your area.
Please add your name and a valid email.
Check your inbox — click the link in our email to finish your request.
Or browse covered communities:
Send feedback
Spotted an error, or have a tip? Let us know — we read every note.
Know where the video for this meeting lives? Paste the link below and we'll add it.
We'll email you a link to confirm — this keeps out spam. We won't share your address.
Please add a valid email and a message.
Check your inbox — click the link in our email to confirm your feedback.
Search MeetingWatch
MeetingWatchStay informed — without the slant.
Hours of public meetings. Zero time to watch them.
MeetingWatch uses AI to attend every public meeting in covered communities —
transcribing debates, logging votes, and surfacing what actually mattered.
No slant. No bias. Just what was said on the record, so you can stay
informed about your town without burning your evenings.
44
Communities covered
533
Meetings analyzed
1946
Voices logged
Get started in three steps
1
Tell us where you live.
We'll surface the meetings, votes, and decisions in your town first.
One weekly email. Decisions, dissents, and the off-agenda items from every covered community. Unsubscribe in one click.
✓ Subscribed — check your inbox to confirm
3
Support the work.
MeetingWatch is a civic accountability project. Reader contributions cover transcription, hosting, and the cost of attending every meeting — and help grow coverage to more towns.