Executive Board Pack Preparation

Board and committee pack preparation

Purpose

A board paper has one job: allow a group of people with limited time and no operational context to take a decision they can defend later. Most papers do the opposite — they narrate the work, bury the ask on page nine, present one option dressed as an analysis, and list generic risks nobody will act on. This skill fixes the order, forces genuine alternatives, and separates what the decision needs from what merely evidences it.

Prerequisites

• Inputs: the decision actually being sought and who has the authority to take it; the options genuinely available; the figures behind them, sourced and already through data-analytics-report-qa; the current risk position; the terms of reference or delegated authority of the forum.
• Access: the previous pack and the minutes of the last meeting, so the paper can state what changed and close out prior actions.
• Timing: the papers deadline and the reading expectation. A paper tabled at the meeting is a paper that was not read.

If the decision is not yet defined, stop and define it. A paper "for discussion" with no proposition consumes the scarcest governance time there is and produces no minute.

Data classification and stop condition

Board material is Confidential by default, and frequently price-sensitive, legally privileged, or subject to regulatory notification. Handle accordingly:

• State the classification and the distribution list on the front page.
• Where a paper covers litigation or regulatory engagement, mark it and route through legal before circulation — privilege can be lost by distribution.
• Report individuals by role, not by name, unless the paper is expressly about a named appointment or a matter requiring it.
• Aggregate client and personal data. A board decision practically never requires row-level personal data, and a pack is the most widely forwarded document an organisation produces.

Stop condition: if personal data, account numbers, client identities or individual trading positions are supplied for inclusion, flag it and stop. Ask for an aggregated extract before continuing.

Non-fabrication rule — absolute. Never invent, interpolate, round-to-plausible or carry-forward a figure into a board paper. Every number is sourced and dated. If a number is not available, the paper says "not available", says why, and says when it will be. If a number is an estimate, it is labelled as an estimate with its basis and its range. A fabricated board figure is a governance failure, and it is minuted with your name on it. When the data does not support the paper, that is the finding — report it rather than filling the gap.

Required order

The order is the substance. It is not negotiable, and it is the reverse of how the work was done.

Procedure

1. Write the decision request first and confirm the forum can actually take it. Check the terms of reference and delegated authority: a paper asking for a decision outside a forum's authority wastes the meeting and creates an invalid minute.
2. State the recommendation immediately after the request. Directors read the first page; a recommendation revealed at the end has already been pre-empted by whatever they concluded on the way there.
3. Build the options honestly. Each option needs a real advocate case, a cost, and a stated reason for rejection. Include the do-nothing option with its actual consequence. Straw-man options are the most common defect in board papers and the most damaging: they convert governance into ratification, and a director who spots one distrusts the whole paper.
4. Source every figure to a named system, report or document, with an as-of date, and run it through data-analytics-report-qa before it enters the pack. Where the same metric appears elsewhere in the pack, reconcile it — two numbers for one thing in one pack is the finding directors remember.
5. Write risks that are risks. A risk is specific, has an owner, has a probability and impact, has a mitigation with a date, and has a residual position after mitigation. "Execution risk" and "market conditions" are not risks; they are placeholders. Include the risks of the recommendation, not only of the alternatives — a paper whose recommended option carries no stated risk is not credible.
6. State legal and regulatory implications by regime, parameterised to the jurisdictions the organisation actually operates in, with the status of each obligation: met, in progress with a date, or requiring a decision. Where an obligation is uncertain, say so and name who is confirming it.
7. Apply the main-body / appendix split. The body contains only what is needed to take the decision; everything else is appendix, referenced by number. Test each body page: remove it — can the decision still be taken? If yes, it is appendix. The appendix carries the detail a challenging director will ask for; it is not a dumping ground, and it is indexed.
8. Length discipline. The body should be readable in the time the forum will actually give it. If the body exceeds that, cut to appendix, not to the ask.
9. Write what changed since this forum last saw the matter, including anything that has moved against the position previously reported. A paper that repeats a previous position without acknowledging deterioration will be caught, and it destroys the credibility of every other paper from the same source.
10. Close out prior actions with status, owner and date. Actions that quietly lapse train the forum to stop assigning them.
11. Pre-read the objections. List the three questions the toughest director will ask, and make sure the paper answers them — in the body if they bear on the decision, in the appendix if they bear on the evidence.
12. Circulate against the papers deadline, with classification and distribution list on the front page, and version control on the document.

Failure modes

• Ask buried. The decision appears after the narrative and the forum arrives at it already committed to its own reading.
• Single option presented as analysis. Removes the forum's ability to govern.
• Generic risks. Unactionable, and they signal that the real risks were not examined.
• Unsourced or inconsistent figures. One reconciliation failure discredits the paper.
• Everything in the body. A long body is read partially and unpredictably; the parts skipped are chosen by the reader, not by you.
• No stated deterioration. The gap between the paper and the reality is discovered by the forum rather than disclosed by management.
• Decision outside the forum's authority, producing a minute that does not hold.

Boundaries

• A recurring project or programme update with no decision attached — use operations-project-status-report.
• Producing the slides from finished material — use cross-functional-deck-assembly; this skill owns the content and the ordering, that one owns the assembly.
• Drafting the policy or standard the board is being asked to approve — use legal-compliance-policy-drafting, then attach it as the appendix.
• Assessing the impact of a regulatory change that will be tabled — use legal-compliance-regulatory-change-impact to produce the analysis first.
• Selecting a supplier the board is asked to approve — the evaluation belongs to operations-vendor-evaluation; the paper presents its conclusion.

Hand-offs

• Receives from: operations-project-status-report (delivery position and escalated decisions), finance-month-end-variance-analysis and data-analytics-report-qa (verified figures), legal-compliance-regulatory-change-impact (obligations and deadlines), operations-vendor-evaluation (a recommended supplier and its rationale), engineering-decision-record (a technical decision needing governance sign-off).
• Routes to: cross-functional-deck-assembly where the paper must also be presented, legal-compliance-policy-drafting where the decision creates a policy obligation, and operations-sop-authoring where an approved decision becomes a recurring control.