Update NDT Evidence Plans After a Client Spec Change

A client can issue a revised specification after an inspection team’s personnel evidence has already been reviewed. The immediate question is not whether every record must be collected again. It is what changed, when the revised requirement applies and which earlier decisions depend on the affected wording. Begin with the controlled project documents and ask the contract or technical owner to identify the relevant change. A new revision number alone does not explain its impact on personnel. Conversely, an apparently small wording change may alter an evidence request or responsibility that the earlier review did not address.

This guide produces a version-linked qualification question packet. It connects the revised project requirement to specific duties, evidence and decisions while preserving the earlier review for its original basis. It is distinct from changing the employer’s written practice itself. The client may introduce a project condition without changing the employer’s general program, or the employer may decide that another controlled process also needs attention. Do not assume either outcome. Make the dependency visible, route the question to its actual owner and avoid spreading an ambiguous request through every personnel folder.

Record the document identity, old and new revisions, date received and the project or work package affected. Ask the responsible owner when the revision applies and whether any transition instruction exists. Do not infer retroactive effect or a universal stop-work rule from this guide. The actual project requirements and responsible decisions govern those questions. If multiple copies circulate, identify the controlled source before comparing wording. A personnel review based on an uncontrolled attachment can become difficult to explain even when the reviewer’s reasoning was sound for the text they received.

Request a focused change description where available, but verify the relevant context through the authorized review process. A summary may omit an interaction with another referenced requirement. Keep the comparison limited to information you are permitted to share. The qualification planner does not need a full confidential client specification. It needs a general description of the question and a reference held in the project’s controlled system. This separation lets a coordinator organize follow-up without distributing contract material or allowing a copied excerpt to become the unofficial source for future decisions.

A project specification, employer written practice, credential program and inspection procedure can each describe different aspects of the work. Keep their roles identifiable when a revision arrives. ASNT’s explanation of employer-based certification describes an employer’s written practice within its certification program. That context does not mean every client change automatically rewrites the employer program. Ask the employer’s responsible reviewer how the new project requirement interacts with existing personnel arrangements. Document the answer instead of changing record labels yourself to make the project and employer terminology appear identical.

The difference matters operationally. A client might request an additional evidence submission, clarify a technique or change who reviews a report. Those examples raise different personnel questions even if the same credential remains part of the packet. Identify whether the change affects evidence presentation, actual work scope or an acceptance decision. If the employer determines that its own controlled documents also need revision, reference that process separately. The project qualification worksheet should point to the relevant decisions, not silently become a substitute written practice or an unofficial amendment to the client’s specification.

Describe the affected duties in neutral terms first. Identify the method or technique, product scope, evaluation role or report responsibility involved. Then identify which proposed assignments contain those duties. This task-first approach can keep the review proportionate: a revision relevant to one activity need not automatically create the same question for every person on a project. Ask the responsible reviewer to confirm that interpretation. Do not use the worksheet to decide that someone is unaffected merely because their job title differs from the wording in the client document.

For each affected assignment, identify the earlier decision and the evidence it relied on. The new requirement may be answered by an existing record, by additional context or by a different development arrangement. Keep those possibilities open until reviewed. Avoid describing the person as newly unqualified simply because a document changed. The accurate status may be that acceptance for the revised project basis needs review. That wording preserves both facts: the earlier decision existed, and the current assignment question has not yet been resolved. It is more useful than erasing the old review or treating it as permanently universal.

Keep the earlier packet, requirement reference and decision intact in the appropriate records process. Do not overwrite an accepted status without preserving what it meant and when it applied. Add a new review entry linked to the revised basis. That makes it possible to explain why a person was assigned under an earlier version and what changed for later work. It also avoids a misleading historical record in which today’s requirement appears to have been reviewed before it existed. The worksheet should support the organization’s actual retention process rather than invent a new universal retention period.

If the earlier review cannot be located, record that as a separate retrieval problem. Do not reconstruct its approval from a schedule, email access or a completed report signature alone. Ask the authorized holder for the decision record and identify any limits in what can be recovered. The new review can proceed according to the responsible process while the history remains accurately described. This is especially important when personnel or project coordinators have changed, because an apparently simple status reset can otherwise remove the only visible connection between the old requirement and the decision originally made.

The qualification evidence planner can generate a new question list for the revised assignment context. Use a general role description and mark affected evidence as available, needing clarification or needing to be obtained as appropriate. The tool does not compare specification revisions or determine which personnel are affected. It also does not inspect uploaded records. The version comparison and applicability decisions belong in the project’s controlled process. Use the planner to organize the resulting questions, then attach its export to your working packet only if that helps the responsible review.

Entries remain in the open page, with deliberate TXT and CSV exports and no automatic saving to an account or browser storage. Keep client document text, names and credential identifiers out of the short descriptions. The separate worksheet supplies columns for old and new requirement references, affected tasks and decision status. Recreate the planner checklist when the context changes rather than sharing an earlier export as if it had updated automatically. Downloads remain files under your control; the planner does not withdraw old copies or notify recipients that a revised question list now exists.

Imagine a fictional fabrication project whose original personnel packet was accepted for a defined inspection scope. A later client revision asks for clearer evidence of the people responsible for reviewing and releasing reports. The coordinator initially plans to request every certificate again. Instead, the project owner confirms which upcoming work packages use the revised requirement, and the technical reviewer identifies the affected reporting responsibilities. The team maps the existing records and decision references to those duties. The question is now specific: what evidence and acceptance are needed for the revised report-review arrangement?

In this invented scenario, some existing records remain relevant, while one responsibility requires clarification from the employer. The old acceptance is retained against the original project revision. A new entry records the open question under the revised basis and identifies the person who can answer it. The team does not rewrite previously issued reports or declare all inspectors deficient merely because the client changed its request. Any effect on actual work is decided through the responsible project process. The example illustrates version control and targeted review, not a claim about what any named code or client universally requires.

Use distinct statuses for document availability and acceptance against a requirement. A credential file can remain available while project acceptance under the new revision is pending. A training record can remain unchanged while a question about its relevance is reopened. This avoids unnecessary requests for documents the employer already holds and makes the unresolved decision easier to see. Ask the responsible reviewer to identify which earlier conclusions remain usable. Do not treat the absence of a new request as confirmation that every previous decision carries forward unchanged; record the basis for that conclusion where it matters.

A targeted reset also helps with scheduling. The work coordinator needs to know which task or responsibility has an open condition, not merely that an employee record is yellow in a spreadsheet. Describe the actual affected assignment and direct operational questions to the project owner. The worksheet does not authorize continued work or prescribe suspension. It organizes the information needed for those decisions. Where the project provides an interim instruction, preserve its scope, timing and issuing authority so that a temporary arrangement does not become an undocumented assumption for later work.

When the reviewer identifies a genuine gap, ask for the specific supporting information and who may provide it. Include the revised requirement reference so the record holder understands the purpose. Do not send a vague request to update all certifications when the issue is one report responsibility or a clarification of technique. A precise request is easier to answer and less likely to produce irrelevant replacements. Keep original evidence intact, and distinguish newly issued records from explanatory correspondence. The receiving reviewer still determines whether the response addresses the project requirement.

If the response requires development rather than documentation, record the proposed activity and its dependency on the revised task. Ask whether the project schedule and assignment need adjustment through the appropriate process. Do not assume that purchasing a course automatically resolves the client’s change. A revised scope, additional evidence or a development plan can have different consequences. Present them as questions for the responsible people, with their actual decision references afterward. This keeps the qualification discussion connected to the project change instead of allowing it to become a generic training initiative without a clear acceptance basis.

If the revision affects reporting responsibilities, confirm how the change will appear in the project’s report preparation and release process. The digital NDT reporting tool lets users enter their own procedure, specification and acceptance references and prepare editable report tables. It does not determine which client revision applies or whether the person entering data has the required authority. Before issuing an actual report, use the project’s confirmed references and responsibility arrangements. A convenient editor field should never become the reason an unresolved qualification decision is treated as complete.

For a report already issued, follow the responsible organization’s revision process when a change is actually required. Do not casually replace a historical reference to make the document look current. The reporting product supports immutable issued versions and revisions in its verified-account workflow, but that document behavior does not decide whether a technical or contractual correction is necessary. Keep the personnel review and report decision linked through references while preserving their distinct purposes. This makes the final handover easier to understand: the project requirement changed, the affected duties were reviewed and any required document action has an identified basis.

Once the responsible review is complete, tell the project coordinator which duties and work packages the decision covers. Retain the requirement revision and outcome reference in the authorized record. The certificate manager can organize entered credential information and dates, but it does not synchronize client specification revisions or automatically change assignment acceptance. A separate project decision may therefore remain necessary even when the underlying credential record is unchanged. Make that relationship visible so future users do not expect a reminder tool to maintain a project-specific review state it does not hold.

Review the planning copies shared during the change. Where appropriate, identify the final worksheet version and tell recipients which earlier question lists are superseded. Do not erase historical evidence or exceed the organization’s retention process. The purpose is to prevent an outdated open-question sheet from being mistaken for the current decision, or an old approval from being used for the new basis without explanation. A short cover note can state what changed, what was reviewed and what remains open. That is often more useful to scheduling than forwarding an entire chain of technical correspondence.

Use the worksheet to connect four facts: the revised requirement, the affected task, the evidence considered and the decision received. Keep any unresolved applicability or timing question visible. A later reviewer should be able to follow that chain without guessing which revision a green status referred to. This is the specific value of the guide’s worksheet compared with a general personnel record inventory. It records why a review was reopened and what allowed it to close, while leaving original records and formal decisions in their proper controlled locations.