The portal is one door. Suggestion, kaizen, and near miss are separate forms. Module choice sets the content and the reference prefix. Writing the same text on three forms mixes the reports. The first question is the type of event. HR writes which modules are open on the menu at setup; a closed module does not sit on the create screen. An unused type does not appear on the menu. Point rules for a closed module are hidden as well. The checklist is written into the period agenda.
A suggestion is an improvement idea not yet applied. Current state, proposed improvement, and expected benefit are written. Classification is the benefit type; there is no category field. Application comes later; after approval the implementation note enters the file. Work still at the idea stage belongs on the suggestion form. If a monetary estimate exists, the amount is tracked on the economic step. If place of application is empty, revision is asked. Expected benefit does not carry round praise. The dashboard total shows open and closed counts.
Kaizen is a small-step, measurable correction. Before value, after value, and unit of measure are required. Without a measure the reviewer asks for revision. If scope grows into a project, a separate suggestion or a separate record is opened; the kaizen form is not inflated. An unmeasured improvement sentence is not enough to close a kaizen. If units differ, the comparison is written separately on the file. The unit of measure is written in company language. Role decides the visible task row.
A near miss is an event that closes without injury. Place, hazard, and first action are written. Visibility defaults to internal. A permanent rail or procedure change is separate work; a suggestion or kaizen is opened when needed. Immediate action and permanent work are not mixed in one sentence. The hazard line is not left empty. Situation language is used instead of blame language. If internal is the only visibility option, the field is hidden. Step history carries a time stamp.
Near miss sits as a record type inside the HSE root module. It is not a separate root page. When HSE is open on the menu, near miss is part of that area. It does not share a reference prefix with the suggestion list. The HSE frequency table is read from this type filter; suggestion benefit type does not enter that table. The type filter is fixed on the period agenda. The branch filter keeps period comparison.
A success story is the period summary of finished work. It does not replace a suggestion or a kaizen. The source record opens from the reference. A lesson learned is read from the close note; it is not a separate journal application. The story does not carry text that is still at the idea stage. Measured result and place of application are written. Without a link, the source is sought in the period meeting. An attachment binds to the record.
Field guidance sits separately for the three forms in training. On a suggestion, place of application and benefit type are checked. On a kaizen, before-after measure and unit are checked. On a near miss, the place line is written at line, corridor, or rack level; workshop is not enough. Company is chosen, then branch; if branch is empty, period comparison shifts. In a holding structure the wrong company breaks the queue. In a holding structure company selection is required. A decision without rationale is not accepted.
Reviewer checks catch type error first. An unmeasured kaizen returns to revision. A suggestion with an empty benefit type is not advanced. A near miss missing place or hazard does not close. Rejection without rationale is not accepted. If the wrong module was chosen, the type error is written into the reason. A missing field stays named in the reason. If an attachment exists it is read from the attachment area. The menu hides a closed screen.
Common mistakes enter the period agenda. Writing a near miss on a suggestion. Forcing an unmeasured correction onto kaizen. Treating finished work as a new suggestion and skipping the success story. Splitting the same scene across three forms. These mistakes mislead participation and close time. The training note is renewed with sample records. The quality board counts wrong-module reasons once a month. If the count rises, training is repeated. The unit name is written in company language.
If the wrong module is chosen, the reviewer writes the type error into the revision or rejection reason. The reference number does not change; a new record opens in the correct module and the older file closes with rationale. Automatic type conversion is not the default; links and derivation are used only when the company has them on. Correction is tracked from the same person's task list. The reference number does not change.
A link between records is kept, for example when moving from suggestion to kaizen. If the target module is closed, the transition is hidden. A link does not mean the two files replace each other; it leaves a trail. A suggestion opened for permanent HSE work may carry the source near miss reference. Kaizen measure lines are written on the new file; they are not copied automatically from the suggestion. The checklist is written into the period agenda.
The task list filters by module. An HSE reviewer sees the near miss queue. Quality looks at suggestion and kaizen steps. Role does not open the wrong queue. A row without permission does not sit on the list. The due date is written when the task opens; the overdue badge looks at the same date. Reminders land in the portal inbox. Reminder and badge look at the same date. The dashboard total shows open and closed counts.
Training shows three examples side by side: a line-layout idea is a suggestion; a measured correction that cuts cycle time is a kaizen; an event that closes without a fall on a wet floor is a near miss. The same scene is not split across three forms. HR carries these three examples into the unit meeting. A new hire fills the three drafts in order in the first month. Role decides the visible task row.
Reporting opens with a module filter. Mixed form choice misleads participation and close time. The period meeting looks at module spread first, then drills into the unit row. A silent unit is zero records; no forecast sentence is produced. An audit asks for reference, step history, and rationale. Suggestion close count and near miss frequency are not summed. Kaizen measure average is a separate row. Step history carries a time stamp.
A point rule is written by module. Points for near miss are a company decision. Points on suggestion approval are a separate rule. A second rule does not run for the same person on the same record. When a catalog request opens, points are held; they finalize on fulfillment and refund on refusal. Points do not stand in for type choice. Without a rule the program is still tracked by closes. The branch filter keeps period comparison.
The demo portal may show the three forms with sample records; live production data is not in the sample. At go-live, unit, role, and open modules are rewritten. Demo rows do not move into the period report. Unused modules stay closed at setup. Price and calendar are clarified on the contact form. SSL protects sign-in and the form. At live setup sample rows are separated. An attachment binds to the record.
Quality and HSE carry separate agenda rows in the same period. Kaizen measure average is read separately. Success story count is the visible summary of applied work; it does not replace suggestion closes. The reference prefix keeps type separation on the list. Excel export depends on permission. A shared spreadsheet is not the source. A row without permission does not enter export. A decision without rationale is not accepted.
The form-choice card sits in a portal notice. Suggestion: idea, benefit type, expected benefit. Kaizen: before value, after value, unit of measure. Near miss: place, hazard, first action. Success story: summary of applied work and source reference. When the wrong card is chosen, the reviewer writes the type error into the reason. In the unit meeting the card is opened with a sample record. The menu hides a closed screen.
An audit verifies the field spine of the chosen type from a sample file. Excel carries the on-screen filter. A silent unit is seen with a separate filter per module. HR ties the training plan to those rows. Derivation without a link record creates source-search load in the period meeting; for that reason the source reference is written.
In short: an idea goes to suggestion, a measured correction to kaizen, an injury-free event to near miss. The door is the same; the form is separate. A success story is the summary of applied work. A wrong choice is corrected with rationale; the report is read from the module filter.