Signing guides
After signing a PDF: download, check and save the audit record
“Signed” is the start of filing the result, not the end. Download the completed version, check it opens correctly and keep its record beside it. An invitation email or a temporary browser link is a poor substitute for a copy you can actually retrieve.
DocAISign paid checkout is not currently enabled. Self-signing is free; check your available sends and the Pricing page before planning a request.
Download both records from the completion page
DocAISign offers Download signed PDF and Download audit record after completion. For a completed request, it also sends those attachments to the sender and recipient. Save the files themselves rather than only bookmarking the signing link.
Open the signed PDF and check every page, including the signature/date fields. Confirm it is the completed file rather than the unsigned upload or an earlier request. If an email is missing, use the available completion downloads while the files remain accessible.
Use a simple filing convention
Put the final PDF and its audit record in the same controlled folder, with a document reference and a clear completed-version label. Keep an unsigned source separately. A shared filename such as “document-final-final.pdf” does not reliably distinguish several requests.
If you need to share the completed result, send the intended files through an appropriate channel. Do not post the private signing URL. Consider who should see the audit too: it can include email addresses, IP addresses, browser information and event times.
Understand what the audit describes
The DocAISign audit includes a document reference, file fingerprints, signature details and a timeline labelled UTC. Use that time zone when comparing an event with a local email timestamp; different clock displays need not describe different events.
A drawn or typed mark, an email address and an IP record are not formal identity verification. DocAISign does not provide certificate-based digital signatures. The audit documents activity in this workflow; it is not a guarantee that a particular recipient or organisation accepts the method.
Compare the signed file’s fingerprint when needed
The audit lists a SHA-256 value for the signed PDF. Computing SHA-256 for the exact downloaded bytes lets you compare that copy with the listed value. Matching values indicate matching file content for this check; they do not establish who signed or whether an agreement is valid.
Use the signed-file entry, not the original-upload entry. If you print to PDF, compress, annotate or resave the file, its bytes may change. Keep the downloaded completed original before making any working copy. The audit itself includes Windows and macOS/Linux hash commands.
Check retention before relying on a link
Review the Privacy page for the current file-retention policy. Automatic deletion can remove downloadable files even when audit records are retained. Do not wait until a document link stops working to discover that your own copy was never saved.
A closed invitation and deletion are different events. Files already downloaded or delivered as attachments can remain with recipients. Keep records according to your own needs and agreed process, rather than assuming application deletion recalls every copy.
Before sending the result onward
- The completed PDF opens and contains all required pages.
- The associated audit refers to the intended document and signed file.
- The stored source and completed version cannot be confused.
- Access to the files matches the people who need them.
- For separate fax delivery, use the completed PDF and retain the fax service’s available delivery report.