Bookings Backlog Changes
Structured bridge that reconciles opening bookings backlog to closing backlog through the period's new bookings, conversions to revenue, post-contract losses, and value adjustments (starting + new − converted − lost + increases − decreases = ending). The bespoke sales card reads this typed object to show the backlog motion. Distinct from the editor's `sales.bookings_backlog_total` FlowSubform container — this is the typed `IBookingsBacklog` the feed card consumes. Common pitfall: an ending value that does not reconcile because conversions to recognized revenue were not netted out. — 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_changes
Type: Text
Domain: Sales
Definition
Structured bridge that reconciles opening bookings backlog to closing backlog through the period's new bookings, conversions to revenue, post-contract losses, and value adjustments (starting + new − converted − lost + increases − decreases = ending). The bespoke sales card reads this typed object to show the backlog motion. Distinct from the editor's sales.bookings_backlog_total FlowSubform container — this is the typed IBookingsBacklog the feed card consumes. Common pitfall: an ending value that does not reconcile because conversions to recognized revenue were not netted out.
Formula
Container — { startingBackLogValue, newBookingValue, bookingsConvertedToRevenue, lostBookingsPostContract, backlogValueIncreases, backlogValueDecreases, endingBackLogValue, netChange, netChangePercent }. Identity: starting + new − converted − lost + increases − decreases = ending.Why it matters
Makes signed-but-not-yet-recognized revenue auditable — a growing backlog is forward revenue visibility; a shrinking one (conversions outpacing new bookings) is an early top-of-funnel warning.
How to interpret
When conversions consistently exceed new bookings, the backlog erodes and future recognized revenue will soften. Disproportionate post-contract losses signal delivery or scoping problems.
Related KPIs
sales.bookings_backlog_totalsales.bookings_backlogsales.arr
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 stage | Priority |
|---|---|
| Series A | Recommended |
| Series B | Recommended |
| Series C+ | Recommended |
| Public | Recommended |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- Sales
- Finance
Machine-readable
- This KPI as JSON:
/api/ontology/sales/bookings_backlog_changes.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
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).
Bookings Backlog Total
Total dollar value of all signed contracts that have not yet been recognized as revenue — the visibility window into future revenue at a point in time. Closely related to sales.bookings_backlog; this entry serves as the FlowSubform `start` slot for the per-period bookings-backlog flow (open + new bookings − recognized − cancellations = close). Common pitfall: omitting cancellations from the flow leaves a phantom backlog that overstates future revenue visibility — every backlog flow needs an explicit cancellation line even when zero. — Sales KPI, I'mBoard-authored (editorial tier).