Loading…

Fortive (FTV) backlog: remaining performance obligations

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

Data as of .

Fortive backlog history

$0$2B$4B$6BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025ul 2026ct 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
2 Oct 2026$843M$4.40B0.2 yrs$473M
3 Jul 2026$825M$4.32B0.2 yrs$477M
3 Apr 2026$840M$4.24B0.2 yrs$472M
31 Dec 2025$841M$4.16B0.2 yrs$464M
26 Sep 2025$811M$4.11B0.2 yrs$436M
27 Jun 2025$813M$4.09B0.2 yrs$628M
28 Mar 2025$783M$4.09B0.2 yrs$619M
31 Dec 2024$762M$4.08B0.2 yrs$433M
27 Sep 2024$728Mn/an/a$560M
28 Jun 2024$705Mn/an/a$564M
29 Mar 2024$712Mn/an/a$586M
31 Dec 2023$723M$3.91B0.2 yrs$590M

Questions

What is Fortive's backlog?
Fortive reported $843M of remaining performance obligations at 2 Oct 2026, up 4% from a year earlier and up 2% from the previous quarter. That is 0.2 years of trailing revenue already under contract. Book-to-bill last quarter: 1.02.
How fast does Fortive's backlog turn into revenue?
Over the last twelve months Fortive recognised revenue equal to about 531% 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.