Board pack preparation is one of the most punishing recurring tasks in a finance function. The data arrives late, fragmented across ERP extracts, management accounts, KPI trackers, and prior-quarter commentary. Someone has to reconcile the numbers, draft the narrative, build the deck, and then rebuild half of it after the pre-read review. The work is high-stakes and low-tolerance for error, yet it is usually compressed into a three-to-five day window at the end of an already full reporting cycle.
The friction is not analytical. Most finance teams know exactly what the board needs to see. The friction is assembly: converting raw outputs into a structured story, keeping commentary consistent with the numbers, and doing it again next quarter without reinventing the format. Version control alone consumes hours. A single late adjustment to the cash flow statement can invalidate six slides of narrative.
ChatGPT does not replace the judgment in a board pack. What it does well is the translation layer: taking your data files and your house standards, and producing a first draft of the structure, the commentary, and the variance explanations in a consistent voice. Used with disciplined prompting, it compresses the assembly phase from days to hours and leaves your team free for the analysis that actually warrants their attention.
The discipline that makes the difference
The difference between a useful ChatGPT output and a generic one is context. A prompt that says “write board commentary on these results” produces something a competent analyst would discard. A prompt that supplies the prior board pack as a reference, states the audience’s expected reaction, and defines what the output must not sound like produces a draft that is genuinely close to final.
The two prompts below follow that pattern. The first builds the analytical foundation: variance analysis and the narrative spine. The second converts that into the deck structure and slide-level commentary. Run them in sequence, in the same conversation, so the second builds on the first.
First, read these files completely before responding:
[current_quarter_management_accounts.xlsx] — P&L, balance sheet, cash flow, actual vs budget vs prior year, by cost centre
[prior_board_pack.md] — last quarter’s full board pack, including commentary and appendix
[kpi_tracker.xlsx] — monthly operational KPIs with definitions and targets
Here is a reference for what I want to achieve:
The prior board pack in markdown. Study the variance commentary on pages 4 to 11 in particular.
Here’s what makes this reference work:
Variances are stated in absolute and percentage terms before any explanation. Every explanation names a driver, not a category. Commentary avoids adjectives and never uses the word “challenging.” Each section ends with a forward-looking sentence. Numbers in commentary always tie to the tables.
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: Variance analysis table plus narrative commentary, approximately 900 to 1,200 words, structured by P&L line then balance sheet then cash.
Recipient’s reaction: The CFO should read it and think “I can take this into the pre-read with light edits,” not “I need to rewrite this.”
Does NOT sound like: A management commentary written for the board. No hedging language, no restating the obvious, no explanation that simply names the budget line that moved.
Success means: Every variance above [materiality threshold, e.g. 250k or 5%] has a named driver and an owner, and zero commentary sentences contradict the tables.
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.
Note the materiality threshold in the success criteria. Set it explicitly. Without it, ChatGPT will either explain every trivial movement or skip variances your board will ask about. The threshold is your judgment call and it belongs in the prompt, not in the model’s inference.
Once the narrative spine is agreed, the second prompt converts it into the deck. This is where most of the time saving lands, because slide structure and speaker notes are highly pattern-driven and the model has the prior pack to work from.
First, read these files completely before responding:
[agreed_variance_analysis.md] — the narrative spine we finalised in the previous step
[prior_board_pack.md] — last quarter’s deck, including slide order, chart types, and appendix structure
[board_standing_agenda.md] — the fixed agenda items and time allocations for this board
Here is a reference for what I want to achieve:
The prior board pack deck structure. Match its section order, its chart selection per slide type, and its appendix conventions.
Here’s what makes this reference work:
Every slide has one message, stated in the slide title as a full sentence. Charts appear only where a trend or comparison matters. Appendices carry the detail the board does not need in the room but may request. Speaker notes are three to five sentences and never repeat the slide text.
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: Slide-by-slide outline, approximately 18 to 22 slides plus appendix list, with title, content bullets, chart specification, and speaker notes per slide.
Recipient’s reaction: The deck builder should be able to open PowerPoint and execute without asking a single clarifying question.
Does NOT sound like: A generic consulting template. No stock section names, no slides that exist to fill space, no chart without a stated takeaway.
Success means: Every slide title is a full-sentence message, every chart has a specified type and data source, and the total slide count fits the [agenda time allocation, e.g. 90-minute] board session.
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.
Two practical notes before you run these. First, upload the prior board pack as markdown, not PDF. The model reads structure and tone far more reliably from clean text, and you avoid losing table formatting. Second, keep both prompts in a single conversation so the second has the first’s output in context. If you are running this quarterly, save the final prompt pair as a reusable template with the file names and thresholds pre-filled.
The realistic expectation is a first draft that is seventy to eighty percent of the way to final. That is a substantial saving on a task that recurs four times a year. The remaining twenty to thirty percent, the judgment, the political sensitivity, the numbers only you can vouch for, stays where it belongs: with you.
Published on 31 October 2026 on growwithgpt.com