Lead quality standards: the written spec to give every supplier
A lead quality standard is a short written spec a buyer gives each supplier before the first lead is sent. It lists the fields every lead must carry, the qualifier answers that drive routing in each vertical, the consent record stored with each lead, how many buyers may receive a lead, and which faults make a lead returnable.
This page is a template for that spec, built on the field names Summit Leads uses on its MVA and home services leads.
A quality standard is a spec, not a promise
Every supplierSupplierAny company that provides leads to a buyer, whether it generates them itself or brokers them from publishers. Glossary says its leads are high quality. A spec turns that claim into things you can check on a single lead: is the field there, does the answer match your filter, can the consent record be produced. If a point on your list cannot be checked on one lead, rewrite it until it can.
Vetting a supplier is a separate job, covered in how to evaluate a lead supplier. The spec is what you hand over once you have chosen one, so both sides test against the same list.
The five parts of a lead quality spec
| Part | What it defines | Evidence to ask for |
|---|---|---|
| Contact and location | Which identity and address fields every lead must carry, and in what format. | A sample lead or field specification with every required field filled. |
| Qualifiers | The answers your routing depends on, vertical by vertical. | The form questions behind each qualifier, worded as the consumer saw them. |
| Consent record | What must be stored with each lead to show the consumer agreed to be contacted. | The consent fields on a test lead, and a record pulled for a lead you name. |
| Routing and exclusivity | How many buyers may receive the same lead, and which filters run before you see it. | A plain description of how the supplier routes and caps distribution. |
| Return triggers | The objective faults that make a lead returnable under your agreement. | The written return terms agreed during onboarding. |
Keep the spec to one page. A long list of soft requirements is harder to enforce than a short list of checks.
Qualifier fields to name in the spec, by vertical
Contact and location fields (name, phone, email, address, city, state, ZIP code) are the same everywhere. The fields that differ are the qualifiers. These are the field names on Summit’s leads, taken from the sample leads:
| Vertical | Qualifier fields | Why buyers check them |
|---|---|---|
| Car accident (MVA) | accident_date, injury, at_fault, represented, doctor_treated, accident_type, case_description | Recency of the accident, a reported injury, fault and whether a lawyer is already retained decide whether intake can take the case. |
| Roofing | project_type (install, replace or repair), roofing_type, property_type, own_property | Repair and replacement jobs go to different crews, and material and property type decide who can quote. |
| Bathroom remodeling | project_type (for example full remodel, tub-to-shower conversion, walk-in tub, vanity replacement), own_property | A full remodel and a single-fixture job are different products, often for different buyers. |
| Window replacement | num_windows, project_type, type_of_windows, window_material, own_property | Window count and frame material shape the size of the job and which installers want it. |
| HVAC | project_type (install, replace or repair, heating or cooling), own_property, purchase_time_frame | Repair requests and system replacements are routed to different teams. |
| Solar | own_property, project_type, purchase_time_frame, full street address | Solar companies look at the home itself before quoting, so the address and homeownership matter most. |
Mark each field as required or optional. If you only buy from homeowners, say so and name the field (own_property) rather than writing “qualified homeowners”. Field names, formats and required fields are confirmed during onboarding.
Questions the consent record must answer
Instead of asking whether a supplier is “TCPATCPAThe Telephone Consumer Protection Act, the federal law that governs telemarketing calls and texts, autodialers, prerecorded voice messages and the Do Not Call Registry. Glossary compliant”, write down the questions a stored consent record has to answer for any single lead:
- What exact opt-in wording did the consumer see next to the submit button (tcpa_text)?
- On which page was the form submitted (landing_page_url)?
- When was it submitted, and from what device (submission time, ip_address, user_agent)?
- Is there an independent record of the form session that you can open and keep?
- Does the wording cover the way your team will contact the consumer: calls, texts or both?
Ask for the record on a named test lead before live traffic starts. Federal rules changed in 2025 when the FCC’s one-to-one consentOne-to-one consentAn FCC rule adopted in 2023 that would have limited each prior express written consent to a single seller. Glossary rule was vacated, so check older consent language with your counsel. The TCPA compliance guide covers the background. This is general information, not legal advice.
Writing exclusivity and routing into the spec
“Exclusive” only means something when it is defined. Write it as a rule: an exclusive leadExclusive leadA lead delivered to one buyer and not resold to others. Glossary is delivered to one buyer and is not sold to anyone else. A shared lead states the most buyers who may receive it. Then ask the supplier to describe, in plain words, how its system enforces that rule.
Routing belongs in the same section. List the filters that run before a lead reaches you (states or ZIP codes, project type, homeownership, accident recency) and the daily caps you set. In a ping/postPing/postA real-time selling method in which a lead is pinged to buyers with partial data, buyers bid, and the winning bidder receives the full lead by post. Glossary setup the buyer sees partial data first and only receives the full lead after winning it, so filters can be checked at the ping. See exclusive vs shared leads.
Turning the spec into return triggers
Each check in the spec should map to a return reason, and each return reason should be something either side can verify on the lead itself:
| Fault | How it is judged |
|---|---|
| Phone number not in service | Objective: can be checked on the first attempt. |
| Lead outside the filters you set (state, ZIP code, project type) | Objective: compare the lead with the agreed filters. |
| Duplicate of a lead you already received within the agreed lookback | Objective: match on phone, email or address. |
| A required field is missing or obviously false | Objective: listed in the written spec. |
| Consent record cannot be produced for the lead | Objective: request it by lead ID. |
| Consumer did not answer, chose another company or changed their mind | Not a quality fault: normal sales outcome, usually not returnable. |
How returns are submitted and credited is explained on how lead returns work.
How Summit Leads meets a buyer’s spec
- Leads are web form leads, delivered in real time by ping/post, so your filters run before you buy.
- TCPA consent is captured on every lead, and the consent fields travel with the lead.
- MVA and home improvement leads are exclusive by default; shared leads are available on request.
- Field names, required fields, caps and return terms are agreed during onboarding, before the first live lead.
- Our team has 7 years of combined experience in lead generation.
Related buyer resources
What should a written lead quality standard include?
Five parts: the contact and location fields every lead must carry, the qualifier answers your routing depends on in each vertical, the consent record stored with each lead, how many buyers may receive the same lead, and the objective faults that make a lead returnable. Each part should name the evidence the supplier will show you, such as a sample lead or a consent record pulled on request.
Which qualifier fields matter most on an MVA lead compared with a home improvement lead?
On a car accident lead, intake looks first at the accident date, whether the consumer reports an injury, fault, and whether a lawyer is already retained. On home improvement leads the deciding fields are homeownership and the project itself: install, replace or repair for roofing and HVAC, the type of bathroom project, or the number of windows and frame material for window replacement.
What should a buyer be able to learn from a lead’s consent record?
The opt-in wording the consumer saw, the page where the form was submitted, when it was submitted, the device details, and an independent record of the form session. From those, a buyer and its counsel can judge whether the consent covers the calls or texts the buyer plans to make. This is general information, not legal advice.
How do lead quality standards relate to lead returns?
The standard says what a good lead looks like; the return terms say what happens when a lead falls short. Writing return triggers as objective faults (a disconnected number, a lead outside your filters, a duplicate, a missing required field) keeps returns quick to settle. Not reaching the consumer or losing the sale is a sales outcome, not a quality fault.
Are Summit Leads leads exclusive?
MVA and home improvement leads are sold exclusive by default, to one buyer, and shared leads are available on request. Leads are delivered in real time by ping/post with TCPA consent captured on every lead, and return terms are agreed during onboarding.
Ready to set quality standards with a supplier you can trust?
Send us your spec with the verticals and states you buy in, and we will go through it point by point.
Become a BuyerGenerating leads instead? Sell your leads
Related for publishers: Publisher traffic guidelines. Related in the lead gen guide: How to verify leads.