# Gaps — Automated data-gap analysis

> Know what you're missing before a regulator does.

Gaps ingests regulatory dossiers in IUCLID format, maps every study to its toxicology endpoints, and flags what is missing: studies that cannot be mapped and endpoints with no data behind them. It reads the Yard warehouse to tell a real gap from one already covered elsewhere.

## Key facts
- **IUCLID** — dossiers ingested directly
- **Endpoint** — level mapping of every study
- **Yard** — backed, so gaps are real gaps

## What Gaps does

### Dossier in, gaps out
Point it at an IUCLID dossier and it returns the endpoints with no supporting study.

### Study-to-endpoint mapping
Every study is placed against the endpoints it informs, and unmappable studies are surfaced too.

### Grounded in the warehouse
By reading Yard, it separates a true data gap from evidence that already exists elsewhere.

## Works closely with
- [Yard](https://toxindex.com/platform/yard.md): Raw data warehouse
- [ToxJobs](https://toxindex.com/platform/toxjobs.md): Prediction toolkit
- [Flow](https://toxindex.com/platform/flow.md): Reproducible workflow engine

## Frequently asked questions

**What does Gaps do?**

Gaps ingests IUCLID dossiers, maps every study to its toxicology endpoints, and flags what is missing: studies that cannot be mapped and endpoints with no data.

**How does Gaps know a gap is real?**

It reads the Yard warehouse underneath, so it can tell a genuine data gap from evidence that already exists elsewhere in the record.

**What happens after Gaps finds a gap?**

Each flagged endpoint hands straight to read-across or a predictor, so analysis rolls into remediation without a context switch.

---
Canonical page: https://toxindex.com/platform/gaps