> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Data completeness
> How EnerG scores billed coverage, why gaps and overlaps lower the score, and how completeness gates benchmarking
**Data completeness** is a score from 0% to 100% that measures billed coverage from each meter's service start through today. It is the trust signal behind every EnerG metric. This page explains how the score works and what moves it.
To fix gaps, see [Data completeness](/products/energ/data-quality/data-completeness) in the Data Quality section. For the color legend and status values, see [Data and meter fields](/products/energ/reference/data-and-meter-fields#data-quality-legend).
## What the score measures
Completeness compares the bills EnerG expects against the bills it has. It counts every month from a meter's service start date to the current date.
Missing bills, gaps, and overlaps lower the score. Complete, non-overlapping coverage raises it.
| Signal | Effect on score |
| -------------------------------------------- | ---------------- |
| Complete billing period | Raises coverage |
| Gap (missing expected bill) | Lowers coverage |
| Overlap (duplicate or double-counted period) | Lowers coverage |
| Delivery-only or supply-only bill | Partial coverage |
## Meter, building, and portfolio scoring
Completeness rolls up in three layers.
* **Meter level** scores one meter from its service start to today.
* **Building level** aggregates meter scores across all included meters for the site.
* **Portfolio level** averages building coverage for the KPI on Portfolio Home.
A meter excluded from metrics does not drag down the building score. Confirm the `Include In Metrics` setting when a meter should or should not count.
## Why completeness gates benchmarking
EnerG only ranks buildings that meet your organization's completeness threshold. Buildings below the threshold appear with **No Ranking** until coverage recovers.
This rule protects peer comparisons. A building with three missing months would post an artificially low EUI and distort rankings. Completeness holds it out until the data is trustworthy.
The same rule applies before you set baselines, train models, or publish reports. Each needs 12 consecutive months of complete data to qualify.
## Common causes of low coverage
* A utility credential failed, so new bills stopped arriving.
* A meter was assigned late, so early months never loaded.
* A provider issued overlapping or corrected bills.
* A manual meter has no readings for recent months.
Each cause has a fix in the [gap investigation workflow](/products/energ/data-quality/data-completeness#investigate-and-fix-gaps).
## Next steps
Review a meter timeline and work through the gap investigation steps.
Review how bills and interval reads enter EnerG and roll into meters.
Triage billing gaps, overlaps, and late bills across the portfolio.
See how completeness thresholds affect EUI, WUI, and GHG rankings.