Loading…

Gartner (IT) backlog: remaining performance obligations

How much revenue Gartner already has under contract, how fast it converts, and who it is with.

Data as of .

Gartner backlog history

$0$2B$4B$6BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$6.30B$6.44B1.0 yrs$2.60B
30 Jun 2026$6.50B$6.46B1.0 yrs$2.78B
31 Mar 2026$6.60B$6.47B1.0 yrs$3.05B
31 Dec 2025$6.40B$6.50B1.0 yrs$2.84B
30 Sep 2025$6.10B$6.46B0.9 yrs$2.55B
30 Jun 2025$6.10B$6.42B1.0 yrs$2.71B
31 Mar 2025$6.10B$6.33B1.0 yrs$2.95B
31 Dec 2024$6.40B$6.27B1.0 yrs$2.79B
30 Sep 2024$5.70B$6.14B0.9 yrs$2.59B
30 Jun 2024$5.60B$6.06B0.9 yrs$2.65B
31 Mar 2024$5.60B$5.97B0.9 yrs$2.82B
31 Dec 2023$5.60B$5.91B0.9 yrs$2.67B

Questions

What is Gartner's backlog?
Gartner reported $6.30B of remaining performance obligations at 30 Sep 2026, up 3% from a year earlier and down 3% from the previous quarter. That is 1.0 years of trailing revenue already under contract. Book-to-bill last quarter: 0.87.
How fast does Gartner's backlog turn into revenue?
Over the last twelve months Gartner recognised revenue equal to about 101% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.