How to Write a Quality Improvement Project Report

Introduction

Quality Improvement (QI) is an iterative process focused on making services better for patients and staff. While conducting the project is central, effectively communicating its outcomes and learnings through a comprehensive report is equally vital. A QI report serves multiple purposes: it demonstrates accountability, facilitates knowledge sharing, supports continuous professional development (CPD), and can contribute to local governance requirements or even peer-reviewed publication.

Why This Topic Matters

Many excellent QI projects go unrecognised or fail to embed change simply because their story isn't told effectively. A robust QI report:

• Validates your efforts: Clearly articulating your project's aims, methods, and results demonstrates rigor and impact.
• Shares learning: Other teams can learn from your successes and challenges, avoiding duplication and accelerating improvement.
• Informs decision-making: Leaders and managers rely on well-presented data to make strategic choices about resource allocation and service development.
• Supports professional development: For trainees, it's often a requirement for portfolio progression (e.g., ARCP) and demonstrates transferable skills in leadership, data analysis, and communication.
• Promotes sustainability and spread: A clear report can be instrumental in securing buy-in for sustaining changes or implementing them in other areas.

Practical Explanation: Key Elements of a QI Report

While there's no single mandatory format for all QI reports, particularly for local internal reporting, a common structure borrowed from scientific reporting often works well. The key is to be clear, concise, and logical.

1. Title

• Be specific: Clearly state what the project was about and its main focus. Avoid jargon.
• Example: "Reducing Delays in Discharge Summary Completion for Medical Inpatients at St Elsewhere's Hospital: A Quality Improvement Project."

2. Authors and Affiliations

• List all key contributors and their roles/departments. Include supervisors.

3. Abstract/Executive Summary

• A concise, standalone summary (typically 200-300 words) covering the entire project: Background, Aim, Methods, Results, Conclusion, and Key Learnings.
• This is often the only section busy readers will review, so make it impactful.

4. Introduction/Background

• The problem: Clearly define the issue your project addresses. Why was it a problem? What was the impact on patients, staff, or the system?
• Context: Briefly describe the setting (e.g., specific ward, department, trust).
• Evidence: Briefly mention any relevant national guidance (e.g., NICE, GIRFT), local data, or literature that highlights the problem and the need for improvement.

5. Aim Statement

• SMART: Specific, Measurable, Achievable, Relevant, Time-bound.
• Often expressed as: "We aim to [achieve what] by [how much] by [when] for [whom] in [where]."
• Example: "We aim to reduce the proportion of discharge summaries completed more than 24 hours post-discharge from 60% to 20% by 31st December 2024 for medical inpatients on Ward C, St Elsewhere's Hospital."

6. Methods

• QI Methodology: State the QI model used (e.g., PDSA cycles, Lean, Six Sigma, Model for Improvement). If using PDSA cycles, state how many and for what.
• Team: Who was involved in the project team?
• Measures: Clearly define the outcome, process, and balancing measures collected. How were they defined and collected? (e.g., manual audit, electronic health record extraction).
  • Outcome measure: What are you trying to improve (e.g., discharge summary completion time).
  • Process measure: Are the steps in the new process being followed? (e.g., daily ward round discussion of discharge planning).
  • Balancing measure: Are there any unintended consequences of the change? (e.g., increased junior doctor workload).
• Interventions: Describe the changes tested (the 'ideas for change' in PDSA cycles) in chronological order. Be specific about what was done, when, where, and by whom.
• Data Analysis: How was the data analysed and presented? (e.g., run charts, control charts, simple percentages).

7. Results

• Present your data clearly, typically using run charts or statistical process control (SPC) charts where appropriate. These are crucial for demonstrating change over time and distinguishing common cause from special cause variation.
• Describe the trends, any shifts, and specific points of interest on your charts. Link these to your interventions.
• State whether your aim was met.
• Use a narrative to explain what the charts show, but let the charts do most of the talking.

8. Discussion

• Interpret results: Explain what your findings mean in the context of your aim. Was the aim met? Why/why not?
• Learnings: What did you learn from the project, both successful and unsuccessful?
• Limitations: Acknowledge challenges, biases, and limitations (e.g., small sample size, short duration, Hawthorne effect).
• Comparison to literature/guidance: How do your results compare to existing evidence or national standards?
• Sustainability and Spread: How can the improvements be sustained? Are there opportunities to spread this change to other areas? What are the next steps?

9. Conclusion

• A brief summary of the main achievement and key take-home message. Reiterate whether the aim was achieved and the overall impact.

10. Acknowledgements

• Thank anyone who contributed significantly but isn't an author (e.g., IT support, ward clerks, audit department).

11. References

• List any cited literature, national guidelines, or resources.

Common Pitfalls

• Lack of clear aim: Without a SMART aim, it's hard to measure success.
• Poor data visualisation: Charts without clear labels, legends, or annotations make it difficult to follow the story.
• Confusing QI with audit/research: QI focuses on sequential small tests of change; audit measures compliance against standards; research aims to generate generalisable knowledge. Be clear which methodology you are applying.
• Insufficient detail on interventions: Vague descriptions make it impossible for others to replicate or learn from your methods.
• Not using run charts/SPC charts: These are the backbone of QI data presentation; simple bar charts or pre-post comparisons rarely tell the full story of change over time.
• Ignoring balancing measures: Focusing solely on the primary outcome can miss negative unintended consequences.
• Lack of reflection: A good QI report reflects on the journey, not just the outcome.
• Overly academic tone: While professional, a QI report should be accessible and practical, focusing on actionable learning.

Step-by-Step Approach to Writing Your QI Report

1. Start Early: Don't wait until the project is finished. Draft sections as you go (e.g., background, aim, methods).
2. Gather Your Data and Charts: Ensure all your data is analysed and visualised correctly in run or SPC charts.
3. Draft the Results Section First: Once your charts are ready, write the narrative for the results section, describing what the data shows.
4. Write the Methods: Detail exactly what you did, how you collected data, and the specific interventions tested.
5. Develop the Introduction and Aim: Clearly set the stage for your project.
6. Craft the Discussion: Interpret your results, discuss implications, limitations, and future plans.
7. Conclude: Summarise the key findings and impact.
8. Write the Abstract/Executive Summary: This should be the last thing you write, summarising all the key components.
9. Review and Refine: Read through your report, checking for clarity, conciseness, grammar, and consistency. Get feedback from colleagues or your supervisor.
10. Proofread: A final check for typos and errors.

Example in Clinical Practice

Imagine a junior doctor team on a busy surgical ward aiming to improve the timeliness of venous thromboembolism (VTE) risk assessment documentation. Their aim is: "To increase the proportion of surgical inpatients receiving VTE risk assessment documentation within 4 hours of admission from 70% to 95% by 30th September 2024 on Ward 7, St Elsewhere's Hospital."

Key sections in their report would include:

• Background: Highlighting national VTE guidelines, local audit data showing suboptimal compliance, and potential patient safety risks.
• Methods: Describing their use of PDSA cycles, team meetings, daily audits, and interventions such as a laminated 'VTE checklist' on admission trolleys, a new prompt in the electronic patient record, and a brief educational session for new starters.
• Results: A run chart showing an initial baseline of 70%, then a sustained shift upwards to 90-95% compliance following the introduction of the checklist and EPR prompt. They would highlight specific points on the chart corresponding to intervention deployment.
• Discussion: Reflecting on the success, attributing the improvement to the combination of interventions, noting challenges like staff turnover requiring repeated education, and discussing next steps such as integrating the checklist into the electronic admission form across the Trust. They might also include a balancing measure on junior doctor time taken for admissions, finding no significant increase.

How Lazomis Can Help

Lazomis can support your QI project reporting by providing a centralised platform for data collection, analysis, and visualisation. Our tools can help you:

• Standardise Data Collection: Create custom forms for efficient and consistent data gathering for your measures.
• Generate Visualisations: Automatically generate run charts and other relevant charts from your collected data, saving time and ensuring accuracy.
• Organise Project Documentation: Keep all your project artefacts – aim statements, PDSA cycle details, meeting notes, and draft report sections – in one accessible place.
• Facilitate Collaboration: Share project progress and data visualisations with your team and supervisors, gathering feedback for your report.

This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.