# Which NRC Regulations Apply to a Microreactor Today?

> A regulatory applicability analysis of the four NRC licensing pathways open to a microreactor developer, the guidance above them, and where the choices lie.

[Resources](https://rankshieldenergy.com/resources) / Technical papers Technical papers

# Which Regulations Apply to a Microreactor? A Framework Applicability Analysis
Published August 11, 2026 · By [Jamie Kloncz](https://rankshieldenergy.com/authors/jamie-kloncz), Founder, RankShield Energy

HELIX microreactor, concept render. RankShield Energy is at the pre-application stage; this depicts a design under development, not an operating facility. Technical paper · document control
Document type Technical paper Version 1.0 Published August 11, 2026 Revised August 11, 2026 Status Regulatory applicability analysis, open for comment Regulatory status RankShield Energy is a pre-applicant engaged in early regulatory interaction with the U.S. Nuclear Regulatory Commission. RankShield Energy holds no NRC license, permit, or design approval. No RankShield Energy design, product, or facility, and no safety, performance, or operational characteristic of one, has been demonstrated to or accepted by the NRC. Descriptions of design behaviour are design intent and are subject to analysis, testing, and regulatory review.

## Abstract
A developer bringing a microreactor to the U.S. Nuclear Regulatory Commission today meets several licensing frameworks rather than one, together with a body of guidance that shapes an application without carrying the force of a rule. Two frameworks have been in force for decades, a third became effective in 2026, and a fourth exists as a proposed rule. No single published document maps which of these applies to a microreactor, and when. This paper builds that map. It is a regulatory applicability analysis: it describes the pathways at 10 CFR Parts 50, 52 and 53 and the proposed microreactor framework, the guidance architecture above them, the methodology layer beneath them, and the pre-application instruments that precede all of them. It then presents a decision map identifying, for each pathway, what it presumes about design maturity at the point of filing and the question a developer is actually deciding.
The map and the distinctions it draws are the contribution, not a recommendation. No pathway is recommended and none is ranked, because ranking requires weights that belong to a developer's business case rather than to the regulator's framework. The principal limitation is that a pathway determination is made on a specific docket against a specific design, so nothing here can be carried to a particular case without that review. A second limitation is authorship: RankShield Energy is a pre-applicant with an interest in the answer, and this paper describes frameworks rather than announcing a pathway it has selected.

This paper is technical analysis prepared for a professional audience. It is not legal, regulatory, engineering, or investment advice. It does not interpret regulatory requirements on behalf of any third party. Where this paper describes a proposed rule, the rule is not final and may change. Readers responsible for regulatory decisions should rely on the primary sources cited rather than on this summary of them.

## Scope and limitations
This paper addresses which published U.S. Nuclear Regulatory Commission licensing frameworks are available to a microreactor, what guidance sits above and beneath those frameworks, which pre-application instruments precede an application, and where a developer's actual choices lie. It draws on twenty primary sources spanning the regulator, the Government Accountability Office, the Department of Energy and a national laboratory, and the International Atomic Energy Agency. Where a document is characterised, it is cited and its status is stated: rule in force, proposed rule, draft guidance, interim staff guidance, staff paper, or research.
Several things are deliberately out of scope. The paper does not tell any party what a rule requires of it; it describes the regulator's published frameworks and leaves application to the reader and the reader's advisers. It contains no design detail for any RankShield Energy system: no geometry, no fuel description, no enrichment, no performance or lifetime figures. It contains no cost, fee, or economic analysis. It does not name, rank, or characterise other developers. It does not describe unattended or fully autonomous operation of a reactor; where operating-model provisions are mentioned, the operating model under discussion keeps a human in the loop for reactivity and safety actions. Where a guidance document's primary text sits outside the twenty cited sources, this paper names the document and describes its role in the architecture without attributing specific content to it and without citing a URL for it.
Several developments would change the analysis materially and should trigger a revision: a final microreactor licensing rule, or withdrawal or material amendment of the proposal; final rather than draft application guidance for that framework; issuance or revision of the guidance and interim staff guidance named in sections 3 and 4; a Commission decision adopting or rejecting positions analysed in the staff papers cited here; or published agency direction on how the frameworks are expected to be applied to this reactor class. The decision map in section 7 is our reading of the cited record and is offered for disagreement.

A developer that has settled its reactor physics has not settled its regulatory question, because the U.S. Nuclear Regulatory Commission does not present a microreactor with one licensing framework. It presents several, of different ages and different legal statuses, with a layer of guidance above them that governs how an application is assembled and a layer of methodology beneath them that governs how the safety case is built. There is no single published map of which framework applies to a microreactor and when. This paper draws one.
The method is deliberately plain. Section 1 sets out why applicability is a live question rather than a formality, and what a late answer costs. Section 2 describes the four licensing pathways and states the status of each. Section 3 describes the guidance architecture that sits above the rules and explains why guidance is not requirement. Section 4 describes the methodology layer beneath them and what a developer commits to when it adopts one. Section 5 separates the pre-application instruments, which are routinely conflated. Section 6 examines the construction permit provision that most affects sequencing. Section 7 presents the decision map. Section 8 applies the analysis to RankShield Energy, including the parts we cannot answer.
Two framing points govern everything that follows. What is in force is identified as in force: the construction permit provision at 10 CFR 50.35 [[7]](#src-7), the license conditions at 10 CFR 50.54 [[8]](#src-8), and the risk-informed, technology-inclusive framework at 10 CFR Part 53, which was published as a final rule and is effective [[1]](#src-1). What is proposed is identified as proposed at every mention, including proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it) [[2]](#src-2), whose companion application guidance is NUREG-2271 (draft guidance issued by the NRC staff for comment; staff guidance, not final) [[3]](#src-3). RankShield Energy is a pre-applicant engaged in early regulatory interaction and holds no NRC license, permit, or design approval [[5]](#src-5). Nothing in the design has been demonstrated to or accepted by the NRC, and this paper describes frameworks rather than announcing a pathway RankShield Energy has selected.
Key takeaways

- A microreactor developer today has three licensing pathways it can file under and a fourth it can read and comment on, and the frameworks differ less in stringency than in when they demand design maturity and what they let a developer reuse.
- Guidance, regulatory guides, and interim staff guidance are not requirements; departing from them is permitted and shifts the burden of demonstration onto the applicant rather than placing it out of compliance.
- The methodology layer, not the rule text, is where a risk-informed framework consumes a developer's early engineering budget, because the rules rely on an analysis the applicant supplies.
- A white paper seeks staff feedback and no approval; a topical report seeks staff review and approval of a discrete technical issue and produces something a later application can reference, and the two are routinely conflated.
- Proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it) does not settle which framework any specific applicant would be held to, and that determination is made on a docket against a specific design.

## 1. Why applicability is a real question
A developer approaching the U.S. Nuclear Regulatory Commission with a microreactor design does not meet a licensing framework. It meets several, stacked in layers, each carrying a different legal status. Two frameworks have been in force for decades. A third, 10 CFR Part 53, was published as a final rule in the Federal Register on March 30, 2026, at 91 FR 15696, and became effective on April 29, 2026 [[1]](#src-1). A fourth exists as proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it) [[2]](#src-2). Above all of them sits a body of guidance, regulatory guides, and interim staff guidance that shapes how an application is assembled and reviewed without carrying the force of a rule [[3]](#src-3) [[9]](#src-9).
The reactor class itself is described in the public record well before any framework is chosen. The Government Accountability Office published a science and technology spotlight on nuclear microreactors that describes the class for a general technical audience [[17]](#src-17), and the Department of Energy, through Idaho National Laboratory, maintains a microreactor program plan describing federal research and demonstration activity supporting it [[18]](#src-18). Our explainer on [what a nuclear microreactor is](https://rankshieldenergy.com/resources/what-is-a-nuclear-microreactor) covers the class-level description. None of those documents is a licensing document, so none establishes which body of regulation a given machine will be licensed under.
Choosing late is expensive in a specific way. The content of an application is set by the framework it is filed under, and that content is in turn set by decisions frozen years earlier: what was analysed, what was instrumented, how the safety case was constructed, and which methodology produced the classification of structures, systems, and components. A developer that defers the applicability question until the application is being drafted discovers that analysis it has already paid for was scoped to a different framework's expectations. The Government Accountability Office has reported that the NRC needed additional actions to prepare to license advanced reactors [[15]](#src-15) and maintains priority open recommendations for the agency [[16]](#src-16), so schedule risk sits on both sides of the table.
Two boundaries govern this paper. It describes the frameworks the regulator has published and the choices those frameworks leave open. It does not tell any party what a rule requires of that party, and a reader with a regulatory decision to make should work from the primary sources cited rather than from this summary of them. The second boundary is that this is a licensing map, not a complete map of federal obligation. Fuel availability is administered through a separate Department of Energy program [[19]](#src-19), international safeguards are an institutional arrangement in which an outside body verifies declarations rather than a licensing pathway [[20]](#src-20), and the statutory backdrop, including the ADVANCE Act, sits above the agency's rulemaking rather than inside it [[10]](#src-10).

## 2. The four licensing pathways and the status of each
The 10 CFR Part 50 pathway is the oldest and proceeds in two steps. A construction permit is issued following review of a preliminary safety analysis, construction proceeds, and an operating license is issued following review of a final safety analysis. The construction permit stage carries a provision at 10 CFR 50.35 addressing issuance of a construction permit where the applicant has not supplied all of the technical information otherwise required, subject to the conditions the rule states [[7]](#src-7). Conditions attaching to the license itself, including licensed-operator conditions, sit at 10 CFR 50.54 [[8]](#src-8); section 6 returns to the construction permit provision.
The 10 CFR Part 52 pathway rearranges the same review into instruments obtainable separately and then combined: an early site permit addressed to site suitability, a standard design approval or design certification addressed to a design, and a combined license that authorises construction and conditions operation in one instrument. The Federal Register notice for the Part 53 final rule describes that rule as an additional framework rather than a replacement for Parts 50 and 52 [[1]](#src-1). The property that matters to a developer intending repeat deployment is that design review is separable from site review, which is why standardisation arguments tend to be made in its vocabulary. Staff analysis of Nth-of-a-kind microreactor licensing and deployment considerations, which is staff analysis presented to the Commission rather than a Commission position, examines repeat deployment in that light [[12]](#src-12).
10 CFR Part 53 is final. The rule was published in the Federal Register on March 30, 2026, at 91 FR 15696, and became effective on April 29, 2026, under the title Risk-Informed, Technology-Inclusive Regulatory Framework for Advanced Reactors [[1]](#src-1). Technology-inclusive means the requirements are written so as not to presuppose a particular reactor technology, which allows machines of different families to be reviewed against the same rule text. Risk-informed means the structure of the rule leans on an applicant's own risk analysis to establish what is safety significant, which moves work into the methodology layer of section 4. Being final and effective, this framework is available now, which distinguishes it from the fourth pathway.
The fourth pathway is proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it), published under the title Licensing Requirements for Microreactors and Other Reactors With Comparable Risk Profiles, at 91 FR 23628 [[2]](#src-2). Because it is a proposal, there is nothing in it to apply for, its text may change before any final rule issues, and the agency's public summary of microreactor regulatory activities is the practical place to watch for movement [[9]](#src-9). Our explainer on [the proposed microreactor rule](https://rankshieldenergy.com/resources/nrc-part-57-autonomous-operation-explained) treats its operating-model provisions in detail.
Stated plainly, a developer today has three pathways it can file under and a fourth it can read, comment on, and design toward at its own risk.

## 3. The guidance architecture above the rules
Below the rule text and above the application sits the layer that does most of the day-to-day work: guidance. Guidance describes methods the NRC staff finds acceptable. It is not a requirement, and the distinction is not academic. An applicant that follows guidance obtains a review path the staff already understands. An applicant that departs from guidance is not out of compliance, because there was nothing there to comply with, but it assumes the burden of demonstrating that its alternative satisfies the underlying rule. The agency publishes guidance across topic areas, including digital instrumentation and controls for advanced reactors, which is guidance rather than rule text [[13]](#src-13).
Two guidance frameworks recur in advanced reactor licensing discussion: the advanced reactor content of application project, known as ARCAP, and the technology-inclusive content of application methodology, known as TICAP. Both are guidance rather than requirements, and both address what an application contains and how it is organised rather than what a reactor is required to achieve. This paper names them descriptively and does not attribute specific content to them, because their primary texts sit outside the twenty sources cited here; the agency's microreactor regulatory activities summary is the entry point the NRC itself maintains for that material [[9]](#src-9).
A further instrument in this layer is DANU-ISG-2022-01 (interim staff guidance, which is guidance and not a requirement), issued to describe a review roadmap for risk-informed, technology-inclusive advanced reactor applications in advance of, or in place of, a fully developed guidance document. Interim staff guidance is staff-level material: it describes how the staff currently intends to approach a class of application, and it establishes no obligation. For a developer the practical consequence is that a roadmap of this kind is the nearest available index of where review expectations are written down, while remaining guidance rather than rule text [[9]](#src-9).
The guidance associated with the fourth pathway is NUREG-2271 (draft guidance issued by the NRC staff for comment; staff guidance, not final), issued in April 2026 as guidelines for preparing and reviewing applications under the proposed framework [[3]](#src-3). Two consequences follow. Its content is provisional in the same sense that the rule it accompanies is provisional, since guidance written against proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it) cannot be more settled than the proposal it accompanies. And the pairing itself is informative: the agency issued draft application guidance alongside the proposal rather than long after it, which gives a developer an early view of the content that would be expected if the proposal became final. Reading draft guidance early is useful. Treating it as settled would be a mistake, and the same caution applies to every document named in this section.

## 4. The methodology layer beneath the rules
Beneath the content question sits a methodology question, and it is the one that determines how much of a developer's engineering budget is spent before an application exists. A risk-informed framework requires an applicant to establish what is safety significant using an analysis of its own, and the rule does not perform that analysis [[1]](#src-1). The methodology layer is where that analysis is specified: how event sequences are selected, how they are quantified, how uncertainty is treated, and how the results are used to classify structures, systems, and components and to set the treatment each class receives. Three guidance documents recur in this layer. Their primary texts sit outside the twenty sources cited here, so this paper names them and describes their role in the architecture without attributing specific content to them.
The Licensing Modernization Project approach is the methodology most often named in this context, and the NRC endorsed a version of it in Regulatory Guide 1.233. That endorsement is guidance: it identifies an approach the staff finds acceptable, and it does not prohibit an alternative. Naming it precisely matters, because what a developer takes on when it adopts an approach of this kind is not a single document but a chain, running from a method for developing event sequences, through the targets against which those sequences are judged, to a classification scheme that falls out of the result. Each link in that chain is an engineering commitment with a cost and a schedule attached [[9]](#src-9).
A second guidance document, Regulatory Guide 1.232, addresses design criteria for advanced reactors, adapting criteria written for light-water plants into forms intended for other technologies. It is guidance. Its practical role is to give a developer a starting vocabulary of design criteria that a reviewer will recognise, which is worth more than it sounds when a review depends on both parties meaning the same thing by the same term. A third, Regulatory Guide 1.247, concerns endorsement of a probabilistic risk assessment standard for advanced non-light-water reactors, and is likewise guidance. Its significance is quality of analysis rather than scope of analysis: it bears on what makes a risk assessment adequate to be relied upon, which becomes load-bearing in a framework that uses the risk assessment to decide what matters.
What a developer chooses when it adopts this layer is a set of commitments it will be held to in review and a set of interfaces into its own engineering. It is choosing the vocabulary in which its safety case will be written, the analysis products it will have to produce and maintain under configuration control, and the review practice it will encounter. Departure remains available at every step; departure costs argument, and argument costs schedule. Staff analysis of policy and licensing considerations related to micro-reactors, which is staff analysis prepared for Commission consideration rather than an adopted requirement, canvassed questions of this type for the reactor class specifically [[11]](#src-11).

## 5. Pre-application instruments and what each is for
Before an application exists there is a set of interactions the agency has structured and published. The NRC describes a pre-application process for prospective new reactor applicants as general guidance [[4]](#src-4), and maintains a separate description of pre-application activities for advanced reactors [[5]](#src-5). The stated purpose of these activities is alignment: reducing the probability that an application arrives containing a surprise for either party. Pre-application interaction confers no approval of anything, and our explainer on [the pre-application process](https://rankshieldenergy.com/resources/nrc-pre-application-process-explained) covers the mechanics at greater length.
The instruments are distinguishable and are frequently conflated. A letter of intent notifies the agency that a prospective applicant intends to engage and describes what it expects to submit. A project number is an administrative identifier the agency assigns so that correspondence with a pre-applicant can be tracked before any docket exists; it is a filing convenience rather than a status, and it is not a license, a permit, or an approval of any technical position. The agency's pre-application process page is where the mechanics of these steps are described [[4]](#src-4).
A regulatory engagement plan is the instrument that turns intent into a schedule. The NRC publishes a description of the regulatory engagement plan and its role in advanced reactor pre-application interaction [[6]](#src-6). In practice it is where a prospective applicant states the pathway it intends to use, the submittals it intends to make, and the sequence and timing of those submittals, so that agency staff and review resources can be planned against it. Its content is a statement of intent rather than a commitment enforceable as a license condition, and it is revised when the intent changes.
The distinction between a white paper and a topical report is the one most worth getting right, because the two documents look alike and do different work. A white paper is submitted to obtain staff feedback on an approach. It does not request approval, the staff response is feedback rather than a finding, and nothing in the exchange binds either party in a later review. A topical report is submitted to obtain staff review and approval of a discrete technical issue, and a favourable outcome is a safety evaluation that a subsequent application can reference. The consequence is asymmetric: a white paper is fast, inexpensive in review effort, and non-binding; a topical report is slower and heavier and produces something a later application can stand on. The agency describes both among the pre-application mechanics it publishes [[4]](#src-4) [[5]](#src-5). A readiness assessment is a third instrument, in which staff examine whether a planned submittal is complete enough to be accepted for review; it is a schedule instrument rather than a technical finding.

## 6. What a construction permit does and does not require
The construction permit provision at 10 CFR 50.35 is the sequencing instrument carried by the two-step pathway, and it is the provision most often misread [[7]](#src-7). The rule provides that the Commission may issue a construction permit where the applicant has not supplied all of the technical information otherwise required, subject to the conditions the rule states, and it further provides that a construction permit is not an approval of any design feature unless approval of that feature was specifically requested and granted [[7]](#src-7). Both halves of the provision matter, and they matter in opposite directions.
The permissive half addresses a real problem in early-unit deployment: a design is rarely complete at the moment construction has to begin if a schedule is to close at all. The provision allows a review to proceed on a preliminary safety analysis and remaining technical questions to be resolved before the operating stage, rather than requiring a complete design as a precondition of any authorisation to build [[7]](#src-7). For a developer whose schedule risk is concentrated in construction rather than in operation, that is the property of the two-step pathway that no other pathway reproduces in the same form.
The restrictive half is what a developer with a standardisation strategy should read closely. Because a construction permit does not approve a design feature unless approval of that feature was specifically requested, a permit obtained for one unit does not by itself carry design approvals forward to the next unit [[7]](#src-7). Carrying approvals forward is what the Part 52 instruments are structured to do [[1]](#src-1). Staff analysis of Nth-of-a-kind microreactor licensing and deployment considerations, which is staff analysis presented to the Commission rather than a Commission position, examines how repeat deployment accumulates justification across units rather than receiving it at the outset [[12]](#src-12).
The sequencing consequence is that a pathway choice determines when design maturity has to exist, not whether it has to exist. A pathway that permits an early authorisation moves the maturity requirement later and buys schedule with it; a pathway built around design approval moves the maturity requirement earlier and buys reusability with it. Neither is inherently superior, and the trade depends on how many units a developer intends to build and how much confidence it has in a frozen design. Downstream of any of these choices, conditions attach to the license itself, including the licensed-operator conditions at 10 CFR 50.54 [[8]](#src-8), and an operating plant enters the Reactor Oversight Process, which is the agency's framework of inspection, performance indicators, significance determination, and assessment for operating reactors [[14]](#src-14). Our comparison of [oversight models for a deployed fleet](https://rankshieldenergy.com/resources/oversight-models-fleet-scale-microreactor-deployment) takes that downstream question up separately.

## 7. A decision map
The table below compresses section 2 into a single view and adds two columns the rule text does not supply: what each pathway presumes about design maturity at the point of filing, and the question a microreactor developer is actually deciding when it considers that pathway. Three cautions before reading it. The cells are qualitative, because the cited record supports nothing quantitative about pathway selection. The two analytical columns are our reading and not the regulator's. And the table maps choices rather than making one: nothing in it establishes which pathway suits any particular design, and that determination is made on a docket against a specific application.

Table 1. The four licensing pathways available to or proposed for a microreactor, with the status of each and two analytical columns. The status column reports the public record cited in this paper. The maturity and open-question columns are RankShield Energy analysis. This table is not a regulatory position, it has not been reviewed or accepted by the NRC, and nothing in it is required, endorsed, or approved by any agency.

Pathway
Status
What it is for
What it presumes about design maturity
Principal open question for a microreactor developer

10 CFR Part 50, two-step
In force
A construction permit on a preliminary safety analysis, then an operating license on a final safety analysis
Least at the permit stage; the rule addresses issuance where technical information is incomplete
Whether schedule bought at the permit stage is repaid at the operating stage, and what carries to the next unit

10 CFR Part 52 instruments
In force
Early site permit, standard design approval, design certification, and combined license, obtainable separately and combinable
Most, where a design approval or certification is sought; site and design questions are separable
Whether the unit count justifies front-loading a design review to obtain a reusable approval

10 CFR Part 53
Final rule, published March 30, 2026 at 91 FR 15696, effective April 29, 2026
A risk-informed, technology-inclusive framework for advanced reactors, alongside Parts 50 and 52
Analysis maturity rather than drawing maturity; the framework relies on the applicant's own risk analysis
Whether the methodology chain in section 4 is affordable at microreactor scale and how early it has to be committed

Proposed microreactor framework
Proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it)
A licensing framework proposed for microreactors and other reactors with comparable risk profiles
Not determinable from a proposal; the companion application guidance is a draft issued for comment and not final
Whether to design toward a proposal that may change, and what to do if a schedule arrives before a final rule does

Two patterns run across the rows. Design maturity and reusability move together: every pathway that lets a developer file earlier gives it less that can be carried to the next unit, and every pathway that produces a reusable approval demands a more complete design before it will produce one. That trade appears in every row and is resolved by none of them. The second pattern is that analytical burden migrates rather than disappearing. A risk-informed framework moves work out of prescriptive compliance and into the applicant's own analysis, which is why the methodology layer described in section 4, and not the rule text, is where a developer's early spending concentrates.
What the table does not do is rank the pathways, and the omission is deliberate. Ranking requires a weighting across schedule risk, capital exposure, intended unit count, and confidence in a frozen design, and those weights belong to a developer's own business case rather than to the regulator's framework. A developer building a single demonstration unit and a developer intending a repeat-build fleet will read the same row differently, and both readings can be correct. A reader who wants the vendor-facing version of the same discipline can consult our note on [evaluating a microreactor vendor](https://rankshieldenergy.com/resources/how-to-evaluate-a-microreactor-vendor). What the record does settle is that the choice has to be made explicitly, because it will otherwise be made implicitly by whatever the engineering organisation happens to have produced by the time an application is drafted.

## 8. How RankShield Energy is approaching this
The standard this paper follows requires it to apply its own analysis to RankShield Energy and to state where we do not have a strong answer. The status, stated exactly. RankShield Energy is in pre-application engagement with the NRC and filed a letter of intent in August 2026. A project number has been requested and has not yet been assigned. RankShield Energy holds no NRC license, permit, or design approval, and nothing in the design has been demonstrated to or accepted by the NRC. Pre-application interaction confers no approval of anything [[5]](#src-5) [[4]](#src-4).
This paper does not announce a selected pathway, and that omission is the honest choice rather than a coy one. Three pathways are available to file under and a fourth is proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it) [[2]](#src-2). Announcing a selection before the analysis supporting it is complete would convert a working position into a public commitment, and a public commitment that later moves is exactly the kind of inconsistency that costs a pre-applicant credibility on a docket. What this paper does instead is publish the map, so that an eventual choice can be read against the reasoning rather than asserted without it.
The uncomfortable part is that the pathway question and the design question are coupled, and we do not yet hold all of the inputs. Our own emphasis is an assurance and verification layer, which is a component inside whatever oversight arrangement a licensed plant eventually has rather than a licensing pathway in its own right. If the eventual framework treats such a layer as an addition to be reviewed rather than a substitution for something already required, its licensing value is smaller than a developer would like it to be, and we hold no evidence either way. The draft application guidance that might bear on it is NUREG-2271 (draft guidance issued by the NRC staff for comment; staff guidance, not final), which is not a document to plan against as though it were settled [[3]](#src-3).
Two further dependencies sit outside anything a pathway choice settles. Fuel availability is administered through a separate Department of Energy program [[19]](#src-19), and safeguards are an institutional arrangement in which an outside body applies technical measures to verify declarations [[20]](#src-20). Neither is resolved by choosing a framework, and either can constrain a schedule that a framework choice appears to have freed. Agency readiness is a further variable a developer does not control and that has been examined externally [[15]](#src-15) [[16]](#src-16), and the agency's own summary of microreactor regulatory activity is where movement becomes visible [[9]](#src-9). What remains genuinely unsettled is recorded below and in our [open questions paper](https://rankshieldenergy.com/resources/open-questions-autonomous-microreactor-oversight). We would rather publish an incomplete map with the gaps marked than a complete-looking one with the gaps painted over.

## Frequently asked questions

### How many licensing frameworks can a microreactor actually use today?
Three are available to file under: the two-step construction permit and operating license pathway at 10 CFR Part 50, the instruments at 10 CFR Part 52, and the risk-informed, technology-inclusive framework at 10 CFR Part 53, which was published as a final rule on March 30, 2026 and became effective on April 29, 2026. A fourth framework exists as proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it), so it can be read, commented on, and designed toward, but not filed under. Which of the three available frameworks suits a given design is determined on a docket rather than in a paper of this kind.

### Is guidance the same thing as a requirement?
No, and the difference has practical consequences. Guidance, regulatory guides, and interim staff guidance describe methods the NRC staff finds acceptable. Following them obtains a review path the staff already understands. Departing from them is permitted, and it shifts the burden onto the applicant to demonstrate that the alternative satisfies the underlying rule rather than placing the applicant out of compliance. Requirements live in the rule text and in conditions attached to a license.

### What is the difference between a white paper and a topical report?
A white paper is submitted to obtain staff feedback on an approach. It seeks no approval, the response is feedback rather than a finding, and it binds neither party in a later review. A topical report is submitted to obtain staff review and approval of a discrete technical issue, and a favourable outcome is a safety evaluation that a later application can reference. The trade is speed and cost against durability of the result.

### Does the proposed microreactor rule determine which framework applies?
No. The instrument in question is proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it). A proposal contemplates a framework; it does not establish which framework any specific applicant would be held to, and the companion application guidance, NUREG-2271, is draft guidance issued by the NRC staff for comment and is not final. The determination for a specific design is made on a docket.

### What would change the analysis in this paper?
A final microreactor licensing rule, or withdrawal or material amendment of the proposal. Final rather than draft application guidance for that framework. Issuance or revision of the regulatory guides and interim staff guidance named in sections 3 and 4. A Commission decision adopting or rejecting positions analysed in the staff papers cited here. Or published agency direction on how the existing frameworks are expected to be applied to this reactor class. Any of those would move cells in the decision map, and the map is versioned so that movement can be recorded.

## Sources

- [U.S. Nuclear Regulatory Commission. Risk-Informed, Technology-Inclusive Regulatory Framework for Advanced Reactors (10 CFR Part 53, final rule). Federal Register, March 30, 2026 (91 FR 15696); effective April 29, 2026](https://www.federalregister.gov/documents/2026/03/30/2026-06048/risk-informed-technology-inclusive-regulatory-framework-for-advanced-reactors)
- [U.S. Nuclear Regulatory Commission. Licensing Requirements for Microreactors and Other Reactors With Comparable Risk Profiles (proposed 10 CFR Part 57). Federal Register, May 1, 2026 (91 FR 23628); proposed rule, comment period closed June 15, 2026, not final](https://www.federalregister.gov/documents/2026/05/01/2026-08550/licensing-requirements-for-microreactors-and-other-reactors-with-comparable-risk-profiles)
- [U.S. Nuclear Regulatory Commission. Guidelines for Preparing and Reviewing Applications Under 10 CFR Part 57 (NUREG-2271, Draft for Comment), April 2026; draft staff guidance issued for comment, not final, accompanying a proposed rule that is not final](https://www.nrc.gov/reading-rm/doc-collections/nuregs/staff/sr2271/index.html)
- [U.S. Nuclear Regulatory Commission. Pre-application Process (general guidance). Accessed August 2026](https://www.nrc.gov/reactors/new-reactors/advanced/new-app/general-guidance/pre-app-process)
- [U.S. Nuclear Regulatory Commission. Pre-Application Activities for Advanced Reactors. Accessed August 2026](https://www.nrc.gov/reactors/new-reactors/advanced/who-were-working-with/pre-application-activities)
- [U.S. Nuclear Regulatory Commission. Regulatory Engagement Plan. Accessed August 2026](https://www.nrc.gov/reactors/new-reactors/advanced/new-app/general-guidance/engagement)
- [U.S. Government Publishing Office. 10 CFR 50.35, Issuance of construction permits. 2024 CFR edition](https://www.govinfo.gov/content/pkg/CFR-2024-title10-vol1/xml/CFR-2024-title10-vol1-sec50-35.xml)
- [U.S. Government Publishing Office. 10 CFR 50.54(m), Conditions of licenses. 2024 CFR edition](https://www.govinfo.gov/content/pkg/CFR-2024-title10-vol1/xml/CFR-2024-title10-vol1-sec50-54.xml)
- [U.S. Nuclear Regulatory Commission. Microreactors: Regulatory Activities. Updated May 2026](https://www.nrc.gov/reactors/new-reactors/advanced/modernizing/microreactors/reg-activities.html)
- [U.S. Nuclear Regulatory Commission. About the ADVANCE Act. Accessed August 2026](https://www.nrc.gov/about-nrc/governing-laws/advance-act/about-advance-act)
- [U.S. Nuclear Regulatory Commission. SECY-20-0093: Policy and Licensing Considerations Related to Micro-Reactors (staff paper, not a Commission position). October 2020](https://www.nrc.gov/docs/ML2025/ML20254A363.html)
- [U.S. Nuclear Regulatory Commission. SECY-25-0052: Nth-of-a-Kind Microreactor Licensing and Deployment Considerations (staff paper, not a Commission position). June 2025](https://www.nrc.gov/docs/ML2430/ML24309A266.html)
- [U.S. Nuclear Regulatory Commission. Digital Instrumentation and Controls guidance for advanced reactors (guidance, not rule text). Accessed August 2026](https://www.nrc.gov/reactors/new-reactors/advanced/modernizing/guidance/digital-instrumentation-and-control.html)
- [U.S. Nuclear Regulatory Commission. Reactor Oversight Process Framework. Accessed August 2026](https://www.nrc.gov/reactors/operating/oversight/rop-description.html)
- [U.S. Government Accountability Office. Nuclear Power: NRC Needs to Take Additional Actions to Prepare to License Advanced Reactors (GAO-23-105997). July 2023](https://www.gao.gov/products/gao-23-105997)
- [U.S. Government Accountability Office. Priority Open Recommendations: Nuclear Regulatory Commission (GAO-26-109004). June 2026](https://www.gao.gov/products/gao-26-109004)
- [U.S. Government Accountability Office. Science and Tech Spotlight: Nuclear Microreactors (GAO-20-380SP). February 2020](https://www.gao.gov/products/gao-20-380sp)
- [Idaho National Laboratory for the U.S. Department of Energy. A Microreactor Program Plan for the Department of Energy (INL/EXT-20-58919 Rev. 4). May 2025](https://gain.inl.gov/content/uploads/4/2025/06/Microreactor-Program-Plan_INL-EXT-20-58919-Rev-4.pdf)
- [U.S. Department of Energy, Office of Nuclear Energy. HALEU Availability Program. Accessed August 2026](https://www.energy.gov/ne/haleu-availability-program)
- [International Atomic Energy Agency. Basics of IAEA Safeguards. Accessed August 2026](https://www.iaea.org/topics/basics-of-iaea-safeguards)

## Open questions
Questions this paper does not resolve, including those we cannot answer from the current record.

- **OQ-1. Whether the proposal becomes a rule.** Whether proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it) is finalised, materially amended, or withdrawn, and on what schedule [[2]](#src-2) [[9]](#src-9). Unresolved because a comment period closing is not a rulemaking outcome. Resolver: the NRC, through rulemaking.
- **OQ-2. Interaction between the frameworks.** How an applicant that has invested in the risk-informed, technology-inclusive framework at 10 CFR Part 53 [[1]](#src-1) would carry that work across if a microreactor-specific framework later becomes available. Unresolved because the cited record describes the frameworks separately rather than describing migration between them. Resolver: the NRC, through rulemaking and guidance.
- **OQ-3. Guidance maturity.** When application guidance for the proposed framework moves from draft to final, given that NUREG-2271 (draft guidance issued by the NRC staff for comment; staff guidance, not final) is what a developer would otherwise plan against [[3]](#src-3). Unresolved because guidance for a proposal cannot settle ahead of the proposal. Resolver: the NRC staff.
- **OQ-4. Methodology cost at small scale.** Whether the methodology chain described in section 4 scales down economically to a reactor of this class, or whether the analysis burden is close to invariant with size. Unresolved because staff analysis of policy and licensing considerations related to micro-reactors canvassed the questions without settling the cost of answering them [[11]](#src-11). Resolver: applicants and the NRC, demonstrated on dockets.
- **OQ-5. Reuse across units.** What actually carries from one unit to the next under each pathway, given that a construction permit is not an approval of a design feature unless approval was specifically requested [[7]](#src-7) and that staff analysis of Nth-of-a-kind licensing and deployment considerations, which is staff analysis rather than a Commission position, treats justification as accumulating across units [[12]](#src-12). Resolver: the NRC, on specific dockets.
- **OQ-6. Digital review expectations.** How the guidance layer for digital instrumentation and controls in advanced reactors, which is guidance rather than rule text [[13]](#src-13), interacts with a framework choice, and whether that interaction changes the pathway calculation for a design with a substantial digital content. Resolver: the NRC, through review practice.
- **OQ-7. Agency capacity as a pathway variable.** Whether review capacity differs materially between pathways in a way a developer should account for, given that the Government Accountability Office has reported preparation gaps for advanced reactor licensing [[15]](#src-15) and maintains priority open recommendations [[16]](#src-16). Unresolved because the cited record addresses readiness in aggregate rather than by pathway. Resolver: the NRC, with Government Accountability Office scrutiny.
- **OQ-8. We cannot answer this one.** Which framework RankShield Energy will file under, and whether the framework we would prefer will exist when we need it. We have filed a letter of intent and requested a project number that has not yet been assigned [[4]](#src-4) [[5]](#src-5), we hold no NRC license, permit, or design approval, and the determination depends on a rulemaking outcome we do not control and on a design maturity assessment we have not completed. Publishing a selection now would be a claim rather than an answer. Resolver: the NRC for the framework, RankShield Energy for the filing, and neither of us alone.

This paper reflects the state of the cited record as of its revision date. Regulatory proposals, national-laboratory results, and standards referenced here are subject to change. Section references to proposed rules should be re-checked against the current docket before use.

## Related

- [The NRC pre-application process explained →](https://rankshieldenergy.com/resources/nrc-pre-application-process-explained)
- [Oversight models for fleet-scale microreactor deployment →](https://rankshieldenergy.com/resources/oversight-models-fleet-scale-microreactor-deployment)
- [Open questions in autonomous microreactor oversight →](https://rankshieldenergy.com/resources/open-questions-autonomous-microreactor-oversight)
- [How to evaluate a microreactor vendor →](https://rankshieldenergy.com/resources/how-to-evaluate-a-microreactor-vendor)

Written by
Jamie Kloncz
Founder, RankShield Energy
Jamie leads the HELIX microreactor pre-application program and RankShield Energy's verification-first approach to advanced-reactor operations. [More about the author](https://rankshieldenergy.com/authors/jamie-kloncz)

*This paper reflects the state of NRC advanced reactor and microreactor rulemaking and the published guidance record as of August 2026. Proposed requirements, including proposed 10 CFR Part 57 (a proposed rule published in the Federal Register on May 1, 2026, with the comment period closed on June 15, 2026; not final, and no developer is licensed under it), may change before any final rule issues. Re-check the docket before relying on any section reference here.*
**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