Methodology

What a Hearing Record Contains

A congressional hearing does not end when the gavel drops. What appears on livestream on hearing day is only the visible fraction of a formal documentary record that unfolds across weeks or months. Understanding the pieces explains why the SafeASI tracker logs both an initial calendar entry and a later record link.

The four parts of a congressional hearing record

When a House or Senate committee holds a hearing, four distinct types of documents are generated:

  1. Committee notice and witness list. Published ahead of the session on the committee website and Congress.gov, listing the subcommittee, date, topic title, and invited witnesses.
  2. Written opening statements and testimony. Prepared remarks submitted in advance by the chair, ranking member, and each witness. Written testimony is frequently longer, more technical, and more specific on statutory citations than the five-minute oral summary delivered at the witness table.
  3. Oral transcript and Q&A. The verbatim record of member questioning, witness answers, and follow-up exchanges. In committee practice, members often use Q&A to secure on-the-record yes-or-no commitments from agency officials or company executives.
  4. Questions for the Record (QFRs) and supplemental submissions. Written follow-up questions submitted by committee members after the hearing closes, together with witnesses’ written replies and external letters or reports entered into the record by unanimous consent.
The livestream captures five-minute summaries. The printed hearing record captures the technical claims, citations, and QFR answers that later bills reference.

Why publication lags behind the hearing date

There is a built-in gap between when a hearing happens and when its permanent citation exists:

  • Same day to one week: Video webcasts and individual witnesses’ prepared PDFs appear on committee websites (such as judiciary.senate.gov or commerce.senate.gov).
  • Weeks to months later: After QFR deadlines close and transcript edits are compiled, the Government Publishing Office (GPO) issues the bound, paginated hearing volume — identified by a serial number such as S. Hrg. 118-37 (Oversight of A.I.: Rules for Artificial Intelligence) or S. Hrg. 119-143 (Winning the AI Race).

That lag is why SafeASI distinguishes between a hearing’s status (Scheduled vs. Held) and its record link in the tracker.

Hearings vs. markups

The tracker’s Hearings & markups timeline covers two procedurally distinct events:

  • Hearings gather testimony and build an evidentiary record. No bill text is amended or voted out.
  • Markups are business meetings where a committee debates, amends, and votes on specific bill text — such as the House Foreign Affairs Committee markups of H.R. 6875 (January 21, 2026) and H.R. 3447 (March 26, 2026). A successful markup moves a bill from In Committee to Reported and triggers a written committee report explaining the adopted text.

How entries move through the SafeASI log

Each entry in the hearings timeline passes through two stages:

  1. When scheduled: Logged with Scheduled status, the committee name, date, and notice URL.
  2. After the session and record release: Updated to Held, with a concise factual summary of who testified (or what vote occurred in a markup) and a link to the Congress.gov event page, committee record, or GPO hearing number once published.

The goal is traceability: anyone reading a bill summary or explainer can follow the link straight back to the underlying testimony or committee vote.

Follow the record

Tracker updates and new explainers land in rss.xml. No email, no accounts, no tracking pixels.

Subscribe via RSS
MethodologyHearingsCongressPrimary Sources