The Terrorist Watchlist Data Accuracy and Transparency Act amends the Homeland Security Act to force the Department of Homeland Security to perform formal quality‑assurance (QA) reviews on its initial nominations to the federal terrorist watchlist ecosystem and to run regular audits of those nominations. It requires DHS—through the Under Secretary for Intelligence and Analysis—to run an annual review of all U.S. person nominations and a monthly random audit program for all nominations, notify the FBI’s Terrorist Screening Center and the NCTC within 24 hours if DHS finds errors, and consult with those agencies if corrections are not completed within 30 days.
The measure matters because it converts internal data‑quality practices into statutory obligations, creates explicit interagency notification and consultation timelines, and mandates an annual report to Congressional homeland security committees with counts of corrections and reissued nominations disaggregated by U.S. person status. For compliance officers, intelligence managers, and legal counsel at DHS, FBI, and NCTC, the bill creates new process requirements, auditing records, and cross‑agency interactions that will affect staffing, case handling, and oversight documentation.
At a Glance
What It Does
The bill adds a new section (210H) requiring DHS to run pre‑submission quality assurance reviews of its initial nominations to the Terrorist Screening Center and NCTC, conduct annual reviews of U.S. person nominations, and operate a monthly random audit program. It mandates 24‑hour notification to the FBI and NCTC when DHS determines a nomination contains errors and a 30‑day consultation requirement if corrections are not made.
Who It Affects
Directly affects DHS components that generate watchlist nominations (acting through the Under Secretary for Intelligence and Analysis), the FBI’s Terrorist Screening Center, and the National Counterterrorism Center. Indirectly affects transportation and border screening processes (e.g., No Fly List/Selectee List), airlines, state/local law enforcement that rely on watchlist outputs, and individuals whose identities appear on those lists.
Why It Matters
This is a statutory shift from discretionary QA to mandated audits and interagency notification, increasing accountability and creating measurable outputs for Congress. It will change how nominations are vetted, tracked, and corrected—and could force tradeoffs between speed of placement and data verification.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill inserts a new statutory duty into the Homeland Security Act requiring DHS to verify the accuracy of every initial nomination it sends to the federal terrorist screening system. Before a component may forward an initial nomination to the FBI’s Terrorist Screening Center or the NCTC, DHS must carry out a quality‑assurance review and include the result of that review with the nomination packet.
The statute frames that review as a determination that the nomination is “free from error,” although it does not prescribe a specific review methodology.
Beyond the pre‑submission check, the bill requires two ongoing audit streams. First, DHS must, within 90 days of enactment and annually thereafter, review all nominations of United States persons (U.S. citizens and lawful permanent residents) to determine both factual accuracy and continued satisfaction of the Watchlisting Advisory Council’s guidance.
Second, DHS must stand up a random audit program—also starting within 90 days—that runs monthly to sample nominations across categories and assess the same questions of error and continued eligibility.If either an annual or random audit finds an error or that a nomination no longer meets watchlisting criteria, DHS must notify the FBI’s TSC and NCTC within 24 hours and, where appropriate, request a correction or retraction. If the FBI or NCTC have not implemented the correction or retraction within 30 days of DHS’s request, DHS must promptly consult with the relevant Director to discuss the justification for retaining the record.
Finally, DHS must send an annual report to the House and Senate homeland security committees with counts of identities referred for correction or retraction, disaggregated by U.S. person and non‑U.S. person, and the number of nominations recalled or reissued.Taken together, the provisions make DHS responsible not only for originating nominations but for an ongoing attestative role about their quality and for formal follow‑through when errors are discovered. The bill does not change the substantive criteria for placing someone on the list; it creates process obligations, notification windows, and reporting requirements to create measurable accountability for data quality across the interagency watchlisting ecosystem.
The Five Things You Need to Know
Before DHS forwards an initial nomination to the FBI Terrorist Screening Center or NCTC, DHS must conduct and include a quality assurance review certifying that the nomination is free from error.
Within 90 days of enactment and annually thereafter, DHS must review every nomination of a United States person to confirm factual accuracy and continued satisfaction of Watchlisting Advisory Council criteria.
Within 90 days and monthly thereafter, DHS must operate a random audit program sampling nominations (including No Fly, Selectee, and exceptions) to check for errors and continued eligibility.
If DHS determines a nomination is erroneous or no longer meets criteria, it must notify the FBI TSC and NCTC within 24 hours and may request correction or retraction; if not addressed within 30 days, DHS must consult with the relevant Director.
DHS must annually report to House and Senate homeland security committees the number of identities referred for corrections or retractions (disaggregated by U.S. person and non‑U.S. person) and how many nominations were recalled or reissued.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Pre‑submission quality assurance reviews
This subsection requires DHS to run a QA review on every initial nomination it sends to the FBI’s Terrorist Screening Center and to NCTC, including nominations to No Fly, Selectee, and watchlist exceptions. Practically, that means DHS must develop and document review procedures and attach the QA determination to the nomination file. The provision places the attestation obligation on the Secretary (executed through the Under Secretary for Intelligence and Analysis) and creates an auditable trail that receiving agencies will see with the referral.
Annual audit of United States person nominations
This clause mandates a full annual review—starting within 90 days of enactment—of all DHS nominations for U.S. persons to determine factual accuracy and whether listings continue to meet the Watchlisting Advisory Council’s guidance. The scope covers initial nominations and, implicitly, standing nominations (No Fly, Selectee, etc.). By singling out U.S. persons, the statute demands a higher‑frequency, comprehensive check for citizens and lawful permanent residents, triggering programmatic work to inventory and re‑validate those records each year.
Monthly random audit program
This subsection creates a monthly random sampling regime to assess the accuracy and continued eligibility of DHS nominations across the universe of individuals, not limited to U.S. persons. The program requires DHS to design statistically valid sampling procedures, document selection and review results, and integrate those findings into corrective workflows. The monthly cadence is designed to surface errors more quickly than an annual‑only schedule, but it also imposes recurring operational demands on analysts and case managers.
Correction, notification, and interagency consultation timelines
If an audit yields a negative determination, DHS must notify the FBI’s TSC and the NCTC within 24 hours and include a request for correction or retraction as appropriate. If the receiving agency has not effectuated the correction or retraction within 30 days, DHS must promptly consult with the relevant Director to discuss the rationale for retaining the record. These timelines create explicit expectations for interagency response, but the statute stops short of prescribing remedial steps if consultation does not resolve the disagreement.
Annual reporting and definitions
DHS must report annually to the House Committee on Homeland Security and the Senate Committee on Homeland Security and Governmental Affairs with counts of identities referred for corrections or retractions, disaggregated by U.S. persons and non‑U.S. persons, and the number of nominations recalled or reissued. The section also defines key terms—'terrorist watchlist,' 'other terrorism databases,' and 'United States person'—which frames coverage for QA and audit activities and links DHS duties to existing statutory constructs (e.g., the Terrorist Identities Datamart Environment).
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- United States persons (U.S. citizens and lawful permanent residents): annual reviews and faster correction pathways reduce the risk of persistent false positives that disrupt travel, employment, or interactions with law enforcement.
- Individuals wrongly listed (non‑U.S. persons and U.S. persons): the 24‑hour notification and 30‑day consultation timelines increase the chance of timely correction or retraction of erroneous records.
- FBI Terrorist Screening Center and NCTC analysts: cleaner, DHS‑attested nomination packets should reduce time spent chasing basic data errors and improve downstream screening signal quality.
- Congressional homeland security oversight committees: the mandated annual report with disaggregated counts provides measurable oversight metrics previously unavailable in statute.
Who Bears the Cost
- DHS (Under Secretary for Intelligence and Analysis and originating components): must staff and fund pre‑submission QA, full annual U.S. person audits, and a monthly random audit program, creating significant analytical and recordkeeping workloads.
- FBI TSC and NCTC: will receive more formalized correction/retraction requests and engage in consultations when DHS and the receiving agency disagree, increasing their administrative and legal burden.
- Operational screening partners (aviation, border control, state/local law enforcement): may face increased volatility in watchlist entries (temporary holds, recalls, reissues) as corrections propagate, complicating operational procedures.
- Classified information handlers and legal teams: must reconcile transparency/reporting obligations with safeguards for classified or sensitive intelligence—adding compliance complexity and possible redaction workloads.
Key Issues
The Core Tension
The central dilemma is improving accuracy and transparency for individuals affected by watchlists versus preserving the speed, flexibility, and secrecy necessary for counterterrorism operations. Raising the standard for data verification reduces false positives but risks slowing the addition of urgent threat information and increasing interagency friction when agencies disagree about retention or correction.
The statute converts data quality practices into enforceable process requirements but leaves important implementation details unresolved. It orders DHS to certify nominations are “free from error” without defining what constitutes an acceptable level of uncertainty, what types of errors (identity attributes, identity resolution, identity conflation, stale intelligence) trigger correction, or how QA must be documented.
The absence of required standards or minimum sample sizes for the random audit leaves DHS discretion over methodology, which will materially affect outcomes and resource needs.
The bill imposes fast notification and consultation windows (24 hours and 30 days) but does not allocate funding or create a dispute‑resolution mechanism if the FBI or NCTC declines to act on a DHS correction request. That gap could leave DHS with a statutory obligation to request corrections but no effective means to compel them, producing friction in interagency relationships and potential delays.
Also unresolved is how to handle classified or sensitive source‑protected information in Congressional reports and interagency disclosures—balancing transparency with operational security will require detailed implementing guidance.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.