Published October 12, 2026.
Why the control matters
A board packet often compresses finance, operations, people, risk, and product material into a single narrative. A source map lets reviewers trace each material claim to an owner, reporting period, and approved record without cluttering the director-facing document.
Build the record
For every section, list the author, accountable executive, source system or controlled document, data cutoff, version, known limitation, and approval state. Use stable links and restrict access according to the underlying information.
Run the workflow
Mark facts, estimates, management judgments, and proposed decisions differently. A chart with a current visual style can still contain an old denominator; a copied paragraph can retain a conclusion after the source changed.
Review the evidence
Before circulation, reconcile cross-references, pagination, appendices, and figures against the approved source map. Freeze a distribution version and route late changes through a named owner instead of silently replacing files.
Close the loop
After the meeting, connect resulting decisions and requested follow-ups to the exact packet version considered. The assistant owns orchestration and evidence; directors, officers, counsel, and functional owners retain their respective judgments.
Authority and limitations
Create a Source Map for Board Pre-Reads is an operating workflow, not legal, financial, security, employment, travel, or governance advice. The executive office should approve authority, information handling, retention, and exception ownership before using it.