On this page11 sections
Why the review happens before the import
A purchased or partner list arrives as rows, and the rows rarely carry the context that made the contact lawful to email. The import is the point where that context either enters the system or disappears. If the team imports first and reviews later, the first campaign may already have gone to people who never agreed to hear from this business. A consent review before the import is cheaper than a cleanup after complaints. It also gives the team a defensible record if a recipient asks how they were added.
Identify the source and the collector
For every list in scope, name the organization that collected the data and the website, event, or form where the collection happened. Record the date of collection and the method, such as a checkbox, a double opt-in, or a paper form. A list described only as "partner leads" is not enough. The source determines whether the consent can travel to this business at all. If the collector cannot be identified, treat the list as unusable until the source is confirmed.
Capture the exact consent language
Record the text the person agreed to, not a summary written later. The language should say who will contact them, for what purpose, and through which channel. If the consent covered a different brand or a different kind of message, that scope matters. Save the exact wording with the list and the date it was shown. A checkbox that says "I agree to receive marketing" is not the same as consent to receive email from this specific company. The wording is the evidence.
Check the timestamp and the record
Each record should include a timestamp that can be tied to the consent event, not only the date the list was exported. Record the field that holds the timestamp and whether it is reliable. If the list includes an IP address or a form identifier, note it. A consent record without a time cannot show that the person agreed before the first send. If the list has no timestamps, the team should decide whether the consent can be verified another way before importing.
Confirm the scope covers this sender
Consent for one brand does not automatically transfer to another. Review whether the collector disclosed that data would be shared with partners, and whether this business was named or described by category. If the disclosure was generic, the team needs a lawful basis it can actually rely on rather than assuming the transfer is covered. Record the reasoning and the person who approved it. This is the step where a list can look acceptable in form while failing in scope.
Test a sample against the source system
Pick a sample of records and check them against the collector's own system or a copy of the original form. Confirm that the email, the consent value, and the timestamp match. Look for records that were added after the export or edited by hand. A sample that matches gives some confidence in the list; a sample with unexplained differences is a reason to pause. Record the sample size and the result, and keep the evidence with the import decision.
Decide the suppression and welcome path
Even a lawful list contains people who should not receive the first campaign. Check the list against the business's existing suppression list, prior unsubscribes, and complaint records before import. Decide whether the first message is a campaign or a permission reminder that confirms the relationship. A permission reminder can reduce complaints and gives the recipient a clear way to decline. Record the decision and the message that will be sent.
Import into a quarantined segment
Import the list into a separate segment that is excluded from normal campaigns until the review is complete. Confirm that the segment carries the source, the consent date, and the review status. Do not mix it with the main audience during the import. The quarantine gives the team a chance to fix a mapping or remove a batch without affecting the working list. It also makes the first send a deliberate action rather than an automatic inclusion.
Measure the first send closely
For the first send to the new segment, watch bounces, complaints, and unsubscribe rates more closely than usual. Compare them with the normal campaign baseline. A spike in complaints is a signal that the consent or the expectation was wrong. Record the result and pause further sends if the rates are outside the expected range. The first send is a test of the review, not only of the list.
Keep the evidence with the list
Store the source, the consent language, the timestamp field, the sample result, and the approval with the list record. Keep it where the team can find it when a recipient asks or when a regulator or partner requests evidence. Record the retention period and who can access the evidence. A list that cannot be explained later is a liability even if the first campaign performed well.
Review the partner before the next list
After the import, review the partner's collection process rather than only the list. Ask whether the form names the partner, whether the timestamp is reliable, and whether the scope covers future sharing. Use the answer to decide whether to accept another list from the same source. The goal is not to reject every purchased list; it is to accept only the ones the team can explain and defend.