> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beaconrevenue.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What Beacon measures about a stage

> The five things Beacon measures about any stage rail — pace, dwell, pass-through, health and how a group moves together — and which of them are published today.

A stage rail on its own tells you where a record is. The useful questions are about movement — how fast, how long, how many get through. Beacon answers those five ways, and only five.

<Note>
  This page describes the measurement model. Some of the five already have a published value, linked below; others do not.
</Note>

## The five

| What it measures | The question it answers | Published today |
| - | - | - |
| Pace | How quickly a record is moving relative to comparable records | [`deal_velocity_percentile`](/definitions/deal-velocity-percentile) |
| Dwell | How long it has sat where it is | [`days_in_stage`](/definitions/days-in-stage) |
| Pass-through | What share of records get from one stage to the next | Not published |
| Stage health | How well a record is progressing against the pace typical for its segment | [`health_score`](/definitions/health-score), [`deal_health`](/definitions/deal-health) |
| Group progression | How a set of records that started together is moving as a set | [`cohort_net_revenue_retention`](/definitions/cohort-net-revenue-retention), [`cohort_gross_revenue_retention`](/definitions/cohort-gross-revenue-retention) |

Group progression is published as the pair of retention figures for a cohort — how much revenue a group that started together keeps, and how much it keeps and grows. Neither is one number: each is a curve, one point per month of the cohort's life, and [the cohort object](/data-model/cohort) sets out how they are served.

Pass-through is still measured and still has no published value — stated here rather than left as a gap you would find by looking for it.

## What makes them comparable

**Stages are ordered.** A rail is a sequence, so "further along" means something and pace can be compared between records at different points.

**A move is a dated event.** Every measure above is derived from recorded transitions, not from anyone's assessment of where a record has got to. See [What changes when a stage changes](/lifecycles/what-changes-when-a-stage-changes).

**A rail has an end, and it has exits.** Records reaching the final stage stop accruing pace and dwell. Records that leave early — a lost deal, a churned account — leave through a named exit rather than sitting indefinitely in the stage they were in. Without that, dwell on a rail slowly fills with records that stopped moving months ago.

**The benchmark is the segment, not the average.** All five read against what is typical for records like this one. A 40-day enterprise stage and a 40-day SMB stage are not the same event.

## What none of them do

No measure here works out its own version of where a record has reached. They all read the stage the owning system published, which is why two Beacon figures never disagree about a record's position — there is only one answer for them to read.

## Related

<Columns cols={3}>
  <Card title="How a customer moves through Beacon" href="/lifecycles/overview">
    The two stage rails these measures run over.
  </Card>

  <Card title="What changes when a stage changes" href="/lifecycles/what-changes-when-a-stage-changes">
    The transition that every measure is derived from.
  </Card>

  <Card title="Definitions" href="/definitions/overview">
    Each published value in full.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.