StatuteData

Maintained jurisdictional regulatory data

Rules vary by jurisdiction. Summaries of those rules go stale quietly.

StatuteData maintains a structured, cited record for all fifty states and the District of Columbia. Every field carries the source it came from, the date that source was checked, and a verification status.

Field fragment
// one field, with its provenance attached
{
  "value":        "conditional",
  "conditions":   [ /* machine-evaluable */ ],
  "citation":     "[state code § ref]",
  "tier":         "statute",
  "retrieved":    "2026-08-03",
  "verification": "primary_verified",
  "last_reviewed":"2026-08-03"
}

Fields are stored structured rather than as prose, so they can be queried, compared across jurisdictions, and rendered without anyone rewriting them.

51Jurisdictions
MonthlyRe-verification
ContinuousChange monitoring

Coverage

Fifty states and the District of Columbia. Federal requirements are stored once and joined, rather than duplicated across records, so a change at the federal layer propagates to every jurisdiction at the same moment.

ALAKAZARCACOCTDEDCFLGAHIIDILINIAKSKYLAMEMDMAMIMNMSMOMTNENVNHNJNMNYNCNDOHOKORPARISCSDTNTXUTVTVAWAWVWIWY

Every field carries a status

Primary verified

Traced to a statute, regulation, or official agency publication, with the citation and the retrieval date recorded alongside the value.

Conflicting

Two authoritative sources frame the rule differently. Both are recorded and the divergence is described. The conflict is surfaced rather than resolved, because choosing between them is the client's call.

Unverified

No primary source located. The field is left empty and marked. It is never filled by inference, and never completed from a secondary summary.

Method

  • Sources are statutes, regulations, and official agency publications. Commercial summaries are never treated as sources of record.
  • A last-reviewed date is recorded separately from a version number, so a field checked and found unchanged is documented as an outcome rather than as silence.
  • Records are versioned and changes are stored as diffs, so the state of the dataset on any past date can be reconstructed and cited.
Monitoring
Legislative and regulatory sources are watched continuously, including bills that would change a field before they pass.
Re-verification
Every field is re-checked against its source monthly, whether or not anything is expected to have changed.
Revision
Confirmed changes are published out of band rather than held for the next cycle.

Access

Audit

A one-off review of published claims against primary sources, returned as a discrepancy report with citations and severity ranking.

Records

Maintained jurisdiction records, delivered as versioned files or a nightly bulk export, with a change log per jurisdiction.

API

Query a jurisdiction, product and activity and receive a decision with citations attached. Past decisions can be replayed against the dataset version that produced them.

What this is not

This is not legal advice. StatuteData reports what identified sources say, and where those sources disagree. It does not reach conclusions about what any person or business may lawfully do.

Nor is it a system of record. It supplies inputs and evidence. Determinations remain with the client and their counsel.