Backlog Coverage
Backlog coverage is the ratio of contracted, undelivered work to a target revenue period, expressed in months, indicating a firm's near-term revenue security.
Backlog coverage is the ratio of contracted but undelivered work to a target revenue period, expressed in months, showing how many months of revenue a firm has already secured. It is the clearest single number for assessing near-term revenue security.
The formula
Backlog coverage (months) = Total backlog / Average monthly revenue
If the backlog is $1.8M and average monthly revenue is $450K, backlog coverage is 4 months.
Why it matters
Backlog coverage separates delivery firms that know their next 90 days from those that are guessing. A firm with 5 months of coverage can staff confidently, negotiate hiring timelines, and plan partner compensation without worrying that one stalled deal disrupts the quarter. A firm with 6 weeks of coverage is one missed close away from a capacity crisis.
Backlog coverage is most useful when tracked alongside pipeline coverage, because the two together show whether the full revenue funnel is healthy or just one end of it. A firm can have strong pipeline coverage and weak backlog coverage, meaning deals are in discussion but not yet signed. The inverse, strong backlog and weak pipeline, means near-term revenue is secure but the horizon beyond three to four months is thin.
Backlog coverage vs. pipeline coverage
Backlog coverage counts only work that is contracted and unconditional: signed SOWs, executed engagement letters, and authorized change orders. Pipeline coverage counts probable future work that has not yet been won. The two metrics together show the full revenue horizon. Tracking only one gives an incomplete picture: pipeline converts at less than 100%, and backlog can erode through project cancellations, scope reductions, or write-offs.
Healthy vs. at-risk coverage ratios
| Coverage | Signal |
|---|---|
| Below 1 month | Critical gap, revenue at immediate risk |
| 1 to 2 months | Tight, dependent on pipeline closing quickly |
| 3 to 5 months | Healthy, sufficient buffer for delivery ramp-up |
| 6-plus months | Strong, but watch for capacity bottlenecks |
How to improve backlog coverage
- Shorten sales cycles by standardizing SOW templates and approval flows
- Pursue retainer and renewal contracts that add predictable future backlog
- Monitor coverage by practice area, not just firm-wide, to catch localized gaps early
Tracking budget burn on active projects alongside backlog coverage helps ensure that signed work translates into recognized revenue on schedule.
From concept to workflow
Servantium helps services teams turn these operating concepts into repeatable workflows.
See how Servantium works