The One-Page Intelligence Briefing Your Board Will Actually Read

Most competitive intelligence dies in the board pack because it is written as news. Boards do not read information; they read options with prices attached. Here is a template for reporting competitive intelligence to the board as decisions: three signals, two implications, one recommendation.

Why intelligence dies in the board pack

The typical CI section of a board pack is chronological: a digest of competitor news from the quarter, ordered by date or by headline size. It is accurate, well-sourced, and unread. Not because directors are lazy, but because nothing in it asks them for anything. A document with no decision attached gets classified as context, and context is the first thing skipped when the pack is thick.

Decision-makers scan for two things: options, and the cost of each option. News summaries contain neither. When a director finishes your section without knowing what you want them to consider, the section failed regardless of how good the underlying analysis was.

There is also an incentive problem on the production side. Intelligence teams are judged on coverage, and missing a competitor announcement looks like failure. So the briefing grows. Every addition lowers the odds that the one decision-relevant item gets read. The failure is not analytical. It is a format that buries the ask under the evidence.

The subtler cost compounds over time. When the intelligence section is reliably skippable, the organization learns that competitor news carries no consequences, and the CI function quietly reclassifies itself as a clipping service. Budget follows perceived relevance, and the next cut lands on the team that never asked anyone for a decision.

The one-page structure

The structure is 3-2-1: three signals, two implications, one recommendation. One page, nothing attached to the body, total length under four hundred words. If it needs more space, the excess goes in an appendix that the board will not read, and that is fine, because the appendix exists for the audit trail, not for the meeting.

Signals. Each signal is one or two sentences, thirty words at most, and must be traceable to a named source with a date. A signal states an observable fact about a competitor or the market, never a conclusion. Competitor X posting a cluster of field-service roles in a region last quarter is a signal. Competitor X getting more aggressive is an opinion. Only the first kind survives contact with a skeptical director.

Implications. Exactly two, each a conditional sentence connecting a signal to your business. Cover the two branches that matter most: the one that threatens revenue and the one that opens an opportunity. If you have four implications, you have not finished editing. The constraint is the feature; it forces you to decide what actually deserves board attention this cycle.

Recommendation. One, in a single sentence containing a verb, an owner, and a cost. Authorize a service-coverage study for the region, led by operations, within a named budget: that is a recommendation. Continue to monitor the situation is not one. It is the absence of one, and boards can tell.

Writing implications as conditional statements

The working syntax is: if X continues, then Y. The condition carries the uncertainty openly instead of hiding it. You are not claiming the future; you are pricing one branch of it. That framing is what lets a board engage, because a conditional invites the only two questions that matter: how likely is the condition, and what does the consequence cost us.

For a strong signal, the condition is observable and checkable: if Competitor X's regional hiring converts into a service hub within two quarters, then our response-time advantage in that region narrows to parity on new bids. The board can send someone to verify the condition, and the consequence is specific to deals you actually compete for.

For a weak signal, keep the same syntax and soften the condition: if the reported capacity addition at Competitor Z is confirmed by permit filings, then quoting pressure in the mid-spec segment likely intensifies next year. The sentence now carries its own research agenda. The board learns both the branch and what evidence would resolve it, which is exactly what an executive intelligence briefing template should do with uncertainty: expose it, never bury it.

Two rules keep conditionals honest. Never write an implication whose condition you cannot describe how to check. And never upgrade a weak signal to a strong one in prose. If the evidence has not arrived, the word if stays in the sentence.

The conditional format also ages well. When the next briefing reviews whether last quarter's conditions held, the record reads as a series of testable claims rather than a pile of old news. Your hit rate becomes visible, and a visible hit rate is what buys the function its credibility.

Cadence and discipline

Run the briefing monthly or quarterly, matched to the board's own rhythm, and freeze the format. Boards learn to read a stable instrument far faster than a fresh one, and the second quarterly one-pager lands better than the first precisely because nothing about its shape is new.

A single anomaly never enters the decision document. One strange data point gets logged and watched; it becomes briefing material only when it repeats or when a second, independent source corroborates it. This rule protects you from the most common credibility killer in board reporting: escalating noise, being wrong once, and spending two years rebuilding trust.

Version and source discipline is non-negotiable. Every page carries a date, a version number, and a source list, and every statement traces to an entry on that list. Someone signs it. The signature is not ceremony; it names the person who answers when a director asks how we know this. For the monthly layer that feeds this page, see the companion piece on designing a CI digest that people actually open.

Escalation criteria deserve to be written down once and reused: escalate to a dedicated deep-dive when a confirmed signal crosses a revenue threshold you name in advance, when two independent signals converge on the same competitor move, or when the same recommendation has been deferred twice. Outside those triggers, the one-pager absorbs it. The table below summarizes the whole discipline.

Run this format for three cycles and something shifts: directors start arriving with questions about last quarter's conditions, which means the intelligence function has finally entered the decision process instead of decorating it.