Processes

What. Versioned business processes (one process row, many process versions). Each version has a turtle/SIPOC structure, owner, KPIs, linked documents, and the same approval chain pattern as documents. Where. /processes

Why processes are versioned

A "process" is a long-lived thing (e.g. Vendor Onboarding). A process version is a snapshot of that process at a point in time - inputs, outputs, KPIs, owner, linked controls. When you change the process you create a new version, run it through approval, and publish it. The old version becomes obsolete.

Lifecycle

Draft  →  In Review  →  Approved  →  Published
                                          │
                                          └──▶  Obsolete (when next version publishes)

Same shape as documents, with one extra superpower: export to Excel "Process Manual".

Create a process

1. Side nav → Processes → New Process.
2. Fill Code (e.g. DGO-04-03), Name, Owner, Department.
3. Optional: Review Frequency (days) - when set, Next Review Date auto-fills as today + N days.
4. Click Save.

You land on the detail page with v1.0 in Draft.

Edit a version

The Process editor has 6 tabs:

• Overview - code, name, owner, department, dates.
• Turtle / SIPOC - Inputs / Outputs / Suppliers / Customers / KPIs.
• Steps - ordered procedure steps with text + role + tools.
• Documents - attach controlled docs (refers to the docs in /documents).
• Risks / Controls - link to risks and the controls that mitigate them.
• CAPAs - open CAPAs against this process.

Edit any tab → Save.

Submit for approval

1. Click Submit for Approval on the version.
2. The chain resolves in this order: chain assigned to this process → chain assigned to its department → fail with "No chain assigned".
3. The chain materializes into approvals rows for the version.
4. Status flips to In Review.

Approve / reject

Same UX as documents:

• If you're the current pending approver, the Approve and Reject buttons appear at the top of the version detail.
• Click → comment dialog → submit.
• When all steps approve, status auto-flips to Approved and a Publish button appears.

Publish

Click Publish → status = Published, published_at set, is_current_published=true. Any prior published version becomes Obsolete.

The published version is what every other module references when they say "linked process" - gap analysis, process manual export, audit checklists.

Process Manual export

The Process Manual is a multi-sheet Excel workbook: one cover sheet, one sheet per department listing its processes, plus optional per-process detail sheets.

1. Open /processes.
2. Click Export Process Manual (top right).
3. The Edge Function export_process_manual runs and downloads <org>_processes_<yyyy-mm-dd>.xlsx.

Use this to share the IMS picture with auditors or new hires offline.

Test it

• Create a process with code, name, owner, and a department that has a chain.
• Set Review Frequency to 90. Next Review Date auto-fills 90 days from today.
• Save the process. v1.0 (Draft) shows on the detail page.
• Edit the Steps tab, add 2 steps, Save.
• Click Submit for Approval. Status flips to In Review and Approvals tab shows the chain steps.
• Approve through every step. Status auto-flips to Approved.
• Click Publish. Status becomes Published. Prior version (if any) flips to Obsolete.
• From /processes, click Export Process Manual and verify the .xlsx downloads with the correct department sheets.
• Pasting a process URL on a different org rejects with "Wrong organization".