The bill amends section 403(b) of the FISA Amendments Act of 2008 to change two statutory references to the repeal date for Title VII: it replaces "April 30, 2026" with "June 12, 2026." The change appears in the 50 U.S.C. 1881 note and the 18 U.S.C. 2511 note, leaving existing substantive authorities intact.
The bill also sets an unusual effective-date rule: the amendment takes effect on the earlier of the date of enactment or April 29, 2026. Practically, that language is designed to prevent any gap in Title VII authorities by making the extension effective no later than April 29, 2026, but it raises questions about retroactivity and operational notice for agencies and outside parties.
At a Glance
What It Does
The bill replaces two statutory references to the Title VII repeal date from April 30, 2026 to June 12, 2026, producing a roughly six-week extension of the current statutory authorities. It does not change the substance of Title VII; it only alters the sunset date.
Who It Affects
The immediate subjects are the federal intelligence community and any entities that interact with Title VII collection authorities (for example, telecommunications carriers and contractors that handle collection or compliance). Oversight bodies that monitor Title VII activity also retain jurisdiction for an additional six weeks under the statutory timeline.
Why It Matters
A short extension avoids an operational lapse in authority that would otherwise kick in on April 30, 2026, while preserving Congress’s ability to negotiate longer-term reauthorization. The effective-date language, which can operate retroactively to April 29, 2026, creates legal and implementation questions that agencies and counsel will need to address quickly.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill makes a narrow, mechanical change: it strikes the date "April 30, 2026" from two places in the statutory notes that govern the repeal of Title VII authorities and inserts "June 12, 2026" in both spots. Those notes are editorial statutory history provisions that point to the scheduled repeal of the FISA Amendments Act authorities (Title VII).
The amendment does not alter programmatic language, reporting requirements, oversight mechanisms, or criminal provisions tied to those authorities.
The statutory citations the bill edits are the note to 50 U.S.C. 1881 and the note to 18 U.S.C. 2511; both are used in current practice to memorialize the scheduled sunset. Because the bill only amends those notes, compliance officers and program managers should read this as a timing fix rather than a change in authority scope, but they must still adjust calendars, contract timelines, and any statutory notices that referenced an April 30 expiration.The bill’s effective-date clause says the amendments take effect on the earlier of the date of enactment or April 29, 2026.
That wording means the date change can operate retroactively to April 29 if the bill is enacted after that date, ensuring no gap between the original repeal date and the new repeal date. Retroactivity should be taken into account for any actions or certifications that would have been affected on or near the original sunset date.Finally, because the amendment is time-limited and narrowly tailored to the sunset language, agencies do not receive new authority or new reporting obligations from this bill.
The practical effect is continuity: programs that rely on Title VII authorities can continue to operate under the current statutory framework for an additional ~six weeks while Congress or others consider longer-term reauthorization or reform.
The Five Things You Need to Know
The bill amends section 403(b) of the FISA Amendments Act of 2008 by replacing the date "April 30, 2026" with "June 12, 2026" in two statutory notes (50 U.S.C. 1881 note and the 18 U.S.C. 2511 note).
The extension length is approximately six weeks (April 30 to June 12, 2026), moving the scheduled repeal forward by 43 days.
The bill includes an effective-date provision making the amendments effective on the earlier of the date of enactment or April 29, 2026, which can render the change retroactive to April 29 if enacted later.
The bill does not amend operational or oversight language in Title VII itself; it does not add, remove, or modify substantive surveillance authorities—only the statutory sunset date.
Because the change is confined to statutory notes, administrative and compliance adjustments are mostly calendaring and notice-related rather than substantive programmatic changes.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Replace repeal date in 50 U.S.C. 1881 note
This clause strikes the existing date "April 30, 2026" in paragraph (1) of section 403(b) and inserts "June 12, 2026." Practically, this updates the historical statutory note tied to 50 U.S.C. 1881 (the FISA Amendments Act) so that the internal cross-reference reflects the new repeal date. For practitioners, the key takeaway is that any compliance schedule keyed to the 50 U.S.C. 1881 note must be adjusted to the new date; it does not change substantive authority language in the U.S. Code.
Replace repeal date in 18 U.S.C. 2511 note
This clause performs an analogous edit in paragraph (2) of section 403(b), replacing the same April 30 date in the note to 18 U.S.C. 2511. That note has been used to tie Title VII authorities to the broader statutory framework governing interception and electronic surveillance. The change synchronizes both statutory notes to the same new repeal date and reduces the risk of conflicting citations in statutory references or legal briefs.
Effective-date clause (retroactivity safeguard)
The amendments take effect on the earlier of the date of enactment or April 29, 2026. That wording functions as a safeguard against a lapse: if the bill becomes law after April 29, the amendment operates as if it were in effect on April 29 (i.e., retroactively), preventing any period between April 30 and the later enactment date in which the prior repeal date could have produced an authority gap. The clause raises operational and legal questions about retroactive effect, notice to third parties, and what actions taken in the intervening period will be treated as authorized.
This bill is one of many.
Codify tracks hundreds of bills on Privacy across all five countries.
Explore Privacy 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
- Intelligence community agencies (e.g., NSA, FBI): They retain Title VII authorities without interruption, avoiding operational pauses that would disrupt collection, tasking, and targeting workflows tied to the statutory timeline.
- Oversight bodies and compliance offices (ODNI, DOJ, FISC processes): They gain extra time to continue oversight under the existing statutory framework and to prepare for any longer-term reauthorization work without an immediate deadline-driven gap.
- Telecommunications carriers and service providers: They avoid abrupt changes to legal obligations and production timelines tied to Title VII authorities, preserving the status quo for a limited period.
- Contractors and program managers who support Title VII collection: They keep existing contracts and tasking intact for the short extension, avoiding immediate contractual and operational churn.
Who Bears the Cost
- Civil liberties and privacy advocacy organizations: The short extension reduces the immediate policy window available to press for reforms or expiration of Title VII authorities, limiting near-term leverage.
- Congressional oversight staff and committees: They inherit a compressed schedule for any meaningful reauthorization or substantive reform work because a six-week extension is short for drafting, hearings, and negotiation.
- Agency legal and compliance teams: They must interpret and implement the retroactive effective-date language, update internal guidance and notices, and manage any potential disputes about actions taken around the original sunset date.
- Entities tracking legal certainty (cloud providers, international partners): They bear uncertainty about the legal status of collection in the narrow window around the original sunset date and may need to assess exposure or change control procedures.
Key Issues
The Core Tension
The bill prioritizes short-term continuity of national-security collection authorities over a deliberative reauthorization process: it prevents a disruptive lapse by moving the repeal date forward (and by making that move effectively retroactive), but it also shrinks the window for meaningful oversight and legislative reform, leaving unresolved substantive issues to be resolved under time pressure.
The bill solves a discrete timing problem but introduces two implementation puzzles. First, the effective-date clause that uses the earlier of enactment or April 29, 2026, creates a retroactivity mechanism: if Congress enacts the bill after April 29, the amendments legally operate as if they were in place on April 29.
That protects against a lapse but can complicate questions about notice, administrative action, or contractual obligations undertaken between April 29 and the later enactment date. Agencies and affected third parties will need to decide whether to treat actions taken in that window as authorized, potentially prompting litigation or claims over retroactive authorization.
Second, the bill is narrowly temporal and does not address substantive concerns that often accompany Title VII reauthorizations (oversight changes, minimization procedure updates, disclosure rules, or statutory reforms). The short extension preserves operational continuity but compresses the time available for Congress and stakeholders to negotiate any substantive changes.
That creates a trade-off between continuity and deliberative reform: continuity is achieved, but substantive questions remain unresolved and may be harder to address on an accelerated timetable.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.