NDT Subcontractor Personnel Records: A Buyer Review Workflow

Define the personnel review separately from supplier selection

Supplier selection can consider equipment, availability, commercial terms, quality systems, and prior performance. Personnel qualification review asks a narrower question: what evidence supports the people proposed for this defined work? Keep that question visible so a favorable company presentation does not automatically become approval of every technician the supplier might later send.

Identify the assignment scope and period, the responsible buyer reviewer, and the supplier's authorized contact. Record which requirements govern the personnel review and who resolves ambiguity. This is an administrative workflow for organizing evidence; it does not determine the technical qualification requirements of a contract or prescribe a universal supplier approval standard.

Ask for the proposed personnel list early enough to review meaningful evidence. A supplier may not yet know every name during an initial quote, but that uncertainty should remain visible. Distinguish an indicative capability discussion from a completed review of the actual team intended for mobilization.

Separate company accreditation from individual credentials

A company may hold an accreditation or participate in an employer-based program while individual personnel hold separate records. ASNT describes accreditation of employer-based certification programs [1]. That company-level evidence has a different subject from a particular person's method, scope, or credential period.

If a supplier claims that its credential issuer is accredited, check the relevant accreditation scope and status through the appropriate source. ANAB's personnel-certification directory distinguishes accredited bodies from applicants and other status categories [2]. A pending application should not be described as current accreditation, and a broad organization name should not replace the scope review.

Keep these layers in separate fields: supplier organization evidence, credential issuer evidence where relevant, and proposed individual evidence. This makes the review more precise and prevents one impressive certificate from being used to answer several unrelated questions.

Request a focused personnel package

Ask the supplier for the information needed to match each person to the intended scope: name or agreed identifier, employer relationship, credential or employer-record issuer, program, method, level, stated limitations, relevant dates, and supporting source. Specify the required evidence format or secure sharing route through the project's approved process.

Do not demand an entire personnel archive by default. A focused request is easier for the supplier to fulfill and easier for the buyer to review. If additional evidence is necessary, explain which requirement or unresolved question it addresses. Avoid collecting unrelated private information simply because it appears in a standard supplier dossier.

Request an index that connects each proposed person to the documents supplied. A single PDF containing many certificates without names in the index can obscure missing pages or duplicated records. The buyer should be able to identify which evidence applies to which person without asking the supplier to narrate every attachment.

Match the evidence to the actual employer and role

Check who issued an employer certification record and which employer relationship is relevant to the proposed assignment. A previous employer's record may be useful supporting history, but it should not be silently treated as the current supplier's qualification decision. Ask the supplier to explain its current program basis and review outcome where that is required.

Read the role proposed for each person. A team member assigned to collect data, interpret results, supervise, or review reports may be subject to different requirements under the applicable process. Do not assume that a generic job title answers these questions. Let the responsible technical reviewer compare the role with the evidence.

Keep the supplier's explanation with the review record. If a subcontracting chain introduces another employer, identify that organization and its responsibility. The buyer's review should not lose the actual issuing authority behind several layers of logos, proposal covers, or agency names.

Verify issuer claims without overextending the result

Use the official issuer route for any certification-body credential that needs verification. ASNT describes its directory verification route in its FAQ [3]. Record the source, date, matching basis, and returned facts. A successful match supports those facts; it does not automatically establish every project requirement.

If a directory result is absent or conflicts with the supplied document, ask for clarification and keep the issue open. Do not accuse the person of misrepresentation solely because one search failed. Equally, do not close the review just because the supplier repeats the original claim without additional evidence.

Keep the verification note separate from the buyer's acceptance decision. The buyer may accept the personnel package for a specific purpose after considering other requirements. That decision should identify its scope and conditions rather than imply that the buyer has issued a new credential.

Review the full assignment period

Compare relevant recorded dates with the expected work period, including likely extensions where the planning process requires them to be considered. A credential may be current at proposal review and need attention before the assignment ends. Record the date overlap as a planning issue for the responsible reviewer.

Ask the supplier how it will communicate material changes to the proposed personnel evidence. That might include renewal outcomes, scope corrections, or a change in employer relationship. The expectation should be stated in the actual project process, not assumed from a supplier's general promise to keep records current.

Do not treat a planned renewal as completed evidence. Record the current source and the supplier's next action separately. If the project depends on a future outcome, the appropriate planner needs a contingency decision rather than a matrix that has already been updated to an unconfirmed date.

Establish a substitution workflow

Personnel substitutions are a common point where a reviewed package loses its practical value. Identify how the supplier will submit a replacement person's evidence, who reviews it, and what happens before the person starts the relevant work. The process should be proportionate to the assignment and consistent with the applicable requirements.

Do not assume that a replacement is equivalent because the job title or method abbreviation matches. Compare the actual scope, employer record, dates, and assignment role. Reuse the original requirement map where appropriate, but create a separate review trail for the substitute's evidence.

Record which personnel list is current. An email approving one substitute should not leave an old team list circulating as the active record. Update the controlled roster and preserve the earlier version where needed to explain who was reviewed or assigned at a particular time.

Work through a fictional late substitution

Imagine a fictional supplier proposes two technicians and provides complete evidence for review. Shortly before mobilization, one technician becomes unavailable. The supplier proposes another person with a similar job title but a different stated scope and a separate employer record.

The buyer uses the existing assignment requirements to review the replacement package. One scope question needs clarification, so the review remains pending for that person while the supplier provides the missing evidence. The buyer does not reuse the original person's approval or simply change the name in the roster.

After the responsible reviewer resolves the question, the active team list is updated with the decision date and evidence reference. The earlier roster remains available as history. This keeps the review attached to the people actually supplied instead of to an abstract promise that qualified staff will attend.

Record decisions and open conditions clearly

A review outcome should identify the person, assignment, evidence examined, reviewer, date, and any conditions or unresolved questions. Use precise language such as package accepted for the stated review purpose rather than universally qualified. The latter can imply a broader decision than the buyer has made.

If the package is incomplete, name the missing evidence and its owner. Avoid a vague rejection that forces the supplier to guess what to send next. A focused response might request an attachment defining scope or a clarification of the current employer record. Keep commercial pressure separate from the factual evidence question.

Track conditions through resolution. A condition noted in a review email but omitted from the active roster can be forgotten when the work starts. The people making assignment decisions need an accessible summary of what remains open and who is responsible for the next step.

Maintain a limited supplier evidence archive

Retain the review package and decision history according to the organization's applicable records process. Separate current operational records from historical evidence so old personnel are not accidentally presented as the active team. Keep the archive accessible to authorized reviewers without exposing it broadly to everyone involved in procurement.

When the supplier sends a corrected document, identify what changed and which earlier version it supersedes. Update any affected review or roster through the controlled process. A corrected file in a shared folder is not enough if the active decision still rests on the older evidence.

Review recurring issues with the supplier after the assignment. Missing identifiers, unclear issuer labels, and late substitutions may point to a better intake template or communication process. Improve the evidence exchange without turning one project's special conditions into an unsupported universal requirement.

Reconcile the proposed roster with the team that arrives

Create a controlled roster reference for the personnel package reviewed for the assignment. The roster should identify the people, proposed roles, relevant evidence references, review state, and applicable work period. A supplier's company name alone is not enough to connect the review to the actual team. Keep the roster reference available to the person responsible for confirming mobilization so substitutions or role changes are noticed before the earlier decision is relied upon.

At mobilization, compare the supplied team list with the reviewed roster using the organization's normal identity and personnel process. Record discrepancies narrowly: a different person, a changed role, a different employer relationship, or a missing review reference. The administrative check should not become an improvised technical assessment at the gate. Route any change to the designated reviewer and follow the project's established process for deciding whether additional evidence or approval is needed.

In a fictional case, a supplier sends the two reviewed technicians but exchanges their proposed roles. Both names match the approved roster, yet the role-specific evidence may require reconsideration. The coordinator flags the role change rather than treating matching names as sufficient. The responsible reviewer determines whether the existing package supports the revised arrangement. The record should preserve that decision without implying that the original approval covered every possible role assignment.

Record later personnel changes against the same roster history. A long assignment may involve rotation, leave coverage, or an extension beyond the original period. Keep current operational information easy to identify while retaining the earlier team and review references where required. This lets a later reviewer connect a particular person's work period with the evidence considered, instead of assuming that the final roster describes everyone who participated throughout the project.

Clarify responsibility when several organizations supply personnel

Some proposed teams include people employed by another organization or working through an intermediary. Ask the supplier to identify the relevant employer relationship and the origin of each employer-issued record. Do not assume that an intermediary's commercial agreement makes it the issuer of another organization's personnel evidence. The review should establish which organization made the qualification decision being relied upon and which party can answer questions about it.

Use a responsibility note with the proposed person's role, actual evidence issuer, supplier contact, and designated reviewing authority for the assignment. Where the project requires a particular employer program or other arrangement, route questions about that requirement to the responsible owner. The note organizes the facts; it does not decide contractual responsibility or create a certification relationship between organizations. Avoid using a supplier logo on the cover page to obscure who issued the underlying records.

Request clarification through the agreed supplier channel while identifying the source needed for the answer. A coordinator may relay an issuer statement, but their assurance should not be presented as though they personally issued or reviewed the credential. Preserve the authoritative response and any limitation. If the source organization can confirm only part of the proposed scope, keep that boundary visible in the personnel review rather than replacing it with the broader capability claims in the supplier's brochure.

Before closing the review, confirm that future changes have an owner. The party maintaining the roster, the party supplying updated evidence, and the party approving a change may be different. Record those responsibilities and the approved communication route. A clear chain of responsibility makes late questions easier to resolve and prevents the buyer from relying on an outdated package simply because everyone assumed another organization was monitoring the personnel records.

Use marketplace information as an introduction

An NDT Connect profile can help a buyer discover a supplier and ask relevant questions. The certificate manager can organize dates supplied through account records. Neither should be treated as independent validation of every technician's qualification or as proof that the proposed team is accepted for the project.

Request the evidence needed for the actual assignment through the authorized supplier-review process. Keep issuer verification and employer qualification review distinct from account or profile verification indicators. A useful marketplace connection begins the conversation; the personnel decision still needs its own evidence and responsible reviewer.

The result should be a clear current team list, a traceable decision for each person's stated role, and an agreed way to handle changes. That is more dependable than a large supplier brochure or an undated folder of certificates that may not describe the people who arrive.