A DROP vendor follow-up checklist

An operating list for chasing vendor deletion answers: who holds a copy, what you sent, what is still open, and when to export the file.

Use this as a desk checklist for one cycle. It does not replace the statute, and it is not legal advice.

Before you send

Before you send anything:

List every service provider or contractor who stores or derives a copy of the personal information in the batch.
Confirm the email you will actually use.
Open the cycle as 30 days or 45 days, and write down the due time.

When the batch is in:

Upload the CSV with request_id, identifier_type, and identifier_value.
Send each vendor a private acknowledgment link. Treat the link as the credential. Do not forward it.
Ask for an acknowledgment, or an exception with a reason: no records, exempt, unable to process, or other.

While the window is open:

Read the queue. Reminders for people who have not answered are set for day 7 and day 14.
Send the ones that are due. If mail is not configured, copy the link from the cycle page.
When an answer arrives, the open reminders for that vendor can be cancelled.

When you close:

Closing freezes new uploads and new answers. Outstanding vendors stay visible.
Export the CSV and the PDF together. Check that the PDF shows the same checksum as the CSV body.
File both exports with the cycle name.

Drop Ledger helps you organize that sequence. It does not contact DROP, and it does not decide that the cycle was enough.

This note is not legal advice. Drop Ledger helps you organize evidence. It does not decide whether a law has been met.