NDT Renewal Handover: Transfer an Application in Progress

Define the handover boundary

A renewal may be owned personally by the credential holder while an employer helps gather evidence or track dates. Another renewal may concern an employer-controlled certification record. Begin the handover by stating which situation applies and who is authorized to act. The person maintaining a spreadsheet is not automatically authorized to submit an application or make declarations for someone else.

List the reason for the handover: staff leave, a coordinator change, employer transfer, or temporary absence. That reason affects which access and responsibilities should change. A temporary backup may need visibility into open actions but should not inherit another person's login credentials or make unapproved changes to the application.

API publishes application and recertification guidance for its individual programs [1]. ASNT publishes separate guidance for its Level III renewal process [2]. Use the actual program's current instructions as the source for required evidence and submissions. The handover process below organizes the work; it does not replace those instructions or establish a common renewal rule.

Record the current state in precise language

Use a status that describes what has actually happened: evidence collection underway, package under internal review, application submitted, issuer requested more information, or new credential evidence received. Avoid nearly renewed or renewal done when the only completed step is payment or submission. The incoming coordinator needs a factual starting point.

Record the date of the status and the supporting evidence. A portal confirmation, issuer email, or controlled employer review record can establish the milestone. A colleague's recollection may be useful background but should be labeled as unconfirmed until the source is located. Preserve the difference between a reported action and an evidenced action.

Write the next action as a verb with an owner and target date. Obtain signed employment statement from the authorized contact is clearer than experience pending. Include the reason the action matters and what counts as completion. This lets the successor recognize a useful response when it arrives.

Prepare a compact handover index

The index should identify the person, issuer, program, credential reference, method or scope, current recorded expiry, application reference if one exists, evidence location, and open actions. Add the official issuer contact route and the responsible internal reviewer. Keep passwords, payment information, and unrelated personal identifiers out of this document.

Separate the current application package from historical supporting material. The successor should be able to find exactly what was submitted and distinguish it from documents collected afterward. If a file was revised before submission, retain the submitted version as a reference rather than assuming the newest file reflects what the issuer received.

Include a short field dictionary if local abbreviations are used. An incoming coordinator should not have to decode shorthand such as sent L3 or waiting HR to determine what remains. Plain descriptions reduce the chance of duplicating a request or closing an item that has not actually been resolved.

Map every evidence item to its purpose

For each document, state the requirement or claim it is intended to support. An activity certificate may support a renewal activity claim, while an employer statement may support employment evidence. Keep the issuer's categories and units intact. Do not combine different kinds of evidence into a single total merely because the handover spreadsheet has one column available.

ASNT's Level III renewal point guidance identifies activity categories and associated documentation [3]. Where that route is relevant, preserve the link between the claimed activity and its supporting record. The coordinator should not decide that a document earns a particular value merely because it resembles another accepted item.

Flag evidence that is awaiting review. A document can be received but not yet accepted, readable but missing a signature, or complete for one method while incomplete for another. A handover that lists only received files can make the package look finished while concealing these unresolved conditions.

Preserve the communication history that changes the work

Save issuer requests, clarification responses, and submission confirmations that affect the application. A long mailbox export is usually less useful than a focused correspondence index with dates, subjects, and controlled links. The successor needs to understand the decision trail, not every scheduling email associated with it.

When a telephone conversation materially affects the next step, record who spoke, when, what was discussed, and what remains to be confirmed. If written confirmation is needed, request it through the appropriate channel. Do not turn an informal conversation into a definitive issuer decision without support.

Identify unanswered messages and their follow-up dates. If the outgoing coordinator has already contacted the issuer, the incoming coordinator should know the reference number and wording used. This prevents duplicate requests that contain conflicting information or make it difficult for the issuer to follow one coherent application history.

Transfer access through approved account processes

Do not share a credential holder's password with a new coordinator. Use the issuer's supported account or authorization process where one exists, or have the credential holder perform actions that require personal access. A handover can transfer administrative knowledge without transferring an account inappropriately.

For employer-controlled systems, have the authorized administrator grant the successor the access needed for the role and remove access no longer required. Confirm that evidence links work under the successor's own account. A link that opens only for the outgoing coordinator is not an effective handover, even if the document path looks correct.

Record any access limitation as an open action. The successor may be able to view the inventory but not the underlying package, or receive reminders but not edit profile data. Resolve those limitations before assuming the person can own the task. Avoid workarounds that place sensitive files in an uncontrolled personal folder.

Work through a fictional information-request handover

Imagine a fictional renewal coordinator, Lee, leaving for planned leave after an application has been submitted. The issuer has asked for clarification on one activity record. The credential holder has requested a corrected statement from the activity organizer but has not yet received it. The original certificate expiry is still the date shown in the tracker.

Lee's handover identifies the issuer request, the organizer request, the exact document expected, the person authorized to submit the response, and the next review date. The successor can check for the corrected statement and help route it without resubmitting the entire application or changing the expiry prematurely.

When the statement arrives, the successor records its receipt and review. The credential holder or authorized actor supplies it through the proper process. Only after the issuer provides the relevant outcome does the active credential record change. The handover preserves progress while keeping submission and approval distinct.

Reconcile deadlines and internal targets

List the authoritative dates and the team's internal planning targets separately. The source expiry, an issuer response deadline, and an internal evidence-review date are different kinds of dates. The successor should know which source supports each one and which dates the organization chose for its own planning.

If a target has been missed, describe the consequence and next decision rather than moving the date forward silently. An overdue internal follow-up may require escalation; a missed issuer deadline may require direct program guidance. The handover should make the situation visible enough for the appropriate person to act.

Avoid importing a rule from another credential. Similar program names or familiar renewal terminology do not establish identical conditions. When the applicable instructions are unclear, assign a specific clarification task with the issuer rather than asking the successor to infer the rule from an old unrelated application.

Keep the certificate manager aligned with evidence

In NDT Connect, profile records supply the credential details used by the certificate manager. The handover should identify who maintains those details and whether the verified account has opted into email reminders. A reminder reaching the old coordinator does not mean the new owner has visibility into the work.

The application does not submit renewal applications, issue credentials, or transfer issuer account access. It also does not provide a full automatic audit-package export or a work-dispatch lockout. Keep the evidence index and handover action list in your controlled process where those functions are required.

When new credential evidence arrives, compare person, issuer, identifier, scope, and dates before updating the saved record. Retain the previous period as history according to the records policy. Close the handover task only after the successor can confirm that the active tracker and the authoritative evidence are aligned.

Include the commitments already made

Identify any commitments that affect the next step, such as a promised evidence response date, an agreed internal review meeting, or a credential holder’s planned availability. Label these as coordination commitments rather than issuer approvals. The successor should know which people are expecting a response and which discussions still need a decision. If a commitment can no longer be met, assign responsibility for updating the relevant party through the authorized process. This prevents a technically complete evidence handover from failing because the practical arrangements were left in the outgoing coordinator’s memory.

Prepare for an unplanned coordinator absence

An unexpected absence may leave the successor without a prepared handover or access to the outgoing coordinator's personal notes. Start with controlled organizational records and the credential holder's account of the work. Establish the application reference, last evidenced milestone, current source expiry, and any known issuer request. Label uncertain information as provisional. Do not recreate missing correspondence from memory or assume that a draft package was submitted because it appears complete in a shared folder.

Identify the authorized actor before taking action. The credential holder may need to obtain status through their own issuer account, while an employer administrator may be permitted to review internal evidence. Follow the issuer's supported process for assistance or representation. The urgency of a deadline does not make password sharing an appropriate handover mechanism. Record any access limitation and decide with the responsible person how the immediate request will be handled.

Create a temporary situation note with three parts: confirmed facts, unresolved questions, and the next authorized actions. Assign a time for reviewing the note as evidence arrives. This avoids presenting a provisional reconstruction as the complete application history. If the issuer confirms that an item was already supplied, update the note and stop the duplicate request. If no submission can be confirmed, refer that finding to the person responsible for deciding what to do next.

Preserve the interim actions when the original coordinator returns. The returning owner should be able to see which messages were received, which documents were supplied, and which commitments changed. Otherwise the original coordinator may resume from an outdated mental picture and undo useful progress. A short reconciliation meeting can establish one current action list and retire the provisional notes while retaining the evidence behind decisions made during the absence.

Define acceptance and return of responsibility

For a planned handover, define what the incoming coordinator is accepting. The responsibility may be monitoring an issuer request, assembling evidence, arranging an internal review, or maintaining the date tracker. It should not silently expand to making personal declarations or approving qualification. Write the accepted tasks and the boundaries in the handover note. Where the credential holder retains a task, identify that person explicitly so the task does not fall between coordinators.

Use a practical acceptance check. The successor identifies the next external response expected, the last date supported by source evidence, the package version already submitted, and the person authorized to act on a new request. They then open the relevant documents using their own access. Any missing answer becomes an action with an owner. A signed handover acknowledgment is useful only when it reflects this practical ability to continue the work.

If responsibility will return after leave, agree on a handback point and record what will be reviewed then. The temporary coordinator should summarize changes since the handover, including unresolved items whose target dates moved and the reasons. The original owner confirms which tasks they resume. Avoid leaving both people as apparent owners of the same follow-up; duplicate messages can confuse the issuer and create different versions of the evidence response.

Close the administrative handover independently of the renewal outcome. The handover may be complete while an application remains under review, or the renewal evidence may arrive while access and tracker ownership still need correction. Use separate closure statements for those conditions. This makes the record honest about both kinds of progress and gives the organization a usable continuity practice for the next absence, rather than treating receipt of a new certificate as proof that every ownership issue was resolved.

Test the handover before the outgoing owner leaves

Ask the successor to explain the current state in their own words: what has been submitted, what remains open, who can act, and what happens next. This is a practical comprehension check rather than an examination. Any uncertainty reveals where the handover needs a clearer link, label, or decision record.

Have the successor open a small sample of evidence using their own approved access. Confirm that the application reference and official contact route are available without asking for someone else's password. If a key document is missing, record that as an action before the outgoing owner becomes unavailable.

A good handover ends with an accepted responsibility, not merely a sent email. Record who has taken ownership and the next review point. That explicit acceptance protects continuity while preserving the credential holder's responsibility for personal declarations and the issuer's authority over the renewal outcome.