The 'No Surprises' rule for boards

The board should never hear important news for the first time at the meeting itself. A CEO who surprises the board loses trust faster than any other behaviour can rebuild it. This holds true even when the news is positive — surprises tell the board it does not have the full picture.

The three channels

How to keep the board ahead of the news:

1. Monthly chair contact — 30 minutes, fixed in the calendar. Even when nothing is urgent.
2. Pre-meeting briefing on difficult items — three to five days before the meeting. Never deliver hard messages only at the meeting itself.
3. Agreed thresholds — defined levels that trigger an email outside the meeting cycle.

The monthly chair contact

The chair is your earliest sounding board. Half an hour a month — including the months where "there's nothing to report" — builds the relationship that lets you call when something acute happens. If contact only happens when there's a problem, the chair will start reading every call as bad news. That creates the opposite behaviour in you: you postpone the conversation.

Brief the chair on hard items first

If you have a difficult message for the meeting — a covenant risk, a customer loss, a senior departure — the full board should not hear it for the first time at the meeting. Speak to the chair three to five days before, and let them decide whether the message should go to the rest of the board in writing first. In about 80% of cases the chair will say: "Send a short written update to everyone. We'll take the discussion at the meeting, focused."

Agreed thresholds

Define in advance what triggers a notification outside the meeting cycle. Written down, approved by the board. Examples:

• Loss of a customer representing more than 10% of revenue.
• Liquidity below 30 days of operations.
• Covenant headroom below 15%.
• Expected variance from annual budget above 15%.
• Departure of a member of the executive team.
• Material legal claim above an agreed threshold.

When a threshold is hit, a short written notification goes out — typically within 48 hours. Not a full memo. An email of 5 to 10 lines.

The five situations where notification most often fails

In practice, the failure happens in five concrete patterns. If you recognise yourself in any of them, that's where to tighten the discipline:

1. You hope it blows over. A number has moved the wrong way for 14 days. You're waiting for it to correct itself. It rarely does. The rule: if a number moves the wrong way for more than 7 days, it needs to be flagged.
2. You're waiting for "more data". You want the full picture before notifying. But the full picture often only arrives once the situation is locked in. The rule: flag with what you know now, and promise an update when more data is available.
3. You assume the chair already knows. "She saw the email, that's enough." But implicit communication doesn't count. The rule: if it matters, say it directly.
4. You don't want to cause unnecessary worry. You flagged last quarter too, and it passed. You don't want to "cry wolf". But notifications that don't materialise don't cost credibility — delayed ones do.
5. You're already working on the solution. You want to present the problem alongside the fix. Understandable — still wrong. The board should know about the problem even if the plan isn't ready.

Why CEOs delay

The most common reason boards get surprised is not bad intent — it's that the CEO hopes the problem resolves before the next meeting. Or doesn't want to "worry" the board about something that may pass. That logic always breaks. What you defer grows — and when it finally surfaces, it looks as if you've been sitting on it.

Template: the threshold email

When a threshold is hit, a short written message goes out — typically within 48 hours. Not a full memo. An email of 5 to 10 lines. The structure is simple:

Example — liquidity notification:

Subject: Notification — liquidity threshold reached

To the board,

Our liquidity dropped to 58 days of operations yesterday, below our agreed warning level of 60 days. The main driver is a delayed invoice from Customer A for €210K, expected within 14 days.

Consequence: We remain above the 30-day floor in our loan agreement, but the buffer has tightened. If Customer A does not pay as expected, and one further deviation hits, we could reach the floor by mid-June.

My recommendation: We take this at the next meeting on 23 June. Until then I'll track daily and report back if the threshold drops below 50 days. No extraordinary meeting needed now.

Best, Lars / CEO

Three paragraphs. No panic. A recommendation included. An email like this takes 15 minutes to write and often saves 2 hours at the meeting itself — because directors arrive prepared instead of reacting in the room.

What if the board has already been surprised?

It happens. A customer leaves without warning. A reporting number lands further off than expected. You spot the problem too late. Three rules:

• Acknowledge the delay before you explain the event. "I should have flagged this two weeks ago, when I first saw the signal. I didn't. Here's what's happened."
• Bring the plan, not just the problem. Even a partial plan is better than none. "I propose we do X over the next 30 days. Here's what that requires from the board."
• Change the notification routine concretely. Not "I'll do better" — but "from now on I check [specific thing] every Friday, and notify if [specific threshold]".

A single surprise can be forgiven. A pattern of surprises is very hard to recover from. It is the change in behaviour, not the apology, that makes the difference.

The hard rule

If you're standing there asking yourself "should I call the chair about this?" — the answer is yes. It is a simple rule, because the doubt itself is the signal: if it weren't worth mentioning, you wouldn't be in doubt.