Where this offering fits
Consent management should preserve the relationship between a person’s choice, the stated purpose and the processing systems that act on it. It is different from keeping a marketing contact list. Consider this scope when choices change across websites, applications and business channels and the organisation needs a traceable way to propagate those changes.
Architecture and rollout decisions
Inventory collection points and the language or notice version presented at each point. Identify which purposes actually rely on consent under the organisation’s approved legal analysis. Define how a withdrawal reaches dependent systems and how exceptions are reviewed. In the pilot, follow a synthetic consent grant, update and withdrawal from intake through the relevant application, retaining the agreed evidence of what was presented and when the choice changed.
An evaluation scenario for this offering
Use a fictional contact who grants one purpose, declines another and later withdraws the first. Follow those changes into the designated downstream application. Temporarily make the receiving system unavailable and review how the change is retried or escalated under the supported design. The evidence should distinguish the person’s recorded choice from the time every dependent system applied it. Include the notice version so later reviewers can understand what the choice referred to.
Evidence to request for this scope
- Agree purpose identifiers and the authoritative preference record across business channels.
- Verify integration behaviour when the receiving application is temporarily unavailable.
- Test how a changed notice or renewed choice is represented without overwriting necessary historical evidence.