If you already have a project in hand and just need to get your charter written correctly, this article is for you. A DMAIC project charter template is not just a form to fill out — it is the formal agreement between your team and leadership that defines what you are solving, why it matters, and how you will measure success. Get it right from the start, and every phase that follows becomes easier to execute and defend.
This article walks through each field of a real, filled-out Six Sigma project charter example — section by section. You will see concrete phrasing, tips for quantifying your business case, guidance on writing SMART goals, and examples drawn from manufacturing, healthcare, and government projects. No generic DMAIC overviews here. Just practical charter-writing clarity you can apply today.
Key Takeaways
- A DMAIC project charter is the core Define‑phase contract that aligns leadership, team, and expected results.
- Every charter field must be specific, quantified, and tied to a clear business impact.
- Problem statements describe the performance gap only, without causes or proposed solutions.
- SMART goal statements directly close the quantified gap with a time‑bound target metric.
- Tight scope, primary and secondary metrics, and defined tollgate dates prevent project drift and suboptimization.
The Full DMAIC Project Charter Template Structure
A standard DMAIC project charter template includes nine core sections. Each one serves a specific purpose, and skipping any of them tends to create confusion during tollgate reviews. Think of the charter as a contract — it commits leadership to resources and commits the team to results.
Here is the full structure you will work through in this article:
| Charter Section | Purpose | Common Mistake |
|---|---|---|
| Project Title and ID | Identifies and tracks the project | Too vague or missing project ID |
| Problem Statement | Describes the current performance gap | Including causes or proposed solutions |
| Business Case | Quantifies the financial and strategic impact | No dollar figure attached |
| Goal Statement | Sets a SMART, measurable target | Goal does not close the gap in the problem statement |
| Project Scope | Defines in-scope and out-of-scope boundaries | Scope too broad or undefined |
| Primary and Secondary Metrics | Tracks progress and guards against suboptimization | Only one metric listed |
| Team Roles | Assigns accountability and decision authority | No sponsor or champion listed |
| Milestones and Timeline | Sets DMAIC phase dates and tollgates | No tollgate dates; timeline too long |
| Risks and Constraints | Flags barriers before the project starts | Left blank until problems arise |
With the structure clear, the next step is understanding how to fill in each field with language that will hold up in a tollgate review.
How to Write a Six Sigma Project Charter: Breakdown with DMAIC Project Charter Template Examples
Each section of the DMAIC project charter template has a specific job to do. The examples below come from real project types across manufacturing, healthcare, and government settings. Use them as starting points and adapt the phrasing to your own data and process.
1. Project Title and Project ID
The project title should be descriptive enough to communicate the problem area without being a full sentence. Keep it to ten words or fewer, and include a unique project ID for tracking in your deployment system.
- Weak: "Quality Project"
- Strong: "Reduce Surgical Instrument Tray Error Rate — Q3-2024-MFG-017"
2. Problem Statement in a Six Sigma Project Charter Example
The problem statement describes what is wrong, where it is happening, when it was observed, and how big the gap is. It does not mention causes, and it does not propose solutions. That discipline is what separates a well-written Lean Six Sigma project charter template from a weak one.
- Weak: "We need to fix the billing errors caused by the outdated software system."
- Strong: "From January through June 2024, the accounts payable process at the Denver facility generated billing errors at a rate of 12.4%, against a target of 2.0%, resulting in an estimated $340,000 in rework and penalty costs."
Notice the strong version has a baseline, a target, a location, a time frame, and a financial impact. Every one of those elements matters during a sponsor review.
3. Business Case and COPQ in DMAIC Project Charter Fields
The business case answers the question: why does this project deserve resources right now? It connects the problem to a financial figure — typically the Cost of Poor Quality (COPQ) — and to a strategic priority. Sponsors approve projects based on this section more than any other.
- Include hard savings (scrap, rework, overtime, warranty costs) and soft savings (customer satisfaction, cycle time) separately.
- Tie the project to a current organizational goal or initiative where possible.
- Example: "Reducing the billing error rate from 12.4% to 2.0% is projected to recover $280,000 annually in rework costs and reduce customer dispute resolution time by 35%, directly supporting the Q4 cost reduction initiative."
4. Goal Statement That Is SMART and Time-Bound
The goal statement must close the gap described in the problem statement. It follows a SMART format: Specific, Measurable, Achievable, Relevant, and Time-bound. A goal that does not directly address the problem statement metric is a red flag in any tollgate review.
- Weak: "Improve billing accuracy."
- Strong: "Reduce the billing error rate from 12.4% to 2.0% or below at the Denver facility by December 31, 2024, as measured by monthly audit reports."
You might be wondering whether the target needs to close 100% of the gap. Not always. Closing 80% of the gap in a defined time frame is often more credible than promising full elimination with no supporting data.
5. Project Scope in a Lean Six Sigma Project Charter Template
Scope defines where the process starts and ends for this project. It also lists what is explicitly excluded. Tight scope boundaries prevent the team from drifting into adjacent problems that belong in separate projects.
- In scope: "The billing process from invoice generation to payment posting at the Denver facility."
- Out of scope: "Vendor contract negotiation, ERP system replacement, and billing processes at other facilities."
- Process start point: "Purchase order approval."
- Process end point: "Payment confirmation received from customer."
6. Primary and Secondary Metrics Across DMAIC Project Charter Fields
Primary metrics measure the problem directly — these are your Y variables. Secondary metrics guard against suboptimization, meaning they catch situations where improving Y1 accidentally damages another part of the process.
- Primary metric: Billing error rate (target: 2.0% or below)
- Secondary metric: Invoice processing cycle time (must not increase beyond current 4.2 days average)
- Secondary metric: Employee overtime hours in accounts payable (must not increase)
7. Team Roles and Decision Authority
Every charter needs named individuals, not just job titles. The sponsor approves resources and removes barriers. The champion provides strategic alignment. The Black Belt or Green Belt leads the project. Subject matter experts and process owners contribute domain knowledge.
- Sponsor: VP of Finance — approves budget and removes organizational barriers
- Champion: Director of Operations — ensures strategic alignment
- Project Lead (Black Belt): [Name] — leads DMAIC execution
- Team Members: Two accounts payable analysts, one IT liaison, one customer service lead
8. DMAIC Phase Milestones and Tollgate Dates
A realistic timeline shows sponsors that the team has thought through the work. Many DMAIC projects are scoped to finish within three to six months, depending on complexity and resource availability. Each phase typically ends with a tollgate review where the sponsor confirms the team is ready to move forward.
- Define complete and tollgate: Week 2
- Measure complete and tollgate: Week 6
- Analyze complete and tollgate: Week 10
- Improve complete and tollgate: Week 16
- Control complete and project close: Week 20
9. Risks, Constraints, and Dependencies
Listing risks upfront is not pessimism — it is planning. Common risks include data availability, resource conflicts, system access delays, and leadership changes. Identifying them in the charter gives the sponsor a chance to address barriers before they stall the project.
- Risk: Billing data prior to 2023 may not be accessible in current ERP system.
- Constraint: Team members are available 20% of their time for project work.
- Dependency: IT must complete system access configuration before Measure phase begins.
With each field explained, the next question is how real projects have used this structure to deliver results worth documenting.
Real DMAIC Project Charter Examples from Successful Six Sigma Projects
Seeing a filled-out charter from a completed project makes the template far more useful than any blank form. The examples below reflect real project types that have been executed using the DMAIC methodology across different industries.
Manufacturing
A manufacturing facility in the automotive supply chain used a DMAIC project to reduce first-pass yield defects on a stamping line. The charter's problem statement documented a 14.3% defect rate against a 3.0% target, with a COPQ of $520,000 annually. The goal statement targeted a reduction to 3.5% within five months. By the Control phase, the team achieved a 4.1% defect rate — not the full target, but a documented $380,000 in annual savings, which the sponsor accepted as a successful close with a follow-on project scoped for the remaining gap.
Heathcare
In healthcare, a hospital system used a Lean Six Sigma project charter to address patient discharge delays. The problem statement cited an average discharge time of 3.8 hours past the physician order, against a benchmark of 1.5 hours, affecting 42% of discharges and contributing to downstream bed availability issues. The team scoped the project to one medical-surgical unit and excluded the emergency department. The goal was to reduce average discharge time to 2.0 hours within four months. The project closed at 1.9 hours average, with a secondary metric showing no increase in readmission rates — a critical guard rail the team had built into the charter from day one.
These examples reinforce one consistent pattern: the teams that write detailed, quantified charters at the start spend less time defending their work at each tollgate. The charter does the alignment work upfront so the team can focus on analysis and improvement.
Courses That Support Strong Charter Writing and DMAIC Project Execution
Writing a strong charter is a skill that improves with structured training and practice. Air Academy Associates offers targeted programs that help belts define projects clearly, scope them correctly, and execute them with statistical rigor.
Whether you are writing your first charter or coaching a team through the Define phase, the right training makes a measurable difference in project outcomes. Here are four programs worth reviewing:
1. Project/Study Definition Short Course
This focused short course from Air Academy Associates is built specifically for the Define phase. It covers how to frame a problem statement, quantify the business case, and set boundaries that keep a project on track.
- Teaches the structure of DMAIC project charter fields in a practical, hands-on format
- Ideal for Green Belts and Black Belts preparing to launch a new project
- Covers scope definition, stakeholder alignment, and goal-setting techniques
- Designed for immediate application — bring your real project and leave with a draft charter
Learn more: Project/Study Definition Short Course
2. A3 Training Course
The A3 format is widely used in Lean environments as a one-page problem-solving and project definition tool. This course teaches practitioners how to use A3 thinking for chartering, scoping, and communicating project status to leadership.
- Complements the DMAIC project charter template with a visual, structured problem-solving format
- Helps teams communicate scope and progress on a single page
- Useful for Lean-focused projects where the A3 replaces or supplements the traditional charter
- Applicable across manufacturing, healthcare, and government settings
Learn more: A3 Training Course
3. Lean Six Sigma Green Belt Online Course
For practitioners who need a full belt-level foundation, the Green Belt online course covers the complete DMAIC methodology — including Define phase tools, charter writing, measurement system analysis, root cause analysis, and control planning.
- Self-paced format fits busy schedules without sacrificing depth
- Covers how to write a Six Sigma project charter as part of a full DMAIC curriculum
- Includes practical exercises tied to real project scenarios
- Prepares practitioners to lead improvement projects and present at tollgate reviews
Learn more: Lean Six Sigma Green Belt Online Course
4. Lean Six Sigma Black Belt Online Course
The Black Belt course goes deeper into statistical analysis, project leadership, and coaching skills. It is designed for practitioners who will lead complex projects, mentor Green Belts, and drive deployment-level results across an organization.
- Covers advanced DMAIC project charter fields and multi-phase project management
- Includes DOE, regression, hypothesis testing, and control chart analysis
- Builds the skills needed to coach teams through Define phase challenges
- Recognized certification pathway with competency and project-based validation
Learn more: Lean Six Sigma Black Belt Online Course
Common Mistakes in DMAIC Project Charter Fields and How to Fix Them
Even experienced practitioners make predictable errors when filling out a charter for the first time. Knowing these mistakes in advance saves significant time during sponsor reviews and tollgate approvals.
Problem Statement Includes a Cause or Solution
This is the most frequent error. Writing "due to outdated software" or "by implementing a new system" in the problem statement locks the team into assumptions before any data has been collected. Strip causes and solutions out entirely — those belong in Analyze and Improve.
Business Case Has No Dollar Figure
A business case that says "this project will improve customer satisfaction" without a financial figure rarely gets approved. Sponsors allocate resources based on return. Attach a COPQ estimate, even a conservative one, to make the case concrete.
Goal Statement Does Not Match the Problem Statement Metric
If the problem statement measures defects per million opportunities and the goal statement targets customer satisfaction scores, the charter is internally inconsistent. The goal must directly address the metric described in the problem.
Scope Is Too Broad for One Project
A scope that covers multiple facilities, multiple process streams, or multiple product lines is rarely completable in a single DMAIC cycle. Narrow the scope to what one team can control, measure, and improve within a defined time frame.
No Secondary Metrics Listed
Secondary metrics are not optional. They protect the business from solutions that fix one problem while creating another. Always identify at least one process metric and one output metric beyond the primary Y.
Timeline Has No Tollgate Dates
A DMAIC project without tollgate dates tends to drift. Sponsors lose visibility, teams lose momentum, and projects stall in Analyze. Set specific dates for each phase review from the start, even if they shift slightly during execution.
Wrapping Up Your DMAIC Project Charter with Confidence
A well-written DMAIC project charter template is the difference between a project that earns sponsor support and one that stalls before Measure. Fill in every field with data, specifics, and clear boundaries — and your charter becomes the strongest tool in your Define phase. Air Academy Associates has helped more than 250,000 professionals build exactly these skills through practical, results-focused training. If you are ready to strengthen your charter-writing ability and lead projects that deliver real results, explore the courses above or connect with our team to find the right program for your goals.
Air Academy Associates has trained 250,000+ professionals in proven Six Sigma methodologies worldwide. Their expert-led DMAIC certification programs give your team real-world charter skills that deliver measurable results. Get started today.
FAQs
What Is a DMAIC Project Charter?
A DMAIC project charter is a one-page document that defines a Six Sigma improvement project's purpose, scope, goals, and key roles. It aligns stakeholders early, clarifies what success looks like, and provides a clear "north star" for the Define phase through Control—an approach we emphasize in Air Academy Associates' Lean Six Sigma training and coaching.
What Should Be Included in a DMAIC Project Charter Template?
A strong DMAIC charter template typically includes: business case; problem statement; goal statement (SMART); scope (in/out); timeline and milestones; team roles (sponsor, champion, belt, SMEs); customers and CTQs; baseline performance and target; benefits (financial/operational); assumptions/constraints; risks; and required approvals. Including these elements helps ensure the project is measurable, feasible, and tied to business outcomes.
How Do You Write a Six Sigma DMAIC Project Charter?
Start by confirming the business need with the sponsor, then write a clear problem statement based on data (what, where, when, how big). Define a SMART goal tied to a primary metric, set scope boundaries to avoid "project creep," identify stakeholders and roles, and outline expected benefits and timing. Finally, review and secure sponsor approval—our instructors often recommend validating the charter against VOC/CTQs before moving deeper into Measure.
Where Can I Download a Free DMAIC Project Charter Template?
You can download free DMAIC project charter templates from reputable Lean Six Sigma training providers, professional quality organizations, and many internal continuous improvement offices. For example, Smartsheet, and various Six Sigma tool libraries publish charter templates that follow standard DMAIC structure and include sections for business case, problem statement, goals, scope, metrics, team roles, and risks. Air Academy Associates also offers project charter templates aligned with its Lean Six Sigma coursework and certification expectations.
What Is the Difference Between a Project Charter and a SIPOC in DMAIC?
A project charter defines the "why, what, and who" of the project (purpose, goals, scope, team, benefits, and timeline). A SIPOC is a high-level process map that defines "how the process works" by listing Suppliers, Inputs, Process steps, Outputs, and Customers. In DMAIC, the charter authorizes and frames the work, while the SIPOC helps clarify process boundaries and key handoffs early in Define.
Related Articles:
