Review steps load at setup. Review and close arrive as seed; HR adds the names from the company procedure. When the record is submitted it lands on the first step. The responsible person opens the record from the task list.
If a step is skipped, the record does not move. Order is the layout quality accepts. Approval moves the record to the next step or to close. Rationale can be required.
Rejection closes the file; the text the author sees is the reason for the decision. Revision returns the text to the author. The reference number does not change; the new version stays on the same file.
A review note is tied to the step. A comment is for discussion and does not stand in for the decision. The technical step reads feasibility. The economic step looks at the cost and benefit lines.
Manager approval is placed on records above the unit threshold. The branch manager closes the local step; the headquarters step is a separate order. The implementation note closes the work on the floor. A photo or measure is attached when it exists. An empty close is not accepted.
Step history answers who, when, and which decision. An audit asks for this list. When a reviewer’s leave or role changes, the open task moves to the new person; older notes are not deleted.
A notice lands in the portal inbox. The decision does not stay in an email body. A web-based screen removes the signature sheet and the scan chain. Suggestion, kaizen, and success story use the same layout.
A near miss flow can start with an HSE step; visibility remains internal. Corporate identity is the same logo and color on the task list as well. Staff do not see a foreign queue.