💡 SOP Improvement Register

Register Code:    REG_SOP_IMPROVEMENT_V1
Owner:            Management / SOP Editors
Updated By:       Anyone may suggest; SOP owner/management approves
Frequency:        Ongoing
Last Updated:     2026-06-25

Purpose

Capture and track suggestions to improve any SOP. Anyone can suggest. Only the SOP owner or management can approve official SOP changes.

Columns

Date	SOP Name	Process Code	Suggested By	Current Problem	Suggested Improvement	Reason / Benefit	Photo?	Priority (Low/Med/High)	Status	Reviewed By	Review Date	Implementation Date	Remarks

Status values: Open · Under Review · Approved · Rejected · Implemented

Improvement Workflow

flowchart TD
A[Staff suggests improvement] --> B[Supervisor reviews]
B --> C{Valid suggestion?}
C -- Yes --> D[Send to SOP owner]
C -- No --> E[Close with reason]
D --> F[Owner approves]
F --> G[Update SOP + bump version]
G --> H[Mark implemented]

Rules

Tie every suggestion to a specific Process Code (e.g. REDSOIL_RECEIPT_V1).
A rejected suggestion must have a reason recorded.
When a suggestion is Implemented, bump the SOP version (e.g. _V1 → _V2) and update that SOP's Version and Last Updated.
High-priority safety/quality suggestions are escalated to Ram/Srinivasan immediately.

Automation Readiness

Telegram command: /improve
n8n workflow:     wf_sop_improvement_v1
Odoo object:      project.task (improvement backlog)
Supabase table:   sop_improvements
Status:           Future automation