Used NDT Instrument Checklist: Options, Support and Evidence
A used NDT instrument can be a practical purchase when its actual configuration, support and record workflow fit the intended task. Assess the specific unit and its complete evidence package, rather than relying on a familiar model name or a calibration sticker.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Define the job the candidate must support
Write a short requirement for the intended application before reviewing listings. Identify the necessary instrument functions, probes or accessories, record output and technical acceptance process. A low asking price is difficult to evaluate without knowing what the organization must add or verify to make the package useful. The requirement should be specific enough to reject an unsuitable candidate even if its condition appears attractive.
Separate essential capability from optional convenience. The technical owner determines the inspection requirements, while purchasing identifies the equipment and evidence needed to support them. This guide does not authorize operation, select inspection settings or provide financial or legal conclusions about a transaction. It offers a practical evidence checklist so the organization can make a documented purchasing decision and identify unresolved questions before depending on the instrument for customer work.
Establish the exact physical identity
Request clear evidence of the manufacturer, full model designation, serial number and relevant hardware revision. Compare the listing, nameplate, configuration screen and supplied documents. A product-family name may cover several generations with different capabilities and support arrangements. Do not assume that a familiar case design establishes the internal configuration or that a photograph of another unit represents the candidate being sold.
Record unexplained differences and ask the seller or manufacturer to resolve them. If a serial label is unreadable, duplicated across documents or inconsistent with the offered configuration, keep the identity issue open. The purchasing file should identify the actual unit to which the offer and evidence relate. This is basic reconciliation, not an accusation about the seller. Clear identity is necessary for later service inquiries, option verification and an accurate receiving record.
Verify installed options rather than advertised family capability
Ask for evidence of the functions enabled on the specific unit. Product literature may describe features available somewhere in a family without establishing that this instrument includes them. Evident's BondMaster manual, for example, distinguishes model capabilities and describes purchased upgrades. Use that as a reminder to verify the actual configuration, not as an assumption about every brand's licensing design.
Have the technical owner identify which options are essential to the intended application. Request a supported demonstration or manufacturer confirmation of those options for the candidate. Keep proposed upgrades separate and obtain current availability and scope before including them in the business case. A feature that could once be purchased is not necessarily available now. The final decision should distinguish delivered functionality, confirmed additions and unsupported expectations.
Check the relevant support lifecycle
Consult the manufacturer's current lifecycle information for the exact model and revision. Eddyfi's discontinued-product table separates several lifecycle milestones and links official customer letters. A device being unavailable for new sale is not the same statement as a particular service function ending. Read the applicable product information and obtain a current response when the candidate's scope is unclear.
Record the date and substance of the support inquiry. Ask about the services the organization actually needs, such as repair, calibration, replacement components and software maintenance. Do not assume that a newer instrument with the same family name extends support to every older hardware revision. The purchasing decision can accept a limited-support item for a defined role, but that limitation should be deliberate and visible to the people who will schedule and maintain it.
Distinguish general policy from product-specific confirmation
Eddyfi's end-of-life policy links a document explaining changes in support as products move through their lifecycle, while noting that product circumstances can vary. A general policy is useful background. The buyer still needs the current answer for the exact candidate and required service. Avoid converting a broad policy interval into a guaranteed remaining service life for a used unit.
Preserve any product-specific letter or supplier response with the purchase record. If service depends on parts availability or another condition, record that qualification. Do not summarize a conditional answer as fully supported. The relevant question is whether the organization can sustain the intended role for its planned period of use. That assessment should include the consequences of an unavailable repair or required software function, rather than relying only on whether the instrument currently turns on.
Request calibration evidence with its full scope
Obtain the complete available certificate and reconcile its identity with the instrument. Review what was evaluated, the date, results and any stated limitations with the technical owner. A sticker or a photograph of the certificate cover does not establish the full evidence. A recent date also does not answer whether the documented scope meets the intended measurement need.
NIST's traceability policy distinguishes traceability from fitness for a particular purpose. Use that principle when evaluating broad seller language such as NIST traceable or fully calibrated. Ask what evidence supports the claim and have the responsible owner decide suitability. The purchase review should also consider relevant events after the certificate, such as repair, storage or damage, without assuming that a past certificate guarantees the unit's present condition.
Separate service history from cosmetic condition
Request the available repair and service history, including known modifications and component replacements. A clean enclosure may be welcome, but it does not explain the condition of connectors, installed functions or the measurement path. Conversely, cosmetic wear alone does not establish that an otherwise documented unit is technically unsuitable. The appropriate review should consider the evidence relevant to the intended role.
Record which history is known, which is seller-reported and which is unavailable. Do not fill gaps with an invented clean history. If the organization requires an independent evaluation before acceptance, define its scope and commercial arrangements with the responsible parties. The technical owner determines what examination or verification is appropriate. Purchasing coordinates the evidence and disposition so the decision does not rest on a vague statement that the instrument was working when last used.
Reconcile the complete accessory package
List probes, wedges, cables, chargers, batteries, adapters, reference items and other application dependencies included in the offer. Identify relevant models and serial numbers where applicable. A carrying case with several unlisted accessories can look complete while missing the one cable or probe needed for the intended task. Compare the actual package with the original requirement and the supported configuration.
Ask which accessories have their own documentation or service needs. Do not assume that a certificate for the instrument covers every item in the case. Keep unsupported substitutions visible and obtain technical review where necessary. The buyer should price and confirm missing essential items before treating the offer as a ready package. This avoids a purchase whose apparent saving disappears because a critical obsolete accessory cannot be obtained or supported.
Confirm software and account access explicitly
Identify the software, licenses, option entitlements and account relationships needed for acquisition, analysis and retained-file access. Ask the seller and relevant supplier what can be transferred and what the purchaser must obtain separately. Do not assume that software installed on a supplied computer automatically grants the new owner all required rights or continuing support. Preserve the written response and the applicable commercial terms.
Distinguish instrument-enabled functions from workstation licenses and cloud services. A hardware sale may leave those components with different transfer or renewal requirements. The buyer should not use another organization's account as an informal substitute for an agreed transfer. Define the supported ownership and access arrangement before acceptance. This is a request for clear terms, not a universal statement that transfers are prohibited or permitted for every vendor and product.
Demonstrate the required record workflow
Use approved nonproduction data to test the actual candidate and proposed review environment. Ask the technical owner to define the needed demonstration. Follow a fictional job through identity entry, saved data, review and the required export. A power-on video or a screenshot of a response does not establish that the organization can produce and retain its intended customer record.
Open the exported package on the receiving system the organization plans to use. Confirm the required metadata, units and analysis access. Record the instrument firmware and software versions involved. If the demonstration relies on a seller-owned license or computer that is not included, identify the dependency. The purchase should deliver a supported record path, not merely an instrument that once worked within someone else's undocumented combination of software and accessories.
Handle previous-owner data through an agreed process
A used instrument or bundled computer may contain records belonging to its prior owner. Agree who is responsible for retaining, removing or transferring those records under the applicable organizational rules and permissions. Do not inspect or reuse unrelated customer files simply because they remain on the device. The purchase trial should use approved test data that the parties are entitled to share.
Obtain a documented handover state for the equipment and necessary configuration information. Distinguish removal of prior customer records from preservation of legitimate instrument configuration or service evidence. A reset may affect useful settings or access, so follow the supplier-supported process and the parties' agreement. The buyer should receive a usable, appropriately prepared package without depending on unauthorized access to the previous owner's data or credentials.
Define inspection and return conditions before relying on them
Clarify what opportunity the purchaser has to inspect the actual unit, what evidence will be supplied and how a material mismatch will be addressed. Keep the agreed terms in the purchasing record. Do not assume that a listing's broad condition label includes an application trial or that a general return statement covers every technical concern. The responsible purchasing owner should resolve the commercial scope with the seller.
Use the requirement list to define the concrete items to verify. This makes the review fair to both parties: the seller knows what was represented, and the buyer knows what evidence is needed. Avoid adding new essential requirements after acceptance that were never part of the agreed evaluation. If the intended application changes, treat that as a new requirement and obtain the necessary technical and commercial review rather than recasting it as a defect in the original offer.
Work through a fictional supported-model assumption
A hypothetical inspection business finds a used instrument whose family is still prominent in online product material. The candidate's hardware revision is older than the units shown on the current product page. Before purchase, the coordinator asks the manufacturer about calibration, repair and software access for that exact revision. The response identifies a service limitation that was not apparent from the family name alone.
The team considers whether the restricted support fits a narrowly defined role and whether another candidate better meets its planned work. It also checks the required option and sample-file access. This fictional example does not imply that all older instruments are unsuitable. It shows why lifecycle, installed capability and record access are separate questions. A unit can function today while presenting a different continuity obligation from a newer configuration with the same familiar branding.
Compare total readiness under explicit assumptions
Build a readiness worksheet that includes the purchase, confirmed missing accessories, required evaluation, software access and support arrangements. Use actual quoted or internally established information and label unresolved costs. Do not present a universal discount percentage or break-even formula for used equipment. The meaningful comparison depends on the organization's required service and the evidence available for each candidate.
Include time as a planning dependency. An instrument awaiting a scarce probe or an unresolved license transfer may not be available for a scheduled project even if the physical unit ships quickly. Assign owners to open items and distinguish a promising candidate from a ready asset. The purchase decision should explain which requirements are satisfied, which are conditional and which remain unacceptable for the intended role. That is more useful than reducing the comparison to asking price alone.
Use the evidence-review worksheet to close gaps
The downloadable worksheet records candidate identity, installed-option evidence, service response, software-rights response, calibration review, export trial, missing items, decision owner and disposition. Its sample is fictional. Replace it with the actual evidence references for each candidate. It is a generic purchasing aid and is not a NDT Connect import format or a certificate of technical suitability.
Keep original documents in the controlled purchasing file and use the worksheet as an index. Mark an item resolved only when the responsible owner has accepted the evidence. A seller statement, manufacturer confirmation and completed local trial are different evidence types; preserve that distinction. If the organization elects to accept a limitation, record the bounded role and decision rather than quietly deleting the open issue from the comparison.
Introduce the accepted unit as a new asset relationship
At receipt, reconcile the actual identity, accessories and evidence against the accepted candidate record. Record shipping damage or unexplained differences through the agreed process. The technical owner determines the required acceptance before use. Do not copy the seller's availability status into the organization's own record as though the two decisions were identical.
Create the equipment record with the actual name, type, serial number, manufacturer, model, due date, status and useful notes. NDT Connect supports those administrative fields; it does not verify ownership, transfer software rights, test installed options or approve technical readiness. Keep the accepted application and evidence in the controlled file. The completed purchase should leave a specific, understandable asset with a supported role and a clear history of how the organization accepted its limitations and capabilities.
Frequently Asked Questions
Does a current calibration sticker make a used instrument ready for our work?
No. Review the complete certificate, actual configuration, condition, required accessories and application acceptance evidence.
Does a current product-family page prove support for an older hardware revision?
No. Obtain current lifecycle and service information for the exact model and revision.
Can installed software be assumed to transfer with the hardware?
No. Confirm the applicable rights, account arrangements and required access with the seller and supplier before relying on them.
References & Standards Cited
- Eddyfi: discontinued products and service lifecycle information View source ↗
- Eddyfi: end-of-life policy and linked August 2023 policy document View source ↗
- Evident: BondMaster 600 model and option documentation, September 2022 View source ↗
- NIST Policy on Metrological Traceability View source ↗
Related on NDT Connect
Join NDT Connect — free
The free marketplace for the NDT industry — connect inspectors and the companies that need them.
Free to join · Compare provider qualifications and confirm availability directly · Browse providers
By NDT Connect Editorial · Updated
Source-based editorial guidance. Read our editorial policy and disclosures.