Build · Guide

Evidence file checklist for a simple electronic signature

If a signature is contested, a judge reads the evidence file your tool produced, sometimes line by line. This page turns that into a checklist for the DocuSeal setup: what each requirement is, what the setup gives you, and what you still have to do.

This is the Build stage, after the DocuSeal tutorial. It is engineering guidance, not legal advice. Have your legal counsel review the result for the jurisdictions you operate in.

1. Why the evidence file matters

With a simple electronic signature, the signer’s identity is not backed by a certificate that a trust service provider issued after checking an ID. When the signature is contested, you have to show who signed, that they agreed, what they signed, and when. The evidence file is how you show it.

The recipe splits this into two chains: identity and consent, and integrity and date. DocuSeal covers much of both chains out of the box. The parts it does not cover are mostly decisions about how you run it.

Courts have set aside evidence files for small, avoidable reasons: a file that did not repeat the contract reference, a log that recorded a local address instead of the signer’s, a one-second difference between the document’s time and the log’s time, a log that was unreadable for a non-specialist. None of these is a cryptography problem. They are design and operation problems.

2. The checklist

The third column says what this guide’s setup gives you. Recorded means the DocuSeal tutorial produces it. Check means you must confirm it in your own instance, because this guide has not verified it. You add means the setup does not provide it.

Requirement Why it matters This setup What to do

Tie each signature to a documented means of identification, not just a signed-in session

The signature must be attributable to a person. An email address alone is a weak link if the mailbox is shared.

Recorded: link to a unique email address (step 7 of the tutorial)

Write down, in your procedure, that identification is control of a corporate mailbox. For higher assurance, add a one-time code (DocuSeal Pro) or move up a tier.

Record who carried out the identification

The log should say whether your company or a provider checked the signer.

You add

State it in your procedure. For internal use it is your organisation, through the provisioned mailbox.

Prove each invitation or code was sent, and to whom

If you cannot show where the link went, the identification is unsupported.

Check: the audit log records the email address and times

Keep your mail relay’s delivery logs. Confirm the invitation event appears in the audit log of a test submission.

Show the document before the signature can be activated, then record the explicit action

Consent is a decision to sign a specific document. Typing a code is not consent.

Recorded: signer sees the document, ticks the consent checkbox, then signs (step 6)

Keep the wording of the consent text and the privacy notice you used, with their dates.

Repeat the contract reference in every event and in the signed document

Files that did not match the document’s reference have been rejected.

Check

Decide which reference identifies a transaction. Make sure it appears in the PDF itself and in the audit log. If the audit log does not carry it, add it as a field in the document.

Date the document and the log from one reliable clock, and timestamp the key steps

A small time gap between the contract and the log is enough to be challenged.

Recorded: RFC 3161 timestamp on each signed PDF and on the audit log (step 5)

Synchronise the server clock with a reliable time source. See running it for real.

Record the version and hash of every document shown, including annexes

You must be able to show exactly what the signer saw.

Check

Put every annex in the signed PDF. Record the SHA-256 of the final PDF in your own system when the submission completes.

Record the signer’s real IP address and link it to their identifier

Behind a proxy, applications often log the proxy’s address or 127.0.0.1.

Check: recorded, but the value depends on your network setup

Test it from another device before go-live. See running it for real.

Seal and timestamp the log at the end of the transaction

A log that can be edited afterwards is weak evidence.

Recorded: the audit log PDF is sealed and timestamped (step 9)

Keep the audit log PDF with the signed document, never one without the other.

Produce a summary that a non-specialist can read

A judge does not work from raw event rows.

Check: the audit log PDF is the readable record

Read your own audit log PDF as a stranger would. If it is not clear, add a one-page summary to the case file.

Limit what you collect and set a retention period

The file contains personal data: name, email, IP address.

You add

Define what is kept and for how long. See running it for real.

3. What to keep for each signature

Store these together, under the same transaction reference:

  • The signed, sealed and timestamped PDF.

  • The audit log PDF.

  • The consent text and privacy notice, with the version or date the signer saw.

  • The invitation email text and the mail relay’s delivery record.

  • The SHA-256 of the final PDF.

  • The root certificate that the seal chains to, and its SHA-256 fingerprint, so the seal can be validated years later.

  • A short description of your setup at that date: DocuSeal version, the timestamp server used, the signing certificate used.

  • Your written procedure: how signers are identified, who is responsible, how long files are kept.

4. Review a test signature like a judge

Before you use the setup for real documents, run the smoke test from the tutorial with two other people, then read what you have as if you were challenging it.

  1. Open the signed PDF in a validator. Does it show the seal and the timestamp? Does the document report as unchanged?

  2. Open the audit log PDF. Can you tell, without help, who signed, when, from which address, and after seeing what?

  3. Is the IP address in the log the signer’s, not your proxy’s?

  4. Do the contract reference, the document and the log agree?

  5. Compare the time in the document with the time in the log. Is the gap acceptable?

  6. Can you retrieve the consent text the signer saw?

Any "no" is a change to make before go-live.

5. What an SES does not give you

An SES gives procedural evidence, not cryptographic proof of identity. The seal shows the file has not changed since sealing. It does not show who the individual signer was. That is why this page matters: with an SES, the evidence file is your case.

If your documents need to stand up to a harder challenge on identity, use a higher tier. An advanced signature ties the signature to the signer with a certificate. A qualified signature requires a certificate from a qualified trust service provider, and a self-hosted setup cannot produce one by itself. See choose your setup for how these tiers fit.

Are you looking to strengthen the evidential value of your electronic signatures?

Tell us more