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.
Suggestion Module
A suggestion is written on the form, receives an ONR number, and enters the review order.
Record Fields
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.
Record Path
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.
The record moves to the next step. At the last step the status becomes Implemented and the record closes.
A note is required. The author corrects the fields the step opens and resubmits.
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.
Features
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.
Users
The same record reaches a different person at each step.
Write the problem seen on shift into the form, get the number, and follow the status in their own records.
Run the pre-review and technical steps as evaluators and write a revision note for thin records.
Approves suggestions for their own unit at the manager step, or returns them with a reason.
Enter the amount at the economy step and see role and point balance in the people directory.
Comparison
| Topic | Old Habit | This Module |
|---|---|---|
| Intake | The box is opened once a month and paper stays on a desk. | The suggestion arrives through the form, gets a number, and enters the review queue. |
| Answer | The answer is given verbally, or not at all. | Approval, revision, and rejection notes are written to History. The author sees them in the inbox. |
| Correspondence | The same suggestion circulates in three emails. | Questions, comments, and attachments stay on one record page. |
| Reward | Nobody remembers later who was given what. | The point movement sits in the Point Ledger, tied to its record. |
| Time | Nobody tracks how long a suggestion has waited. | The step’s days sit in the organization setting. A late record is marked. |
| Co-author | Names of people who helped stay on the side. | Co-authors stand beside the author on the record page. |
| Visibility | The box is either open to everyone or to no one. | Public or organization-only is chosen. If the portal is closed, there is no choice. |
| File | A drawing is lost in email. | A photo, drawing, or table arrives on the record file. |
| Order | Who will look is decided in the moment. | The published order is pinned to a new record. A stop can be turned off. |
| Repeat | The same idea drops into the box twice. | The list filters by title, place, and date. A similar record is found. |
Frequently Asked
Signed-in staff write. If the organization opens the portal to the public, people without an account can also send a suggestion through the guest form with a name and email.
Setup opens with seven stops. Step name, responsible role, and rejection reason follow the organization’s own order. A stop can be turned off. A record already in motion keeps the order it started with.
No. Points depend on the point rule set for the organization. Without a rule the record earns no points; the review flow works the same.
There is no number until it is sent. On send the record is numbered and the status becomes Submitted.
Points go to the author. Co-authors appear beside the author on the record page.
Yes. A photo, drawing, or table is uploaded from the record page.
A person with access sees it. A public record can be read without signing in when the portal is open to visitors.
No. A rejection closes it with a reason. A revision returns the same file to the author; no new file is opened.