Risk acceptance lineage
Every accepted risk traced to who accepted it, when, and why.
Formula
Risk acceptance lineage completeness
(accepted risks with approver, rationale, timestamp, affected area, and review date / total accepted risks) * 100
Unit
percent
Direction
Higher is better
Cadence
Monthly for active risk portfolio.
Numerator
Accepted risks with complete lineage
Denominator
Total accepted risks
Worked Example
Review of accepted AI and platform risks.
Accepted risks
22
Risks with complete lineage
13
Calculation
13 / 22 * 100
Result
59.1%
Interpretation
Risk acceptance is not consistently accountable or auditable.
Recommended action
Require complete lineage before risk acceptance is valid.
Why it matters
This metric helps leaders see whether the governance layer is healthy enough to support execution and AI readiness.
What it reveals
Whether risk acceptance is accountable and auditable.
Manual assessment method
Review accepted risks and confirm each has a named approver, rationale, timestamp, and affected area.
Lapemo calculation path
Supported by risk signals, audit records, approvers, rationale, and resolution notes.
Interpretation Bands
Healthy
85-100%
Strong enough for normal operating review.
Watch
70-84%
Usable, but gaps should be assigned owners.
Risk
50-69%
Weak enough to slow execution or create risk.
Critical
<50%
Do not scale the related workflow without intervention.
Required inputs
- Accepted risk
- Approver
- Rationale
- Timestamp
- Affected area
- Review date
Data sources
- Risk register
- Governance workflow
- Audit log
- Control map
Common pitfalls
- Counting risk notes without approval
- Missing review dates
Recommended actions
- Complete missing lineage
- Assign risk review owners
- Escalate untraceable accepted risks
Measure Before You Scale
Measure the operating model before AI amplifies it.
Use the Metrics Library to understand what to diagnose, what to monitor, and where Lapemo can turn framework metrics into operating intelligence.