DROP Status Reporting and Amendments
Reporting is where a processing cycle becomes evidence. Outcome categories need consistent internal definitions before staff start applying them.
Outcome categories to define internally
| Outcome | Internal definition you need |
|---|---|
| Deleted | What deletion means across each system, including backups and derived data. |
| Opted out | When an opt-out outcome applies instead of deletion, and who decides. |
| Exempt | Which exemption, on what basis, recorded by whom. |
| Not found | What matching attempts were made before concluding no match exists. |
Write one sentence per outcome category that any operator can apply the same way. Inconsistent categorization across cycles is harder to correct after the fact than to prevent.
Amendments matter because real cycles produce corrections: a record is found late, an exemption is reassessed, or a matching bug is fixed. Decide in advance who can amend a reported status and what evidence the amendment requires.
Confirm the current status values, reporting windows, and amendment mechanics against official DROP technical documentation.
This page describes CA DROP Broker's operational reading of publicly available California materials. Verify current requirements against official CalPrivacy sources and with qualified counsel.