ML20206A890

Submits NRR Ofc Ltr 101,Rev 13 101,replacing Rev 12,dtd 980826,redelegating Signature Authority as Provided for in MD 9.27

ML20206A890
Person / Time
Issue date:	03/28/1999
From:	NRC (Affiliation Not Assigned)
To:	NRC (Affiliation Not Assigned)
References
NUDOCS 9904290067
Download: ML20206A890 (21)

Text

- '

. PDL 0

o OFFICE OF NUCLEAR REA CTOR REGULA TION Office Letter Transmittal  ;

i TO: All NRR Employees puBUC DOCUMDIT ROOM

SUBJECT:

NRR OFFICE LETTER NO.101, REVISION 13, DELEGATION OF i SIGNATURE AUgOQlTY-2  ! P2 fS PURPOSE: NRR Office Letter 101, Revision 13, replaces Revision 12, dated August 26,1998. It redelegates signature authority as provided for in ,

Management Directive 9.27.

Revision 13:

Realigns the signature authority in accordance with the NRR reorganization effective March 28,1999.

In cases of conflict with other previously-published NRR guidance, the l I delegations provided by this revised office letter take precedence.

i Substantive revisions and additions are indicated by bars in the right J margin.

DIVISION OF ORIGIN: Program Management, Policy Development and Analysis Staff CONTACT: Roberta ingram,415-1219 DATE APPROVED: March 28,1999 >

l AVAILABILITY: R. Ingram I

I l

nGj yQ/) ,

So ks e

842;9g67,g2e PDR

~

ag I

NRR OFFICE LETTER NO 101, REVISION 13 a

DELEGATION OF SIGNATURE AUTHORITY OBJECTIVES To authorize signature authority for various documents and correspondence issued by NRR to ensure effective and efficient implementation of the assigned responsibilities.

RESPONSIBILITIES AND AUTHORITIES Redelegation of responsibilities and authorities is delineated in the attachment to this revised office letter.

j As appropriate, NRR division directors may issue written guidance reflecting internal NRR signature authorities that are consistent with the delegation of authority reflected in the attachment and the responsibilities assigned.

CONCURRENCES All correspondence should reflect the concurrence or review of those NRC organizations exercising functional responsibihty for the subject matter involved. Individuals can limit their concurrence to technical, policy, or legal areas. Documents should be complete and accurate, yet the developmental process must be efficient and timely. To accomplish these objectives, follow the guidelines provided in Part II, Section (J), of Management Directive Handbook 3.57,

" Correspondence Management," and the following cdditional guidelines for NRR-generated correspondence.

1. When changes are made to a document which has previous concurrences, the document should be returned to the primary author (the individual who prepares the document, including consolidation of contributions from others into an integrated product) and the appropriate supervisor for their reconcurrence. If the primary author does not agree with changes made to the document, or some compromise, the primary author or supervisor may choose to rescind his or her concurrence. This policy denotes the minimally acceptable procedure for reconcurrences. Certain instances may exist where additional reconcurrences by individuals other than the primary author would be p*udent. Sound judgment should be exercised to ensure that all concurrence 3 remain unaffected.

2. Concurrence from other divisions within NRR should be at the lowest level that can speak authoritatively on a subject. This usually will be at the project manager, senior staff, or section chief level,

a. Branch chief concurrence would be appropriate on issues involving novel technical content, multi-site impact, or minor policy questions.

I a

b.' Division director concurrence normally would be appropriate if (1) significant programmatic impacts are likely, or (2) substantial policy issues are involved. In these cases, the appropriate associate director should be notified.

c. The Director, NRR, should be informed before any action is taken that is likely to result in changes to plant operating status.

3. The cognizant division director is responsible for all actions within his or her functional area, whether or not concurrence is obtained from any other NRC/NRR organization.

The decision-making authority rests with the cognizant division director. Therefore, inability to obtain concurrence from another organization does not relieve the division director of the responsibility to meet schedules.

4. To ensure appropriate independent review of certain types of documents, when a non-supervisory staff member is acting for the supervisor, the staff member should not concur and/or sign on their own work. The staff member should obtain concurrence or signature from another cognizant supervisor, or the next higher level of management.

This requirement applies only to specific items in the attachment indicated by a footnote.

5. The Director, NRR, holds the cognizant associate director and division direcior responsible for the technical, financial, and administrative accuracy of all documents j prepared for the Director, NRR, or higher agency management.

6. Concurrence on controlled correspondence is to be obtained in accordance with Management Directive 3.57. The Office of the General Counsel (OGC) should concur on correspondence that involves legal issues or regulatory interpretation, correspondence from intervenors or relating to an active proceeding, and 10 CFR 2.206 petitions. OGC concurrence should be obtained on those documents denoted by footnote 2 listed on page 15 of the attached Delegation of Signature Authority.

7. If the extemal agency communication (oral or written) contains new or unresolved policy or technical issues, or differs from a stated policy, the communication must be fully coordinated with both the Executive Director for Operations and the Chairman.

This coordination may be accomplished by telephone, personal meeting, electronic mail, or inclusion on the concurrence chain. Sample concurrence chains are attached (Attachment 2) for written communications that meet this criterion. These samples should also be used for controlled correspondence that is designated as " Chairman ,

Correspondence." If oral communication channels are used, the date and nature of the  !

coordination should be noted on the Official Record Copy, or in a memorandum to the I file. (See F. Miraglia's rnemorandum dated March 19,1998, and L. J. Callan's 1 memorandum dated January 30,1998.)

j l

l l

8. Concurrence in Enforcement Actions is to be consistent with item 23.a of the attached signature authority.

Attachments: 1. Delegation of Signature Authority NRR Office Letter No.101, Rev.13

2. Sample Concurrence Chains cc: W. Travers, EDO F.Miraglia, DEDR M.Knapp, DEDE P. Norry, DEDM H. Miller, RI L. Reyes, Ril J. Dyer, Rill E. Merschoff, RIV SECY OGC(5)

OP RES NMSS PUBLIC 4

I

i OFFICE OF NUCLEAR REACTOR REGULATION (NRR) - DELEGATION OF SIGNATURE AUTHORITY NRR OFFICE LETTER NO.101, REVISION 13 DELEGATED SIGNATURE AUTHORITY'

1. Federal Reaister Notice' and formal Project Manager or Branch Chief 3 memoranda requesting publication '

2. Environmental Assessment and Finding of No Project Manager or DLPM Section Significant impact, including letters pertaining to Chief NRR findings involving historic properties *2

3. Safety Evaluation Reports, Environmental Director, Division of Licensing Project Impact Statements and Supplements thereto Management, or Director, Division of related to issuance of initial and renewed Regulatory Improvement Programs license (LWAs, cps, OLs), PDAs and FDAs2

4. Approvals and denials of Amendments (including exigent amendments) to cps and OLs, Extensions of cps and OLs, and the associated Safety Evaluations:

a. Those resulting from changes in owners or Director, NRR operators (either direct or indirect) of licensed power production facilities

b. (1) Approvals of changes to license DLPM Section Chief', or Chief, Events conditions, the technical Assessment, Generic Communications specifications, changes in the facility and Non-Power Reactors Branch

• procedures, or authorizing the conduct of tests or experiments 8 (2) Denials of requests for changes to Project Director or Chief, Events license conditions, the technical Assessment, Generic Communications specifications, changes in the facility and Non-Power Reactors Branch procedures, or authorizing the conduct of tests or experiments

c. All others (e.g., license terminations, Project Director or Chief, Events possession only license amendments and Assessment, Generic Communications non-power reactor license renewals)' and Non Power Reactors Branch 2

5. Emergency Amendments DLPM Section Chief l

• Pursuant to 36 CFR Part 800, which became effective 10/1/86 Attachment 1

r DELEGATED SIGNATURE AUTHORITY'

6. Notices of Enforcement Discretion'"(NOED) Project Director

• I

7. All SERs, EISs and Supplements not included Project Manager in items 3 and 48

8. Internal correspondence between divisions Section Chief' l

9. NUREGs other than those covered by items 3 Division Director ,

and 4 above" {

i

10. Construction Pecmits, LWAs, Operating Director, NRR Licenses, PDAs, PDAs and Power Reactor License Renewals i

11. All authorizations permitting increases in power Director, NRR level:

12. Exemption Approvals8 and Denials Parts 20,50,51,52,54,55 and 70.24' Director, Division of Licensing Project Management, or Director, Division of Inspection Program Management

13. Certification of Pollution Control Facilities: Director, NRR

14. Approvals and Denials specified in: I

a. 10 CFR 50.55a (ISI/IST)' DLPM Section Chief' i

b. Appendix G'8 DLPM Section Chief'

c. Appendix H' DLPM Section Chief'

d. Appendix J' DLPM Section Chief'

e. Part 20 Director, Division of Licensing Project Management, or Director, Division of Regulatory improvement Programs

• NRC Inspection Manual, Part 9900

• • OGC concurrence could be appropriate l

DELEGATED SIGNATURE AUTHORITY'

15. a. Orders to power reactor licensees, Director, NRR including extension requests (e.g., those required in connection with various rule changes)2

b. Orders as in 15.a for non-power reactors Director, Division of Regulatory improvement Programs

16. Operator Licensing

a. Power Reactor Operator License Appeals Director, Division of Inspection Program Management

b. Non-power Reactor Operator Licenses (1) New, Renewal, Terminations'8 Chief, Events Assessment, Generic Communications and Non-Power Reactors Branch (2) Appeals Director, Division of Regulatory improvement Programs

17. Testimony and Filings

a. Staff Testimony'0 Staff member preparing the testimony with concurrence by supervising Branch Chief or Project Director

b. Legal Filings (other than staff testimony) Concurrence by Division Director (as requested by OGC)

18. Letters to Applicants / Licensees / Vendors /Public

a. Acceptance review, LWAs, rejection of Director, Division of Licensing Project

. application for QA certifications and other Management, or Director, Division of action reflecting Commission final approval Regulatory improvement Programs or disapproval position

b. All routine correspondence related to the - Project Manager normal processing of applications and related reviews, including transmittal of question lists, SEs, SERs, licenses, amendments, exemptions, orders and items related to meetings

4 DELEGATED SIGNATURE AUTHORITY'

c. Non-routine correspondence with Director, Division of Regulatory vendors / owners groups Improvement Programs, or Director, Division of Inspection Program Management

d. Routine correspondence to Project Manager, Chief, Quality vendors / owners groups' Assurance, Vendor inspection, Maintenance and Allegations Branch, or Chief, Generic Issues, Environmental, Finance and Rulemaking Branch

e. Plant-specific 50.54(f) letters8 Division Director, with justification approved by the Director, NRR

f. Letters involving unreviewed safety matters Director, Division of Licensing Project as specified in 50.59(a)(2): Management, or Director, Division of Regulatory Improvement Programs

g. Generic Letters and Bulletins Director, Division of Regulatory improvement Programs

h. Information Notices and other generic Chief, Events Assessment, Generic administrative correspondence'0 Communications and Non-Power Reactors Branch I. Backfit issue Correspondence (1) Regulatory Analysis or Evaluation Director or Deputy Director, NRR 1

(2) Letter to licensee containing Backfit Director, Division of Licensing Project Determination and enclosing the Management, or Director, Division of {

Regulatory Analysis Regulatory improvement Programs l J. Proprietary information - Letter to Project Manager or Section Chief' for Applicanta Topical Reports

k. Confirmatory Action Letters

}

(1) Issued by Regions' Concurrence by Director, NRR l t I

i l

i

DELEGATED SIGNATURE AUTHORITY' (2) Issued by NRR Director, Division of Licensing Project Management, or Director, Division of Regulatory improvement Programs, NRR (w/ concurrence by Regional Division Director, Reactor Projects, and Director, NRR)

19. Correspondence related to Topical Report Review Program

a. Letters related to acceptance of reports for review under Topical Report Program (1) Acceptance letter including points of Section Chief' or Project Manager contact, schedule and statement of broad proprietary information treatment, as necessary ,

(2)' Nonacceptance for Topical Report Section Chief or Project Manager Program

b. Question lists and routine correspondence Section Chief' relating to Topical Report reviews

c. Letters approving or disapproving Topical Branch Chief Reports for reference [

d. Topical Report fee memorandum to Section Chief' Resource Management Branch

e. Approval or disapproval of request for_ Section Chief' proprietary information treatment for Topical Report after Accepted Version (approved version) is filed, as necessary

20. Letters to Congressional Oversight Committees Director, NRR

21. Letters to Department of Energy concoming Director, Division of Regulatory reviews encompassed within a Memorandum of improvement Programs Understanding (MOU) (e.g., DOD reactors, Navy Projects)

6-DELEGATED SIGNATURE AUTHORITY'

22. Letters to Governors, State officials, local officials, and Federal agencies

a. Routine hansmittals forwarding copies of Project Manager SER/ER, notices and other routine documents q

)

b. Transmittal of information to the Branch Chief or Project Director Department of Energy (DOE) not related to ,

license reviews

c. Correspondence which does not establish Branch Chief or Project Director new policy

d. Correspondence which establishes new Director, NRR policy *

23. Enforcement Actions (EA)

a. (1) Concurrence in EAs pertaining to DLPM Section Chief" l reactor licensees or applicants (2) Objection to EAs pertaining to Associate Director, ADPT reactor licensees or applicants

b. EAs for violations caused by vendors (notices of violation, nonconformance and proposed civil penalties in accordance with the delegation reflected in memorandum dated July 17,1987, from J. Lieberman, Director, Office of Enforcement, to T.

Murley, Director, NRR)

(1) Actions involving Severity Level I & 11 Director, Division of Inspection violations and proposed civil Program Management

• penalties 1

Requires concurrence of EDO and the Chairman. See Concurrences, item 7, of this office I letter.

• • Requires coordination w/DLPM. See OL 908.

l

r DELEGATED SIGNATURE AUTHORITY' (2) Notices of Violations with Severity Chief, Quality Assurance, Vendor Level 111 violations inspection, Maintenance and Allegations Branch" (3) Notices of Violations with Severity Chief, Quality Assurance, Vendor LevelIV violations Inspection, Maintenance and Allegations Branch (4) Acceptance of vendor's response to Section Chief Notice of Nonconformance or Notice I of Violation

c. EAs for violations caused by non-power reactor licensees (notices of violation, deviations, and proposed civil penalties in accordance with the delegation reflected in memorandum dated February 3,1998, from J. Lieberman, Director, Office of Enforcement, to S. Collins, Director, NRR).

(1) Actions involving Severity Level I & ll Deputy Director, NRR, or above" violations and proposed civil i penalties (2) Notices of Violation with Severity Director, Division of Regulatory Levelill violations improvement Programs or above" (3) Notices of Violations with Severity Chief, Events Assessment, Generic LevelIV violations, Notices of Communications and Non-Power ,

Deviation, and associated Reactors Branch, or above '

documents

24. Transmittal of staff reports, supporting Firstlevelof supervision documents and review schedule information to j ACRS '

25. Board Notification transmittals

a. To a sitting Board Project Manager

b. To the Commission Director, Division of Licensing Project Management, or Director, Division of Regulatory improvement Programs

e DELEGATED SIGNATURE AUTHORITY'

26. Issuance of Inspection Reports and Operational Safeguards Response Evaluations (OSREs)

a. Reactor inspection Reports and OSREs Chief, inspection Program Branch, prepared by NRR'" Chief, Operator Licensing, Human Performance and Plant Support Branch, or Chief, Events Assessment, Generic Communications and Non-Power Reactors Branch *

b. Vendor inspection Reports Chief, Quality Assurance, Vendor inspection, Maintenance and Allegations Branch

c. Operator Licensing Exam Reports' Chief, Operator Licensing, Human Performance and Plant Support Branch, or Chief, Events Assessment, Generic Communications and Non-Power Reactors Branch

27. Interactions with Office of Nuclear Regulatory Research (RES)

a. User needs request memoranda Director, NRR

b. Endorsement of research program plans Associate Directors l

c. Comments / concurrence on research Division Director products, resolution of programmatic issues, etc.

Concurrence by the applicable Project Director, Director, Division of Licensing Project Management, or Director, Division of Regulatory improvement Programs

DELEGATED SIGNATURE AUTHORITY

28. Correspondence with FEMA regarding Emergency Preparedness

a. Policies and positions Director, Division of Inspection Program Management, or Chief, Operator Licensing, Human Pedormance and Plant Support Branch depending on significance of issues (w/ concurrence by Director, NRR, EDO and the Chairman, as appropriate *)

b. Routine matters Section Chief'

29. Issuance of Standard Review Plans Division Director

30. Issuance of Inspection Procedures Director, Division of Inspection Program Management ,

l

31. Task Intedace Agreements (TIAs) ( See OL i 1201.)'

a. Related to policy issues Appropriate Associate Director (w/ l concurrence by Director, NRR, EDO and the Chairman, as appropriate *)

b. All others Deputy Director, Division of Licensing Project Management

32. RegionalOversight

a. Delegation of Authority Director, NRR

b. Procedural and Programmatic Guidance (1) Operator Licensing Chief, Operator Licensing, Human Performance and Plant Support Branch, or Chief, Events Assessment, Generic Communications and Non-Power Reactors Branch (2) Licensing Technical Reviews Branch Chief or Project Director See item 7 of this office letter for guidance in this area.

l DELEGATED SIGNATURE AUTHORITY' j (3) Inspections Chief, inspection Program Branch (4) Evaluation of Licensee Performance Chief, inspection Program Branch (SMM, etc.) l

c. Policy Guidance and Programmatic Division Director (for assigned Direction functional area)

d. Issuance of Regional Performance Evaluation (1) Periodic Technical Program Reviews Division Director (for assigned functional area)

(2) Management Team Reviews Associate or Deputy Director, NRR (as l assigned)

(3) Observations from Team Inspections Division Directors (4) AnnualIntegrated Evaluations Director, NRR

e. Response to Requests from Regions for Support (1) NRR Staff Support Project Director / Branch Chief (2) Contractor Assistance Project Director / Branch Chief

33. Controlled Correspondence i

a. Green Ticket items As stated on the green ticket *

b. EDO WITS Items (1) Items for the EDO Director, NRR (2) items for the Commission Executive Director for Operations

c. Yellow Ticket items  !

(1) Items for the EDO Director, NRR l

When the EDO has designated the Director, NRR, to sign the response to a green ticket item, NRR can redelegate to the Division Director. However, this should be approved by i the Deputy Director, NRR, and the NRR Mailroom also should be notified.  !

l

DELEGATED SIGNATURE AUTHORITY' (2) Routine As assigned (may be redelegated by the Division Director *)

d. Due date extension requests Primary Author

34. Procurement

a. RFPAs and program transmittal letters Division Director

b. NRC Form 173, ' Standard Order for DOE Division Director Work (SOEW)"

c. NRC Form 367, " DOE Source Selection Division Director Justification"

35. Certification of billings from technical assistance Project Manager (per Management contracts and consultant services Directive (MD) 11.7) or Project Officer (per MD 11.1)

36. Letters to consultants & DOE and DOE Project Manager (per MD 11.7) laboratories transmitting documents

37. Domestic Travel:

a. Form 279, Official Travel Project Director or Branch Chief Authorization-Block 27 (Admin. Approval)

Use of non-contract carrier' Project Director or Branch Chief in Block 27 Use of free upgrades to premium-class air Project Director or Branch Chief in accommodations Block 27

b. Form 64, Voucher (Part 1) Block 33 Same signature which appeared in (Approving official)'" Block 27 on the Form 279 unless voucher involves Change of Station (COS). COS vouchers may be administratively approved by Division i Directors."

If the Division Director decides to change the signature level, the NRR Mailroom should be notified.

• • Travel authorizations for COS (NRC Form 279A) are administratively approved by the Office of Human Resources.

1

. l DELEGATED SIGNATURE AUTHORITY'

c. Form 1164, Local-Block 8 (Approving Project Director or Branch Chief Official)'" l

39. Foreign Travel (Form 445) Supervisorof traveler (Project j Director / Branch Chief or above) and Deputy Director, NRR

39. Certification of funds: Funds Certifying Official or Alternate 5

a. Travel (Block 26)

b. Technical Assistance '

40. Hours of Work and Premium Pay:

a. Establish work schedules IAW NRC MD Project Director or Branch Chief 10.42 (4136-036 a., f., h., and k.)'"

b. Authorize Overtime" Project Director or Branch Chief

c. Authorize work schedule adjustments for Project Director or Branch Chief religious obsewance'0

d. Deny work schedule adjustments for Director, NRR religious observance purposes

e. Authorize payment for unused religious Project Director or Brcnch Chief observance time (at the time of an employee's separation or transfer)'

f. Recommend to Director, Office of Human Division Director Resources, approval of premium pay on an annual basis in lieu of other premium pay

g. Assure office coverage during official immediate Supervisor hours of operation

h. Approve leave, excused absence up to 2 Section Chief, Branch Chief, or Project hours, absence in duty status and leave Director without pay (see NRC MD 10.62)

1. Approve excused absence up to 1 day, as Project Director or Branch Chief limited by NRC MD 10.62 J. Certify the accuracy of Time and Section Chief, Branch Chief, or Project 7

Attendance (T&A) cards Director

DELEGATED SIGNATURE AUTHORITY'

k. Maintain T&A cards and records (T&A Secretary or Support Staff clerk)'

l. Receive paychecks and Earnings and Secretary or Support Staff Leave Statements 7

41. Training / Personnel

a. Training request and authorization for immediate Supervisor internal NRC courses

b. NRC Form 368, Training Requests and Project Director or Branch Chief Authorizations

c. Non-SES personnel actions including Division Director salary exceptions, promotions up to and including GG-14, separations, details, postings, and other non-SES personnel actions of a general or routine nature

42. Candidate evaluation, certification and selection Selecting Official8 record (personnel selection Form NRC-178)

43. Memoranda or letters involving discipline, See NRC MD 10.99 adverse actions or separations

44. Indemnity Agreements and amendments Chief, Generic Issues, Environmental, thereto Finance and Rulemaking Branch l

45. Internal Controls All correspondence with NRC's intemal Control Chief, Resource Management Branch Committee regarding Office Internal Control l directives

a. Implementation of reviews, monitoring status of corrective actions resulting from reviews

b. Other routine correspondence

46. NRC Form 426," Publication Release for Author's Supervisor and Associate Unclassified NRC Staff Reports"(see Office Director l Letter 700)

F

~

DELEGATED SIGNATURE AUTHORITY'

47. FOIA (Freedom of Information Act) requests

a. Denials Division Director

b. Appeals Deputy Director, NRR i

4

)

1

I -

w Footnotes

1. Authority is also delegated to higher levels within the same organization. If the designated organizational unit does not exist in a division, the next higher level is delegated the authority.

Deputy Division Directors and Deputy Branch Chiefs are authorized and directed to act in the stead of appropriate Division Directors and Branch Chiefs.

2. OGC concurrence is required. For item 1, OGC concurrence may not apply to notices required by 10 CFR 50.91 (Sholly Notices); seek guidance from NRR Licensing Assistants. OGC {

concurrence is not required on notices requesting public comments on proposed generic letters I and bulletins.

S. Concurrence by the Director, NRR, is required before issuing a license amendment and final no significant hazards consideration determination if a requested hearing will not be completed before the license amendment is issued.' In such instances, notification to the Commission must be provided at least 5 days before the date that the staff intends to issue the final no significant hazards consideration determination and license amendment. See memorandum from Roy P.

Zimmerman to Steven A. Varga and Jack W. Roe dated January 31,1997, for further guidance on the notification form and process.

4. The concurrence of the Director, Office of Enforcement, and the Deputy Executive Director for l Regulatory Effectiveness, unless delegated to the Director, Office of Enforcement, is required on Notices of Violations with Severity Level ill violations or higher, proposed civil penalties and correspondence associated with such actions.

5. May be redelegated with written approval of the Director, NRR.

6. The names and signatures of individuals specifically delegated this authority shall be furnished to the Division of Accounting and Finance, Office of the Chief Financial Officer (OCFO), via the Time and Attendance Reporting Delegations Form approved by an Associate Director or Director, Program Management, Policy Development and Analysis Staff, or higher, as l

appropriate. Alternates must be of equal or higher rank as the overtime approving official.

SES personnel may not be compensated or granted compensatory time off for overtime worked, except that overtime hours worked, including holiday work, may be credited as an offset for time off for religious observance.

7. The names and signatures of individuals specifically delegated these authorities shall be fumished to the Division of Accounting and Finance, OCFO, via the Time and Attendance Reporting Delegations Form approved by an Associate Director or Director, Program Management, Policy Development and Analysis Staff, or higher, as appropriate. These authorities do not routinely transfer to an official serving in an " Acting" capacity unless specifically so delegated as an Alternate on the Time and Attendance Reporting Delegations Form.

8. Completed selection packages must be reviewed by the Division Director or his/her immediate staff prior to submittal to the Resource Management Branch, Program Management, Policy Development and Analysis Staff.

F r .

I 16-

9. May be redelegated to senior staff member.

10. To ensure appropriate independent review, when a non-supervisory staff member is acting for the supervisor, the staff member should not concur and/or sign on their own work. The staff member should obtain concurrence or signature from another cognizant supervisor, or the next higherlevelof management. {

j

11. If not otherwise delegated to the Director, Office of Enforcement, the concurrence of the Director, Office of Enforcement, and the Deputy Executive Director for Regulatory Effectiveness, is required on Notices of Violation with Severity Level ill violations or higher, proposed civil penalties, and correspondence associated with such actions.

I l

1 l

I

y I

f AGENCY COMMUNICATIONS ON POLICY MATTERS AND CHAIRMAN CORRESPONDENCE I. DOCUMENTS SIGNED AT THE PROJECT DIRECTOR OR BRANCH CHIEF LEVEL A. The Project Director (PD)/ Branch Chief (BC) is permitted to sign only after the document has been fully concurred in by the NRR Directors' office, the EDO, and the Chairman. If i substantial changes, as determined by the NRR mail room, are made by the EDO and/or the Chairman, the document must retum to the NRR Director's office again before final signature is permitted.

B. The proper concurrence chain is as follows:

Project Director / Branch Chief (concur only, do not sign), NRR Office Director, Executive Director for Operations, Chairman, NRR Office Director (only if substantial changes are made), Project Director / Branch Chief (sign)

OFFICE NRR NRR: NRR: NRR:oD OEDo oCM/SJ NRR.OD NRR:

PD/BC DD/AD PDSC NAME Ori96nator P0/BC Mgt Chain

• SCollins/ WTrevers SAJackson SCollins/ PDSC Name RZimmerman RZtmmerman** Name (concur) (concur) (concur) (concur) (concur) (concur) (sign)

DATE / /99 / 199 / 199 / 199 / /99 / /99 / /99 / /99

• The appropriate management chain varies across Divisions. Typically, this can include the Division Director and Associate Director.

" The second NRR Director's office concurrence is required only if substantial changes, as determined by the NRR mail room, are made by the EDO and/or the Chairman.

11. DOCUMENTS SIGNED BY THE DIRECTOR, NRR A. The document is signed only after it has been concurred in by the Executive Director for ,

Operations and the Chairman. >

B. The proper concurrence chain is as follows:

NRR Office Director (concur only, do not sign), Executive Director for Operations, Chairman, NRR Office Director (sign)

OFFICE NRR: NRR:DD/AD NRR:OD OEDO OCM/SJ NRR:OD NAME Originator Mgt. Chain

• SCollins WTravers SAJackson SCollins (concur) (concur) (concur) (concur) (concur) (sign)

DATE / /99 / /99 / /99 / 199 / /99 / /99 l

• The appropriate management chain varies across Divisions. Typically, this can include the j Section Chief, Branch Chief, Division Director, and Associate Director.

Attachment 2