Guide · changed pages
Changed-page approval workflow for websites
When a website changes after sign-off, compare the new evidence with the approved baseline and send only materially changed pages back to the client.
Baseline
Capture the public pages in scope and store the desktop/mobile evidence, content hash and page-level decisions. This becomes the approved baseline.
Recheck
Run the same page list after a deployment. Compare the new capture with the baseline. A page can be marked unchanged, volatile-only, materially changed or failed.
Decision
Carry forward approval for unchanged pages. Mark changed pages as requiring reapproval. A reviewer can approve or request changes without creating an account.
Why this helps
- Small Pricing or copy changes do not reopen the entire handoff.
- Clients see exactly which page needs attention.
- Developers can use the same evidence contract in a release job or Playwright workflow.
Boundary: this is a screenshot-version evidence workflow. It does not certify the truth of page content or capture private logged-in pages.