This bill adds a new reporting requirement to the Federal Power Act that directs the Federal Energy Regulatory Commission to tell Congress, each year, where pending hydropower license applications stand. It targets applications that are already known to FERC — either where an existing licensee said it planned to reapply or where a third party signaled intent to seek an original license — but for which no new license has yet been issued.
For practitioners, the change matters because it converts relicensing case-level status into regular, standardized congressional reporting. Developers, tribes, states, resource agencies, and FERC staff should expect more public visibility into pending relicensing dockets and potential pressure to explain delays or anticipated decision dates.
At a Glance
What It Does
The bill adds Section 37 to the Federal Power Act, requiring FERC to submit its first report within 180 days of enactment and annually thereafter. Reports must cover two categories of pending proceedings (new/subsequent licenses tied to existing licensee notices and original licenses tied to third-party notices) and include specific docket and status data, upcoming proceedings, and a description of actions taken by all involved parties.
Who It Affects
Directly affected parties include FERC, existing hydropower licensees who have notified intent to reapply, third-party prospective applicants (citizens, associations, corporations, States, Indian Tribes, and municipalities), fish and wildlife agencies referenced in section 15(b)(3), and congressional committees that oversee energy and natural resources.
Why It Matters
The reporting requirement creates a durable oversight tool for Congress and a public record of relicensing progress that developers and resource agencies can use for planning. It also formalizes a standardized data set that can highlight procedural bottlenecks and interagency coordination issues in the hydropower relicensing pipeline.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill instructs FERC to compile an annual inventory of hydropower relicensing matters that have been signaled to the agency but not yet resolved. It focuses on two trigger events: (1) when an existing licensee notifies FERC under the Federal Power Act’s relicense provisions that it intends to file at least three years before the report date; and (2) when a non-licensee (for example, a tribe, municipality, or private entity) files a regulatory notice of intent to seek an original license at least three years before the report date.
Those triggers narrow the universe to projects already on FERC’s radar rather than every potential future application.
For each matter that meets the inclusion thresholds, FERC must collect a short set of administrative and scheduling details: when the notice was received, whether an application is on file, any docket identifiers, the status of the proceeding and an anticipated issuance date, scheduled hearings or meetings, and a concise description of steps completed or outstanding for all named actors (existing licensee or prospective applicant, FERC, resource agencies, and any other relevant bodies). The statute also requires that FERC present its findings separately for new/subsequent licenses under the relicense provisions and for original licenses under the statutory provision that governs non-FERC-started projects.Operationally, the mandate pushes FERC to standardize status-tracking across relicensing streams so it can produce a consistent brief for Congress each year.
That standardization likely means drawing information from dockets, notices-of-intent, interagency coordination records, and input from state and federal resource agencies. The result is intended to make visible where relicensing is delayed, what agencies or steps are implicated in delays, and when FERC expects decisions — information stakeholders can use to prioritize engagement or to press for resolution.
The Five Things You Need to Know
The bill requires FERC to deliver the first status report to Congress within 180 days after the law is enacted and to repeat that reporting on an annual basis.
Only matters where a notice of intent was provided at least three years before the report are included — covering existing-licensee relicense notices and third-party notices for original licenses.
Each report must state whether an application has been filed, provide any docket numbers, list upcoming proceedings, and give an anticipated date for issuance where available.
Reports must describe actions completed or required of each named actor: the applicant or licensee, FERC itself, fish and wildlife agencies noted in the statute, and any other applicable agencies.
All data in the report must be disaggregated by license type: (a) new or subsequent licenses processed under the relicense provisions and (b) original licenses processed under the statutory original-license provision.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — Hydropower Licensing Transparency Act
This is the bill’s caption. It has no operative effect but signals congressional intent that the measure is about increasing transparency in the hydropower relicensing lifecycle.
Who and when FERC must report
Subsection (a) sets the reporting duty and timing: FERC must submit the first report within 180 days of enactment and then annually. It defines the two categories of proceedings to include — (i) certain new or subsequent licenses tied to existing-licensee notices under the relicense provisions, and (ii) original-license proceedings tied to third-party notices under the original-license provision — but only when the applicable notice was filed at least three years before the report date and no license has yet issued.
Required content for each covered proceeding
Subsection (b) lists specific items each report must contain: the date the notice was filed with FERC; any docket number; whether an application exists; a status summary including an anticipated issuance date; dates for upcoming proceedings or meetings; and a description of steps taken or outstanding for all implicated parties (applicant/licensee, FERC, fisheries and wildlife agencies referenced in the statute, and other agencies). Practically, this compels FERC to pull scheduling, docket, and interagency coordination information into a single, Congress-ready product.
Disaggregation by license type
Subsection (c) requires FERC to separate the reported items by license category: one set for new/subsequent licenses handled under the relicense process, and another set for original-license matters handled under the original-license provision. That separation lets Congress and stakeholders compare timelines and choke points across distinct procedural routes.
This bill is one of many.
Codify tracks hundreds of bills on Energy across all five countries.
Explore Energy 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 oversight committees — gain a consistent, annual dataset to monitor relicensing backlogs, compare timelines, and target oversight or legislative fixes.
- Prospective applicants and local governments (States, municipalities, Indian Tribes) — receive clearer visibility into where their pending original-license matters stand and can use the report to coordinate strategy or escalate concerns.
- Environmental and fish-and-wildlife agencies — benefit from a more public record that can document where their required consultations or recommendations fit into the overall schedule.
- Project developers and investors — obtain standardized information that can reduce uncertainty around expected issuance dates and improve planning for capital deployment or project timelines.
Who Bears the Cost
- FERC — must absorb the administrative work of aggregating, verifying, and annually publishing detailed docket- and schedule-level information, which will require staff time and likely new data workflows.
- State and federal resource agencies (including fish and wildlife agencies) — will face repeated requests for timely status updates and may need to formalize information-sharing to meet FERC’s reporting cadence.
- Existing licensees and prospective applicants — increased public disclosure of procedural status and anticipated dates may create pressure, public scrutiny, or strategic consequences (for example, competitive or political pressure) that change negotiation dynamics.
- Smaller applicants and intervenors — could face indirect costs if they need to engage more frequently to ensure their actions are reflected accurately in FERC’s annual report.
Key Issues
The Core Tension
The central trade-off is accountability versus feasibility: Congress gains a standardized, public view into the relicensing pipeline, which improves oversight and predictability, but that transparency imposes recurring operational costs on FERC and other agencies and risks pressure to produce precise timelines that the administrative process cannot reliably guarantee.
The bill trades opacity for recurring administrative burden. Producing a reliable annual snapshot requires FERC to reconcile docket records, agency inputs, and applicant statements — and the statute’s demands for an anticipated issuance date could force FERC to provide forecasts that are inherently speculative.
Those forward-looking dates may be useful signals but risk creating false expectations or litigation if they are repeatedly revised.
The statute also raises questions about confidentiality and sensitive business information. The reporting items are largely administrative, but some status descriptions or anticipated dates may reveal commercially sensitive schedules.
The bill does not create a clear mechanism for protecting legitimately confidential information while still meeting Congress’s oversight needs. Finally, the requirement focuses on proceedings with a three‑year notice — a sensible cutoff to limit the universe — but it may omit shorter-cycle matters or novel filings, meaning the report will not be a complete map of all licensing activity and could give a skewed impression of overall workload.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.