Adapting One Financial Report for the Board and the Team
The fastest way to share a financial report is sending the same document to the board and the team. That gets the numbers out to everyone, but it also means the board gets more detail than a deck slide can hold, and the team gets financial language most of them don't use day to day.
Warning
One report sent to every audience isn't communication, it's distribution. A document built for a board deck reads as overwhelming in an email, and one built for a plain-language email reads as thin in a board deck.
The numbers are the same either way. How much detail earns a read isn't.
Why one version underserves both readers
A detailed report is built to be precise, with every line item accounted for. That precision is exactly what a board deck can't hold in five bullet points, and exactly what a team email doesn't need when most readers just want to know if things are on track.
Before: finish the detailed report, attach it to both the board packet and the team email, let each reader extract what they need.
After: give Claude the full report once, and ask for a version reshaped for each audience, headline bullets for the board, plain language for the team, same underlying numbers.
A process for reshaping one report for two audiences
- 1
Start from the full report, not a mental summary
The detailed version has every number in context. Working from memory of what it says risks leaving out a figure that matters to one audience but not the other.
- 2
Name what each audience actually needs from it
State it explicitly: the board needs headline metrics they can scan in a deck; the team needs to know what it means for their work, in language that doesn't assume financial background.
- 3
Give a real format and length for each version
Ask for a specific number of bullet points for the board and a word count for the team email. A format constraint is what actually produces something scannable instead of a slightly shorter report.
- 4
Confirm both versions keep the same headline numbers
Read both outputs side by side and check the core figures match. A number that shifts slightly between versions, even rounded differently, undermines trust in both.
“
Turn this 4-page Q2 financial report into 5 board-deck bullet points and a 100-word email summary for the broader team, keeping the same headline numbers in both.
”
Inside Claude Tutorial
Reshaping the same numbers for what each reader needs is transferable.
Adapting one underlying document for how differently two audiences actually read, instead of sending the same version to both, applies well beyond financial reports. The app has a full lesson on it, with practice that carries over to any report with more than one real audience.
When the team version needs a number the board doesn't
Sometimes the team email needs a figure the board deck would consider too granular, a specific budget line relevant to their department, for instance. That's fine to include, as long as it's added deliberately rather than left out of both versions by default.
Tip
Ask Claude what detail the team specifically would want that the board summary omits, rather than assuming the board version is simply a longer version of the team one. The two audiences don't just need different lengths, they sometimes need different numbers entirely.
“
The team will want to know how their specific department's budget line performed, which isn't in the board's headline metrics. Add that detail to the team email version without changing the board deck bullets.
”Continue reading
- Writing a Board Update That's Honest About Mixed Results: writing the board-facing version this article reshapes from with the same honesty about what the numbers show.
- Sharpening a Financial Summary Before It Goes Out: making sure each reshaped version still passes a skim test for its own audience.
- Turning a Batch of Expenses Into a Categorized Analysis: where the underlying numbers in a report like this one often start.