A board meets for a few hours, a handful of times a year, to govern an organisation it does not run day to day. Almost everything it knows arrives in a document written by the executives it is meant to hold to account. That is the strange, fragile heart of corporate governance: the people being overseen prepare the evidence for their own oversight. Board reporting is the discipline of doing that honestly and well, and the board paper is where it happens or fails.

The quick version

  • A board paper is a structured document prepared for directors ahead of a meeting; the board pack is the bundle of them. Together they are how a board learns enough to decide.
  • The most important line in any paper is its purpose: is this for decision, for discussion, or for noting? Get that wrong and the meeting goes wrong with it.
  • A good decision paper states a clear recommendation, shows the options considered, including doing nothing, and gives directors enough to challenge it without drowning them in detail.
  • The deeper problem is information asymmetry: management knows far more than the board. Reporting either narrows that gap or quietly widens it.

The idea in depth: reporting exists to close an information gap

To see why board papers matter, start with the structural problem they answer. In their foundational 1976 paper, economists Michael Jensen and William Meckling framed the modern company as a web of principal–agent relationships: owners (principals) hire managers (agents) to run the business, but the managers know far more about what is actually happening than the owners ever can. That gap, information asymmetry, is the root of most governance trouble, because an agent who controls the information can shape the decision (Jensen & Meckling, "Theory of the Firm," Journal of Financial Economics, 1976; see the overview of the principal–agent problem).

That changes what a paper is for. Treat it as an instrument for closing the gap, not for managing the board's impression. The honest test isn't "does this make my function look good?" but "after reading this, does the board know what I know, including the parts I'd rather they didn't ask about?" A report that buries the bad news, or gives only the option the writer prefers, isn't poor writing; it's a small governance failure, because it leaves the people accountable for the company less informed than the people running it.

An honest limitation. Agency theory is a lens, not the whole picture. It can make boards and managers sound like adversaries locked in suspicion, when most boardrooms run on trust and shared purpose, and a rival "stewardship" view argues managers are often good-faith stewards, not self-interested agents. The point of naming the asymmetry isn't to assume bad faith, it's to remember that even well-meaning management has more information than the board, so the reporting has to do real work whether or not anyone is hiding anything.

The purpose line does the heavy lifting

If you change one thing about how your organisation writes for the board, change the first line. The governance guidance is consistent on this: a paper should declare what it is asking the board to do. The Governance Institute of Australia's guidance on board papers sorts every paper by purpose, for decision, for discussion, or for noting (with variants like for ratification), and frames the ask plainly: to seek approval for, to update, to seek feedback. A noting paper needs no recommendation; a decision paper lives or dies by one.

This sounds clerical. It is actually the single biggest lever on how a meeting runs. A paper mislabelled for noting that secretly wants a decision ambushes the board; a routine update dressed up for decision wastes the scarcest resource in the room, which is collective attention. The fix is mechanical and immediate. Open every paper with one sentence, "This paper is for decision: the board is asked to approve X", before a word of background. The reader now knows what kind of thinking to bring. Everything after that is in service of the ask.

flowchart TD
  A(["A board paper"]) --> B{"What is it
asking the board to do?"}
  B -->|"Approve something"| C(["For decision
needs a clear recommendation
+ options considered"])
  B -->|"Shape a direction"| D(["For discussion
frame the question,
offer the trade-offs"])
  B -->|"Stay informed"| E(["For noting
no recommendation;
flag what's changed"])
The purpose line routes the reader's attention before the content starts. Leaders Loop

What a decision paper owes the board: a real choice

The hardest papers to write well are the ones that ask for a yes. A weak decision paper presents the recommendation as the only conceivable path; a strong one shows the board a genuine choice and then argues for one route through it. The reason is governance, not style: directors carry legal duties of care and judgement, and they cannot exercise judgement over a decision that has been pre-made for them.

That is why the better governance guides insist on showing the options considered, including the option to do nothing. As Board Intelligence puts it in its guide to decision papers, directors "need to understand what other options have been considered and the reasons for their rejection," including "the possibilities of doing nothing, rejecting the proposal, or pushing it down the road", with the caveat that "options exist to clarify the argument, not to give the board a free choice." So, for any paper asking for approval: lay out the realistic alternatives, say plainly why each was set aside, and keep the do-nothing case on the page even when it's obviously wrong. A board that can see the discarded options trusts the recommendation more, not less, and occasionally catches the one you discarded too quickly.

The honest test of a board paper: after reading it, does the board know what you know?

The companion skill is restraint. The Institute of Directors in New Zealand, in its tips for better board papers, makes the point that non-executive directors attend infrequently and won't carry forward the context an executive lives in daily, so a paper must supply background without burying the decision in operational detail that belongs in a management report. The craft is subtraction: enough for an outsider to decide, no more. Push the reference material to appendices; keep the argument short enough to be read on a Sunday evening, which is when much of it actually is.

The chair owns the standard

Good reporting isn't only the writer's job; someone has to set and defend the bar. Under the UK's Corporate Governance Code, maintained by the Financial Reporting Council, the chair is responsible for ensuring that directors receive accurate, timely and clear information, and that they get it far enough ahead of the meeting for genuine consideration and challenge. Those three words are a usable editorial checklist: accurate (the numbers reconcile and the bad news is in there), timely (it lands days before, not the night before), clear (a non-specialist can follow it).

If you chair or run a board, make the standard explicit and enforce it. Set a paper template with a mandatory purpose line and recommendation; impose a circulation deadline and send late papers back; cap length so the pack stays readable. This connects directly to how the board evaluates itself, David Nadler's Harvard Business Review study "Building Better Boards" (2004) names access to information as one of the core domains that separate high-performing boards from compliant ones, alongside composition, agenda and culture. A board starved of clear information cannot govern well no matter how good its members are.

A worked example

Take a mid-sized charity, call it Riverbank Trust, whose finance director wants the board to approve replacing its ageing case-management system. (Illustrative figures throughout; this is a teaching example, not a real organisation.) The first draft of her paper is eleven pages: vendor history, a feature matrix, screenshots, and a closing line recommending the £180,000 platform her team has already chosen. It is labelled, vaguely, "IT Systems Update."

Run it through the lens above and it fails on every count. The purpose is muddled, is this a decision or an update? There is one option, not a choice; the do-nothing case (limp along another year) and the cheaper middle path (a hosted upgrade at, say, an illustrative £60,000) are nowhere. The eleven pages bury the one question the board can usefully answer. A trustee reading it on Sunday night cannot tell what they are being asked to do, only that someone has already decided.

flowchart LR
  A(["Draft: 11 pages
'IT Systems Update'
one option, pre-decided"]) --> B(["Add the purpose line:
'For decision, approve
system replacement'"])
  B --> C(["Show 3 options:
do nothing · £60k upgrade ·
£180k replacement"])
  C --> D(["Cut to ~3 pages
+ detail in appendix"])
  D --> E(["Board can challenge,
then decide with confidence"])
The rewrite doesn't add work, it moves the thinking to where the board can use it. Leaders Loop

The rewrite opens: "This paper is for decision: the board is asked to approve replacing the case-management system at a cost of £180,000 over three years." Then three options, do nothing, a £60,000 hosted upgrade, the full replacement, each with its cost, risk, and why it was kept or set aside. The recommendation stays, but now it is an argument the board can test, not a fait accompli. Eight pages of vendor detail move to an appendix for the trustees who want them. The paper is shorter, more honest, and far more likely to get a clean, confident yes, because the board can see the choice it is actually making.

Frequently asked questions

What's the difference between a board report and a board paper?

In practice the terms overlap. "Board paper" usually means a single document on one agenda item, a decision, a discussion topic, or a noting item, while "board reporting" is the broader practice, including the regular performance reports (finance, risk, operations) that a board receives each meeting. The "board pack" is the whole bundle sent out before the meeting. The principles are the same throughout: clear purpose, right level of detail, honest about the bad as well as the good.

How long should a board paper be?

Shorter than the writer's instinct, almost always. Governance guidance converges on a few pages of argument for most papers, with reference material pushed to appendices, a decision paper of around three to four pages plus a one-page summary is a common benchmark. Length is a symptom: a paper sprawls when the author hasn't yet decided what the board actually needs to know. Brevity signals that you understand the topic well enough to compress it.

Should a board paper include a recommendation?

A decision paper, yes, a clear, single recommendation is the point of it, and leaving it out forces the board to reverse-engineer what you want. A discussion or noting paper doesn't need one; there it's enough to frame the question or flag what has changed. The mistake is a recommendation that hides the alternatives. State your recommendation and show the options you rejected, so the board is approving a considered choice rather than rubber-stamping the only door you left open.

Who is responsible for the quality of board papers?

Authorship sits with management and the company secretary, but the standard is the chair's to set and defend, under the UK Corporate Governance Code the chair must ensure directors get accurate, timely and clear information. In practice that means a shared template, a circulation deadline, and a willingness to send substandard papers back. Quality is a system, not a talent: get the template and the deadline right and the average paper improves more than any single author could.

How do I report bad news to the board?

Early, plainly, and near the top. The temptation is to soften or delay, but a board that learns of a problem late, or from someone other than management, loses trust fast, and that trust is hard to rebuild. State the issue, its size, what's being done, and what (if anything) you need from the board. A reputation for surfacing bad news straight is the most valuable thing a reporting executive can build; it's what lets the board believe the good news too.

Related in the Toolkit

Reporting only makes sense alongside who's in the room and what they owe: the split between executive and non-executive directors is exactly why papers must explain themselves to outsiders, and the legal weight of director duties is why a paper has to give directors a real choice to exercise judgement over.

Where to go next