The Rounds Journal · Quality & improvement
How to write a healthcare quality improvement project charter
Turn a broad improvement idea into a short agreement about scope, ownership and measures.
Turn a broad improvement idea into a short agreement about scope, ownership and measures.
Name the process and scope
Describe the problem as it is currently understood. For a fictional outpatient office, focus on the completeness of appointment requests from one service rather than all access across the hospital. State which teams and processes are outside this first project.
Give the team a way to learn
Write the current baseline or identify who will collect it. Define completeness, set a review date and check whether a change creates extra processing time. Decide who owns the project, who can approve a change and who needs to be consulted.
Bring one page to the sponsor
Ask the sponsor to confirm the scope, available time and escalation route. Record open questions instead of filling them with guesses. At the first check-in, review whether the problem statement still matches what the team is seeing.
A one-page charter example
A fictional clinic office receives incomplete requests from one team. The proposed project will review that team’s new requests for four weeks. The coordinator will measure the share complete at first review and track minutes spent requesting corrections. The sponsor will confirm access and approve any trial. Existing requests and clinical triage sit outside the scope.
Write the aim after reviewing the baseline
If ten of 30 requests are incomplete, confirm what counts as incomplete and whether the sample is representative. Discuss a realistic target and deadline with the people doing the work. If the baseline is unknown, make baseline collection an explicit first task.
Set the meeting and decision dates
Record who prepares the baseline, who checks the definitions, when the first test can begin and when the sponsor will review it. Note any dependencies such as approval for a new form. Use the review to decide whether to continue, change direction or close the project.
Make the problem statement clear enough for someone else to test
Start with the process and the observation that prompted the project. In the fictional request example, a reviewer has to return some forms because the preferred contact route is missing. Identify who reported it, which requests you looked at and when. If you only have examples, write that the baseline still needs checking. Do not assume why people leave the field blank until you have heard from those who complete and review the form.
Ask the sponsor to confirm the scope in practical terms. For a four-week review, decide when the clock starts, how to handle requests submitted before the trial, and whether to include resubmissions. Name the team whose requests will be studied. If the team is not authorised to change the form itself, the charter can support an approved observation or a trial of an existing review process while a wider change is considered.
Write the definitions and decision in the same document
For a first-review completeness measure, count each in-scope request once. Make the denominator all in-scope requests checked during the period and the numerator those that meet the agreed definition at first review. Record which fields are required and who applies the definition. If a request is returned and submitted again, keep that second submission visible as rework without counting it as a new request in the original measure.
Choose a second measure that could reveal a cost the headline result hides. For instance, staff may spend more time checking forms even if they return fewer. Decide how to sample that time and when to ask staff about the effect. Agree the decision the team will make at the end of the test: continue, adapt, repeat with better measurement or stop. Set a review date and decide who has the final say.
Use the charter during the project
At the first meeting, read the aim and the scope aloud. Invite anyone who will do the work to point out an exception or missing responsibility. Be clear about who coordinates the trial, who has access to the data, who can approve changes and how concerns are raised. If two people believe the other owns a task, settle that before the test starts.
At each review, compare what happened with what the charter expected. If another team asks to join halfway through, pause to decide whether that changes the scope or makes the results harder to interpret. Record the approval and effective date for changes. When the project closes, add what the team learned, which decisions were made and who will own any continuing work.
A short checklist for the sponsor
- Can a colleague identify which requests the project covers and which it excludes?
- Can the person collecting the measures explain how each will be calculated?
- Do the people testing the change have the time, supervision and relevant approvals?
- Does the charter say what could lead the team to change or stop the test?
- Is there a calendar date and a named owner for the review?
Use the answers to finish the document. Keep it within reach while the work is underway so it can help the team resolve decisions rather than sit in a folder after approval.