NDT Training Gap Plan: Turn Record Review into Useful Actions

Define the target role in observable terms

Start with the intended work and the applicable qualification context. A plan to become better at NDT is too broad to guide evidence collection or course selection. Identify the method, scope, responsibilities, and employer or certification program being considered. The technical owner should confirm these targets before a coordinator turns them into training tasks.

Separate the desired future role from the person's current authorized responsibilities. A development plan can prepare someone for additional work without implying that they may perform it independently today. Record who will review progress and who has authority to make the eventual qualification or assignment decision.

ASNT distinguishes its NDT and 9712 certification programs in its program comparison [1]. That matters when choosing a development route: similar level names do not make every program or evidence requirement interchangeable. Use the current guidance for the intended route rather than building a plan from an unrelated course advertisement.

Classify the gap before choosing the remedy

Use four practical categories: evidence missing, evidence unclear, learning needed, and experience or assessment needed under the applicable program. These categories are an editorial planning aid, not a new qualification standard. Their purpose is to prevent every unresolved record from automatically producing a course purchase.

A person may have completed relevant learning but lost the documentation. Another person may hold a clear course certificate but still need additional preparation for a new scope. A third may have substantial experience whose relationship to the target requirement needs review. The same action cannot sensibly resolve all three situations.

Record the gap in one sentence with the evidence behind it. For example, course hours not stated on supplied certificate is a documentation question. Required topic not shown in reviewed syllabus is a content question. Avoid vague labels such as insufficient qualification unless the responsible reviewer has made and documented that conclusion.

Build an evidence-first baseline

Collect the current training documents, relevant experience evidence, existing credentials, and employer review records. Keep each in its proper category. ASNT's 9712 Level II guidance separates training and experience documentation [2]. That separation helps prevent a planning spreadsheet from treating a course certificate as proof of field work.

Summarize what the evidence actually states, including limitations and unresolved details. Preserve the original wording beside internal labels when necessary. Do not infer broad capability from a familiar course title or count the same activity twice simply because it appears in both a certificate and a learning-platform transcript.

Have the appropriate reviewer identify which evidence can support the target role. The administrator can organize the file, but the reviewer decides how the evidence relates to the requirements. Record the basis and date of that decision so the plan does not depend on an informal conversation that later participants cannot reconstruct.

Set a learning objective that can be reviewed

For a genuine learning need, describe the intended outcome in concrete terms agreed by the technical owner. The objective might concern understanding a subject area, interpreting a controlled procedure under supervision, or developing a defined reporting skill. Avoid promising that a course alone will produce an independently qualified technician.

Identify how completion and progress will be evidenced. A provider's completion certificate may document the course, while a separate employer review may assess its relevance to the role. The plan should show both where needed. This prevents the final course receipt from being treated as the end of every development requirement.

Keep the objective narrow enough to select an appropriate activity. A large collection of unrelated webinars may produce many certificates without addressing the actual gap. Conversely, a focused activity may be valuable even if it does not produce a new credential. Record the purpose rather than measuring progress only by the number of documents collected.

Compare activities against the objective

Review the syllabus, delivery format, stated prerequisites, practical components, instructor arrangements, and evidence issued. Ask the provider questions that follow from the identified gap. If the missing element concerns supervised practical learning, a course's marketing claim of comprehensive coverage is not enough to establish that the relevant component is included.

ASNT Education explains its own course contact-hour and completion descriptions in its FAQ [3]. Use provider-specific definitions when comparing options. A nominal duration, contact-hour statement, and participant's actual completion time can describe different things. Preserve those meanings rather than converting them into one convenient total without a basis.

Ask the intended reviewing authority about acceptability before relying on an activity for a particular program. This is especially useful when the course is delivered in a different format or jurisdiction from the employer's usual training. The plan should document the answer, not merely the provider's assurance that the course is widely recognized.

Sequence the work around dependencies

Some actions can happen immediately, such as requesting a missing syllabus or correcting a participant name. Others depend on access to a suitable course, approved supervision, or an assessment process. Put those dependencies in the plan so the timeline reflects the work that must occur before the next decision.

Choose realistic internal target dates with the people who will support the activity. Label those dates as planning commitments, not issuer deadlines unless they actually come from the issuer. If a dependency changes, revise the plan openly and explain the effect on the target role or assignment.

Do not solve a scheduling problem by changing qualification status. If the necessary development cannot be completed before a project starts, the responsible planner needs that fact. The training plan should support a staffing decision, not hide the gap behind a future course booking.

Work through a fictional three-gap plan

Consider a fictional technician, Robin, moving toward a broader inspection role. The records review identifies three issues: one course certificate lacks hours, a new application topic is not covered by the documented syllabus, and the employer reviewer needs clearer experience evidence for the target scope. These are three different tasks.

The first task is a provider clarification request. The second is a targeted learning activity selected with the technical owner. The third is an evidence request and review under the applicable program. Robin does not enroll in the same introductory course three times to make the spreadsheet appear complete.

The plan names the owner, expected evidence, and review point for each task. When the provider supplies the missing hours, that documentation gap closes. The learning and experience tasks remain open until their own outcomes are reviewed. This makes progress visible without implying that one resolved item settles the whole qualification question.

Keep supervision and assessment responsibilities explicit

If the development activity involves workplace practice, identify the authorized supervisor and the conditions under which the activity occurs. The plan should refer to the employer's approved process rather than giving technical operating instructions. A learning objective is not permission to bypass supervision or perform work outside the person's current role.

Record who will assess the resulting evidence and how the decision will be documented. The person organizing the calendar may not be the person responsible for technical assessment. Clear ownership prevents the final signature from becoming an administrative formality added after everyone assumes the plan is complete.

Protect assessment material according to the applicable process. A development ledger generally needs the outcome and evidence location, not confidential questions or answer keys. Keep those materials in their controlled system and provide reviewers with authorized access when required.

Review progress using evidence, not attendance alone

At each planned review, compare the completed activity with the objective. Check what the provider or employer has actually documented and identify any remaining questions. Attendance can be a useful milestone, but it should not automatically close a learning objective whose intended outcome requires another review.

If progress is different from expected, revise the action based on the reason. The activity may have covered the wrong topic, the evidence may be incomplete, or the person may need more supervised development. Avoid labeling every delay as a performance problem when the plan itself was unclear or the required opportunity was unavailable.

Record partial completion accurately. A completed theory component and an outstanding practical component should remain separately visible if that distinction matters to the program. Do not describe the whole activity as failed or complete when neither description represents the evidence.

Close the plan with a defined decision

A development task closes when the expected evidence and review outcome are recorded. The overall plan closes when the responsible owner decides whether its stated objective has been met or whether a revised plan is needed. These decisions should identify their scope so they are not later interpreted as a universal endorsement of capability.

If the plan supports a new employer certification or qualification decision, create that record through the employer's process. Do not edit the training certificate to make it serve as the employer decision. Keep the learning history, evidence review, and resulting credential or authorization distinct and linked.

Update the personnel matrix only after the appropriate decision. A course completion date can be reflected in the training ledger immediately, while the qualification summary may require additional review. This separation gives managers an honest view of progress without turning a development milestone into an unsupported work-status change.

Turn the gap review into a usable action sheet

Create one action row for each distinct gap instead of one broad task called complete training. A row should identify the target role, the evidence reviewed, the gap category, the proposed action, the expected output, the owner, and the reviewer who will assess the result. Include the source of the expectation, such as the applicable employer program or the intended application's instructions. This makes the plan reviewable even when the administrator did not attend the original technical discussion.

For a documentation gap, the expected output might be a provider statement connecting hours to a named course session. For a learning gap, it might be completion evidence for a specifically selected activity followed by the employer's review. For an experience question, the action may be obtaining a supported statement or arranging the next step identified by the responsible reviewer. Keep these outputs distinct so a course booking cannot close an unrelated evidence or experience action.

Add a dependency field only where it changes the sequence. A practical learning opportunity may depend on suitable supervision and approved access; a course may depend on prerequisite evidence; an application review may depend on a corrected identity record. State which owner can resolve the dependency. A target date without this information can become an optimistic deadline that everyone repeats even though nobody controls the missing prerequisite.

Review the action sheet with the technician. Confirm that the person understands the intended outcome, what they need to collect, and who decides whether the result supports the target role. Invite factual corrections to the evidence baseline. A course missing from the folder may already have been completed, while an apparent prerequisite may be based on an outdated role description. Resolving these points before enrollment can prevent unnecessary expense and an avoidable cycle of incomplete evidence.

Reassess the plan when opportunities or requirements change

A development plan should have explicit review triggers in addition to planned meetings. Examples include cancellation of the selected course, a material syllabus change, loss of the planned supervisor, a revised target role, or clarification from the reviewing authority. Record the trigger and assess which objectives it affects. Avoid restarting the entire plan when only one dependency changed, but do not continue with an activity that no longer addresses the identified gap.

Suppose a fictional technician books a course selected for a particular practical component. Before delivery, the provider moves that component to a later session. The plan owner records what changed and asks the technical reviewer whether the revised sequence still supports the intended development. The already completed theory can remain recorded accurately. The plan should not show full completion merely because the original booking date passed, nor erase useful completed learning because another component remains open.

If the employer changes the target role, compare the existing objectives with the revised responsibilities. Some learning may remain relevant; other activities may no longer be priorities. Preserve completed evidence and document the revised purpose of outstanding actions. A canceled objective is a planning decision, not proof that the technician failed it. This distinction matters when managers later review development history or use it to discuss performance.

At the next review, assess whether the plan's assumptions were sound. Did the provider issue the expected evidence? Was supervision available? Did the selected activity address the gap identified by the reviewer? Use the answers to improve future planning rather than measuring success only by money spent or certificates collected. A useful development record shows how the organization connected a real need to an appropriate activity, examined the result, and made a documented decision about the next step.

Maintain the plan alongside the actual tools

NDT Connect's profiles and certificate manager can help maintain accurate credential descriptions and recorded dates. They do not determine training acceptance, approve an experience claim, or issue a qualification. Keep the development objectives, supervision arrangements, and review decisions in the controlled process that your organization uses.

Use the training information hub to identify questions and research routes, then confirm current offerings and requirements with the relevant provider or authority. A directory or guide does not establish that a course is available for your dates or accepted for your intended purpose. Record the confirmation you actually receive.

A good training-gap plan reduces wasted effort by distinguishing what is missing from what needs to be learned. It gives the technician a clear objective, gives the employer a reviewable evidence trail, and makes progress understandable without promising a credential or assignment outcome in advance.