BoardMemo
Free reference

How to write a board paper (or board memo) that gets a decision

A board paper has one job: to get a decision, or an informed view, from people who do not run the business and have a few hours to read the whole pack. This guide sets out the structure the governance bodies recommend, how long each section should be, how to frame the ask, and what boards complain about most, with a checklist and a worked example.

Board paper structure at a glance

The bodies that publish board paper templates, the Chartered Governance Institute UK & Ireland (CGI), the Governance Institute of Australia (GIA), the Australian Institute of Company Directors (AICD) and the Institute of Directors in Ireland (IoD Ireland), converge on almost the same spine. They differ on lengths, so the right-hand column gives the range their templates set, or my own working figure where they say nothing.

SectionWhat it is forTypical length
Header blockAgenda item, paper type, sponsor, author, date. Tells the director what this is and who owns it.A few lines
Proposed resolutionThe exact words the board is asked to adopt, written to stand alone in the minutes.As short as precision allows
Purpose and contextWhy this is at the board, why now, and what the board must do.Five to ten lines at most (GIA)
Executive summaryKey messages, the questions the paper answers with their answers, the recommendation and the ask.Four to five lines (IoD Ireland, AICD) up to one page (CGI)
BackgroundWhat the board has seen before and needs to know to follow the argument.About 12 lines (IoD Ireland) to one page (AICD)
Options consideredThe realistic alternatives, including doing nothing, compared on the same criteria.Half a page, or one table
RecommendationThe preferred option, the reasons, the outcomes it should deliver.12 lines (IoD Ireland) to one page (AICD)
Strategic alignmentWhich agreed objective the proposal serves, and how.10 lines (IoD Ireland) to half a page (AICD)
Financial implicationsCost, timing, cash flow, budgeted or not, and the assumptions behind the number.12 lines (IoD Ireland) to half a page (AICD); detail in an appendix
Risks and mitigationsPrincipal risks of the proposal and of not doing it, with treatment and owner.12 lines (IoD Ireland) to half a page (AICD); best as a table
Governance, compliance, stakeholdersLegal and regulatory implications, effect on the people involved, and how the board will be kept informed.About 12 lines (IoD Ireland)
Accountability and next stepsWho delivers, who oversees, what happens after the decision and by when.A few lines
AppendicesEvidence for directors who want to test the argument. Never a repeat of the body.Only what the argument needs
The whole paperOne subject, one ask.GIA suggests a limit of two, three or four pages for routine papers, with exemptions for major capital spend, acquisitions, strategy and financial reporting

The first-page test. A director who reads only page one should know what you are asking for, what you recommend and why. The GIA's sample paper says so in terms: purpose, recommendation and executive summary belong on the first page. If a paper fails that test, no polish further down will save it.

What a board paper is for, and how it differs from a management report

Board papers are the main channel through which directors get what they need to take decisions and to oversee management. That makes a board paper a governance instrument, not a status report. In the UK, the Corporate Governance Code makes the chair responsible for ensuring directors receive accurate, timely and clear information, and the Financial Reporting Council's guidance on the Code says board papers should be accurate, clear, comprehensive and up to date, contain a summary, tell each director what is expected of them, and arrive far enough ahead of the meeting to be read properly. Those four tests are a fair definition of a good paper in any jurisdiction.

I spent eight years as a CTO and five as a Chief Commercial Officer writing papers for boards, and have read many more in executive committees and steering groups since. A handful of habits separates the papers that get decided from the ones that get deferred.

Board paper, board memo, cover paper: one instrument

UK and Australian organisations mostly say board paper; many companies say board memo, often for shorter notes, including those sent between meetings; public bodies talk about cover papers or submissions. The discipline does not change with the name: one subject, one clear ask, written for people who are not in the business every day.

Who you are writing for

Directors set direction and hold management to account. They are not there to run the operation. Non-executives may attend only a handful of meetings a year, often sit on other boards with their own vocabulary, and arrive with limited knowledge of your subject. The GIA names the commonest failure precisely: papers written for management rather than for the board, which hand directors too much detail and too little of the information a decision actually needs.

In my experience the giveaway is a paper that answers the questions the author finds interesting. A CTO wants to explain the architecture. The board wants to know what it costs, what it buys, what could go wrong and what happens if it says no. Write for the second set of questions, and put the first in an appendix if it belongs anywhere at all.

Write as if a regulator will read it

Board papers are part of the organisation's record, and the GIA reminds authors that regulators and courts may examine them later. Hence the advice to write in a formal, factual style, with fact and opinion clearly distinguished. That is not a licence to be bland. It is a reason to be precise: say what you know, what you believe and why, and what you do not yet know.

The ask: for decision, approval, noting or discussion

State the paper type at the top, before any argument, and make the purpose line match it. The bodies use slightly different labels. The AICD sample offers for decision, for discussion and for noting; IoD Ireland's template asks whether the paper is for decision, approval or information; the GIA adds for recommendation (used when a committee is advising the board) and for ratification. The CGI puts it most plainly: the paper must say whether the board is to note the information, approve or decide, or give input.

Paper typeWhat the board doesWhat the paper must containWhat the minutes record
For decision or approvalAdopts the proposed resolution, amends it, defers it or rejects itThe exact resolution, the options considered, the recommendation, cost, risks and who will actThe resolution as passed
For discussion or inputGives a view that shapes work not yet ready for decisionThe specific questions you want answered, the options as they stand, and when it will come backThe board's guidance and any follow-up
For noting or informationAcknowledges that it has received and understood the informationWhy the board needs to know, what has changed since it last saw the subject, and what would trigger a decisionThat the paper was noted
For ratificationConfirms an action already taken under urgent or delegated authorityWhat was done, under which authority, and why it could not wait for a meetingThe ratification

Write the resolution you want minuted

Where you want a decision, give the exact wording of the proposed resolution. If the board passes it unamended, that is what goes into the minutes, so it must make sense without the paper beside it. Be precise about amount, scope and authority, and where someone has to act, include the delegation: who may sign, and up to what limit. The GIA recommends both, with the company secretary checking every proposed resolution. The AICD's test is a good one: write it so the board can approve it without amendment.

Example resolution. That the Board (a) approves capital expenditure of up to €4.2 million to replace the warehouse management system, as set out in paper 7; and (b) authorises the Chief Operating Officer to sign the supplier contract and statement of work within that limit.

Stop hiding decisions behind "for noting"

For noting is the most abused label in the pack. Sometimes the paper needs no action at all and is there because it always has been; ask whether a dashboard or a reading-room section would do. Worse is a real decision dressed as an update so that it slides through. Among the factors the FRC's guidance lists as distorting board decisions is a tendency to bring matters to the board for sign-off rather than for debate. If you want the board's view, label the paper for discussion and write down the questions you want answered. The CGI suggests a section headed something like "Input sought" or "Questions to the reader" for exactly this purpose.

The one-page executive summary

If the board reads one section properly, it is this one. The CGI's 2026 guidance on board reporting gives the clearest recipe I know, and it works best followed in order:

  1. Why it matters. Tie the paper to something the board already cares about: the strategy, a target, a known risk.
  2. Why now. Is there a trigger (a deadline, a failure, an offer that expires), or is this a scheduled item?
  3. The questions the paper answers. Three to five of them, with no overlap and nothing important missing.
  4. The answer under each question. Directly beneath it, in a sentence or two. A board paper is not a detective story.
  5. What the board must do. Note, decide, approve or give input, matching the label at the top.

The CGI's ceiling is one page. Other templates are tighter: the AICD sample allows a paragraph of four or five lines, IoD Ireland no more than four lines, the GIA two or three paragraphs. The short versions are really a purpose statement; the CGI's is a summary of the argument. Use both: a few lines that state the ask, then no more than a page that carries the reasoning. Whatever else you cut, never cut the first.

Answer first

Compare two openings for the same paper.

  • Weak: This paper provides background on the warehouse management system and summarises the work the project team has done since March.
  • Strong: We ask the Board to approve up to €4.2 million to replace the warehouse management system. Vendor support for the current system ends in 21 months, and outages on it disrupted dispatch on 11 days last year.

The first tells the director what the paper is about. The second tells them what to do and why, and every later section can be read as evidence for or against it.

Headings that ask the board's questions

The CGI makes a point I wish I had learned earlier: generic headings such as Background and Recommendations can be filled with anything, while headings phrased as the board's questions (what do we propose to do and why? what happens if we do nothing? what could go wrong?) force the author to answer them. They also let a director spot a missing question at a glance. Write the summary last, once the body has settled, and read it first when you review.

Recommended board paper structure, section by section

A template for a decision paper, assembled from the published templates and trimmed by experience; update papers are covered at the end. Mark a section that does not apply as not applicable rather than deleting it, so the reader knows you considered it.

1. Header block

Organisation, forum (the board, or which committee), meeting date, agenda item number, a title that matches the agenda, the paper type, the executive sponsor, the author and the date the paper was finalised. The date matters more than it looks: it tells directors how current the numbers are.

2. Proposed resolution, purpose and context

The exact wording of the resolution (or a statement that the paper is for noting or discussion), then what the paper is for and why it is at the board at all: a legal or charter requirement, a matter reserved to the board, prior consideration by a committee. The GIA caps the purpose at five to ten lines.

3. Executive summary

The key messages, the questions and answers, the recommendation and the ask, in no more than a page.

4. Background

Only what a non-executive needs to follow the argument, plus a reference to any previous board paper on the subject with its date. Name any external advice that informed the paper; the AICD and IoD Ireland both ask for this. If it runs past a page, summarise here and move the rest to an appendix.

5. Options and recommendation

The realistic alternatives compared on the same criteria, then the preferred option, the reasons and the outcomes it should deliver. The AICD sample asks that the recommendation explain why the board should accept it without repeating earlier sections. Both are covered in depth below.

6. Strategic alignment

How the proposal serves the agreed strategy or business plan. A sentence saying it "supports our strategy" without naming the objective is filler.

7. Financial implications and risks

Cost, timing, cash flow, budget status and the assumptions behind the numbers; then the principal risks of the proposal, and of not doing it, each with its treatment and owner. The business case goes in an appendix.

8. Governance, compliance and stakeholders

Legal and regulatory implications, the effect on employees, customers, suppliers and communities where it is material, and how the board will be kept informed during and after implementation. The AICD sample adds environmental, social and economic impact for proposals where those matter.

9. Accountability and next steps

The executive accountable for delivery, any director with oversight, what happens after the board decides, who does it and by when.

10. Sign-off and appendices

The AICD and IoD Ireland templates both close with sign-off by the chief executive and the sponsor and a list of contributors, so the board knows who stands behind the paper. Appendices hold evidence for directors who want to test the argument, not material you would rather not discuss. The GIA is explicit that an attachment is still part of the paper and directors are expected to read it, so moving bulk to the back does not make the paper shorter.

When the paper is an update rather than a decision

A progress report needs a different shape: the purpose, a one-sentence headline on whether things are on track, progress against the plan with numbers, risks and issues, the outlook, and any support needed from the board. If an update uncovers a decision, take the decision out into its own paper rather than burying it on page three.

One paper, several forums

If the same material goes to a committee and then to the board, the CGI suggests a paper whose front section stands alone for the board and whose back section can be detached for committee use. It beats maintaining several versions of one paper.

The free memo builder on this site uses compressed versions of these spines: its Decision brief runs Purpose, Background, Options Considered, Recommendation, Risks and Mitigations, The Ask, and its Board update runs Purpose, Headline, Progress, Risks and Issues, Outlook, Support Needed. Because The Ask closes the Decision brief, put a one-line version of it in the Purpose as well, so the first lines carry it.

Options and a recommendation the board can test

A paper that offers one course of action asks the board to approve rather than to decide, and directors notice. In a 2026 AICD article on reading board packs, an experienced director named two warning signs: a problem presented with no options for solving it, and a paper that only lets the board say yes or veto. The GIA asks for the advantages, disadvantages and material risks, financial and non-financial, of each alternative, and for the judgements behind the recommendation. The FRC's guidance suggests that papers on significant decisions describe how the proposal was developed and challenged before it reached the board.

Three real options, one of them doing nothing

My rule is three genuine options, one of which is to do nothing or defer, each judged on the same four or five criteria: cost, time, benefit, risk and fit with strategy. A straw man is worse than no option at all, because a board that spots one stops trusting the others. If there truly is only one credible route, say so, and say why the alternatives fell away.

OptionOne-off costTime to go-liveMain riskAssessment
A. Defer: two years of premium extended support, then replace€0.9m, then the replacement cost on topNone nowOutages continue; vendor may still withdrawBuys time at a price; solves nothing
B. Replace with a cloud system (recommended)€4.2m14 monthsCut-over disrupting dispatchLive with a seven-month margin; covers all required functions
C. Extend the ERP's own warehouse module€3.1m20 monthsNo cross-docking support; almost no marginCheaper, but too slow and a weaker fit

The figures are illustrative; they belong to the worked example at the end of this page.

What a good recommendation contains

  • Which option, in the first sentence.
  • The two or three reasons that carried it, tied to the criteria.
  • What you would have to believe for it to be wrong, and what would change your mind.
  • How confident you are, and where that confidence comes from. The CGI asks authors to show this explicitly.
  • The key judgements you made, kept visibly separate from the facts.

The third point is the one that earns trust. A board that can see the load-bearing assumption can test it in two minutes instead of circling it for twenty.

Risks and financials: the sections boards read twice

Risks

The risk section is about this proposal, not a copy of the corporate risk register. The GIA, the AICD and IoD Ireland all suggest a simple table: the risk, its likelihood, its impact and how it will be managed. The AICD version records the risk level before and after treatment, which is worth doing for anything material, because it shows what the mitigation actually buys.

RiskLikelihoodImpactMitigationOwner
Cut-over disrupts dispatchMediumHighGo-live outside peak season; two-week parallel runCOO
Carrier integration slipsMediumMediumCarrier interfaces built and tested in phase one; fixed-price clauseCIO
Benefits not realisedLowHighBaseline measures agreed now; post-implementation review to the board at 12 monthsCFO

Two habits make this section credible. Include the risk of not acting, often the largest. And give bad news its proper weight: the CGI warns against the temptation to hide it, and directors who find it later will reread everything else with suspicion.

Financials

Keep the body short and the numbers complete. State the cost, the timing of spend, the cash-flow effect and whether it is in the budget; IoD Ireland and the AICD both ask for the budgeted-or-unbudgeted question to be answered explicitly for significant spend. The GIA adds key assumptions and sensitivity analysis where the subject calls for them. Put the full business case in an appendix and summarise it in a few lines.

My test for a financial section: one number, one range, and the assumption that moves it most. "€4.2 million, between €3.9 and €4.8 million depending mainly on data migration effort" tells the board exactly where to probe. Then check that the figure is identical in the summary, the body and the appendix. Numbers that do not stack up are among the first things experienced directors look for, and a single inconsistency costs the whole paper its credibility.

What boards complain about, and the fix

The CGI and Board Intelligence have researched board reporting since 2018, gathering data from 1,857 individuals and 1,676 organisations. Their 2026 report makes uncomfortable reading for anyone who writes papers: 63% of respondents are not confident the pack has been fully read and digested, and 42% say the materials actively limit board effectiveness. The FRC, for its part, lists poor quality papers, inadequate information or analysis, and insufficient notice among the factors that lead boards to poor decisions. The complaints are remarkably consistent.

ComplaintWhat the evidence saysThe fix
Too longThe average pack ran to 220 pages in 2025, up 27% since 2019. The CGI reckons that takes 7 to 20 hours to read properly; directors reportedly spend about four.Page limits for routine papers, the first-page test, and appendices that do not repeat the body.
The point is buried54% say the key messages are buried; 47% say packs are light on the implications of what they report (CGI).Answer first. Say what the information means, not only what it is.
No clear askExperienced directors treat it as a red flag (AICD). The FRC's guidance says papers should tell directors what is expected of them.Paper type at the top, a purpose line, and the exact resolution.
No optionsA problem with no options, or a yes-or-veto choice, worries directors (AICD).Three real options, one of them doing nothing.
Too operational60% of organisations say their papers are too operational at the expense of strategy (CGI).Template headings that start with the decision, not the background.
Jargon and acronymsPlain English, few acronyms and a glossary where needed (GIA); directors may sit on several boards, each with its own jargon (CGI).Write for a director who has never worked in your function.
Opinion without evidenceUnsubstantiated claims send directors digging into things that should have been settled (AICD).Link each claim to data or a source, and separate fact from judgement.
Late papersOnly 48% of organisations always get papers five working days ahead; 17% rarely or never do (CGI).Work back from the distribution date, and make a late paper an exception the chair agrees to.

On timing, the guidance agrees. The GIA describes distribution about a week before the meeting as common practice; the CGI says no less than five working days ahead, except in exceptional circumstances. Documents tabled on the day should be rare, and the GIA adds that directors must have the chance to read one, even if the meeting adjourns so they can.

One more complaint, from the writer's side of the table: the paper that has been through five reviewers and kept everyone's paragraph. Every reviewer adds; nobody cuts. Make one person, usually the sponsor, responsible for removing material.

Board paper checklist

Run this before the paper goes to the company secretary. It draws on the CGI's checklist and the published templates, reorganised the way I use it.

The ask

  • The paper type (decision, discussion, noting, ratification) is at the top and matches the purpose line.
  • For a decision, the exact resolution is stated, stands alone, and includes any delegation of authority.
  • For a discussion, the questions you want the board to answer are written down.
  • It is clear why this is coming to the board, and why now.

The argument

  • The executive summary gives the answers up front, in no more than a page.
  • Headings signpost the argument, ideally as the questions the paper answers.
  • Where a decision is sought, the options, benefits, risks and costs of each are set out, including doing nothing.
  • The recommendation names the option in its first sentence and shows the key judgements.
  • It says what the information means, and is candid about bad news.

The numbers and risks

  • Cost, timing, cash flow and budget status are stated, with a range and its main driver.
  • Every figure matches across summary, body and appendices.
  • Risks are specific to the proposal, include the risk of not acting, and each has an owner.

The reader

  • It is pitched at board level, strategic rather than operational.
  • Jargon and acronyms are removed or explained.
  • Charts and tables carry a sentence saying what they show.
  • Page one alone tells a director what is asked, what is recommended and why.

The process

  • The sponsor has read it and is prepared to stand behind every sentence.
  • You left it for a day and reread it cold; IoD New Zealand's tips make the same point.
  • It reaches the company secretary in time for the pack to go out at least five working days before the meeting.

If you drafted it with AI

The CGI's 2026 report devotes a chapter to this. AI is already used in board reporting, acknowledged or not, and it helps with first drafts, summaries and spotting gaps. But it changes how a paper is produced, not who is accountable for it: the executive who presents the paper owns its content. The report's principles are worth adopting as they stand: a human reviews every AI output before it reaches the board, AI use is disclosed, and confidential material goes only into tools whose data handling meets the organisation's standards, including whether it trains a model. Board papers carry some of the most sensitive information an organisation holds, so where the drafting happens matters.

A worked example: a short decision paper

A condensed decision paper for a fictional distribution company. The figures are illustrative. In practice the options, financials and risks would each have their own short section and an appendix; here the whole argument fits on about a page.

Northwind Distribution. Board meeting, agenda item 7. Replacement of the warehouse management system. For decision. Sponsor: Chief Operating Officer. Author: Head of Logistics Systems. Paper finalised two weeks before the meeting.

Proposed resolution. That the Board approves capital expenditure of up to €4.2 million to replace the warehouse management system and authorises the Chief Operating Officer to sign the supplier contract within that limit.

Purpose. To seek approval to replace the warehouse management system before vendor support for the current system ends in 21 months. The spend is in the approved capital plan.

Summary. Why now? Support ends in 21 months and replacement takes 14, so the decision is needed this quarter to leave a safe margin. What are the options? Defer with premium extended support (€0.9m, solves nothing), extend the ERP's warehouse module (€3.1m, 20 months, no cross-docking), or replace with a cloud system (€4.2m, 14 months). What do we recommend? Replacement: it is the only option live with a margin before support ends, and the only one covering every function we use. What does it buy? An end to the outages that disrupted dispatch on 11 days last year, and no hardware refresh next year. What could go wrong? Cut-over disrupting dispatch, managed by going live outside peak season with a two-week parallel run.

Financials. €4.2m one-off, within a range of €3.9m to €4.8m depending mainly on data migration effort. Subscriptions of €0.35m a year, against €0.4m a year of current support and hosting costs that fall away. Business case in appendix A.

Key risks. Cut-over (medium likelihood, high impact; off-peak go-live and parallel run; COO). Carrier integration slipping (medium, medium; interfaces tested in phase one, fixed-price clause; CIO). Benefits not realised (low, high; baseline measures agreed now, review at 12 months; CFO).

Next steps. Contract signed within a month of approval; a progress line in each board update; a post-implementation review to the Board 12 months after go-live.

Why it works

  • The ask, the amount and the authority sit in the first three lines.
  • The summary is written as the board's questions, each answered directly beneath.
  • Doing nothing for now is a priced option, so the board can see the cost of delay.
  • The money has a range and a named driver, and every risk has an owner.
  • The board knows when it will hear about this again, and what it will be shown.

What it leaves out is just as deliberate: the vendor selection, the architecture and the project plan belong in appendices, or in the committee version of the paper.

Practise it, not just read it

The free memo builder gives you the same six templates and four audiences as the BoardMemo app. You write each section yourself, and a board-tone check flags hedging, vague numbers and buried points as you type. Nothing you type leaves the browser.

If you are starting from rough notes, the iPhone app does the writing: paste or dictate them and it drafts the memo in that structure, on the device. Where the notes are ambiguous it writes an explicit [TO CONFIRM: …] marker instead of a confident guess, and one tap will tighten the memo, make it more formal, sharpen the risks or halve its length. It needs an iPhone 15 Pro or newer on iOS 26 with Apple Intelligence enabled.

Try the free memo builder Download on the App Store Free · runs in your browser · On the App Store on iPhone

Common questions

How long should a board paper be?

There is no universal limit, and the FRC's guidance sets none. The Governance Institute of Australia suggests a page limit of two, three or four pages can help for routine papers, with exemptions for large capital projects, acquisitions, strategy and financial reporting. The CGI recommends an executive summary of no more than one page. In practice: the shortest paper that lets the board decide, with evidence in appendices that do not repeat the body.

What is the difference between a board paper and a board memo?

In substance, none. Board paper is the usual term in the UK and Australia; board memo is common in many companies and is often used for shorter notes, including those sent between meetings. Both should cover one subject, carry one clear ask, and give the board the information it needs to act on it.

What does "for noting" mean on a board paper?

It means the board is asked to acknowledge that it has received and understood the information, not to take a decision. No resolution is proposed, and the minutes simply record that the paper was noted. If the board needs to decide or to give a view, label the paper for decision or for discussion instead.

What should the executive summary of a board paper include?

Following the Chartered Governance Institute UK & Ireland's 2026 guidance: why the paper matters, why it is coming to the board now, the three to five questions it answers with the answer directly under each, and what the board is asked to do. Ideally no more than one page, and on the first page together with the purpose and the proposed resolution.

How far in advance should board papers be sent?

The CGI says papers should usually go out no less than five working days before the meeting, except in exceptional circumstances, and the Governance Institute of Australia describes about a week as common practice. The FRC's guidance asks for papers to be delivered sufficiently in advance of the meeting. Late and tabled papers should be the exception, clearly flagged, with time allowed to read them.

Who writes board papers?

Usually management: the author is the person closest to the subject, and an executive sponsor owns the content. The company secretary sets the timetable, checks proposed resolutions and compiles the pack. Directors share the responsibility by saying what they need and giving feedback when papers fall short.

About the author

Magnus Oxenwaldt is VP Group AI at Columbus Global. Two decades in enterprise architecture — ERP, integration, customer engagement, and now AI. He hosts the Future Bytes podcast, speaks at executive forums and board off-sites, and writes at oxenwaldt.com.