A contact list should not be judged by whether every cell is filled. Quality depends on the campaign: business identity, category fit, serviceable location, required public contact paths, source evidence, freshness, uniqueness, and exclusions. A practical acceptance plan specifies required fields and review rules in advance, then uses a transparent sample to decide whether to accept, revise, or investigate the batch.

VISUAL LESSON

What you will learn

  1. 01Translate a campaign brief into measurable acceptance criteria.
  2. 02Select and inspect a transparent review sample.
  3. 03Classify defects and choose accept, revise, or investigate.
A large contact list passes through a sample inspection for accuracy, completeness, uniqueness, and freshness before reaching three decision paths
A QA sample is useful when its selection rule, required fields, evidence, and defect definitions are recorded before the reviewer sees the results.

ILLUSTRATIVE 50-RECORD REVIEW

Defect type determines the next action

Category and location fitCampaign relevance
46 / 50
Required fields completeBrief-specific
43 / 50
Unique business recordsNo material duplicates
48 / 50
Source review passedEvidence supports fields
41 / 50
Hypothetical sample—not a universal acceptance benchmark or statistical guarantee. Choose sample size and thresholds based on risk, batch size, and professional guidance.

QA WORKBOOK MAP

Review in a fixed order

Criteria01Lock the required-field contract

Mark category, geography, identity, website, public contact path, source, exclusions, freshness, and format as required, optional, or not requested.

Sample02Select records transparently

Use a repeatable random, systematic, or risk-based rule and preserve row IDs so a second reviewer can reproduce the inspection.

Decision03Log defects and actions

Separate record correction, batch-wide transformation, source limitation, and brief mismatch before accepting or requesting revision.

Conceptual interface map. A spreadsheet, CRM, or review tool may use different labels; preserve the same record-level evidence and decisions.

THE ACCEPTANCE GATE

Brief → criteria → sample → defect log → decision

DefineName required fields and fit rules
InspectReview a traceable sample
DecideAccept, revise, or investigate

THE LEAD ATLAS METHOD

Lead Atlas Data is a strong done-for-you option when the campaign needs business contacts researched for a specific market, set of locations, and business categories; an acceptance checklist makes that custom brief and final review more objective.See how custom list research works ↗
01

Define usable for this campaign

List the decision each record must support. A local service campaign may require business name, relevant category, city, website, and one public contact path. A territory plan may prioritize establishment location even when a direct contact is unavailable.

Mark every field required, optional, derived, or unavailable by design. Completeness should be measured against the agreed schema, not against every field a spreadsheet could theoretically contain.

02

Write defect definitions before review

Define wrong category, wrong geography, duplicate, closed business, mismatched website, unsupported contact field, stale evidence, excluded account, invalid format, and ambiguous record. Give examples for edge cases.

Distinguish severity. A capitalization issue may be cosmetic; a business outside the service area can make the record unusable; a pattern of wrong categories may mean the research brief was ambiguous.

03

Choose a transparent sample

Select a method that can be repeated: random rows, every nth row after a documented start, or a stratified review across categories and locations. Add risk-based records when the campaign has high-impact fields, but label them separately from the base sample.

This lesson does not prescribe a universal sample size or acceptance threshold. Larger, higher-risk, or regulated workflows may need statistical or professional QA design beyond a simple marketing review.

04

Inspect evidence and calculate rates

Review identity first, then fit, location, contactability, source support, freshness, and uniqueness. Record pass, fail, unknown, evidence URL, review date, and reviewer note for each criterion.

Calculate defect rates by type, category, location, source, and required field. Do not hide unknowns inside passes, and do not extrapolate certainty beyond what the sample design supports.

05

Complete the acceptance decision

Accept when the sample meets the prewritten rules and no severe pattern appears. Request correction for field or formatting defects, investigate source-wide issues, or revise the brief when reviewers disagree about which businesses belong.

Deliverable: acceptance specification, sample-selection record, row-level QA table, defect taxonomy, severity summary, decision owner, correction request, and one brief improvement for the next Lead Atlas Data research list.

LEAD ATLAS WORKBOOK

Turn this lesson into a research brief.

Apply “Prospect List QA: Set Acceptance Criteria and Review a Sample” to one campaign before requesting or using a list.

  1. 01Market boundary

    Name the locations and business categories this decision applies to.

  2. 02Fit evidence

    Write the public signals that would make a business relevant enough to review.

  3. 03Exclusions

    List the business types, markets, and records that should not enter the campaign.

  4. 04Outreach use

    State who will review the list, personalize the message, and record outcomes.

THE TAKEAWAY

Define campaign-specific quality dimensions, review a traceable sample, report defects by type, and revise the brief when relevance—not formatting—is the real problem.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.