Review the work against the agreement.

Each line points back to the proposal or the approved change, beside what was observed.

Scope reference	Illustrative review observation
EXHIBIT-PROPOSAL / Priority A	Request categories and ownership are clear; unassigned requests are visible.
EXHIBIT-PROPOSAL / Priority B	Status labels, handoff notes and routine-question guide match the agreed workflow.
EXHIBIT-CHANGE / weekly summary	Summary groups requests by category for the selected week; no matching requests shows an empty-state message.

Fictional review observations, not evidence of actual delivery or testing.

An empty week should still make sense.

The approved change had to explain an empty week, not show a blank page. The review checks that state too.

Concept preview · sample data

No requests match this week, with the selected dates stated.

Confirm the week and filters. An empty selection is a valid result, not a trend.

Fictional review observation. Not evidence of actual delivered software.

Who says it is done?

The owner or designated approver reviews the checklist and records acceptance. It follows the earlier approval of the extra work.

Before the extra work

Scope and privately agreed charge approved before added work began.

After the review

Delivered work accepted by the authorized client approver.

AI may organize review notes. It cannot accept work for the client.

Simulated acceptance. This page does not certify delivery or authorize payment.

Guides people can follow, a record of each decision and a named role for follow-up questions.

Review record

Practical guides

Follow-up

No unresolved in-scope item is shown in this fictional example. A new request is reviewed separately, not silently added.