Make consent monitoring a concrete client deliverable
The CMP handles the choice. An independent check examines what the website actually does. Use this workflow for a scoped review or maintenance agreement without promising GDPR certification.
1. Agree the scope
Select public pages and who will assess the findings. Explain that authenticated content, server-to-server traffic and legal assessments are outside browser-scan coverage.
2. Establish the baseline
Run a paid consent test, retain the report link and agree which signals need investigation. A free scan is an inventory, not the complete consent test.
3. Follow up
Give the developer a concrete observation, supporting evidence and an expected recheck outcome. Do not mark an observation fixed merely because it was reviewed.
4. Deliver before-and-after evidence
Repeat the check after the change and share dated observations. Different test conditions or incomplete checks must be explained as uncertain, not passed.
5. Continue weekly
Let automatic monitoring follow active sites. Review change alerts and failed checks even when the customer has not commissioned a new audit.
A simple deliverable
Scope and date → key observation → source and report link → implementation change → recheck and limitations → continued monitoring. Agree price and responsibility with the client; do not promise a particular income or time saving.