A lead status is useful when a salesperson can point to an observable action or event behind it. Vague labels such as “warm” become unreliable when different teams apply them differently.
The decision sequence
Begin with a real buyer or team task and keep the relevant source record. The worksheet below is meant to expose a decision that someone can check, rather than replace specialist review or claim a Megvi client result.
| Decision point | What to check |
|---|---|
| Write entry rules | For each status specify the event that enters it, the owner and timestamp source. |
| Define exit rules | State what moves a record onward, what closes it and when it returns for follow-up. |
| Keep reasons separate | Use a reason field for no fit, no response or duplicate rather than creating many ambiguous status names. |
| Audit examples | Review real anonymized records with sales and marketing to reconcile disagreements. |
Worked example
Illustrative model: New = form received; Contacted = a logged two-way contact attempt; Qualified = fit criteria confirmed in notes; Proposal sent = dated proposal link; Closed lost = reason and date recorded. “Contacted” should not be applied merely because an automated email fired.
What could change the decision
If statuses are used to judge staff, people may advance records prematurely. Check event evidence, not label counts alone.
Review before using it
Give two reviewers ten anonymized records. If they disagree on status, revise the definition before adding a new dashboard.
Next useful step
Managers can use those stage definitions to spot exceptions in Planning Sales Manager Dashboards Around Exceptions. For help with a live implementation, see Megvi’s CRM development service. Bring the current page, workflow or evidence record and the decision you need to make.