Aback Sign
Sign documents. Automate agreements. Keep control.
Send a PDF, choose who signs and in what order, and get back a final PDF with a completion certificate and an evidence trail you can check. Recipients sign for free, with no account.
Free plan included. No card needed to start.
From PDF to signed record in four steps
- 1
Upload a PDF
We check the file before storing it and keep an exact, unchangeable copy with its SHA-256 digest.
- 2
Add people and order
Signers, approvers and copy recipients. Let everyone sign at once, or set the order they go in.
- 3
Place the fields
Drag signature, initials, date, text and checkbox fields onto the pages, assigned to each person.
- 4
Track and download
Follow each person's progress, then download the signed PDF, a completion certificate and the evidence file.
Built around the signing transaction
Correct documents, the right people, explicit consent and durable evidence come before everything else.
Parallel or in order
Sequential routing invites the next person only when the previous step is done. Parallel invites everyone at once.
Type, draw or upload
Recipients adopt a signature once in the browser, on any device, with no account and no download.
Extra checks when it matters
Ask a recipient for an access code you share separately, or a one-time code sent to their inbox.
Explicit consent
Every recipient reads and accepts a versioned disclosure before acting. The exact version is recorded.
A complete completion package
The flattened final PDF, a certificate of completion and a structured evidence file, stored before anything is marked complete.
Honest status
Email accepted by the provider is shown as exactly that. We never mark something sent just because a request returned.
Evidence you can check yourself
Every envelope keeps an append-only trail of what happened and when: invitations, link opens, verification, consent, each submission and finalization. At completion the trail is chained by SHA-256 and sealed into the evidence file, and the certificate records the digests of the original and final documents.
- SHA-256 of the original upload, frozen at send
- SHA-256 of the final PDF, certificate and evidence file
- Hash-chained audit events, so later edits are detectable
- A public check page that hashes files in your browser
What the evidence does not claim
A digest proves that a file is byte for byte the one we produced. It does not prove who someone is, what they intended, or that a signature is valid for a particular document under a particular law. Device details are context, not identity. We state these limits on every certificate, because trust depends on not overstating what the record shows.
Made for people who sign every week
Freelancers and independents
Proposals, contracts and statements of work, signed without chasing printouts.
Founders and small businesses
Offer letters, NDAs, vendor agreements and approvals with a record you can find later.
Agencies and consultants
A shared workspace with roles, so the team sends while owners keep control of billing.
Questions, answered plainly
Electronic signatures are recognised for many documents in many countries, but not for every document everywhere. Whether an electronic signature suits a particular document depends on the law that applies to it. Aback Sign records consent and an evidence trail; it does not give legal advice. Check with a lawyer for documents that need a specific form.
Send your first document in a few minutes
Create a free account, upload a PDF and send it. Your recipients only need an email address.
Create a free account