Community Engagement for Fall — How to Frame the Priorities Before the Data Review Season
September 8, 2027
The November data review will produce decisions. The December year-end reset will produce evaluation findings. The January goal adoption will produce new targets.
All of those governance actions matter. None of them will be fully understood by the community unless the board frames the priorities now, in September, before the data tells its story.
Here is what I have learned about community engagement from watching boards do it well: the board that engages the community in September has a fundamentally different relationship with the community in April. The board that waits until the budget hearing to explain what it has been doing all year has a relationship built on defense.
September is the month to frame the fall priorities. Here is how.
Frame the year’s goals and the fall data review calendar
The board adopted goals in January. The board worked through the summer to prepare for the fall. The community is not in the meeting room.
The board’s first community engagement action of the fall should be a public communication that frames what the board is working on, what the board will be reviewing this fall, and what the community should expect from the data review process.
This does not need to be complicated. A single-page community-facing document published on the district website, shared via the district newsletter, and mentioned at the September board meeting opening. It should answer three questions:
- What are the board’s adopted goals for 2027?
- What data will the board review this fall to monitor progress?
- How will the community learn about the board’s findings and decisions?
Most boards never answer those three questions in a single public document. The community learns about board priorities through news coverage of controversial votes, social media posts from individual board members, or the grapevine at school events.
The board that publishes a single, clear document in September takes control of the narrative before the data review season begins.
Establish the community feedback channel
The fall governance cycle produces data review findings, budget direction decisions, and goal-setting groundwork. The board will make decisions that affect the community. The community should have a structured way to provide input before those decisions are made.
I recommend a community feedback channel that runs from September through December. The format depends on the district size and community preferences. It could be:
- A standing community input item at each board meeting, framed around the specific governance decision the board is preparing to make
- A community survey tied to the goal-setting process, distributed in November when the board begins drafting 2028 goals
- A public work session in October or November focused on the budget guidance conversation — framed as input before the board delivers guidance to the superintendent
The specific format matters less than the consistency. The community should know, by the end of September, when and how they can provide input on the board’s fall governance cycle.
Invite the community to the data review
Most boards hold data reviews in closed study sessions or work sessions. The public is technically welcome — the meeting is posted, the agenda is published — but nobody shows up because the community does not know the meeting is happening or what it is for.
I recommend publishing the October data review date, time, and purpose in the September board meeting public notice. A brief description: “The board will conduct its first fall data review, examining progress against the goals adopted in January. The board will review data for each goal, make written decisions, and publish a community-facing summary of findings within 72 hours of the review.”
The community that knows the data review is happening, knows what the board is reviewing, and knows how to find the findings is a community that trusts the board’s governance process.
What the board should do this week
Three actions:
One. Draft the community-facing priorities document. One page. Three questions answered. Published on the district website and shared through the district communication channels by the end of September.
Two. Establish the community feedback channel. Decide the format. Announce it in the board meeting and through the district communication channels. Invite input.
Three. Publish the October data review date and purpose in the September board meeting notice. Invite the community to attend or to follow the findings online.
September community engagement is not about selling the board’s decisions. It is about creating the conditions for the community to understand the board’s governance process before the data review season delivers its findings.
Your free CTA: Reply to this email with the keyword FallEngage and I’ll send you the Community Engagement for Fall Kit — including the community-facing priorities document template, the community feedback channel setup guide, and the data review public notice language examples.
Your paid CTA: I offer a Community Engagement Strategy Session — a sixty-minute virtual session with the board president or communications lead covering the fall engagement calendar, the community-facing document design, and the feedback channel framework. Reply to this email for pricing and availability.
This piece closes the first week of the Fall Governance Cycle series. Monday’s piece (Sep 6) covered data packet preparation for the October data review. This piece covers community engagement — how to frame the fall priorities before the data review season begins. The next piece in the series picks up in late September when the Fall Operations Transition arc (the Sep 21-30 series) launches with the October data review readiness check. Subscribe at effectiveschoolboards.com to continue the series.