Prepare for eCoC signing: people, permissions and certificates

Having a certificate file available is only one part of signing readiness. Your team also needs the appropriate permissions, the correct signatory information and an arrangement that fits the intended process. Addressing these points early helps prevent an otherwise prepared vehicle record from waiting at the final stage.

Separate record access from signing permission

Someone who can prepare or manage vehicle records is not necessarily authorised to sign them. Your company may assign preparation, review and signing to one person or distribute them across a team. Configure the responsibilities accordingly. Permission to sign and permission to submit to an authority should also be considered separately.

Set up the authorised person accurately

Review the person’s name, role, signing method and authorisation dates. The training example uses Emre Çetin as Homologation Responsible. It illustrates an authorisation record, not a completed signature. In your own workspace, the details should reflect the actual person and your company’s authorisation arrangements.

Review the certificate assignment

When using the PFX/P12 upload workflow, check the connection between the certificate and the intended authorised person. The demonstration uses a non-qualified training certificate. An active label or a selected security level does not, by itself, establish qualified status or acceptance by a receiving authority. Certificate suitability needs to be assessed separately.

Sign the current output, not an earlier version

Before signing, confirm that the vehicle record and generated output reflect the latest reviewed information. If a relevant vehicle detail or signing context changes, regenerate the output rather than reusing an earlier download. The objective is to ensure that the document being signed corresponds to the information your company has approved.

Keep signing readiness distinct from acceptance

This guide covers permissions and certificate preparation. It does not present the unfinished signing demonstration as a successful completed workflow. A personal electronic signature and an electronic seal associated with a legal person are different concepts; suitability depends on the applicable requirements. Obtaining a signed file and receiving authority acceptance are also separate milestones.

Let’s look at your workflow

Let’s review your authorisation, certificate and authority-connection requirements together, so signing preparation fits the rest of your eCoC process.

Discuss your workflow

Continue reading

• From vehicle data to eCoC XML: a practical workflow for manufacturers
• Use VECTO source data as part of eCoC preparation

Updated: 17 October 2026 · Electronic COC Platform