Decision Notices
Show who was told, and what they asked for.
Decision Notices tracks which people were told an automated system was used in a decision about them, what they were told, and what they asked for afterwards.

What goes wrong
The rules moved from audits to notices and records.
California and Colorado both have automated-decision obligations with a 1 January 2027 date, as law firms report them. What remains after two years of amendments is mostly notice, explanation, human review and record keeping.
A notice after an unfavorable outcome
Records kept for years
Dates that keep moving
How it works
A notice sent is a record kept.
Decision Notices delivers the notices and logs the requests that follow. It runs on the same consent record, rule library and append-only log as the other eight modules.
- It records the notice
- The wording, the person, the channel and the time are captured for each notice, in the same consent record Sender Check writes.
- It logs what people ask for
- A request to opt out, to have a decision explained, to correct data or to have a person review it is logged with its date and its outcome.
- It tracks deadlines by rule
- Each rule in the library carries its source and effective date. Decision Notices shows which notices are due and when.
- It keeps records for the period each rule sets
- Retention follows the rule that applies to the decision and is visible on each record.
Features
What Decision Notices is made of
Pre-use notice delivery
Sends the pre-use notice for an automated system, and records what was sent, to whom and when.
Adverse-outcome notice tracking
Tracks the notice owed after an unfavorable decision and the deadline for sending it under each rule in the rule library.
Opt-out requests
Where a rule gives people a way to opt out of automated decisions, logs each request and what was done about it.
Explanation and human-review requests
Logs each request for an explanation, a correction or a human review, with who handled it and the outcome.
Retention by rule
Keeps each record for the period the applicable rule sets and shows when that period ends.
One view across states
Shows, for each decision process, which state rules are in the rule library, their effective dates and their sources.
Export per person
Produces everything one person was told and everything they asked for as a single packet.
On the platform
The steps of the consent record this module runs
All nine steps run in every module, from capturing what a person was shown to producing the record when someone asks for it.
- 1. Capture
- Record the page, form or script a person was shown, the exact wording, the time, the device and the action they took. A screenshot alone is not a record; the wording and the event are.
- 6. Record
- Write the decision, the inputs and their dates to a log that is appended to and never edited, so it can be produced later exactly as it was.
- 7. Propagate
- Carry an opt-out, a cancellation or a withdrawal to every system that needs to honor it, and record when each one acknowledged it.
- 9. Produce
- Export the record for one person as a single packet: for a carrier reviewer, a card network, an auditor or your own counsel.
What this does not do
Where Decision Notices stops
It does not test a system for bias
It does not decide whether a system is in scope
It does not keep pace with every change unaided
It does not replace counsel
Read next
The guide, the article and the quiz
Reviewed 12 November 2026
Consentra is software. Nothing on this site is legal advice, and using Consentra does not by itself make a business compliant with any law or carrier rule. Whether a rule applies to your business is a question for your counsel.
See the consent record for yourself
Book a call and we show you the record on your own flow: what each person saw, what they agreed to, and what you can hand over when someone asks.