What Happens After the Public Hearing — Turning Community Testimony Into Board Action
April 26, 2027
The public hearing is over. The community showed up. People spoke. Some were passionate. Some were frustrated. Some asked specific questions about specific line items. Some made general statements about district priorities.
The board listened, took notes, thanked each speaker, and adjourned without adopting. That was the protocol. Now the question is: what happens next?
I’ve watched boards treat the public hearing as the endpoint of community engagement. The hearing happens, the community speaks, and the board proceeds to adopt without incorporating anything that was said. The testimony is recorded in the minutes and never referenced again. The community participated, but the participation produced no visible impact.
That approach does more damage than not holding a hearing at all. A hearing where testimony is heard but ignored tells the community: we went through the process, but your input didn’t matter. A board that holds a hearing and ignores the testimony has the worst of both worlds — the procedural burden without the trust benefit.
The twenty-four-hour follow-up
The day after the hearing, the board should send a communication to the community. The board president prepares a brief statement — one or two paragraphs — that does three things.
One: thanks everyone who participated. Name the range of topics that were raised, even if you can’t respond to every point. “The board heard testimony on early literacy funding, staffing ratios, facility maintenance, and transportation costs.” The community sees that the board was paying attention.
Two: confirm the next steps. “The board will consider all testimony during the adoption meeting on [date]. The superintendent has been directed to prepare responses to questions the board couldn’t answer at the hearing. Those responses will be available [timeframe].”
Three: invite continued engagement. “Community members who wish to provide additional testimony may submit written comments to [email] by [date]. Written comments will be included in the adoption meeting record.”
The communication goes out via the same channels the board used for the hearing notice — district email, website, social media, district newsletter. The same reach. The same timing.
Closing the loop at the adoption meeting
The separate adoption meeting — the one the board committed to during the hearing — is the opportunity to demonstrate that testimony mattered. The board president opens by acknowledging the hearing testimony and summarizing how it affected the board’s process.
I’ll give you an example. A board held a hearing where multiple community members raised concerns about transportation funding. The board didn’t have the data to respond at the hearing. The superintendent prepared a transportation budget analysis between the hearing and the adoption meeting. At the adoption meeting, the board president acknowledged the testimony: “Several community members raised concerns about transportation funding at the hearing. The superintendent has prepared a transportation budget analysis that shows we are, in fact, under-resourcing transportation relative to the prior year. The board is directing the superintendent to include a transportation resource assessment in the first budget-to-actual report for the new fiscal year.”
That’s closing the loop. The community raised a concern. The board investigated. The board reported. The board acted.
Compare that to: “We heard your concerns about transportation. We appreciate your input. The budget is adopted.” The community hears what they already know — that the hearing was a procedural step.
What to do about testimony the board can’t act on immediately
Some testimony will raise issues the board can’t address through the budget adoption process. A community member asks for a program the district doesn’t offer. A community member asks about a state policy issue the board can’t control. A community member asks about a past decision that predates the current board.
The board’s response to these questions determines whether the community feels heard even when the answer is “we can’t act on this right now.”
The protocol: acknowledge the concern specifically, explain why it can’t be addressed through the current budget adoption process, and offer an alternative avenue. “You raised a concern about after-school programming. That’s not an item in the current budget cycle, but the board will include after-school programming as a discussion topic in the May strategic planning work session. We invite you to attend.”
The key is offering a specific alternative, not a generic “we’ll take it under advisement.” A specific alternative — a future meeting, a committee assignment, a survey distribution — tells the community member that their concern was heard and redirected, not dismissed.
The documentation standard
The board should document every piece of testimony and the board’s response. This serves two purposes. First, it creates a record the board can reference throughout the year — if transportation funding reappears as a concern in the fall, the board has the hearing record to show it was acknowledged. Second, it demonstrates transparency. A member of the public can ask for the hearing record and see exactly which questions were asked and which responses were given.
The documentation format: a table with four columns — community member, topic, question/concern summary, board response. The table is included in the adoption meeting materials and posted publicly. The board president references the table during the adoption meeting opening.
The long-term trust impact
Community testimony doesn’t end with the adoption meeting. The trust the board builds through the hearing-to-adoption process carries into every subsequent interaction with the community.
Here’s what I’ve observed. A board that closes the loop — that documents testimony, that responds specifically, that acts where it can and redirects where it can’t — builds community trust that lasts through the year. When that board asks for community input on the next issue — the strategic plan, the superintendent evaluation, the facilities bond — the community shows up. Why? Because they learned that their input actually matters.
A board that holds a hearing and lets the testimony disappear builds community distrust. When that board asks for community input on the next issue, the community doesn’t show up. Why? Because they learned that their input is a formality.
The public hearing is not the endpoint of community engagement for the spring. It’s the midpoint. The board’s response to testimony — the follow-up communication, the adoption meeting acknowledgment, the documentation, the redirection of questions the board can’t currently answer — determines whether the community’s spring engagement produces trust or cynicism.
Wednesday April 28’s piece closes the April arc and looks ahead to May and June — the second data review, the superintendent evaluation process, and the year-end progress update.
Your free CTA: Reply to this email with the keyword TestimonyAction and I’ll send you the Community Testimony Response Protocol — a template for the twenty-four-hour follow-up communication, the adoption meeting testimony summary framework, the documentation table format, and the testimony-to-action tracking sheet.
Your paid CTA: I offer a Community Engagement Coaching Session — a ninety-minute call covering the hearing testimony documentation, the adoption meeting response protocol, and a long-term community engagement strategy for the remainder of the governance year. Reply to this email for pricing and availability.
This continues the April Governance to Impact arc: budget adoption, public hearing, mid-year check-in, post-adoption monitoring, and community testimony response. Today’s piece covers closing the testimony loop. Wednesday April 28’s piece closes the April arc and looks ahead to May and June — the second data review, the superintendent evaluation, and the year-end progress update. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece extends the public hearing execution protocol from the Apr 12 piece. The twenty-four-hour follow-up communication connects to the public hearing preparation checklist from the Apr 7 piece. The testimony documentation framework follows the board communication discipline protocol from the Feb 10 piece. The long-term trust framework builds on the board-to-community trust communication framework from the Mar 15 piece.