# Alabama delivery and corrective-action register

Alabama Data Breach Notification Act | Worked example with fictional data

Step: Reconcile delivery, preserve the record and close gaps
Owner: Privacy operations + Customer support + Internal audit
When: During delivery and after the last required notice

## Gather first
- Approved notice version
- Final recipient file
- Mail and email results
- Regulator receipts
- Call-center and service records
- Investigation closeout

## How to prepare it
1. Freeze a dated copy of the final recipient population. Record the data extract, deduplication method, Alabama-residency rule and approvals. Keep restricted person-level data outside the broad corrective-action tracker.
2. For each channel, log the approved notice version, planned and actual send dates, count attempted, count delivered, returned mail, email failures and the owner for follow-up. Preserve sample proofs and provider reconciliation reports.
3. Log regulator and consumer-reporting-agency submissions separately. Record submission time, receipt or confirmation, confidentiality marking, supplements and the next owner action.
4. Turn each root cause into a measurable fix with a named accountable executive, implementation owner, due date, validation evidence and retest date. Prioritize recurring or systemic failures and report them to management.
5. Close only when the final population reconciles, required notices and supplements are evidenced, exceptions have owners, evidence is retained and open remediation has accepted owners and dates.

## Example

### Fictional delivery row
Training example only. Version AL-NOTICE-v3 approved 12 May 2026. Mail file: 1,140 unique Alabama residents. Vendor accepted 1,138 records; two address exceptions assigned to Privacy Operations. Do not treat vendor acceptance as successful delivery.

### Fictional regulator receipt
Training example only. Alabama Attorney General web-form confirmation saved as IR-AL-2026-014/REG-01. Submission time, filer, confirmation number and confidential attachment list recorded in the restricted evidence index.

### Fictional remediation
Root cause: public export link lacked an expiry. Owner: payroll platform VP. Fix: disable anonymous exports, add short-lived authenticated links and alert on bulk download. Evidence: approved configuration, negative access test and a 30-day monitoring review.

### Executive closeout
Summarize confirmed scope, notice count, unresolved uncertainty, service impact, regulator exchanges and corrective actions. Label estimates, route privilege-sensitive advice to counsel and avoid including personal rows in the board copy.

## Review
A replacement owner can prove what was sent, to whom, which records failed, how the regulator was contacted and whether each agreed control change actually worked.

## Handoff
Give owners their assigned corrective actions and schedule the retest. Keep the incident evidence in its approved retention location.

Official reference: Alabama Data Breach Notification Act, §§8-38-5 to 8-38-10
https://www.alabamaag.gov/wp-content/uploads/2026/05/Act-2018-396.pdf

Use the current rules and any prescribed forms for your engagement.
