> ## 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. # Data readiness score > One score from 0 to 100 for how complete, fresh and linked your data is — the line that decides which kinds of module may switch on. The Data model module's headline figure. Not calculated yet. ## What it is `data_readiness_score` is one score from 0 to 100 for how complete, fresh and linked your data is across the tools you have connected. Higher is readier. It is the headline figure of the [Data model module](/modules/data-model). It describes your data as a whole, not any customer. Its job is to decide which kinds of module may switch on: a module that forecasts needs more of your data than one that reports. It is published for your company as a whole, on the [company and period object](/data-model/company-period). **This value is not calculated yet.** The rules below are Beacon's, and they are fixed, but nothing works the score out today. Every door returns `not_computed` for it, and the Data model page shows it as not yet calculated. Nothing is estimated in its place. ## How it is calculated Measured. Seven areas of your data are each given a fixed weight: | Area | Weight | | - | - | | CRM | 0.22 | | Billing | 0.22 | | Product usage | 0.16 | | Links between tools | 0.16 | | Accounting | 0.12 | | On time | 0.08 | | Support, marketing and HR together | 0.04 | Each area scores the share of its required fields that are present and valid. The weighted total is then cut when any tool is behind its minimum sync time, and cut by 15% when one of the three key links between your tools breaks — billing to CRM, product usage to customer, or marketing to pipeline. What the score allows: | Score | What may switch on | | - | - | | Under 60 | Nothing new | | 60 to 79 | Modules that report and alert | | 80 or more | Forecasts too | The line for forecasts is 80 as standard, 85 for larger companies and 75 for small ones. Your data lead sets it, and the weights and which links count, in Setup. Beacon never changes them itself, and a module held back by the line is never switched on early. **The score and the steps can tell different stories.** Beacon also names a step from the tools you have connected — Connected, Validated, Ready, Full — and forecasts wait for Ready, which needs your accounting tool. The weights alone can reach 80 without accounting. Both rules are Beacon's, and this page does not pick between them. ## Where it comes from | Source | What it supplies | Required | | - | - | - | | Your billing system and your CRM | The two heaviest areas, and the billing-to-CRM link | Yes | | Product analytics | Product usage, and the usage-to-customer link | Adds to the score | | Your accounting tool | The accounting area | Adds to the score | | Support, marketing and HR tools | The last area, and the marketing-to-pipeline link | Adds to the score | | Every connected tool's delivery times | The on-time area and the cut for a late tool | Yes | | Where it is available | | | - | - | | Read interface | Yes, with an opt-in | | MCP | Yes, with an opt-in | | Events | Yes, with an opt-in | | CRM property | Yes, with an opt-in | No read interface or MCP tool serves this value yet, and the value itself is not calculated yet. This table publishes its shape ahead of both. **Where the choice is made.** This value is not open by default on any door. The choice happens when a reader grant that reaches it is issued or widened, when you subscribe to events, or when you turn the CRM property on. Whoever makes it is shown who becomes able to see the value, and their yes is recorded. ## How fresh it is Once calculated, it is worked out on each read of your tools. **Which read's score stands for a period is not yet declared**; until it is, read the value with its own `computed_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 score, with no unit and no currency. ## What changes it Connecting a tool, which fills an area. A required field being filled or emptied in one of your tools. A tool falling behind its sync time, or catching up. A key link breaking, or holding again. Your data lead changing a weight or a line, which is logged. ## What it is not * **Not a customer score.** It describes your data as a whole. * **Not [`data_integrity_rate`](/definitions/data-integrity-rate).** That is the share of records passing every check. This weighs how complete, fresh and linked each area of your data is, and decides what may switch on. * **Not the [score for each record](/data-integrity).** That measures the data behind one customer, deal or subscription. * **Not something Beacon can override.** No module is switched on below its line, whatever it is asked. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.