The prospect spreadsheet arrives with 180 rows and a status of “done.” Your next step is supposed to be loading the contacts into an outreach sequence. But a complete-looking file doesn’t tell you whether those companies fit your brief, whether the contacts are current, or whether anyone on the list has already asked not to be contacted.
To audit a lead list before outreach, first confirm where the data came from and screen the entire batch against your existing records and suppression lists. Then check a spread of rows for company fit, contact roles and supporting sources, review email-verification results, and make one decision about the batch: accept it, return it for rework or reject it. Set your failure conditions before looking at the results.
This test is for founders, agency leads and sales teams receiving a finished prospect list from a virtual assistant, colleague or outside researcher. It begins where delegating lead generation to a virtual assistant leaves off: deciding whether the delivered list is ready for use, not how to build it. The sample sizes and pass marks below are illustrative working choices, not industry standards. This is operational guidance, not legal advice.
What a list has to pass before anyone sends
Five checks matter, and each answers a different question:
| Check | What you’re trying to establish | Why it matters |
|---|---|---|
| Provenance | Who built the list, when, from which sources and against which brief? | You need to know what the rows actually represent. |
| Permission and suppression | Is anyone excluded, opted out or otherwise ineligible for this outreach? | An address can be reachable but still unsuitable to contact. |
| Company fit | Do the companies meet the agreed industry, geography and other criteria? | Wrong-fit records waste the campaign’s limited attention. |
| Contact currency | Is the named person still plausibly in the role recorded? | Old job titles can make otherwise accurate-looking records misleading. |
| Deliverability | Is the email address valid, invalid, catch-all or unresolved? | Technical checks help reduce avoidable failed sends, but don’t establish fit or lawful use. |
These checks are not interchangeable. A verification tool may identify a deliverable mailbox without telling you whether the person works at the company or has objected to marketing. Likewise, a company can match your target profile while its contact channel still needs review.
For UK business outreach, the Information Commissioner’s Office (ICO) guidance on B2B marketing distinguishes corporate subscribers from individual subscribers, including sole traders and some partnerships. The email-marketing rules can differ, and the UK GDPR can still apply when you process a business contact’s personal data. Publicly listed contact details are not a blanket permission slip.
Why a bad list costs more than the time to check it
The numbers mailbox providers watch
List quality isn’t the same as email infrastructure, but poor targeting and stale or unwanted contacts can contribute to the problems mailbox providers measure.
Google’s Gmail sender guidelines FAQ says senders should keep their user-reported spam rate below 0.1% and prevent it from reaching 0.3% or higher. Yahoo’s sender best practices call for spam complaint rates below 0.3%, with additional unsubscribe requirements for bulk senders. These percentages concern spam complaints, not bounced emails. They are provider guidance, not proposed defect tolerances for your spreadsheet.
Separately, Microsoft’s high-volume sender requirements took effect on May 5, 2025 for domains sending more than 5,000 emails a day to its consumer addresses. They require SPF and DKIM to pass and an aligned DMARC policy of at least p=none. Microsoft’s updated announcement specifies rejection for mail that fails these authentication requirements. This is a sending-domain obligation, not something a lead-list audit can fix.
Why “verified last quarter” isn’t current enough
Contact data changes after a list is collected. In a September 2026 analysis, data vendor Lusha reported that 12.25% of a cohort of 140,284 US VP- and C-suite sales leaders had changed roles over a 12-month window. The vendor also described a delay before very recent role changes appear in datasets. Those findings concern that particular cohort and the vendor’s methodology, not every B2B contact.
The practical lesson is modest: a refresh date is useful context, but it’s not proof that an individual still holds a listed role. Check important records close to the time you intend to use them.
Before you look at a single row: set your pass marks
Deciding what counts as failure after you have seen the defects makes the test harder to apply fairly. Record two kinds of conditions before you sample the list.
Hard stops: no release until resolved
Treat these as reasons to pause the affected campaign batch rather than quietly load it:
- Suppression or objection match: an opted-out contact appears in the proposed send group. Remove it from the send path and investigate how it entered the file.
- Missing provenance: required source evidence is absent and you cannot establish why the record belongs in the list.
- Wrong target filter: the batch was built against the wrong industry, geography or other mandatory criterion.
- Unresolved UK subscriber status: a UK email contact may be a sole trader or another individual subscriber, with no documented consent or applicable soft opt-in. Hold that record while the responsible person determines whether marketing is permitted.
One hard-stop finding prevents as-is acceptance. It doesn’t necessarily mean every row is unusable. Where the cause is traceable and fixable, returning the batch may be more appropriate than rejecting it.
Tolerances: define what can be repaired without rebuilding
For duplicates, stale job roles, missing noncritical fields, role-based inboxes and catch-all or unknown verification results, set a limit that suits the campaign’s risk. There is no universal pass percentage.
For example, a sales lead might say: “In a 30-row sample, no more than one contact may have an out-of-date role, and every row must have a source that supports its inclusion.” That is an illustrative owner-defined rule, not a deliverability benchmark.
Record the checks, acceptable evidence, permitted fixes and decision-maker. My guide to giving clear instructions to a virtual assistant covers how to make those expectations unambiguous before work starts.
How to audit a lead list before outreach, step by step
Run the checks in this order. An early failure may save you from spending time verifying addresses in a batch that was built against the wrong brief.
Step 1: Confirm provenance for the whole batch
Identify the researcher or source, delivery date, original targeting brief and version, research dates and whether the data was researched, imported or purchased. For each row, the supporting source should explain why the company or contact qualifies, not merely repeat its name.
If nobody can tell you what rules or sources were used, pause the acceptance test and ask for that information first. For a future list-building assignment, this research-task guide explains how to specify source links and exception fields upfront.
Step 2: Screen the entire list against known records
Check all rows, not just the sample, against suppression and do-not-contact lists, existing customers, active opportunities, and contacts who have already received the campaign. Normalize domains and emails carefully enough to catch obvious variations, without assuming that people with similar names are identical.
Not every collision means the same thing. An opt-out is a send stop; an existing customer may belong in a different segment; a possible duplicate may need investigation. For the underlying record-handling rules, see CRM cleanup before merging records and how to handle archived and suppressed contacts.
Step 3: Hand-check a spread of rows
For a typical few-hundred-row delivery, 20 to 50 hand-checked rows can be a reasonable illustrative starting point. For a list below roughly 50 rows, reviewing every record may be simpler. Larger or higher-risk campaigns may justify more checking. None of these figures guarantees a statistical confidence level.
Select rows across the entire file, including different source groups, research dates and customer segments. Add randomly chosen rows within those groups rather than inspecting only the first 30. If you discover one suspicious source or import group, inspect that group further.
For each selected row, open the company website or another approved first-party source and ask: Does the company meet the brief? Does the contact still appear to hold the relevant role? Does the cited source actually support the field recorded? Treat a social-profile discrepancy as a reason to flag and investigate, not as permission to copy unverified details into the list.
Step 4: Review email verification separately
Run the agreed verification check and keep its results distinct from your fit checks. Useful categories include valid, invalid, catch-all and unknown; these labels depend on the tool and aren’t proof of permission.
Catch-all domains may accept mail for addresses that cannot be confirmed individually. An “unknown” result also calls for caution, not automatic approval. Apply the campaign’s pre-set policy for these contacts, rather than converting every uncertain result into “verified.” Review generic or role-based addresses against the agreed contact criteria.
Step 5: Count defects and decide the batch
For each test category, record how many sampled rows failed, plus example row IDs. Keep whole-list checks, such as suppression matching, separate from the sampled findings. Then compare the results with the pass marks recorded before testing.
If a hard stop is unresolved or a tolerance is exceeded, the batch is not ready as delivered. Don’t repair a handful of sampled rows, declare victory and assume the other rows are fine. You need a decision about the batch and, when appropriate, a defined re-test.
Accept, return or reject: what each decision means
| Decision | Use it when | Next action |
|---|---|---|
| Accept | Required whole-batch checks pass, sample findings meet pre-set tolerances and no unresolved send stops remain. | Record sign-off, retain the acceptance sheet and release only eligible contacts to the approved outreach workflow. |
| Return for rework | Defects are material but the source, filter or verification problem can reasonably be corrected. | Send a defect log with examples, required fixes and re-test conditions. Do not send the batch yet. |
| Reject | Provenance is irretrievable, the list is fundamentally outside the brief, or reliable correction isn’t practical. | Don’t use the batch; commission a new list or agree on a different sourcing method. |
The researcher or virtual assistant can investigate exceptions, replace unsupported records and document corrections. The person accountable for outreach should approve the acceptance rule and the release decision. Returning work with an actionable defect log is more useful than silently rewriting the spreadsheet yourself.
Worked example: a 180-row list that needs to go back
Imagine a small UK-focused agency receiving 180 prospect records for outreach to marketing agencies. The file is marked complete. Before looking at individual rows, the sales lead sets these fictional, illustrative conditions: zero unresolved opt-outs, zero unsupported rows, no unresolved individual-subscriber email eligibility, and no more than one stale role in a 30-row sample.
The team screens the full 180 rows against its known records, then hand-checks 30 spread across the file and its source groups. The sample uncovers:
| Finding | Example row IDs | Result |
|---|---|---|
| Three contacts have changed roles | 017, 072, 146 | 3 of 30 exceeds the illustrative allowance of 1. |
| Two rows have no supporting source | 031, 128 | Hard stop until provenance is restored or rows are replaced. |
| One business is a sole trader with no documented email-marketing basis | 154 | Hold the contact; assess the applicable UK rules before any send. |
| One company is already an active customer | 166 | Remove from this prospecting segment and check the exclusion logic. |
These are invented records, not results from a real campaign. The sole-trader finding does not, by itself, prove that an email would be unlawful; it shows that eligibility hasn’t been established. The customer match is a campaign exclusion, not automatically a legal suppression.
Decision: Return for rework. The evidence still allows the list to be rebuilt or corrected, but accepting the other 173 rows without a batch-level check would ignore the possibility of repeatable sourcing errors.
Example return note
Batch: UK marketing agencies, 180 rows. Decision: RETURN, no release to outreach. In the 30-row sample, review role currency for rows 017, 072 and 146; replace or substantiate sources for 031 and 128; hold 154 until the responsible reviewer confirms email eligibility; and remove 166 from this campaign segment. Check the same problems across the full list, document every changed row and source, then resubmit. Re-test all flagged rows, repeat the full-list suppression screen and review a fresh spread sample before sign-off.
The person preparing the rework should also correct the research brief if a repeated problem came from an ambiguous instruction rather than an isolated mistake.
Copy this lead list acceptance sheet
Use the following as one page in your campaign workbook, or save it alongside other repeatable procedures in your SOP library. Complete the pass marks before checking results.
Batch details
| Field | Entry |
|---|---|
| List name / batch ID | ______ |
| Received on / received from | ______ |
| Builder and source type | ______ |
| Target brief / ICP version | ______ |
| Channel and recipient country | ______ |
| Total rows / research date range | ______ |
| Campaign decision-maker | ______ |
Pre-set acceptance conditions
Hard stops: ______
Allowed defects by category (counts or percentages): ______
Sampling method and sample size: ______
Rules for unresolved or catch-all email addresses: ______
Test results
| Check | Method | Found | Pass / fail / pending | Example rows |
|---|---|---|---|---|
| Provenance | Batch documentation + selected source checks | ___ | ___ | ___ |
| Suppression / existing contacts | Full-list match | ___ | ___ | ___ |
| ICP fit | Spread sample, first-party evidence | ___ | ___ | ___ |
| Current role | Spread sample, approved sources | ___ | ___ | ___ |
| Source supports the row | Spread sample | ___ | ___ | ___ |
| Duplicates | Full-list normalization and match | ___ | ___ | ___ |
| Deliverability | Agreed verification process | ___ | ___ | ___ |
| Role-based or catch-all inboxes | Verification exceptions | ___ | ___ | ___ |
| UK subscriber type, if relevant | Classification and eligibility review | ___ | ___ | ___ |
Decision and handoff
Decision: ACCEPT / RETURN / REJECT
Decision-maker and date: ______
Defects and counts: ______
Example rows and evidence: ______
Required correction: ______
Who owns rework: ______
Re-test method / next review date: ______
Keep the completed sheet with the campaign record. Its purpose isn’t to create another permanent checklist for every small task; it’s to make the acceptance decision understandable when someone else prepared the file.
When a full sample audit isn’t worth it
Tiny hand-built lists, warm introductions and recently approved segments may not need the same sampling procedure as a large external delivery. Checking every row may be quicker for a short list, and previously checked records may need only a focused refresh if nothing material has changed.
Still perform the relevant suppression and eligibility checks before outreach. Earlier approval doesn’t override a later opt-out or a change in the way you intend to contact someone.
The useful final output is a documented decision, not a prettier spreadsheet. When the list fails, turn the actual defects into a revised brief and request a reworked batch rather than absorbing the research job yourself.
If you need help building or correcting source-linked prospect lists against clear acceptance criteria, explore my Research & Lead Generation support. The sourcing and rework can be handled as defined support work, while you retain the campaign’s targeting and final sign-off.


