Board pack preparation is one of the most punishing recurring tasks in a finance function. The data arrives late, the narrative has to be rebuilt from scratch every quarter, and the same twelve slides somehow consume three full days of a controller’s time. Worse, the work is rarely a single linear task. It is a dozen small tasks stacked on top of each other: pulling actuals, reconciling variances, drafting commentary, building charts, checking consistency across sections, and rewriting everything once the CFO or CEO adds a last-minute request. The result is a process that is high-stakes, low-leverage, and almost impossible to delegate without losing quality.
Most of the friction is not analytical. It is editorial. The numbers are usually correct long before the deck is presentable. What eats the time is translating a trial balance and a set of management accounts into a clear, defensible narrative that a board can absorb in twenty minutes. That translation layer is exactly where ChatGPT performs well, provided it is given structure, context, and constraints rather than a vague instruction to “summarise the results.”
Used properly, ChatGPT becomes a drafting engine for the pack, not a replacement for judgement. It can convert raw variance tables into first-pass commentary, restructure a messy set of bullet points into board-ready prose, stress-test whether your messaging is consistent across sections, and generate the skeleton of a CFO script for the meeting itself. The key is treating it as a structured briefing exercise: feed it your files, your standards, and your audience, then demand a plan before it writes a single word.
Why a structured prompt beats a clever one
Finance professionals tend to under-specify prompts because they assume the model already knows what a board pack looks like. It does not know your board, your reporting conventions, or the tone your CEO expects. A structured prompt fixes this by separating the task, the reference material, the success criteria, and the constraints into explicit blocks. This mirrors how you would brief a new analyst: here are the files, here is last quarter’s pack, here is what good looks like, here is what to avoid.
The two prompts below follow that structure. The first covers variance commentary and narrative drafting from management accounts. The second covers the assembly and quality-check pass across a full pack. Both are designed to be pasted into ChatGPT with your own files attached.
First, read these files completely before responding:
[management_accounts_[month].xlsx] — actuals, budget, prior year, and variance columns by cost centre
[prior_quarter_board_commentary.md] — last quarter’s approved commentary, used as the tone and structure reference
[board_pack_style_guide.md] — formatting rules, terminology, and prohibited phrasing
Here is a reference for what I want to achieve:
[Upload prior_quarter_board_commentary.md as markdown, or paste two or three approved sections]
Here’s what makes this reference work:
– Opens with the headline number and direction, not with process
– Explains variance drivers in order of financial materiality, not organisational hierarchy
– Distinguishes clearly between timing, permanent, and one-off items
– Uses plain declarative sentences, no hedging, no filler adjectives
– Every claim is traceable to a line in the accounts
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: Board commentary, 600 to 900 words, split by P&L line and cost centre
Recipient’s reaction: The board should understand what moved, why, and what management is doing about it, without asking clarifying questions
Does NOT sound like: A management report, an audit note, or a press release
Success means: The CFO approves with fewer than five tracked changes and no rewrites
My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.
Give me your execution plan (5 steps max) before you begin.
Notice what the first prompt does not ask for. It does not ask for a summary of the accounts. It asks for commentary that survives CFO review, which is a different and much harder target. Specifying the acceptable number of tracked changes is the single most useful constraint you can give a model in this workflow, because it forces it to prioritise clarity over completeness.
The assembly and consistency pass
Once the individual sections are drafted, the second failure point appears: inconsistency. The CFO’s summary says margin improved, slide nine says it was flat, and the appendix uses a different definition of adjusted EBITDA than the main body. This is where a second prompt earns its place, treating ChatGPT as a reviewer rather than a writer.
First, read these files completely before responding:
[draft_board_pack_[quarter].md] — full draft pack, all sections in order
[definitions_and_metrics.md] — approved definitions for all non-statutory metrics
[prior_quarter_board_pack.md] — last quarter’s final pack, for structural comparison
Here is a reference for what I want to achieve:
[Upload prior_quarter_board_pack.md as markdown, or describe the standard structure]
Here’s what makes this reference work:
– Every metric used in the narrative appears in the definitions file with identical wording
– Section headings and ordering match the prior pack unless a change was explicitly approved
– Numbers quoted in commentary reconcile exactly to the tables they reference
– Forward-looking statements are labelled as such and attributed to management
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: A findings list, maximum 400 words, grouped by severity
Recipient’s reaction: The controller should be able to action every finding in under an hour
Does NOT sound like: A general critique or a style opinion piece
Success means: Zero numerical inconsistencies and zero undefined metrics remain in the final pack
My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.
Give me your execution plan (5 steps max) before you begin.
Run this second pass after every section is drafted but before anything is formatted into slides. Catching a definitional inconsistency in markdown takes seconds; catching it after the deck is built and circulated to the executive team costs a day. Treat the findings list as a checklist, resolve each item, then move to design.
A practical tip: keep a running context file for your board reporting cycle. It should contain your reporting calendar, the board’s composition and known areas of interest, your approved metric definitions, and the tone rules your CFO has enforced over time. Attach it to every prompt in the cycle. The model’s output quality tracks almost linearly with how well that file is maintained.
The next thing to try is the CFO script. Once the pack is final, feed the approved commentary back in and ask for a ten-minute verbal walkthrough with anticipated board questions and suggested responses. It is the same structured briefing approach applied to the meeting itself, and it is usually the fastest win available after the pack is signed off.
Published on 3 October 2026 on growwithgpt.com