What are pipeline hygiene standards?
A short set of enforceable rules about what an open opportunity must contain and how long it can sit without moving.This is narrower than CRM data governance and that narrowness is the point. Governance covers every object and every field, takes a year to roll out, and gets partially adopted. Pipeline hygiene covers open opportunities and about six fields, which makes it enforceable in a quarter.
The purpose is not tidiness. Every number that drives a revenue decision is calculated from open opportunity records. Coverage, forecast, capacity plans, and quota models all inherit whatever condition those records are in.
Which fields need a standard?
Stage, close date, amount, next step, and the primary buyer contact.Everything else is useful and none of it changes a forecast. Restrict the standard to fields that alter a number.
| Field | Rule | Fails when |
|---|---|---|
| Stage | Must match documented exit criteria for that stage | Stage advanced with no buyer evidence recorded |
| Close date | Must be in the future and revisited at each stage change | Date is in the past or unchanged since creation |
| Amount | Must reflect quantity and term under discussion | Amount equals the opening ask with no configuration |
| Next step | Must contain an action and a date | Blank, or wording with no date attached |
| Buyer contact | At least two named contacts above median deal size | Single-threaded on a large deal |
| Source | Must use a controlled picklist value | Free text or "other" |
Which rules are worth enforcing?
The ones with a defined threshold and an automatic consequence.Start with six.
No stage, close date, or amount change in 30 days flags the deal for manager review.
No such change in 90 days removes the deal from the forecast while leaving it open.
No such change in 12 months closes the deal as lost automatically. That threshold holds up against how opportunities actually behave. When deals are grouped by pattern and each group gets a predicted time-to-close curve, those curves run from one week to eighty weeks with most closing expectation before week twelve, and very few groups carry expectation past week fifty-two.
A close date in the past triggers a required update before the record appears in any forecast view.
A close date moved twice on the same deal triggers a manager decision about whether it stays in the forecast. Rep-initiated close date movement is the strongest available signal that a deal is in trouble, and the second move deserves a decision rather than an acknowledgment. Track the pattern through deal slippage.
An amount that sits more than a defined multiple above the closed-won average for that segment triggers a validation step. A pipeline can carry an $80,000 average open deal size against a $40,000 average closed-won deal size, and that gap propagates into every forecast built on the pipeline value.
How do you enforce without adding admin work?
Enforce at the point of change and automate everything else.Validation rules at save time cost a rep seconds. A weekly hygiene report costs a rep an hour and produces resentment along with compliance theater.
Three mechanics do the work.
Required fields on stage advance rather than on record creation. Asking for close plan detail at the moment a deal enters qualification is asking for fiction. Asking at the move into proposal is asking for something the rep already knows.
Automated flagging that runs continuously and posts to the rep before the review, not during it. The flag is the reminder, so the meeting does not have to be.
Automatic status changes on the thresholds above, with a manager override path. The default is the rule and the exception requires a written reason.
What this replaces is worth naming. Manual forecast assembly is expensive. Forecast accuracy on new and expansion business typically lands near 90 percent when produced by hand, and it takes significant effort while staying static as conditions change. Hygiene automation is what makes a dynamic alternative possible.
What should happen when a deal fails a rule?
Something automatic, visible, and escalating with age.| Failure | Consequence | Owner |
|---|---|---|
| 30 days no movement | Flag posted to rep, dated next step required | Rep |
| 90 days no movement | Removed from forecast, stays open | RevOps automated |
| 6 to 12 months no movement | Closed as lost unless manager documents a reason | Manager |
| Over 12 months no movement | Closed as lost automatically | RevOps automated |
| Close date in past | Excluded from forecast views until corrected | RevOps automated |
| Second close date move | Manager decision on forecast inclusion | Manager |
Who owns pipeline hygiene?
RevOps owns the rules and the automation. Managers own exceptions.Reps own their records but should never own the judgment call about whether a record survives. The deals hardest for a rep to close as lost are the ones with the most invested effort, which are usually the stalest ones in the book.
Managers get one lever, which is documenting an exception with a dated buyer action attached. Anything else and the rule stops being a rule.
Publish the standard as one page. If it does not fit on one page, it will not be followed.
How do you measure hygiene?
Track the share of open pipeline that passes every rule, weekly, by team.That single percentage is more useful than a dozen field-completeness scores. Set a floor, report it alongside coverage, and let the trend do the arguing.
Two supporting measures. The count of deals closed as lost by rule versus by rep decision, which shows whether the automation is doing the work it was built for. Then forecast accuracy over the following two quarters, which is the reason the standard exists.
One objection comes up every time, which is that the data is too messy for any of this to matter. It is not a real objection. Everyone has messy data, and garbage in does not have to mean garbage out. Consistency is what makes prediction possible, and consistency is exactly what a hygiene standard produces. The wider practice is covered in sales forecasting best practices.
Frequently Asked Questions
What are pipeline hygiene standards?
A short set of rules that define what an open opportunity must contain and how long it can go without movement. They apply to open pipeline specifically, which is narrower than CRM data governance and easier to enforce because the rules attach to a small number of fields.
How many hygiene rules should you have?
Five to seven. Longer lists get partially enforced, and partial enforcement teaches reps that the rules are optional. A short list with automatic consequences changes behavior faster than a comprehensive policy nobody applies.
Should hygiene rules be based on activity counts?
No. Logged calls and emails are easy to produce without a deal advancing, so activity rules get satisfied within a week of being announced. Test against a change in stage, close date, or amount instead.
Who owns pipeline hygiene?
RevOps owns the rules and the automation. Frontline managers own exceptions and sign-offs. Making individual reps responsible for judgment calls guarantees the deals most in need of cleaning are the ones with the most effort invested in them.
What happens when a deal fails a hygiene rule?
Something automatic and visible, escalating with age. Flag first, remove from forecast next, close as lost last. A rule with no consequence is a suggestion, and suggestions do not change a pipeline.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo