Track Repair and Retest Cycles in NDT Records

Start the register with the original examination event and preserve its result as recorded through the applicable review process. Add repair and follow-up events as separate linked records. Replacing the original result with the latest outcome can hide why the repair occurred and what evidence supports the current state. A cycle register makes that sequence visible without requiring every report to repeat the full technical narrative. Each event should point to its source record and identify the physical component or zone to which it applies.

This is different from correcting an error in a report. A repair changes the physical item or its condition; a document correction may change only the written record. Sometimes both occur, but they should remain distinguishable. The report amendment guide covers controlled document changes. Use the cycle register to explain the examination and repair history itself. A new report revision should not be used as the only evidence that an additional physical intervention or examination event took place.

Identify the component, joint and relevant repair location using the project’s established convention. A repair designation such as R1 is not enough by itself when several areas or components use the same label. Connect it to the original examination reference and the repair record. If the repair affects only part of a larger examined area, preserve that boundary. Do not imply that an examination of the repaired zone covers the entire component unless the actual performed scope and applicable requirements establish that coverage.

A drawing or location map can change during the repair process. Retain the relationship between the original reference and any later identifier. Where material is removed or a section replaced, determine through the responsible process whether the old and new records describe the same physical feature, a modified feature or a replacement item. The reporting team should not decide that relationship from a convenient filename. An accurate location history prevents a follow-up result from being attached to the wrong repair or original indication.

An examination report describes evidence and its evaluation within the stated scope. It does not necessarily authorize a particular repair. Reference the actual repair disposition, instruction or other controlled decision that applies. Identify its relationship to the examination finding without inventing the engineering basis or authority. A report preparer should not turn a note saying refer for repair assessment into a definitive repair instruction. Keep the decision path clear so a later reviewer can distinguish observed condition, technical evaluation and authorized physical work.

TWI’s repair procedure development discussion describes repair planning as involving material, process and service considerations. The practical implication is that the repair basis is a separate technical input, not an automatic consequence of a report label. This guide does not prescribe a repair method, welding sequence or acceptance threshold. It provides a way to record the real decision and connect it with the work that was subsequently performed and examined.

Agree how the register distinguishes the original examination, first repair, first follow-up and any later cycle. The labels should identify sequence without implying a universal industry convention. Different clients may use R1 to mean a repair number, a report revision or a retest event. State the local meaning explicitly. Keep document revision in a separate field from physical repair cycle. That separation prevents a report edited twice for formatting from appearing to document two additional repairs.

Where several repair areas are handled independently, use a structure that preserves their separate histories. One area may complete a follow-up while another remains under repair. A component-wide cycle number alone can obscure that difference. Record the zone relationship and current state at the level needed for decisions. Do not create artificial cycles merely to make all rows share the same number. The register should reflect the actual sequence of authorized work, including parallel or partially completed events where they occurred.

An examination performed during excavation, after a repair operation or after another process step may address a different question. Record the actual process state and applicable examination instruction. Do not combine these events under one generic retested label. The technical requirements determine what examinations are needed and when; the register preserves the evidence that the required sequence was followed or identifies where the record is incomplete. It should not invent a universal requirement to apply the same method at every stage.

If the source does not clearly establish the examination stage, seek clarification before assigning the result to a particular part of the repair sequence. A date may show that work occurred after another event without proving the physical condition at the time. Reference the work record or other evidence that establishes the state. This is particularly useful when several teams perform different steps and the final report compiler did not observe the repair operation directly.

Record the method, applicable procedure and evaluation basis for each examination event as required by the project. A follow-up may use an authorized different technique or a changed instruction. Do not assume that the original report’s references automatically apply to every later event. Where the same basis remains valid, the register can reference it concisely. Where it changes, preserve the reason and the effective event boundary so the recipient can understand which requirements were used to interpret each result.

A method change does not make two results directly comparable in every respect. The responsible technical reviewer must assess the significance of differences in coverage, sensitivity, geometry or evaluation approach. The register should make those differences visible rather than presenting a simple improvement trend from unlike evidence. A satisfactory outcome under a stated follow-up scope is a supported event result; it is not a universal declaration that every earlier concern or every part of the component has been resolved.

Include the relevant earlier report and repair references in the follow-up record. JPL’s QC14b NDI/NDT certificate clause explicitly includes previous report references for applicable repair or rework in that procurement context. This is a concrete example of why the relationship matters, not a requirement that automatically applies to every customer. Follow the actual contract and technical instructions for your project while preserving enough linkage to understand the examination sequence.

Check that the predecessor reference points to the correct event and version. A later amendment to the original report may clarify a location without changing the physical history. The cycle register should retain the relevant relationship rather than linking blindly to whichever PDF has the highest revision number. If several reports cover different methods or zones, identify which one prompted or supports the follow-up. A broad reference to previous reports can leave the reviewer unable to determine which evidence was actually considered.

Consider a fictional joint J-44 with two separately identified repair areas, A and B. The original examination is event E0. Repair record RA1 addresses area A and RB1 addresses area B. Follow-up event EA1 records the reviewed result for A, while examination of B cannot yet proceed because a required process step remains incomplete. The coordinator keeps the two area histories separate. The report does not describe the whole joint as retested merely because one area now has a completed follow-up record.

Later, event EB1 documents the follow-up for B under its applicable instruction. The register links each area to the original event, its repair record and its own follow-up evidence. If another intervention is required on A, that becomes a new area-specific event rather than overwriting EA1. This example is hypothetical and establishes no required repair method, waiting period or examination sequence. It demonstrates how separate location histories prevent a partly resolved component from being reported as uniformly complete.

A repeated examination may occur because the original data was incomplete, a setup required correction or a review requested additional coverage. That is not necessarily a repair cycle. Record the actual reason for the repeat and whether the physical item changed. Otherwise a register may falsely suggest that material was repaired several times when the team only repeated data acquisition. Conversely, a physical repair should not be hidden under a generic recheck label that leaves the intervention undocumented.

Keep the technical assessment of the original data with the responsible review process. If the earlier event was invalidated or limited, reference that decision and preserve the source history appropriately. Do not delete it merely because a later acquisition was more useful. A recipient may need to understand why the first result was replaced, supplemented or retained with a limitation. The event chain should explain that relationship clearly without requiring the reader to infer it from timestamps and similar filenames.

If an area undergoes another repair, retain the additional decision, intervention and examination references. The applicable engineering, customer and code requirements determine any restrictions or approvals. This worksheet does not establish an allowable number of repair cycles. Avoid importing a familiar limit from another project or material into the current record. The register’s job is to make the actual sequence visible so the responsible people can assess it against the requirements that truly apply.

Repeated activity can reveal an unresolved process question, but the reporting team should not diagnose the cause from cycle count alone. Record relevant evidence and refer the question to the appropriate technical process. Distinguish a new condition, an incomplete prior repair and a revised interpretation when the authorized evidence supports those descriptions. If the reason remains unknown, preserve that uncertainty. A precise count of interventions is useful; an unsupported explanation of why they occurred can mislead later decisions.

Different examination events may use different personnel or equipment. Record those relationships at the level required by the project rather than copying the original report header into every follow-up. The equipment tracker can organize the relevant asset records, but it does not validate an examination setup or determine equipment fitness. Reference the actual supporting records for the event. Where an equipment change affects technical comparability, identify that issue for the responsible reviewer instead of assuming it is merely administrative.

Similarly, distinguish the person who performed the examination from the person who compiled the cycle summary. A coordinator may assemble several reports without being the examiner or technical approver for each one. Preserve source authorship and the actual review references. The register can be concise while still making those responsibilities traceable. Do not add a signature or approval representation for someone who has not provided it through the organization’s applicable process.

A customer often needs a short statement of what remains open. Derive that summary from the event chain and the responsible technical dispositions. Identify the relevant component areas, latest supported states and unresolved actions. Do not assume that the latest date alone establishes the current controlling result. An event may cover only one zone or may remain under review. The summary should state the scope of its conclusion and point to the records that support it.

Use the free digital reporting tool to prepare the examination table and cycle references. It supports editable report content and PDF export, not automatic interpretation of repair histories. The procedure draft tool can help organize proposed event-recording responsibilities for review. Neither tool decides whether a repair is acceptable or authorizes return to service. The organization must supply the applicable technical decisions and distribute the resulting records through its actual process.

An NDT provider may examine a repaired item without having performed or witnessed the repair. Attribute the repair record to its actual source and distinguish supplied information from direct observation. A statement that the item was presented as repaired should not become a claim that the examiner verified every repair operation. Record the relevant work-package reference and any required confirmation through the project’s process. This keeps the examination report useful while preserving the boundary between the provider’s performed work and information supplied by the fabricator or owner.

If the supplied repair record does not identify the area clearly, resolve that gap before assuming it matches the original finding. A repair completion date and a component number may not distinguish several interventions on the same item. Request the location and event relationship needed for the follow-up record. Where that information remains unavailable, report the limitation accurately and obtain the responsible technical direction. The register should not fill a missing repair history with a reconstructed sequence that nobody can substantiate from the actual work records.

Before delivery, select a component with more than one intervention and trace it from the original report through the final summary. Confirm that the repair references, area identities and follow-up events remain distinguishable. Check for accidental merging caused by identical local repair numbers or repeated component names. A combined table may need separate event and area columns to stay clear. The report buyer-review guide offers broader completeness checks; this review specifically protects the sequence that explains the current state.

Retain the completed worksheet with the appropriate supporting package. It should allow a future user to identify what changed physically, what was examined afterward and which evidence supports the latest stated outcome. If an event remains pending, record the next responsible action rather than filling the result with a presumed satisfactory value. An honest cycle register is useful precisely because it preserves unfinished work and earlier evidence alongside the current result, without forcing the entire history into one overwritten status cell.