DRC-2025-002236

299 South Main Street, Suite 1700 ▪ Salt Lake City, Utah 84111 [phone] ▪ Fax: [phone] ▪ www.energysolutions.com
July 8, 2025 CD-2025-138
Mr. Doug Hansen, Director Division of Waste Management and Radiation Control 195 North 1950 West Salt Lake City, UT 84114-4880
Subject: Radioactive Material Licenses No. UT 2300249: Response to Compliance Advisory No. 2501001 Compliance Evaluation Inspection
Dear Mr. Hansen: EnergySolutions respectfully responds to the July 1, 2025 Compliance Advisory issued by the Director of the Division of Waste Management and Radiation Control regarding access control to the Clive Facility’s licensed Restricted Area.1 We appreciate the
Director’s thorough evaluation and welcome the opportunity to demonstrate compliance with Condition 62 of Radioactive Material License UT 2300249 (License) and address the concerns raised about Restricted Area access control. Director’s Request:
The Director has recommended the following actions to prevent recurrence of compliance issues: 1) Ensure Restricted Area gates remain closed and locked; or 2) Ensure access to Restricted Area gates is actively monitored and controlled by a qualified gate guard when operations require gates to be open.
Response to Director’s Request: The Advisory references two events: a self-identified issue in May 2024 and an inspection conducted by Division inspectors on December 3-4, 2024.
• 2024 Self-Identified Non-Compliance: On May 9, 2024, at 19:38, during a routine off-hours security patrol (per CL-SE-PR-001), EnergySolutions identified that Restricted Area Gate #4 was improperly secured due to a padlock not being looped through both ends of a steel chain. This non-compliance was promptly
reported to Clive Management, and the gate was secured. Condition Report CR-
2024-0402 (attached) was issued to track resolution. To prevent recurrence, EnergySolutions enhanced its Learning Management System (LMS) training for all Clive employees, emphasizing procedure CL-RS-
PR-120. This procedure mandates single ownership for gate security, visual and

1 Hansen. D.J. “Compliance Advisory No. 2501001 - Compliance Evaluation Inspection: Radioactive Material Licenses No. UT 2300249 and No. UT 2300478” (DRC- 2025-0001391) Letter from the Division of Waste Management and Radiation Control to Vern Rogers of EnergySolutions, July 1, 2025.
Mr. Doug Hansen CD-2025-138 July 8, 2025 Page 2 of 2
299 South Main Street, Suite 1700 ▪ Salt Lake City, Utah 84111 [phone] ▪ Fax: [phone] ▪ www.energysolutions.com
manual gate checks, and dual verification when locking gates. All Clive Facility
staff, who may verify gate locks, completed the updated training. Since implementation, no further issues with Restricted Area gate locks have been reported, demonstrating the effectiveness of these corrective actions.
• December 2024 Inspection: The Advisory notes that during the December 3-4,
2024 inspection, Restricted Area Gate 22 (north side of Section 32, near the East Side Rotary Facility) was allegedly left open and unattended without a qualified gate guard. This observation is inaccurate. Per Clive Operating Procedure CL-RS-PR-120, Section 3.3.7, when Non-Contaminated Restricted Area (NCRA) gates
are unlocked, a qualified Radiological Safety Technician (RST) or NCRA Gate
Monitor must remain within visual sight and no more than 100 feet from the gate. During the December 2024 rail movement, Maes Krish, a qualified switchman and certified gate guard, monitored Gate 22 while maintaining visual line of sight, as required.
Although no non-compliance occurred, EnergySolutions has proactively improved its process by transferring oversight of qualified Gate Guards to the Security Manager. This ensures enhanced accountability and reinforces our commitment to regulatory excellence through ongoing review and improvement of Restricted
Area access control procedures. For further clarification, please contact me at [phone]. Sincerely,
Vern C. Rogers
Director, Regulatory Affairs
enclosures

Vern C.
Rogers
Digitally signed by Vern C. Rogers DN: cn=Vern C. Rogers, o=EnergySolutions, ou=Waste Management Division, email=[e-mail], c=US Date: 2025.07.08 10:17:33 -06'00'
Improperly closed restricted area gate
Source: Routine
Owning Organization: Waste Management Project/Site: Clive Functional Area: Operations
Description:
CL-SE-PR-001 REV 9 States the following reqiorements
4.7.6 All breaches of fence or boundary to the Restricted Area will be guarded
and reported immediately to the Shipping Receiving Manager, the RSO, and
the General Manager of Clive.
4.7.7 Any employee who opens/closes/verifies a gate shall do so by the following
method:
4.7.7.1 Inform Security when opening a gate, providing them the
name of who is opening it and the gate number.
4.7.7.2 Inform Security when closing a gate, providing them the
name of who is closing it and who verified it is properly
secured.
4.7.7.3 When closing/verifying a gate:
4.7.7.3.1 Ensure the chain/cable is looped twice around the
gate opening (where applicable).
4.7.7.3.2 Ensure the lock is hooked through both/opposing ends
of the chain/cable and as close to the gate as possible.
4.7.7.3.3 Challenge the lock to ensure it will not open.
CL-SE-PR-001
Security Operations Protocol Revision 9
Non-Proprietary Page 8 of 18
4.7.7.3.4 Tug on each end of the remaining chain
independently and separate them for a visual to assist
with verifying the gate is secure.
4.7.7.3.5 Install the carabineer (where applicable) in the same
links as the lock or as close to the gate as possible and
ensure it is above the lock and hooked through
opposing ends of the chain.
Gate #4 was improperly closed with only one end of the chain hooked in the lock. Both the gate closer and the verifier failed to notice that
the other end of the chain passed through the lock hoop but was not hooked by the lock. The unsecure gate was discovered at
approximately 1938 hrs during a routine patrol by a site security officer.
Originator: Justin R Lee Date Identified: 5/13/2024 Initiated On: 5/13/2024
Originators Questions Answer Notes
Were there any immediate actions taken?Yes Management was notified and the gate was properly secured.
Is there anyone else that might be able to provide
additional information?Yes Justin Lee
Externally Identified?No N/A
Initiate Completed By: Lee, Justin on 05/17/2024
10 CFR 71 Applicable:
Completion Due Date: 10/10/2024
Significance Level: SL 2
Screen Completed By: Kirk, Curtis on 05/17/2024
Ops Review Task Skipped
CR-2024-0402
1 of 14 (CR-2024-0402)
Screening Question Answer Notes Person Notified Date Notified
Is information in CR adequate?Yes N/A N/A
Does Issue meet criteria for CR?Yes N/A N/A
Are any Interim Actions needed?No N/A N/A
10 CFR 21 Potentially Reportable?No N/A N/A
10 CFR 71 or 10 CFR 72 Potentially
Reportable?No N/A N/A
PAAA Applicable? (DOE only)No N/A N/A
Require Causal Analysis Yes N/A N/A
Require an Action Plan Yes N/A N/A
Require Extent of Condition Review No N/A N/A
Require CARB Review No N/A N/A
Designation: SCAQ
Causal Analysis Type: Apparent Cause Analysis (ACA)
Responsible Manager: Justin R Lee
Causes
Cause Code: A4B3C10 – Problem performing repetitive tasks and/or subtasks
Cause Type: Apparent
Description:
Deviation from procedure
Reference Summary
ANATT-2024-0032 1 Attached File(s):
- Gate Five Why Analysis.pdf
Evaluation Results Summary:
Personell were using different methods of locking and verification around the site. Placement of carabiner before placing the lock and
allowing workers inside the Restricted area to visually verify the lock was correct.
Action Plan
CRA01-2024-0794 Due Date: 8/31/2024
Date Closed: 6/17/2024
Title: Preventative Action
Description:
Develop LMS training for Clive employees to ensure they understand procedure CL-SE-PR-001. This will be set up for all Clive employees
due to anyone could be tasked with verifying a lock.
Action Type: Preventative Action
Owning Organization: Waste
Management Project/Site: Clive Functional Area: Safety
Action Owner: Leon Clifford Baker
Detailed Evaluation Completed By: Lee, Justin on 06/13/2024
Evaluator: Justin R Lee
RM Review Completed By: Lee, Justin on 06/06/2024
CR-2024-0402
2 of 14 (CR-2024-0402)
Action Taken:
Set up Learning Management System (LMS) training for CL-SE-PR-001 for Clive employees who are responsible for verifying locks.
QA Review Completed By: Kirk, Curtis on 06/14/2024
CARB Approval Task Skipped
RM Completion Review Completed By: Lee, Justin on 06/20/2024
QA Completion Review Completed By: Watkins, Shauna on 06/24/2024
Final Closure Review Completed By: Lee, Justin on 07/08/2024
RM Concurrence Completed By: Lee, Justin on 06/13/2024
CR-2024-0402
3 of 14 (CR-2024-0402)
Analysis - Attachment (Misc)
Generated From: CR-2024-0402
Originator: Justin R Lee Initiated On: 6/13/2024
Type of Analysis: Apparent Cause
Initiate Completed By: Lee, Justin on 07/08/2024
Additional Details
Attachments
Gate Five Why Analysis.pdf
ANATT-2024-0032
4 of 14 (ANATT-2024-0032)
5
o
f

1
4

(
A
N
A
T
T
-
2
0
2
4
-
0
0
3
2
)
Preventative Action
Generated From: CR-2024-0402 Due Date: 8/31/2024
Date Closed: 6/17/2024
Action Type: Preventative Action
Owning Organization: Waste Management Project/Site: Clive Functional Area: Safety
Action Owner: Leon Clifford Baker
Description:
Develop LMS training for Clive employees to ensure they understand procedure CL-SE-PR-001. This will be set up for all Clive employees due
to anyone could be tasked with verifying a lock.
Originator: Justin R Lee Initiated On: 6/13/2024
Initiate Completed By: Lee, Justin on 06/13/2024
Verify Task Skipped
Implementation Completed By: Baker, Leon on 06/17/2024
Action Taken:
Set up Learning Management System (LMS) training for CL-SE-PR-001 for Clive employees who are responsible for verifying locks.
Additional Details
Attachments
CL-SE-PR-001 Training Record.xlsx
CL-SE-PR-001.docx
CRA01-2024-0794
6 of 14 (CRA01-2024-0794)
User
Alvarado,Lois(lkalvarado)
Anderson,Jonathan(jcanderson)
Andresen,Jerrod(jtandresen)
Bake,Everett(esbake)
Bell,Dean(debell)
Benitez,Salvador(sbenitez)
Beynon,Tyce(tdbeynon)
Black,Tyrell(tbblack)
Booth,David(dbooth)
Brand,Russell(rbrand)
Brown,Thomas(tabrown)
Brunson,Grant(gcbrunson)
Carrillo Melendez,J Jesus(jjcarrillo-melendez)
Cason,James(jmcason)
Chavez,Julio(jcchavez)
Christensen,William(wcchristensen)
Clegg,Hillary(hjclegg)
Cook,Christopher(clcook)
Correa,Gabriel(gxcorrea)
Correa,Ricardo(rcorrea)
Davis,Brett(bdavis)
Dick,Brennon(bdick)
Dutson,Garrett(gqdutson)
Ekins,Roger(rekins)
Ekins,Stewart(sgekins)
Evans,Albert(aevans)
Evans,Danielle(dxevans)
Feuerbach,Michael(mlfeuerbach)
Garcia,Kristina(kmgarcia)
Gleason,Scott(sagleason)
Godoy-Gonzalez,Francisco(fjgodoy-gonzalez)
Gonzalez,Jaime(jgonzalez)
Gowans,Shauna(smgowans)
Guerrero,Jesus(jjguerrero)
Gurr,Steve(sdgurr)
Herrera,Francis(fnherrera)
Hicks,Javonnie(jrhicks)
Hill,Jason(jhill)
Hodges,Jeremy(jhodges)
Howsden,Gerald(jdhowsden)
Jones,Adam(acjones)
Kelley,Darryl(dkelley)
Kenison,John(jdkenison)
Krish,James(jfkrish)
7 of 14 (CRA01-2024-0794)
Kubat,Rocky(rwkubat)
Lee,Justin(jlee)
Leyva,Christopher(cjleyva)
Mead,Roger(rmmead)
Medrano,Kelly(kmedrano)
Messer,Michael(mjmesser)
Metcalf,Kyle(krmetcalf)
Moreno Gonzalez,Fidencio(fmmgonzalez)
Mortazavi,Abolghasem(amortazavi)
Nokes,Ronald(rdnokes)
Ovard,Drew(djovard)
Perez,Sonia(sperez)
Richman,Jeffrey(jgrichmanjr)
Rigby,Larry(lcrigby)
Riley,Joseph(jriley)
Robinson,Sean(snrobinson)
Romero,Alex(aromero)
Romero,Alexis(anromero)
Rooney,Carson(crooney)
Schofield,Daniel(dmschofield)
Schofield,Jared(jlschofield)
Schofield,Jedediah(jgschofield)
Seely,Robert(raseely)
Smart,Matthew(mrsmart)
Sotelo,Marissa(mrsotelo)
Springer,Stoney(sdspringer)
Stanley,Samuel(sstanley)
Stark,Jared(jstark)
Stein,Brandon(bmstein)
Stewart,Todd(tlstewart)
Vanwagoner,Michael(mvanwagoner)
Villegas,Elizabeth(evillegas)
Villegas,Fabian(fvillegas)
Villegas,Omar(oxvillegas)
Williams,Carlin(crwilliams)
Wright,Arianna(aewright)
Yeaman,Brandon(bvyeaman)
Young,David(dlyoung)
8 of 14 (CRA01-2024-0794)
Training
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
9 of 14 (CRA01-2024-0794)
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
Clive Facility Security Operations Protocol(CL-SE-PR-001)7.0
10 of 14 (CRA01-2024-0794)
Assignment Status Assignment Due Date *
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
11 of 14 (CRA01-2024-0794)
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
Incomplete 06/30/2024 11:59:59 PM
12 of 14 (CRA01-2024-0794)
13

o
f

1
4

(
C
R
A
0
1
-
2
0
2
4
-
0
7
9
4
)
14

o
f

1
4

(
C
R
A
0
1
-
2
0
2
4
-
0
7
9
4
)