The CHECKPOINT Act requires U.S. Customs and Border Protection to establish a Checkpoint Program Management Office (CPMO) inside U.S. Border Patrol to exercise centralized oversight of checkpoint operations, data quality, training, and coordination across CBP components. The bill forces regular collection and reporting of checkpoint statistics and surveillance-technology inventories to Congress and mandates an independent GAO review of the CPMO’s effectiveness.
Practically, the law imposes new administrative duties on CBP sectors and field staff — data collection, designated field points of contact, and standardized procedures — while forbidding any additional appropriations and terminating itself five years after enactment. That mix of oversight, transparency, and a sunset raises immediate implementation and resource questions for CBP leaders and compliance teams.
At a Glance
What It Does
Creates a permanent program office within Border Patrol to set checkpoint policies, train sector staff on data entry and procedures, and coordinate covert testing and canine operations. It also directs CBP to collect a specified set of checkpoint data and to produce annual and special reports for congressional committees.
Who It Affects
U.S. Border Patrol sector leadership, sector-level data integrity teams, CBP components that support checkpoints (for example, the National Canine Program and Operational Field Testing Division), and congressional oversight offices that will receive unredacted surveillance inventories.
Why It Matters
The bill shifts checkpoint oversight from a decentralized, sector-driven model toward centralized program management and standardized data practices; that centralization changes who makes operational decisions, who documents activities, and how Congress receives information about checkpoint technology and results.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The centerpiece of the bill is the Checkpoint Program Management Office (CPMO), an office within U.S. Border Patrol that the Commissioner must establish to oversee checkpoint operations nationwide. The CPMO will develop policies and standard operating procedures, take responsibility for checkpoint data quality, provide regular training on procedures and data entry to sectors and stations, and coordinate covert testing and canine-assisted inspections.
The Chief of U.S. Border Patrol must pick an Assistant Chief to run the CPMO for at least a two-year term.
To make oversight meaningful, the Act requires designated field points of contact in every sector that operates checkpoints. Those liaisons are responsible for communicating policy and training updates, coordinating with sector data-integrity teams, and meeting regularly with CPMO staff.
The Chief must formalize the CPMO’s authorities and distribute the relevant memoranda and standard operating procedures to the field within discrete deadlines set by the law.The bill also mandates a structured data program. CBP must collect recurring, itemized checkpoint data — covering apprehensions and seizures at checkpoints, technology and assets used, people involved, canine-assisted drug seizures, trace marijuana seizures, non-drug property seizures, attempted circumventions, and records of secondary inspections using CBP’s Border Enforcement Secondary Tool or successor tools.
The Chief must produce a plan with goals and milestones to improve data reliability and address GAO-identified deficiencies.On reporting and review, the Act requires annual submissions to congressional homeland security committees describing collected data, progress on the data plan, and oversight activities related to the CPMO. It further directs the Comptroller General to deliver an independent analysis of the CPMO’s effectiveness 18 months after enactment.
Separately, the Secretary of Homeland Security and CBP must deliver an unredacted annual inventory of surveillance technologies — including source, use, data storage and deletion rules, privacy impact assessments, recurring costs, and cases that used surveillance-derived data.Two implementation constraints stand out: the bill explicitly prohibits new appropriations for its requirements and includes a five-year sunset. Those provisions mean CBP must absorb the workload within existing resources and plan for the program’s end at the five-year mark unless Congress acts again.
The Five Things You Need to Know
The Chief must select an Assistant Chief to manage the CPMO for a term of at least two years.
CBP has 180 days after enactment to issue or update memoranda defining the CPMO’s authority and to approve the CPMO standard operating procedures.
The statute prescribes specific data elements to collect at checkpoints, including apprehensions, seizures (including trace marijuana), canine assists, secondary-inspection records, technology used, and attempted circumventions.
CBP must provide an unredacted, item-level annual inventory of all surveillance technologies — covering source, use, data storage and deletion policies, privacy impact assessments, and annual recurring costs — to the homeland security committees.
The Act bars new funding for implementation and automatically sunsets five years after enactment; it also requires a GAO effectiveness report 18 months after enactment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions that narrow the law’s scope
This section defines key terms used throughout the Act — CPMO, CDC Chief, Assistant Chief, checkpoint, and appropriate congressional committees. The definitions limit the law’s reach to permanent or temporary U.S. Border Patrol checkpoints and identify which committees receive reports, reducing ambiguity about recipients and the institutional focus of oversight.
Establishing the Checkpoint Program Management Office
Requires the CBP Commissioner to create and operate a CPMO inside Border Patrol to provide nationwide oversight of checkpoint operations. Practically, the CPMO becomes a program office with authority to issue policies, oversee data quality, and coordinate training; the Chief must appoint an Assistant Chief to manage it for at least two years, anchoring leadership continuity for implementation.
CPMO administration, training, and covert testing
Directs CPMO responsibilities beyond paperwork: maintain policies and SOPs, oversee checkpoint data accuracy, deliver recurring training to sectors and stations, review staffing/resource needs, serve as the central liaison for sector issues, and coordinate covert testing through CBP’s Operational Field Testing Division. The combination of training and covert testing is intended to move oversight from passive review toward active verification of checkpoint performance.
Coordination with CBP components and field POCs
Mandates regular coordination between CPMO and CBP units that support checkpoints — notably the National Canine Program, Operational Field Testing Division, Mission Support, Strategic Planning and Analysis, and Office of Field Operations’ Non-Intrusive Inspection office. It also requires a designated checkpoint point of contact in each sector, who must handle communications, coordinate with data-integrity teams, and meet routinely with CPMO staff, creating a defined communication chain between headquarters policy and field operations.
Structured checkpoint data collection program
Imposes detailed data collection obligations: sectors must collect recurring data on seizures, apprehensions, technology and assets used, persons involved, canine assists, trace marijuana seizures, non-drug property seizures, attempted circumventions, and secondary inspections using CBP’s Border Enforcement Secondary Tool or successors. The Chief must prepare a plan with goals and milestones to improve data collection and address GAO-identified shortcomings, signaling a move toward auditable, standardized checkpoint metrics.
Annual and independent reporting requirements
Requires annual reports to homeland security committees describing collected checkpoint data, progress on the data improvement plan, and CPMO oversight actions. Separately, it compels an 18-month GAO report analyzing CPMO effectiveness. It also compels an unredacted annual surveillance technology report from DHS/CBP that lists every surveillance asset, source, purpose, storage and deletion policies, privacy assessments, recurring costs, and criminal investigations that used surveillance-derived data — giving Congress granular visibility into CBP’s surveillance footprint.
Funding prohibition and sunset
Section 7 explicitly disallows additional appropriations for implementing the Act, making the requirements an unfunded mandate on existing CBP resources. Section 8 sunsets the law five years after enactment, making the CPMO and reporting obligations temporary unless Congress reauthorizes them or funds a permanent change.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense 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
- Congressional homeland security committees — they gain regular, unredacted inventories of surveillance technology and annual checkpoint data, improving oversight and the ability to evaluate program effectiveness.
- CPMO and centralized Border Patrol leadership — they receive authorities, standardized procedures, and formal channels to enforce data quality and training across sectors, strengthening programmatic control.
- Sector-level data-integrity teams — the law elevates the importance of data quality and provides clearer mandates and integration with CPMO, which can lead to more consistent metrics and resourcing arguments.
- Policy and civil oversight organizations — access to unredacted surveillance inventories and GAO analysis gives outside monitors and researchers stronger factual bases for independent analysis of checkpoint operations.
Who Bears the Cost
- U.S. Customs and Border Protection (line offices) — must absorb the administrative burden of establishing the CPMO, staffing training and data-collection efforts, coordinating across components, and producing detailed unredacted reports without additional appropriations.
- U.S. Border Patrol sectors and field stations — sector POCs, data teams, and frontline staff will face added reporting, training, and data-entry workload and must meet new SOPs and review requirements.
- Privacy and IT teams inside DHS — maintaining, documenting, and defending unredacted surveillance inventories, privacy impact assessments, and data-retention policies will require technical work and legal review, potentially diverting resources from other priorities.
- Operational units relying on surveillance or tactics — publicly reported inventories and GAO findings could force operational adjustments or constrain use of certain tools if congressional or public pressure follows disclosure.
Key Issues
The Core Tension
The central dilemma is between transparency and capacity: the Act demands centralized oversight, granular data, and full surveillance inventories to improve accountability, but it forbids additional funding and imposes a sunset — forcing CBP to choose between underfunded compliance that produces poor-quality data or diverting operational resources to meet reporting demands, potentially undermining border security objectives the bill seeks to enhance.
The Act creates a strong transparency and standardization push but places its entire implementation on CBP’s existing budget. That creates a real risk that either the CPMO will operate under-resourced, undermining its effectiveness, or field operations will shoulder additional administrative tasks that reduce time spent on enforcement.
The prohibition on additional funding is likely to drive prioritization choices inside CBP that will shape how comprehensively data collection and training are executed.
Mandating unredacted annual surveillance inventories addresses congressional visibility but raises operational and privacy trade-offs. Detailed public reporting (or even classified-to-congress reporting) of specific sensors, storage locations, and use cases could reveal tactical patterns or sensitive data architectures.
The bill does require documentation of privacy impact assessments and deletion policies, but it does not resolve how to balance transparency with operational security, or who within Congress will receive and safeguard highly sensitive, unredacted details.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.