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

# Data Quality

> Monitor data issues and track completeness across your utility portfolio.

<Tip>
  Need help in this area? See [Data Quality FAQ](/docs/platform/data-quality/faq).
</Tip>

Nectar's Data Quality module gives you visibility into problems and gaps in your utility data. Instead of discovering issues downstream — in a report or an export — you can catch and resolve them at the source.

The module includes these tools:

<CardGroup cols={2}>
  <Card title="Issues" icon="triangle-exclamation" href="/docs/platform/data-quality/issues">
    Triage and resolve bill and meter issues (and anomalies) with guided resolution steps.
  </Card>

  <Card title="Completeness" icon="chart-pie" href="/docs/platform/data-quality/completeness">
    Visualize coverage gaps and monitor whether every site has the data you expect.
  </Card>

  <Card title="Anomalies" icon="chart-line" href="/docs/platform/data-quality/anomalies">
    Detect usage, cost, unit-price, and fee anomalies (and bills after a site is archived). They
    appear in **Issues and Anomalies → Triage** when detection is on (off by default).
  </Card>

  <Card title="Usage estimation" icon="chart-area" href="/docs/platform/data-quality/usage-estimation">
    Optional site-level usage fills when bills are missing — coverage, analytics, and configuration.
  </Card>

  <Card title="Savings" icon="piggy-bank" href="/docs/platform/data-quality/savings">
    Review estimated bill savings and billing-risk findings (when enabled for your company).
  </Card>
</CardGroup>

For how to work a missing month (connection health first, then duplicates, then timeline), see
[Filling data gaps](/docs/platform/data-quality/filling-data-gaps).

## How it works

Data quality checks run automatically across Nectar's collection and processing flows:

| Check type              | Trigger                                                  | Examples                                                                                            |
| ----------------------- | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Connection issues**   | Each weekly connection check (fix in **Data Input**)     | Incorrect password, site down, MFA required                                                         |
| **Data quality issues** | Bill and meter processing                                | No usage data, potential duplicate, unmatched account, illegible bill, low confidence date or units |
| **Anomalies**           | Daily detection (or on demand) when enabled              | Usage, cost, unit-price spikes; interest charges; bills after site archived                         |
| **Completeness gaps**   | When you open Completeness (computed from current bills) | Missing billing periods, sites with no active connections                                           |

<Note>
  Data quality features are actively evolving. New issue types and completeness views are added
  regularly.
</Note>

## Related pages

* [Issues](/docs/platform/data-quality/issues) — triage bill and meter issues (and anomalies)
* [Completeness](/docs/platform/data-quality/completeness) — period coverage and gaps
* [Anomalies](/docs/platform/data-quality/anomalies) — unusual usage, cost, and fees in the Issues inbox
* [Savings](/docs/platform/data-quality/savings) — estimated savings opportunities (when enabled)
* [Usage estimation](/docs/platform/data-quality/usage-estimation) — optional module for site-level usage fills (when enabled)
* [Filling data gaps](/docs/platform/data-quality/filling-data-gaps) — diagnose missing months on Completeness
* [Data Quality FAQ](/docs/platform/data-quality/faq) — troubleshooting quality checks and gaps
* [Troubleshooting connections](/docs/platform/data-input/troubleshooting) — resolve connection errors that block collection (and then show up as completeness gaps)
* [Sites](/docs/platform/sites/overview) — view per-site completeness from the site dashboard
* [Methodology](/docs/platform/methodology/overview) — understand how Nectar processes and calendarizes bill data

## FAQ

<AccordionGroup>
  <Accordion title="What types of issues does Nectar detect?">
    Nectar surfaces problems in a few product areas:

    * **Connection issues** — problems that prevent bill collection, such as incorrect passwords, expired credentials, MFA challenges, or provider site outages. Fix these in Data Input.
    * **Data quality issues** — problems found during bill and meter processing, such as missing usage data, duplicate bills, unmatched accounts, illegible scans, or low-confidence dates and units. See [Issues](/docs/platform/data-quality/issues) for the full list of issue types.
    * **Anomalies** — unusual usage, cost, unit price, or fees (same Issues inbox, when enabled). See [Anomalies](/docs/platform/data-quality/anomalies).
  </Accordion>

  <Accordion title="How often are issues updated?">
    **Connection issues** are updated each time a connection is checked, which happens on a weekly schedule. **Data quality issues** are created or resolved whenever a bill or meter is processed or reprocessed. **Anomalies** update on the daily detection run, or when you run detection on demand.
  </Accordion>
</AccordionGroup>