Lead Scoring Rubric
Translate qualification information into a consistent priority and next-action classification, so every responder reaches the same decision from the same evidence and no high-intent opportunity is missed or falsely…
Link
3
Link Name
Qualification
Role
rubric
Loop Step
Repair
Purpose
Translate qualification information into a consistent priority and next-action classification, so every responder reaches the same decision from the same evidence and no high-intent opportunity is missed or falsely discarded.
Governing Principle
Classification must follow evidence, not a single variable. A lead is never scored on budget, source, urgency, geography, or estimated deal value alone. Where a numeric score is used, it must map transparently to a customer-facing classification — no opaque black-box number.
Classifications
HIGH INTENT
- Id
- high_intent
- Evidence Required
- Clear fit + explicit intent to act soon (asking to book, urgent timeline, ready to proceed).
- Example Conditions
- Requests an appointment or callback now; States an immediate or near-term timeline; Confirms need the business clearly serves
- Priority
- Highest
- Routing
- Immediate route to booking / best-available owner (RLR-20)
- Response Expectation
- Fastest response tier per RLR-11
- Next Action
- Book or connect to owner now
- Follow Up Treatment
- Persistent, prompt (Link 4)
- Stop Condition
- None unless prospect opts out or is confirmed non-fit
QUALIFIED
- Id
- qualified
- Evidence Required
- Fit established and need clear, but timeline or readiness is not immediate.
- Example Conditions
- Good fit, planning to act within a normal window; Need confirmed, comparing options
- Priority
- High
- Routing
- Route to appropriate owner/calendar (RLR-20)
- Response Expectation
- Standard qualified tier per RLR-11
- Next Action
- Advance to booking or scheduled follow-up
- Follow Up Treatment
- Standard sequence (Link 4)
- Stop Condition
- None unless disqualified later with evidence
NURTURE
- Id
- nurture
- Evidence Required
- Potential fit but not ready now (timing, readiness, or external dependency).
- Example Conditions
- Interested but acting later; Fit likely, decision not yet possible
- Priority
- Medium
- Routing
- Route to long-term nurture (Link 4 / RLR-25)
- Response Expectation
- No urgent SLA; scheduled touchpoints
- Next Action
- Enroll in nurture with a revisit date
- Follow Up Treatment
- Long-term nurture (Link 4)
- Stop Condition
- Defined nurture end or opt-out
DISQUALIFIED
- Id
- disqualified
- Evidence Required
- Evidence of genuine non-fit — confirmed out-of-scope service, ineligible, or explicit no-interest.
- Example Conditions
- Requests a service the business does not offer; Confirmed outside served area/eligibility; Explicitly declines
- Priority
- None (closed)
- Routing
- Respectful decline + referral where possible (RLR-21)
- Response Expectation
- Courteous close
- Next Action
- Record disqualification reason; refer out where possible
- Follow Up Treatment
- None
- Stop Condition
- Immediate; must cite evidence of non-fit
ESCALATE
- Id
- escalate
- Evidence Required
- High-value, sensitive, complex, or time-critical situation needing a human/senior owner now.
- Example Conditions
- High-stakes or complex request; VIP / strategic opportunity; Situation beyond intake authority
- Priority
- Highest (human)
- Routing
- Escalate to named owner per RLR-20
- Response Expectation
- Immediate human handoff
- Next Action
- Warm handoff with full context
- Follow Up Treatment
- Owner-directed
- Stop Condition
- Owner accepts ownership
INSUFFICIENT INFORMATION
- Id
- insufficient_information
- Evidence Required
- Not enough evidence to classify fit or intent — a process gap, NOT non-fit.
- Example Conditions
- Contact incomplete; Required questions unanswered; Lead went quiet mid-qualification
- Priority
- Recover before deciding
- Routing
- Return to qualification / incomplete-information follow-up (RLR-19)
- Response Expectation
- Prompt attempt to complete qualification
- Next Action
- Gather missing evidence before any disqualification
- Follow Up Treatment
- Incomplete-information recovery (Link 4)
- Stop Condition
- Only after defined recovery attempts fail
Disqualified Vs Insufficient
- Rule
- A lead must NEVER be marked DISQUALIFIED because the business failed to gather enough information. Absence of evidence is INSUFFICIENT INFORMATION and requires a recovery attempt first. Disqualification requires positive evidence of non-fit.
- Why
- Conflating the two silently discards good opportunities and hides a qualification-process leak behind a 'not a fit' label.
Scoring Model
- Note
- Scoring is multi-factor and configurable. No single factor can classify a lead by itself.
- Weighting Guidance
- Businesses set weights deliberately for their model. A common default emphasizes Fit and Intent over Value so a high-value poor-fit lead never outranks a strong-fit ready buyer. Weights must be written down and applied consistently. There is no universal correct weighting.
- Score To Classification Mapping
- If a numeric score is used, publish the exact bands that map to each classification (e.g. which score ranges = HIGH INTENT vs QUALIFIED vs NURTURE) so the number is always explainable. A score with no visible mapping is not allowed.
- Guardrail
- Fit must gate the score: a confirmed non-fit is DISQUALIFIED regardless of value or urgency, and a lead missing the evidence to judge fit is INSUFFICIENT INFORMATION regardless of an apparently high partial score.
Threshold Policy
- Approved Thresholds Available
- false
- Rule
- Do not fabricate universal scoring thresholds or 'industry-standard' cutoffs. Thresholds and weights are configurable and set by the operator from the RLR-16 baseline and the KPI Dictionary (RLR-35).
What To Measure
Whether the same evidence yields the same classification across responders, and whether classifications are backed by the required evidence rather than a single factor.
How To Interpret
Divergent classifications on similar evidence means the rubric is not being applied consistently; a spike in DISQUALIFIED that is really missing-information means the disqualified/insufficient rule is being violated.
Action That Follows
Attach the required classification + evidence to every qualified record, feed it to routing (RLR-20) and disposition (RLR-21), and correct any misuse of DISQUALIFIED vs INSUFFICIENT INFORMATION.
Owner
Sales/intake manager owns the rubric, the weights, and the score-to-classification mapping.
How To Implement
Adopt the six classifications, set factor weights deliberately, publish the score bands if numeric scoring is used, wire classification into the CRM, and train responders on the disqualified-vs-insufficient distinction with examples.
How To Test
Give several responders the same 5-10 anonymized records and confirm they reach the same classification; audit a sample of DISQUALIFIED records to confirm each cites evidence of non-fit.
When To Remeasure
Re-audit with RLR-16 at 14 and 30 days; review weights/mapping quarterly in RLR-38.
How To Know It Improved
Classification agreement between responders rises, unknown-mislabeled-as-disqualified falls, high-intent recognition rises, and qualification-to-booking improves — measured on records, not asserted.
Consolidation Note
Reuses and improves ShiFt's prior lead-scoring guidance (including the public lead-scoring-vs-AI-qualification explainer); that explainer remains public, and this is the canonical operational rubric it points to.
Delivery Status
content_ready_delivery_pending
How to implement
Install the change exactly as the playbook describes; log it on the Repair Plan.
How to verify
Installing a workflow is implementation, not closure. QA the repair before you trust it.
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