Diagnosing Business-Value Gaps in Outcome Documents for the CCAR-P Exam

When a complete-looking document cannot do its job

This is the evaluate-level failure mode of the outcome document. You are shown a document that is accurate, detailed, and full of real metrics, and asked whether it can do the one job it exists for: justify expansion to a financial stakeholder. The CCAR-P exam wants you to diagnose the specific gap where a document reports only technical metrics and is missing the before-and-after business metric and its auditable control. The document looks finished and is useless for its actual purpose.

The trap is that the metrics are genuine. Volume, latency, and error rate are all worth tracking and all correctly measured, so a reviewer scanning for errors finds none. The gap is not an error; it is an absence of a different kind of metric, the one that answers "what was this worth?" rather than "does it run?"

Runs versus worth

The distinction the whole knowledge point turns on is between demonstrating that a system runs and demonstrating what it was worth. Forty thousand requests a month, sub-two-second latency, and a sub-half-percent error rate all demonstrate that the system runs. None of them say anything about the business outcome the deployment targeted. If the use case was to cut claims-processing time, the document needs the claims-processing time before and after, not the request volume. A document that reports only the runs-metrics has measured its own operation and skipped the thing the sponsor came for.

The CFO's first question

The failure has a canonical shape. A sponsor takes an outcome document, forty thousand requests a month, sub-two-second latency, error rate under half a percent, to their CFO to justify expanding the deployment. The CFO's first question is what the deployment saved or produced in business terms: what were claims-processing times before, and what are they now? The document cannot answer, because the two fields that would have made it usable, the before-and-after on the business metric and the auditable control behind the comparison, were never filled in. Without the before number there is no story; without the control the after number is an assertion. The document was complete as a technical record and useless as a case for expansion.

An after-metric without a control is not evidence

Even a document that includes a business after-metric can have the gap in a subtler form. If someone adds "claims-processing time down 40 percent" but names no auditable control behind it, the number is unverifiable, a business-sounding assertion the CFO has no reason to trust. The evidence-over-assertion discipline applies here exactly: an after-metric is only evidence when a named, inspectable control stands behind it. Diagnosing the gap therefore means checking both that the business before/after exists and that the after number has a control, not just that a value figure appears.

What the exam trips candidates on

The first trap is assuming a document full of real, correctly-measured technical metrics is automatically ready for an expansion conversation. The exam presents an accurate technical record and asks if it justifies expansion; the credited answer identifies that it measures operation, not worth, and is missing the business before/after.

The second trap is adding a business-sounding after-metric without an auditable control behind it, leaving the number effectively unverifiable. The exam offers a document with a value figure but no control, and rewards recognising that an uncontrolled after-metric is an assertion, not the evidence a financial reviewer needs.

Common misreadings to avoid

How this shows up on the exam

A scenario shows an outcome document and a sponsor who cannot answer a CFO, and asks what is missing. The reliable reading is that the document reports only runs-metrics and lacks the before-and-after business metric, and that even a stated business result is not evidence without an auditable control. Diagnose by looking for the business before/after and its control, not by re-checking the technical numbers.

This is the evaluate-level failure mode of the outcome document as a closing artifact, and it applies the control register's evidence-over-assertion discipline to a value claim. An outcome document with this gap is exactly what fails to gate the expand-or-iterate decision in lifecycle phase-gating.