Make Your Financial Summary Skimmable in 30 Seconds
Most financial summaries go out after one read-through by the person who built the numbers. That catches typos, but it doesn't catch whether the two figures that actually matter stand out to someone giving the doc thirty seconds, not a careful read. A finance lead who spent two days reconciling a Q2 budget can send a summary where the one number a director actually needs, whether spend came in under or over plan, is buried in the third paragraph.
Warning
You already know which numbers matter before you open the doc. A reader skimming it for the first time doesn't have that advantage, and a summary that only works for you isn't finished.
A summary you can read fast because you already know it isn't the same as one a stranger can read fast.
Why your own read-through can't catch a skim failure
You wrote the summary with every number already meaningful to you, so your eye naturally lands on what matters. A first-time reader has no such shortcut, and a number that isn't visually or structurally emphasized just blends into the paragraph around it. A figure you'd recognize as the headline the moment you glance at the page reads, to someone new to the document, exactly the same as every other number on it.
Picture a Q2 marketing budget summary written as four dense paragraphs, one per category. The headline fact, that total spend came in 8% under plan, is true and stated, but it's the fourth sentence of the second paragraph, with the same formatting as every other sentence around it. A director skimming for thirty seconds before a meeting is more likely to catch a smaller, more visually prominent number, like a single line item that happened to be bolded for an unrelated reason, than the actual headline result the whole summary was meant to communicate.
Before: write the summary, read it once, decide the important numbers are obvious, send it.
After: hand it to Claude with the summary and ask directly whether a thirty-second skim would catch the numbers that matter most, then fix what it flags.
A process for testing a summary before it goes out
- 1
Give Claude the actual draft, not a description of it
Paste the summary as written. A description of what it says loses the exact structure and phrasing that determines whether a number actually stands out, since the test depends on the real layout, not a paraphrase.
- 2
Name which numbers are the ones that matter most
Tell Claude specifically which one or two figures the reader needs to walk away with. Without that, it can only guess at what "important" means in this doc, and different readers of the same summary might reasonably guess differently.
- 3
Ask directly whether a skim would catch them
Ask whether someone skimming for a set amount of time would actually register those numbers, not whether the summary "looks good." A skim test is a different question than a quality check, and it's the one that actually predicts whether the summary does its job.
- 4
Fix the structure, not just the wording
If the numbers don't stand out, the fix is often structural, a bolded figure, a shorter opening sentence, not a full rewrite. Ask for the smallest change that makes the number land, since a full rewrite risks losing the parts that were already working.
Here's my draft Q2 budget summary for the marketing department. Tell me honestly if someone skimming for 30 seconds would catch the two numbers that matter most, and suggest how to make them stand out.
”Different audiences skim for different things, so it's worth running the check again if the same summary is going to more than one reader with different priorities.
This same summary is also going to the operations team, who care more about the vendor spend line than the overall budget variance. Check whether that specific number would survive their skim too, and adjust if it wouldn't.
”
Inside Claude Tutorial
Testing for a skim, not just a careful read, is transferable.
Checking whether the point of something survives a fast read, instead of only a careful one, applies well beyond financial summaries. The app has a full lesson on it, with practice that applies to any document most people won't read start to finish.
When every number seems important
Sometimes the honest problem isn't formatting, it's that too many numbers are competing for attention and none of them clearly win. That's worth catching before send, since a summary that emphasizes everything effectively emphasizes nothing. A doc with five bolded figures has, in practice, zero figures that actually stand out from the rest.
Tip
Ask Claude to force a ranking: if the reader only remembers one number from this summary, which one should it be? A summary that can't answer that question needs a sharper point, not better formatting.
This summary has five numbers I initially flagged as important. If a reader could only walk away remembering one, which should it be, and how would you restructure the summary around that single number?
”Once one number has been chosen as the headline, the remaining figures still need a place, just a visually quieter one, so the summary stays complete for a reader who does want the full picture without competing with the headline for attention.
Now that we've picked the headline number, restructure the rest of the summary so the other four figures are still present and easy to find for a reader who wants the full detail, without competing visually with the headline.
”Continue reading
- Writing a Budget Variance Explanation That Doesn't Sound Defensive: what to write once a skimmable summary surfaces a number that needs explaining.
- Turning a Batch of Expenses Into a Categorized Analysis: where the numbers in a summary like this one often come from.
- Getting Started with Claude: the underlying habits, context, iteration, specificity, this entire process is built on.