Suggestion can arrive public. HSE stays inside the organization at opening. Kaizen and success story arrive off and enter the menu when opened.
Platform
Platform Modules
Each work area opens from its own form. The number, the list, the decision, and the points stay in the same layout.
Suggestion
ONR
On
A Numbered Record Instead of a Box
An improvement idea, where it applies, and the expected benefit.
- Title, summary, current state, and expected benefit share one form.
- A co-author can be added.
- On a suggestion, review passes all seven stops.
Kaizen
KZN
Off
Before and After on the Record
A small-step improvement, with a before and after measure.
- Before and after stay on the same file.
- The implementation note is written when the record closes.
- A closed record can earn reward points.
OHS
ISG
On
Near Miss Notice
Hazard, near miss, incident, and other occupational health and safety reports.
- Place and hazard cannot be left empty.
- The report is tied to the author's unit.
- Acceptance moves it to follow-up. An injury record is not this module.
Success Story
BSH
Off
Outcome and Lesson Learned
Finished work, the period, and the result.
- Summary, audience, and period are written.
- Co-authors stay on the file.
- The text can also earn points. Points land on the balance.
Shared Layout
One Portal, Shared Rules
The form changes by area. The list, the file, the decision, and the points layout stay shared.
The list, the record file, the review, and the task screen use the same layout in every area. A person who learns one area can read the next.
It is created on send. Suggestion starts with ONR, kaizen with KZN, an HSE report with ISG, and a success record with BSH. A draft has no number.
Approval moves the record on. A revision note is required and returns the record to the author. Rejection closes it with a reason.
Points depend on the rule in administration. Without a rule the record earns none. Severity, likelihood, and recognition are not points.
Suggestion
A Numbered Suggestion Record
A suggestion is written on the form, receives an ONR number, and enters the review order.
Record Fields
What A Suggestion Record Holds
The form asks for enough that the reviewer does not have to ask the same question twice. Every field below is on the portal form.
Title. Names the suggestion in one sentence. It shows in lists and in the inbox.
Summary. Short text read under the title in the record list.
Company. Required. In a holding, the record is tied to the right company.
Branch And Department. Shown when there is more than one branch or department. A single company or a single branch needs no choice. Location is information on the branch.
Benefit Type. Cost reduction, workplace safety, time saving, or quality. The list belongs to the organization.
Current State. How the work is done today.
Proposed Improvement. What should change.
Expected Benefit. What the change gains.
Implementation Notes. A note for whoever carries it out.
Suggestion Partners. Staff who contributed to the suggestion are added to the record.
File Attachments. A photo, drawing, or table is uploaded from the record page.
Visibility. Public can be chosen when the portal is public. When the record stays inside the organization, there is no choice.
Features
How A Suggestion Record Works
When a suggestion is a team’s work, contributing staff are added as co-authors and appear beside the author on the record page. A photo, drawing, or table is uploaded from the record page and downloaded from the same page.
Questions and comments open under the record page. A question is separate from a comment: “Which line could we trial this on?” is a question. Each question and comment is rated one to five stars, and the average shows beside the text.
If the organization has defined a point rule, the author receives fixed points on submission and on approval. Balance and movements show in the portal. Points are spent on a reward from the reward list and the request is recorded.
A new suggestion lands in the task list of the evaluator whose turn it is. Revision, rejection, and approval are sent to the author. If the organization’s mail template is on, the same event also goes by email.
Record Path
Which Steps A Suggestion Passes
A suggestion passes seven stops. Each stop records acceptance, revision, or rejection. The organization can turn a stop off. The person whose turn it is sees the record in their tasks.
-
Open The Record
The employee writes the title, the current state, and the proposed improvement. The record receives a number when it is sent.
-
Pre-Review
Scope, missing detail, and a duplicate record are separated. A thin text is sent back for revision.
-
Technical Review
Feasibility and the expected benefit are written.
-
Administrator Approval
The administrator looks at priority and the organization’s work.
-
Implementation Routing
The person who will carry out and follow the work is chosen.
-
Economy Approval
The estimated amount and the benefit reason are written on the record.
-
Implementation Follow-up
The realized result is written. The record closes. Points stay on the file.
Three Outcomes at Every Step
-
Approve
The record moves to the next step. At the last step the status becomes Implemented and the record closes.
-
Request Revision
A note is required. The author corrects the fields the step opens and resubmits.
-
Reject
One of the step’s reasons is selected, or a note is written. The record closes.
Every action is written to the History list on the record page: who, at which step, what they did, and their note.
Kaizen
A Measured Kaizen Record
The before measure, the after measure, the waste type, and the PDCA stage stay on one record.
Before · Before Metric
The current time, scrap, step count, or distance is written with its unit.
- Current State describes the work as it is today.
- Waste Type says under which heading the loss falls.
- The list filters by waste type.
After · After Metric
The value taken after implementation, or the target, is written the same way.
- The Implementation Notes field says what changed.
- Realized Amount is written at the implementation follow-up step.
- The author edits the record to update the measure.
Improvement Cycle
PDCA Stage And Waste Type
Kaizen repeats in small steps. The stage field shows which cycle the record is in; the waste type shows what is being reduced.
-
P
Plan
The problem and the target measure are written.
-
D
Do
The trial runs on the floor.
-
C
Check
The following measure is taken.
-
A
Act
The result becomes the standard.
PDCA Stage is a free text field. Write the stage name your organization uses.
Features
How A Kaizen Record Works
Before Metric, After Metric, Waste Type, and PDCA Stage are read in the Record Details section. The reviewer does not open an attachment to find the measure.
The estimated amount is written at the Economy Approval step and the realized amount at Implementation Follow-up. Both show in the flow panel on the record page.
A time sheet, before and after photo, or count table is uploaded to the record as an attachment. The reviewer downloads it from the same page.
How the measure was taken is asked under the record. Questions and comments are rated one to five stars.
Record Path
At Which Step The Measure Is Checked
A kaizen record passes the same review order as a suggestion. Each stop reads the before and after measure.
- 01 Pre-Review Are the previous measure and the current state readable. A revision is requested if not.
- 02 Technical Review Can the measure be taken. One of the rejection reasons is Missing Measure.
- 03 Administrator Approval Does the improvement fit how the organization works.
- 04 Economy Approval The estimated amount is written on the record.
- 05 Implementation Follow-up Realized amount and implementation note are written. The record becomes Implemented.
OHS
An HSE Report
Type, place, and risk are written on the HSE form. A suggestion is not opened from this form.
Report Type
Four Types, One Report File
The employee chooses the type first. The type decides which detail the form asks. The list filters by this type.
No event has happened yet. The source and the risk to be removed are written.
It closes with a preventive action.
The event happened. There was no injury or damage. Severity and likelihood are written apart.
The immediate action is on the record.
There was injury or damage. The form asks for the date, the immediate action, and an injury mark.
It does not replace a statutory accident file.
A dangerous physical condition on the floor: an open guard, a wet surface, a missing barrier.
The record stays open until the condition is corrected.
Near Miss
How An Event Without Injury Is Written
A near miss is not a separate menu. It is chosen as the type when an HSE report is opened.
Company, branch, and unit are chosen. The date of the event is written.
Each is a number from 1 to 5. The record reads them side by side. No automatic risk score is produced.
What was done on the spot is written: stopping the area, drying the floor.
The place can be attached. Do not put a person in the frame.
Action Class
Corrective, Preventive, Improvement
Every report carries an action class. The class says what the record is closing.
Removes a nonconformity that already happened.
Cuts a risk that has not happened yet, at the source.
Makes the present condition safer.
Review
From Report To Close
An HSE report follows its own order. Typical stops are first look, technical review, unit approval, and close. The days on a stop are an organization setting.
- 01 Report Type, place, risk, and current state are written. A number is given when the report is sent.
- 02 First Look The HSE owner checks whether the place and the action are clear. A thin report is sent back for revision.
- 03 Technical Review The lasting action, the unit that will carry it out, and the expected benefit are written.
- 04 Unit Approval The unit manager approves the action in their area, or returns it with a reason.
- 05 Close The implementation note is written. The record closes. Entry points, if a rule exists, post to the author.
Success Story
A Recorded Success Story
Audience, period, and outcome are written on the record. It passes review and becomes Implemented.
Record Fields
A Success Record Answers Three Questions
Beside title and summary, a success record carries three special fields. Each field is one question of the story.
-
01
For whom?
Audience
Which team, line, or customer group benefited from the improvement. Free text.
-
02
When?
Period
The month or year the improvement ran, written like “2026 First Half”.
-
03
What changed?
Outcome
The outcome text, written with its unit. A long text field.
Fields On Every Record
- Title
- Summary
- Company And Place
- Audience
- Current State
- Proposed Improvement
- Expected Benefit
- Implementation Notes
- Partners
- File Attachments
- Visibility
Visibility
One of two visibilities is selected when the record opens.
The record is visible only to signed-in members of the organization. This is the default.
If the portal is public, the record is also visible to visitors who are not signed in. The option appears on the form only when the portal is public.
Features
Appreciation, Questions, And Comments
Under a success record, members leave an appreciate mark, ask questions, and write comments. The appreciate mark is not added to stars; it is counted separately.
A one-tap mark on the record page. The count is visible.
Free text under the record.
Separate from a comment, such as “Have you applied this on another line?”.
1 to 5 per question and comment, with the average beside it.
Split
Where The Areas Split
What they share is the list, the file, and the decision. What splits them is the form, the number, the opening state, and the review order.
| Topic | Suggestion | Kaizen | OHS | Success Story |
|---|---|---|---|---|
| What Is Written | Title, current state, proposed change, and expected benefit. | Before measure, after measure, waste type, and PDCA stage. | Type, place, risk, and the action taken. | Audience, period, and result. |
| Number | ONR. Created on send. | KZN. Created on send. | ISG. Created on send. | BSH. Created on send. |
| Opening | Arrives on. | Arrives off. It enters the menu when opened. | Arrives on. | Arrives off. It enters the menu when opened. |
| Visibility | It can arrive public. Administration changes that. | It stays inside the organization at opening. | It stays inside the organization at opening. There is no anonymous report. | Once opened, the default is public. Administration can keep it inside. |
| Order | Seven stops. The economy stop records the amount. | The same order. Each stop reads both measures. | Its own order: first review, technical review, unit approval, and close. | The same order. The last stop sets the status to Applied. |
| Limit | A near miss is not opened from this form. | The measure is free text. The difference is not calculated. | The legal minutes and the investigation are not on this record. | There is no post to an outside network, no automatic announcement, and no printed board. |
Questions
About The Platform
Is a near miss a separate menu?
No. A near miss is a type of HSE report. The list filters by that type.
What happens to a module that is off?
Its menu, record, task, and notice stay hidden. When the organization turns it on, it uses the same portal layout.
How does a record number start?
Suggestion is ONR, kaizen is KZN, an HSE report is ISG, and a success record is BSH. The number is created on send.
Is review the same in every module?
Suggestion, kaizen, and success use the same order. An HSE report has its own order. A stop can be turned off. A record already in motion keeps the old order.
Which modules are on at opening?
Suggestion and HSE arrive on. Kaizen and success story arrive off and enter the menu when opened.
Who sees a record?
A person with access sees it. Suggestion can arrive public. HSE stays inside the organization at opening.
Are points mandatory?
No. Points depend on the rule in administration. Without a rule the record earns no points.
Do the forms mix?
No. Each module opens from its own form. What they share is the list, the file, the task, and the decision layout.
Going Live
Deployment Options
Cloud or company server. The address and where the data sits follow the setup. The record layout stays the same.