ML20133P198

From kanterella
Jump to navigation Jump to search
NRR Ofc Ltr 1003,Rev 2, Mgt of Allegations
ML20133P198
Person / Time
Issue date: 07/31/1996
From: Jun Lee
NRC (Affiliation Not Assigned)
To:
Shared Package
ML20133N901 List:
References
FOIA-96-488 PROC-960731, NUDOCS 9701240114
Download: ML20133P198 (26)


Text

. . - _ - - . - . - __ -

,> a i

l OFFICE OF NUCLEAR REACTOR REGULA TION Office Letter Transmittal n j T0: All NRR Employees

SUBJECT:

NRR OFFICE LETTER NO. 1003, REVISION 2, " MANAGEMENT OF ALLEGA-t TIONS" i

PURPOSE: Office Letter 1003, Revision 2, supersedes NRR Office Let-b 1 ter 1003, Revision 1, dated December 31, 1990. It provides the policies and procedures for the management of allegations i

in NRR arid establishes the NRR Allegation Review Board (ARB) responsible for directing and overseeing the allegation management process in NRR. This revision to the office letter updates NRR procedures to comply with Management Direc-tive (MD) 8.8, " Management of Allegations." Substantive revisions and additions are indicated by bars in the right [;

i margin. Editorial changes are not marked. This revision also '

incorporates the applicable provisions of Office Letter No. 1000, " Requesting OI Investigations and Notification to OI of Potential Wrongdoing," and Office Letter No.1002, "The Timing of the Disclosure to Licensees of Pending Investi-4 gations and/or Criminal Referrals." Thus, Office Letters j Nos. 1000 and 1002 are hereby cancelled.

. DIVISION OF [

} ORIGIN: Division of Reactor Program Management CONTACT: Jean Lee, 415-2918 -

8

) DATE APPROVED: July 31, 1996 i

i AVAILABILITY: Roberta Ingram, 415-1219

(

r A

4 4

C i

i 9701240114 970114 PDR FOIA KELLER96-488 PDR

0 NRR OFFICE LETTER NO.1003, REVISION 2 l

MANAGEMENT OF ALLEGA TIONS 1 ,

.ml POLICY l

In accordance with Management Directive 8.8, " Management of Allegations," it 1s the policy of the NRC to review allegations and consider appropriate l

enforcement action, when warranted. The allegations must be reviewed as expeditiously as resources and other priorities allow - normally, the goal is to complete the review within six months of receipt by the office assigned responsibility for review. {

An alleger is not a confidential source unless a written confidentiality i agreement has been issued. However, it is the policy of the NRC to take all reasonable efforts to prevent disclosure of the identify of an alleger to any individuals or other organizations outside the NRC unless indicates no objection to being identified, (b) disclosure (a) the allegerto is necessary ensure public health and safety, inform Congress or State or Federal agencies in furtherance of NRC responsibilities under law or public trust, (c) the J, alleger has taken actions that are inconsistent with NRC protection of the  !

alleger's identity, (d) disclosure is necessary to pursue an enforcement '

hearing, or (e) disclosure is necessary in furtherance of a wrongdoing investigation, including an investigation of harassment and intimidation. All potential licensee and contractor wrongdoing matters must be promptly provided to the Office of Investigations (01). 01, in consultation with the technical and legal staff, will determine if an investigation of wrongdoing matters (including harassment and intimidation) should be conducted.

All allegations of wrongdoing by NRC employees or NRC contractors that arise within the context of an allegation will be handled in accordance with NRC Announcement No. 14, dated February 16, 1996. Such allegations will normally be handled outside the allegation review process. Supplemental information is provided in Office Letter No.1004, "NRR Handling of Allegations of Improper Actions by NRC Staff Involved in License or Inspection Activities."

BACKGROUND

~

Since December 1982, the NRC has followed procedures approved by the Executive Director for Operations (EDO) for the handling of allegations. In June 1987, NRC Manual Chapter 0517, " Management of Allegations," was issued to all NRC employees. NRC-0517 was revised and reissued on April 3, 1990. Reviewed and approved by the Commission, NRC-0517 codified the Commission's policies with regard to handling of allegations, confidentiality for allegers, and staff interface with the 01. The Appendix to NRC-0517 established the procedures.

and guidelines for implementing the Commission's policies in these areas. . :-.

Revision I to Office Letter No. 1003 was issued on December 31, 1990, to reflect the revision to NRC-0517. On May 1, 1996, MD 8.8 was issued. MD 8.8 e replaced NRC-0517 in its entirety. This office letter extensively references those policies and procedures issued in MD 8.8 and provides guidance on the implementation of MD 8.8 in NRR.

g

O DEFINITIONS An allegation is a declaration, statement, or assertion of impropriety or in- 5 adequacy associated with NRC-regulated activities, the validity of which has not been established. This term includes all concerns identified by sources such as individuals or organizations and technical audit efforts from Federal, . <

State, or local government offices regarding activities at a licensee's site.

Excluded from this definition are technical or regulatory inadequacies provided to NRC staff by licensee managers acting in their official capacity,; matters being handled by more formal processes such as 10 CFR 2.206 petitions, misconduct by NRC employees or NRC contractors; non-radiological occupational health and safety issues; and matters involving law {

enforcement and other Government agencies. ,

i An emergency situation is one in which, in the opinion of the senior technical staff knowing of the situation, a present danger to public health or safety or to the common defense requires the release of investigative information to a licensee without the delay necessary to consult with appropriate OI personnel.

Such information must be kept to the minimum necessary to immediately protect the public.

I RESPONSIBILITIES AND AUTHORITIES Office of the Director. 'NRR

a. Approves all policies and procedures concerning the management of allegations in NRR.
b. Approves all confidentiality agreements issued by NRR. f
c. Approves all referrals to the Office of the Inspector General (OIG) initiated in the allegation review process.
d. Informs the Director, Office of Investigations (01), in advance, when information that may compromise an investigation must be released to a licensee.
e. Informs the Director. 01, and the ED0 that information that may compro- 5 mise an investigation has been released, in an emergency situation, to a licensee.

'This exclusion is intended to clarify that technical or regulatory inadequacies discussed during official routine conversations between licensee managers and NRC staff members are normally not intended to be treated as q allegations. However, if the information provided by the licensee manager 1 concerns a wrongdoing issue or the manager expresses dissatisfaction with the licensee's handling of the issue, or the matter relates to another facility, .

the information should be treated as an allegation.

1.

p The NRR A11eaation Review Board directs and oversees the allegation management process in NRR. Among other things, the Board does the following:

. E

a. Reviews each new allegation considered for NRR action to determine the appropriate resolution plan (including the degree of regional office and/or licensee involvement), approves schedules, and establishes review priority,
b. Reviews assignments of allegations to NRR branches for resolution.
c. Determines the potential safety significance of each allegation. [
d. If 01 has not determined an investigation is warranted, discusses the l

need for OI consideration. Under normal circumstances, NRR will already i have advised 01 if wrongdoing is suspected. The need for notifications may arise within the context of an allegation or may come to the staff's l attention through other means.

l e. On the recommendation of the Office Allegations Coordinator (OAC),

i reviews actions taken by the assigned branch or project director-ate and approves a revised review plan or closure when the pro-1 l

posed closure differs substantively from the approved resolution p1an.

f. Reconvenes to review allegations open for more than 180 days to determine the reasons for the delay in resolution and to focus management attention on these issues, as necessary. Such reviews will l occur every 4 months, commencing when the allegation is 6 months old.

l .E, However, this review would not normally include matters under review by 01 or the U.S. Department of Labor (DOL).

g. Recommends NRR priorities for 01 cases and reviews those priorities, periodically for revision, if appropriate.

NRR Division Directors (As Appropriate)

a. Ensure that the policies and procedures in MD 8.8 and in this office ~'

l letter are implemented by division managers, supervisors, and staff. i

b. Review all closure letters to allegers and letters that provide results l of review, including interim reports, after concurrence by the OAC.

l

c. Approve formal notifications to 01, with input on priorities from the ARB.
d. Project Division Directors participate, as required, as members of the "~

ARB.

l.

l l

l l

e. Technical Division Directors are invited to attend meetings of the ARB l when allegations within their purview are discussed and are expected to w attend the third and subsequent status ARB meetings on allegations not 5 yet closed.

l NRR Branch Chiefs and Proiect Directors .

a. Ensure that their staff are familiar with the policies and procedures in M) 8.8 and in this office letter.
b. Participate in the ARB process, as required. g
c. For allegations assigned to their branches or project directorates, propose resolution plans for consideration by the ARB and ensure that the resolution plan approved by the ARB is followed and the schedule for l

resolution is met. l

\

d. Prepare letters to allegers to advise of allegation receipt, status, or closure.
e. Approve and sign other correspondence that leaves the office Il!

i involving allegations, following concurrence by the OAC and '

l Division Director, as required.

f. Ensure that all suspected or potential wrongdoing issues that surface outside the allegation process (i.e., through inspection findings) are i brought to the attention of OI on a timely basis. Such issues will also be brought to the attention of the ARB for recommendation of prioritiza-tion to OI. {.
g. Advise the OAC of notifications to 01 by the branch or project director-ate.
h. Prepare formal 01 notifications and referrals, if required.

Director. Division of Reactor Procram Manaaement (DRPM)

a. Administers the allegation review program in NRR, in accordance with 3 MD 8.8 and this office letter,
b. Serves as Chair of the ARB.
c. As Chair, ARB, assures that safety significance, resolution plan, review priority, and wrongdoing matters are considered for each allegation.

NRR Office A11eaations Coordinator y L

a. Provides advice, guidance, and assistance to NRR management and staff in the implementation of the policies and procedures in MD 8.8 and in this ,

office letter.

'i I

1 l l

-5 . ,

! I

b. Serves as the central control point for allegations assigned to NRR.

1 l

c. Reviews NRR correspondence involving allegations that leaves the Ei '

office, including letters to allagers and letters to licensees and t

vendors referring allegations. .

l l d. On receiving information about suspected wrongdoing violations from NRR staff, notifies 01 or confirms with OI that notification has been given. 1 I

i e. Prepares letters to allegers to advise of review, status, or transfer of resolution responsibility to another office.

E.

i f. Requests TAC numbers for allegations assigned to NRR for review.

p .

j g. Maintains the official agency files on allegations assigned to NRR.

l h. Assists the Chair of the ARB.

i l 1. Performs other 0AC duties as described in MD 8.8.

All NRR Fanloyees

^

a. Maintain a working knowledge of the policies and procedures in MD 8.8  ;

, and this office letter.

l' b. Record the receipt of new allegations in as much detail as possible, I l using Attachment 2, " Allegation Data Receipt Form," or equivalent.

1 c.. Provide information received regarding suspected wrongdoing to OI or to b j the OAC promptly following receipt.

j d. Guard the identity of allegers in accordance with policies and .

j procedures in MD 8.8 and this office letter.

l l e. Provide all information received on allegations directly to the OAC l within 5 days of receipt of the allegation.

d

f. Ensure that correspondence to and from allegers and similar
  • allegation material receive appropriate limited distribution

! (e.g., is not placed in the public document rooms, docket files,

] central files, or the Document Control System).

j g. Consult the OAC when in doubt regarding whether a matter is an allega-tion or when uncertain of the procedure to follow.

s l.

i In addition, senior technical staff may, in an emergency situation, release information that may compromise an investigation to a licensee. (See Basic i Requirements, paragraph g.) In such situations, the Project Manager (or other i, assigned person) is responsible for documenting any release of information 1

I l

1 t i l

3 .

g

~

j _ _

1

l O.

l that may compromise an investigation, to a licensee or vendor, including the preparation of notices to the EDO and the Director, 01, for the signature of ~E the Director, NRR. "

BASIC REQUIREMENTS

a. Receiot of Alleaations Any NRC employee may receive an allegation. Accordingly, all employees must maintain a working knowledge of the NRC policies and employee responsibilities for the receipt, control, and processing of allega- :rTJ tions. Attachment 1 is a flow chart that depicts the allegation review '

process. Employees are responsible for ensuring protection of the identity of an alleger, as well as information that could compromise the identity of an alleger. Therefore, only persons involved in the review and processing should participate in discussions or handle documentation concerning allegations.

NRR employees who receive allegations verbally will record the informa-tion on an " Allegation Data Receipt Form," Attachment 2, or equivalent, y and provide this form, along with any other information or material related to the allegation, directly to the OAC within 5 days of receiv-ing the allegation. During the initial contact with the alleger, the alleger must be informed of NRC identity protection provisions and limitations. (See Attachment 3 for a discussion of the information to be provided to the alleger.) The original copy of allegations submitted in writing by an alleger, including the envelope, will also be given to the OAC within 5 days of receipt. No copies are to be made. (NRR employees working with the regions as part of a region-based inspection program should provide this information to the regional OAC.) The OAC y

will distribute copies, as needed, to the appropriate management for review and discussion of the safety significance of tho allegation during the ARB meeting.

As stated above, the individual receiving the allegation shall notify OI and the OAC of allegations of suspected wrongdoing promptly after receipt. This notification may' be a telephone call or a brief memoran-dum with copies of telephone conversation records or allegation receipt documentation. (See Management Directive 8.8, Part IV.) 1

b. Determination of Action Office On receiving an allegation, the OAC will determine the most appropriate action office for resolution. Normally, allegations regarding a specific reactor or material facility are referred to the appropriate regional office or the Office of Nuclear Materials Safety and Safeguards, respectively. Allegations against a .[_

reactor vendor, or those involving interpretation of license conditions or technical specifications, and generic issues are usually handled by NRR. If the OAC determines that the allegation '

1 .

0 should be assigned for resolution outside NRR, the OAC will initiate discussions with the proposed action office. If that office agrees to accept the allegation, the allegation J will be transferred by the OAC. The OAC will also ensure that the a11eger is advised of the new point of contact, if necessary.

All allegations not assigned to'other offices or regions will be assigned by the OAC to an NRR branch or project directorate for resolution. The OAC will also advise the AR8 Chair of the receipt of the allegation and will arrange an AR8 meeting.

E, TAC numbers are used in NRR to record time spent on reviewing allega-tions. Tha OAC will secure a TAC number from the Division of Inspection and Support Programs and will inform the cognizant staff of the number.

Resources expended during allegation resolution activities are not charged to licensees,

c. Action by the A11eaation Review Board The ARB consists of (1) the Director, DRPM, who will serve as Chair; (2) the OAC; and (3) an NRR Projects Division Director or 1

designated Deputy Director. Normally, the Projects Division 4 Director is selected by the OAC according to the reactor facility involved. When a reactor facility is not involved, the Projects Division Director will be selected on a rotational basis. In the absence of the Director, DRPM, the Deputy Director, DRPM, will be the alternate chair.

Prior to the meeting, the technical contact will prepare an allegation E briefing sheet and provide it to the OAC. Attachment 3 is a copy of the format for the briefing sheet. The briefing sheet must be completed and returned to the OAC no later than two days prior to the meeting to allow timely distribution by the OAC to the AR8 prior to the meeting. At'the ARB meeting, the Branch Chief or Project Director assigned to act on the allegation will review the allegation with the ARB, discuss the poten-tial safety significance, propose a resolution plan and schedule, and make a recommendation on the need for licensee referral and 0I involve- y ment. The ARB will approve a resolution plan and review schedule and J will determine the potential safety significance. The AR8 will also assign a priority to resolving the allegation in accordance with the priority ranking system established by the Director, NRR, in his memorandum of June 6, 1993, to staff regarding the priority ranking system for review efforts. Allegations assigned as Priority 3 will have a completion target date of six months or less.

. Although the staff may notify 01 directly of an allegation if the staff -

suspects wrongdoing, the OAC should also be informed so that the ARB can i consider the allegation. OI will advise the OAC of its decision whether to initiate an investigation. If OI plans to initiate an investigation, a formal referral will not be necessary. In those rare occasions where i

O' 01 does not plan to initiate an investigation and the ARB recommends '

that an investigation is needed to determine whether regulatory action ~E is required, the AR8 will discuss with OI the basis for the recommenda- n' tion of initiation of an investigation. If this matter is not resolved at this level, it may be considered by NRC senior management (See Management Directive 8.8.) .

d. A11eaation Review Board Meetinas l As determined by the ARB Chair, other Division Directors, Branch Chiefs, or other NRR staff may be required to participate in the 5'fr '

ARB proceedings.- Cognizant technical Division Directors are invited to ARB meetings; and the Director, 01, will be advised of all ARB meetings and invited to attend. The Office of Enforcement and 1 the Office of the General Counsel are invited to meetings when an allegation involves issues within their purview. The Chair will  !

determine at the beginning of each ARB meeting if sufficient personnel are available to conduct the business of the ARB. The ARB is required to meet within 30 days of receipt of an allegation'for which (1) NRR is {

1 the action office .or (2) no agreement has been reached on assigning it Tlj to another action office. ~

IfduringthereviewofanalNgation,thebranchorproject directorate assigned by the ARB to act on the allegation deter-  !

mines that the appropriate closure differs substantively from the )

resolution plan approved by the ARB, the ARB will normally, on the l recommendation of the OAC, reconvene to review the revised closure '

action. The OAC may also recommend that the ARB reconvene for other. reasons; for example, if information becomes available that

changes the safety significance of the allegation or new techni- T) cal or wrongdoing information becomes available. Individuals responsible for resolving the allegations should come to the ARB meeting prepared to (1) discuss the safety significance of the allegation, assuming that the allegation is true, (ii) recommend a priority for an OI investigation (see Part (IV)(A)(5) of MD 8.8, if applicable).. and (iii) justify their decisions in (1) and (ii).

If a referral to a licansee or vendor is recommended or there is a ....

recommendation that 01 consider an issue for investigation, the J review group should be prepared to discuss the rationale for the proposal. . ,

e. Action by the Assioned Branch or Pro.iect Directorate The NRR branch or')roject directorate assigned action on the I allegation will nace its best efforts to resolve the allegation and bringsit to final closure in accordance with the resolution -;

plan, and schedule approved by the ARB. In its resolution t. i activity, a branch may receive new allegations. The branch should discuss this situation as soon as possible with the OAC. Nor-mally,.-allegations of a similar nature or involving the same 1 .

m -- -- - - - - . - - ----_- _---- - _._ - - - - _

0 system or plant function will be documented by the receiving party and incorporated as part of the original allegation by the I OAC.

However, these allegations may be addressed separately if different allegers are involved, if it is not feasible to incor-porate the new allegations into the continuing resolution effort or if consideration of unrelated new matters would significantly delay closure of the original allegation. The ARB will reconvene to discuss the safety significance and proposed resolution of the new allegations.

Similarly, an inspection or other resolution activity may uncover 3 evidence of wrongdoing or impropriet not a part of the original concern. y by the licensee or vendor that was When NRR personnel uncover such information, they will contact their management as soon as possible for guidance on proceeding with resolution activity. Management should consult with OI promptly to determine the proper course of action.

However, all parties should exercise caution to avoid compromising a subsequent investigation by 01. Management shall also assure that the -

0AC is informed. The OAC will confer with the Chair. The OAC will arrange the ARB meeting, if requested by the Chair, ARB.

f. Documentation No informal transmittal of documents from the NRC to licensees or vendors will occur. Correspondence addressed to reactor licensees must be signed by the appropriate projects organization. Copies of letters from allegers in whole or in part, will not be for-warded to licensees or ve,ndors. gl The referral may contain language similar to the allegations, but care must be taken to avoid inad-vertent disclosure of information that could reveal the identity of the alleger. All documentation involved in the allegation resolution process which contains the identity of the alleger will ,

have limited distribution. Copies will not be placed in the Document Control System (DCS), the NRC Public Document Room (PDR),

Local PDRs or the docket files. Access to this information will be on a nee,d-to-know basis. Copies of correspondence will not be placed in files (including branch reading files) accessible to 3 "

individuals who do not have the required need to know. Distribu-tion within NRC will be made using " Addressee Only" envelopes.

The OAC will receive copies of all correspondence on allegations.

Questions on Freedom of Information Act (F0IA) applicability should be referred to the OAC or to the NRC Agency Allegations Advisor.

  • .e Because of the sensitive nature of allegations, the inclusion of '

allegations in daily or weekly highlight reports requires the approval of the Office Director. If it is determined that senior management should be apprised of specific allegation information,

'O

O consideration should be given to issuance of a note or an "Execu-tive Team Only" highlight. The technical substance of any matter ~E may be included in daily or weekly highlights if the information a is obtained from a source other than an alleger.

All of the following documents will become part of the permanent . <

allegation file maintained by the OAC. l

. I

1. Allegation Data Receipt Form and Allegation Briefing Sheet l

As stated earlier, allegations received verbally by NRR employees y' will be documented on an Allegation Data Receipt Form (Attach-ment 2) or equivalent and will be handcarried by the recipient directly to the OAC or forwarded in an " Addressee Only" envelope within 5 days of receipt. The briefing sheet will be prepared prior to the ARB meeting.

2. Incoming Correspondence The recipient will provide the originals of all incoming corre-spondence or E-mails from allegers, including any envelopes, and T

~

copies of all correspondence from the licensee or the vendor

' concerning allegations to the OAC for incorporation in the allega-tion file.

3. Acknowledgment Letters The OAC or the assigned branch or project directorate will prepare and issue a letter to the alleger within 30 days of the receipt of , [.

the allegation by NRR. The letter will acknowledge receipt of the allegation, establish a contact person for further correspondence, provide the staff's understanding of the allegation, invite the alleger to clarify or correct the staff's interpretation, discuss NRC identity protection provisions and limitations, and provide additional information as needed. If the alleger believes he or she has been discriminated against as a result of raising safety concerns, the letter will also advise the alleger of the right to . - -

file a complaint with the U.S. Department of Labor. J

' Attachment 4 is a sample of the format for an acknowledgment let-ter. Acknowledgment letters will be signed by the Branch Chief or Project Director who has the lead responsibility for allegation resolution, or the OAC. The OAC and the lead Branch Chief or 4

Project Director will be placed on concurrence for these letters.

i In some cases it is necessary to call the alleger to obtain more precise information on the allegation prior to issuance of the m acknowledgment letter. All telephone calls to allegers must be e documented as t% scribed in item 4 below.

)

O.

i I

4. Meetings and Telephone Contacts with Allegers When it is necessar j l' with an alleger (e.yg.,

to contact anan to clarify alleger by telephone allegation), or to must the results meet be documented by the assigned branch or project directorate. This documentation may consist of a memorandum to the OAC, a Record of Conversation (Optional Form 271), or a letter to the alleger.

5. ARB Meeting Summaries 1 t

The meeting summaries of the ARB will be prepared by the OAC and approved by the Chair, ARB. These summaries will identif Tl allegation; (2) the safety significance of each concern; (3) y (1) the the facilities involved; assignment; (5) the re(4) the NRR solution plan,branch or project resolution directorate schedule, and technical review priority; (6) the potential wrongdoing informa-tion and 01 notification; (7) recommended priority level for 01 investigation (if applicable);

be referred to the licensee or v(8) inhether endor; the allegation (9) basis should for AR8 decision for items (5) through (8); and (10) any other comments that the

,[

ARB wishes to make concerning the allegation.

Meeting summaries will be distributed to the Executive Team, cognizant Division Directors, Branch Chiefs or Project Directors, the Director 01, the Director, Division of Operational Assessment of AEOD, the OAC, and the meeting participants. Attachment 5 provides the format to be used for ARB meeting summaries.

6. Letters to Licensees, Applicants and Vendors Letters to the licensees, applicants, or vendors concerning allegations or referring allegations for review will be signed at the Branch Chief or Project Director level. The OAC will be  !

placed on concurrence for these referral letters.

For referrals to vendors and licensees, the description of the allegation should be marked "NOT FOR PUBLIC DISCLOSURE." The ~

letters should state that the concerns are the result of an -

allegation and the allegation number will be noted on the letter.

In addition, vendors and licensees should be told not to docket their responses. The response is to be sent to the office / region contact designated in the letter with no other copies to the NRC, i.e., the document control desk.

7. Notifications to 01 As stated in Part IV of Management Directive 8.8, it is the '

responsibility of the staff to promptly notify OI of suspected

' wrongdoing information. The notification may be as informal as a telephone call or note to 01. OI will consult with the technical

. - - . ----- -- - - ~ . - _ . - - - . - _ - - - - . - . .

l i i

j and legal staff and evaluate the information and other relevant information in deciding whether to initiate an investigation. u,

! However, the ARB may determine or 01 may request that formal 5 i notification.should be made in certain instances. If so, a

! memorandum will be issued by the cognizant Division Director to 1

the Director, 01. .

8. Closure Documents 4

Within 30 workdays of when the NRC has completed action on the 1 allegation, the assigned branch or project directorate will issue a closecut letter to the alleger, to be signed by the Branch Chief T' ,',

} or Project Director, detailing the action taken by the NRC on the

! allegation and enclosing any related inspection reports, safety

evaluations, or staff analyses that support the allegation resolu-i tion. In certain instances such as where there is little techni-  ;
cal content, the closecut letter may be signed by the OAC. i i Inspection reports and other documents may be used to address and resolve certain items and need not acknowledge that the issue was  !

} raised in the context of an allegation. The OAC and the cognizant l Division Director will be placed on concurrence for all status ]1 l

reports and closure letters to allegers. Attachment 6 is an l i example of a closure letter to an alleger. {

j If the alleger is anonymous, the closure document will be a memorandum to the OAC and will include the same information as closure letters to allegers. Closure letters may be issued by the Branch Chief or Project Director having resolution responsibility j but will be concurred in by the appropriate Division Director. In

! some cases, the OAC may recommend that the closure document be <[

j held for review by the ARB to determine the adequacy of the resolution effort. The closure document will always be held for i ARB review if the closure differs substantively from the resolu-l tion plan. Attachment 7 is an example of a closure memorandum.

l f g. Disclosure to Licensees or Vendors of Pendina Investiaations and/or i

4 Criminal Referrals

1. In most cases, the review of technical issues and the conduct of investigative activities proceed in parallel. For example, an
inspection or technical review may be conducted at the same time as investigation activities are in process.

In such cases, the staff must coordinate with OI to avoid compromise of an 01 inves-i tigation. Information regarding a pending or ongoing investiga- ,

] tion by OI is normally released to a licensee only if 01 deter-i mines that such release.will expedite the investigation. Normal- ~r i ly, referrals to licensees regarding a technical or safety issue L j will not reveal investigative activities. When information that

must be released to the licensee or vendor will present the risk i of compromising an investigation, the Director, NRR, shall '

2 l

i

, O i,

3 ,

3

' inform the Director, 01, in advance that information related to an i

open investigation is being considered for release to the licensee or vendor because safety or security concerns require initiation .I

. of corrective actions before the investigation report is pub-3 lished.

j The Director, 01, will review the information to be released and

advise the Director, NRR, of the anticipated effect of its release on the course of the investigation. The Director, NRR, will t release the information only after determining that the safety or 1

security concerns are significant enough to justify the risk of :E.

j compromising the effectiveness of the pending investigation and, possibly, subsequent enforcement or prosecution options. Any such l release of information should be recorded in the investigation report.

j .

i In the event of an emergency, or a significant safety or security

! issue that appears to require immediate action, senior technical

staff, at their discretion, may discuss with,.show to, or provide i

to the licensee or vendor any pertinent material they believe the circumstances warrant. If time permits, NRR management should be 1l consulted before such action is taken. Examples of such types of, i

emergency situations are those that involve a potential radiation  ;

i

overexposure to personnel or a potential release of radioactivity to the environment.

4

, For example, if an NRC employee knew, through

an investigation, that falsified calculations were used to deter-mine the radioactivity of the contents of a tank and there was a )

4 4

i clear potential for the release of the contents to the environ-  ;

ment, the NRC employee should proceed with action to stop the '

release immediately. Likewise, if an NRC employee who, solely '

because of information gained from an investigation, was in a position to prevent a radiation overexposure to someone, the NRC (

employee would intervene even though the intervention might l

i compromise the investigation. l As soon as practical after a release of investigations information in such an emergency situation, NRR management, including the "i i

Director, NRR, shall be informed of the details regarding the "

! information disclosure. The Director, NRR, will inform the EDO and the Director, 01. In all other instances where there is not an immediate danger to public health and safety, the staff is required to consult with 01 before releasing investigations l information.

d i

As previously stated, generally there should be no need to indi-

  • cate the fact that an investigation is underway when information .

is provided to licensees pertaining to potential safety concerns 1 i or to obtain correction of a specific technical issue. However, i - when for the reason stated above, the Director, NRR, decides after 3 i

)

b

1I
1 4

O.

this decision and the basis on which the delay is found to be I consistent with public health and safety should be documented and w the decision reexamined every three months to ensure its continu- E ing validity. The Project Manager (or other assigned reviewer) is responsible for. ensuring that this reexamination takes place and l 1s documented. .

1 The fact that a particular matter has been or will be referred to l the Department of Justice (D0J) should never be disclosed to the ,

licensee by other than 01 or the D0J itself. A reply of "I cannot comment on such matters" is appropriate in most cases.

7 I h. Identity Protection and Confidentiality '

1. It is the policy of the NRC to protect the identity of all alleg-  !

, ers. For the majority of the individuals bringing their ..cicerns  !

to the NRC, the staff will make reasonable efforts (as sumurized below and as defined in the Commission's policy statement on ,

confidentiality and in MD 8.8) to protect the alleger's identity. l Reasonable efforts include the following:

7l l l a. The need-to-know principle will be applied; that is, the i identity of an alleger or other identifying particulars will J not be unnecessarily used in internal NRC discussions and documents.

b. Copies of letters from allegers, in whole or in part, will  !

' not be forwarded ts licensees or vendors. The referral i may contain language similar to the allegations, but care y!

must be taken to avoid inadvertent disclosure of informa- )

tion that could identify the alleger. I

c. Documents that contain the identity of the alleger will be placed in secure storage when not under the personal control of the user.
d. Inspection reports, safety evaluations, and other publicly ..

available documents will not contain the identity of allegers. .;

e. Draft documents will be discarded as soon as possible.
f. Documents containing the identity of the alleger will be hand-delivered or securely wrapped and marked " Addressee Only."

.L i L

'i i

O' l

8 .

l g. Information that could reveal the identity of the alleger will usually be withheld under F0IA.

I

h. Responses to specific questions from outside the NRC will

! not acknowledge that an individual is an alleger. NRC j . policy is to neither confirm nor deny that an individual

, is an alleger, usually by a statement to the effect that l "we do not comment on such matters."

2. An alleger will be informed that NRC will take all reasonable j measures to protect the alleger's identity unless the alleger has 1

j clearly indicated no objection to being identified, the alleger {

has taken actions that are inconsistent with and override the j purpose of protecting the alleger's identity, or disclosure is .

necessary because of (1) an overriding safety issue, (2) an order l
of a court or NRC adjudicatory authority, (3) an enforcement j hearing, (4) a need to inform Congress or State or Federal agen- l cies in furtherance of NRC responsibilities under law or public '

l trust, or (5) investigation of a wrongdoing issue, including harassment and intimidation.

] ,

I j 3. When the protective measures summarized in items 1 and 2 are -

considered insufficient to protect the identity of an i alleger, the agency may consider granting confidential '

3 source status to an alleger. As defined by MD 8.8 and by the Commission's policy statement on confidentiality, t i i confidential source is an alleger who has signed a written  !

Confidentiality Agreement with an authorized NRC official. '

In NRR, the authorizing official is the Director, NRR. All 1:!

! requests for confidential source status should be directed to the OAC. The staff is not authorized to grant confiden-j tial source status. ,

t

, 4. The recipient of an allegation should not raise the subject 4

of confidentiality. Questions regarding confidentiality j should be addressed to the OAC.

i . 1 EFFECTIVE DATE .  !

This office letter revision is effective immediately. l 4

i i

.I

L

O REFERENCE Management Directive 8.8, " Management of Allegations" ]

Attachments:

1. Allegation Review Chart *
2. Allegation Data Receipt Form
3. Allegation Briefing Sheet
4. Sample Acknowledgment Letter
5. ARB Meeting Summary Format
6. Closure Letter
7. Closure Memorandum T cc w/ attachments:

J. Taylor, EDO J. Milhoan, DEDR H. Thompson, DEDS T. T. Martin, RI S. Ebneter, RII H. Miller, RIII .A L. Callan, RIV 1 J. Blaha, EDO G. Caputo, 01 J. Lieberman, OE L. Chandler, OGC P. Norry, ADM SECY OGC PUBLIC

E
  • ?

A.

  • I L

2 a 4 a.m .. s -

f

-""a= *. .

I

'jf

^ O i

' I L~hl'sljlGll!lI,l

~

~

I wlul O

li= / '

(

~~

}

l Ihk #,l\

.E I! l!

1a r tA _s 5 5

~i I Il v

l .ullI,l -

a T T vl T i -

m l=t .

i lil \ll I

T elj l !!

'j,II

/'l il .

l

~

ll. rir ' !i

,  !! c-I!

'f i

I v

ul lisW= ll g" d ii

                                                      =                     si                       :

4. n Eg e lu ATTAC N NT 3

         ~

9

(2 4 LIMITED DISTRIBUTION ALLEGATION DATA RECEIPT FORM Date & Time Allegation , Received: Number: (leave blank) E Allegation received from: ]. Name: Address: . Phone: ,3 . Job title: { Employed by: Facilities Involved: Alleger's Preference for Method and Time for Further

Contact:

Details of Allegation: (Ask: Who? What? Where? When? How? Why?) k (attach additional pages, if necessary) Identitv ProtoctIon Procedures and Lfmitatiens Inform alleger of the following An alleger is not considered a confidential source unless a confidentiality agreement has been signed by Nec and the source. NaC wilt take all reasonable measures to 5, protect the alleger's identity mless the alleger has clearly Indicated no objection to being identified, 2 the atteper has taken actions that are inconsistent with and o.orride the purposc of protecting the atteser8 4 Identity, or disclosure is necessary because of (1) an overriding safety issue, (2) en order of a court or NGC adjudicatory authority, (3) en enforcement hearing, (4) e need to inform Congress or State or Federal agencies in furtherence of NRC responsibilities mder low or phtic trust, or (5) investigation of a wrongdoing issue, including herseement and intimidation. DOL Rfahts (if applicable) If you believe you have been discriminated agelnet for engaging in a protective activity, you may have personal remedios through the U.S. Department of Labor. The complaint must be stdunitted in writing within 180 days of occurrence of the discriminatory act to ensure that your personst employee rights are protected. 3

  • The complaint should be filed with your local DOL office or with the Of flee of the Administrator, Wege and hour DivieIon, Esployment standerds Adminietretion, U.S. Dopertaent of Labor, Room $3502, 200 ConstItWtion 1-Avenue, NW, Weehington, Oc 20210.
    . Employee receiving allegation: Name Organization:                                   Phone:

LIMITED DISTRIBUTION ATTACHMENT 2

                                                                                                                         . r

\

O SENSITIVE PREDECISIONAL INFORMATION - NOT FOR PUBLIC DISCLOSURE ALLEGATION BRIEFING SHEET Prepared by (Name) (Date) . 1. ALLEGATION N0. (if known):

2. FACILITIES /0RGANIZATIONS:
3. STATEMENT OF ALLEGATION (S):

T

4. BACKGROUND:

1

5. DISCUSS POTENTIAL SAFETY SIGNIFICANCE, INCLUDING BASIS:
6. NEED FOR Of INVESTIGATION AND PRIORITY (High/ Medium / Low or N/A):
                                                                                ;E
7. PROPOSED TECHNICAL REVIEW PRIORITY:

(I) High Priority (immediate action required) (2) High Priority Near Term (short-term action required) (3) Low Priority (longer-term action required)

8. REGULATORY ASSESSMENT:
9. NON NRR ISSUES (0GC, OE, REGION, ETC.) cl l
10. PROPOSED RESOLUTION PLAN AND TARGET DATES:

SENSITIVE PREDECISIONAL INFORMATION - NOT FOR PUBLIC DISCLOSURE ATTACHMENT 3

O. 4 SAMPLE ACKNOWLEDGMENT LETTER j

SUBJECT:

(Facility Name) 1 Dear i 4 This letter acknowledges receipt of your letter dated . We II! ; have decided process. to address the issue (s) you raised in our allegation review The first step in that process is to confirm with you the issue (s) {. you wish to have evaluated by the U.S. Nuclear Regulatory Commission (NRC). Our understanding of your concern (s) is as follows: l. 1 i 2. [I 4 3. I i

4. [l[

4 { 5. l-i If the above summary of your concerns is incorrect, please contact me within I, two weeks at 800-368-5642. If you prefer, you may mark corrections on this ' letter and return it to us. The next step in our review process is to conduct a detailed review of the i issue (s) you raised. Resolution of your concern (s) has been assigned to the Branch / Directorate. Our goal is to complete the review within 180 days. Upon completion of our review, we will - ) inform you in writing of the results. " For your information, the following is a discussion of our routine procedures for handling issues such as those you raised. Although you are not a confi-dential source unless a written confidentiality agreement has been issued, it is the policy of the NRC to take all reasonable efforts to prevent disclosure of your identity to any individuals or other organizations outside the NRC unless (a) you indicate no objection to being identified, (b) disclosure is i necessary to ensure public health and safety, inform Congress or State or ' ' Federal agencies in furtherance of NRC responsibilities under law or public "_

    '   trust, or to support a hearing on an enforcement matter, or (c) you have taken                                    '
actions that are inconsistent with NRC protection of your identity. If we
  • determine that an investigation of wrongdoina matters (including harassment
.'      and intimidation) should be conducted, it may be necessary to disclose your identity.

4 ATTACHMENT 4

                                                                                                                         's 4
                         -m-.          -%   v-              i y-                  --.          w               -

O In some instances, we request licensees or vendors to address concerns. If we do so for the issue (s) you brought to our attention, your identity will not be disclosed. The response by the licensee or vendor will be evaluated as a part of our review. '][ If a request if filed under the Freedom of Information Act related to your area of concern, the information provided will, as allowed by that Act, be - purged of your name and other potential identifiers. s If you have please let usany questions or additional information concerning the above, know. Thank you for contacting us regarding the above con-cern(s).

                                                                                                '[{

Sincerely, Office Allegation Coordinator, Project Director, or Branch Chief Distribution: Reviewer (redacted copy) and Allegation Coordinator _l[ Concurrence must include the Allegation Coordinator and review Branch Chief or Project Director t L F

                                                                                                  *G

_ . . _ . _ - - _ _ _ - . . _. --- -- -.. _ . _ = _ . . . . . - - 0 LIMITED DISTRIBUTION ALLEGATION REVIEW BOARD SUMARY Allegation Number NRR-XX-A-XXXX . TAC No. l l

1. The NRR Allegation Review Board met.on (date) at (time).

. 2. Present at the meeting were: (list of attendees).

3. Facilities / organizations involved:
4. Allegation title: (insert abbreviated description)
5. This allegation has been assigned to (branch or project directorate) for resolution. , E.
6. The AR8 determined the concerns identified in the allegation to be .

safety significant/of no safety significance /of potential safety i significance based on . I

7. The AR8 assigned this allegation a Priority Level of (1-3) after consideration of its safety significance based on
8. (Potential wrongdoing issues) l
9. The following resolution plan and schedule was approved by the ARB:

Activity Due Date

a. Acknowledgment letter -
b. Referral to licensee / vendor
c. Inspection
d. Etc.
e. Closure letter 10.

The basis for the abcve resolution activities is as follows: y

11. Additional comments:
12. Prepared by:

Office Allegation Coordinator Date

13. Approved by: '

Chairman, ARB Date Distribution: NRR Executive Team Director. 01 Cognizant Division Director DOA Director, AEOD Chief, Assigned Branch or Project Directorate l " r NRR OAC 1 Meeting Participants Allegation File No. NRR-XX-A-XXXX l LIMITED DISTRIBUTION ATTACHMENT 5 eme- a ws

l b 1 . . p'p 'ing% 3" **, UNITED STATES I j .jf NUCLEAR REGULATORY COMMISSION 4 o WASHINGTON. D.C. 20555 0001 l .  %, ...../ October 13, 1994 E l, h I amuuammmmmmmmun l Dear Mr. g l By facsimile dated April 10, 1994, you submitted information to i Mr. 6 of my staff. By letter dated May 9, 1994, we acknowledged t E. i receipt of your concern and by letter dated July 14, 1994, we advised you that l our review of this concern was ongoing. The information you submitted has j been the subject of further review by my staff and the results of this review

are provided below.

1 The NRC staff performed an inspection in ]- l response to these concerns. ihe inspection' activities includ E e However, the results of

                                                                                                                                                                                  ,[ )

j 1

                                                                                                                                          =

l enclosed for your information. The M findings are discussed on 2 page 8 of the report. , Our evaluation of the information you submitted to the NRC by the facsimile i dated April 10, 1994, is complete, if you have any questions re ' evaluation, please contact Mr. N at (301) 6.garding our i I I Sincerely, e l.

o e
 }

4 i l

Enclosure:

                       " Routine Resident Inspection Report and Notice of Violation,"                                                                  '(

j dated July 26, 1994. ATTACHMENT 6

   -,,-c             -

I i O. ll ,#* *' % p 4 4 j UNITED STATES g o 2 NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 2055M001

           %, .....p                                      September 22, 1995 I *                                                                                                          ~E i

i MEMORANDUM T0: Jean Lee 7 Office Allegations Coordinator {

SUBJECT:

ALLEGATION ON

                                                                                                            ,. a.

i j 4 (ALLEGATION NO. NRR-94-A-0076) l In late 1994, an allege _r raised a concern during a casual conversation regarding the manufactured by ._ Inc., for motor-operated valves (MOVs) { installed in nuclear porer plants. Although the alleger initially indicated j that he would provide additional information, he did not respond to repeated 1l attempts to contact him by telephone to solicit the information. As the alleger did not provide a mailing address, the resolution of this issue cannot be provided to him. 1 On August 8 and 9, 1995, the NRC staff conducted an inspection at the office j. of issues.6 Attached in Misto evaluate a copy of the NRC report this and the documenting other staff's W findings. As discussed in the inspection report, the NRC staff has confirmed the allegation that th o g-L M i i states that it believes that the-1 the inspection, the staff found that . During l did not have adequate documentation for its position. Therefore, in the inspection report l staff cites, as a nonconformance, the failure of M , the to c

                                                                                                                 .I Nuclear power plant licensees have been informed of them at The staff will alert licensees to the findings from the inspection at the next p eting. We will also discuss this 4

issue with the region staff for their information. "

  '-                                                                                                           L i

i ( ATTACHMENT 7

i O i , i i i J. Lee 2 ' I  ! l l potential safety concern through meetings and inspections. This completes our i evaluation of the allegation. , . CONTACT: j t .

Attachment:

As stated - i i 1

r. ,

I I l 1 e-- l l

                                                                                        -s I, \

t

                                          -}}