Business Process Fields

1. Description

• What it’s for: A description of what this business process does, who performs it, and what it produces.

• What to include:

  • Describe the activity in business terms — what happens, who is involved, and what the outcome is.
  • Focus on what the business does, not how the solution will support it — that traceability comes from the relationships.
  • Include context about when the process is triggered if it is not obvious.

• Example: "The Invoice Approval process is performed by the Accounts Payable team when a supplier invoice is received. The team validates the invoice against the purchase order and goods receipt, obtains manager approval for invoices above the threshold, and records the approved invoice for payment."

2. Customer Reference

• What it’s for: An optional external reference for this process in the customer’s own process register or documentation.

• What to include:

  • If the customer uses their own process numbering or naming convention, record it here to enable cross-referencing.
  • Leave blank if no external reference exists.

• Example: FIN-P-003

3. Level

• What it’s for: Classifies where this process sits in the process hierarchy, enabling structured decomposition from high-level areas to operational detail.
• Guidance:

• Use consistent level numbering across the project so that the hierarchy reads clearly in filtered views.
• Leave blank if level decomposition is not being used.

Relationships