ARR backlog tracks contracted annual recurring revenue that has yet to be delivered or recognized. It reflects signed customer commitments—not a quarterly forecast—and may include renewals and expansions. See how this measure connects future delivery with revenue recognition in a subscription business.

Multiple Choice

Which statement best describes ARR backlog?

The main idea being tested is what ARR backlog actually represents. ARR backlog is the portion of contracted Annual Recurring Revenue that hasn’t been delivered to the customer yet or recognized as revenue. It’s about signed commitments that will convert to revenue in future periods as delivery occurs or as the subscription runs its course. That’s why the best choice says backlog represents contracted ARR that has not yet been delivered or recognized. It’s not the current term’s approved forecast, nor forecasted ARR for the next quarter, because those are forward-looking projections, not the unfilled portion of contracted revenue. And it isn’t limited to non-renewing contracts; backlog includes all contracted ARR awaiting delivery or recognition, including renewals and expansions.

Understanding ARR Backlog in a Subscription Business

Annual recurring revenue, or ARR, is a useful way to describe the steady subscription revenue a business expects from its customers. But ARR doesn’t tell the whole story. A company may have signed a customer contract even though some of the service hasn’t been delivered yet. That gap is where ARR backlog comes in.

ARR backlog represents contracted recurring revenue that has not yet been delivered or recognized. It reflects commitments already made by customers, not revenue the business merely hopes to earn. That distinction matters when leaders assess growth, plan delivery, and explain the company’s financial position.

A signed commitment, not a prediction

Picture a customer who signs a two-year subscription agreement in December. The contract is binding, but the subscription service begins in January. Until delivery starts, the company has a contracted commitment that has not yet been fulfilled. Depending on how the business defines and tracks its metrics, that amount may be included in ARR backlog.

The key point is that backlog comes from an existing contract. A sales forecast for a possible customer may be useful for planning, but it isn’t backlog. The customer hasn’t committed, so the revenue remains uncertain.

This is why ARR backlog shouldn’t be confused with a forecast for the next quarter or an approved budget estimate. Forecasts describe what a company expects might happen. Backlog describes contracted business that is still waiting to be delivered or recognized. One looks ahead based on assumptions; the other starts with a signed commitment.

Why the word “backlog” matters

In everyday terms, backlog suggests work that’s been agreed to but hasn’t been completed. A furniture maker might have orders for tables that are still on the production line. A software company has a different kind of delivery, but the basic idea is similar: the customer has committed, and some part of the promised service remains ahead.

For subscription businesses, that remaining service can span months or years. A customer might sign a contract today for access that begins later, or agree to a multi-year subscription that earns revenue over time. In both cases, the contract’s value and the revenue recognized in a given period are not necessarily the same thing.

That’s because recurring revenue is usually recognized as the company provides the service—not all at once when the customer signs. If a subscription runs for twelve months, the business generally recognizes revenue over the period in which it delivers access. The timing depends on accounting rules and the contract’s terms, so companies should be clear about what their ARR backlog metric includes.

Backlog, ARR, and recognized revenue: related, but not identical

These measures can sound alike, especially in a dashboard full of sales and finance metrics. They answer different questions, though.

  • ARR estimates the annualized value of active recurring subscriptions at a particular point in time.

  • Recognized revenue is revenue recorded as the company delivers goods or services, following applicable accounting rules.

  • ARR backlog tracks contracted recurring revenue that has not yet been delivered or recognized, based on the company’s stated definition.

  • Forecasted ARR estimates future recurring revenue from expected sales, renewals, or other changes that haven’t all become contracted commitments.

The boundaries can vary by company. For example, one business may include a signed subscription that begins next month in its backlog metric; another may report it separately until service starts. Contract changes, cancellation terms, implementation delays, and how the company treats renewals can all affect the calculation.

So, when comparing ARR backlog figures across businesses, don’t assume the labels mean exactly the same thing. Check the metric definition. A number without its rules is a bit like a map without a legend: it may look precise, but it’s easy to misread.

What belongs in ARR backlog?

At its core, ARR backlog covers contracted recurring revenue that is still awaiting delivery or recognition. It isn’t restricted to contracts that won’t renew. A renewal or expansion can contribute if it represents a committed amount that has not yet been delivered or recognized and meets the company’s criteria.

Consider a customer that renews for another year, with the new term starting after the current subscription ends. The renewed commitment may appear in a backlog measure if the business records future contracted ARR that way. An expansion works similarly: if a customer signs for additional seats or services that will begin later, that contracted value may be included.

By contrast, a renewal that’s merely expected—but hasn’t been agreed to—belongs in a forecast, not contracted backlog. The difference may seem small on a spreadsheet. In business reporting, it’s a major one. Treating expected revenue as committed revenue can make a company’s future position look firmer than it really is.

Why teams pay attention to it

ARR backlog gives teams a view of future contracted business that has not yet turned into delivered or recognized revenue. That can help finance teams estimate how revenue may develop over time, while customer success and delivery teams can see what commitments are coming their way.

For instance, a sharp rise in backlog may point to strong contracting activity. It may also signal that delivery capacity needs attention. If many customer subscriptions are scheduled to begin in the same period, support, onboarding, or infrastructure teams may need to plan accordingly. A crowded runway can be encouraging, but the business still has to help those customers get airborne.

Backlog can also support discussions about revenue timing. A company with a large backlog may have meaningful contracted commitments ahead, yet those commitments don’t automatically equal cash on hand or revenue already earned. Payment schedules vary, and delivery still has to occur. That’s why backlog is best read alongside other measures, such as ARR, recognized revenue, cash collections, and retention.

What ARR backlog does not tell you

A backlog figure can be useful, but it isn’t a complete picture of business health. It doesn’t, on its own, show whether customers are satisfied, whether delivery will happen on schedule, or whether every contract will remain unchanged. Contracts may be amended, delayed, or canceled under certain terms.

Nor does backlog necessarily tell you when revenue will be recognized. Two companies with the same backlog might have very different contract start dates or service schedules. One might recognize much of it soon; the other may recognize it over a longer stretch.

For that reason, teams should pair the number with context. Useful questions include: What contract types are counted? Are future renewals included only after signature? How are expansions handled? Does the figure reflect start dates, delivery milestones, or another trigger? These details help readers understand what the metric can—and can’t—support.

Clear definitions make the metric useful

ARR backlog is most helpful when the company defines it consistently and explains how it relates to its other revenue measures. A clear definition lets leaders compare periods, spot shifts, and coordinate around upcoming commitments without mixing signed contracts with hopes and estimates.

The simplest distinction is also the most important: backlog is grounded in contracted business that has not yet been delivered or recognized. A forecast points to possible future business. Recognized revenue reflects service already delivered under the relevant accounting rules. They may all speak to growth, but they speak from different points in time.

Once those lines are clear, ARR backlog becomes easier to interpret. It shows a slice of the road ahead—one built from commitments already made, with delivery and revenue recognition still to come.