Title, summary, current state, proposed improvement, and expected benefit. An HSE report also records type, place, and risk. A kaizen record adds the before and after measure.
Core Capabilities
What It Delivers
Form fields, review steps, and roles meet in one screen set; no separate desktop program required.
Step names match your procedure. Each step leaves rationale on the record.
Employees open records. Unit managers and evaluators decide by step. HR runs the process and reward rules.
Questions and comments stay under the record; average star rating appears on the detail view.
Point balance and reward requests run in the portal; financial benefit and fixed-point rules are set in administration.
The logo is the organization’s own file. The screen language is Turkish or English. Staff sign in to their own organization.
How a Record Moves
Three Outcomes at Every Step
The form is submitted, lands on the evaluator’s task list, and closes with approval, rejection, or an implementation note on the file.
-
Accept
The record moves to the next step. The task appears on the next owner's list.
-
Revision
A note is required. The author corrects the text and sends it again. The record waits on the same step.
-
Reject
A reason is chosen from the list or written as a note. The record closes. The author can read the reason.
Work Areas
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
A Numbered Record Instead of a Box
An improvement idea, where it applies, and the expected benefit.
Module Details
Kaizen
Before and After on the Record
A small-step improvement, with a before and after measure.
Module Details
OHS
Near Miss Notice
Hazard, near miss, incident, and other occupational health and safety reports.
Module Details
Success Story
Outcome and Lesson Learned
Finished work, the period, and the result.
Module DetailsCapabilities
System Features
The record, the review, the notice, the reward, and the report live in one portal.
Suggestion, kaizen, near miss, and success story open from the same door. A draft has no number; once sent, the file receives a number, a unit, and an author.
Each step writes acceptance, revision, or rejection. The reason stays on the file, and the record lands on the next owner’s list.
Approved work is routed to the implementation owner. At close, the work done and the actual result are written on the same record.
The author is reminded of a similar record and a missing field. The reviewer sees a repeated topic before opening the file.
Task, decision, and revision notices follow the role. A step that does not concern the person does not open on their list.
Comments, questions, and noted handoffs stay on the record. Chat and the notice flow do not scatter; the reason sits in the file history.
The point rule is set by step and module. Approval and closing points land on the balance; the rule changes from administration.
The catalog shows the point price and the quantity left. Opening a request holds the points; rejection refunds them.
An open record on the same topic is shown while a new file is opened. The reviewer separates the repeat and links it to the existing file.
A closed file stays in the archive with its number, module, and result. The lesson learned is read from the success story.
How long a step has been waiting is read from the list. A task past its time rises on the owner’s queue.
Photos and documents stay attached to the record. Review does not scatter into email attachments; the file opens from the same record.
The menu follows the role and the open areas. Who sees a record and who writes the decision is read from one table.
Each organization’s records are kept apart. An unauthorized user does not see another organization’s file.
Screens are used with a keyboard and a reader. Focus, color, and target size follow the same order on the work screen.
Comments, questions, and stars stay on the file. The average is read on the record page; the discussion runs until close.
Filter by number, module, status, unit, and the person waiting. The record is not hunted by file name or in the inbox.
Status, module, and participation are read on a chart. The period list, close time, and point total come from the same report.
Steps, decision forms, roles, the catalog, and mail wording change without code. An existing record is not broken by that change.
Who changed what, and when, stays on the record history. The decision, the points, and a setting change are read from the same trail.
The organization announcement lands on the panel. The person who can publish manages the text. An announcement does not replace the record.
About the Suggestion System
Common Questions
Which record types does Suggestion System cover?
Suggestion, kaizen, near miss, and success story run in one portal. Near miss is a record type inside HSE. The lesson learned sits in the success story text. Form fields differ by area; review steps are shared.
Can review steps be changed?
Step names follow your procedure. Each step leaves rationale on the record.
How do reward points work?
Approved contributions earn points. Staff request items from the reward catalog; rules sit in administration.
Can an unused module be turned off?
Which record types are open is an organization setting. Unused modules do not appear in the menu.
What does the author do when revision is requested?
They read the note, correct the requested field, and send the same record again. A new record is not opened. The file waits on the same step.
Who can see a record?
The author sees their own record. Evaluators and managers see records on the steps their role covers. Another organization's records do not appear in the list.
Where do file attachments go?
Photos and documents attach to the record form. The review screen opens the same files. There is no separate folder to check.
How do multiple sites work?
Company, site, and unit are chosen on the record. Lists filter on those fields. Each site does not install a separate product.