Kaizen Charter Template and Example
Agree the problem, goal, scope, team and follow-up before the event.
Example loaded: Press 4 changeover event.
Filled boxes are tinted. Click a box to go to it.
Get the Plant Floor Briefing: one free template like this every 2 weeks
One guide, one free tool, one problem fixed. Every 2 weeks by email. No spam, unsubscribe any time.
How to fill out a kaizen charter
- Pull the baseline first. Get two to four weeks of real data for the metric you want to move. A charter without a baseline cannot prove the event worked.
- Write the problem as a gap. Current number, required number, and what the gap costs: hours, dollars, overtime or late orders.
- Set one primary goal. A number with a direction and a target. Add one or two secondary goals at most, plus a safety goal.
- Draw the boundaries. List what the team may change and what is off limits, especially money, other areas and systems.
- Pick the team. The people who do the work every day, someone from maintenance or quality, and one fresh pair of eyes from outside the area.
- Plan the 90 days after. An owner and a date for each check. This is where most kaizen gains are lost.
- Get the sponsor to sign. Review the charter together two to four weeks before the event, so resources and data are ready on day one.
Kaizen charter example
A filled-in charter for a changeover reduction event on one press. The blank form above uses the same example as its hints. The 9.4 hours in the problem statement is 47 minutes × 12 changeovers a week = 564 minutes. See the SMED worksheet for the same press broken down step by step.
| Field | Example entry |
|---|---|
| Event name | Press 4 Changeover Reduction Kaizen |
| Sponsor / Facilitator | Plant manager / CI engineer |
| Team | Two press operators, a die setter, a maintenance tech, a production supervisor, and one person from outside the area |
| Problem statement | Average changeover on Press 4 is 47 minutes. At 12 changeovers a week, that is 9.4 hours of lost production. Demand needs 15 minutes or less to avoid weekend overtime. |
| Baseline | Average 47 min, range 32 to 68 min, 12 changeovers a week |
| Goal | Average 15 min or less, standard deviation 3 min or less, zero safety incidents |
| In scope | Press 4 changeovers, tool staging, die storage and transport, standard work |
| Out of scope | New equipment over $5,000, other presses, ERP and scheduling changes, building changes |
| Schedule | Day 1 observe and map, day 2 analyze, day 3 implement, day 4 trial and adjust, day 5 report out |
| Sustain plan | 30 days: weekly audit of the new standard work. 60 days: confirm the average is still 15 min or less. 90 days: sponsor review, then roll out to Press 2. |
Why this tool matters
Kaizen events fail when the team arrives Monday morning and spends the first day arguing about scope. The charter prevents this. It locks in agreement on what you're fixing, what success looks like, who's doing it, and what's off limits, before the clock starts. The sponsor signs off. The team can now spend 100% of event time improving, not debating.
Facilitator tip
Scope is the #1 killer of kaizen events. If you can't describe the scope in one sentence, it's too big. Split it into two events. A focused event that achieves its goal builds momentum. An ambitious event that fails to finish destroys trust in the process.
Frequently asked questions
What is a kaizen charter?
A one-page agreement, signed before a kaizen event starts, that states the problem, the measurable goal, the team, what is in and out of scope, the event schedule, and the 30-60-90 day plan to keep the gains. It stops the team from spending the first day arguing about scope.
What should a kaizen charter include?
The event name, sponsor, facilitator, dates and team members; a problem statement; the current state baseline and the target state goal; the event schedule; the success metrics; and a 30-60-90 day sustain plan. Each one is a field in this template.
Is there a kaizen charter example?
Yes. The template opens with a filled-in example so you can see what a finished charter looks like, field by field. Clear it with Start blank to write your own.
What is a kaizen project charter?
Another name for the kaizen charter: the one-page scope for a kaizen event or short improvement project. It states the problem, the measurable goal, the team, the schedule and how the gains will be kept.
Who fills out and signs the kaizen charter?
The facilitator drafts it with the process owner, using baseline data. The sponsor, usually the manager who owns the area and its budget, reviews and signs it. The team reads it on day one.
When should the kaizen charter be done?
Two to four weeks before the event. That leaves time to collect baseline data, free up the team members, and order any materials the event will need.
What is the difference between a kaizen charter and an A3?
The charter scopes a single improvement event before it happens. An A3 tells the whole problem-solving story on one page, from background and root cause through countermeasures and follow-up, and it can cover work that is not an event at all.
How big should a kaizen event scope be?
Small enough to finish in the event, usually three to five days. If you can't describe the scope in one sentence, split it into two events.