Build an Examination Evidence Index for a Nuclear Outage

An examination index helps a reviewer find the records supporting a particular component, weld and examination event. During an outage, many people may produce procedures, field records, evaluations and closeout documents on different schedules. A list of filenames alone does not show how those records relate or which version supports a stated result. Begin by defining the index's purpose, scope and owner within the site's actual records process. The index should make a controlled evidence package easier to navigate without becoming an unofficial replacement for that package.

This guide provides an organizational worksheet for supporting examination records. It does not define a nuclear quality assurance program, select inspection requirements or certify software for regulated record retention. Use the licensee's approved processes to determine where actual records belong and which tools may handle them. The downloadable worksheet can be evaluated with fictional or otherwise authorized information before adoption. A useful index records supported relationships and unresolved handoff questions; it does not create missing approvals, technical evidence or permission to move controlled information into an unapproved workspace.

Define the index's coverage in its own introduction. An index for one contractor's examination package should not be titled as if it represents every outage record at the facility. Identify the covered work packages or other approved scope references, the period represented and any intentional exclusions. A completeness statement then has a meaningful boundary: the preparer can explain which expected records were reconciled and which records belong to a different handover. If the work scope expands, update that boundary and the expected-record inventory before making a new completion statement. This avoids a misleading situation in which the spreadsheet contains every row the preparer happened to receive but is described as a complete record of a broader assignment.

Confirm who receives the examination package, which system holds the authoritative record and what acceptance of the handover means. Separate a contractor's working folder from a record accepted through the site's controlled process. An emailed acknowledgment may confirm receipt without resolving technical review or records acceptance. Record the actual handoff status and its reference. This helps avoid a common closeout misunderstanding in which a package is described as complete merely because a compressed folder was transmitted before the scheduled deadline.

The NRC's historical RIS 2000-18 on electronic QA records discusses controls supporting record integrity and retrieval. It is background context, not a declaration that a particular current application satisfies a site's program. Determine the applicable current requirements through the responsible organization. The worksheet can list the record owner and destination; it cannot choose retention periods, approve a storage system or establish that a generic private account meets nuclear recordkeeping obligations. Keep those decisions with the actual program and the people assigned responsibility for them.

Identify the component or weld through the site's actual designation and the relevant drawing or configuration reference. Then identify the examination event separately. A stable component identifier can appear in several outage campaigns, follow-up examinations or repair sequences. Combining them into one row without an event reference can make an older result look like the current record. Include the work package or other source reference needed to distinguish the event and preserve the actual dates recorded for the work.

Check whether local contractor labels differ from site identifiers. Retain the original source label and its confirmed cross-reference instead of silently replacing it throughout the index. If the relationship is unresolved, identify the missing clarification and its owner. Do not infer that two similar weld numbers refer to the same physical item. A retrieval index is only as dependable as these identity relationships. The recipient should be able to recover the intended component and event without depending on the memory of the person who assembled the spreadsheet.

Classify each referenced item by what it actually contains. A field record, native acquisition file, evaluation sheet, issued report and closeout summary serve different purposes. A PDF summary should not be described as if it contains the native examination data unless that is true. Likewise, a file manifest proves what was listed for transfer, not whether every listed record has completed technical review. Use concise record-kind labels and preserve the relevant version or issue reference for each item.

Some records may remain in a separate approved repository while the index provides their controlled identifiers. State that arrangement accurately. A hyperlink is useful only if the intended recipient has appropriate access and can identify the correct record after ordinary system changes. Retain stable document identifiers alongside any permitted link. Do not copy an entire sensitive record into a broadly shared worksheet merely to avoid an access question. Resolve the authorized retrieval route through the site's records process and record the resulting reference at the level appropriate to the index.

Record the procedure identifier and revision supported by the examination record, together with any approved instructions relevant to that event. The latest available revision is not automatically the revision under which earlier work was performed. Preserve the historical relationship. If the record and work package disagree, leave a specific reconciliation question for the responsible reviewer rather than editing the index to make the references look consistent. The index should expose that discrepancy, not hide it through a convenient assumption.

Separate the examination procedure reference from any source used to evaluate findings. A package may contain different documents governing how work was performed and how a result was assessed. The index can identify both roles without reproducing controlled technical text. Include the actual review or disposition references where required by the receiving process. Do not let a broad code edition label stand in for a missing procedure revision or an unresolved applicability decision. The useful information is the supported chain connecting the event, its governing instructions and the records produced under them.

Identify the roles associated with the examination and review using the actual records. A person who uploaded a file may not be the examiner or technical reviewer. Preserve that distinction when assigning record ownership. Where personnel qualification evidence is part of the required package, reference the relevant controlled records and their applicable scope through the site's process. Avoid describing a general training document as if it were task-specific authorization. The index should help the authorized reviewer find the evidence needed for the actual role.

Limit personal information to what the approved handover requires. A retrieval worksheet does not usually need unrelated credentials, private contact details or copies of every personnel document available to the preparer. The certificate manager is a general organization tool, not an issuer-verification service or a substitute for the site's qualification records system. Do not assume it is approved for this assignment. The practical value of the index is a precise reference to the right evidence, with access and verification handled through the responsible organization's established controls.

Connect the examination event to the relevant instrument and configuration records rather than listing whichever equipment is currently assigned to the contractor. If an instrument changed during the work, identify the affected period or result group using the actual evidence. Preserve calibration and examination-check references according to their different purposes. A current equipment-register entry does not establish the historical state of the instrument during an earlier examination. The index should direct the reviewer to the records that address that time and task.

Where native data depends on a configuration, software version or analysis reference, retain the information necessary for the site's approved retrieval and review process. Do not infer that opening a PDF demonstrates that the complete examination evidence can be recovered. The equipment tracker can organize general asset information, but it does not validate an examination setup or automatically populate this index. Use the worksheet to identify the actual evidence relationship, then keep the authoritative records in the approved system and confirm any required handoff through that process.

Give unresolved items a specific description and a link to the responsible process. Missing files, unclear identities, limited examination coverage and technical evaluation questions are different kinds of issues. Avoid one generic pending label that hides what must happen next. State the record needed, the owner of the action and the reference to the actual review or corrective process where applicable. The index can support follow-up without attempting to make the technical decision itself.

When an issue is resolved, record the actual outcome and supporting reference. A closed checkbox alone cannot show whether a file was supplied, an identity corrected or a technical question evaluated. Preserve the original relationship where the history matters. Do not remove the existence of an earlier exception merely to produce a clean final spreadsheet. The controlled process determines what records are retained and how changes are documented. The index should make the final evidence package understandable while remaining consistent with that process and its actual decisions.

Distinguish a corrected record from a separate examination event. A revised report can replace the issued presentation of one event without creating a new examination. A follow-up examination has its own event relationship even if it addresses the same component. Record the actual connection and identify which record is current for the stated purpose. Avoid treating the most recently modified computer file as authoritative simply because its timestamp is later than the others in the folder.

Preserve the references needed to understand superseded material according to the site's record controls. The index can indicate that one issue has been replaced and point to the controlling issue, while the repository manages retention and access. Do not delete source material or rewrite its dates as part of spreadsheet cleanup. Check that cross-references in summaries and handover lists reflect the reviewed revision relationships. A corrected report reference in one table is not sufficient if another part of the package still directs the recipient to an obsolete issue without explanation.

Consider a fictional package for component C-42. The index lists an examination report, a procedure revision and an equipment record. During a retrieval check, the receiver finds that the linked report concerns a follow-up event, while the procedure entry was copied from the initial examination. The files themselves are not assumed to be wrong; the index has combined references from different events. The preparer separates the event rows and compares each relationship with the actual source records through the responsible review process.

A second issue remains because one native-data reference cannot be retrieved through the agreed repository. The package is not marked complete solely because the PDF can be opened. The missing relationship is assigned to the appropriate records owner and retained as an unresolved handoff item until the actual outcome is documented. This invented example provides no plant information, inspection requirement or technical disposition. It illustrates why a small, deliberate retrieval sample can reveal defects in an index that contains all the expected column headings and appears administratively complete.

Confirm the actual delivery destination and the evidence used to acknowledge acceptance of the package. The NRC's electronic submittals information describes formal channels for submissions to the agency. Those channels are distinct from a contractor's internal document handover. The index should identify the route relevant to its actual purpose instead of assuming that uploading a file to any online service constitutes a regulatory submission. This guide does not determine whether a particular examination record must be submitted to the NRC.

Test retrieval with the intended receiving role using the approved process. Check a current report, its procedure reference, supporting evidence and an exception history rather than simply opening the first file in a folder. Record what was checked and what remains unresolved. A sender's access does not demonstrate that the recipient can retrieve the same controlled record. Where permissions or repository references need correction, resolve them with the responsible records administrator. Do not broaden access indiscriminately or create uncontrolled duplicate copies merely to make a hyperlink appear functional.

The free reporting workspace can demonstrate a supporting index layout with fictional or authorized content and generate an ordinary PDF. It is not offered as an approved nuclear QA repository, regulatory submission service or technical approval system. Before using actual project information, follow the organization's decisions about permitted tools and information handling. The downloadable CSV can also be adapted inside an approved environment, allowing the task-specific columns to support the real process without moving records into a new application.

Close the index only according to its defined purpose and the actual receiving process. Retain a clear owner for later corrections and identify the version delivered. The practical result should be a reviewer who can find the correct examination event, understand the record roles and see unresolved relationships without asking the original preparer to reconstruct the package from memory. That is the value of the workpaper: organized retrieval and transparent handoff, with technical authority, controlled retention and approval remaining in the systems and processes established for the assignment.