What is typically required for the executive summary in EI submissions?

• A. A long, multi-page narrative
• B. A concise narrative outlining goals, actions, impact, partnerships, and sustainability in about one page.
• C. Only a list of sponsors
• D. A detailed technical design document

Answer: (B)

The executive summary is meant to give a concise, high-level snapshot of the project in about one page. It should quickly communicate what you aimed to achieve, what you did to get there, the results or expected impact, who you partnered with, and how the project will continue after the grant or submission period.

Focus on these elements in a tight narrative:

• Goals: state the purpose and what you hoped to accomplish, stated clearly and specifically.

• Actions: summarize the main activities or approaches you used to pursue those goals.

• Impact: describe the outcomes or anticipated effects, including any measurable results or metrics.

• Partnerships: highlight key collaborators, supporters, and how those relationships enabled progress.

• Sustainability: outline how the project will endure over time beyond initial support, such as ongoing funding, community uptake, or maintenance plans.

Keep it brief and accessible so someone skimming the submission can understand the project’s purpose, what was done, and why it matters.

Long, multi-page narratives are too lengthy for an executive summary; a mere list of sponsors doesn’t convey actions or outcomes; and a detailed technical design document goes into details that belong in the main sections, not in the summary.