How to Keep Your Board Informed Between Meetings (A No-Surprises Communication Plan)

Many boards meet quarterly, some monthly. In between, they hear very little. Then a packet arrives a few days before the meeting, the first hour goes to getting everyone back up to speed, and anything that went wrong in the meantime lands on the table all at once.

Boards don't expect to hear everything, but they do expect no surprises. The fix is a plan for what reaches them between meetings: short, predictable, and clear about what needs their attention.

This guide is for executives of board-led organizations of any kind: associations, public authorities, special districts, cooperatives, institutes and member organizations. If you run a nonprofit and want a ready-made monthly email, see our board update email template.

Why "no surprises" is the rule that matters

A board's job is oversight. It approves the budget, sets direction, hires and evaluates the executive, and carries responsibility for the organization. It can't do any of that well with information that arrives only a few times a year.

When a board member hears about a problem for the first time at a meeting, or worse, from a member, a reporter or a council member, two things happen. The problem gets harder to handle, and trust in the executive takes a hit that outlasts the problem itself.

A no-surprises plan protects both. It means agreeing in advance on what the board will hear, when, and how, without flooding them with detail.

The three layers of board communication

Think of board communication as three layers, each with a different job.

1. The regular between-meetings update

A short update on a fixed schedule, usually monthly. Its job is to keep the board current so meetings go to decisions rather than briefings.

It should take under five minutes to read or watch. It covers what changed, what's at risk, and what you'll need from them soon.

2. The meeting packet

The full package before each meeting: financials, committee reports, and anything requiring a vote. Because the board is already current, the packet can focus on what's being decided.

3. The immediate notice

Some things can't wait for the monthly update. Agree with your chair, in advance, on what triggers an immediate notice. A reasonable starting list:

• Anything that could significantly change the budget or cash position
• Loss of a major funder, contract, or member
• A leadership or key staff departure
• A legal, regulatory or safety issue
• Anything likely to reach the press or elected officials
• A serious complaint about the organization or its leadership

For these, call the chair first. Then send the full board a short note: what happened, what it means, what you're doing, and when they'll hear from you next.

What to include in the regular update

Keep the same structure every time so the board learns where to look.

• The headline. One sentence on the most important thing since the last update. If there's bad news, it goes here, not at the bottom.
• A few key measures. Three to five numbers the board cares about, the same ones every time, so trends are obvious.
• Progress on priorities. Where the board-approved plan stands. Name what's on track and what isn't.
• Risks and issues. What's emerging, and what you're doing about it.
• Decisions coming. Anything the board will be asked to decide at the next meeting, with enough context to start thinking about it.
• Dates. Meetings, deadlines and events they should know about.

What to leave out: operational detail the board doesn't govern, program stories meant for members or the public, and anything that belongs in a committee report.

A between-meetings update template

Copy this and adapt the sections to your organization.

Subject: [Organization] board update: [Month Year]

The headline: [One sentence. The single most important thing since the last update.]

Key measures

Progress on this year's priorities

• [Priority]: [on track / behind / ahead]. [One line of detail.]
• [Priority]: [status]. [Detail.]

Risks and issues

• [Issue]. What we're doing: [action]. Next update: [when].

Coming to the board

• [Decision] at the [date] meeting. [One line of context.]

Dates

• [Date]: [meeting, deadline or event]

[Name] [Title]

A filled-in example

This example is fictional. It shows the level of detail that works for a regional authority.

Subject: Lakeshore Water Authority board update: October 2026

The headline: The treatment plant upgrade is on schedule, but steel prices have pushed the phase two estimate up by about 8%.

Key measures

• Operating budget spent: 61% at 58% of the year (slightly ahead of plan)
• Unplanned service interruptions: 2 (down from 5 last October)
• Customer complaints: 34 (flat)

Progress on this year's priorities

• Treatment plant upgrade: on track. Phase one handed over on October 9.
• Meter replacement program: behind. Supplier delays have pushed completion from March to May.

Risks and issues

• Phase two cost increase of roughly $1.1 million. What we're doing: re-bidding two packages and reviewing scope with the engineers. Next update: at the November meeting, with options.

Coming to the board

• Phase two contract approval at the November 18 meeting. The finance committee will review options on November 4.

Dates

• November 4: finance committee
• November 18: board meeting

Maria Chen General Manager

The cost increase is in the headline. The board now has a month to think about it before being asked to approve anything, and nobody will be surprised on November 18.

Beyond the board: funders and constituents

Most board-led organizations answer to more than the board. Funders, members, partner agencies and the public all have a stake, and they usually hear even less.

The same monthly update can serve them with light editing:

• Funders want to know their money is being put to work. Keep the progress and results; drop the internal risk detail unless it affects them.
• Members or constituents want to know what the organization is doing on their behalf. Lead with outcomes they'll recognize.
• Committee chairs often want a little more detail on their area. A short note on top of the general update is usually enough.

Write the board update first, then trim it for each group. It's much faster than writing four separate updates from scratch.

Mistakes to avoid

• Waiting until you have good news. Silence reads as either nothing happening or something being hidden.
• Letting the schedule slip. An update that arrives irregularly teaches the board it isn't important.
• Sending detail instead of judgment. The board needs your read on what matters, not every fact you have.
• Surprising the chair. For anything sensitive, the chair should never learn about it from the group email.
• Asking for decisions without notice. Flag major decisions at least one update before the meeting where you need them.

Try video for the regular update

A written update is fine. A short video from the executive is often better. Board members hear your judgment and tone, not just the facts, and a few minutes on camera takes less time than writing and formatting a report.

Send it with the written version. The video carries context and emphasis, and the text carries the numbers and dates.

Where Stakeholder Studio fits

Stakeholder Studio turns a short video update into the written versions: the board email, a briefing document, and trimmed updates for funders and constituents. It sends each group its own version, keeps videos private to the people you send them to by default, and shows you who opened it.

It's in beta now. If you lead an organization that reports to a board, join the waitlist.