Where the data comes from and how fresh it is

What we cover today

Indiana is the initial paid-pilot focus. That focus does not establish that every Indiana bill, session or facet is available. The table below shows only coverage supported by a current verified snapshot. While that snapshot is unavailable, coverage and freshness remain unknown. A bill appearing in search does not establish complete text or action history.

Current coverage is unverified. A verified current coverage snapshot is unavailable. Unknown does not mean no bills or no legislative activity.

Coverage snapshot: Unverified.

The jurisdiction list is a reference list, not a list of supported jurisdictions. Scroll the table to see every facet.

What each level means

These definitions describe how to read a verified coverage label. They are not claims that a jurisdiction currently meets that level.

• Full: Bills, status, latest action, full text and versions have current supporting evidence. Hearings, votes and action history are separate facets.

• Status: Bills, status and latest action have current supporting evidence. Full text and versions are not available at this level.

• Not covered: The current source explicitly identifies bill coverage as unavailable or planned. This does not promise a launch date.

• Unknown: Current supporting evidence is missing, stale or unavailable. Unknown does not mean no bills or no legislative activity.

Hearings, votes and action history are independent facets. “Full” describes bill depth; it does not mean complete hearing, vote or historical coverage. “Partial” means the facet has known limits. Read those limits and check the session and version you need. Missing evidence remains “Unknown.”

How often we check and what “last checked” means

“Last checked” identifies a successful source check for the jurisdiction. It is not the time a bill was introduced, the latest action date, the last promotion into the product, or a delivery receipt. A recent check does not establish that every change reached the bill you are reading.

“Typical check interval” describes a verified collection schedule, when one is available. It is not a delivery guarantee. Different sources and session periods can have different schedules. This page gives no default interval or freshness promise where the schedule or freshness target is unverified.

If the source check fails, is stale, has never been queued, or cannot be read, the check time is unknown and the table says “Freshness unavailable.” Missing data is different from no legislative activity. The table is a snapshot; check its generation time before relying on it.

Why an alert can arrive after the official site changes

An alert follows collection of the source change, processing into the product, evaluation of the alert rule, and delivery. Each step can add delay. A source-check timestamp does not prove alert delivery. No measured end-to-end alert latency is published here; check the notification's own delivery evidence when timing matters.

What we do not establish yet

Unknown entries do not establish coverage or absence of coverage. A bill record does not establish that every text version, action, hearing or vote has been collected. Example screenshots and synthetic fixtures do not establish current legislative activity. Requests for additional jurisdictions are reviewed requests, with no promised availability date.

Always check the official source before acting

Before acting on a deadline, hearing location, vote or bill text, check the original legislature or official congressional source. Use the official bill link when it is available in the record. A summary is a starting point for review.

How to report a problem

Use Contact Civitas or email [email protected]. Include the bill id or bill number, jurisdiction, session, official source link, what looks wrong and when you noticed it. Leave private client information, passwords and credentials out of the message.

The contact page prepares an email draft in your email app. Review it and send it yourself; opening the page or preparing a draft does not deliver a report. There is no guaranteed support response time.

How to request a state

Use the same contact route, name the jurisdiction and describe the workflow and data depth you need. A request does not enable collection or establish that the jurisdiction is supported.

This article has source and synthetic local validation only. A production walkthrough and founder wording review remain pending.