What it is
contract_coverage_rate is the share of your running subscriptions that rest on a contract — a signed contract, or the standard online terms a customer accepted at sign-up — as a ratio between 0 and 1. The rest rest on billing alone: Beacon knows the start date, the product and the revenue, and nothing of the terms. It is the headline figure of the Contract intelligence module, which shows it on its Coverage view as counts — so many on a signed contract, so many on online terms, so many missing one.
It answers the question every figure built on contract terms depends on: how much of what we bill do we actually have the agreement for? A renewal forecast, a payment-terms analysis or a discount check built on 40% of your subscriptions says something different from one built on 95%, and this is the figure that tells them apart.
It is published for your company as a whole, on the company and period object.
How it is calculated
Measured. A plain ratio of two counts:contract_coverage_rate = running subscriptions resting on a signed contract or online terms ÷ running subscriptions.
Every morning Contract intelligence makes sure each subscription in your billing has a contract record, and each record says what it rests on: signed contract, online terms, or billing only. A record moves from billing only to signed contract when its terms are typed in on the Coverage view or read from a signed contract, and to online terms when Use online terms is applied. The count is over subscriptions billing marks as running; subscriptions that have ended are not in either number.
If you have 3,000 running subscriptions, 400 with terms from a signed contract and 2,400 on your online terms, the rate is 2,800 ÷ 3,000 = 0.933.
Nothing is weighted and no customer is given a score. The two counts are written by the morning run; the ratio is your data store’s own formula over them. Contract intelligence — how it is calculated sets out how the records are opened and what each one rests on.
Where it comes from
No read interface or MCP tool serves this value yet. This table publishes its shape ahead of the doors.
How fresh it is
Worked out once a day, after your tools have synced, over the subscriptions billing marks as running that morning. When terms are typed in, the Coverage list moves at once and the counts move at the next morning run. Which day’s figure stands for a period is not yet declared; until it is, read the value with its owncomputed_at.
Both timestamps travel with it: the moment the value describes, and the moment Beacon last worked it out.
Currency and rounding
Neither applies. It is a ratio of two counts of subscriptions, with no unit and no currency.What changes it
Terms typed in or read from a signed contract for a subscription that rested on billing alone raise it; so does applying your standard online terms to a small-business customer. A new subscription starting in billing with no contract on record lowers it until its terms are added. A subscription ending leaves both counts. Nothing about the value of a subscription moves it: a large contract and a small one each count once. Contracted ARR is the figure that weighs them.What it is not
- Not a share of revenue. One subscription is one count, whatever it is worth. The revenue under contract is contracted ARR.
- Not a check that the terms are right. A record resting on typed-in terms is covered; whether those terms keep to Finance’s limits is the guardrail check, which is not calculated yet.
- Not the reverse check. Signed contracts that no running subscription is billing are counted separately on the Coverage view and are not in this ratio.
- Not data completeness. That asks whether the records Beacon expected from your tools arrived. This asks whether the subscriptions that did arrive have their agreement on record.
- Not something that moves by itself. It changes only when a contract is added or a subscription starts or ends.