Pipeline inflates when a stage change costs nothing. Below is a Lightning-style Opportunities list view with a record page beside it. Pick a record, choose a stage on the Path and click Mark as Current Stage, and watch a validation rule and a Flow decide. Fix the fields and try again, or switch the rule off to see what an unguarded save lets through.
In a real environment
Data sources
- Standard Opportunity fields: StageName, Amount, CloseDate, NextStep and LeadSource.
- OpportunityContactRole for contact roles, checked in a Flow because a validation rule reads the record and its parents, not child rows.
- A handful of custom fields per stage (the __c names here are illustrative), chosen with sales leadership.
- Opportunity stage history for measuring the effect afterwards.
Limits and prerequisites
- The stage values in the formulas must match the picklist values in the org: confirm in the target org.
- Validation rules also run on API saves and data loads, so integrations need a bypass such as a custom permission: confirm in the target org.
- The rule fires when the stage changes, in either direction, so open opportunities already in a stage are not blocked until they move.
- Path shows up to five key fields and up to 1,000 characters of guidance per stage, but it does not enforce anything by itself.
- An error location of a field falls back to Top of Page if that field is not on the page layout. A Flow Custom Error message is limited to 255 characters.
- List view search covers only the first 2,000 records in the list.
How it would be validated
- Sandbox tests per stage, including jumping over stages, moving backwards, bulk updates and an integration user.
- A pilot with one team, reviewing the error messages with the reps who see them.
- Before and after comparison of stage changes and time in stage from opportunity history reports, with the same filters.
Standard Salesforce behavior on this screen: list view search, column sorting and filters, the Path with its key fields, the Mark Stage as Complete and Mark as Current Stage buttons, validation rule errors, and the Flow Custom Error element. Illustrative: the Gaps column, the Inflated and Ready to advance filters, the Setup, Flow and Why tabs beside the record, the custom fields, the stage criteria and all data.
What this demo does not claim: that these checklist items fit your sales process, that enforcement improves forecast accuracy by any amount, or that every stage needs every check. Each item has a cost for the rep, so start with the few that the forecast review actually asks about.
References: Sample opportunity management validation rules, Tips for writing validation rules, Validation rule best practices on Trailhead, Flow Custom Error element, Create a Path, Work with an opportunity record on Trailhead, Search list views, Sort list views. Check current vendor documentation before relying on any figure.