Consent Flow Review Worksheet
- Assign one owner plus a backup before filling cells.
- Link each row to a system name—not a vague team name.
- Attach evidence (ticket IDs, screenshots policy) for audits later.
- Revisit quarterly or when vendors and flows change.
See also: Compliance portal · Official resources · Guides index
Use this worksheet to review how consent is requested, what users are told, and what happens after collection. The useful test is not whether the screen looks polished. It is whether the business can explain the flow clearly and reproduce what happened later.
Best owner
Usually product, growth, lifecycle, or founder-led teams.
- Involve design if wording or interface changes are needed
- Involve engineering if logging or evidence capture is weak
- Involve ops if requests or complaints often reference the flow
- Re-run this review after experiments, new forms, or campaign launches
How to use this worksheet
- Review one journey at a time: signup, checkout, lead form, webinar, demo request, or onboarding.
- Capture the exact user-facing text and screen order.
- Note what downstream systems receive the data and how the permission is honored.
- Log open fixes for wording, timing, defaults, or evidence gaps.
Worksheet prompts
- Where is the consent request shown?
- What exact language is shown to users?
- What purposes are tied to the flow?
- Are optional and necessary elements separated clearly?
- Can the team show what users saw at the time of collection?
- What happens in CRM, lifecycle, support, or vendor systems after submission?
Common failure points
- Marketing experiments changing text without updating internal records
- Form fields collecting more data than the team can justify operationally
- Suppression, withdrawal, or downstream syncing not behaving as expected
- Notice language, checkbox wording, and actual system behavior drifting apart
If you cannot show what a user saw at collection time, your team will struggle later when questions or complaints appear.