Duplicate and Reissued NDT Certificates: Version Control

Identify what changed before replacing anything

When a new document arrives, compare it with the existing record rather than immediately overwriting the old file. Ask why it was issued. A replacement for a lost copy may repeat the same credential. A correction may fix a name. A renewal may establish a new validity period. An endorsement may add information while leaving the base credential intact.

Record the issuer's explanation where available. If the email says replacement certificate, preserve that message with the document. If the meaning is unclear, ask the issuer. The title or file creation date alone may not tell you whether the qualification changed or whether only the presentation of the evidence changed.

AWS includes duplicate-document resources within its CWI information [1], while ASNT describes digital document access through its badge system [2]. These are different issuer mechanisms. Use the process for the actual credential and avoid assuming that every newly downloaded PDF is a newly issued certification.

Define credential identity separately from file identity

A credential record should identify the person, issuer, program, credential number where available, and scope. A file record should identify the particular document version, date received, source, and status. Keeping these identities separate allows several files to support one credential without inflating the number of qualifications in a matrix.

Do not rely on the filename as the credential key. A person may upload certificate.pdf repeatedly, while the issuer may use a different filename each time a document is downloaded. The meaningful comparison occurs inside the document and its source metadata, not in the name chosen by the browser or sender.

Where an issuer changes a credential number, preserve the explanation and the relationship to the previous record. Do not assume that a changed number always means a new credential or that an unchanged number always means unchanged scope. The issuer's evidence and the responsible review determine how the records should be linked.

Compare a defined set of fields

Check the person's name, issuer, program, method, level, scope, credential identifier, issue date, expiry date, and any limitation. Compare attached schedules and reverse sides as well as the first page. A corrected name on page one can distract from a changed scope elsewhere in the package.

Record each material difference in plain language. Name spelling corrected, expiry unchanged is more useful than updated certificate. If a difference is only cosmetic, note that no substantive change was identified after review. Avoid asserting that two documents are identical unless the relevant content has actually been compared.

Use the comparison to decide which downstream records need updating. A name correction may affect profile display and search matching. A scope change may require a technical review. A new expiry may affect reminders. Updating every field automatically can introduce errors that were not present in either source document.

Keep originals and annotations distinct

Preserve the issuer's file as received. Add your review notes in the inventory or a separate controlled note. Do not place an internal approved stamp on the source PDF in a way that could be mistaken for issuer approval. If your organization marks controlled copies, make the origin and meaning of that marking explicit.

Retain the earlier version according to the applicable records policy and label it as superseded where appropriate. Historical evidence can explain why an earlier project review used a particular name, date, or scope. Removing it without a controlled retention decision can make that history difficult to reconstruct.

Avoid ambiguous filenames such as final-final or latest-new. A practical filename can include the internal record reference, issuer, document type, and received or issue date. Keep the filename free of unnecessary personal identifiers. The controlled index should indicate which version is active so the naming convention does not have to carry the entire process.

Handle corrections without changing the original claim

A corrected certificate may fix an administrative error while leaving the credential's scope and validity unchanged. Compare the actual evidence before altering the active record. If the issuer corrects a name, update the displayed identity and retain an appropriate link to the prior spelling for future verification questions.

Do not make your own correction directly on the certificate. Ask the issuer to provide the corrected document or written clarification. A local note can explain that an apparent typo is under review, but it should not conceal the fact that the official source has not yet been corrected.

If a correction affects a field already shared with a customer or employer reviewer, identify who needs the updated information. A quiet replacement in the internal folder may not correct the copy used in a proposal or assignment review. Record the distribution action through the organization's normal document process.

Work through a fictional duplicate and renewal sequence

Imagine a fictional coordinator receives three files for one technician. The first is an original credential PDF. The second is a replacement downloaded after the original was misplaced. The third arrives months later after renewal. The replacement repeats the original dates, while the renewal displays a new period.

The coordinator links the first two files to the same credential period and marks the usable replacement as the preferred document copy. The renewal becomes the current period after its contents are reviewed. The earlier period remains in the history. The matrix does not count three credentials merely because three PDFs exist.

Now suppose the renewal also changes a scope description. The coordinator routes that difference to the responsible reviewer instead of carrying the earlier matrix entry forward automatically. This shows why version control is more than tidying filenames: it protects the meaning of the qualification summary.

Resolve conflicts with the issuer

A replacement may conflict with a directory result or an earlier letter. Record the exact fields that disagree and consult the issuer through its official route. BINDT's PCN FAQ identifies a replacement process for its documents [3]. The relevant issuer is the right source to explain what its replacement represents.

Keep the disputed values visible in the review note until the issue is resolved. Do not choose the later expiry simply because it is more convenient, and do not assume that a directory always updates at the same moment as a document. Ask the issuer to clarify the current authoritative position.

When the response arrives, record the decision and update the active evidence link. If an issuer acknowledges an error, preserve its clarification with the corrected file. A later reviewer should be able to understand why the record changed without relying on a coordinator's memory of a telephone conversation.

Prevent duplicate rows from creating false reminders

Before adding a new record to a date tracker, search for the same person, issuer, program, and credential reference. A duplicate row can produce repeated alerts or conflicting status displays. Decide whether you are updating an existing credential period, adding a distinct method record, or creating a new period with a retained history.

If the application does not model document versions, keep the controlled version history separately. Update only the current values the application is intended to track. Do not represent a replacement copy as another active qualification just to preserve the file somewhere. The records system should reflect the evidence relationship, not the limitations of a convenient upload field.

NDT Connect's certificate manager organizes saved credential dates and uses profile records. It does not automatically authenticate duplicate documents or determine which version is authoritative. Review and correct the saved information deliberately, and do not assume an import or document-versioning workflow exists where the product does not provide one.

Control shared copies after a revision

Make a short distribution list for records that were supplied for a specific review. When a material correction occurs, determine which recipients need the replacement and why. Send or share it only through authorized channels. A broadly distributed personnel file should not be the default method of correcting a single field.

Label the replacement clearly and state which earlier copy it supersedes. Avoid language that implies the earlier qualification never existed if the change merely updates a renewal period. The recipient needs to know whether to replace a document, reconsider a decision, or simply update an administrative detail.

Keep a record of the correction's communication where it matters to your process. This need not be elaborate, but it should show that the operational user was informed. A correct central file does not fix a stale offline copy that continues to guide a staffing decision.

Keep an attachment relationship visible

If an issuer replaces only one page of a package, establish which unchanged pages remain part of the current evidence. A coordinator should not combine a new first page with an old schedule simply because both are available in the folder. Ask the issuer to confirm the intended package where the relationship is unclear. Record the complete set of active pages in the index, including page references or document identifiers. This makes it possible to provide a complete current package without accidentally attaching an obsolete restriction sheet or omitting a continuing limitation.

Distinguish identical files from equivalent evidence

Two files can contain the same credential information while differing in file size, download date, image quality, or layout. Conversely, two files with the same name can contain different scope or dates. Use file properties to help organize the review, but assess the visible credential content and source relationship before declaring that the evidence is equivalent. A duplicate-detection tool may identify matching files; it cannot decide what an issuer intended by a replacement or endorsement.

Record three separate observations when useful: exact file copy, apparently equivalent document content, and different document requiring review. The first concerns the stored file, the second concerns the information examined, and the third signals a substantive comparison task. Do not treat a different file hash or a newer download timestamp as proof of a new certification period. Equally, do not assume that matching titles establish equivalence when an attachment or limitation has changed.

Consider a fictional credential available as a wallet card, a full certificate, and a digital badge page. The three formats may refer to the same underlying credential but display different amounts of detail. Link them to that credential and describe their functions. If the card omits a scope attachment shown with the full certificate, retain the complete package for reviews that need that scope. The shortest format should not become the authoritative summary merely because it is easiest to email.

Choose a preferred copy based on readability, completeness, provenance, and the intended use. Record why that copy was selected. A clean issuer download may be preferable to a compressed photograph, but the photograph may still explain what a customer received earlier. Preserve historical relationships according to the applicable policy. The objective is a clear current evidence path and an understandable history, not the smallest possible number of files regardless of context.

Reconcile duplicates without erasing a review trail

Before merging duplicate index rows, list the references that depend on each row. An older row might be linked from a completed audit, a customer submission, or an archived personnel matrix. Deleting it without an explanatory link can break the history even if the current credential data is accurate. Decide which row remains active, which references need updating, and how a future reader will understand the retired identifier.

Prepare a merge note showing the two row identifiers, the evidence used to establish their relationship, the selected active record, and any differences preserved for review. If the rows represent distinct credential periods, do not merge those periods into one undated history. Connect them instead. If the rows represent the same period but one carries a clarification, keep that clarification with the surviving evidence set. Resolve actual conflicts before making the records appear identical.

Check notifications and summaries after reconciliation. A duplicate may have created two expiry entries, but removing one reminder record does not necessarily update a separate matrix or a previously downloaded spreadsheet. Identify the systems that were using the redundant row and confirm their current values. Do not assume NDT Connect performs this cross-system reconciliation; profile editing and the certificate manager should be checked against the reviewed source as part of the manual process.

Finish with a retrieval test that starts from both old and new references. An authorized reviewer following a historical reference should reach the relevant historical evidence or a clear note explaining its replacement. A reviewer starting from the active summary should find the selected current package without sorting through conflicting copies. This test confirms the purpose of duplicate cleanup: fewer ambiguous choices for current work, with enough traceability to explain why earlier records or decisions used a different document.

Audit versions with a small, meaningful sample

Select records with actual revision history: a changed name, a renewed credential, an added attachment, or a conflicting date that was resolved. Ask a colleague to identify the active version and explain the relationship to the older evidence. If the answer is unclear, improve the index and labels.

Check whether the active matrix, profile description, and reminder date agree with the reviewed current evidence. Differences can arise when one system is updated and another is overlooked. Assign an owner to reconcile them rather than treating the newest-looking screen as automatically correct.

Good version control produces a simple result: one clear current record for the stated purpose, a preserved explanation of material changes, and a history that remains accessible to authorized reviewers. It avoids both extremes of deleting everything old and keeping a folder of indistinguishable documents that no one can interpret.