The Next Governance Year Starts This Summer — Goal-Setting Timeline and Priority Preview

May 12, 2027


The January-through-June governance year is ending. The fall governance year — whichever month your board designates as the start — is the next cycle, and the most important determinant of whether that cycle succeeds is how the board uses the intervening months.

Most boards treat July and August as a governance pause. They don’t convene. They don’t plan. They don’t prepare. When they reconvene in September, the board president asks: “What should our goals be for this year?” and the discussion starts from scratch — no data, no priorities, no community input gathered during the summer, no preparatory work done by the superintendent.

That’s the difference between a board that sets goals and a board that adopts goals. A board that sets goals in September with no preparation produces goals that are generic, aspirational, and disconnected from the district’s actual trajectory. A board that adopts goals in September with preparatory work completed and priorities established produces goals that are specific, measurable, and aligned with the district’s trajectory.

The goal-setting timeline

A goal-setting process that produces real goals — adopted by the board, aligned with the district’s data, connected to the community’s priorities, and supported by the superintendent’s operational plan — requires four phases spread across the summer and early fall.

Phase one: June — Lessons and data collection. The board completes the spring lesson-capture framework from the May 3 piece and the self-evaluation from the May 5 piece. The superintendent compiles the district’s end-of-year outcome data, the budget-vs-actual analysis for the completed fiscal year, and any external data — state accountability ratings, federal designations, community survey results — that the board should consider during goal-setting. The board directs the superintendent to prepare a one-page data brief covering each domain the board expects to set goals in: academic performance, financial stewardship, operational efficiency, or whatever domains the board’s governance model uses.

The data brief is the board’s most important goal-setting input. The board that adopts goals without an end-of-year data brief is adopting goals based on impressions, not evidence.

Phase two: July — Priorities identification. The board does not meet formally in most districts. But the board president and superintendent should meet in July to review the June data brief and identify the three to five priority areas that the fall goal-setting process should focus on. The priority areas should answer one question: if the board achieves nothing else in the next governance year, what three things must be different?

The priority identification July meeting is not a goal-setting meeting. It’s a focus meeting. The board president and superintendent identify the priority areas and prepare a recommendation for the full board. The recommendation document is two pages: the three to five priority areas, a one-paragraph rationale for each priority area based on the June data brief, and a list of open questions the full board needs to discuss before adopting goals.

Phase three: August — Community and board input. August is the input month. The board president distributes the priority recommendation document to all board members with a request for written feedback. The superintendent presents the priority recommendation to the district’s stakeholder groups — the parent advisory committee, the teacher advisory committee, the student advisory committee if one exists. The community has an opportunity to provide input on priorities before goals are drafted.

A board that gathers community input on priorities before drafting goals produces goals the community recognizes as its own. A board that drafts goals and then presents them for community input produces goals the community feels were imposed.

The August board study session convenes for a goal-setting workshop. The board reviews the priority recommendation, the community input, the written feedback from board members, and the June data brief. The board discussion produces a consensus on priorities and a directive to the superintendent: draft goals for these priority areas using this data. The superintendent has thirty days to return with draft goals in the board’s preferred format.

Phase four: September — Goal adoption. The September study session receives the superintendent’s draft goals. Each goal includes a baseline, a target, a timeline, a resource estimate, and a monitoring schedule. The board discusses each goal, makes adjustments, and directs the superintendent to prepare the final version.

The September regular meeting adopts the goals. The adoption is not the end of the process — it’s the beginning of the governance year. But a board that arrives at September with the summer’s preparatory work completed adopts goals in one meeting instead of three and starts the governance year with a month of execution time that a board starting from scratch doesn’t have.

What the board should decide now

Before the summer break, the board should make three decisions that ensure the goal-setting timeline stays on track.

Decision one: The data brief deadline. The board directs the superintendent to deliver the end-of-year data brief by a specific date in June. The date should give board members time to read the brief before the last board meeting — or before they scatter for summer travel — so board members can ask clarifying questions before the summer pause begins.

Decision two: The July meeting date. The board president and superintendent schedule the July priority identification meeting before the summer break. A meeting that isn’t scheduled doesn’t happen. An hour in July makes the difference between a board that starts September with priorities ready and a board that starts September with a blank page.

Decision three: The August goal-setting workshop date. The board schedules the August study session for goal-setting before the summer break. The workshop should be at least ninety minutes — a sixty-minute discussion isn’t enough for a board to work through priorities, review data, and produce a consensus. The August workshop is the most important board meeting that isn’t a regular meeting. It determines whether the fall governance year starts with clarity or confusion.


Your free CTA: Reply to this email with the keyword GoalTimeline and I’ll send you the Goal-Setting Timeline and Priority Preview Template — a complete four-phase framework covering the June data brief format, the July priority identification meeting agenda, the August goal-setting workshop facilitation guide, and the September goal adoption protocol.

Your paid CTA: I offer a Strategic Goal-Setting Process Design — a full governance cycle planning engagement covering the priority identification framework, the community input design, the goal-setting workshop facilitation, and the monitoring schedule design. Reply to this email for pricing and availability.


This concludes the Summer Launchpad and Transition to Next Governance Year arc. This week’s pieces covered spring lessons capture (May 3), board self-evaluation using check-in data (May 5), summer reading and training planning (May 10), and the goal-setting timeline for the next governance year (May 12). The Summer Launchpad arc prepares boards for the fall governance year — the six-week transition between the June governance closeout and the September goal adoption. Subscribe at effectiveschoolboards.com to continue the series.

Backlinks: This piece completes the Summer Launchpad arc and connects to the spring lessons-capture framework from the May 3 piece, the board self-evaluation from the May 5 piece, and the summer reading plan from the May 10 piece. The four-phase goal-setting timeline extends the governance calendar framework from the Jan 6 governance calendar piece and the Jan governance year launch arc. The data brief methodology connects to the data review framework from the Feb and May data review pieces. The community input phase builds on the community engagement framework from the Mar community progress report and Apr community testimony response pieces. The September adoption protocol connects to the goal adoption process from the Jan governance year launch arc and the Jan 13 goal alignment piece. The monitoring schedule design connects to the Apr 21 post-adoption monitoring setup piece.