Briefing on 10 CFR 50.33 and 10 CFR 50.34 Versus Proposed 10 CFR 57.55 and 10 CFR 57.60

Small Pressurized Water Reactor. Image is AI generated.

Executive Summary

10 CFR 50.33/50.34 is the current two-step Part 50 application architecture: general information plus a preliminary safety analysis report (PSAR) at the construction-permit (CP) stage, then a final safety analysis report (FSAR) plus operating, emergency planning (EP), security, and other operating-license (OL) content later. Proposed rule 10 CFR 57.55/57.60 is very different: it is a proposed-only, eligibility-gated, joint CP+OL architecture for reactors that can meet Part 57’s entry criteria, and it front-loads much more of the licensing package into the initial application. For a small/mobile Pressurized Water Reactor (PWR), that creates a real strategic fork: Part 50 is more immaturity-tolerant, while proposed Part 57 is more standardization- and deployment-model-driven, with benefits only if the design can actually satisfy the proposed 1 rem TEDE / 10 metric ton fissile-material inventory cap eligibility screen and associated design-attribute expectations. Part 50 buys sequencing; proposed Part 57 buys potential speed and repeatability, but only after much earlier design, program, and business-case discipline.

10 CFR 50.33 compared with proposed 10 CFR 57.55

10 CFR 50.33 and proposed 10 CFR 57.55 are structurally similar, but the differences matter because they signal how the regulator expects the business case, emergency planning posture, and decommissioning funding basis to be packaged. The most important practical change is that proposed 57.55 sits inside a joint CP+OL model, and the NRC explicitly says it is equivalent to 50.33 except that no Emergency Planning Zones (EPZs) would be defined for Part 57 facilities.

Topic	10 CFR 50.33 current requirement	Proposed 10 CFR 57.55 counterpart	What I would say in strategy discussions
Status and trigger	Applies now to Part 50 applications.	Proposed-only; applies within proposed Part 57 Subpart C joint CP+OL applications for reactors that qualify under §§ 57.25 and 57.30.	I would treat Part 57 as an option study, not as the baseline compliance path, until I can show eligibility and the rule is final.
Core applicant information	Name, address, business, ownership/citizenship/foreign control, class of license, intended use, term, related licenses.	Same core fields, with nearly parallel organization information and license/use statements.	This part of the package is largely portable across both regimes.
Financial qualification	Applicant must show it possesses or has reasonable assurance of obtaining funds for construction and operating costs; newly formed entities may need additional financial relationship detail.	Applicant must show it appears to be financially qualified; must provide a financial capacity plan and current funding sources, and if funding is 50% or less at filing, should propose license conditions to verify funding before construction/operation starts.	Proposed 57.55 is more explicit about front-end financing controls. For a startup developer, that can be a benefit if you want a staged license-condition structure, but it also sharpens NRC focus on capital readiness at filing.
Emergency planning information	For power-reactor OL/COL applications, § 50.33(g) requires EPZ-related information and offsite emergency plans; for SMRs/non-LWRs/NPUFs using § 50.160, the application still needs the analysis used to determine EPZ extent, if any.	The NRC states proposed § 57.55 is equivalent to § 50.33 except that no EPZs would be defined under Part 57.	This is a genuine opportunity for low-consequence designs, but I would not misread it as “no emergency planning.” Part 57 still requires an emergency plan under proposed § 57.60.
Construction schedule	Part 50 applicants proposing to construct/alter must state earliest and latest completion dates.	Same basic requirement for construction/material alteration timing.	No major strategic difference here.
Decommissioning funding assurance	Under § 50.33(k), an OL/COL application must include a decommissioning funding assurance report under § 50.75.	Proposed § 57.55(i) requires decommissioning funding assurance information in the application.	For a joint Part 57 filing, I would assume decommissioning funding logic must be ready earlier than in a traditional Part 50 phased strategy.
Classified / restricted information handling	Classified and unclassified information must be separated.	Same concept appears in proposed § 57.55(j).	This is substantively the same discipline.

For a small/mobile PWR, the real strategic takeaway is that Part 50 preserves more staging, especially on emergency planning and decommissioning-funding timing, while proposed Part 57 expects a more integrated business-and-program package at the start. If I wanted to preserve both options, I would build a single applicant-information matrix that covers ownership/foreign control, capital structure, construction schedule, § 50.160 emergency-planning basis, and decommissioning funding logic from day one, even if I ultimately file under Part 50. NRC’s emergency-preparedness guidance page also confirms that § 50.160 is the current performance-based EP path for Small Modular Reactors (SMRs) and points applicants to RG 1.242 as staff-accepted guidance.

10 CFR 50.34 compared with proposed 10 CFR 57.60

This is the more consequential comparison. 10 CFR 50.34 vs proposed 10 CFR 57.60 is the difference between a phased technical case and a front-loaded technical case. Under current Part 50, the construction-permit stage is built around a preliminary safety analysis report (PSAR), while the operating-license stage is built around the FSAR and operating programs; under proposed Part 57, the NRC would require a single FSAR-based joint application that is already complete enough to support both the CP and the future OL once construction is substantially complete.

Topic	10 CFR 50.34 current requirement	Proposed 10 CFR 57.60 counterpart	My strategic read
Filing architecture	CP application includes a PSAR; OL application later includes an FSAR.	Each joint application must include an FSAR and be complete enough to support issuance of both CP and associated OL(s).	This is the single biggest difference. Part 50 lets me mature the safety case in phases; proposed Part 57 requires much more design and program maturity at the front end.
Accident/siting basis	Part 50 CP content for power reactors is tied to site assessment, Part 100 siting criteria, and offsite consequence evaluation under § 50.34(a)(1)(ii).	Proposed Part 57 uses the § 57.25(a) dose-based entry criterion and does not require Part 100 compliance or the specific individual dose criterion construction used in § 50.34(a)(1)(ii)(D).	For a bounded-consequence design, this is the core Part 57 opportunity. For a conventional small PWR, it is also the core eligibility hurdle.
Eligibility gate	No comparable Part 50 eligibility screen in § 50.34.	Reactor must satisfy proposed Part 57 entry criteria, including ≤1 rem TEDE at the unrestricted area for the bounding accident and ≤10 metric tons total thorium/uranium/plutonium inventory, plus design-attribute requirements in § 57.30.	Before I spend time on a Part 57 strategy for a small/mobile PWR, I would first run a brutal eligibility screen on source term, core inventory, passive heat removal, and safety-function architecture.
Principal design criteria	§ 50.34(a)(3) requires principal design criteria; Appendix A GDC are the minimum requirements for water-cooled plants similar to previously licensed plants and guidance for others.	Proposed § 57.60(a)(2) requires principal design criteria tied to the Part 57 design-attribute set; NRC says applicants would not be required to meet Appendix A GDC, though GDC could still serve as guidance.	That is a real opportunity for a mobile or nontraditional deployment model because it lets me write technology- and use-case-specific PDCs instead of forcing a large-LWR framing.
QA basis	§ 50.34(a)(7) and § 50.34(b)(6)(ii) tie power-reactor QA to Appendix B and require discussion of how the Appendix B criteria will be satisfied.	Proposed § 57.60(a)(3) requires a QA-program description for safety-related SSCs, but NRC states proposed Part 57 would not impose Appendix B; proposed § 57.60(a)(9) instead emphasizes justified use of consensus codes and standards.	I see this as the clearest regulatory-burden relief in proposed Part 57, but also as a major documentation burden: the applicant has to defend the graded QA and codes-and-standards basis more explicitly.
Testing and validation	§ 50.34(a)(8) asks the applicant to identify SSCs that need R&D and provide the program and schedule to resolve associated safety questions.	Proposed § 57.60(a)(1)(vii) asks for analysis, test programs, prototype testing, operating experience, or a combination sufficient to show compliance with § 57.30 design attributes.	In practice, I would still expect thermal-hydraulics validation, materials qualification, and code V&V to be major schedule drivers in either path; proposed Part 57 just frames them in a more performance-based way.
Emergency planning	Part 50 OL content requires emergency plans based on Appendix E or, for SMRs/non-LWRs/NPUFs, § 50.160.	Proposed § 57.60(a)(8)(iv) still requires an emergency plan, offsite coordination, and an opportunity for offsite response organizations to comment before submittal, even though proposed § 57.55 does not define EPZs.	I would describe Part 57 as EP without fixed EPZ architecture, not as reduced concern for offsite interfaces.
Security / cyber / access authorization	Part 50 handles physical security, safeguards contingency, cyber security, and SGI protection in separate OL application provisions in § 50.34(c)–(e).	Proposed § 57.60 rolls security into the operational-program package and expressly includes physical security, cyber security, information security, and access authorization.	Proposed Part 57 is actually more integrated here, not less regulated. It just packages the security basis differently.
Fitness for Duty (FFD) and staffing	§ 50.34 itself does not require an explicit FFD-program description; FFD applies separately through current Part 26 to Part 50 operating licensees and construction-permit holders.	Proposed § 57.60(a)(8)(xiv) requires an FFD program in the application, and § 57.60(a)(8)(xv) requires a staffing plan. Proposed Part 26 Subpart P would be the tailored FFD regime for Part 57, with an additional option for an applicant-defined FFD program only for designs that do not require operator action to remain within § 57.25(a) and for which credible operator/maintenance error could not cause exceedance.	This is a material opportunity for highly autonomous designs, but for a human-in-the-loop small PWR I would assume FFD/staffing become earlier licensing artifacts under Part 57 than under Part 50.
Standardization and siting flexibility	No analog inside § 50.34 for generic finality or designated large areas.	Proposed § 57.60(c) allows a request for generic finality; § 57.60(d) allows large designated areas with procedures for determining specific locations later.	For a mobile or repeat-deployment business model, this is the most commercially important Part 57 feature after eligibility.
Residual cross-cutting obligations	Part 50 is the baseline reactor framework.	Proposed § 57.80 still points NRC review to Parts 20, 50, 51, 54, 70, 71, 72, 73, 74, and 140 as applicable.	I would not sell Part 57 internally as a wholesale escape from existing NRC requirements; it is more accurately a streamlined filing architecture with selected substantive flexibilities.

For me, the alternative FFD issue is especially important because it shows the philosophy shift. Under the current Part 50 world, Part 26 applies directly to operating-licensees and certain construction-stage entities; the application sections themselves do not create a tailored FFD off-ramp. Under proposed Part 57, by contrast, the FFD concept is pulled into the application and would allow either Subpart P, the fuller Part 26 framework, or, in a narrow case, an FFD program of the applicant’s own specification—but only if the plant is effectively operator-independent for staying within the § 57.25(a) consequence criterion and operator/maintenance error cannot credibly push it over that threshold. I would treat that flexibility as real, but only for designs whose autonomy and human-factors case are already exceptionally mature.

Next Steps I Would Take

I would take five actions before choosing a licensing posture for a small/mobile PWR.

First, I would run a Part 57 eligibility screen immediately: can the design credibly meet the 1 rem TEDE entry criterion, the 10 metric ton inventory cap, and the § 57.30 design attributes for reactivity control, passive heat removal, fission product retention, shielding, effluent control, and security by design? If the answer is weak or conditional, I would stop treating Part 57 as a near-term primary path.

Second, I would build a dual-regime content matrix that maps current Part 50 artifacts to Part 57 analogs: applicant/financial package, decommissioning funding basis, emergency-planning basis, PDC basis, QA basis, test/validation plan, security package, FFD/staffing concept, and site-bounding assumptions. That lets me preserve optionality without writing two disconnected strategies.

Third, if I want to preserve a Part 50 path, I would still develop the § 50.160 emergency-planning basis now and use NRC’s current emergency-preparedness guidance, including the agency’s identification of RG 1.242 as the relevant guide for the performance-based EP framework for SMRs and related technologies. That work is useful under either strategy because Part 57 still requires an emergency plan and local/offsite coordination.

Fourth, if I want to preserve a Part 57 option, I would front-load the package that Part 50 normally lets me defer: FSAR-level safety case, graded QA/codes-and-standards justification, security and cyber basis, FFD/staffing concept, and any generic-finality or designated-area strategy. In other words, I would only pursue Part 57 if the business case genuinely values standardization, repeat deployment, or mobility enough to justify that earlier maturity burden.

Fifth, I would actively monitor the Part 57 rulemaking docket now, because this is still a proposed rule published on May 1, 2026, with comments due June 15, 2026. I would expect meaningful discussion during the comment period on the entry criteria, alternative FFD boundaries, and how much real relief Part 57 gives light-water designs.

Originally published by Sarah Gibboney on LinkedIn, May 5, 2026.