The kaizen form asks for a before value, an after value, and a unit of measure. The record is incomplete without those three fields. A small step may be a line layout, a label, or a single operation order. If the scope grows, a suggestion or a separate record is opened.
A suggestion is an idea not yet applied. Kaizen describes a measurable correction. The two modules do not replace each other. The reference code carries the kaizen prefix; in an audit it is separated from the suggestion list.
Quality reads the file from the measure line. Text length does not decide the case. A line stop is written in minutes, scrap as a rate, or maintenance time and cycle count as figures. The unit must be clear.
A loss seen at shift handover is written the same day; delay loses the measure. The reviewer confirms the before value on the floor. A mismatch is written into the revision reason. The after measure is entered after application ends. An early close breaks the report.
An approved kaizen closes. If the same correction will be repeated in another cell or branch, a new record is opened. The location field keeps repeats apart. A success story is the period summary of a closed kaizen; it is a separate module.
The cost-saving line writes the material or labor difference. A round sentence is not accepted. Competition is built from repeated kaizen that reduce defects reaching the customer. One large project is not expected.
HR lists kaizen counts by unit and month. Training need is read from that spread. A kaizen on the task list lands on the responsible person’s step. The decision stays on the record history.
A web-based record removes the board photo and the lost sheet. The file opens in the browser. Corporate identity is the same logo and color on the kaizen list as well.