Capability Template¶

Use this template for every Business Capability record.

YAML Front Matter¶

---
title: Capability Name
status: draft
owner: Owning Practice
version: "0.1"
last_reviewed: YYYY-MM-DD
business_value: One sentence describing the customer value created by this capability.
capability_id: PREFIX-NNN
owning_practice: Practice Name
accountable_digital_professional: Digital Professional Name
maturity_level: 1
tags:
  - business-capabilities
---

Capability ID¶

PREFIX-NNN

Capability Name¶

Replace with the business-readable capability name.

Why This Exists¶

Explain why this capability exists and what procurement business problem it solves.

Owner¶

State the owning Practice and accountable Digital Professional.

Business Value¶

Describe the business outcome this capability creates for the customer.

Definition¶

Define the capability as a stable business ability.

Scope¶

In Scope¶

TODO

Out of Scope¶

TODO

Capability Classification¶

Field	Value
Capability ID	`PREFIX-NNN`
Prefix	TODO
Capability type	Strategic, operating, enabling, governance, or platform
Owning Practice	TODO
Accountable Digital Professional	TODO
Customer visibility	Customer-visible or internal
Execution mode	Manual, assisted, automated, or learning
Criticality	Low, medium, high, or mission-critical
Current maturity	1-5
Target maturity	1-5

Required Capability Mapping¶

Mapping	Description
Practice	TODO
Digital Professional	TODO
SOP	TODO
Business Rules	TODO
APIs	TODO
Events	TODO
Data	TODO
UX	TODO
KPI	TODO
Business outcome	TODO

Relationships¶

flowchart TD
    Capability[Capability Name]
    Practice[Owning Practice]
    Professional[Digital Professional]
    SOP[SOP]
    Rules[Business Rules]
    APIs[APIs]
    Events[Events]
    Data[Data]
    UX[UX]
    KPI[KPI]
    Outcome[Business Outcome]

    Capability --> Practice
    Capability --> Professional
    Capability --> SOP
    Capability --> Rules
    Capability --> APIs
    Capability --> Events
    Capability --> Data
    Capability --> UX
    Capability --> KPI
    Capability --> Outcome

Dependencies¶

Dependency	Type	Direction	Impact	Owner
TODO	Practice, professional, SOP, rule, API, event, data, UX	Upstream or downstream	Low, medium, high, critical	TODO

Business Rules¶

TODO

Events¶

Event	Produced or consumed	Purpose
TODO	Produced or consumed	TODO

Data¶

Data object	Purpose	Memory impact
TODO	TODO	TODO

UX¶

Describe where the customer experiences this capability, such as Executive Office, Board Room, War Room, Proposal Studio, Compliance Centre, Marketplace, Academy, or Intelligence Centre.

KPIs¶

KPI	Definition	Target
TODO	TODO	TODO

Maturity Assessment¶

Level	Evidence
Current	TODO
Target	TODO

Governance¶

Field	Value
Review cadence	TODO
Approval status	Draft
Related decision records	TODO

Version History¶

Version	Date	Change	Approved by
0.1.0	YYYY-MM-DD	Initial draft.	TBD