28 January 2026 · By Diego Aranha · 7 min read
The records officer doesn't need to know about cryptography. The records officer needs to know that a document signed today will still be defensible in fifteen years, when the certificate that signed it has long since expired and the certificate authority that issued it may not exist. That's the gap long-term validation closes. Everything else is plumbing.
Here's the rest of it, said carefully.
An electronic signature is, at the most elementary level, a cryptographic commitment by a private key to a hash of the document. To verify that signature later, you need three things: the document, the signature, and the public key (with its certificate chain) that the signer used.
That last piece is fragile. Certificates have expiry dates. Certificate authorities revoke certificates when keys are compromised. CAs themselves can wind down. Five years from now, the chain that secured today's signature may no longer be reachable, and a verifier asking "was this signature valid when it was made?" can't answer without the historical context.
Long-term validation freezes that historical context inside the signed document. At the moment the signature is applied, the platform also embeds:
Then, periodically — usually annually, before the embedded materials themselves expire — the platform re-timestamps the bundle. The new timestamp wraps the old one. The chain of trust keeps walking forward in time, leaving a verifiable trail that doesn't depend on any one CA still being around.
For audited records — engagement letters, board approvals, regulated contracts — the question that gets asked five or ten years later isn't "is this signature valid right now?" It's "was this signature valid at the moment the document says it was signed?" LTV answers that question with evidence that doesn't degrade.
Every signature applied through Documents Platform receives LTV-grade enrichment by default. Annual re-timestamping happens automatically; you'll see a small note in the audit log when it does. The format we produce conforms to ETSI EN 319 142-1 (PAdES B-LTA for PDFs) and ETSI EN 319 122-1 (CAdES B-LTA for CMS structures).
If you're migrating documents in from another e-signature service that didn't apply LTV, we can wrap your existing signatures in a fresh timestamp on import — preserving the original signature, its time, and its context.
LTV does not extend a signature's legal validity. That's a question of jurisdiction, signing intent, and the underlying contract. What LTV does is preserve your ability to prove the signature was valid at the time of signing.
If you'd like to walk through how this works against your records-retention policy, we're happy to take you through it.
Further reading: ETSI's standards portal publishes the EN 319 series. The European Commission's eIDAS overview is the friendliest entry point.