# SaaS lead quality audit checklist > Diagnose lead problems using a shared fit definition and observed sales outcomes. Work through 10 checks, record evidence and owners, and save an editable copy. Source: https://saas-marketing.net/checklists/lead-quality-audit/ Topic: SaaS Lead Generation Type: checklist Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/checklists/lead-quality-audit/ ## Short answer SaaS lead quality audit checklist helps a SaaS team diagnose lead problems using a shared fit definition and observed sales outcomes. Mark each check only after reviewing the evidence. Record unresolved items with an owner and next action; a completed checklist records the review, not a guarantee of business results. ## Key takeaways - Diagnose lead problems using a shared fit definition and observed sales outcomes. - Do not solve a quality complaint merely by raising a score threshold and hiding rejected volume. - Record evidence and an accountable owner for each unresolved check. - The editable download includes status, owner and evidence columns. --- Diagnose lead problems using a shared fit definition and observed sales outcomes. For the wider context, see the [saas lead generation hub](/saas-lead-generation/). ## Work through the checks **SaaS lead quality audit checklist** ## Save the evidence | Check | Status | Owner | Evidence and next action | | --- | --- | --- | --- | | Lead and qualified-lead definitions are distinct | Not reviewed | | | | Duplicate records are identified | Not reviewed | | | | Disposable or invalid submissions are measured | Not reviewed | | | | Account fit is evaluated separately from activity | Not reviewed | | | | Sales rejection reasons are recorded | Not reviewed | | | | Routing reaches the correct owner | Not reviewed | | | | Response times are measured from valid submission | Not reviewed | | | | Campaign source survives enrichment | Not reviewed | | | | Opportunity creation is tracked by cohort | Not reviewed | | | | Feedback changes are documented | Not reviewed | | | ## A situation to test Review a sample of rejected leads with sales. A routing error can look like poor lead quality when the right rep never saw the account. Use this example as a review prompt. Ask the owner to demonstrate the real behavior or show the underlying record. A screenshot of settings can help, but it does not replace testing the outcome the customer experiences. ## When to stop and fix the issue Do not solve a quality complaint merely by raising a score threshold and hiding rejected volume. Prioritize failures that mislead customers, lose data, break the promised action or make measurement unreliable. Cosmetic improvements can be scheduled separately when they do not prevent the task from being completed. Record the reason for any accepted exception so the next reviewer does not mistake it for an overlooked problem. ## How to close the review Assign every unresolved item to a named person and a date. Keep the evidence close to the checklist, using links with appropriate access rather than copying sensitive records into a public document. After the fix, repeat the relevant check and record what changed. The final review should answer three questions: what passed, what remains uncertain, and what action follows. If a requirement does not apply, state why. A blanket tick against every row provides less value than a shorter list with specific evidence and a clear next step. ## Related resources - [B2B SaaS lead generation](/guides/b2b-saas-lead-generation/) - [The B2B SaaS lead generation funnel](/guides/saas-lead-generation-funnel/) - [Lead generation by company stage](/guides/lead-generation-for-saas-companies/) - [Lead generation playbooks by ACV band](/playbooks/b2b-saas-lead-generation-by-acv/) - [Lead generation for a SaaS startup](/guides/saas-startup-lead-generation/) Browse more [checklists](/checklists/) or save the [resource index](/resources/). {/* expanded-practice-2026-09 */} ## Apply saas lead quality audit checklist in a working review Treat each check as a request for evidence, not a box to tick from memory. Inspect the actual behavior or record, note the result and assign an owner to any failure. Distinguish a blocking issue from a deferred improvement. Keep the reason for an exception so a later reviewer can understand why the work proceeded. For this topic, involve the conversion-path owner and the person reviewing saved requests and work from the form promise, stored record and actual delivered resource. The relevant unit is a valid consented request with a defined purpose. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence. ### Evidence to prepare Test the entire path from a suitable visitor’s action to verified storage and useful delivery. A success animation is not evidence that a record was saved. Keep the requested resource accessible after completion and make error recovery clear without exposing private submissions. | Review field | What to record | | --- | --- | | Topic | SaaS lead quality audit checklist | | Decision | The specific action this explanation should help you choose | | Working evidence | the form promise, stored record and actual delivered resource | | Unit and scope | a valid consented request with a defined purpose | | Responsible people | conversion-path owner and the person reviewing saved requests | | Remaining uncertainty | The missing fact that could change the decision | ### Two situations that can change the interpretation #### When form fields reduce useful submissions A file download may need only email and consent, while a tailored audit request can justify a small amount of business context. Use this check: Review each field's operational purpose and inspect valid incomplete attempts without collecting unnecessary private data. A shorter form can reduce context, so review downstream quality as well as volume. The [focused diagnostic guide](/guides/form-fields-reduce-useful-submissions/) provides the correction process and a working evidence sheet. #### When duplicate submissions inflate lead reporting A visitor downloading three related worksheets creates three interactions, not necessarily three independent sales opportunities. Use this check: Compare normalized identifiers and submission purposes within an explicit deduplication window. Do not merge different people merely because they share an organization or domain. The [focused diagnostic guide](/guides/duplicate-submissions-inflate-lead-count/) provides the correction process and a working evidence sheet. ### Record the decision and the limit A synthetic test request can confirm that the form validates, the database accepts the intended fields and the advertised file exists. The test should be isolated from real leads and cleaned up by an authorized process. Operational review of genuine requests remains a separate responsibility. Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required. Use the [complete topic collection](/topics/saas-lead-generation/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### How should I use this checklist? Choose one campaign, page, process or account group. Review each check against actual evidence, record exceptions and assign follow-up work before marking the review complete. ### What should stop the work from proceeding? Do not solve a quality complaint merely by raising a score threshold and hiding rejected volume. ### Does a completed checklist guarantee success? No. It records a structured review of known risks and requirements. Customer behavior, market conditions and facts outside the review can still change the outcome. ### Can I save the checklist? Use the download form for an editable CSV copy. Browser checkmarks are saved on this device where local storage is available; they are not shared with your team.