Reviewer responsibilities
Reviewers evaluate whether a change is safe, well-supported, and ready. They must understand why the change exists, what systems it touches, what risk it creates, what safeguards are required, and whether evidence is complete.
Start from My Approvals
Use the My Approvals queue to surface changes that require your action.
What to review first
Review in order: change summary, systems and domain, Revenue Impact Report, Coordination Plan rationale, evidence checklist, timeline.
Reading the Revenue Impact Report
The report helps reviewers understand risk level, failure modes, impact areas, and required safeguards.
Reading the Coordination Plan
The plan answers why you were included, who else was suggested, what evidence was expected, and what blockers exist.
Evidence enforcement
If required evidence is missing, approval may be blocked. Typical issues: rollback plan missing, monitoring plan not provided, validation incomplete.
Important
Reviewers should not treat approval as a substitute for missing evidence. Evidence and approval reinforce each other.
Approve or reject
Approve when the change is understood, evidence is sufficient, safeguards are appropriate, and risk is acceptable. Reject when evidence is incomplete, the change is poorly scoped, or safeguards are inadequate.