I'mBoardDocs
Board OntologySales

Bookings Backlog

Total value of signed contracts that have not yet been recognized as revenue — future revenue locked into the books. Equivalent to "remaining performance obligation" (RPO) in public-SaaS disclosures, though private companies often track only the in-period portion. Board reads this as the visibility horizon: a healthy backlog means recognized revenue is largely already-sold and not dependent on Q-end heroics. Common pitfall: confusing backlog with pipeline — backlog is contractually committed, pipeline is unsigned opportunity. Surface the two on the same dashboard but never sum them. — Sales KPI, I'mBoard-authored (editorial tier).

I'mBoard-authored (editorial tier)

No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.

Rogue ID: sales.bookings_backlog Type: Currency Domain: Sales

Definition

Total value of signed contracts that have not yet been recognized as revenue — future revenue locked into the books. Equivalent to "remaining performance obligation" (RPO) in public-SaaS disclosures, though private companies often track only the in-period portion. Board reads this as the visibility horizon: a healthy backlog means recognized revenue is largely already-sold and not dependent on Q-end heroics. Common pitfall: confusing backlog with pipeline — backlog is contractually committed, pipeline is unsigned opportunity. Surface the two on the same dashboard but never sum them.

Formula

Bookings Backlog = TCV of all signed customer contracts − Revenue already recognized against those contracts. For a SaaS business, the dominant component is unrecognized subscription value on multi-month / multi-year contracts. Most-comparable public-disclosure equivalent: ASC 606 Remaining Performance Obligation (RPO).

Why it matters

The single best read on next-period revenue predictability — high backlog means the revenue line for the coming quarter is largely contractual, not pipeline-dependent. Boards use it to gauge whether the team is selling for in-quarter close or building durable forward visibility.

How to interpret

Backlog at year-end ≥ 1.0× the next year's ARR plan is the "visible year" threshold most boards expect at Series B+ subscription companies (industry folk-wisdom — no single published standard; the underlying conventions derive from ASC 606 RPO disclosure norms in public-SaaS filings). Backlog declining as a share of forward plan = visibility eroding; usually demands a sales-cycle or pipeline-coverage drill-down.

  • sales.bookings_backlog_total
  • sales.total_revenue
  • sales.arr
  • sales.carr
  • sales.pipeline_value
  • sales.weighted_forecast

Source

I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.

Stage relevance

Company stagePriority
Series ARecommended
Series BCore
Series C+Core
PublicCore

Suggested for stages: Series A, Series B, Series C+, Public.

Default owning functions

  • Sales
  • Finance

Machine-readable

On this page