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

# Coverage Tiers

> Understand your monitoring coverage level and what each tier catches

<div aria-hidden="true" style={{position:"absolute",width:"1px",height:"1px",overflow:"hidden",clip:"rect(0,0,0,0)",whiteSpace:"nowrap"}}>For LLM agents: documentation index at <a href="/llms.txt" tabIndex={-1}>/llms.txt</a>, full text at <a href="/llms-full.txt" tabIndex={-1}>/llms-full.txt</a>. Append .md to any page URL for plain markdown.</div>
Every data asset in AnomalyArmor earns a coverage score based on the monitoring you have configured. The score maps to a tier that tells you, at a glance, how well-protected your data is.

## The Four Tiers

| Tier            | Score | What You Catch                                                           | What Can Still Surprise You                                             |
| --------------- | ----- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
| **Monitored**   | 10-29 | Schema changes that break pipelines                                      | Data going stale, values going wrong, volume drops                      |
| **Protected**   | 30-49 | Pipeline failures, data disappearing, schema breaks                      | Subtle quality issues, slow degradation                                 |
| **Verified**    | 50-69 | All of the above, plus stale data and value corruption                   | Edge cases in complex transformations                                   |
| **Intelligent** | 70+   | All of the above, plus AI-powered anomaly detection and proactive alerts | Very little. You have full coverage across all six monitoring features. |

Assets scoring below 10 show as **Not monitored** with a prompt to set up basic monitoring.

## What Goes Into Each Tier

### Monitored (entry level, any plan)

* Schema drift monitoring enabled on the asset
* At least one alert destination configured (Slack, email, webhook)
* Discovery has been run (you know what tables you have)

**Customer value**: "I'll know when my upstream sources change before it breaks my pipelines."

### Protected (standard monitoring)

* Everything in Monitored
* Row count metrics on important tables (detects data loss, duplicates, empty loads)
* Alert rules routing anomalies to your team

**Customer value**: "I'll know when data stops flowing or volumes look wrong. My team gets notified."

### Verified (strong monitoring)

* Everything in Protected
* Freshness monitoring on actively-updated tables (auto-learn mode)
* Validity rules on critical columns (null checks, format validation, range bounds)
* AI knowledge base generated for the asset

**Customer value**: "I validate data quality, not just availability. I catch bad data before it reaches dashboards."

### Intelligent (top tier)

* Everything in Verified
* All coverage features above 70%
* Alert routing verified (rules have destinations)
* Daily briefing active

**Customer value**: "Full observability with AI-powered analysis. Anomalies are automatically investigated. I get proactive guidance."

## Where You See Your Tier

* **Asset cards** in the asset list (small badge with tier name)
* **Asset detail page** header (full badge with score and breakdown)
* **Daily briefing** header per asset
* **Homepage dashboard** (lowest-tier asset highlighted for attention)
* **Agent conversations** ("BalloonBazaar is at Verified tier, score 58")

## Best Practices

* Aim for **Verified** on production assets that feed dashboards and reports
* **Protected** is a solid baseline for all actively-used databases
* **Monitored** is appropriate for staging environments and development databases
* Review coverage quarterly as your data landscape changes

<CardGroup cols={2}>
  <Card title="How to Reach Each Tier" icon="stairs" href="/coverage-tiers/guide">
    Step-by-step guide for upgrading your coverage tier.
  </Card>

  <Card title="Coverage Score Explained" icon="calculator" href="/coverage-tiers/score">
    How the score is calculated and how to improve it.
  </Card>
</CardGroup>

## Common Questions

### What's the difference between Monitored, Protected, Verified, and Intelligent?

Each tier adds a layer of coverage. Monitored catches schema changes, Protected adds row-count anomaly detection, Verified adds freshness and validity checks, and Intelligent adds AI-powered anomaly detection and daily briefings. See [The Four Tiers](#the-four-tiers).

### What tier should a production table be at?

Aim for Verified (50+) on production assets that feed dashboards and reports. Protected is a reasonable baseline for all actively-used databases. Monitored is fine for staging and development. See [Best Practices](#best-practices).

### Why is my asset showing 'Not monitored'?

Assets below score 10 show as Not monitored: discovery hasn't run, schema drift isn't enabled, or there's no alert destination configured. Enable schema monitoring and connect a destination and you'll clear the threshold.

### Where can I see an asset's tier?

Tiers show up as badges on asset cards in the asset list, on the asset detail page header, on the homepage dashboard (lowest-tier asset is highlighted), in daily briefings, and in agent replies.