Executive Summary Template for Traceable Evidence

Compress evidence for review without taking ownership from the sources

Begin with the executive use case and the authoritative records, then compress only what the named audience needs for one bounded review. Public writing and analysis guidance supports audience focus, visible limitations, plain structure, and source transparency. It does not make a universal executive-summary field model or validate a local conclusion.

1. Freeze the audience, decision purpose, source set, and review window

   Name role IDs for the audience, owner, and reviewer; state the one decision or next review the summary is intended to inform; list the bounded sources; set an evidence cutoff and review-by date. Digital.gov guidance starts with audience, purpose, and topic structure. The pack turns those writing principles into explicit local fields without claiming GSA prescribed the model.

   Sources: [executive-summary-pack], [gsa-plain-principles], [gsa-plain-writing]

2. Register every source before writing the summary

   Give each source a stable ID, safe URL, title, publisher or owner role, publication and access dates, bounded scope, limitations, and current status. Keep full source text and confidential material in the authoritative owner. GOV.UK guidance favors clear, meaningful structure and accessible text; the pack applies that discipline to a source register.

   Sources: [executive-summary-pack], [govuk-clear-language], [govuk-accessible-documents]

3. Extract source facts without flattening their evidence type

   Assign a stable ID and classify each item as fact, explicitly labeled inference, source-owned recommendation, or gap. Preserve source references, confidence, and evidence status. The UK Analysis Function recommends making limitations and what can or cannot be concluded prominent; its cited page was marked under review on 2026-08-01, so its status is disclosed here.

   Sources: [executive-summary-pack], [analysis-function-uncertainty]

4. Reconcile every quantitative statement exactly

   Retain value, unit, as-of date, numerator, denominator, denominator unit, measure ID, and source-fact ID. Recompute percentages from numerator and denominator, and reject a statement that drops any required token. This is arithmetic and traceability validation, not verification that the source measure is true or representative.

   Sources: [executive-summary-pack]

5. Map every material statement through the compression ledger

   Each summary statement names its exact source-fact IDs and matching compression type. Inferences begin with “Inference:”, source-owned recommendations with “Source recommendation:”, and gaps with “Gap:”. The narrow historical GAO executive-summary guide is useful as a public-sector writing reference, but its 1986 context does not establish a current universal template.

   Sources: [executive-summary-pack], [gao-executive-summaries]

6. Keep risk, gaps, uncertainty, and dissent visible

   Link each risk, gap, uncertainty, and dissent item to source facts and visible summary statements. A stale or expired source must retain its status and a visible gap. Do not upgrade association into causation, a source recommendation into Playcode advice, or missing evidence into a clean conclusion.

   Sources: [executive-summary-pack], [analysis-function-uncertainty]

7. Hand off decisions and actions, then validate the draft

   Use reserved external references for separately owned decision and action records, keep handoff status at not_started, and preserve every authority and outcome flag as false. Run the closed schema, semantic tests, privacy and CSV guards, projection checks, and deterministic builder before human review. These checks expose selected defects; they do not approve the record.

   Sources: [executive-summary-pack], [json-schema-2020-12], [rfc-2606], [owasp-csv-injection], [w3c-wcag-22]

The executive-summary boundary

This owner covers one versioned evidence-compression record for a bounded source set, named executive audience, and decision purpose. The authoritative sources and every later proposal, appraisal, meeting, project state, decision, action, and outcome remain separate.

Three bounded executive-review patterns

Each pattern begins with a named audience and source set, preserves limitations, and stops before an adjacent owner. The summary can inform a later review without becoming the project, proposal, appraisal, meeting, research, decision, or action record.

Decide whether a statement belongs in this summary

A mapped statement remains a draft compression of source material. Use these rules to keep the review layer concise without overstating evidence or absorbing adjacent records.

1. The statement has no exact source-fact ID

   Choose: Remove it or create a typed source fact linked to an authoritative source, with an explicit evidence status and limitations.

   Tradeoff: The draft may become shorter, but an unsupported sentence cannot acquire authority through repetition.

2. The sentence moves beyond a source fact into interpretation

   Choose: Label it as an inference, preserve the supporting fact IDs, state the uncertainty, and avoid causal or universal language the sources do not support.

   Tradeoff: The implication remains visibly qualified instead of appearing to be a direct source fact.

3. The source recommends an option or next step

   Choose: Label it “Source recommendation:” and retain the source owner; do not rewrite it as “we recommend” or a Playcode recommendation.

   Tradeoff: Readers see the recommendation without confusing source ownership with endorsement or authorization.

4. A source is stale, expired, under review, incomplete, or contested

   Choose: Keep its status and limitations visible, add a mapped gap or uncertainty item, and set a review expiry instead of silently dropping the caveat.

   Tradeoff: The summary is less tidy, but the evidence boundary stays honest and reviewable.

5. A sentence includes a number

   Choose: Preserve the exact value, unit, as-of date, denominator and denominator unit, source-fact ID, and numerator when the measure is a percentage.

   Tradeoff: The statement takes more space, but a reviewer can reconcile the measure and its population.

6. The sentence records project state, appraisal, proposal, meeting, research, approval, action, or outcome

   Choose: Replace copied fields with a stable external reference and return the content to its canonical owner.

   Tradeoff: Reviewers follow the source record, but the executive summary does not become a stale parallel system.

What this template and validator cannot prove

A closed record can expose missing IDs, unsupported mappings, stale evidence, hidden gaps, broken chronology, unreconciled measures, unsafe data, and projection drift. It cannot make a source, compression, or judgment true.

• The fictional sources, measures, facts, inference, recommendation, gaps, uncertainty, dissent, and handoffs are examples, not evidence about a real organization or decision.
• Passing validation does not establish source authenticity, truth, completeness, accuracy, representativeness, causation, recommendation quality, or suitability for a decision.
• The pack creates no approval, authorization, project status, business case, project proposal, meeting minutes, research report, legal or compliance conclusion, financial conclusion, audit assurance, action, or outcome.
• The validator rejects selected unsafe links, contacts, secrets, commands, formula prefixes, authority claims, and copied adjacent fields, but it is not a complete privacy, security, accessibility, legal, compliance, financial, or audit review.
• GSA, GOV.UK, the UK Analysis Function, GAO, JSON Schema, W3C, IETF, and OWASP did not prescribe, review, approve, certify, or endorse this Playcode artifact.
• The resource is an ordinary informational article and does not grant AI signup credits or claim that Playcode automatically summarizes, verifies, approves, decides, or executes anything.

Primary guidance and same-release artifact evidence

The pack is the exact source for its fictional records, mappings, tests, and archive. Primary public guidance supports audience focus, clear structure, visible uncertainty, source transparency, accessible content, safe fictional domains, and CSV risk awareness. None validates the local evidence or prescribes this field model.

1. [executive-summary-pack] Playcode editorial artifact:Executive summary template pack

   Checked August 1, 2026. Supports: The exact fictional Markdown, JSON, two CSV projections, closed schema, validator behavior, 66 tests, privacy boundaries, and deterministic archive described on this page. Public availability remains unverified until deployment.

2. [gsa-plain-principles] US General Services Administration:Plain Language Principles

   Checked August 1, 2026. Supports: Defining the audience, leading with the topic, organizing information, and summarizing long material. It does not prescribe this data model or validate a summary.

3. [gsa-plain-writing] US General Services Administration:Plain Language Writing

   Checked August 1, 2026. Supports: Audience-centered wording, direct structure, active voice, and readable sections. It does not establish evidence truth or completeness.

4. [govuk-clear-language] GOV.UK Publishing:Use clear language

   Checked August 1, 2026. Supports: Clear language for broad and specialist audiences, specific wording, active voice, and short readable chunks. It does not prescribe the pack fields.

5. [govuk-accessible-documents] GOV.UK:Publishing accessible documents

   Checked August 1, 2026. Supports: Simple document structure, meaningful headings, accessible text, descriptive links, and avoiding images that contain text. The page was last updated 2025-10-09 when checked.

6. [analysis-function-uncertainty] UK Government Analysis Function:Communicating quality, uncertainty and change

   Checked August 1, 2026. Supports: Prominent limitations, audience-tailored uncertainty, source transparency, context, and clear statements about what can and cannot be concluded. The page displayed an under-review notice when checked.

7. [gao-executive-summaries] US Government Accountability Office:Executive Summaries

   Checked August 1, 2026. Supports: A narrow historical public-sector executive-summary writing reference published in 1986. Its age and context do not support a universal current template or any local conclusion.

8. [json-schema-2020-12] JSON Schema:JSON Schema Draft 2020-12

   Checked August 1, 2026. Supports: The schema dialect used to close object shapes, require fields, and constrain the bundled record. Structural validity does not establish evidence truth or judgment.

9. [rfc-2606] Internet Engineering Task Force:RFC 2606: Reserved Top Level DNS Names

   Checked August 1, 2026. Supports: Reserved fictional example domains. It does not make an arbitrary URL or imported record safe.

10. [owasp-csv-injection] OWASP Foundation:CSV Injection

    Checked August 1, 2026. Supports: Spreadsheet formula-prefix risk considered by the pack CSV guard. The selected guard is not a complete spreadsheet security guarantee.

11. [w3c-wcag-22] World Wide Web Consortium:Web Content Accessibility Guidelines 2.2

    Checked August 1, 2026. Supports: Applicable web-content guidance for perceivable structure, meaningful sequence, contrast, reflow, labels, and robust rendering. No conformance claim is made.

Executive summary template questions