A nursing QI executive summary gives a busy reader the essential account of a quality-improvement project and the decision its findings support. It should identify the local problem, explain what was tested, present the most relevant results and state a proportionate next step.
The challenge is selection. A full project may contain background literature, several improvement cycles, measurement details and implementation lessons. The summary must preserve the meaning of those findings while removing detail that the reader can obtain from the main report. Shortening every section equally rarely achieves that purpose.
This guide explains how to write the summary of a completed nursing QI project. If you are deciding which document your assignment requires, use executive summary versus abstract in nursing. For the full report, see writing a nursing quality-improvement project.
Start with the audience and decision
Ask who will read the summary and what they need to do afterwards. A ward team deciding whether to continue a small test needs different detail from an academic marker assessing the project’s learning. The assignment brief may prescribe a structure that takes priority over general advice.
University of Leeds report-writing guidance emphasises audience, purpose and concise organisation, and describes an executive summary as covering the problem, objectives, main findings and recommendations (University of Leeds, n.d.). Apply that principle to the actual QI project rather than copying a business-report format without adaptation.
Write a private planning sentence: “After reading this summary, the reader should understand whether to [decision] because [main evidence and limitation].” This is a drafting aid, not necessarily a sentence for the final document. It forces you to identify the report’s practical conclusion.
If the project did not support a clear implementation decision, say so. A summary can recommend further testing or better measurement. It does not need to describe every completed project as a success. Honest uncertainty is useful when it identifies what must be resolved before wider adoption.
A practical nursing QI executive summary structure
| Component | Reader’s question | Include |
|---|---|---|
| Problem and context | Why was this project needed here? | Local issue, setting and relevant baseline |
| Aim | What was the project trying to change? | Specific improvement objective |
| Change and evaluation | What was tested and assessed? | Intervention, scope, period and key measures |
| Findings | What happened? | Main results with interpretable numbers |
| Limits and implications | How much confidence is justified? | Important uncertainty and practical consequence |
| Decision or recommendation | What should happen next? | Feasible, evidence-linked action |
These components can appear as short headings or a connected paragraph, depending on the required format. They are not a universal mandatory template. Use the brief’s terminology and ensure the final summary stands alone.
The SQUIRE 2.0 reporting guideline draws attention to improvement theory, context and the study of the intervention (Ogrinc et al., 2016). Those concerns help you decide what meaning must survive compression. SQUIRE is a reporting guideline, not a rule that every executive summary must reproduce the full checklist.
Write the problem using local evidence
Begin with the actual care or process problem. Explain where it occurred and why it mattered to nursing practice. A broad opening such as “patient safety is important worldwide” consumes space without telling the reader what the project investigated.
If you have a baseline measure, identify its denominator and period. A percentage without a population or timeframe can mislead. If the baseline data were incomplete, do not convert an impression of poor performance into a precise claim.
Separate the clinical concern from the measure available. Incomplete documentation may indicate a recording problem, a care-delivery problem or both. The summary should not claim that a documentation audit directly measured patient understanding unless that was genuinely assessed.
Keep the context selective. Staffing changes, a new electronic record or an unusual seasonal workload may be relevant if they affect interpretation. A long service history is usually less useful. Include the contextual feature because it helps explain what was tested or what the result means.
State the aim and what was actually tested
Use the project’s final authorised aim. If the aim changed during the work, the main report should explain why; the summary should reflect the completed scope. Avoid presenting an abandoned objective as if it was achieved.
Name the change in concrete terms. “Improving communication” is too broad if the intervention was a checklist used at discharge. State who used it, where it was tested and the relevant duration. These details help the reader judge whether a recommendation is feasible elsewhere.
Distinguish the improvement activity from its evaluation. Introducing a reminder is the change. Auditing completion, collecting staff feedback and monitoring delays are ways of examining it. The summary needs enough information to show how the findings were obtained without listing every operational step.
Use the correct tense. A completed project reports what happened. A proposal explains what will be tested and how. Never write invented outcomes to make a proposal look like a finished evaluation. If the assignment asks for a hypothetical example, label it clearly.
Choose results that answer the improvement question
Select findings that connect directly to the aim and decision. Usually, the reader needs the main process or outcome measure and any important balancing information. A positive process result may be less persuasive if the change caused substantial delays or extra workload.
Report actual numbers in a form the reader can interpret. When presenting a proportion, retain numerator and denominator where space permits. When showing change, identify the baseline and follow-up periods. Explain whether the same sampling approach was used.
Do not equate a before-and-after difference with a proven intervention effect. Other changes may have occurred over the same period. Small samples and short follow-up may limit interpretation. The summary should preserve the most important limitation rather than hiding it in a later chapter.
For detailed measurement choices, consult the numerator and denominator guide and the evaluation-timeframe guide. This article concerns how to communicate those decisions concisely once the project evidence is available.
Worked nursing QI executive summary example
Fictional teaching example: The following summary demonstrates reporting structure. The service, figures and findings are invented for explanation and must not be presented as real project evidence.
This project examined incomplete documentation of medicine explanations on a fictional adult ward. The aim was to improve recording of the agreed discharge explanation without increasing discharge delays. A brief documentation prompt was tested for four weeks following a four-week baseline audit.
The same eligibility rule was applied in both periods. Documented explanations increased from 18 of 30 eligible records at baseline to 25 of 32 during the test. Staff feedback suggested that the prompt was easier to use when incorporated into the existing discharge workflow. Discharge-delay data were incomplete, so the project could not determine whether the change affected timeliness.
The findings support continuing a limited test while improving balancing-measure collection. They do not establish improved patient understanding or justify immediate implementation across other wards. The ward improvement lead should review the prompt with staff and patient representatives, confirm the measurement plan and report the next cycle’s findings before a wider rollout decision.
The example keeps the problem, intervention, findings and recommendation connected. It distinguishes documentation from patient understanding and does not describe the before-and-after difference as causal proof. The missing balancing data affect the recommendation directly.
Notice the denominator change. Thirty baseline records and thirty-two test-period records are not presented as though the same individuals were followed. The summary also avoids reporting a vague “large improvement” when exact descriptive information is available.
Annotate the example before adapting the approach
| Example feature | Why it matters |
|---|---|
| Fictional setting identified | Prevents an illustrative case being mistaken for evidence |
| Specific documentation outcome | Keeps the claim aligned with the measure |
| Baseline and test periods | Shows the comparison window |
| Numerators and denominators | Makes proportions interpretable |
| Incomplete delay information | Preserves a decision-relevant limitation |
| Limited next test | Matches the recommendation to the evidence |
To adapt the approach, replace the structure with your project’s own verified information. Do not retain the fictional findings as a convenient model result. If your project uses qualitative feedback, summarise what was actually reported and avoid inventing prevalence from a small set of comments.
If the brief requires citations in the summary, follow that convention. If references are normally confined to the report, ensure the evidence can still be traced there. Neither approach permits unsupported claims. The summary should remain consistent with the cited argument in the main text.
Turn findings into a proportionate decision request
Make the requested action visible. “Further improvement is needed” leaves the reader unsure what to authorise. A more useful recommendation identifies the next test, the responsible role and the evidence needed before expansion.
Match the action to the evidence stage. A small feasibility test may justify refinement. Repeated local improvement with reliable measurement may support broader testing. Neither automatically demonstrates that a change is effective in every nursing setting.
Include resources when they materially affect the decision. If continuing the intervention requires protected staff time or a digital change, acknowledge that requirement. Do not invent a cost saving simply because the intervention seems efficient. Financial claims need their own evidence.
The summary should point to the main report for detailed planning. Use prioritising evaluation recommendations when the task is choosing between actions. The executive summary’s role is to communicate the report’s justified choice, not redo the whole prioritisation exercise.
Edit your nursing QI executive summary
Follow the assessment’s actual limit. There is no universal executive-summary length for nursing projects. If no limit is given, use the document’s purpose and seek course guidance rather than assuming a fixed percentage of the report.
Cut general background before cutting essential findings. Remove repeated explanations of why quality matters, long descriptions of routine meetings and acronyms that require several words of explanation but add little. Keep the outcome, period and limitation that determine the decision.
Replace promotional language with evidence. “A highly successful initiative transformed practice” is less informative than a precise account of what changed and what remains uncertain. Strong verbs help, but accurate meaning matters more than making the project sound impressive.
Read the summary without the report open. Can a reader identify the problem, change, main result and next action? Then read it alongside the report. Does every claim agree with the underlying evidence? Both checks are necessary: a standalone summary can still be inaccurate.
Common errors in completed-project summaries
- Writing an introduction that explains the topic but omits findings.
- Using future tense for a completed project.
- Calling a documentation change a patient-outcome improvement.
- Reporting percentages without identifying the relevant sample.
- Leaving out a balancing measure that changes the recommendation.
- Claiming effectiveness from an uncontrolled short local test.
- Adding recommendations that do not appear in the report.
- Describing a proposed project as if implementation occurred.
When correcting these errors, change the claim rather than merely adding a cautious adjective. “Possibly improved patient safety” remains unsupported if safety was not measured. State the outcome actually assessed and explain its relationship to the wider clinical aim.
Also check confidentiality. A summary circulated beyond the immediate team may need less identifying context than an internal authorised report. Follow the university and organisation’s requirements. Anonymisation should preserve the meaning of the project without exposing patients, staff or the service unnecessarily.
A final consistency check across the report
Compare the summary with the aim, methods, results and recommendations in turn. Make a short list of every numerical claim and verify it against the final table. Check whether exclusions or missing data changed the denominator after an earlier draft was written.
Next, check the wording of causal claims. Terms such as caused, prevented and reduced can imply more than the design establishes. Use descriptive language where appropriate, and reserve stronger conclusions for evidence that supports them.
Finally, ask whether the recommendation follows from the limitations. If follow-up was short, a sustainability claim needs qualification. If implementation varied, the next step may involve understanding that variation. A summary becomes useful when uncertainty leads to a practical next question.
For editing feedback, provide the full report and assessment brief with the summary. Reviewing the summary alone cannot establish whether it faithfully represents the project. The editing guide explains how to focus feedback on structure, evidence and consistency.
Check the summary with a decision-focused reading
Ask a reader unfamiliar with the project to identify the requested decision after one reading. If they can describe the topic but cannot say what should happen next, the recommendation may be buried or too vague. Move the decision into a clear final sentence and retain the evidence that makes it reasonable.
Then ask what information would make the reader hesitate. They might notice that the measure concerns recording rather than care quality, that staff feedback came from only a few volunteers or that follow-up ended before the service returned to its usual workload. These observations can identify a missing qualification.
Do not respond by adding every possible limitation. Choose the uncertainty that materially affects the decision. A concise summary should help the reader judge the project, not list every issue discussed in the dissertation. If several limitations jointly prevent expansion, make that implication explicit.
Save this reader check until the main report is stable. Otherwise, the summary can become polished around findings that later change. After any revision to analysis or recommendations, return to the summary and update it before submission or circulation.
Frequently asked questions
Should I write the summary first?
You can draft planning notes early, but finalise the summary after the findings and recommendations are settled. Otherwise it may describe intentions instead of completed work.
Can I use headings?
Yes, if the required format permits them. Short headings can help readers locate findings and recommendations. Follow any university template.
Should I include every result?
No. Select results that answer the aim and affect the decision. Preserve important negative or balancing findings even when they complicate the message.
Can the summary contain a table?
Only where the brief and length allow it. A compact table can clarify key results, but it should not force readers to search elsewhere for the main meaning.
What if the project did not improve the outcome?
Report that honestly and explain what the evaluation suggests next. A justified decision to refine or stop a change can be useful improvement learning.
Can I use the example in my assignment?
Use it to understand the structure. Write the submitted summary from your own authorised project and verified findings, following your institution’s academic-integrity requirements.
Final writing check
A strong nursing QI executive summary makes the project understandable and the next decision assessable. Preserve the evidence that matters, explain its limits and request an action the findings can support.
Arrange a focused executive-summary review
When requesting feedback, include the complete QI report and its final results tables. This lets the reviewer check whether the summary preserves the project’s meaning, rather than merely polishing its sentences. Retain responsibility for the findings and obtain any necessary organisational permission before sharing service information. Remove confidential patient and staff details from the material.
Request feedback on your nursing QI summary after checking the review process. Our academic-support principles and client experiences explain the service context. The nursing academic-support homepage provides routes to guidance for other parts of your project.
References
- Ogrinc, G., Davies, L., Goodman, D., Batalden, P., Davidoff, F. and Stevens, D. (2016) ‘SQUIRE 2.0 (Standards for QUality Improvement Reporting Excellence): revised publication guidelines from a detailed consensus process’, BMJ Quality & Safety, 25(12), pp. 986–992. Available at: https://doi.org/10.1136/bmjqs-2015-004411 (Accessed: 16 October 2026).
- University of Leeds (n.d.) Report writing. Available at: University of Leeds report-writing guidance (Accessed: 16 October 2026).
