Nurse leaders, administrators and committee members rarely have time for a full report. An executive summary gives them the answer first: what you found, what it means and what you recommend they do. This guide shows how to fit a whole project onto one page.
An executive summary is written for someone who will decide, fund or approve, and who may read nothing else. That is different from an abstract, which is written for researchers. A chief nursing officer wants to know whether the change worked, what it cost in effort and resources, and whether to keep it. A committee wants to see that the project answered its aim honestly.
Name your reader before you write, and use plain language they would use themselves. Define any term they may not know, and keep statistical detail to what supports the message.
Write the summary after the report is finished, but build it around what the reader must walk away with. A dependable order:
A headed layout with bold lead-ins and a small results table helps a busy reader scan. Some programs ask for the recommendation to come first; follow the rubric.
Share your project report and audience. The ProNursingScholars team can help distill it to one clear page. Details stay confidential.
A summary can be persuasive without being promotional. State the results as they are, including targets that were missed, and give the reason to act or not to act. Stay within one page, roughly 300 to 500 words, using short paragraphs and bullets. If something cannot be shortened without distortion, it probably belongs in the report and can be linked to in a single sentence.
Remove details that would identify patients, staff or units, and confirm with your site whether the summary may be shared beyond the project committee. When you summarize published evidence, credit the sources; style details are on the APA in-text citation page.
Test the page on someone outside the project. Ask a colleague who has not seen the report to read it for two minutes and then tell you what you are asking them to do. If they hesitate, the recommendation is not yet clear enough. Then read the summary against the full report one last time and make sure every number, date and claim matches, because this is the page most likely to be forwarded on its own.
Fictional project: a nurse-led mobility protocol on a surgical unit. Numbers are illustrative.
| Weak opening | Strong opening |
|---|---|
| This report describes a project on patient mobility that was carried out over several months. Many articles were reviewed and a framework was used. The report is divided into six chapters. | Recommendation: Continue the nurse-led mobility protocol on the surgical unit and extend it to one further unit for a 12-week evaluation. Why: Over 10 weeks, documented first-day mobilization rose from 41% to 67% of eligible patients (target 75%), with no increase in reported falls. Findings come from one unit and should be confirmed in a second setting. |
The strong opening leads with the decision, gives numbers with a target, and states a limit. The weak version tells the reader how the report is laid out, which they do not need.
Usually one page, often 300 to 500 words. Some programs allow two. Check the rubric or the organization's own format.
Include a few key citations if the reader will need them, and point to the full reference list in the report. Keep the page uncluttered.
One small table or chart that shows the main result can help. If it takes over the page, move it to an appendix.
Usually before the introduction, or as a separate document for stakeholders. The DNP outcomes evaluation help page covers how results are framed for decision-makers.