> ## 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 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 problems on a **bill or meter** (for example, a duplicate, unmatched account, or
    low-confidence field) and, when enabled, **anomalies**. Completeness gaps indicate missing
    expected coverage for a month. Connection errors are **not** Issues inbox rows — fix those in
    [Data Input](/docs/platform/data-input/troubleshooting) (see also [Data input FAQ](/docs/platform/data-input/faq)).
  </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. See
    [Filling data gaps](/docs/platform/data-quality/filling-data-gaps).
  </Accordion>

  <Accordion title="How do I prioritize what to fix first?">
    Start with active connection failures in Data Input, then open **action-required** bill issues
    (and anomalies if you use them) in the Issues inbox, then completeness gaps that affect your
    reporting period.
  </Accordion>

  <Accordion title="Can I export while issues exist?">
    Yes, but bills with unresolved **bill-tied** issues are excluded by default. Meter issues (site
    match, address mismatch, container size) do not drop the bill. In the export wizard, use
    **Include bills with unresolved issues** (analytics) or **Include records with unresolved
    issues** (integrations). 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 steps under **Resolution options** in the triage inbox or Issue sheet. See
    [Glossary — Data quality issue](/docs/platform/glossary#data-quality-issue).
  </Accordion>

  <Accordion title="How do I resolve a data quality issue?">
    Open [**Data Quality > Issues and Anomalies > Triage**](https://dash.nectarclimate.com/data-quality/issues),
    or open the bill or meter and click **View** on the issue alert (if several issues are open,
    pick one first). Use **Resolution options** in the detail header or Issue sheet — not cards
    above tabs. Follow the guided steps for that type: compare on the duplicates pane, **Edit
    dates** / **Edit usage units**, type-specific dismiss, **Reassign site**, or **Contact
    support**.
  </Accordion>

  <Accordion title="Can I resolve issues in bulk?">
    Yes. In Individual triage, select one or more records of the same Kind (issues **or**
    anomalies) with the checkboxes, then click **Bulk actions**. Choose
    `Begin resolving {type}… (N)`, **Assign site… (N)** when meters have location issues, or
    **Export… (N)**. In Grouped view, check constituent rows and use **Resolve selected**.
  </Accordion>

  <Accordion title="What is the difference between dismissing and deleting?">
    **Dismissing** marks the issue as resolved — the record stays in your portfolio. After you
    dismiss a **bill-tied** issue, that bill returns to analytics and exports; meter issues were
    never withheld. **Deleting** permanently removes the bill (for example **Delete this bill** or
    **Delete the other bill**). Use delete only when the record should not exist (wrong document or
    confirmed duplicate).
  </Accordion>

  <Accordion title="What happens when all issues on a record are resolved?">
    Issue badges and alerts clear. If the resolved issues were bill-tied, that bill's data is
    included in analytics dashboards and exports again. Who resolved it, when, and any notes are
    stored on the issue (resolved view and Resolution summary).
  </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 and email [support@nectarclimate.com](mailto:support@nectarclimate.com) so the failing
    scope can be diagnosed quickly.
  </Accordion>

  <Accordion title="How do I clear a recurring connection-related issue?">
    Connection **status** problems (credentials, MFA, provider-side changes) are not Issues inbox
    types. Resolve the root connection problem in [Data Input](/docs/platform/data-input/troubleshooting),
    then run a fresh collection cycle. Missing months after a healthy collect may still need
    [Completeness](/docs/platform/data-quality/completeness) or
    [Filling data gaps](/docs/platform/data-quality/filling-data-gaps).
  </Accordion>

  <Accordion title="The gap detail sheet shows an Inspect tab—what is it?">
    For gaps with site context, **Inspect** opens the [Aggregation Inspector](/docs/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](/docs/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. Large **Site** selections can
    live in session storage, so a pasted link may omit the full site list and a teammate may need to
    re-pick sites.
  </Accordion>

  <Accordion title="Completeness says I am missing data but bills exist—why?">
    The cell reflects whether expected [usage data](/docs/platform/glossary#usage-data) (or bills, depending on
    configuration) exists for that entity and month. Wrong site assignment or calendar boundaries can
    still show a gap. Open issues do not make a month missing — completeness still counts those bills.
    Use the gap detail **Bills**, **Excluded**, and **Inspect** tabs (site view), and **Trends** for
    the usage chart, 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="/docs/platform/data-quality/overview">
    Summary of quality workflows and detection types.
  </Card>

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

  <Card title="Anomalies" icon="chart-line" href="/docs/platform/data-quality/anomalies">
    Cost, usage, and fee anomalies in the same Issues inbox.
  </Card>

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

  <Card title="Savings" icon="piggy-bank" href="/docs/platform/data-quality/savings">
    Review estimated bill savings (when enabled).
  </Card>

  <Card title="Filling data gaps" icon="wrench" href="/docs/platform/data-quality/filling-data-gaps">
    Diagnose missing months and choose the right fix.
  </Card>

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