Blog

FP&A Reporting Pack Checklist: 8 Things to Verify Before the Board Sees It

The errors that embarrass a finance team are rarely wrong calculations. They are a "Q1" label on a Q2 slide, a $1234 missing its comma, or a chart from last month's model. Here is a checklist.

Most reporting pack errors are not math errors. They are presentation errors — things that are correct in the spreadsheet but wrong, stale, or inconsistent by the time they reach the slide. The board does not see the spreadsheet. They see the deck. And these are the mistakes that erode confidence in the numbers, even when the numbers themselves are right.

This checklist covers the eight most common failure points, roughly in the order you should check them. Some are manual checks that require human judgment. Others can be partially or fully automated.

The checklist

1. Period, scenario, and date labels are consistent

This is the most common silent error in recurring packs. A slide title says "Q2 2026" but the chart beneath it still shows Q1 data. A YTD label reads "YTD April" on one slide and "YTD May" on the next. Or a slide labeled "Forecast" actually shows Actuals — easy to miss in a large pack, and just as damaging as a wrong date.

How to check: Manually scan every slide for month, quarter, YTD/QTD, fiscal year, and Actual/Budget/Forecast references, and compare them against the period the pack is supposed to cover. This is tedious by hand, but Navifia's Check Period answers what periods the deck claims to cover — one row per logical period (FY26 and FY2026 share a row; YTD and QTD stay separate) — so a leftover "Q1" in a "YTD May" pack, or an FY/CY mix, is obvious before the board sees it.

2. Charts and tables reflect the current model

If charts are pasted as static images — which is how most teams do it — there is no way to verify programmatically whether a chart matches the current spreadsheet. You compare visually, or you trust the process.

How to check: If your charts are linked (via paste-special OLE objects or a tool like Navifia), check the link status. Navifia's Excel Sync keeps every chart, table, or range as a live linked shape, and the Excel Links pane shows each one's status — OK, Stale, or Source missing — so you can verify without opening every source workbook. If charts are static images, compare key figures against the model by hand.

3. Number formatting is consistent

A revenue figure of $1234 next to another formatted as $1,234 looks like a mistake even if both are correct. Inconsistent decimal places, missing thousands separators, and mixed currency symbols undermine credibility.

How to check: Review every figure on every slide. Navifia's Check Numbers inventories distinct hardcoded quantities — $1,234 and 1234 share a row — so leftover KPIs and formatting differences are easy to spot after Check Period.

4. Fonts and colors follow the template

Pasting content from Excel into PowerPoint often brings the source formatting along. A chart pasted from a workbook with Calibri into a deck templated in Arial is obvious in person, even if it is hard to spot on screen.

How to check: Spot-check against the brand palette. If a rogue typeface slipped in, Navifia's Check Fonts (optional polish) lists fonts rarest-first and can Replace them deck-wide.

5. Open discussion threads are resolved — or at least visible — before you publish

"Where did this EBITDA margin come from?" A question like that often lives in an email thread, disconnected from the slide it's actually about, and it's easy to forget it was ever open by the time the deck ships.

How to check: If review questions live in email or chat, someone has to remember to chase every one down before distribution — there's no list to check against. Navifia's Threads anchors a discussion to the actual cell it's about, and if a linked shape's source workbook has open threads, they surface right in PowerPoint's Excel Links — so before you publish, you can see at a glance whether the data behind a slide still has an unresolved question attached, without switching to Excel or digging through email.

6. No internal draft markings, review notes, or hidden slides remain

Working copies of board decks accumulate "Draft" or "For Review" watermarks, hidden backup slides, and speaker notes with internal commentary ("need to check this with Sarah") — none of which should reach the board.

How to check: Switch to Slide Sorter view to catch hidden slides, and read through speaker notes by hand — neither is something software should silently delete for you. For status watermarks, Navifia's Stamp applies DRAFT, FOR REVIEW, or other overlays during the working cycle, then removes them from every slide in one click — this slide or all slides — once the deck is ready. If your policy requires a CONFIDENTIAL mark on the final copy, Stamp adds that too.

7. Slide titles, sources, and footnotes match the content

Titles are often the last thing updated because they were written when the slide was first created — a slide titled "Revenue Growth Accelerates" above a chart showing flat revenue is a credibility problem. The same goes for sources: a slide that says "Source: Bloomberg, March 2026" in a June pack tells the reader either the data is stale or the footnote is.

How to check: Read each slide title against the data it describes, and confirm every slide with external data has a source footnote whose date matches the current period. There is no shortcut for either — both require human judgment about whether the narrative and the citations actually match what's on the slide.

8. The final copy is clean, current, and correctly sent

A working file should never go out as-is: it can carry raw Excel-link metadata (the workbook path, sheet, and cell address a recipient could read straight out of the file), leftover stamps, or simply balloon to 50 MB or more from months of accumulated pasted images, making it slow to open and hard to email.

How to check: Agree on a version-naming convention with your team and confirm the filename and title slide match it before distribution. Navifia's Finalize Deck produces a distribution-ready copy in one click — strips every link tag and stamp, exports to .pptx or .pdf — while the working deck keeps its live links for next month. Send Slides then exports just the approved slides (or the whole deck) straight to a new file or an unsent Outlook email, without touching the live presentation. Using linked shapes instead of pasted screenshots also keeps file size down over time, since a link stores only the current version, not a stack of historical pastes.

Building the habit

No checklist helps if it lives in a shared drive and nobody opens it. The useful version is the one taped to the process: the last step before the deck leaves, run by the person who owns the pack.

Most of these checks — period consistency, leftover figures, link status, open threads, draft markings, the final export — are mechanical enough to automate, which is what Navifia's deck QA and cleanup tools (Check Period, Check Numbers, Excel Links, Threads, Stamp, Finalize Deck, Send Slides — plus optional Check Fonts) are built to do: catch the errors that are tedious for a human to find but straightforward for software to flag. The judgment calls — whether a title matches its chart, whether a footnote is actually current — still need a human.

The goal is not zero errors. It is catching the avoidable ones before the board does.

Automate the mechanical checks

Navifia's Check Period and Check Numbers (plus Threads and Stamp) handle the tedious passes. Free during the public beta — see Pricing for dates.

Join the beta