Discrete ManufacturingFree templatePDF, Excel, Word exportDiscrete Manufacturing

Kaizen Event Charter Template (Rapid Improvement Event)

A kaizen event succeeds or fails before the first day, in the charter. This template turns the usual fuzzy request into a one-page agreement on the problem, scope, measure, team and schedule. Fill in the fields, export to PDF or Word, and get the sponsor's signature before the team assembles.

Fill in

Event title

Site and area

Executive sponsor

Event leader

Start date

End date

Problem statement

In scope

Out of scope

Primary metric

Baseline

Target

Team members

Constraints and risks

Gate

Live preview

Download:

Kaizen Event Charter Template

Kaizen Event Charter

Event: Reduce changeover time on CNC cell 4 Site and area: Plant 2, Machining, Cell 4 Dates: 2026-11-09 to 2026-11-13 Executive sponsor: Plant Manager Event leader: Continuous Improvement Lead Status: Charter draft

Problem Statement

Changeover on Cell 4 averages 95 minutes, causing batches of 800 pieces and 11 days of WIP between machining and assembly. Late orders to the assembly line occurred 7 times last quarter.

Scope

In scope: Setup process for the two CNC lathes and the tool presetter, from last good piece to first good piece.

Out of scope: Machine replacement, changes to customer drawings, ERP routing structure.

Objective and Measure

Metric	Baseline	Target
Changeover time (minutes)	95 minutes (average of 12 changeovers)	45 minutes or less
Safety incidents during event	0	0
5S score of area

Team

Setup technician, 2 operators, manufacturing engineer, quality technician, maintenance technician, planner

Constraints and Risks

Production must continue on Cell 3; budget for fixtures limited to 3,000 USD; customer deliveries cannot slip.

Event Schedule

Day	Focus	Output
Day 1	Train team, go to gemba, baseline data	Current-state measures and video
Day 2	Analyze waste, identify ideas	Prioritized idea list
Day 3	Trial and implement	Changes made and tested
Day 4	Standardize and measure	Updated standard work
Day 5	Report out	Presentation and 30 day action list

Approvals

Executive sponsor / Date

Event leader / Date

Area manager / Date

Finance (if spend exceeds limit) / Date

A charter should fit on one page. Keep the scope narrow enough to finish in the event window. Adapt wording to your site's improvement system.

Automate follow-up of improvement actions

Optional: ask how improvement actions can be tracked against ERP data and approvals.

Optional. The tool and every export work without this. No spam.

How to fill in the charter

Start with the problem statement and write it in facts: what happens, where, how often and with what effect. Avoid solutions in the problem statement. Choose one primary metric with a baseline measured before the event and a target the team can reach in a week. Name the scope boundaries in both directions, which prevents the event from drifting into a redesign. Pick a cross-functional team of five to eight people with at least two who work in the process every day.

One metric, one baseline, one target
Include operators who run the process, not only engineers
State what is out of scope to protect the event
Confirm the sponsor has released the team from normal duties

Structure of a typical five day event

Day one trains the team and establishes the current state at the gemba. Day two analyzes waste and generates ideas. Day three is trial and change, ideally with quick, low-cost fixes. Day four standardizes the new method and measures the result. Day five is the report out and the 30-day action list for items not finished. The schedule in the template follows this pattern, and you can compress it for a three-day event.

Making results stick

Many events produce a good week and then slip back. Counter this by writing the new method into standard work, updating ERP routings and setup times if they change, and scheduling a 30-day follow-up with the sponsor. Keep the open action list visible on an area board with owners and dates. Record the savings in the language finance uses, for example hours released or inventory reduced, and avoid claiming savings you cannot trace.

Common mistakes

Choosing a vague topic such as improve productivity, skipping baseline measurement, inviting too many people, and treating the event as a project that engineering will finish later are the usual causes of disappointing results. Another pitfall is leaving the sponsor out; without a sponsor, barriers such as maintenance support or quality approval stall mid-week.

Frequently Asked Questions

What is a kaizen event charter?

It is a short document that defines the problem, scope, goals, team, schedule and sponsor of a rapid improvement event. It aligns everyone before the event starts and gives leadership something to approve and review.

How long should a kaizen event be?

Most are three to five days. Smaller, well-bounded problems can be solved in two or three days. Larger flow redesigns may need a preparation week and a longer implementation period.

Who should sign the charter?

At minimum the executive sponsor, the event leader and the area manager. Add finance if spending is expected, and quality if the change touches validated or customer-approved processes.

Is a kaizen charter the same as an A3?

No. The charter plans an event and its scope. An A3 documents the thinking and results for a problem. Many teams use a charter to start and an A3 to report the outcome.

If your event results need to flow into ERP routings, setup times and standard costs, we can help automate those updates with approval steps.

Talk to an Expert Explore More Free Tools

Related Tools

Quality & Inspection

More Discrete Manufacturing tools

See all

Back to All Tools