Christine A. Bither — Historical EOIR code records

• 14 eligible asylum records have no application result; 14 of them appear in the dated list.
• 8 asylum-linked proceedings have conflicting saved application results.

A blank date or result does not establish a pending case, an undecided application, or the absence of a decision. Missing dates are not assigned to an assumed fiscal year.

Counts describe stored proceedings associated with the judge code, not unique cases, people, or verified decision authorship. Asylum applications are combined per proceeding using the same joins and conflict rules as the dated list.

4,858 asylum-linked proceedings meet the proceeding-type, case-link and result-consistency rules. These eligible records split into missing dates, invalid dates, dates after the cutoff, and dated records through the cutoff.

The dated list includes all saved result categories, including a blank result. Grant share uses only dated grants divided by dated grants plus denials; other categories are excluded.

The 2026-08 EOIR edition is grouped using a source cutoff of 2026-08-31. Counts describe proceeding records with retained future hearing dates, grouped by the judge and court codes stored on each schedule record. Records with a handling reason and other excluded records are kept outside the counts; records that cannot be confirmed are listed separately. All proceedings includes the reliably identified asylum-associated subset.

Later recorded hearing dates are included in the source coverage summary.

All proceedings · future hearing dates through 2036-08-31

These source coverage counts include all proceedings and do not change with the proceedings filter above.

These are historical pooled counts, not a judge score or a current pattern. This product has no annual judge-code breakdown. DIS does not prove this judge was affirmed; REM is not an asylum grant; SUS is not a final asylum outcome.

Recorded BIA disposition patterns can change over time. These FY2021–FY2025 counts are not a permanent characteristic of this judge code. Changes may coincide with law, policy, administration, BIA composition, case mix or backlog; these descriptive data do not establish a cause.

All-party source coverage is separate from the respondent-filed table. National parent appeal events: 119,252 · Linked to a stored judge code: 119,155.

Respondent-filed source events: 109,995 · Linked to a stored judge code: 109,915 · Published respondent-filed events: 67,156 · Respondent-filed events with identity limitations: 42,759.

Judge code: CAB · Stored source field: B_TblProceeding.IJ_CODE · Population: bia-decided-stored-judge-chronology-clean-1.

Disposition date basis: tblAppeal.datBIADecision · Historical period: 2020-10-01–2025-09-30 · Source cutoff: 2026-08-31.

The stored code is an association in the snapshot, not proof of decision authorship or assignment when the original decision was issued. Today’s judge directory and court listing describe current context only.

Download certified judge-code BIA aggregates · Companion manifest · Read disclosure certificate · Methods