NDT Credential Verification: Read Issuer Directory Results

Identify the claim before choosing a directory

Write down the credential claim exactly as supplied: issuer, program, person, method or scope, identifier, and relevant date. A directory search cannot be meaningful if the claim itself is ambiguous. A document mentioning a standard or recommended practice may have been issued by an employer rather than the organization whose name appears in the reference.

Ask for clarification where the issuer is unclear. A course provider, employer, and certification body can each issue documents with different purposes. Do not search one organization's registry and conclude that every document absent from it is invalid. The first task is to establish which authority is being claimed.

ASNT's FAQ identifies its certificate-holder directory as a route to checking its certifications [1]. AWS and API maintain their own verification tools [2][3]. These sources cover their respective programs; none should be treated as a universal registry of every NDT training, employer certification, or inspection qualification record.

Navigate from an official source

Use the issuer's official website or a verified link from it to reach the search service. A screenshot in a proposal or a link embedded in an unfamiliar message can be a starting point, but it should not replace checking the source. Record the actual service used and the date of the search.

Be careful with look-alike organization names and unrelated uses of familiar acronyms. The identity of the issuing body matters more than whether the page design looks professional. If a domain or service changes, follow the issuer's current navigation rather than assuming an old saved link remains authoritative.

Do not provide account credentials to a third-party page merely to verify another person's public credential claim. If a service requires a specific authorized process, follow that process. Keep private account access, public lookup, and employer evidence review as separate activities with different information needs.

Use the fields the service actually supports

Follow the instructions of the selected tool. AWS's verification page asks for a certification number and last name [2]. API's service allows selection of the program and searching by name or certification identifier [3]. ASNT provides its own directory route [1]. Do not assume that search behavior is identical across these systems.

Copy identifiers carefully from the source, retaining leading zeros or other meaningful characters where applicable. Check whether spaces, punctuation, or a name variation could explain a missing result. Avoid repeatedly altering several search fields at once; make one controlled change so you can understand why a result appeared.

Use the minimum information needed for the lookup. A public directory search should not require circulating an entire personnel file among colleagues. If identity confirmation needs additional evidence, route that through the organization's approved process rather than attaching sensitive personal material to a routine search note.

Match the result to the right person

A matching name is useful but may not be sufficient. Compare the credential identifier and program with the supplied evidence, and examine other relevant fields the source provides. Two people can share a surname, and a person may use different name formats over time. Preserve uncertainty until the match is supported.

If a name has changed, ask for the issuer's correction or linking evidence through the appropriate process. Do not assume that similar names represent the same person, and do not expose identity documents unnecessarily in a general qualification matrix. A controlled identity check can support the match without publishing the underlying sensitive material.

Record the matching basis in a concise note. Identifier and program matched to supplied credential is clearer than verified online. The note should tell another reviewer what was compared, not simply announce a favorable conclusion without the evidence needed to understand it.

Read the returned program and scope

Confirm that the result covers the program actually claimed. A person may hold one credential with an issuer while a proposal claims another. A successful search for the person's name does not establish every qualification listed in the proposal. Compare each material claim with the specific result that supports it.

Read method, level, scope, and date fields as displayed. Do not expand a listed method into every technique or application. If the directory provides only a limited summary, obtain the relevant credential document or issuer clarification for questions the summary cannot answer. The absence of a field is not evidence that no restriction exists.

Keep the credential fact separate from project suitability. A valid directory match can support the existence of a credential while leaving employer certification, customer acceptance, or assignment-specific scope questions unresolved. Record those as separate reviews so the online lookup does not silently close the entire personnel assessment.

Record a dated observation rather than permanent approval

A verification note should identify the search date, source, search inputs appropriate to retain, matched result, and reviewer. If a screenshot or PDF is retained under your process, label it as a dated observation. It captures what was displayed then; it is not a continuously updated statement of status.

Choose when to repeat a check based on the actual review process and changes in the record. A renewal, correction, disputed date, or new assignment may justify a fresh lookup. This guide does not establish a universal recheck interval. The responsible organization should define a proportionate process for its work.

Avoid placing the word verified on a profile without explaining what was verified and when. Account ownership, business contact information, and issuer credential status are different checks. A broad badge can create more certainty in the reader's mind than the underlying review supports.

Handle a missing result neutrally

First check that the correct issuer and program were selected and that the identifier and name were entered accurately. Review the source instructions for supported search variations. If the result remains absent, record no matching result found using the stated inputs rather than declaring the person unqualified or the document fraudulent.

Ask the credential holder or issuer for clarification through an appropriate route. The issue may involve a name change, a recently updated record, a program not covered by that directory, or another condition that the issuer can explain. Do not speculate about the cause while presenting the speculation as a finding.

Keep the review open where the missing result affects a required claim. Neutral language does not mean ignoring the gap. The responsible employer or buyer still needs to decide what evidence is necessary before relying on the credential for the intended purpose.

Resolve a conflicting expiry or status

If the directory and supplied document disagree, preserve both observations and identify the exact field in conflict. Do not automatically choose the later date or the source that best supports the preferred outcome. Ask the issuer for the current authoritative explanation and record the response.

API's verification page directs questions about an expiry to its program staff [3]. Use that issuer-specific route when applicable rather than applying another body's rules about renewal timing or special periods. Similar terminology across programs does not establish identical status conditions.

Until the issue is resolved, keep the operational summary honest. It can show date discrepancy under review and identify the decision owner. The certificate manager should not contain an invented compromise date intended to keep reminders quiet or make a proposal look complete.

Work through a fictional buyer review

Imagine a fictional buyer reviewing a proposed inspection team. One person's supplied credential matches the official issuer result in identifier, program, and date. A second person's result appears under a different name format but with a matching identifier. A third person's claimed employer record is not a credential issued by the directory operator.

The buyer records the first match, routes the second identity detail for clarification, and asks the supplier for the appropriate employer evidence for the third. The buyer does not label all three people verified merely because some names were found, nor reject the third solely because an unrelated registry does not list the employer's record.

After clarification, the buyer completes the separate project-scope review using the applicable requirements. The directory checks remain useful evidence within that review, but they do not replace the other decisions. This keeps a simple online lookup from becoming an unsupported statement about the whole team.

Keep verification efficient and respectful

Use a standard short review note and a defined escalation route. That makes checks consistent without turning them into an investigation of unrelated personal history. Focus on the credential claim and the information necessary to assess it. Avoid collecting sensitive details simply because they might be available online.

If a discrepancy is resolved, update the active record and retain the explanation according to your process. Do not leave an old unresolved label in a matrix after the issuer has corrected the information. Equally, do not erase the history so completely that another reviewer cannot understand why the record changed.

A repeated issue may indicate an intake problem. Perhaps suppliers omit identifiers, profiles use vague issuer labels, or old certificates are routinely attached. Improve the request template to obtain the necessary information earlier. A better intake question can reduce repeated searches without weakening the review.

Distinguish an unavailable service from an unmatched search

An unavailable verification page and a completed search with no matching result are different observations. Record a service error, inaccessible page, or failed search request as a technical access problem. Do not translate it into a negative credential result. Where the issuer offers an alternative official route, use that route and retain the response. Otherwise identify the unresolved check and its owner so the review does not quietly proceed as if verification had succeeded.

For a completed but unmatched search, record the selected program and the meaningful inputs used. Check a limited, justified variation, such as a documented name format or a transcription error in the identifier. Avoid broad searching through unrelated people until something similar appears. A result that resembles the claim is useful only if the identity and program match can be supported. Document the basis for any correction to the search inputs.

If a service changes its interface, read the current instructions before repeating an old procedure. A saved guide may refer to fields that no longer exist or a directory that covers a different set of programs. Record the official navigation route used at the time of the check. Do not rely on a third-party search engine snippet as a substitute for the issuer's returned result or a direct clarification of the credential status.

Keep the operational consequence separate from the search outcome. An unavailable service may require a later check or direct issuer confirmation under the organization's process. A missing result may require a focused evidence request. The designated reviewer decides what is needed for the intended use. Neither an administrative delay nor a search mismatch should be converted by the coordinator into a categorical statement that the person is qualified, unqualified, or dishonest.

Review several claims without extending one successful match

A personnel submission may list several credentials from the same issuer, several methods within a program, and employer records alongside them. Create a claim list before searching. Give each material claim its own evidence reference and verification outcome where an official lookup applies. This avoids the common shortcut of finding one valid result for the person's name and marking the whole submission verified.

In a fictional example, a proposed team member lists a current issuer credential, a historical credential under another program, and a current employer record. The official directory confirms the first claim. The historical claim needs evidence relevant to its period and purpose, while the employer record needs the appropriate employer review rather than a search in the issuer's personal credential directory. The final note can describe all three outcomes without forcing them into one green or red status.

Use a compact verification worksheet with claim, source, search date, matching basis, displayed result, and unresolved question. Where the directory omits a field needed for project review, record that limit. Do not fill the blank from a different credential held by the same person. If a source document provides the missing detail, identify that document separately so a later reviewer can distinguish what was checked online from what was read in the supplied package.

Before releasing the review summary, compare every favorable statement with its supporting observation. Replace broad phrases such as all certifications verified with an accurate description of the checks completed and any remaining review. The summary can still be concise, but it should not conceal the difference between identity matching, credential status, scope interpretation, and employer acceptance. Precision makes the lookup useful to the next decision maker and reduces the chance that a limited public search will be treated as a complete qualification assessment.

Understand NDT Connect's role

NDT Connect helps organize profile information and recorded certificate dates. It does not operate ASNT, AWS, or API verification services, issue their credentials, or independently validate every qualification claim. A directory profile or account flag should not be interpreted as universal confirmation of the person's methods and scope.

Use the issuer's official tools for issuer-specific claims and retain your review note in the controlled personnel or supplier process. Update the relevant profile when authoritative evidence changes. If a platform field cannot capture the review basis, keep that basis separately rather than compressing it into an ambiguous status label.

A successful verification process ends with a precise statement: which credential fact was checked, for which person, at which source, on which date, and what remains outside the check. That statement is more useful to a buyer or employer than an unexplained green tick.