Definition
A four-state lead queue replaces a numerical score with an operational state. Every admitted record is in exactly one state: exclude, research, contact, or active. The state answers what the team may do now and exposes the next unknown that blocks the following action.
- Exclude: dated evidence shows that the record is outside the current target or cannot be pursued under the team's rules. The next unknown is the condition, if any, that would permit reopening.
- Research: the record may fit, but one decision-critical fact is missing or stale. The next unknown is named in the record.
- Contact: admissibility, target fit, person, route, and reason for contact are documented. The next unknown is whether the buyer takes an observable action.
- Active: the buyer has replied, accepted a meeting, requested material, or agreed an explicit next step. The next unknown is the dated commitment that advances the conversation.
The state is not a conversion probability and never proves buyer intent. It is a controlled instruction for the next piece of work.
Prerequisites
Define the admissibility filter before building the queue. A record needs a named company, an accountable role or documented role gap, a source, an observation date, an owner, and a lawful channel review appropriate to the team's context. The filter decides whether the record can enter the operating process. It does not decide whether the buyer is interested.
Use the Defensible B2B Lead Qualification Framework for Small Sales to define eligibility separately from queue state.
The Information Commissioner's Office advises organisations to keep the source and status of personal data clear, review its accuracy, and update it when needed (official accuracy guidance). The queue therefore keeps source URL, observation date, author, and previous state beside every transition.
Browse the Knowledge guides for sales to place this queue beside the other qualification and review methods.
Steps
Build the admissibility filter
Write the minimum conditions in plain language. Separate a disproved condition from an unknown one. A documented mismatch can support exclude. A missing fact sends the record to research. Do not convert absence of evidence into a negative judgment.
Create the four states
Create a single state field with only exclude, research, contact, and active. Add separate fields for state reason, next unknown, evidence URL, observed at, entered state at, owner, and next review date. Keep previous state and previous evidence in history.
Salesforce documents that a lead process can define or customise the status values or stages a lead passes through (official lead-process documentation). The four values here are an editorial operating choice, not Salesforce defaults.
Write dated transition rules
Each transition has a proof condition.
- Research to contact: a dated source confirms the target company, relevant role, valid route, and defensible reason for contact.
- Contact to active: an observed buyer action creates a reply, meeting, request, referral, or explicit next step.
- Contact to research: a dated bounce, role change, invalid route, or contradictory source reopens a named fact.
- Active to research: a dated change invalidates the person, company context, or agreed next step.
- Any state to exclude: dated evidence proves a current disqualifier or records an explicit request not to continue.
Time passing may open a review, but it does not create evidence. Profile views, company fit, public activity, message delivery, and silence cannot move a record to active.
Expose the next unknown
Make one question mandatory for every non-excluded record. In research, ask which fact is missing. In contact, ask which buyer action has occurred. In active, ask which explicit next step is due and when. A record without a next unknown is not ready for work because the team cannot tell what evidence would move it.
Review transitions, not averages
At the operating review, inspect records whose evidence changed, whose next review date arrived, or whose transition is disputed. Confirm the source and date, then accept or reverse the movement. Do not discuss average scores, weight changes, or leaderboard totals. The useful output is a queue where every state can be explained from dated evidence.
Worked example
A small sales team adds a company that appears to match its target market. The company page is current, but the accountable buyer is unknown. The record passes the basic company filter and enters research with one question: who owns the relevant decision now?
A dated leadership page later names the responsible person and a current company announcement supports a relevant conversation angle. The record moves to contact. A sent message and successful delivery do not change the state because no buyer action has occurred.
The buyer replies and asks for a short working session. That dated reply moves the record to active. The record now exposes the agreed session date and requested preparation as the next unknowns. If a later reply states that the initiative has been cancelled, the record can move to exclude with that explicit dated reason. The history preserves each transition.
Common mistakes
Renaming a score without changing the logic: a queue fails if people still add points and sort by a hidden total. Remove the total. Use only the state, evidence, and next unknown.
Treating missing information as exclusion: unknown role, missing source, or stale detail belongs in research. Exclude requires a dated disqualifier, not discomfort with uncertainty.
Treating outreach activity as buyer activity: a sent email, connection request, delivered message, or viewed profile describes the seller's action or a platform event. It does not create the active state.
Letting age move records automatically: a review date can trigger inspection. It cannot prove fit, disqualification, or interest. The transition still needs dated evidence.
Erasing history: correcting a source or state should append a new observation. Preserve the previous value, date, and author so the team can reconstruct the decision.
Tools
A shared spreadsheet or simple board is sufficient when it protects the controlled state field and preserves history. Use separate columns for state, state reason, next unknown, evidence URL, observed date, owner, review date, and previous state. Restrict free text to evidence notes. Do not create a hidden numeric column.
HubSpot documents lifecycle stages for a contact or company and a separate Lead Status property for sales sub-stages (official lifecycle-stage documentation). That separation illustrates why the four-state queue should not overwrite the broader customer lifecycle.
When to use this method
Use the queue when a B2B sales team has no marketing operations support, needs a shared work order, and can review the evidence behind each movement. It fits prospecting work where the primary problem is not prediction but deciding what to verify, whom to contact, and which live conversation requires attention.
Use the Structure a Weekly Outbound Review for Small B2B Sales Teams to review disputed or stale transitions on a fixed cadence.
When not to use it
Do not use this queue as automated profiling, a conversion forecast, or evidence of intent. Do not use it if the team cannot verify source data, preserve history, control permissions, or review records at the promised cadence.
Do not add personal data merely to fill the queue. Purpose, lawful basis, minimisation, accuracy, retention, transparency, and rights require separate assessment. This article is an operational method, not legal advice.
Action plan
Write the admissibility rule. Create the four states. Add one next-unknown field and four evidence fields: URL, observation date, author, and previous state. Classify a small working list without points. Reject every proposed transition that lacks dated proof.
During the first review, start with research records because they expose missing data, then inspect contact records with new buyer actions, active records with due next steps, and excluded records with possible reopening conditions. End with named owners and review dates, not a ranking.
Ember data
Lead Intelligence classifies accounts into explained opportunities to watch, act on or set aside.
Lead Intelligence prioritises opportunities from the available context.
Lead Intelligence proposes the next action and channel that fit the lead situation.
These catalogue capabilities can support contextual priority. The four-state queue in this article is an editorial operating model and does not describe a product status field.
After the mission, Lead Intelligence shows the contacts analysed, signals detected and priority actions actually recorded by Ember.
This proof is limited to persisted mission results. It does not replace an absent action with an inferred intent.
Sources and methodology
Status-method sources: HubSpot lifecycle stages and Salesforce lead processes.
Data-control source: ICO accuracy guidance.
Sources were reviewed on August third, two thousand twenty six. The four-state method is an editorial synthesis. Recheck official pages and local legal requirements before use.
Types of sources used: official pages, institutions and named studies.
Sources
FAQ
How should a B2B sales team compare the four queue states without marketing ops?
Compare what work each state permits and which unknown it exposes. Exclude needs a dated disqualifier and any reopening condition. Research names one missing fact. Contact holds a verified route and reason but no observed buyer action. Active holds an observed reply or explicit next step. Do not compare point totals because the method has none. A valid state must be explainable from the current evidence and transition history.
When can a B2B sales team move a lead from research to contact?
Move the record only when dated evidence resolves the named unknowns required for contact. The team should be able to identify the target company, relevant role, usable route, current source, and defensible reason for the conversation. Record the source, observation date, author, and previous state. If one critical fact remains missing or stale, keep the record in research rather than filling the gap with an inference.
How long may a B2B sales team leave a lead in the contact state?
Time alone does not move the record. The team may set a review date based on its outreach policy, but the review must inspect evidence rather than age. A buyer reply or explicit next step can move the record to active. A dated role change, invalid route, or contradictory source can return it to research. An explicit disqualifier can move it to exclude. Silence remains an observed absence, not intent.
Which evidence lets a B2B sales team mark a lead as active?
Require an observable buyer action with a date, such as a substantive reply, accepted meeting, request for material, referral, or agreed next step. Store the action itself and the next commitment. A sent message, successful delivery, public announcement, profile view, fit judgment, or common connection cannot create the active state. Those items may support contact or research, but they do not establish a live conversation.
Can a B2B sales team use message delivery to change a four-state queue?
Delivery proves that a platform accepted or delivered a message under its own definition. It does not prove that the buyer read, understood, or intends to answer. Keep the record in contact unless another dated fact changes the route or validity. If the address bounces, that evidence can return the record to research. If the buyer replies, the observed action can support active. Keep each event separate.
When should a B2B sales team choose exclude instead of research?
Choose exclude when dated evidence establishes a current disqualifier, an explicit request not to continue, an invalid target under the agreed filter, or another documented rule that prevents pursuit. Choose research when a fact is unknown, stale, conflicting, or incomplete. Record whether exclusion is permanent or has a reopening condition. Never use exclusion to hide uncertainty, and never use research to ignore a clear request to stop.