NDT Report Amendments: Preserve the Original and Explain the Change

Establish which record was actually issued

Identify the report number, revision, issue date and recipients before changing anything. Confirm that the file under review is the issued record rather than an earlier working copy or a later local edit. When several people have similarly named files, an apparent correction can accidentally replace the wrong version and create a new discrepancy.

Preserve the issued file and the evidence of its distribution through the organization's controlled process. Do not rely on a person's downloads folder as the only historical record. The amendment needs a stable reference to what was communicated, especially if the report has already supported another project decision or been incorporated into a larger dossier.

Record the request for correction with the person raising it and the reason. A customer question, an examiner's discovery and an internal review finding may arrive through different channels. Bring them into one traceable amendment process so the team can assess the issue without losing the original context.

Describe the discrepancy precisely

State what is wrong, where it appears and what evidence suggests a correction. Avoid vague descriptions such as report needs updating. A component identifier differs from the examination map is a clearer starting point than report incorrect, because it directs the reviewer to a specific relationship that can be checked.

Separate confirmed errors from questions still under investigation. If two records disagree, do not immediately assume which one is correct. Preserve both values and identify the source needed to resolve the conflict. Replacing one with the more convenient value can make the package look consistent while concealing an unresolved technical or identity problem.

Record the possible consequence without overstating it. An incorrect page reference may affect navigation, while a wrong component identity may affect the meaning of the result. The person receiving the issue should understand why it matters, but an initial coordinator should not make an unsupported engineering judgment about whether the examination remains valid.

Classify the change by what it affects

Use categories meaningful to the quality system, such as administrative information, component identity, examination conditions, recorded observations, interpretation or disposition. These categories help route the issue to the right reviewer. They do not replace that review, and a familiar label such as typographical should not be used to minimize an error whose consequence has not been checked.

Consider whether the correction changes only the report or also exposes a problem in supporting records. An equipment serial number copied incorrectly into the report may be resolved from an unambiguous calibration log. If the log itself is unclear, the issue is broader and may require review of the examination's traceability.

Define who can authorize each type of correction. A document controller may implement an approved administrative change, while a technical change may require an appropriately qualified reviewer. Do not let software editing permission become a substitute for technical authority. The ability to modify a PDF does not establish the right to revise its conclusion.

Review the supporting evidence before editing

Gather the relevant examination log, component map, calibration reference, native dataset, images and review notes as applicable. The purpose is to determine the correct fact and assess the effect of the discrepancy, not to assemble an indiscriminate copy of the whole project archive. Keep evidence linked to the question it resolves.

Check the dates and versions of supporting records. A newer drawing may not describe the configuration present during the original examination. A later setup file may not be the one used for the dataset under review. The evidence must support the historical event being described, not merely resemble it.

NIST's work on integrating design, manufacturing and inspection information highlights the challenge of maintaining usable relationships between lifecycle records [2]. In an amendment review, those relationships are central: the reviewer needs to know which evidence belongs to the original examination and which information was produced later to clarify it.

Determine whether the result needs technical reassessment

Ask the responsible technical reviewer whether the discrepancy affects examination validity, coverage, interpretation or disposition. The answer may be that the result remains supported, that additional analysis is needed or that a defined portion of work requires further examination. Record the reasoning and applicable authority rather than reducing the decision to an unexplained approved checkbox.

Do not infer that every report correction requires a new examination. Equally, do not assume that a correction is purely administrative because no equipment is being used at the moment. A change in component identity or acceptance basis can be technically significant even when the original data files remain unchanged.

Where the issue affects an already communicated result, follow the applicable notification and containment process. Identify who needs to know and what interim status applies. This guide does not prescribe technical acceptance rules or contractual notification periods; those decisions remain with the governing documents and responsible personnel.

Prepare the revised record with an explicit relationship

Use the document-control convention established for revisions or amended reports. Identify the earlier issue being replaced and describe the change in language appropriate to the recipient. A concise change note should make clear whether the amendment concerns identity, wording, supporting evidence or a technical conclusion. Avoid a generic updated label that requires readers to compare every page.

Preserve unchanged information accurately. Editing a report to correct one field can introduce unrelated changes through formatting, copied templates or automatic date updates. Compare the proposed replacement with the issued version and check that every difference is intended. A controlled amendment should narrow uncertainty, not create an unexplained new document.

Where the corrected record depends on revised attachments, update the attachment list and file manifest together. The National Archives' metadata guidance illustrates the importance of preserving descriptive context around electronic records [1]. For an NDT package, the practical requirement is to keep the report's identity and supporting relationships understandable within the applicable project system.

Review the final exported file

Check the version that will actually be distributed. Open the PDF or other final format and inspect page numbering, component references, units, attachments and signature or authorization fields. Confirm that the correction has not been applied only in an editable source while an older export remains attached to the outgoing message.

Review the change record against the final file. If the note says the component identifier was corrected on every relevant page, verify the header, result table, sketch and attachment list rather than checking only the cover. Repeated fields are a common place for partial corrections to remain visible.

Confirm that the authorization shown belongs to the revised issue and follows the applicable process. Do not copy a person's signature image into a new revision simply because the earlier report was signed. The responsible organization must establish how review and authorization are recorded for amended documents.

Distribute the replacement deliberately

Use the original distribution record to identify recipients who may be relying on the earlier report. Explain which issue is superseded and provide the authorized replacement through the agreed channel. If a larger dossier or downstream system contains the earlier report, identify the owner responsible for updating that location.

Record the distribution action and any acknowledgment required by the project. Sending a message, receiving it and incorporating the corrected report are different events. A sent email alone does not establish that every recipient has replaced the earlier file. Keep the status precise so unresolved handover work remains visible.

Avoid circulating unrelated personnel or customer information in the amendment explanation. Provide the facts needed to understand the correction and its effect. If detailed investigation records require restricted access, reference the controlled location and responsible owner rather than attaching the entire internal investigation to a broad distribution list.

Work through a fictional identity correction

Consider a fictional examination report whose cover names component A, while a result table names component B. The examiner's log and acquisition records consistently identify component A. The reviewer checks the source relationships and determines that the table label was copied incorrectly, with no change to the examination observations or technical evaluation.

The amendment record identifies the affected table, the evidence reviewed and the authorized correction. The replacement report receives the appropriate revision identifier, and its change note explains that the component label was corrected. The issued earlier version remains preserved with a superseded status, and the distribution record shows where the replacement was sent.

If the source records had also conflicted, that same simple correction would not have been justified. The example illustrates why classification follows evidence. It is not a rule that every identity discrepancy is administrative, nor a claim that a particular examination can remain accepted after any labeling error.

Trace the correction into dependent records

Identify the records that use the information being amended. A component reference may also appear in an asset register, a summary table, a customer database or a later report. Correcting the original PDF does not automatically correct those dependent records. Record which relationships need review and assign responsibility for communicating the change to their owners.

Use the worksheet to distinguish a direct copy of the error from a separate technical conclusion that relied on it. The first may require an administrative update; the second may require qualified reassessment. Do not infer the significance from how small the edit looks on the page. A changed identifier can alter which physical component a conclusion concerns.

Where the downstream use is unknown, document the search or notification effort and the remaining limitation. Avoid claiming that every affected record has been corrected merely because the original distribution list has been contacted. The amendment record should make clear what was checked, what was confirmed and what still requires the customer's or another owner's action.

Handle an incomplete correction request

Consider a fictional customer who asks for a report's examination date to be changed but supplies no supporting record. The reporting team does not simply replace the date to match the request. It identifies the discrepancy, checks the examination log and asks the authorized technical owner to establish which date describes the actual event.

If the available evidence cannot resolve the conflict, retain that uncertainty and obtain the appropriate review. An amendment is not a mechanism for making historical records match a preferred narrative. The corrected issue must be supported by evidence, or the record may need to explain the unresolved limitation under the applicable quality process.

Record the requester's statement separately from the review conclusion. This preserves why the question arose without treating an external request as proof of the underlying fact. The same approach applies when an internal manager requests a change: authority to request review does not establish the technical accuracy of the proposed replacement text.

Confirm replacement use without deleting the audit trail

After issuing the amendment, ask the relevant recipient to identify the replacement record through the agreed acknowledgment process where applicable. The objective is to reduce reliance on the superseded issue while preserving its controlled history. Do not instruct users to erase every trace of the original when the organization's record requirements call for retention.

Check whether document links, project indexes or handover packages still direct users to the old issue. A notification email may be missed, while a persistent index continues to present the superseded file as current. Update the controlled access route and its status information so a later user can find the replacement without knowing the correction history in advance.

Retain the relationship between the original, the amendment and the authorization record. The sequence should allow a reviewer to reconstruct what was first issued, why it changed and who authorized the new version. This is different from keeping multiple ambiguously named files in the same folder and expecting users to select the one with the newest timestamp.

Before closing the amendment, review one affected downstream record or access route as evidence that the communication process worked. The scope of that check should match the significance and reach of the change. Record any unconfirmed recipients or unresolved dependencies explicitly so closure of the report-editing task is not mistaken for closure of every consequence of the discrepancy.

Learn from the cause without rewriting the history

After closure, identify whether the error arose from an ambiguous source, manual transcription, a template field or a missing review step. Choose a proportionate improvement tied to that cause. Adding another signature box may do little if the underlying problem is that two systems use different component identifiers without a controlled mapping.

Test the improvement on a representative report. For example, check whether a revised review checklist now catches inconsistent component labels across headers, tables and attachments. Record what was changed and what evidence supports the improvement. Do not claim a reduced error rate unless there is a defined comparison and enough reliable data to support it.

Keep the amendment process distinct from the examination procedure itself, while linking the relevant reporting controls. NDT Connect's procedure writer can help prepare a review draft, but it does not authorize corrections to issued customer reports. The useful final state is a technically justified replacement, a preserved history and a clear record of who reviewed and received the change.