NDT Certificate Scope Changes After Contract Award

A revised personnel document arrives after a buyer has awarded an inspection assignment. Its wording differs from the copy used during the quotation review. Perhaps a technique is missing, the issuing employer has changed, or a limitation has been added. The useful first question is what exact statement changed and which promised activities relied on it. Treating the whole assignment as either automatically acceptable or automatically cancelled skips the evidence needed for a reasoned decision.

Create a change record with the earlier document reference, replacement document reference, date received, person who supplied it, and the wording that needs explanation. Keep the earlier file in the controlled project record rather than silently replacing it. This preserves what the original commercial review actually considered. The comparison should identify the uncertainty without deciding that a typographical difference necessarily changes competence or that a familiar qualification label necessarily resolves it.

Not every replacement certificate is a change in authorization. An issuer may have corrected a spelling error, reformatted a table, or replaced a damaged copy. Conversely, a document that looks almost identical may contain an important restriction in a footnote. Ask the issuer or responsible employer to identify the reason for revision and its effective date. Do not infer the answer from a newer issue date or a more polished template.

Use three working descriptions while clarification is pending: administrative correction, confirmed scope change, and unresolved difference. These are project review labels, not certification statuses awarded by NDT Connect. The unresolved category is particularly useful because it prevents a coordinator from selecting whichever interpretation keeps the schedule easiest. Attach the question to a named task and a required decision date so the uncertainty produces a concrete follow-up instead of a vague warning.

The appropriate reviewer depends on the route represented by the document. ASNT distinguishes employer-based certification from its own central certification programs. A certificate label alone therefore does not identify every decision maker for a particular assignment. Read the issuer, scheme or written-practice reference, method, level, limitations, and employer relationship before deciding where to send the clarification.

An administrator can collect evidence and compare references, but should not rewrite the issuer’s scope in order to satisfy a purchase order. A buyer can explain contractual requirements, while the responsible employer or other applicable authority addresses its own authorization decisions. These roles may involve the same person in a small company, yet the decision should still state which responsibility is being exercised. Keep commercial acceptance, credential interpretation, and technical task assignment distinguishable.

Break the awarded work into activities with meaningful boundaries. For example, equipment setup, examination, interpretation, evaluation against an acceptance source, preparation of a report, and review of that report may involve different evidence questions. Avoid a single row saying “UT project” if the concern relates only to an advanced technique or a particular product form. A narrower map helps the reviewer answer the actual issue without unnecessarily reopening unrelated work.

Include activities that have not started and activities already completed. Add the planned or actual date, affected component group, procedure revision, and person assigned. The aim is not to build a second scheduling system. It is to expose where the changed document could alter a promise made during award. If a subcontractor supplies several people, identify the affected individual privately rather than treating one changed document as evidence about the entire company.

A useful comparison places the original statement beside the new statement and then describes the task consequence being investigated. Quote only the short wording necessary for the clarification; retain the full documents in the authorized record location. Include relevant page or section references. Long copied document bundles without a concise comparison create extra reading and increase the chance that the important restriction will be missed.

Distinguish a direct change from a consequence you are asking somebody to confirm. “Technique no longer listed” is an observation if the two documents show it. “Inspector can no longer perform this assignment” is a conclusion requiring the appropriate review. Writing those as separate entries keeps the packet factual. It also makes it easier to revise the conclusion later without altering the original observation or concealing why the question was raised.

The free Certificate Manager stores entered personnel record labels, qualification descriptions, personnel counts, and an expiry date when one is stated. It does not authenticate a revised document or decide whether a customer’s scope is covered. Update its short description only after checking the source, and keep the detailed change packet in your existing controlled document process.

Do not replace a real certificate expiry with the deadline for answering this question. That would make a planning date look like an issuer’s limit and could create misleading reminders. If several records previously shared one line but now have different wording or expiry dates, consider separate entries so a single label does not hide the distinction. The private register is useful for retrieval; the evidence and decision remain necessary outside that compact summary.

The project team should determine what can proceed while clarification is pending, using its own responsibilities and procedures. Document the boundary explicitly: which task is awaiting review, what evidence is missing, and who may release the task. Do not invent a technical workaround from the certificate manager. A clear boundary lets planners arrange access, documentation, or other unaffected preparation without representing the unresolved activity as approved.

State the time at which the boundary was communicated and to whom. If field work is imminent, a note buried in an office folder is not a useful handoff. Use the project’s established communication channel and obtain an acknowledgement appropriate to that process. NDT Connect does not broadcast scope-change notices to a crew or enforce a dispatch hold. The coordinator must connect the record to the people making the next operational decision.

Consider a fictional contractor awarded two work packages for a US fabrication project. One involves conventional examinations under a named procedure; another involves a technique whose reference appeared on the submitted personnel evidence. Before mobilization, a replacement credential omits that technique reference. The coordinator preserves both files and maps the omission to the second package rather than telling the buyer that every aspect of the assignment has changed.

The responsible reviewer confirms that the first package has a separate, unchanged evidence basis. The second remains pending while the issuer explains whether the omission is administrative or substantive. Procurement obtains a contingency proposal from another suitable resource, but does not describe that person as appointed until the normal review is complete. This fictional sequence demonstrates how a focused question can preserve useful planning without assuming the unresolved scope is acceptable.

Send a short request identifying the two document versions, the exact changed statement, the relevant task, and the date on which that task is expected to occur. Ask whether the change alters the stated scope and, if so, when the alteration took effect. Request a controlled response or corrected document through the established channel. A general question such as “is this person still certified?” may be answered accurately while leaving the technique-specific problem unresolved.

If the response uses conditional language, preserve the condition. For example, a statement tied to an employer, procedure, additional assessment, or a defined sector should not become an unrestricted approval in a project summary. Where two reviewers answer different questions, show both answers and their responsibilities. The closeout should make it possible for a later reader to understand why a task was assigned, not merely see a collection of reassuring email phrases.

A difficult case is a replacement followed quickly by another correction. Number the received versions in your working packet and retain the issuer’s own identifiers separately. A filename such as final-new-corrected does not establish which document is effective. Ask the issuer to identify the current document and explain whether earlier replacements were withdrawn or merely reformatted. Then mark your comparison so a reviewer cannot accidentally answer a question about a version that is no longer being proposed.

Record the date received separately from the date stated on the document and the effective date confirmed in the response. Those dates may legitimately differ. An office coordinator receiving a file on Friday should not assume it changed an inspector’s scope on Friday if the document describes another date. Where chronology affects completed work, summarize the sequence in plain language with source references. This helps the responsible reviewer assess the correct time period and prevents an inbox timestamp from becoming an unsupported technical conclusion.

If the replacement arrives after some examination work, map the affected dates and activities before deciding whether previous records need action. A new document may describe a change effective after the work, a correction to an earlier error, or an unresolved situation. Those possibilities have different implications and should not be collapsed into a blanket claim about all historical results. Preserve the actual personnel and document references used at the time.

Refer any question about the adequacy or disposition of completed work to the responsible technical and contractual reviewers. Record their decision reference and the affected report or component identifiers. Do not backdate a certificate entry, substitute a different inspector’s name, or edit an issued report simply to remove a visible inconsistency. The purpose of the change packet is to support an honest review of the evidence trail, including uncertainty that was not known earlier.

A subcontractor may respond with a replacement packet for an entire crew even when only one person’s evidence changed. Compare each affected record against the actual assigned role. Avoid copying a group statement into every personnel row, especially if methods, employers, or expiry dates differ. The project packet can use internal person identifiers to keep the task map readable while access to full personal documents remains limited to people involved in the review.

If the buyer previously accepted a named crew, clarify whether the proposed change concerns the evidence for the same person or a substitution of personnel. Those are different review questions. A substitute may have satisfactory documents yet still require scheduling, access, and assignment checks through the project process. Record the accepted staffing arrangement only when the relevant decisions are complete. The certificate index should reflect the resulting records, while the contract file preserves who was actually proposed, reviewed, and assigned.

Before issuing a report, compare its personnel description with the reviewed scope decision. A copied statement from the quotation or an old template can outlive the document that supported it. Use factual wording identifying the person’s actual role and relevant reference, with any required qualification details supplied from the approved project evidence. A title in the report should not imply that the author performed every stage if responsibilities were divided.

Digital NDT Reporting allows you to edit personnel and review-reference fields in a draft, but it does not pull updated credentials from Certificate Manager. Make the change deliberately and check the exported PDF. If an already issued report needs correction, follow the project’s revision process and use a new draft revision where appropriate. A typed reviewer name records what the user entered; it is not an electronic signature or independent verification of the scope decision.

A confirmed change may require another inspector, a different schedule, or additional review work. Record those commercial consequences separately from the evidence decision so budget pressure does not obscure what remains unresolved. An alternative resource should be assessed against the same task requirements instead of being accepted because travel is already booked. Equally, a pricing dispute does not itself establish that a qualification document is inadequate.

When asking for a revised quotation, describe the affected package and the assumptions that remain unchanged. Include any agreed hold point, access window, or reporting responsibility that influences the replacement arrangement. Avoid circulating a person’s full private credential history to every bidder. Share the minimum requirement needed to quote the work, then use an appropriate channel for the evidence review of the proposed individual. This keeps sourcing focused on a defined service.

A complete closeout identifies the disposition, the person responsible for it, the supporting reference, the effective date, and the tasks to which it applies. It also records what was updated: the private index, assignment plan, customer packet, or draft report. If the outcome is still conditional, state the remaining condition and its owner instead of marking the whole issue closed. The decision table below can organize those alternatives without making the decision for you.

Choose a sensible next review trigger, such as another scope amendment, change of employer, replacement credential, or reassignment to a different technique. Do not create an arbitrary new certificate expiry merely to force a reminder. The resulting packet should be concise enough to use at the next handover and detailed enough to explain the original discrepancy. That is the practical value of the exercise: a traceable answer tied to work, rather than an unexplained change in a register.