Qualification Gap Audit
Determine whether the business consistently gathers the information required to identify fit, intent, urgency, value, and the appropriate next action for each inquiry — and whether qualified opportunities are being…
Link
3
Link Name
Qualification
Role
audit
Loop Step
Diagnose
Purpose
Determine whether the business consistently gathers the information required to identify fit, intent, urgency, value, and the appropriate next action for each inquiry — and whether qualified opportunities are being lost to an inconsistent or incomplete intake process rather than to genuine lack of fit.
Governing Principle
Source quality is NOT qualification quality, and a low-fit lead is NOT the same as a poorly qualified lead. This audit measures qualification quality: whether the business's own process gathered enough evidence to make a sound next-step decision. A potentially valuable lead must never appear unqualified because intake was inconsistent or incomplete.
Critical Distinctions
- Source quality vs qualification quality
- Source quality is how good the leads a channel sends are (measured by RLR-07). Qualification quality is whether the business consistently extracts the evidence needed to decide what to do with a lead. A great source can still be wasted by inconsistent qualification.
- Low fit vs poorly qualified
- A LOW-FIT lead is one the business genuinely cannot or should not help, established from sufficient evidence. A POORLY QUALIFIED lead is one where the business never gathered enough evidence to know — it may be an excellent opportunity that intake failed to surface.
- Disqualified vs insufficient information
- Disqualification requires evidence of non-fit. Absence of evidence is INSUFFICIENT INFORMATION, not disqualification. This audit counts how often leads are classified without sufficient evidence.
What To Measure
For a representative sample of recent inquiries that reached (or should have reached) qualification, measure how completely and how consistently the business captured fit, need, intent, urgency, value, decision readiness, routing, disposition, and next action — segmented by responder, source, and channel.
Scope
- Unit Of Analysis
- One inquiry/lead record that reached, or should have reached, the qualification stage (meaningful contact occurred or was attempted per Link 2).
- Boundary With Link2
- If meaningful first contact never happened, that is a Link 2 (Speed-to-Lead) leak, not a qualification leak. Qualification is audited only where contact occurred or where contact was made but qualification was skipped or partial.
- Sample Guidance
- Use every qualifying inquiry in the review window if volume is low, or a representative random sample (not cherry-picked) of at least 40-60 records where volume is high. Record the window and sample method. Do not draw consistency conclusions from fewer than ~20 records; below that, report 'insufficient sample' rather than a rate.
Data To Collect
- Note
- Collect only what is reasonably necessary to judge fit, next action, and routing. Do not collect sensitive information merely because it exists (see dataMinimization).
Metrics
- Note
- Compute only where data permits. Where a field was not captured for enough records, report coverage ('measurable for N of M records') instead of a misleading rate.
Leak Patterns
No standardized qualification process
- Id
- no_standard_process
- Routes To
- RLR-17
Too many questions before value is established (interrogation)
- Id
- too_many_questions_early
- Routes To
- RLR-17, RLR-19
Too few questions to determine fit
- Id
- too_few_questions
- Routes To
- RLR-17
Inconsistent questions by employee
- Id
- inconsistent_by_employee
- Routes To
- RLR-17, RLR-19
Urgency / timeline not established
- Id
- missing_urgency
- Routes To
- RLR-17, RLR-19
Premature disqualification (non-fit assumed without evidence)
- Id
- premature_disqualification
- Routes To
- RLR-18, RLR-21
High-intent leads not recognized
- Id
- high_intent_unrecognized
- Routes To
- RLR-18
Qualification data gathered but not stored
- Id
- qualification_data_not_stored
- Routes To
- RLR-17, RLR-21
Qualified leads routed incorrectly
- Id
- qualified_routed_wrong
- Routes To
- RLR-20
Leads left in ambiguous states
- Id
- ambiguous_states
- Routes To
- RLR-21
No next action assigned
- Id
- no_next_action
- Routes To
- RLR-20, RLR-21
Handoff missing key context for the next owner/system
- Id
- handoff_missing_context
- Routes To
- RLR-20, RLR-21
Benchmark Policy
- Approved Benchmarks Available
- false
- Rule
- Do not fabricate universal qualification benchmarks. There is no ShiFt-approved 'good' qualification-completeness or qualified-rate number. Where a threshold depends on the business, make it configurable and have the operator set a deliberate target from this audit's measured baseline (RLR-03) and the KPI Dictionary (RLR-35).
Missing Data Rules
A field that was never captured is 'unknown', not a failure of the prospect and not evidence of non-fit. Count unknowns explicitly; never convert an unknown into a disqualification. If critical fields are unknown for most records, the primary finding is 'no reliable qualification data' and the first repair is RLR-17, not a scoring change.
How To Use
1) Pick a review window and pull the qualifying inquiries. 2) For each record, fill the per-inquiry fields from real CRM/call/chat evidence — never invent answers. 3) Compute the metrics that data supports. 4) Tag each record against the leak patterns. 5) Segment by responder, source, and channel to expose inconsistency. 6) Carry the top 1-3 patterns into the repair sequence.
How To Interpret
High missing-critical-fields, high classified-without-evidence, or wide responder variance means the leak is qualification CONSISTENCY, not lead quality — repair with RLR-17/RLR-19 before touching scoring. High ambiguous-disposition or no-next-action means the leak is downstream control — repair with RLR-20/RLR-21. A high 'unknown' share masquerading as 'disqualified' means good opportunities are being discarded by process, not by fit.
Action That Follows
Route the top patterns into the Link 3 repair sequence: framework/checklist (RLR-17) to standardize what is asked, scoring rubric (RLR-18) to classify consistently, scripts (RLR-19) to gather without interrogating, routing matrix (RLR-20) so qualified opportunities reach an owner, disposition standard (RLR-21) so no lead is left ambiguous.
Owner
Revenue operations owner or intake/sales manager accountable for lead handling. One named person owns the audit and the resulting repair plan (recorded on RLR-39).
How To Implement
Install the smallest change that closes the audited defect first — usually the required-question checklist (RLR-17) and the disqualified-vs-insufficient-information distinction (RLR-18/RLR-21). Do not deploy all six instruments at once if one gap dominates.
How To Test
Re-audit a fresh sample of records created AFTER the repair using the same fields and metrics. Confirm records now carry the required fields, classifications cite evidence, and no lead sits in an ambiguous or no-next-action state.
When To Remeasure
Re-run at 14 and 30 days after the repair, then on the standing cadence in the Weekly Revenue Chain Operating Review (RLR-38).
How To Know It Improved
Qualification completeness up, missing-critical-fields down, classified-without-evidence down, responder/source/channel variance narrowed, ambiguous dispositions down, qualified-with-next-action up, and qualification-to-booking rate improved — on re-measured records, not because a checklist was merely published.
Data Minimization
Only capture fields reasonably necessary to determine fit, next action, and routing. Do not instruct businesses to collect sensitive personal, financial, or health information merely because it could be collected. Do not invent industry-specific compliance requirements.
Handoff To Downstream
This audit defines the qualified-output contract the rest of Link 3 must satisfy for Link 4 (Follow-Up) and Link 5 (Booking + Handoff): classification, intent, urgency, routing destination, disposition, next action, owner, follow-up treatment, and relevant context.
Delivery Status
content_ready_delivery_pending
How to implement
Work through every row honestly; enter "Unknown" rather than guessing.
How to verify
A diagnosis is only useful if its inputs are trustworthy — note attribution and data-quality confidence.
Related in this link
Rather not do this part yourself?
You can repair your Revenue Chain yourself with this Kit — or bring in ShiFt at any point. You do not need to finish the DIY path first.
Done with you
Revenue Leak Scan
A ShiFt specialist runs the diagnosis with you and hands you a prioritized repair plan.
Get My Revenue Leak ScanDone for you
ShiFt RevenueOS
ShiFt installs and operates the full Revenue Chain system for you — ConvertOS included.
See RevenueOS