Record an Instrument Swap During an NDT Assignment

An instrument may be replaced because it fails, becomes unavailable, needs a different capability, or must leave the site for another assignment. Whatever the reason, the inspection record now involves two equipment identities. The practical challenge is to show which work was performed with each setup and what was reviewed before the replacement was used. Simply changing the serial number in a report header can erase that distinction.

Start a short swap record when the change is proposed. Identify the original instrument, replacement instrument, reason, time or acquisition boundary, and person coordinating the handover. This is an administrative framework for the project’s technical process, not a substitute for it. The scope of checks, any decision about earlier results, and permission to resume examination must come from the applicable procedure and responsible personnel rather than from the inventory tool.

Before equipment is removed or data are reorganized, identify the last result confidently associated with the original setup. A component number, scan file, weld identifier, or recorded examination sequence may provide a better boundary than a rounded clock time. If there is uncertainty about a group of results, identify that group explicitly. Do not assign a convenient boundary merely because it makes the final table easier to format.

Keep the source record that supports the boundary, such as the field log or acquisition file reference. Record any restart, repeated area, or incomplete scan separately from completed work. This prevents a replacement operator from assuming that the next sequential item was untouched. The handover should make the state of the work visible: completed with identified evidence, partially completed, repeated for a stated reason, or awaiting a responsible decision.

A planned rotation between two suitable instruments raises different questions from an unexpected fault discovered after data collection. Use a factual description of the trigger. “Replacement arranged after display stopped responding” is more useful than “old unit bad,” because it does not claim a technical effect that has not been assessed. Keep any observations, messages, or checks available to the responsible reviewer.

Avoid turning the equipment record into a fault investigation report. The tracker can record status and notes, while the project’s controlled record holds detailed evidence and disposition. If the reason may affect earlier measurements, clearly flag that question and identify the potentially affected period. A successful examination with the replacement instrument does not by itself establish that results from the original unit were satisfactory. That earlier-work question needs its own documented answer.

A matching manufacturer and model can simplify logistics, but does not establish that the replacement is suitable for every planned function. Compare the actual examination requirements with the proposed unit’s configuration, available accessories, software or firmware where relevant, and evidence required by the project. Ask the responsible reviewer to resolve differences before treating the replacement as interchangeable. Record the review reference without inventing universal acceptance checks.

NIST explains traceability in relation to measurement results, which is one reason an instrument label alone is an incomplete evidence description. Retain the replacement’s applicable calibration documentation and the project-specific checks required for use. The administrative record should identify what was reviewed and by whom. It should not translate the presence of a certificate into a blanket statement that every function, range, or technique is approved.

Create or locate the replacement’s own entry in the free Equipment Tracker. The tool stores entered equipment identity, dates, status, certificate reference, and notes. Do not overwrite the original unit’s serial number with the replacement serial merely to reuse an existing row. That would confuse the two histories and could leave future reminders attached to the wrong physical asset.

Update the original unit’s status according to the actual situation and your responsible process. An unavailable unit is not automatically retired; a unit being evaluated is not necessarily ready for service. The available status field is a planning description, not an enforced dispatch lock. Add concise cross-references to the swap record where useful, while retaining the detailed acquisition and technical disposition in the project documentation.

The instrument body may be only one part of the examination setup. Determine whether accessories and settings are transferred, replaced, or independently configured. A handover that records two instrument serials but loses the probe or reference-block relationship can leave the report ambiguous. Use the project’s equipment identification conventions so the replacement setup can be reconstructed from the record without relying on the operator’s memory.

Do not assume that a saved setup file can be moved between units without review. Identify the configuration source and the checks required by the applicable procedure. If a setting changes, record the reason and its relationship to the affected work. This guide does not prescribe technical tolerances or an examination method; it provides a place to retain the actual decisions and references that the qualified project team determines are necessary.

In a fictional US fabrication assignment, an inspector completes a defined group of weld records with Unit A. Before starting the next group, the unit becomes unavailable and Unit B is proposed. The coordinator records the final completed weld identifier and confirms that one additional weld was started but not completed. The handover therefore distinguishes completed records, the partial item, and the remaining untouched group.

The responsible reviewer evaluates Unit B and the required setup checks under the project procedure. The partial item receives a specific disposition rather than being silently counted twice or treated as complete. The report keeps Unit A associated with the first group and Unit B with the later group. These fictional decisions show the structure of a traceable swap; they do not establish that any particular replacement or repeated examination is technically sufficient.

Choose a result-table arrangement that makes the equipment relationship clear. One option is a setup-reference column with a short identifier linked to an equipment summary. Another is separate tables for distinct acquisition groups, each with an explicit setup description. The best choice depends on the existing client format and how readers will use the report. Avoid making a single broad header carry a distinction that applies differently to individual rows.

Digital NDT Reporting allows editable tables and equipment text, but it does not infer which instrument produced an imported result. Enter or verify the association yourself. If an existing spreadsheet already contains setup identifiers, preserve their meaning during import and compare the resulting rows with the source. Adding a new instrument name to the report does not automatically remap old rows or confirm that every affected file has been included.

Sometimes a row summarizes several readings collected before and after the swap. Identify whether the reporting format permits a combined row and what supporting references are necessary. Do not choose one instrument arbitrarily to avoid adding detail. The responsible reviewer may require separate entries, a clear explanation, or further examination. The record should show the actual disposition rather than hiding the mixed acquisition history behind a generic equipment list.

If a boundary cannot be reconstructed confidently, describe the limited set of uncertain records and the evidence reviewed. Avoid expanding that uncertainty to unrelated work or minimizing it without support. A targeted query allows the reviewer to make a proportionate decision. Keep the unresolved status visible in the working report until the project process has addressed it; a polished PDF should not make an unfinished evidence question appear resolved.

An instrument swap may lead to repeat examinations, but the replacement itself is not the reason to merge or discard results automatically. Record why the repeat was performed, which original record it relates to, and how the resulting evidence was evaluated. A later result may have a different acquisition date or setup, and that distinction matters even if the numerical values happen to agree.

Use consistent component identifiers so repeat work can be connected without renaming the component as though it were new. Retain superseded or supporting information according to the project’s record process. In the final report, make the selected result and any necessary explanation clear. The inventory tracker cannot determine which measurement should govern, and a software table edit is not a technical disposition of contradictory or questionable findings.

The replacement may have a different entered calibration due date and a different person responsible for arranging future service. Check its own equipment record and reminder configuration instead of assuming the original unit’s alert covers both. A planned project extension can bring the replacement’s due date into the assignment even when the original unit would have remained within the planned interval. Review the actual dates before mobilization or continued deployment.

Calibration reminders are separate account records associated with an owned equipment entry. They do not transfer automatically because a report now names another instrument, and they do not establish suitability for continued use. Keep the original alert or modify it according to the unit’s actual disposition. A unit sent for service may still require follow-up, while the replacement needs its own planning review rather than inheriting an unrelated date.

If the swap occurs near a shift change, record which setup the next operator will receive and the state of the partially completed work. Include the latest controlled configuration reference, the last confirmed acquisition point, the outstanding question, and the person responsible for release. A verbal statement that “the new unit is ready” can mean different things to the scheduler, operator, and reviewer.

Ask the incoming operator to reconcile the physical equipment identifiers with the handover record through the established site process. This is a chance to catch a case-label mix-up or an accessory left with the original unit. Do not rely on the reporting tool to notify the next shift; it does not provide a shared dispatch or crew acknowledgement system. The project’s communication process remains necessary to turn the recorded information into an operational handoff.

When the replacement is borrowed or rented, plan the data handover before its return. Identify the project files that must be retained, the authorized storage destination, and the person who will confirm that the retained copy is usable. The return deadline can otherwise become the moment when someone discovers that the only acquisition file is still on the instrument. Record the transfer through the project process rather than assuming the report PDF contains all required source evidence.

Check the retained file references against the result groups associated with the replacement. Follow the owner’s and project’s instructions for removing or retaining data on the returned unit; do not make an unsupported promise about secure deletion. Keep the administrative return record separate from the technical disposition of the inspection. Returning the physical instrument closes a logistics action, while evidence retention and report review may still need a named owner and completion reference.

The original unit may return after repair or calibration while the report is still being prepared. Its current equipment status should not change the historical statement about which unit performed earlier work. Likewise, a new certificate issued after the assignment should not silently replace the reference associated with the original acquisition period. Keep current planning information distinct from the evidence cited for completed examination.

If later findings raise questions about the original period, identify affected reports and refer them for the appropriate assessment. Record the resulting decision and any required report revision. An issued report in Digital NDT Reporting is locked; a new draft revision provides a way to prepare a controlled correction while retaining the report number. The software does not decide whether a revision is needed or what the technical conclusion should be.

Before distribution, examine the report as a reader will see it. Confirm that every setup identifier used in a table is explained, both instrument identities remain readable, and the acquisition boundary is understandable without the working spreadsheet. Check page breaks where a table continues so an equipment note is not visually separated from the rows it qualifies. The report should remain coherent even when printed or reviewed outside the editing session.

Compare the exported PDF with a small set of representative source records: one before the swap, the partial or repeated item, and one after the swap. This is a focused administrative reconciliation, not a replacement for technical report review. It helps detect accidental row remapping, a header copied from the original setup, or a missing explanation that was present in notes but never reached the deliverable.

A complete closeout identifies the replacement review, the acquisition mapping, the disposition of incomplete or questioned work, and the inventory updates for both instruments. These can be different decisions made at different times. Do not mark the entire swap complete merely because Unit B arrived on site. The last unresolved item may concern a historical result or the original unit’s return-to-service review rather than the replacement’s availability.

Use the worksheet below to keep those threads connected without merging them. Preserve the reference in the project file and a concise locator in relevant equipment notes. At the next similar event, the team should be able to see how the earlier boundary was established and which evidence supported it. The benefit is a report that accurately describes the work performed, even when the equipment plan changed halfway through the assignment.