Documenting PDSA Cycles for Effective Quality Improvement

Why Effective PDSA Documentation Matters

Effective documentation of PDSA cycles is not merely an administrative task; it is fundamental to the success and sustainability of any quality improvement initiative. It serves several critical purposes:

• Capturing Learning: Each PDSA cycle is a mini-experiment. Documenting what was planned, what happened, what was learned, and what changes were made based on that learning is essential for continuous improvement. This prevents repeating mistakes and ensures insights are not lost.
• Demonstrating Impact: Well-documented cycles provide objective evidence of the changes tested and their effects. This is crucial for demonstrating progress to stakeholders, securing buy-in, and justifying resource allocation.
• Facilitating Communication and Spread: Clear documentation allows others to understand your improvement journey, replicate successful changes, or adapt them to different contexts. It fosters a culture of shared learning across departments and organisations.
• Supporting Governance and Assurance: For QI leads and governance teams, comprehensive PDSA documentation offers an audit trail of improvement efforts, demonstrating due diligence and a systematic approach to addressing identified issues. This can be important for CQC inspections, internal audits, and trainee portfolios.
• Informing Future Work: A detailed record of trials, successes, and failures builds an organisational memory for improvement. This invaluable resource can inform future QI projects, strategic planning, and education.
• Meeting Training Requirements: For junior doctors and trainees, documenting PDSA cycles is often a requirement for curricula and portfolios, demonstrating competency in QI methodology.

Core Elements of PDSA Documentation

While specific templates may vary, effective PDSA documentation typically includes several core elements, aligned with the four stages of the cycle:

1. Plan (P) Phase Documentation

This section sets the stage for your test of change. It should clearly articulate what you intend to do and why.

• Date of Plan: When the plan was developed.
• Cycle Number: Assign a sequential number (e.g., PDSA Cycle 1, 2, 3...) to easily track iterations.
• Aim of the Specific Test: A concise statement describing what this particular PDSA cycle intends to achieve (e.g., "To test if a pre-filled discharge summary template reduces transcription errors by 50% for patients on Ward X within one week"). This is distinct from the overall project aim.
• Prediction: What do you expect to happen when the change is implemented? Be specific and quantifiable if possible. What are the success criteria? (e.g., "We predict that using the template will reduce transcription errors from 10% to 5%.")
• Change to be Tested: A precise description of the change. What exactly will be different? (e.g., "Introduction of a standardised, electronic pre-filled discharge summary template for junior doctors on Ward X.")
• Who will carry out the test?: Identify individuals or teams involved.
• When and Where will the test happen?: Define the timeframe and specific location (e.g., "From Monday 1st to Friday 5th May, on Ward X during morning ward rounds.")
• What Data will be Collected?: Specify the measures (process, outcome, balancing) and how they will be collected to evaluate the test. (e.g., "Number of transcription errors per discharge summary, time taken to complete summary, feedback from doctors.")
• Responsible Person for Data Collection: Who will gather the information?

2. Do (D) Phase Documentation

This captures what actually happened during the implementation of the planned change.

• Date of Do: When the test was carried out.
• Observation of the Test: Describe the process of implementation. Did it go as planned? What challenges were encountered? What unexpected events occurred? Be factual and detailed. (e.g., "The template was introduced on Monday. Two junior doctors struggled initially with locating the template on the system. Training on template use was informal.")
• Data Collected: Present the raw or summarised data collected according to your plan. This might include simple tallies, counts, or qualitative notes. (e.g., "Number of errors: Day 1 - 3, Day 2 - 2, Day 3 - 1. Time to complete: No significant change observed. Feedback: Positive regarding structure, negative regarding system accessibility.")

3. Study (S) Phase Documentation

This is where you analyse the data and compare it to your predictions.

• Date of Study: When the analysis was conducted.
• Analysis of Data: What do the collected data tell you? Use simple charts, graphs, or statistical summaries if appropriate. Compare to baseline data if available. (e.g., "Average transcription errors reduced from 10% to 2% during the test period. Time taken to complete summaries remained stable. System accessibility was the main barrier identified.")
• Summary of What Was Learned: Did the change lead to the predicted outcome? Why or why not? What were the enablers and barriers? What new insights did you gain? (e.g., "The template effectively reduced transcription errors as predicted. However, poor system integration and lack of formal training hindered uptake. The change is technically sound but needs better implementation.")

4. Act (A) Phase Documentation

Based on your learning, what are the next steps?

• Date of Act: When the decision for next steps was made.
• Next Steps: What will you do next? This could be:
  • Adopt: Implement the change on a larger scale (if successful).
  • Adapt: Modify the change and run another PDSA cycle (most common).
  • Abandon: Discard the change and try a different approach.
  • Recommendations: Be specific about the next PDSA cycle (e.g., "Adapt the change: PDSA Cycle 2 will focus on improving system accessibility for the template and providing a brief, mandatory training session for junior doctors. Data collection will continue to monitor errors and include user satisfaction.")
• Responsible Person for Next Steps: Who is accountable for taking these actions?

Common Pitfalls in PDSA Documentation

Avoiding these common issues will significantly enhance the quality and usefulness of your PDSA documentation:

• Lack of Specificity: Vague descriptions of plans, predictions, or changes make it impossible to learn effectively. Be precise.
• Skipping Phases: Rushing through 'Do' without observation, or 'Study' without analysis, undermines the entire cycle.
• Not Documenting Failures: All cycles, including those where the change didn't work as expected, are valuable learning opportunities and must be documented.
• Ignoring Data: Relying on anecdotal evidence instead of collecting and analysing appropriate measures.
• Inconsistent Templates: Using varied formats or no format at all makes comparison and consolidation difficult. Standardise where possible.
• Delayed Documentation: Trying to recall details weeks after a cycle is complete often leads to inaccuracies and omissions.
• Over-complication: Keep documentation clear and concise; avoid excessive prose or unnecessary detail. Focus on the core learning.

A Practical Approach to PDSA Documentation

1. Choose a Standardised Template: Many NHS organisations and QI bodies (e.g., NHS England, Institute for Healthcare Improvement) offer excellent PDSA templates. Using a consistent template ensures all critical information is captured.
2. Keep it Concise: Use bullet points, short sentences, and clear headings. The goal is clarity and ease of understanding.
3. Document in Real-Time (or as soon as possible): The 'Do' phase observations and initial data collection are best captured as they happen or immediately afterwards. Don't wait until the end of the project.
4. Involve the Team: Encourage everyone involved in the PDSA cycle to contribute to the documentation, especially for observations and data collection. This ensures a comprehensive perspective.
5. Focus on Learning: Frame your documentation around what you learned. What surprised you? What worked well? What didn't and why?
6. Regularly Review and Share: Discuss documented cycles with your QI team, supervisor, or project lead. This provides opportunities for feedback, collective learning, and adjustment.
7. Store Centrally: Ensure all PDSA documentation is stored in an easily accessible, shared location (e.g., a shared drive, QI platform) so the entire team and future teams can access it.

Example in Clinical Practice: Improving Discharge Summaries

Project Aim: Reduce patient readmission rates by improving the quality and timeliness of discharge summaries.

---

PDSA Cycle 1: Testing a New Electronic Template

• P (Plan):

  • Date: 01/04/2024
  • Cycle #: 1
  • Aim of Test: To test if an electronic, standardised discharge summary template improves completeness (presence of 8 key data fields) for 10 patients on Ward C in 3 days.
  • Prediction: The template will improve completeness from 60% to 90% for tested summaries. It might take longer to complete initially.
  • Change: Junior doctors on Ward C will use a newly designed electronic discharge summary template for all discharges from 03/04/2024 to 05/04/2024.
  • Who: All junior doctors on Ward C.
  • Where/When: Ward C, during daytime shifts, 03/04-05/04/2024.
  • Data: Completeness of 8 key fields (patient ID, diagnosis, key medications, follow-up plan, allergies, main consultant, date of discharge, GP notified status) via random audit of 10 summaries; time taken for completion (self-reported); informal feedback from doctors.
  • Responsible: QI Lead Nurse, Dr. A. Smith.

• D (Do):

  • Date: 05/04/2024
  • Observation: The template was available. Junior doctors used it, but some reported difficulty finding it on the system. One doctor had not received the email with instructions. Overall adoption was moderate (6/10 summaries used it).
  • Data Collected:
    • Completeness (audit of 10 summaries): 80% (8/10 summaries had all 8 fields). The 2 summaries that didn't use the template had 50% completeness.
    • Time taken: Initial completion time increased by 5-10 minutes for those using the template for the first time.
    • Feedback: Positive on structure, negative on system accessibility and lack of formal brief training.

• S (Study):

  • Date: 08/04/2024
  • Analysis: The template, when used, significantly improved completeness from an average of 50% (previous baseline) to 80%. However, adoption was hindered by awareness and accessibility issues. Initial time taken to complete was slightly longer, but expected.
  • Learning: The design of the template is effective. The implementation needs refinement to ensure all staff are aware and can easily access it. The initial time increase is acceptable for the benefit gained.

• A (Act):

  • Date: 09/04/2024
  • Next Steps: Adapt the change. Plan PDSA Cycle 2 to address implementation barriers. This will involve:
    1. Creating a desktop shortcut for the template.
    2. Delivering a 15-minute 'lunch and learn' session on template use for Ward C junior doctors.
    3. Re-testing the template for 2 weeks on Ward C, monitoring completeness and self-reported time, and user satisfaction.
  • Responsible: QI Lead Nurse to arrange training; Dr. A. Smith to monitor template use and data collection.

---

This structured approach ensures that each test is a building block, contributing to the overall project aim and providing clear evidence for improvement.

How Lazomis Can Help

Lazomis offers integrated tools that can streamline and enhance your PDSA documentation efforts:

• Project Management & QI Workspace: Set up your QI projects within Lazomis. This provides a central hub for all project-related documentation, including a dedicated section for your PDSA cycles.
• Customisable PDSA Templates: Access digital, customisable PDSA templates within the platform, ensuring consistency across your team and projects. These can be tailored to meet your local requirements.
• Data Capture and Visualisation: Integrate your data collection with Lazomis features, allowing for direct input of measures from your PDSA cycles. Use the built-in dashboards to visualise your 'Study' phase data easily, tracking changes over time and against your predictions.
• Team Collaboration Features: Facilitate real-time collaboration on PDSA documentation, allowing team members to contribute observations, data, and insights directly, ensuring that the documentation is comprehensive and up-to-date.
• Reporting and Portfolio Integration: Generate structured reports from your documented PDSA cycles, suitable for stakeholder updates, governance meetings, or direct inclusion in trainee portfolios, demonstrating your QI competency.

Lazomis supports your QI journey by making the essential task of documentation more efficient, standardised, and impactful. This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.