How do you calculate pipeline coverage in Salesforce?
Divide the total amount of open opportunities with close dates inside the period by the revenue target for that period, using a summary Opportunity report for the numerator and a quota record for the denominator.``` Pipeline coverage = Open pipeline in period / Revenue target for period ```
Salesforce ships neither half of that calculation as a ready-made field. It stores opportunity amounts, and it stores quotas if Collaborative Forecasts is turned on, but the ratio between them is something you assemble. The base definition and the reasons the ratio matters are covered in pipeline coverage.
Which report should you build first?
A summary-format report on the standard Opportunities report type, grouped by opportunity owner and then by stage. Start there rather than with a dashboard, because the report is where the filter logic lives and every downstream component inherits it.Group by owner first if you plan to hold reps accountable to individual coverage. Group by stage first if you want to see where the value sits in the funnel, which is the more useful cut for deciding what to do next. Add a second grouping either way, since a single-level summary hides the composition that determines whether the ratio means anything.
Avoid report types that join opportunity products or activities. An opportunity with four product line items returns four rows, and the amount column sums four times. That mistake alone can double a reported coverage ratio.
Which filters keep the ratio honest?
Five filters do most of the work, and leaving any of them out inflates the numerator.| Filter | Setting | Why it matters |
|---|---|---|
| Close Date | Current fiscal quarter | Future-dated deals cannot cover this period |
| Opportunity Status | Open | Closed won and closed lost belong in a different report |
| Last Stage Change Date | Within 90 days | Removes opportunities nobody has worked |
| Amount | Greater than zero | Blank amounts silently drop out of the sum |
| Record Type | Revenue-bearing types only | Excludes internal or test record types |
Where does the quota number come from?
From forecasting quota records when Collaborative Forecasts is enabled, and from a custom object or custom setting when it is not. Quotas load per user per period, which lets a report divide each owner's open pipeline by their own number rather than against a team average.If quotas do not live in the org, the common workaround is hard-coding the target inside a custom summary formula. That works and it fails quietly. Nothing in Salesforce alerts you when the plan changes and the formula still holds last quarter's number, so the ratio keeps reporting cleanly while pointing at the wrong denominator. Put the target in a record that someone owns and can update.
How do you display coverage on a dashboard?
Build a custom summary formula that divides the summed amount by the target, then surface it in a gauge or metric component. The formula runs at the summary level, so it produces one ratio per grouping rather than a single blended figure. That is the right output. A team-level ratio of 3.4x can hide one rep at 6x and another at 1.2x, and only the second one is a problem you can still solve.Set the gauge breakpoints from your own conversion history rather than a default. Across ORM customer data, 3x to 5x is the standard range and most companies sit around 3.5x, but that range describes what teams typically carry, not what any specific team needs. Required coverage is the inverse of the close rate, so a business that converts qualified pipeline at 33% needs 3x while one converting at 20% needs 5x to reach the same revenue.
Why does the Salesforce ratio disagree with what actually happens?
Because the report prices the pipeline you can see, and the quarter is also made of pipeline that does not exist yet. Across ORM customers, roughly 20% of the value carrying in-quarter close dates on day one of the quarter closes inside that quarter. The remaining 80% slips, shrinks, or dies.A report cannot see business that will be created and closed inside the same period, and it cannot see deals pulled forward from later quarters. Both are real sources of revenue, and both are invisible to any calculation built on current records. The habit of reading the ratio as an answer rather than an input is the failure mode described in why the 3x pipeline coverage rule is wrong.
What can Salesforce not do with this metric?
It cannot tell you whether the pipeline in the report is worth its stated amount. The report sums what reps entered. It is common to see an open pipeline averaging $80,000 per deal while closed-won deals average $40,000, and no standard report flags that gap because both numbers are technically correct.The platform also has no native view of close-date movement over time. A deal that has been pushed from Q1 to Q2 to Q3 appears in the current report as clean in-quarter pipeline, with the pattern visible only in field history. That pattern is the strongest early warning available, since a rep changing a close date is the clearest signal a deal is drifting. Tracking deal slippage alongside coverage turns a static ratio into something that predicts the quarter instead of describing it.
Frequently Asked Questions
Is there a standard pipeline coverage field in Salesforce?
No. Salesforce stores open opportunity amounts and, if Collaborative Forecasts is enabled, quota records. The ratio between them has to be built with a summary report and a custom summary formula, or calculated in a dashboard component that references both.
Which report type should I use for pipeline coverage?
The standard Opportunities report type in summary format, grouped by owner or stage. Avoid report types that join products or activities, because a single opportunity with four line items will be counted four times and inflate the numerator.
Why does my Salesforce coverage number look higher than reality?
Three filters are usually missing: close dates outside the period, opportunities with no recent stage or amount change, and duplicate rows from a joined report type. Each one adds pipeline that will not convert inside the period being covered.
Where does the quota come from in a Salesforce coverage report?
From the forecasting quota records if Collaborative Forecasts is enabled, or from a custom quota object or custom setting if it is not. Many teams hard-code the target into a custom summary formula, which works but breaks silently every time the number changes.
Can Salesforce weight the pipeline by stage conversion rate?
Only through the probability field on each stage, which is a static configuration value rather than a measured conversion rate. Producing a genuinely weighted ratio requires calculating close rates from historical opportunity data outside the standard report builder.
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