Executive Summary Pre-Send Checklist: Everything You Must Include Before Sending
Before sending an executive summary, confirm it includes core context for your full document, the key problem or opportunity you address, core recommendations or findings, expected outcomes, and a clear call to action for recipients.
- Ideal summary length
- 10% of full document length, max 1 page for documents under 10 pages
- Required audience focus
- Written exclusively for the needs of the recipient, not the document author
- Mandatory CTA requirement
- Every submitted executive summary needs a specific, time-bound call to action
- Data accuracy rule
- All claims in the summary must match the full accompanying document exactly
- Key takeaway count
- 3-5 priority findings/recommendations maximum, no secondary details
Core Document Context
The first 1-2 paragraphs of your executive summary must set explicit context for the full document it accompanies, so recipients who only read the summary understand what it relates to without opening the full attachment. Mention the full document type (proposal, annual report, project plan, market analysis), the date of the document, the team or department submitting it, and any relevant background that is common knowledge for your audience but not implied in the document title. Avoid overly broad or vague context; for example, instead of "this is a project update", write "this summary accompanies the Q3 2024 South Region Warehouse Expansion Project update, submitted by the Real Estate Operations team".
Core Problem, Opportunity, or Project Purpose
This section directly states the core reason you are sharing the full document, so recipients immediately grasp the stakes of your submission. For problem-focused documents, state the specific pain point, its impact on the business, and the timeline it affects. For opportunity-focused documents, state the unmet market need, internal efficiency gain, or revenue potential you are highlighting, and any time-sensitive windows to act. For status update documents, state the core project or initiative goal you are reporting against. Keep this section to 2-3 sentences maximum, as it is intended to be scannable in 10 seconds or less.
Key Findings or Recommendations
This is the highest-value section of your executive summary, and must include only the most critical 3-5 takeaways from the full document, sorted by priority. For research reports, list your top 3 non-obvious findings that drive your conclusions. For proposals, list your 3 core recommended courses of action, and the justification for each. For project plans, list the 3 core milestones or required approval items you are seeking sign-off on. Do not include minor supporting details, footnotes, or secondary data points here: those belong in the full document.
Expected Outcomes and Risk Overview
Recipients will want to understand what happens if they act on your summary, or if they choose not to act, so this section is non-negotiable for all submissions. State the top 2-3 expected positive outcomes if your recommendations or plan are approved, including quantitative impact where possible (e.g., 12% reduction in operational costs, 18% increase in lead volume over 12 months). Also include 1-2 key risks of inaction or delayed approval, to highlight the urgency of your request. Avoid overstating risks or outcomes, as these should align exactly with the data in your full document.
Final Pre-Send Verification Checklist
Run through this quick checklist immediately before sending your executive summary to confirm no required elements are missing:
- Full document context (type, date, submitting team) is listed in the opening paragraph
- Core problem, opportunity, or project purpose is explicitly stated in the first 3 sentences
- Top 3-5 key findings or recommendations are listed and sorted by priority
- Expected positive outcomes and core inaction risks are clearly outlined
- A specific, actionable call to action (e.g., "approve by EOD Friday, September 13" or "provide feedback by end of week") is included at the end of the summary
- The summary length does not exceed 10% of the full document’s length, or one page maximum for documents under 10 pages
- All figures and claims align exactly with the data in the accompanying full document, with no contradictory or unsubstantiated statements
If you check every item on this list, your executive summary will be clear, actionable, and aligned with stakeholder expectations, reducing the need for follow-up questions and speeding up approval or feedback timelines.
Step by step
- Gather context first Confirm the opening of your summary includes the full document type, submission date, submitting team, and basic background context for the recipient.
- Validate core purpose Check that the core problem, opportunity, or project purpose is explicitly stated in the first 3 sentences of the summary.
- Review key takeaways Confirm you have only 3-5 priority findings or recommendations listed, sorted by relevance to the recipient’s priorities.
- Verify outcomes and CTA Confirm expected outcomes, core risks of inaction, and a specific, time-bound call to action are included at the end of the summary.
- Cross-check against full document Confirm every claim, figure, and statement in the summary matches exactly with the data in the accompanying full document.
FAQ
Do I need to include citations in my executive summary?
Can I include confidential data in an executive summary sent to external recipients?
Should I include a thank you note at the end of my executive summary?
How do I adjust the checklist for a 1-page internal project update summary?
Still have a question about Executive Summary?
Ask the AI Office Work assistant - it answers in your words and can turn the answer into a document.
Ask AI