No Second Set of Facts

Opening Scene

There is exactly one thing a closing argument and a legal brief are never allowed to do differently: state a different number for the same fact. They can differ in length, tone, structure, and emphasis endlessly — that’s the whole design of this series so far — but if the closing argument tells the jury the contract was signed in March and the brief tells the judge it was signed in April, the case doesn’t have two honest documents anymore. It has a credibility problem that swallows both of them, no matter how well-crafted either one is. A single factual contradiction between the two is enough to make a skeptical reader distrust every other number in both documents, whether or not those other numbers were actually correct.

Executive and analyst reporting runs the exact same risk, and it’s the most damaging failure mode in this entire series precisely because it’s invisible until someone happens to compare the two documents side by side — usually in a meeting, in front of exactly the people you’d least want to see it.

In Plain English

Consistent numbers means that any figure appearing in both the executive summary and the analyst report — the same metric, the same time period, the same scope — must match exactly, even though the two documents present very different sets of numbers overall. This doesn’t mean both documents show the same numbers; the executive version rightly shows far fewer. It means that for whatever numbers genuinely overlap between them, there is exactly one truth, computed once, from one source, and both documents draw from it rather than each recalculating it independently.

The Old Way

Reports without a single-source discipline behind them tend to drift into mismatches for a few common, mundane reasons:

Independent recalculation. The executive summary and the analyst report are built by different people, at different times, querying the same underlying database separately — and a filter, date boundary, or rounding choice differs slightly between the two queries without anyone noticing.
Stale snapshots. One document gets updated when new data arrives and the other doesn’t, so a number that was consistent last week quietly stops being consistent this week, with no error message anywhere to flag it.
Definitional drift. A metric like “active customer” gets redefined at some point, and the update reaches one document before the other, producing two different numbers that are each internally correct but no longer describe the same thing.

What’s Changing (and Why AI Is the Reason)

AI-assisted generation makes both documents easier to regenerate from a single computed source rather than built independently by hand. When both the executive summary and the analyst report are drafted from the same underlying analysis object rather than recreated from scratch, the opportunity for independent recalculation to introduce drift shrinks considerably.
This shifts the practical risk from calculation error toward timing and versioning. With generation this fast, the more likely failure isn’t two different formulas producing two different answers — it’s one document getting regenerated on fresh data while the other one, sitting a few clicks away, quietly doesn’t.
AI can now actively check for numeric agreement between two documents automatically, which used to require someone manually cross-referencing every shared figure. A model can compare an executive summary against its source analyst report and flag any figure that doesn’t match — turning a manual, easily-skipped check into an automatable one, a capability this series covers directly later on.

The Metaphor, Fully Extended

Courtroom Element	Executive/Analyst Reporting Concept
The closing argument and the brief needing to agree on every stated fact	The executive summary and analyst report needing to agree on every shared number
A contradiction between the two documents discrediting the whole case	A numeric mismatch undermining trust in both reports at once
The single case file both documents are drawn from	The single computed source both reports should draw their shared figures from
A fact recalculated independently by two different lawyers, drifting apart	A metric recalculated independently for each document, drifting out of sync
A law clerk cross-checking every shared fact between the two filings	AI-assisted automatic checking for numeric agreement between report versions

For Beginners: What to Actually Do

Compute any number that will appear in both the executive summary and the analyst report exactly once, and have both documents reference that single computed value rather than recalculating it separately.
Before finalizing either document, check every figure they share against the other — treat this as a mandatory step, not an optional sanity check.
When updating one document with new data, always check whether the other document needs the same update at the same time.
If you ever discover a mismatch, treat it as urgent — trace it to its root cause immediately rather than just correcting the visible number, since the same root cause is likely to reintroduce the mismatch later.

For Practitioners and Leaders: The Deeper Layer

Build reporting infrastructure so both documents genuinely draw from one computed source rather than depending on individual authors to keep numbers aligned by discipline alone.
Treat any discovered numeric mismatch between an executive and analyst version as an incident worth a root-cause review, not just a quick fix — the underlying process gap that allowed it will produce it again otherwise.
Adopt AI-assisted consistency checking between document versions as a standard pre-publication step, not an occasional audit.
Recognize that a single visible mismatch, however small, tends to cost far more in reader trust than its actual size would suggest — treat consistency as a non-negotiable baseline, not a nice-to-have.

Quick Recap

Every number shared between the executive summary and the analyst report must match exactly, even though the two documents otherwise contain very different sets of numbers.
Independent recalculation, stale snapshots, and definitional drift are the most common mundane causes of mismatches.
Generating both documents from a single computed source reduces calculation-based drift, but shifts the real risk toward timing and versioning.
AI can now automatically check numeric agreement between two report versions, turning a manual cross-reference into a routine, repeatable check.

Where This Fits in the Series

This article closes the core-technique block with the rule every other technique in Articles 5 through 8 depends on: consistency across shared numbers is non-negotiable in a way density and caveat choices are not. Article 10 opens the production block by looking at how teams actually maintain that consistency over time, as both documents get updated again and again without drifting apart.