Reading the board brief

The board brief is the presentable form of everything above. It leads with your priorities rather than with your security program, which is the order a board actually thinks in.

The structure

Each priority gets a row stating whether your capabilities support it, what specifically falls short, and the target date. Below the priorities sits the security program context: your score, what moved, and the talking points behind it. That ordering is deliberate. The board cares about the outcomes first and the program second.

What the statuses mean

A priority is either supported at the level it requires, or it is not, or it has not been assessed well enough to say. That third state is real and the brief shows it rather than defaulting to a reassuring answer. A priority with unconfirmed mappings or missing assessment data will say so.

What to do with it

Read the priority rows aloud as they are written. They are phrased to be said to a board without translation. When someone asks what it would take, the plan estimate is the answer, and when someone asks whether the work is happening, the roadmap is.

Exporting

The brief can be exported for circulation. See Board reports.