A certificate that moves successfully between systems still needs a reason to be trusted. For an aviation organisation receiving a digital training document, the useful question is what evidence survives the transfer: who issued it, whom it concerns, whether it has changed and whether it remains suitable for the intended use.

A maritime initiative offers a useful example of that distinction. It does not establish an aviation acceptance rule or prove that every certificate platform can exchange trusted records today.

What is announced, and what is reported

BIMCO's announcement of its Seafarer Digital Certificates Charter describes a framework for digital certification and an interoperability pilot. Interoperability means that different systems can exchange information and interpret it consistently. The announcement establishes the initiative, rather than the outcome of the later exercise.

Smart Maritime Network reported on the pilot on 20 October 2026. According to that reporting, platforms exchanged certificate information using artificial test data, while trust in issuers and certificate status remained issues to address. The publication describes the result as “technical feasibility rather than universal plug-and-play” interoperability: some exchanges needed advance coordination or adjustments specific to the systems involved. The pilot's results are known here only through this report, so they are used as a reported example, without extrapolating a universal success rate or a ready-made aviation solution.

The editorial lesson is narrower and durable: receiving the information and accepting it as evidence are separate decisions.

A file can arrive without its reasons for trust

Imagine receiving a training record from another organisation. The name and course title display correctly. That answers a transfer question: the receiving system can read the fields.

It does not yet establish that the identified organisation issued the record, that the file is unchanged or that the record applies to the person presenting it. Nor does it settle whether that training meets the requirement for which it is being offered.

The W3C Verifiable Credentials Data Model separates verification from the decision to trust a claim. A verifiable credential is a set of claims with a mechanism for checking their origin and integrity. Those technical checks do not establish the truth of every claim or oblige a receiver to accept the issuer. This is a general design principle, not evidence that the maritime pilot used this particular standard.

Ask what survives the handover

A receiving organisation can use the following checklist when assessing a proposed certificate exchange. It is a decision aid, not a replacement for the rules governing a particular qualification.

QuestionEvidence to seekWhat an unresolved answer means
Who issued the record?A verifiable connection to the claimed issuerA displayed name or logo remains an assertion
Is that issuer appropriate for this purpose?The applicable recognition or authority, where requiredAuthentic origin alone does not establish acceptance
Is this the same document?An integrity check covering the relevant contentReadable fields do not prove the original remained unchanged
Does it concern this person or object?A reliable match to the subjectA genuine record could belong to someone else
Is its status suitable now?Relevant dates and an authoritative status source where applicableA previous result does not automatically answer today's question

The receiver should preserve the meaning of each check. A status field that means “not revoked” cannot silently become “approved for every use”. Where the source cannot answer a required question, retain that uncertainty instead of converting it into a positive result.

A training record that changes employers

Illustrative scenario, not a real customer case: an employee moves to another aviation organisation and brings a digital training certificate. The new employer imports the record, and its system displays the employee's name, course and completion date.

The employee benefits from avoiding repeated manual entry. The employer still needs to establish the source and integrity of the document, match the record to the employee and decide whether the training meets its requirement. If a current-status check is required but unavailable, the import should not be presented as completion of that check.

This is where a clear handover helps. Record which evidence was supplied, which checks were performed, when they were performed and which question remains open. Our guide to checking a certificate's current status explains why an unchanged file and an up-to-date status answer are different things.

Portability should include the ability to check

A portable document should not depend solely on a screenshot of a green result in its former platform. A new receiver needs a way to examine the evidence and understand the limits of the result.

When discussing a migration or exchange with a provider, ask:

  1. What will the recipient receive besides the visible document?
  2. Which checks can the recipient perform without the sender's account?
  3. Which checks still depend on an external service, and what happens when it is unavailable?
  4. How are corrections, replacements and withdrawals distinguished?
  5. What information is disclosed, and is it necessary for this receiving decision?

These questions apply whether the exchange uses a downloaded file or a connection between services. The transport method does not determine the issuer's authority. Our discussion of verification without the original platform develops the continuity question.

Keep the acceptance decision explicit

A procurement demonstration should show more than a document appearing on another screen. Ask the demonstrator to show the evidence behind its origin, the subject match, the meaning and freshness of any status result, and an unresolved case.

For example, a withdrawn record should produce a clearly different outcome from an unavailable status source. Both may prevent immediate acceptance, but they call for different next steps. Preserving that difference is part of a useful exchange.

The maritime report is a prompt to ask better questions about portability. For aviation, the practical aim is a handover in which the receiving organisation can explain what it checked and why the evidence supports its particular decision.

Sources