Workflow and operations
What a consent record should contain
A consent record is only useful if it shows exactly what the consumer saw and agreed to. Here is what to keep.
Ironstark1 min read
When a consumer submits a form and agrees to be contacted, the business needs to be able to show that agreement later. A checkbox value in a database is not enough. The record has to show what the consumer actually saw.
The fields that matter
A usable consent record ties together the exact consent language displayed, the page it appeared on, the date and time of submission, the contact details entered, and the source that brought the consumer to the page. If the consent names the companies that may contact the consumer, the record should show that list as it appeared at that moment.
Version the language
Consent language changes. When it does, older records still need to point to the version that was live when they were created. Keeping each version with an effective date solves this.
Keep opt-outs with the record
An opt-out is part of the consent history. It belongs on the same record, with its own timestamp and channel, so every system that touches the contact sees it.
This article is general information, not legal advice. Requirements vary by channel and state, so confirm them with counsel.