Licensing & pre-application
How the NRC Pre-Application Process Actually Works
Pre-application is the early, voluntary engagement a reactor developer has with the U.S. Nuclear Regulatory Commission (NRC) before it files a license application. It is a working relationship, not a decision. During pre-application the NRC and the developer talk through the developer's approach so that a future application is more complete, but the NRC grants no license, permit, or approval at this stage <sup><a href="#src-1">[1]</a></sup>. Understanding how NRC pre-application works matters because "engaging with the NRC" is often read as an endorsement it is not.
This post explains the process in plain terms and draws the line that the phrase "pre-applicant" is often used to blur. RankShield Energy is a pre-applicant engaged in early interaction with the NRC, which means it holds no license, permit, or approval. That is exactly why the distinction is worth stating carefully. A company has an incentive to make early engagement sound like more than it is, and a reader deserves to know what the stage actually confers. What follows describes the process neutrally, using the NRC's own account of it [1][3].
Key takeaways
- Pre-application is early, voluntary engagement with the NRC before a license application is filed; it grants no license, permit, approval, or safety finding.
- A pre-applicant is a developer that has begun interacting with the NRC, not one whose design has been reviewed or accepted.
- The recognizable steps are a written notice of intent, an assigned project number, a Regulatory Engagement Plan, and pre-application meetings.
- Feedback the NRC staff gives during pre-application is early and generally non-binding, and the staff can revisit it during a formal review.
- If a developer says it is "working with the NRC," read that as its stage in the process, not as an approval of its design.
Pre-applicant, defined
A pre-applicant is a developer that has begun interacting with the NRC about a design or project it may later seek to license, but that has not received, and may not yet have submitted, a license application. The NRC uses pre-application activities to become familiar with a novel design before a formal review begins [1]. RankShield Energy is a pre-applicant. That status describes a stage of engagement; it does not describe a regulatory conclusion about the design.
The distinction is easy to blur. A developer can accurately say it is "working with the NRC" during pre-application, because it is. What it cannot say is that this work has produced a finding, an approval, or a license, because pre-application produces none of those [1]. The NRC's own materials describe pre-application as a way to identify and resolve issues early, so that a later application is more complete and its review more predictable [3]. The value is procedural readiness, not a verdict.
The steps: letter of intent, project number, Regulatory Engagement Plan, and pre-application meetings
Pre-application does not follow a single rigid script, but the NRC describes a recognizable set of interactions [3]. First, a developer notifies the NRC in writing of its intent to engage, describing at a high level the design and the interactions it expects to seek. Second, the NRC assigns a project number so the correspondence and meetings tied to that developer can be tracked as an organized record [1].
Third, the developer and the NRC staff can develop a Regulatory Engagement Plan, a shared document that lays out the topics the developer intends to raise, the submittals it expects to make, and an approximate schedule for the interactions [2]. The plan is a planning tool the two sides maintain together. It is not an application, and it commits the NRC to no outcome. Fourth, the developer and the staff hold pre-application meetings, which may address the design approach, the licensing path the developer is considering, and the technical questions a future application would need to answer [3]. Each step prepares the ground for a possible application. None of them is one.
What pre-application does and does not grant
Pre-application engagement does not grant a license, a permit, a design approval, or a safety finding, and it is not an NRC endorsement of the developer or its design [1]. What it grants is process: a channel to raise questions with the NRC staff, early feedback on the licensing path and on what a future application will need to address, and a project number that organizes the record of those interactions [1][3]. Feedback the staff offers during pre-application is generally not a binding regulatory decision, and the staff can revisit any position once it conducts a formal review of an actual application. A developer therefore leaves pre-application better prepared, not pre-approved. The only way to obtain an NRC license or approval is to submit an application and complete the NRC's formal review, which happens after, and separately from, pre-application. RankShield Energy is a pre-applicant and holds no NRC license, permit, or approval.
In my view, the cleanest way to read any developer's NRC relationship is to assume nothing beyond what the stage itself confers. Engaged, not endorsed. When a developer, including us, describes its NRC interaction, the honest version names the stage and stops there, rather than borrowing credibility the stage does not confer.
Why serious developers engage early
Early engagement exists because advanced-reactor designs often differ from the light-water reactors that the NRC's older frameworks were written around. Pre-application gives the staff time to understand a novel approach, and it gives the developer time to hear, before it commits an application to paper, where the review is likely to focus [3]. The NRC frames the goal as a more complete application and a more predictable review, which serves both the applicant and the public interest in a thorough evaluation [1][3].
For a buyer, an insurer, or a lender reading a developer's regulatory claims, the practical takeaway is to calibrate expectations to the stage. A developer in pre-application is doing the early, transparent work of a serious licensing effort. It has not been told its design is acceptable, because that determination belongs to a formal review that has not happened. Reading the stage accurately protects everyone from mistaking diligence for a decision.
Frequently asked questions
What is an NRC pre-applicant?
An NRC pre-applicant is a reactor developer that has begun interacting with the NRC about a design or project it may later seek to license, before submitting a formal application <sup><a href="#src-1">[1]</a></sup>. The status reflects a stage of engagement. It does not carry a license, a permit, or an NRC finding about the design. A pre-applicant can accurately say it is engaged with the NRC, and RankShield Energy is a pre-applicant, but that is a description of where it stands in the process, not a regulatory approval.
Does pre-application mean the NRC approved the design?
No. Pre-application produces no license, permit, design approval, or safety finding, and it is not an endorsement <sup><a href="#src-1">[1]</a></sup>. Any feedback the NRC staff gives during pre-application is early and generally non-binding, and the staff can revisit its views when it formally reviews an actual application <sup><a href="#src-3">[3]</a></sup>. An NRC approval or license comes only from submitting an application and completing the agency's formal review, which occurs separately from and after pre-application. A developer that is in pre-application has not, by virtue of that stage, had its design approved.
What is a Regulatory Engagement Plan?
A Regulatory Engagement Plan is a document a developer and the NRC staff can maintain together during pre-application to organize their interactions <sup><a href="#src-2">[2]</a></sup>. It typically outlines the topics the developer plans to raise, the submittals it expects to make, and an approximate schedule. The plan is a planning and coordination tool. It is not an application, it does not bind the NRC to any outcome, and maintaining one does not indicate that a design has been reviewed or accepted.
Is pre-application required before applying for a license?
Pre-application is generally encouraged rather than strictly required, and it is especially useful for novel or first-of-a-kind designs that differ from the reactors the NRC has licensed before <sup><a href="#src-3">[3]</a></sup>. A developer engages early so that questions surface before an application is written, which the NRC describes as supporting a more complete application and a more predictable review <sup><a href="#src-1">[1]</a></sup><sup><a href="#src-3">[3]</a></sup>. Choosing to engage early is a sign of a developer preparing carefully. It is not, by itself, a regulatory milestone or an approval.
Sources
This guide reflects the NRC's advanced-reactor pre-application process as of July 2026. NRC guidance and process pages are updated periodically; check the NRC's pre-application pages if you need the current procedure.
About this article. RankShield Energy is a pre-applicant engaged in early regulatory interaction with the U.S. Nuclear Regulatory Commission (NRC). Nothing here should be read as a representation that any RankShield Energy design, product, or facility is NRC-approved, licensed, or certified, or that any safety, performance, or operational characteristic has been demonstrated or accepted by the NRC. Descriptions of reactor and system behavior reflect design intent and are subject to analysis, testing, and regulatory review. This article is for general educational purposes and is not engineering, legal, regulatory, or investment advice.
A note on how we write about our own reactor
HELIX is in pre-application development. Where this article touches our design, every figure is a design target and every physics result is unqualified screening, labeled as such. We cite authoritative sources (NRC, DOE, IAEA, national laboratories) and never invent statistics.
RankShield Energy · HELIX · pre-application