Evidence that travels with the document.
A signed PDF is only as useful as your ability to show how it was signed. When a SignAndGo envelope completes, the PDF carries its own evidence: an audit certificate on the final page, a timestamped audit trail behind it, and a verification ID under each signature that anyone can check without logging in.
The three parts of the record
- Audit trail. The timestamped log kept with the envelope: each email address a link went to, each view, each signature, approval or acknowledgement, and the IP address used at each step.
- Audit certificate. A page appended to the signed PDF summarising the document, the people involved and when each of them acted.
- Verification ID. A short reference printed beneath each signature, with the address of the public verify page beside it.
Checking a document you were sent
The value of the verification ID is that the person relying on a document does not have to take anyone's word for it. A lender in Glasgow, a new landlord in Bath or a buyer's solicitor can check it themselves.
- Find the verification ID printed beneath a signature on the PDF.
- Open the verify page named beside it and enter the ID.
- Compare what it shows, including the document title, its status and the signers with email addresses partly hidden, against the copy you hold.
If they match, the copy came from a completed envelope. If the ID is not recognised or the details differ, ask questions before relying on it.
When the record earns its keep
Someone says they never signed
The certificate shows which email address received the link and when the signature was made, which often settles the matter quickly.
A page looks different
Completed documents are sealed so that later changes can be detected. An edited copy will not match the original record.
Your auditor asks for evidence
Rather than gathering emails and screenshots, you hand over the signed PDF. The steps are recorded inside the file.
The person who sent it has left
The evidence sits with the envelope and on the PDF, not in a former colleague's inbox.
A worked example: a contractor's schedule checked by a payroll provider
Imagine an IT contractor in Reading who has signed an assignment schedule with a consultancy. The contractor and consultancy are invented for illustration. The contractor's payroll provider asks for a copy and wants to know it is genuine. The contractor emails the PDF. Someone at the provider reads the verification ID under the signatures, enters it on the verify page and sees the schedule's title, a completed status and two signers matching the PDF. They file it and carry on, without needing to contact the consultancy.
Good habits for your own files
- Download each completed PDF with its certificate and keep it where your business keeps contracts.
- Keep the certificate attached. Separating it from the document weakens the record.
- Share the downloaded PDF rather than a scan of a printout, which loses the verification details.
- Show colleagues who receive signed documents how to use the verify page.
- Keep the original PDF unaltered, and save any annotated copy separately.
What the record does not prove
An audit trail is strong evidence of what happened within SignAndGo, and it is worth being honest about its edges. It shows which email address received a link and what was done with it. It cannot show who was holding the device, and it cannot show whether the signer understood the document. Where those matter, add a step at the start: a witness who confirms identity, an approver who checks the document first, or a conversation before you send. Whether your document needs anything more as a matter of law is a question for your adviser; see documents that need more.
What someone checking the verify page sees
A person who enters the verification ID sees the document's title, its status, the verification ID itself and who signed. They need no account, and the page does not show the contents of the document. If the document has since been erased by its owner, the page says so plainly, rather than behaving as if it never existed.
Habits that weaken a good record
- Printing the signed PDF, signing it again by hand and scanning it back in. You end up with two versions and a weaker record than the one you started with.
- Keeping only the signature pages. The certificate is part of the file, so store the whole PDF.
- Sending to a shared mailbox such as accounts@ when a named person is meant to sign. The record shows the address used, not who was sitting at the screen.
- Working on the only copy. If you need to annotate or extract pages, do it on a duplicate and keep the original untouched.
Scotland and Northern Ireland
An audit trail is evidence of what happened, wherever the signer happened to be. Whether that kind of signature suited the document is a separate question, and Scotland and Northern Ireland each have their own rules on how documents are signed. Ask a solicitor in that nation, and see Scotland or Northern Ireland.
Documents are kept securely on Google Cloud, encrypted at rest and in transit. For the detail behind each recorded event, read audit trails explained, and for wider security questions see security questions.
Frequently asked questions
- Does someone checking a document need a SignAndGo account?
- No. The verify page is public. They only need the verification ID printed on the signed document.
- What does the verify page show?
- The document title, its status and the signers, with email addresses partly hidden, so the details can be compared with the copy in hand.
- Where is the audit certificate?
- It is appended to the signed PDF, so it travels with the document.
- Does the verify page show the document itself?
- No. It confirms the details of the signing, such as the title, the status and the signers, without showing what the document says.
See SignAndGo for your team
Send your first envelope in a few minutes, and keep every signed copy with its audit trail.
See how it works