HB 2212 amends Section 844 of the Homeland Security Act of 2002 by adding a new subsection that directs the Secretary of Homeland Security to require every DHS component that is part of the DHS Intelligence Enterprise to participate in the ODNI Intelligence Community Civilian Joint Duty Program. Participation must be carried out in a manner consistent with policies the Director of National Intelligence establishes for that program.
The change is narrow in text but consequential in practice: it moves DHS components from optional to required participation in a formal ODNI-managed civilian joint‑duty scheme. That creates new coordination obligations for DHS leadership and human‑capital offices, raises staffing and clearance logistics, and potentially changes career paths for DHS intelligence civilians — all without explicit funding or detailed implementation rules in the bill itself.
At a Glance
What It Does
The bill inserts a requirement into 6 U.S.C. 414 that all DHS components within the DHS Intelligence Enterprise must participate in the ODNI Intelligence Community Civilian Joint Duty Program and do so consistent with DNI policies. It does not alter the text of the ODNI program itself or specify selection, duration, or enforcement mechanisms.
Who It Affects
The requirement applies to DHS components that are members of the DHS Intelligence Enterprise (for example, intelligence offices within custody of component agencies), DHS human resources and personnel offices that manage assignments and clearances, ODNI program administrators, and the civilian employees eligible for joint duty rotations.
Why It Matters
Making participation mandatory changes workforce planning assumptions across DHS and ODNI: expect increased interagency rotations, tighter DNI control over program rules as applied at DHS, and operational consequences where components must provide personnel for external assignments or accept rotational assignees.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
HB 2212 is a single-purpose amendment to the Homeland Security Act of 2002. It adds a subsection to the statute that makes participation by DHS components in the ODNI Intelligence Community Civilian Joint Duty Program a requirement rather than a discretionary option.
The operative instruction is short: the Secretary of Homeland Security must require participation and must do so in ways that align with the Director of National Intelligence’s policies for the program.
Because the bill references ODNI policies, DHS components will be bound by rules the ODNI publishes for the civilian joint‑duty program — rules that can cover eligibility, tour length, performance expectations, and credit toward joint duty qualifications. The bill does not reproduce those rules, nor does it modify the ODNI program; it creates a statutory duty for DHS to conform to the ODNI framework where DHS components are members of the agency’s Intelligence Enterprise.Practically, the amendment shifts several administrative tasks to DHS and ODNI: identifying which component positions are eligible, coordinating security clearances and access for rotation staff, arranging backfill while employees are detailed, and tracking joint‑duty credits.
The statute does not attach new funding, timelines, or reporting requirements, so implementation will depend on existing DHS and ODNI processes and any interagency agreements they negotiate. The bill also leaves open whether participation is mandatory for all employees within a covered component or limited to specific positions designated by DHS and ODNI under their policies.Finally, while the short title mentions law enforcement support, the operative text addresses only civilian participation in the ODNI joint duty program.
It does not create new investigative authorities, change law enforcement missions, or alter classified‑information rules; those operational matters remain governed by existing statute, DHS policy, and ODNI program guidance.
The Five Things You Need to Know
The bill amends 6 U.S.C. 414 (Section 844 of the Homeland Security Act) by adding a new subsection that mandates DHS component participation in the ODNI Intelligence Community Civilian Joint Duty Program.
Participation must be consistent with policies established by the Director of National Intelligence, which means DHS cannot deviate from ODNI’s program rules when carrying out assignments.
The text creates a mandatory participation duty but contains no funding authorization, specific timelines, selection criteria, or enforcement penalties.
Coverage is limited to DHS components that are members of the DHS Intelligence Enterprise; the bill does not define new categories of employees beyond that membership.
The bill does not change ODNI’s program structure; it only requires DHS components to take part under the ODNI-established policy framework.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Gives the act its public name: the 'DHS Intelligence Rotational Assignment Program and Law Enforcement Support Act.' This is a conventional short title and has no substantive effect on responsibilities or authorities; it primarily frames legislative intent but should not be read as expanding the single textual amendment that follows.
Mandatory participation in ODNI civilian joint‑duty program
Adds a new subsection to Section 844 requiring the Secretary to ensure that all DHS components that are members of the DHS Intelligence Enterprise participate in the ODNI Intelligence Community Civilian Joint Duty Program. The wording ties DHS participation to the policies established by the DNI, making ODNI policy the governing standard for how DHS implements joint‑duty rotations. The provision does not set eligibility, duration, or personnel-management rules; those details will derive from ODNI policy and DHS implementing actions.
What the statute requires — and what it leaves to agencies
The statute imposes a general requirement without accompanying resources, deadlines, or enforcement language. That means DHS and ODNI must negotiate operational details—such as which billets are exchangeable, how to handle security‑clearance reciprocity, who pays travel and relocation costs, and how to credit joint duty for promotion — through interagency memoranda and internal policies. Congress did not specify reporting, oversight metrics, or administrative penalties for noncompliance.
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
- DHS civilian intelligence employees seeking joint‑duty experience — the bill opens program access by making participation a departmentwide requirement, increasing rotation opportunities that count toward IC joint‑duty qualifications.
- ODNI and the broader Intelligence Community — mandatory DHS participation enlarges the pool of DHS personnel available for cross‑agency assignments, improving breadth of experience and interoperability across agencies.
- Career development offices and interagency HR planners — the change creates clearer statutory authority to include DHS staff in joint duty pipelines, allowing HR planners to integrate rotations into career tracks and succession planning.
Who Bears the Cost
- DHS component mission managers and program offices — they must provide backfill for rotational details, which can burden small offices or specialized units when experienced staff are moved temporarily.
- DHS and ODNI human resources and security offices — these teams shoulder administrative costs for vetting, clearances, placement logistics, and recordkeeping without an appropriation attached to the bill.
- DHS budget managers — participation likely increases mobility costs (travel, relocation, per diem, training, and temporary staffing), requiring internal reallocation of funds or new budget requests.
- Employees with critical operational roles — mandatory rotations can create tension where mission continuity depends on retained technical expertise that may be exposed to rotational turnover.
Key Issues
The Core Tension
The central dilemma is between stronger interagency integration and the operational integrity of DHS components: mandatory joint‑duty participation advances cross‑cutting intelligence experience and IC cohesion but risks degrading mission continuity, imposes administrative and budgetary burdens on DHS components, and raises questions about how to reconcile ODNI policy requirements with component‑level staffing realities.
The statute stitches ODNI program rules into DHS statutory obligations but leaves crucial design questions unanswered. Most prominently, the bill does not allocate money or create an administrative framework for how DHS and ODNI should coordinate staffing, pay, or backfill.
That gap means implementation will depend on interagency agreements and internal reprioritization of resources, which can produce uneven outcomes across components. Smaller DHS elements with limited personnel may find compliance more disruptive than larger offices that already engage in interagency rotations.
The bill also imports ODNI policy as the controlling standard without clarifying how conflicts between ODNI program rules and existing DHS collective‑bargaining agreements, position descriptions, or mission‑specific statutes will be resolved. Security‑clearance reciprocity, classification access, and duty credit toward promotion are all handled in operational guidance that the bill does not amend.
Finally, the short legislative language gives DHS little explicit discretion about exemptions or phasing, so the practical boundary between mandatory participation and reasonable operational exceptions will be established administratively rather than legislatively, inviting disputes and potential oversight questions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.