The Soo Locks Security and Economic Reporting Act of 2025 directs the Secretary of Transportation, coordinating with the Commandant of the Coast Guard and the Secretary of Defense, to deliver a single report within one year that assesses security vulnerabilities at the Soo Locks and quantifies the supply‑chain, logistical, and economic effects of a malfunction or failure. The report must also identify potential domestic and international threats, describe the current security roles of federal, state, and local agencies, and offer recommendations with cost estimates to mitigate risks and reduce disruptions.
This is a narrow, evidence‑gathering measure rather than an authorization for upgrades. By requiring costed recommendations and an interagency analysis, the bill aims to produce a decision‑ready product for Congress and federal agencies: an inventory of weak points, scenarios for economic impact, and ballpark dollars for fixes.
That output can shape future funding, contracts, and contingency planning affecting Great Lakes shippers, regional industry, and national supply‑chain resilience.
At a Glance
What It Does
Within one year of enactment, the Secretary of Transportation — working with the Coast Guard and the Secretary of Defense — must submit to named congressional committees a report that: identifies security deficiencies; models supply‑chain, logistical, and economic impacts of a Soo Locks malfunction or failure; catalogs possible domestic and international threats; sets out the current security roles of federal, state, and local actors; and proposes recommendations with cost estimates for security and resilience measures.
Who It Affects
Primary affected parties include Great Lakes commercial shippers, bulk commodity supply chains (iron ore, grain, coal and similar cargoes), port and terminal operators, and federal agencies (DOT, USCG, DOD) that would produce or act on the study. State and local public safety agencies, regional manufacturers dependent on Great Lakes shipping, and congressional appropriations and oversight committees are also direct stakeholders.
Why It Matters
The Soo Locks are a chokepoint for critical bulk flows in the U.S.; this bill forces a coordinated federal assessment that quantifies vulnerabilities and the economic stakes. Even though it does not appropriate funds, the report’s costed recommendations create a factual basis for future funding, regulatory changes, and contingency plans affecting regional and national supply‑chain resilience.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a short, focused requirement: a single report due to Congress within one year that brings together security and economic analysis for the Soo Locks at Sault Ste. Marie, Michigan.
The Department of Transportation leads the effort and must work with the Coast Guard and the Department of Defense to compile information across agencies and jurisdictions. The law lists the topics the report must cover, so agencies know the deliverable must combine operational security review, economic modeling, and institutional mapping.
On the security side, the report must identify current gaps — physical, technical, procedural, or organizational — and list which authorities and assets are presently responsible for protecting the locks. For economic analysis, agencies must examine how a malfunction or outage would ripple through logistics and commerce, affecting the surrounding region and the United States.
The bill explicitly requires consideration of both domestic and international threats to the locks’ integrity, which pushes agencies to look beyond accidents and natural failures to deliberate interference.A key output the bill demands is recommendations for strengthening security and reducing supply‑chain impacts, accompanied by cost estimates. Those numbers matter: they convert an abstract vulnerability into a dollar figure that Congress and agencies can use to evaluate investment choices.
The statute also names the three committees that will receive the report, focusing oversight and follow‑up on transportation and environmental committees in Congress. Importantly, the text does not authorize appropriations or compel agencies to implement the recommendations — it creates an informational step intended to inform future action.Practical execution will likely require the agencies to combine classified operational assessments with unclassified economic scenarios; the bill does not prescribe how to handle sensitive material or public release requirements.
The one‑year deadline compresses analysis, so agencies will need to prioritize data sharing, scenario selection, and the production of credible cost estimates within that timeframe.
The Five Things You Need to Know
The Secretary of Transportation is the lead and must submit the report no later than one year after enactment.
The Secretary must coordinate with the Commandant of the Coast Guard and the Secretary of Defense on the study and the final report.
The report must identify security deficiencies, assess domestic and international threats, and detail the current security structure across federal, State, and local agencies.
The agencies must analyze the supply‑chain, logistical, and economic effects of a Soo Locks malfunction or failure on the surrounding region and the United States.
The report must include recommendations to strengthen security and reduce supply‑chain impacts, and provide cost estimates for each recommendation; it must be delivered to three named congressional committees.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Establishes the Act’s name as the “Soo Locks Security and Economic Reporting Act of 2025.” This is a conventional labeling provision that does not affect substance but signals congressional intent to tie security and economic analysis to the Soo Locks.
Reporting mandate and lead/coordinating agencies
Directs the Secretary of Transportation to prepare and submit a single report within one year. The provision requires coordination with the Commandant of the Coast Guard and the Secretary of Defense, making DOT responsible for collating interagency inputs and delivering the product to Congress. Practically, DOT will manage both classified and unclassified contributions and ensure the report meets the enumerated content requirements.
Required report contents
Enumerates five discrete analytic tasks: highlight security deficiencies; model supply‑chain/logistical/economic effects of a malfunction or failure; identify potential domestic and international threats; detail the existing security roles of Coast Guard and other agencies; and provide recommendations with cost estimates for security and supply‑chain resilience. Each subparagraph narrows what must be produced, forcing agencies to combine operational assessments with scenario‑based economic analysis and budgetary costing.
Congressional recipients defined
Specifies which congressional committees receive the report: the House Transportation and Infrastructure Committee, the Senate Commerce, Science, and Transportation Committee, and the Senate Environment and Public Works Committee. Naming recipients channels oversight and signals which congressional actors are expected to use the report in hearings or budget deliberations.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation 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
- Great Lakes shippers and terminal operators — receive a consolidated federal study that clarifies vulnerabilities and, if acted on, could lead to prioritized investments and clearer expectations for security requirements.
- Regional heavy industry and commodity exporters (steelmakers, taconite miners, grain processors) — gain quantified scenarios showing economic exposure that can inform business continuity planning and insurance underwriting.
- Federal and state emergency planners and infrastructure agencies — obtain a single, interagency analysis they can use to update contingency plans, tabletop exercises, and intergovernmental response protocols.
- Congressional oversight and appropriations staff — get costed recommendations and threat inventories that make it easier to evaluate and prioritize funding requests in subsequent budget cycles.
Who Bears the Cost
- Department of Transportation, U.S. Coast Guard, and Department of Defense — must allocate staff time, data collection, and analytical resources to produce the report within a compressed one‑year window.
- State and local agencies and port authorities — likely need to provide operational data, incident histories, and participation in interagency interviews, which consumes local resources.
- Private carriers and terminals — may be asked for proprietary traffic, cargo, and routing data to support economic modeling, and could later face new security requirements if Congress or agencies act on recommendations.
- Taxpayers and appropriations committees — while the bill itself does not authorize spending for upgrades, costed recommendations may prompt future budget requests that require federal appropriations.
Key Issues
The Core Tension
The bill forces a classic trade‑off: produce a public, decision‑useful economic and security assessment to justify investments and contingency planning, but doing so risks revealing operational details that could be exploited or must be classified — limiting transparency. Agencies must balance the public need for credible, implementable cost estimates against the operational need to protect sensitive security information.
The statute forces an interagency assessment but stops short of prescribing how to manage classified material, stakeholder confidentiality, or public release. Agencies will balance the need for transparent economic findings with operational security; sections of the report may need to be classified or withheld, reducing public utility.
The one‑year deadline presses operational units and analysts to produce both plausible impact scenarios and defensible cost estimates quickly, which risks reliance on broad assumptions or high‑level modeling rather than exhaustive analyses.
Another unresolved issue is geographic and jurisdictional reach: the bill requires identification of international threats but does not direct consultation with Canadian counterparts or other international partners who share operational responsibility or interest in Soo Locks traffic. That omission could limit the comprehensiveness of threat assessments.
Finally, because the bill only mandates a report (not funding or mandates), its practical effect depends on whether Congress and agencies treat the recommendations as actionable and budget them; the conversion from analysis to investment is an uncertain, political step that the statute does not address.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.