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

# Data Quality FAQ

> Troubleshooting anomalies, missing periods, and quality issue workflows.

Use this page to troubleshoot quality checks and completeness gaps.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="What is the difference between an issue and a completeness gap?">
    Issues are record-level problems (for example, connection errors or bill anomalies). Completeness
    gaps indicate missing expected coverage over time.
  </Accordion>

  <Accordion title="I see a missing month. Does that always mean data is lost?">
    Not always. It can reflect delayed utility publication, connection downtime, or start-date
    settings. Validate connection status and expected billing cadence first.
  </Accordion>

  <Accordion title="How do I prioritize what to fix first?">
    Start with active connection failures, then unresolved bill anomalies, then completeness gaps that
    affect your reporting period.
  </Accordion>

  <Accordion title="Can I export while issues exist?">
    Yes, but bills with open issues are excluded by default in exports. You can toggle this in the
    export wizard. Review your export settings and resolve critical issues before final reporting.
  </Accordion>

  <Accordion title="What is a data quality issue?">
    A data quality issue is a problem detected on a specific bill or meter — for example, a potential
    duplicate, missing usage data, or an unmatched account. Each issue has a type, severity, and
    guided resolution steps. See [Glossary — Data quality issue](/platform/glossary#data-quality-issue).
  </Accordion>

  <Accordion title="How do I resolve a data quality issue?">
    Open the record from **Data Quality > Issues** or click it in the **Data Inventory > Bills** table.
    Resolution cards appear above the detail tabs. Follow the guided steps for each issue — options
    include comparing duplicates, editing data, dismissing the issue, or reporting it to support.
  </Accordion>

  <Accordion title="Can I resolve issues in bulk?">
    Yes. In the **Data Quality > Issues** triage inbox, select multiple records using the checkboxes,
    then click **Bulk actions** to resolve a specific issue type across all selected records at once.
  </Accordion>

  <Accordion title="What is the difference between dismissing and deleting?">
    **Dismissing** marks the issue as resolved — the record stays in your portfolio and its data is
    included in analytics and exports. **Deleting** permanently removes the record from your inventory.
    Use delete only when the record should not exist (e.g., a non-utility document).
  </Accordion>

  <Accordion title="What happens when all issues on a record are resolved?">
    The record is no longer flagged. Its data is included in analytics dashboards and exports. The
    resolution is recorded in the audit log.
  </Accordion>

  <Accordion title="Why is the Data Quality page not loading?">
    Retry and narrow filters (company/site/date). If errors persist, capture the URL and error
    message for support so the failing scope can be diagnosed quickly.
  </Accordion>

  <Accordion title="How do I clear a recurring connection-related issue?">
    Resolve the root connection problem in Data Input, then run a fresh collection cycle. Recurring
    issues usually indicate unresolved credentials, MFA, or provider-side changes.
  </Accordion>

  <Accordion title="The gap detail sheet shows an Inspect tab—what is it?">
    For gaps with site context, **Inspect** opens the [Aggregation Inspector](/platform/sites/overview#aggregation-inspector)
    for that month. It breaks down how site totals are built from meters, which helps explain unexpected
    completeness or usage totals. See [Completeness](/platform/data-quality/completeness) for the full
    sheet layout.
  </Accordion>

  <Accordion title="Why do stacked panels appear when I click a gap?">
    Drilling from a site row into an account can open a second panel on top so you do not lose site
    context. Close the top panel to return to the main swim lane.
  </Accordion>

  <Accordion title="Can I bookmark a specific completeness view?">
    Yes. Filters are stored in the URL—copy the address bar after setting period, severity, sites, and any
    **+ Add Filter** options to share the same view with a teammate.
  </Accordion>

  <Accordion title="Completeness says I am missing data but bills exist—why?">
    The cell reflects whether expected [usage data](/platform/glossary#usage-data) (or bills, depending on
    configuration) exists for that entity and month. Flagged bills, wrong site assignment, or calendar
    boundaries can still show a gap. Use the gap detail **Bills** and **Usage** tabs to see what
    Nectar counted for the period.
  </Accordion>

  <Accordion title="My fuel meter shows complete for a month with only one delivery—is that correct?">
    Yes. Fuel and waste are spot-delivery commodities — deliveries happen on individual days, not
    continuously. For these commodities, a month is **Complete** as long as at least one delivery record
    exists. A month with zero deliveries is **Missing**. This differs from electricity, gas, and water,
    which require more continuous day-level coverage.
  </Accordion>
</AccordionGroup>

## Related data quality docs

<CardGroup cols={2}>
  <Card title="Data quality overview" icon="book-open" href="/platform/data-quality/overview">
    Summary of quality workflows and detection types.
  </Card>

  <Card title="Issues" icon="triangle-exclamation" href="/platform/data-quality/issues">
    Triage and resolve bill data quality issues.
  </Card>

  <Card title="Completeness" icon="chart-pie" href="/platform/data-quality/completeness">
    Track period-level data coverage and gaps.
  </Card>

  <Card title="Data input FAQ" icon="plug" href="/platform/data-input/faq">
    Troubleshoot upstream collection failures.
  </Card>
</CardGroup>