Bookings Baseline

Last updated: February 25, 2026

The Bookings Baseline setting in Grid determines how we attribute bookings when a customer’s ARR changes multiple times in the same reporting period. It ensures that ARR movements are not double-counted and that the sum of all bookings remains accurate and consistent.

What is Bookings Baseline?

Bookings Baseline defines the time anchor used to categorize ARR changes as New, Expansion, Contraction, or Churn within a reporting period. This setting is critical when customers have multiple ARR changes in a short span—especially when changes move both up and down.

For example, a customer might:

Purchase a $10K contract
Expand by $5K two weeks later
Downgrade by $2K at the end of the month

Depending on the Bookings Baseline, these changes may be grouped together or treated as separate events.

Why It Matters

The Bookings Baseline ensures that ARR changes are counted only once. The Bookings Baseline can be configured based on how you want to group and attribute ARR changes:

Option	Description
Month	Groups all ARR changes within a calendar month. Ideal for monthly reporting.
Quarter	Groups all changes within a calendar quarter. Best for quarterly views.
Initial Contract	Anchors all changes to the first event in the period. Ensures attribution consistency for ARR logic.

Example

Let’s say a customer has the following activity in March:

March 2: $10K new contract
March 15: $5K expansion
March 25: $2K contraction

Here’s how it looks under different baselines:

Month:
- New Sales = $10K
- Expansion = $3K (net of $5K – $2K)
Quarter:
- New Sales = $13K (assuming no adjustments in other months)
Initial Contract:
- Entire $13K ARR change is attributed to the original contract and adjusted accordingly