Stage dictionary template (definition → next action → SLA → exit)

Use this table as your baseline stage dictionary. Customize labels if you want, but keep the structure: one meaning, one next action, one time expectation, one stage exit trigger.

What are lead statuses supposed to solve?

A lead status is not a label. It’s the current working state of a lead plus what must happen next. If two people use the same stage to mean different things, you don’t have a pipeline—you have opinions.

“Good” lead statuses do three jobs: they create clarity, they drive action, and they make performance measurable. If a stage can’t tell you what to do next, it’s not helping.

Lead status vs lifecycle stage vs deal stage (keep them separate)

Most pipeline confusion happens when these three are used interchangeably. They are not the same thing, and they should not change at the same time.

Deal stage

What is happening inside a specific transaction.

Answers: Where are we in this deal process?

• Appointment Set
• Offer Made
• Under Contract
• Closed

Deal stage applies once the opportunity is real. It tracks transaction progress, not outreach activity.

What breaks when you mix them

• Automations trigger at the wrong time.
• SLAs become unclear or unenforceable.
• Handoffs get messy (“who owns this now?”).
• Reports stop matching reality.

Practical rule: lead status tracks follow-up activity, lifecycle stage tracks relationship category, and deal stage tracks transaction progress.

The minimal set of lead stages (no 30-stage nonsense)

The goal is not to describe every nuance of a conversation. The goal is to run follow-up cleanly with predictable rules. If you can’t explain a stage in one sentence plus one next action, it doesn’t deserve to exist.

• New (no attempt logged yet)
• Attempted Contact (attempt logged, no connection yet)
• Connected (two-way communication happened)
• Qualified (Working) (actively progressing toward a next step)
• Appointment / Next Step Scheduled (specific next step exists)
• Follow-Up Needed (Timed) (explicit follow-up time scheduled)
• Nurture (Long-Cycle) (slow cadence)
• Dead / Unqualified (closed out with a reason)
• Closed Won (optional, if you track closes in this pipeline)

What “Attempted Contact” actually means (and how long it can live)

“Attempted Contact” should mean one thing: you tried to reach the lead, but you did not connect. It is not a parking lot.

Exit criteria examples that prevent stage rot

Exit criteria is the specific event that moves a lead out of a stage. Without it, stages drift into “vibes,” and your CRM stops reflecting reality.

• New → Attempted: first outreach attempt is logged.
• Attempted → Connected: two-way communication occurs (call connects or message exchange).
• Connected → Qualified: basic criteria confirmed and a next step is defined.
• Qualified → Appointment/Next Step Scheduled: a specific appointment or action is scheduled.
• Any active stage → Follow-Up Needed: lead is not ready now or they've been asked for additional information. Timed follow-up is scheduled.
• Any active stage → Nurture: lead is not ready now and should move to a slow cadence.
• Any stage → Dead/Unqualified: clear “not a fit” reason logged (not silence).

The goal is not perfect categorization. The goal is that the team can look at a stage and immediately know what must happen next.

Stage hygiene rules that keep the pipeline truthful

Definitions only work when they’re enforced. These rules prevent “stage rot” and keep your pipeline usable for decision-making.

Common failure modes and fixes

• Stages used as emotions (“hot/warm/cold”) instead of states. Fix: temperature is a field; stages are actions + exits.
• “Attempted Contact” becomes a graveyard. Fix: time-box Attempted + force a next step (retry schedule, nurture, or dead).
• No exit criteria → stage rot. Fix: every stage has a single “moves when X happens” rule.
• Duplicate stages that mean the same thing. Fix: collapse into one status; log attempts as activities.
• No required next action → follow-up is optional. Fix: “no next action due time = invalid record.”
• People move stages to make reports look good. Fix: stage changes are tied to observable events.
• Different team members interpret statuses differently. Fix: publish the stage dictionary and enforce it weekly.
• Closed outcomes aren’t standardized (dead vs unqualified vs bad timing). Fix: separate “not a fit” from “not now” with explicit reasons.

Weekly pipeline hygiene review (15 minutes)

The goal is not to shame people for misses. The goal is to keep the system accurate enough to run the business. A short weekly review is how you prevent slow decay.

If nobody owns this weekly loop, your CRM will drift. That’s why many teams assign stage hygiene to ops or CRM support instead of the acquisitions closer.

How to staff stage hygiene so it actually happens

Stage hygiene is an operations function: consistency, clean logging, and tight handoffs. It’s not “deal work,” and it shouldn’t compete with appointments, negotiations, or closings.

Lead Status Dictionary + Hygiene SOP (One-Page Template)

1. Approved Stage List (Minimal Set)

• New
• Attempted Contact
• Connected
• Qualified / Working
• Appointment / Next Step Scheduled
• Follow-Up Needed (Timed)
• Nurture
• Dead / Unqualified
• Closed Won (optional)

2. Stage Dictionary (Complete for Each Stage)

3. Required Fields on Every Open Lead

• Assigned Owner
• Next Action
• Next Action Due (timestamp)
• Last Touch Date
• Lead Source

4. Stage Hygiene Rules

• One owner per lead.
• No open lead without a next action due time.
• No stage change without a logged event.
• Attempted Contact is time-boxed.
• Dead / Unqualified requires a reason.
• Weekly stale-stage cleanup is mandatory.

5. Weekly Hygiene Review

• Review leads with no next action.
• Review SLA misses by stage.
• Review oldest leads in each stage.
• Update definitions if confusion repeats.

6. Exception Policy

Exceptions to stage definitions must be approved by: ______________________

FAQ