Decision and scope
Record the business question, accountable owner, baseline, candidate change and interfaces in scope.
Write a decision that can be resolved by a bounded comparison. Identify the current baseline, the candidate change and the intended use of the conclusion. Include environments, interfaces and conditions that are excluded so the document cannot be mistaken for a broader assurance statement.
- Decision: what must this evaluation resolve?
- Scope: which environments and conditions apply?
- Exclusions: what is not represented?
Inputs and verification
List source snapshots, model versions, authored assumptions and independent acceptance assertions.
Separate observed inputs from authored assumptions and synthetic cases. Record source identity, relevant time, mapping or schema version, model revision and the scenario settings. Define assertions before the candidate run and identify who is responsible for their business meaning.
A decision linked to inputs, assertions, outcomes and review
State what the evaluation must resolve and who owns the answer.
- Evidence: source, timestamp, classification and version.
- Assertions: expected business and operational outcomes.
- Execution: workload, mode, budget and repeatability.
Review and next gate
Record results, exceptions, reviewer decisions and the evidence required for the next stage.
Record accepted, rejected and inconclusive results without collapsing them into a single success flag. Keep the reviewer identity, rationale, unresolved exceptions and limits of the conclusion. If the next step needs new evidence or a different approval, name that gate explicitly.
How would a capacity-change question become a reviewable contract?
State the supported capacity parameter, fixed workload, model identity and required business assertions. Identify which outcomes determine acceptance and which customer measurements remain outside scope.
The resulting package should let a reviewer trace a conclusion to its inputs and conditions. A reusable template is not evidence that the experiment itself has passed.
- Outcome: accepted, rejected or inconclusive.
- Exceptions: impact, owner and resolution condition.
- Next gate: deployment-specific qualification and approval.
Use a contract that survives a handoff
Another reviewer should be able to understand the evidence without access to the original conversation. Prefer stable identifiers and explicit descriptions over informal references such as “the latest run” or “the good dataset.”
The contract should travel with exported results. Keep the question, input pins, expected outcomes and review limits together. Do not include credentials or raw sensitive data merely to make the package appear complete; refer to the approved custody location where appropriate.
Fields that make the evidence usable
| Contract field | Useful entry | Avoid |
|---|---|---|
| Decision | A named change under a declared workload. | An unbounded goal such as “make it better.” |
| Input reference | Exact source, model and scenario identities. | An ambiguous reference to the latest data. |
| Acceptance | Independent assertions and accountable review. | A success threshold chosen after observing results. |
- Use exact versions and source references.
- Retain exclusions and dependence assumptions.
- Separate evidence references from secret material.
Track changes without rewriting history
A changed model, workload or assertion changes the context of the result. Preserve the earlier contract and outcome, then record what changed and why a new evaluation is needed.
A failed qualification remains part of the evidence even if a later candidate succeeds. Distinguish development refinement from independent evaluation and retain the acceptance conditions that applied to each result.
Keep the evidence and its conditions together. A later success does not erase an earlier failure or broaden the original scope.
- Version material changes to the contract.
- Retain failed and withheld outcomes.
- Do not silently retune the acceptance gate after observing results.
Complete the preparation worksheet
Use the editable fields below to draft the question, scope, evidence references and next gate. The text stays in this page session and is included in the downloaded resource.
This is a planning template, not an approval mechanism or a place for secrets. Bring the completed draft to the accountable reviewers and keep the eventual acceptance decision with the actual execution evidence.
Page-session draft. Included in your download. Use references rather than credentials or sensitive records.
Review preparation
0 / 6 prepared- Write one concrete decision.
- Identify the baseline, candidate and assertions.
- Name the reviewer and the next evidence gate.