A summary becomes more useful when a reader can trace an important claim to its source. Preserve that path while reducing the detail shown on the front page.
Use stable references for records, decisions and supporting files. A total can point to a defined reporting period and its source rows. An unresolved action can point to the request that created it. The reader should understand what the reference supports.
Avoid competing truths
In a fictional operations review, a slide shows one delivery count while the workbook shows another. Copying numbers into a presentation created a second place requiring maintenance. A dated export may be appropriate if its boundary is clear; an unexplained manual copy invites confusion.
State the cutoff, version and known limitations with the summary. If information changes after the cutoff, record the revision rather than silently replacing history.
Match detail to the decision
The manager need not inspect every source row in every meeting. Make the path available for exceptions, questions and assurance. Protect access to confidential material instead of distributing it unnecessarily.
Apply the same practice to your own planning. Keep the reason and evidence near a consequential decision so your future self can understand it. Brevity becomes more trustworthy when the missing detail remains retrievable rather than simply disappearing.