Board Papers That Survive a Governance Review

The Paper Is the Record of the Decision, Not the Case for It

Most board papers are written as advocacy. An executive has reached a view, the paper explains why the view is correct, and the recommendation sits at the end as a conclusion the reader has been led to. That is a natural way to write and it misunderstands what the document is for. A board paper is not primarily read at the meeting; it is read afterwards, by people who were not there — auditors, a regulator, a successor board, a court, an acquirer's diligence team — and what they are looking for is not whether the decision was right. It is whether the board understood what it was deciding.

That distinction has practical force because the two documents look different. A persuasive paper presents the recommended course and the reasons for it. A paper that functions as a record presents the decision, the alternatives that were considered and why they were not preferred, the assumptions the recommendation depends on, what happens if those assumptions are wrong, and what the board is being asked to accept. The first is shorter and reads better. The second is what a governance review is looking for, and its absence is what a governance review finds.

The point is frequently misread as a call for caution or for longer papers, and it is neither. A board that approves an ambitious course after seeing a genuine downside case has made a stronger decision, on the record, than a board that approved a modest one on a paper that showed only upside. Governance is not a bias toward inaction; it is a requirement that the risk actually taken was the risk the board knew it was taking. Papers that hide the downside do not protect the recommendation — they leave the board unable to demonstrate that it was informed, which is the exposure that actually matters.

This article sets out what that means in practice: what the minute has to be able to say and how the paper must support it, how a downside case should be declared and by whom, how a board detects management bias and what makes a paper look advocated rather than assessed, how materiality decides what belongs in the paper and what belongs in an annexure, how an audit or risk committee reads differently from the main board, and why a paper that only argues for approval is itself a governance risk. Where our transaction advisory practice prepares material that will reach a board, it is built to be read at the review rather than at the meeting.

One necessary caution. Directors' duties, the status and content of minutes and the composition and remit of board committees are governed by companies legislation and listing rules that differ materially between jurisdictions and between listed and private companies. Nothing here states what any code or statute requires, and nothing here is legal advice; the applicable law, the company's own constitution and its governance framework always govern. What follows is the general practice and, more usefully, the reasoning behind it.

Write the Minute First, Then Write the Paper That Makes It True

The most useful discipline available to anyone drafting a board paper is to write the minute before writing the paper. Not the wording the company secretary will actually adopt, but the substance: what will this minute need to record, and does the paper contain what is required to make each element of it accurate? A minute that says the board considered the proposal and approved it records almost nothing and protects nobody. A minute that records what was considered, what alternatives were examined, what the principal risks were understood to be, and what conditions were attached is a record — and every element of it has to be traceable to something that was actually in front of the board.

This inverts the drafting order in a productive way. Working back from the minute exposes immediately what a paper is missing, because each clause of the intended minute has to point at something. If the minute is to record that the board considered alternatives, the paper must set out alternatives — not a token pair of obviously inferior options, but the courses genuinely available, including the option of doing nothing, with the reasons each was or was not preferred. If the minute is to record that the board understood the principal risks, the paper must state them, and state them where they will be read rather than in a schedule at the back.

The option of doing nothing deserves particular emphasis because it is the alternative most often omitted and the one most often asked about later. Almost every proposal has a counterfactual in which the company does not proceed, and that counterfactual has consequences which are frequently not neutral — a position deteriorates, an opportunity closes, a competitor moves. Stating it plainly does two things: it makes the case for acting stronger where the case is genuine, and it puts on the record that the board weighed the alternative rather than accepting a false binary. A paper that presents a proposal against no alternative at all has, on its face, asked the board to approve rather than to decide.

Conditions are the other element that is regularly under-served. Boards frequently approve subject to something — a valuation confirming, a diligence item closing, a consent being obtained, a price not exceeding a limit. Where those conditions are set out in the paper, the minute can record them precisely and the delegation is clear. Where they are agreed in discussion and captured only in the minute, the scope of the delegation depends on the drafting of a sentence written afterwards, and disagreements about what was actually authorised are common and awkward. Where our advisers prepare material for a board decision, the conditions and the limits of the delegation are drafted into the paper so the minute can adopt them rather than construct them.

The Downside Belongs in the Paper, Written by the Person Recommending

Every proposal has a case in which it does not work. The question is not whether that case exists but whether it appears in the paper, and if so, in what form and written by whom. The weakest version is a risk register at the back listing generic exposures with generic mitigations, none of which is quantified and none of which would change the recommendation. That satisfies a formal requirement and informs nobody. The strongest version is a downside case in the body of the paper, quantified on the same basis as the recommended case, stating what happens to the company if it materialises — and stating explicitly whether, in that case, the recommendation would still stand.

The last element is the one that distinguishes a real downside case from a decorative one. A paper that presents a downside and then observes that the proposal remains attractive within it has not presented a downside; it has presented a mild variation of the base case. A genuine downside is one in which the recommendation would be different, and identifying it requires the author to think about the conditions under which they would themselves change their mind. That is uncomfortable to write and it is the single most valuable paragraph in most board papers, because it tells the board precisely what it is accepting.

Authorship matters more than boards sometimes recognise. A downside case written by the executive making the recommendation, in their own words, is worth considerably more than one supplied by someone else — because it demonstrates that the recommender considered it, and because it cannot be dismissed as the product of a reviewer who does not understand the business. Where the paper instead reads as though the risks were added by a different hand, an experienced director notices the change of register, and the natural inference is that the recommender did not want them there.

The quantification should share a basis with the recommended case so the two are comparable. A base case built on detailed operational modelling, set against a downside expressed as a general observation that conditions might deteriorate, offers no comparison at all. Applying the same model to a specified set of adverse assumptions produces two figures a board can weigh, and it makes the sensitivity of the conclusion visible: where a modest movement in one assumption reverses the recommendation, that fact is far more important than the base case itself. Where our financial due diligence team supports a board paper, the downside is modelled on the same basis as the recommendation for exactly that reason.

One reframing helps with the discomfort. A board that approves a proposal having seen a properly severe downside has made a decision that is defensible however it turns out, because the record shows the risk was known and accepted by the people with authority to accept it. A board that approves the same proposal on a paper showing only upside has made the same decision with none of that protection. The downside case does not weaken the recommendation; it is what makes the approval durable.

Directors Read for the Shape of the Argument Before They Read Its Content

Non-executive directors are structurally disadvantaged and know it. They see the business intermittently, through documents prepared by the people whose proposals they are assessing, without the operational knowledge to test most assertions directly. What they develop instead is a sensitivity to the shape of a document — the tells that indicate a paper has been constructed to produce a conclusion rather than to inform a decision. Those tells are largely independent of subject matter, which is precisely why they are relied on.

The commonest is asymmetry of treatment. Where the upside is modelled in detail and the downside is described in a sentence, where favourable assumptions are sourced and unfavourable ones are asserted, where the recommended course has three pages and the alternatives have a paragraph each — the paper has told the reader where its author's effort went, and effort follows intention. A director does not need to understand the underlying business to notice that the two halves of an argument were not prepared with the same care.

A second is the assumption that has quietly persisted. Papers on a recurring subject inherit their predecessors' assumptions, and an assumption that was reasonable when first adopted can survive for years past the conditions that justified it, carried forward because nobody re-derived it. A director who has been on the board long enough will remember the figure and ask when it was last tested — and the honest answer is frequently that it has not been since it was introduced. Stating the provenance and date of each load-bearing assumption pre-empts this entirely and costs a line.

A third is the conclusion that precedes the analysis. Where the recommendation is stated at the top and the material below reads as support for it rather than as the basis of it, a reader who is looking for it can generally tell — the analysis reaches only the conclusions it needs and stops. The tell is what is absent: the calculation that was not run, the comparison that was not made, the question a knowledgeable sceptic would have asked immediately. In the mandates our advisers run, a paper is read once by someone briefed to find what a hostile reader would notice, before it is circulated, because that reading is considerably cheaper in a draft than in a meeting.

A fourth is worth naming because it is so easy to fix: precision offered where the underlying basis does not support it. A figure carried to two decimal places on an estimate that was arrived at by judgement invites, and deserves, a question about the estimate. Rounding to the precision the basis actually supports, and saying what the basis was, is both more honest and more persuasive — and it removes an easy line of challenge that would otherwise consume time the board should be spending on the substance.

Length Is Not Thoroughness, and an Annexure Is Not a Disclosure

Board packs grow. Each addition is individually justified — a regulator asked about a topic, an incident prompted a new report, a director once requested a schedule and it became standing — and the aggregate is a pack nobody can read properly in the time available. The consequence is not that directors read less carefully; it is that they triage, and triage is a decision about what to skip made by each director separately, on the basis of what looks important. A material item that does not look important is precisely what gets skipped.

This is why materiality has to be exercised by the person preparing the paper rather than delegated to the reader. The test is not whether an item is interesting or whether someone might want it; it is whether it could change a director's view of the decision. What could is in the body. What could not, but supports something that could, is in an annexure with a specific reference from the body. What could not and supports nothing is not in the pack at all — and removing it is a service to the board rather than a withholding of information.

The corollary is important and frequently resisted: an annexure is not a disclosure. Material placed in a schedule at the back, unreferenced from the body, is available to the board in a formal sense and unread in a practical one. When a decision is reviewed later, the question asked is not whether the information was in the pack but whether the board was in a position to appreciate it, and a significant risk disclosed only on page ninety of an annexure invites an obvious and difficult question about why it was not in the paper. Burying is a recognisable pattern, and it is treated as such.

The reverse failure is real too and it deserves saying. A paper that omits material a director needs because the author judged it too detailed has substituted the author's judgement for the board's on a matter the board is responsible for. The discipline is not brevity; it is deliberate allocation, with the body carrying everything that could change a view and the annexures carrying the support for it, each referenced from the point in the body where it is relevant. Where our advisers work with a company secretary on a board pack, the allocation is made explicitly against that test rather than by inheritance from the previous pack, which is how most packs are actually assembled. Across a network of 80+ specialist consultants working in 22 countries, the inherited pack is the single most common structural problem our advisers encounter in a board pack.

Two structural habits help more than their simplicity suggests. Separating decision papers from information papers, so that a decision is never buried inside an update, means a director can allocate attention correctly at the point of triage. And a short cover page on each decision paper — what is being decided, what is recommended, what it depends on, what the principal risks are, what conditions attach — gives every director the same accurate frame before they read, which is the frame the discussion will then be conducted in.

An Audit or Risk Committee Reads for What Management Chose Not to Say

A committee charged with audit or risk oversight reads with a different orientation from the main board, and papers written without recognising that difference tend to satisfy neither. The main board is generally deciding something. The committee is generally assuring itself about something — that the numbers are what they appear to be, that judgements were made on a reasonable basis, that the control environment is functioning, that risks are being managed rather than merely listed. Its instinct is not to ask whether the proposal is good but to ask what would have to be true for the paper to be wrong.

The subject matter follows from that. Where a paper involves an estimate — a valuation, a provision, an impairment assessment, a revenue recognition judgement — the committee is interested in the range at least as much as in the point. A single figure presented without a range, without the sensitivity of that figure to its principal assumptions, and without an indication of where in the range management chose to sit, has withheld the information the committee exists to examine. Presenting the range, and saying plainly where within it the reported figure falls and why, converts a question into a disclosure.

Consistency across time is the second instinct, and it catches things nothing else catches. A committee sees the same estimates repeatedly and notices when a methodology changes, when a judgement moves in a direction that happens to be convenient, or when a figure that was described as prudent last year is described as realistic this year. None of those is improper on its own and each may have an excellent explanation, but the explanation should be in the paper rather than produced in the meeting. A change of basis disclosed by the author reads as diligence; the same change identified by a committee member reads as something else entirely, whatever the merits.

Committees also read for what is not there, and they are better at it than main boards because their agendas are narrower. The estimate whose assumption was not disclosed, the risk that was reported last quarter and has silently disappeared, the matter raised by internal audit that does not appear in the follow-up schedule — these are the characteristic findings. A paper that closes out a previously reported item should say so explicitly, including where the position was resolved rather than improved, because an item that simply stops appearing invites the least favourable interpretation available.

Where a committee is testing something material, the value of an independent view is that it is not the management view, and this bears directly on how such work should be instructed. An opinion commissioned by management and supplied to the committee answers the question with the management case built into its instruction. An opinion instructed by the committee, with the scope set by the committee, answers a question the committee asked. Where our valuation team is engaged by a board committee rather than by executive management, the distinction is set out in the engagement terms and stated in the report itself, because the value of the work depends on it being visible.

A Paper That Only Argues for Approval Is Itself the Governance Risk

The proposition worth stating directly is that a one-sided board paper is not merely a weaker document — it is a governance exposure in its own right, independent of whether the underlying decision was sound. The reason is that it deprives the board of the ability to demonstrate that it decided rather than ratified, and that ability is the substance of what a board is for. A board that receives only advocacy is being asked to approve, and a board that only ever approves has, in a structural sense, stopped being a board however capable its members are.

The exposure surfaces in a predictable pattern. A decision turns out badly for a reason that was foreseeable. Somebody — an auditor, a regulator, a litigant, an incoming board — reads the paper, and finds that the foreseeable reason was not mentioned. The question that follows is not whether the decision was reasonable at the time; it is whether the board was given what it needed to assess it. At that point the paper is the entire evidence, and a paper that presented only the case for approval answers the question against the board that received it, which is the wrong party to have exposed.

There is also a live cost, before anything goes wrong. A board that consistently receives advocacy learns to discount it, and directors begin to apply a general scepticism rather than a specific one — questioning proposals because the papers have taught them that papers are optimistic, rather than because this proposal warrants it. That is corrosive to good proposals, and it is a self-inflicted problem: the executive who over-argues a weak case has made the next strong case harder to get approved. The relationship between board and management is a repeated exchange, and its currency is whether papers can be taken at face value.

The remedy is neither elaborate nor slow. State the decision. Set out the alternatives that were genuinely available, including doing nothing. Identify the assumptions the recommendation depends on and say when each was last tested. Present a downside severe enough that the recommendation would change, and say so explicitly. Recommend, plainly, with the conditions attached. That structure is shorter than most current papers, not longer, because most of the length in a typical paper is argument rather than information — and argument is the part the board did not need.

The final observation is that this serves the executive as much as the board, which is why it is worth advocating rather than imposing. An approval given on a paper that showed the downside is an approval that survives the downside occurring. An approval given on a paper that showed only upside is an approval that will be revisited the moment the upside does not materialise, and revisited in an atmosphere where the executive is answering for what the paper did not say. Where our transaction advisory practice prepares material that will reach a board, the downside is drafted in for that reason: it protects the recommendation, and it is the only version of the document that is durable.

Write the Paper for the Review, and the Meeting Takes Care of Itself

The reorientation is the same one that runs through this whole series, in its governance form. The reader who determines whether a board paper did its job is not in the room. It is whoever reads the paper afterwards, looking for whether the board was in a position to decide — and that reader has only the document. A paper written for the meeting can be persuasive and still fail that test. A paper written for the review will generally also carry the meeting, because a board asked to decide rather than to approve tends to decide faster and with less residual anxiety.

The practical discipline is short enough to keep in mind while drafting. Write the minute first and make the paper support each clause of it. Set out the alternatives that genuinely existed, including doing nothing, and say what doing nothing costs. Name the load-bearing assumptions and date them. Model a downside on the same basis as the base case, severe enough to change the recommendation, and say explicitly that it would. Attach the conditions in the paper so the delegation is clear. Put in the body whatever could change a view and in the annexures whatever supports it, referenced from the point where it matters. None of that requires additional analysis; almost all of it is already known to the person writing.

These are observations about how papers are read rather than a template, and the applicable law, listing rules and the company's own governance framework always govern what a particular board requires. They are drawn from work delivered by a network of 80+ specialist consultants across 22 countries, which is the only reason they are offered as descriptions of a general practice rather than as one adviser's preference. A company secretary or an executive who applies them to their next paper, without instructing anybody, will produce a better record of a better-made decision — which is the entire object, and it is available at the cost of an afternoon's honesty about what could go wrong.