Free Process Documentation Template
Document a whole process — SIPOC, flow, RACI and KPIs — the companion to your step-by-step SOPs.
Part of our free sop templates.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
1.Document Control
| Process Name | {{Process Name}} |
|---|---|
| Process ID | {{Process ID}} |
| Version | {{Version}} |
| Effective Date | {{Effective Date}} |
| Review Date | {{Review Date}} |
| Process Owner | {{Process Owner}} |
| Approver | {{Approver}} |
Keep this block on page one so the process can be governed and audited at a glance. Assign one accountable Process Owner and set a Review Date 6–12 months out — a process description is a controlled document.
2.Purpose & Objective
State in one or two sentences what this process exists to achieve and the outcome it delivers when it runs well.
Describe the result, not the steps — e.g. “to convert an approved purchase requisition into a paid supplier invoice accurately and on time.”
3.Scope, Trigger & Boundaries
Define where this process starts (the trigger) and where it ends, which departments and systems it spans, and what is explicitly out of scope.
Name the start and end events. A clear trigger and end point keep a process description from sprawling into adjacent processes.
4.Process Overview (SIPOC)
| Suppliers | Inputs | Process (high level) | Outputs | Customers |
|---|---|---|---|---|
| {{Who provides inputs}} | {{What is needed to start}} | {{Step 1 → 2 → 3 (summary)}} | {{What the process produces}} | {{Who receives the output}} |
SIPOC frames the whole process on one line: Suppliers, Inputs, the high-level Process, Outputs, and Customers. Fill it in before the detailed flow — it keeps everyone agreed on the boundaries.
5.Roles & Responsibilities
| Role | Responsibility in this process |
|---|---|
| {{Process Owner}} | {{Accountable for the process performing as designed}} |
| {{Role}} | {{What this role does in the flow}} |
| {{Role}} | {{What this role does in the flow}} |
Assign responsibilities to roles, not named people, so the process survives staff changes. The Process Owner is accountable; everyone else is responsible for their part.
6.Process Flow
| Step | Activity | Role | Input → Output | System / record |
|---|---|---|---|---|
| 1 | {{Triggering activity}} | {{Role}} | {{Input → Output}} | {{System}} |
| 2 | {{Next activity}} | {{Role}} | {{Input → Output}} | {{System}} |
| 3 | {{Decision or handoff}} | {{Role}} | {{Input → Output}} | {{System}} |
| 4 | {{Final activity}} | {{Role}} | {{Input → Output}} | {{System}} |
Document the end-to-end flow at the activity level — each row is a handoff between roles or systems. Note decision points (“if rejected, return to step 2”). This is the description of the process, not a click-by-click work instruction.
7.RACI Matrix
| Activity | Process Owner | Operator | Reviewer | Manager |
|---|---|---|---|---|
| {{Activity 1}} | A | R | C | I |
| {{Activity 2}} | A | R | I | C |
| {{Activity 3}} | A | C | R | I |
R = Responsible (does the work), A = Accountable (one per row, owns the outcome), C = Consulted, I = Informed. Replace the column headers with your real roles. Exactly one A per activity keeps accountability unambiguous.
8.Process Metrics (KPIs)
| Metric | Definition | Target | Frequency |
|---|---|---|---|
| {{Cycle time}} | {{How it is measured}} | {{Target}} | {{Monthly}} |
| {{Quality / error rate}} | {{How it is measured}} | {{Target}} | {{Monthly}} |
| {{Cost / volume}} | {{How it is measured}} | {{Target}} | {{Quarterly}} |
Pick a few metrics that show whether the process is healthy — typically a speed, a quality, and a cost or volume measure. A documented process you do not measure will drift.
9.Risks & Controls
| Risk | Control | Owner |
|---|---|---|
| {{What can go wrong}} | {{The check or control that prevents it}} | {{Role}} |
| {{Risk}} | {{Control}} | {{Role}} |
List the main risks and the control that mitigates each. This section is what makes the document audit-ready and useful for ISO 9001 or internal controls.
10.Related Documents & References
- {{Work instructions / SOPs that sit under this process}}
- {{Policies, forms, or upstream/downstream processes}}
Link the detailed SOPs, forms, and the upstream and downstream processes. A process description is the map; the SOPs are the turn-by-turn directions.
11.Revision History
| Version | Date | Author | Summary of change |
|---|---|---|---|
| 1.0 | {{Effective Date}} | {{Process Owner}} | Initial release |
| {{Version}} | {{Date}} | {{Author}} | {{What changed}} |
Update this table every time the process changes. The v1.0 row is pre-filled as an example.
12.Approval
Both sign-offs confirm the process is documented accurately and authorised for use.
A worked example documenting an end-to-end Procure-to-Pay (P2P) business process, with SIPOC, flow, RACI, KPIs and controls.
1.Document Control
| Process Name | Procure-to-Pay (P2P) |
|---|---|
| Process ID | FIN-P2P-01 |
| Version | 1.0 |
| Effective Date | June 1, 2026 |
| Review Date | June 1, 2027 |
| Process Owner | Head of Finance Operations |
| Approver | CFO |
2.Purpose & Objective
This process converts an approved purchase requisition into a paid, correctly matched supplier invoice — controlling spend, capturing early-payment terms, and keeping the ledger accurate.
3.Scope, Trigger & Boundaries
Triggered by an approved purchase requisition and ends when the supplier payment clears and the invoice is posted. Spans Procurement, the requesting department, and Accounts Payable across the ERP. It excludes vendor onboarding (FIN-VND-02) and employee expense reimbursement, which follow separate processes.
4.Process Overview (SIPOC)
| Suppliers | Inputs | Process (high level) | Outputs | Customers |
|---|---|---|---|---|
| Requesting dept, Procurement, Vendor | Approved requisition, vendor catalog, contract terms | Requisition → PO → goods/services receipt → 3-way match → payment | Purchase order, posted invoice, supplier payment | Vendor, Finance, requesting dept |
5.Roles & Responsibilities
| Role | Responsibility in this process |
|---|---|
| Head of Finance Operations | Accountable for the process performing and controls holding |
| Requester | Raises the requisition and confirms receipt of goods/services |
| Procurement | Issues and manages the purchase order against terms |
| Accounts Payable | Runs the 3-way match and schedules payment |
6.Process Flow
| Step | Activity | Role | Input → Output | System / record |
|---|---|---|---|---|
| 1 | Approve requisition and issue PO to vendor | Procurement | Requisition → Purchase order | ERP — Procurement |
| 2 | Receive goods/services and record receipt (GRN) | Requester | Delivery → Goods receipt note | ERP — Inventory |
| 3 | Receive invoice and run 3-way match (PO + GRN + invoice) | Accounts Payable | Invoice → Matched / exception | ERP — AP |
| 4 | If matched, schedule payment per terms; if not, raise exception | Accounts Payable | Matched invoice → Payment run | ERP — AP / Bank |
| 5 | Post payment and close the invoice | Accounts Payable | Payment → Posted ledger entry | ERP — GL |
7.RACI Matrix
| Activity | Finance Ops Head | Procurement | Accounts Payable | Requester |
|---|---|---|---|---|
| Issue purchase order | A | R | I | C |
| Confirm goods receipt | A | I | C | R |
| 3-way match & payment | A | C | R | I |
8.Process Metrics (KPIs)
| Metric | Definition | Target | Frequency |
|---|---|---|---|
| PO cycle time | Requisition approval to PO issued | < 2 business days | Monthly |
| First-pass match rate | % of invoices that 3-way match without exception | > 90% | Monthly |
| On-time payment rate | % of invoices paid by the due date | > 98% | Monthly |
| Cost of invoice processing | Fully-loaded cost per invoice | Trending down | Quarterly |
9.Risks & Controls
| Risk | Control | Owner |
|---|---|---|
| Paying for goods not received | 3-way match required before any payment | Accounts Payable |
| Duplicate or fraudulent invoice | Duplicate-invoice check + segregation of duties | Accounts Payable |
| Maverick (off-contract) spend | No PO, no pay policy; spend against approved vendors | Procurement |
10.Related Documents & References
- FIN-VND-02 Vendor Onboarding process
- AP-007 Invoice Exception Handling SOP
- “No PO, No Pay” policy
- Delegation of authority / approval matrix
11.Revision History
| Version | Date | Author | Summary of change |
|---|---|---|---|
| 1.0 | June 1, 2026 | Head of Finance Operations | Initial release |
12.Approval
How it works
- Preview the process documentation template, including the SIPOC, flow, and RACI sections.
- Download Word/PDF, or copy the text to paste into Google Docs.
- Map your process with SIPOC and the flow, assign a RACI, and set the KPIs and controls you will track.
Frequently asked questions
What is process documentation?
Process documentation describes an end-to-end business process: its trigger and boundaries, the inputs and outputs (SIPOC), the flow of activities across roles and systems, who is responsible (RACI), and the metrics and controls that keep it healthy. This template provides each of those sections, with a worked Procure-to-Pay example.
What is the difference between process documentation and an SOP?
A process description is the higher-level map of a whole process — how work flows across roles and systems from start to finish. An SOP (or work instruction) is the step-by-step detail for one task within that process. You usually document the process once, then link the detailed SOPs underneath it, which this template’s Related Documents section is for.
What is a SIPOC diagram?
SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers — a one-line summary of a process that frames its boundaries before you draw the detailed flow. It keeps everyone agreed on where the process starts and ends. The template includes a SIPOC table you fill in first.
What is a RACI matrix?
A RACI matrix maps each activity to roles as Responsible (does the work), Accountable (owns the outcome, exactly one per activity), Consulted, and Informed. It removes ambiguity about who does what. The template includes a RACI table with an R/A/C/I legend.