What this is
What counts as a kaizen event, as distinct from an everyday improvement idea?
What counts as a kaizen event, as distinct from an everyday improvement idea?
A kaizen event is bounded to a defined week, run by a team released from their normal duties, against a single named process, with a baseline measured before anyone starts. An everyday improvement idea can be raised by anyone, at any time, and doesn't need a dedicated team or a measured before-state to exist. The event exists specifically to force the discipline the ad hoc idea doesn't require.
What is a baseline in this context, and why does it have to be measured before the event starts?
The baseline is the measured state of the targeted process before any change is made, captured in Baseline Value. It has to be measured before the event starts because a number written in afterwards, from memory of how things used to run, cannot be checked by anyone and stops being a measurement. Preparation exists as its own section specifically to force this ordering.
What does 'benefit sustained' scoring actually measure, as opposed to hitting the target during the event?
Target Achieved records whether the week's goal was hit on the day the event closed. Sustained At Follow Up records whether that result still holds thirty days later, once the team is back on normal duties and nobody is watching as closely. The scoring axis is the second one — a target hit on day five and gone by day thirty scores no better than one never hit at all.
Scope
When is a kaizen event record required?
This record is one step in the Continuous Improvement programme. Using it for work that belongs to a neighbouring template produces events with no measured baseline behind them, and results nobody can trust later.
Use this template when
- A dedicated, time-boxed event is being run against a single named process, with a team pulled off normal duties for it
- A baseline has been measured, or can be measured, before the team starts work
- The Continuous Improvement programme is the umbrella and this is the kaizen-event step within it
- The result needs to link forward into an Improvement Project record or a Standard Work record
- The workspace is being set up, or the kaizen-event register needs an entry added or retired
Do not use it for
- Problem Solving Record, which works a problem through background, current state, goal, analysis, countermeasures and follow-up on one page, with no dedicated event or released team.
- Continual Improvement Project Record, which runs a longer, more open-ended improvement initiative than a single bounded week can hold.
- Work Instruction Control Record, which controls the creation, approval, issue and withdrawal of a work instruction once the kaizen event has already decided what the new standard is.
- Idea to Implementation Tracker, which tracks a single improvement idea from the floor through assessment and decision, before it has earned a dedicated event.
- Anything outside KnowOps, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 9001 cl.10.3 requirements does this satisfy?
ISO 9001 cl.10.3 covers continual improvement in general terms; the sections below map that expectation onto the specific evidence the record actually captures, from preparation through to the follow-up.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.10.3 | Determine and select opportunities for improvement, with a defined baseline and target | Preparation |
| ISO 9001 cl.5.1.1 | Top management commits the resources an improvement activity needs | Preparation |
| ISO 9001 cl.10.3 | Implement the actions necessary to address the opportunity identified | During |
| ISO 9001 cl.9.1.3 | Analyse and evaluate data on process performance against the stated target | Outcome |
| ISO 9001 cl.7.5 | Retain documented information as evidence of the new way of working | Sustaining |
| ISO 9001 cl.7.2 | Ensure competence of the people who will operate under the new standard | Sustaining |
| ISO 9001 cl.9.1.1 | Evaluate the effectiveness of the improvement action at a defined follow-up point | Outcome |
What it does not cover
- Baseline Value entered after the event closes, which turns a measurement into a memory and cannot be defended if the improvement is ever challenged.
- Target Achieved marked Yes with no Result Value recorded, which leaves the claim with nothing behind it.
- New Standard Documented marked Yes with no linked Standard Work Record ID, which means the standard exists nowhere anyone else can find it.
- Thirty Day Follow Up Planned marked Yes with no Follow Up Due date set, which guarantees the follow-up never actually happens.
- Changes Trialled During The Event marked Yes and Changes Made Rather Than Recommended marked No, which means the event produced a list of suggestions instead of a kaizen.
Global
Kaizen Event Record requirements by country
ISO 9001 is a voluntary international standard rather than a statute, so what actually matters is which certification or hygiene regime a given plant sits under. The Area picklist on this record — cutting room, boning hall, pasteurising, culture room — points squarely at a food processing site, so that's the reach worth setting out.
ISO 9001:2015 cl.10.3
Certification auditors look for objective evidence that improvement opportunities were identified and acted on, not a policy statement that continual improvement happens somewhere in the business.
A kaizen event record with a real baseline and a dated follow-up is the artefact an auditor actually wants to see; a folder of workshop photos is not.
BRCGS Global Standard Food Safety — management commitment and continuous improvement
BRCGS audits expect a site to show it acts on trend data from its own quality and safety records, and a kaizen event tied to a measured process defect is exactly that kind of evidence.
Keeping Site and Area consistent with the plant's other food-safety registers lets one event stand as evidence in both the ISO 9001 and BRCGS audit trails.
Regulation (EC) 852/2004 on the hygiene of foodstuffs, Article 5
Article 5 requires HACCP-based procedures to be reviewed when a change is made to the process; a kaizen event that changes a cutting room or pasteurising step is exactly that kind of change.
New Standard Documented and Visuals Updated are the trigger for that HACCP review, not an optional extra once the change has already gone live on the floor.
How to complete it
How to complete a kaizen event record, step by step
Filling the form in correctly is the easy half. The harder half is the four judgement calls that decide whether the record can still be trusted months after the event has closed.
Baseline Measured Before The Event marked Yes should be checked against whether Baseline Value actually has a source — a count sheet, a timer, a logged reading — rather than a number someone wrote in from memory once the target already looked achievable.
Sustained At Follow Up is only meaningful if Follow Up Due passed and somebody physically checked the process again. A value entered on the day the event closed, before thirty days have passed, is a prediction wearing the record's most important field.
New Standard Documented and Visuals Updated being marked Yes needs checking against what's actually on the floor a week later, not just what was agreed in the closing meeting. A standard nobody follows was never really documented.
Transferable To Other Areas needs an actual look at whether the same waste exists elsewhere, not a reflexive Yes because it makes the event sound more valuable than a single-area fix.
What auditors find
Most common kaizen event record findings
The patterns below repeat across kaizen event records that don't hold up once someone checks them after the fact.
| Finding | Clause | What fixes it |
|---|---|---|
| Baseline Value and Result Value entered as round numbers on the same day the event closed. | ISO 9001 cl.9.1.3 | Require the baseline to be dated and sourced before Start, and open Result Value only once End has passed. |
| Target Achieved marked Yes while Sustained At Follow Up is left blank weeks later. | ISO 9001 cl.10.3 | Block closure of the Outcome section until Follow Up Due has passed and Sustained At Follow Up carries a value. |
| Operators On The Team marked No on an event about a process only operators run day to day. | ISO 9001 cl.5.1.1 | Make Operators On The Team a hold point for Sponsor sign-off, not just a scored field the facilitator answers alone. |
| Changes Made Rather Than Recommended left No because the team ran out of time and wrote up recommendations instead. | ISO 9001 cl.10.3 | Re-flag the event as problem-solving and route the recommendations into the Problem Solving Record instead of closing it as a kaizen. |
| New Standard Documented marked Yes with no Standard Work Record ID entered. | ISO 9001 cl.7.5 | Make Standard Work Record ID mandatory whenever New Standard Documented is marked Yes. |
| Thirty Day Follow Up Planned marked Yes but Follow Up Due left blank. | ISO 9001 cl.9.1.1 | Auto-populate Follow Up Due thirty days from End the moment Thirty Day Follow Up Planned is marked Yes. |
Case in point
Case in point: a baseline nobody could find
A packing line kaizen event closed with Target Achieved marked Yes and Improvement Percent showing twenty-two. Three months later, a customer audit asked for the source of the baseline figure, and nobody could produce it: the number in Baseline Value had been reconstructed from a supervisor's memory of 'about how it used to run', written in after the event because the facilitator wanted the record closed the same week it happened.
The event itself may well have improved something. What it couldn't do was prove it, because the one field that exists specifically to make the claim defensible — a baseline measured before the team started — had been filled in backwards. The fix wasn't more paperwork; it was refusing to open Start until Baseline Value already carried a number and a source behind it.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- OPS-033
- Archetype
- Record
- Record ID
- KAI-2026-000
- Scoring
- Benefit sustained
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.10.3
- Links
- Links Improvement Project and Standard Work
- Tags
- Improvement, Kaizen
- Sections
- 5
- Fields
- 56
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
16 fieldsEvent ID*
Auto sequence. Format KAI-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Event Title*
Area*
Process Targeted*
Start*
End*
Team Size*
Facilitator*
Sponsor*
Operators On The Team*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Enthusiasm Without A Baseline
A week of activity that feels productive and cannot be evidenced afterwards. The baseline has to be measured before the event, by somebody who will still be there to measure it after.
Preparation
6 fieldsProblem Defined Before The Event*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Baseline Measured Before The Event*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Target Set And Quantified*
- Yes3 pts
- Partly1 pt
- No0 pts
Scope Bounded To A Week*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Team Released From Normal Duties*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Sponsor Committed Resources*
- Yes3 pts
- Partly1 pt
- No0 pts
During
6 fieldsCurrent State Mapped With The Team*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Waste Identified By The Team*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Ideas Generated By The Team*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Changes Trialled During The Event*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Changes Made Rather Than Recommended*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Safety And Quality Assessed For Each Change*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Sustaining
6 fieldsNew Standard Documented*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Training Delivered*
- Yes3 pts
- Partly1 pt
- No0 pts
Visuals Updated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Measure Continued After The Event*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Owner Assigned For The Long Term*
- Yes3 pts
- Partly1 pt
- No0 pts
Thirty Day Follow Up Planned*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Outcome
22 fieldsBaseline Value*
Result Value*
Improvement Percent*
Target Achieved*
- Yes3 pts
- Partly1 pt
- No0 pts
Sustained At Follow Up*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Transferable To Other Areas*
- Yes3 pts
- No1 pt
Improvement Project ID
Links to CMP-051 Project ID
Standard Work Record ID
Links to OPS-035 Record ID
Follow Up Due*
Items Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Facilitator*
Signature*
Sponsor*
Second Signature*
OPS-033 · record IDs look like KAI-2026-000 · Links Improvement Project and Standard Work
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures one event. Keeping the baseline honest, chasing the thirty-day follow-up, and connecting the result to the standard it produced is the work an agent is built for.
Holds the kaizen event library against the site's process registers, chases the thirty-day follow-up automatically, and keeps the link to the Standard Work record current.
Picks up Safety And Quality Assessed and the new standard produced, and folds them into the site's wider quality management system evidence trail.
Tracks whether Training Delivered actually reached everyone on the affected shift, not just the team that ran the event.

Coordinates facilitator, sponsor and action owner across the event's lifecycle, and holds every write — baseline entry included — for approval before it lands on the record.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Kaizen Event Record definitions and key terms
- Kaizen
- A short, bounded improvement event run against a single process, with a dedicated team and a measured baseline, as distinct from an open-ended improvement project.
- Baseline
- The measured state of a process before a change is made, recorded so the size of any later improvement can be checked against it rather than estimated afterwards.
- Standard work
- The documented, current best-known way of doing a task, updated when a kaizen event changes it, and the reference point the next event starts from.
- Sustained benefit
- An improvement still holding at a defined follow-up point, as opposed to a result measured once at the end of the event and never checked again.
- Countermeasure
- A change trialled and adopted during the event to address a specific piece of waste identified in the current-state map, rather than a generic recommendation for later.
FAQ
Frequently asked questions about kaizen event record
How is a kaizen event different from a general improvement suggestion?+
A kaizen event is bounded to a defined week, run by a team released from normal duties, against a single process, with a measured baseline. A general suggestion can come from anyone at any time and doesn't need any of that structure — it belongs on the Idea to Implementation Tracker instead.
Who should measure the baseline, and when?+
Someone who will still be there to measure the process afterwards, and it has to happen before the event starts. A baseline measured by someone who moves on, or measured once the event is already underway, can't be checked or trusted later.
What happens if the team can't hit the target during the event week?+
Target Achieved has a Partly option specifically for this. Recording the honest result matters more than closing the record clean — a Partly result with a real baseline behind it is more useful than a Yes that doesn't hold up.
Does every kaizen event need a linked Standard Work record?+
Only when New Standard Documented is marked Yes. If the event didn't change how the process is meant to run, there's nothing new to document, and Standard Work Record ID stays blank.
What if the improvement doesn't transfer to other areas?+
That's a valid answer. Transferable To Other Areas exists to inform whether it's worth replicating elsewhere, not to grade the event — a fix specific to one line is still a legitimate kaizen.
How long after the event should the follow-up happen?+
Thirty days. Thirty Day Follow Up Planned and Follow Up Due exist as their own fields because that gap is exactly where a result quietly reverts once the team is back on normal duties.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Continuous Improvement
Improvement Suggestion Record
Captures an improvement idea from anybody, with what it would change and who could own it
Continual Improvement Project Record
Records a structured improvement project, from problem statement through measurement to sustained result
Lessons Learned Record
Captures what an event or project taught the organisation, in a form other areas can use
Problem Solving Record
Works a problem through background, current state, goal, analysis, countermeasures and follow up on one page
Work Instruction Control Record
Controls the creation, approval, issue and withdrawal of a work instruction, and confirms the people using it were briefed
Idea to Implementation Tracker
Tracks an improvement idea from the floor through assessment, decision, implementation and the benefit it delivered
More in Continuous Improvement
Problem Solving Record
Works a problem through background, current state, goal, analysis, countermeasures and follow up on one page
Work Instruction Control Record
Controls the creation, approval, issue and withdrawal of a work instruction, and confirms the people using it were briefed
Idea to Implementation Tracker
Tracks an improvement idea from the floor through assessment, decision, implementation and the benefit it delivered

Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 cl.10.3 — Continual improvement
- ISO 9001:2015 cl.9.1.3 — Analysis and evaluation
- ISO 9001:2015 cl.7.5 — Documented information
- BRCGS Global Standard Food Safety — Management commitment and continuous improvement
- Regulation (EC) 852/2004 — Hygiene of foodstuffs, Article 5 (HACCP-based procedures)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.