# Outcome Document

The auditable record of what a project achieved, anchored to a control-in-place and a named measurement owner.

## Why the CCAR-P exam tests this

The exam tests whether an outcome is actually verifiable — with a real control and an owner — versus a claim that measured the wrong thing.

## Definition

An **outcome document** states what was delivered and proves it. To hold up, it needs two things: an **auditable control-in-place** — a mechanism someone can inspect that shows the outcome is real and durable — and a **named measurement owner** — a specific person accountable for how the result is measured and reported.

The classic failure is the **"measured the wrong thing" trap**: the document reports a metric that moved but does not evidence the outcome that mattered. Latency improved while the user-facing error the project existed to fix went unmeasured. Without a control-in-place, the claim is unfalsifiable; without a named owner, no one is accountable when the measurement drifts.

A strong outcome document ties each claimed result to (1) the `control` that keeps it true, and (2) the `owner` who watches the number. It is the artifact that lets a stakeholder audit success months later without re-litigating the whole project.

## Exam trap

An outcome that cites an impressive metric but names no control and no measurement owner is the trap — a moved number is not a verified outcome.

## Commonly confused with

- **stakeholder-sign-off** — Sign-off is agreement to proceed or accept; the outcome document is the evidence that acceptance can be audited against.
- **migration-parity-eval** — A parity eval proves equivalence before cutover; the outcome document records results after delivery.

## Related

- stakeholder-sign-off
- migration-parity-eval
- signal-triage

---

Source: Claude Cert Prep — an independent, unofficial CCAR-P study resource (domain P6). Not affiliated with Anthropic.