FORGE's Planned Project Registry Stops Short of Financing Eligibility · Traverse Analysis
FORGE's Planned Project Registry Stops Short of Financing Eligibility
FORGE's planned registry raises a critical minerals project's visibility, but it does not establish financing eligibility, procurement preference, or an award. Sponsors still need an agency-specific bankability file and a controlled plan for sharing commercial data.
The registry can put a project in front of coalition governments, public finance institutions, and potential buyers. That is a real coordination benefit. It does not establish financing eligibility, a procurement preference, credit approval, or an award.
The distinction matters because the FORGE Guiding Principles give the Project Investment Working Group a broad assignment. It is expected to maintain a registry of priority projects, connect downstream demand with supply, and coordinate finance and offtake support. None of those steps replaces the decision that a lender, export credit agency, development finance institution, buyer, or procurement authority must make under its own mandate.
As chair, Washington can shape how project information moves through the coalition. For sponsors, the immediate task is to track four distinct statuses in board papers and fundraising materials. Those statuses are candidate, coalition priority, eligible under a named agency program, and approved or awarded. Conflating them can turn diplomatic attention into a claim the public record does not support.
Registry inclusion would establish coalition priority only
The registry is designed to solve a visibility problem. Critical minerals projects can stall because a mine, processor, recycler, buyer, lender, and government support program do not reach the same decision at the same time. A shared list can give participating governments a common picture of projects that meet the coalition's policy interests. It can also help officials identify gaps between upstream supply and downstream demand.
That function is valuable before financing. A project sponsor may gain introductions to agencies or buyers that would otherwise evaluate the market in isolation. Governments may see that several proposed mines depend on the same processing bottleneck, or that a planned refinery lacks enough contracted demand. A common registry can make those coordination failures visible without resolving them.
The public principles do not state that registry inclusion creates a right to finance, a common credit standard, a procurement set-aside, or an offtake commitment. They also do not publish a universal application form, scoring rubric, review deadline, or appeal process. The registry therefore supports discovery and coordination. Any stronger status needs a separate record from the institution that can grant it.
Sponsors should use precise language. "Identified as a FORGE priority" describes coalition attention if an official record supports it. "Eligible for EXIM financing" requires an EXIM basis. "Approved" requires an institution-specific approval record. "Financing committed" requires an executed, legally binding arrangement, subject to its terms. "Funded" requires a disbursement record. Each statement answers a different diligence question.
The July principles assign coordination without a common approval test
FORGE was launched at the February 4 Critical Minerals Ministerial as the successor to the Minerals Security Partnership. The July principles organize its work around Project Investment and Policy Coordination. One track focuses on projects, finance, and demand. The other addresses policy tools, market disruptions, nonmarket practices, and shared messaging.
The instrument is nonbinding. An official EU document record described the planned framework as a multilateral nonbinding instrument during its formation. The final principles also rely on consensus. These features allow a wide coalition to exchange information and align political support without creating a single supranational financing authority.
Consensus does not mean that every member has accepted another member's credit rules, procurement law, environmental review, national-security conditions, or domestic-content tests. It means the coalition can organize joint work around agreed objectives. A registry may be shared while the legal effect of an entry remains domestic and institution-specific.
That is the central operating boundary. FORGE can reduce search costs and sequence public support. It cannot erase an institution's governing mandate or underwriting criteria. If a member government later gives registry status a defined benefit, the benefit should appear in that government's own rule, program notice, procurement instrument, or transaction decision.
Financing remains an agency-specific decision
EXIM's current critical minerals material shows what an actual eligibility path looks like. Its Single Point of Entry with Export Finance Australia offers faster referrals, coordinated feedback, and potential joint financing for eligible transactions. EXIM's dedicated critical minerals page says support remains subject to its environmental and social due diligence procedures, International Finance Corporation Performance Standards, relevant third-country and internationally accepted standards, and other U.S. government policy. This is an EXIM review framework, not a FORGE eligibility rule.
That is more concrete than coalition priority. It identifies institutions, a transaction pathway, and agency review requirements. Even then, a referral or an estimate is not a board approval. Credit quality, repayment sources, country exposure, environmental and social review, U.S. benefit, procurement structure, and transaction documentation can remain relevant depending on the program and deal.
Project Vault shows the next step in the status chain. On February 2, the EXIM Board approved a direct loan of up to $10 billion for a public-private critical minerals reserve. The release identifies the board action, the instrument, the maximum amount, manufacturers with initial indications of participation, and suppliers servicing Project Vault. Those are the features of a transaction-specific approval record.
A future FORGE registry could help an agency find a Project Vault candidate or assemble a group of buyers. It would not reproduce the EXIM Board's action. Sponsors should expect two files to move in parallel. The coalition file explains strategic importance, allied demand, supply-chain diversification, and partner interest. The agency file proves that the transaction fits a mandate and can survive underwriting.
House-passed legislation maps machinery that remains unenacted
The House-passed text of H.R. 7037 supplies a legislative comparison. Its Section 102 still uses the predecessor name Minerals Security Partnership rather than FORGE. It would authorize project identification, a critical minerals project database, coordination with finance institutions, and work on pricing, procurement, political-risk insurance, and equity investment. It also would require procedures for handling commercial information shared with partnership members.
The engrossed text is useful because it separates functions that general coalition language can blur. Identifying a priority project is one function. Building and maintaining a database is another. Coordinating finance is another. Approving money or procurement remains with the authorized institution. The proposed text places several of those pieces next to each other without declaring them identical. Its older partnership name also means the bill cannot be assumed to govern the successor coalition without further legislative or executive clarification.
The official GovInfo bill status records House passage as amended by voice vote on June 8. The Senate received the bill, read it twice, and referred it to the Committee on Foreign Relations on June 9. It has not become law. The House-passed text therefore cannot be cited as current FORGE authority or as authority for a present financing entitlement.
Companies can still use it as a map of implementation questions. Which office owns the registry? What project data will be collected? How will priorities be selected? Which support tools can be coordinated? How will proprietary information be protected? Answers published under current executive authority, or later enacted by Congress, would narrow the gap between coalition visibility and transaction eligibility.
Commercial data needs a release plan before coalition circulation
A useful project registry needs information that sponsors often treat as sensitive. Resource estimates, cost curves, customer discussions, expected production, financing gaps, ownership, permitting risk, and offtake terms help governments judge whether a project can reduce a supply-chain vulnerability. The same details can affect negotiations with lenders, buyers, local partners, or potential acquirers.
The House-passed H.R. 7037 text recognizes that tension for the Minerals Security Partnership. Its proposed information-sharing provisions would require collection and transmission procedures and would limit disclosure of geological, geophysical, trade-secret, commercial, and financial information. The text calls for aggregation or other reporting methods designed to avoid identifying a source person. Those provisions have not become law or the statutory operating rules for FORGE, but they identify a real control problem.
A sponsor should not solve that problem by withholding every useful fact. A registry that contains only a project name and a promotional capacity number will not help institutions coordinate. The better approach is a tiered file. A coalition summary can state location, mineral, stage, intended capacity, strategic gap, permitting posture, financing need, and broad demand evidence. A controlled annex can hold detailed cost, customer, reserve, technology, and ownership records for institutions that have an identified authority and protection process.
Before submission, counsel and the commercial team should mark who supplied each data point, whether it can cross borders, what confidentiality promise applies, and what public statement the project can support. If FORGE publishes a common data protocol, that protocol becomes a key diligence document. Until then, the sponsor should confirm the receiving institution and handling terms rather than infer protection from coalition membership.
Sponsors should report four statuses inside the company
The cleanest internal control is a four-stage status table. The candidate stage means a government, company, or coalition participant is considering the project. It carries no formal benefit. The coalition-priority stage means an authorized FORGE record identifies the project for coordinated attention. It can support meetings and policy engagement, but its legal effect depends on the record.
The agency-eligible stage begins only when a named institution confirms that the project can proceed under a program or satisfies threshold criteria. That confirmation may still be conditional and should be quoted with its limits. The approved-or-awarded stage requires the relevant institution's decision record, such as a board authorization, procurement award, or insurance approval. A signed financing agreement and a disbursement record are separate later evidence and should be reported with their conditions.
Each status should have an evidence field, owner, date, and next gate. A board memo might link the FORGE record for coalition priority, an agency correspondence for eligibility, and a board resolution for approval. Investor materials should use the narrowest supported term. If the only record is a meeting or registry nomination, "government-backed financing" is too strong.
This discipline also improves project execution. A sponsor can see whether its bottleneck is political visibility, program fit, bankability, customer demand, or final documentation. It can then ask FORGE for the coordination the coalition is designed to provide while sending the financing institution the evidence its own process requires.
The next operating signal is a published selection process
The U.S. chairmanship can make the registry more consequential without changing its legal character. The most useful next records would be a named registry owner, submission channel, selection criteria, update schedule, data-handling protocol, and a statement of what member institutions do after a project is listed. Those details would let sponsors distinguish a diplomatic directory from an active project pipeline.
Transaction records will matter more than broad commitments. Watch for a named project entering the registry, a finance institution issuing an eligibility or approval notice, a buyer signing an offtake agreement, or a procurement authority creating a defined preference. The links among those records will show whether FORGE is reducing the timing and coordination failures that have kept projects from reaching construction.
The current evidence supports a narrower conclusion. FORGE has created a coalition framework for identifying projects and coordinating policy, finance, and demand. It has not published a common financing entitlement. A project sponsor can use the registry to get the right institutions into the same process. The financing claim begins only when one of those institutions acts under its own authority.
Free account
Keep reading with a free account.
Today's analysis is open to everyone. A free account opens the full archive and full tool output. No card required.