All docs

Electronic signing

Ask people to sign a PDF or a document made from a response with a simple electronic signature: email-verified signers, fields, signing order, reminders, a frozen package, completed files and an evidence record.

Updated . 13 min read.

Send a PDF, or a document made from a response, to one or more people and collect their signatures. Each signer opens a personal link, confirms their email address with a code, reads the exact document, states their intent and signs by typing their name or drawing it. When the last required person has signed, Formspring prepares the completed files and keeps the record with the request, the response and the contact.

What this is, and what it is not. Formspring provides simple electronic signatures. A signer is identified by control of the email address the invitation went to: they enter a one-time code sent to that address before they can open or sign the document. Qualified identity verification is not included, and a signature made here is never described as a qualified signature. Whether a simple signature is enough for a given contract depends on the document and the law that applies to it. If in doubt, ask your legal adviser.

Signing is included with the Scale plan, with a monthly allowance. See Plans and allowances.

How it fits together

You want to Start here
Get a PDF you already have signed Create a signing request
Turn the answers of a response into a document to sign Use a template
Know what your signer goes through Recipient verification
Fix a request that is already out Correct a sent request
Have two or more people sign in turn, or copy someone in Signing order
Keep the signed record Download the signed document and evidence
Work out why a signer did not get the mail Failed delivery
Know how long records are kept Retention

Open Documents in the workspace navigation to see every request in one place, with the views All documents, Needs attention, Awaiting signatures, Completed and Templates.

A request, step by step

  1. Document. Upload a PDF, or start from a response and a template. A document must be checked and ready before it can be sent.
  2. Recipients. Add the people who sign, their order, and anyone who only receives a copy.
  3. Fields. Place signature, initials, name, date, checkbox and text fields on the pages and assign each to a recipient.
  4. Settings. Choose the deadline and whether signers may ask you to hand the request on.
  5. Review. Formspring shows what will be sent, to whom, what it uses of your allowance, and anything that still blocks sending, with the step that fixes it. Send for signature stays disabled until nothing blocks it.

A request that is not ready stays a draft you can come back to. Sending freezes it.

Before the first request goes out, Formspring needs to know who is sending: your own email address must be confirmed, or your workspace needs a verified sending domain. A young workspace can invite a limited number of people per hour and per day.

Fields

Field What the signer does
Signature Types their name or draws it. Typing always works, so signing never depends on a mouse or touch screen.
Initials Types or draws their initials.
Name Starts with the name you entered for them and can be corrected. It is recorded as the name the signer declared, not as a checked identity.
Date The date of signing, set by Formspring on the server (UTC), never by the browser.
Checkbox Ticks it. A required checkbox must be ticked.
Text Types a short answer, up to the length you set. A text field can be restricted to letters, digits, an email address or a phone number.

Every rule is enforced on the server, not only in the page: a required field left empty, an answer that is too long, or a field that belongs to someone else is refused. Place fields by dragging them, or by typing the page and position, so the editor works without a pointer too. A field that would sit outside its page or on top of another field is flagged before you can send.

A previous signature is never reused. Each signer makes a new, explicit signing action on each request.

What the signer sees

A link on its own shows nothing: no document, no title, no sender and no list of signers. The signer asks for a code, we email it to the address the invitation went to, and entering it opens a short-lived session in that browser. The code works for 10 minutes, 5 wrong tries lock it, and the same code cannot be used twice. The session ends after 30 minutes without activity, after 8 hours at the longest, or as soon as the request is signed, declined, voided or expired.

Then the signer sees the exact document page by page, goes through the fields that are theirs, and reads the consent statement ("I intend to sign this document electronically and confirm the information I entered."). Only then does Sign and submit work. The signer never has to accept marketing to sign. The page works with a keyboard and a screen reader.

Opening the link in a mail scanner or link previewer changes nothing: only the signer's own action can verify, sign or decline. A recipient needs no Formspring account.

If other people still have to sign, the signer sees "Your signature has been recorded. We will notify you when everyone has signed." The page says the request is completed only after the completed files exist. See Recipient verification for the details.

Links are personal and work for 48 hours, never longer than the request itself. A request stays open for 30 days unless you set another deadline, up to 365 days. A signer whose link ran out can ask for a new one on the page, and each new invitation or reminder replaces the previous link. Requests sent before the email code existed keep working with their link; every new request uses the email code.

One package, exactly as signed

Sending freezes the package: the document, the pages in order, the field layout, the recipients and their roles, the consent wording and the signing settings. A digest of that package is recorded, and every signature is bound to it and re-checked at each step. A signature records who signed, which package, which field values and which consent wording was shown.

Because the package is frozen, editing the response afterwards does not change or cancel a request that is out. Everyone signs exactly the document that was sent. To change something, make a linked replacement: see Correct a sent request.

Signing order, groups and copies

Recipients belong to ordered groups. Everyone in a group signs independently. The next group is invited only when every required signer of the earlier groups has signed. A countersigner is an ordinary signer in a later group, verified like everyone else: there is no sender bypass. A copy recipient receives the completed files and cannot sign. The same email address cannot be added twice unless you confirm that it is meant to appear in two roles. See Signing order.

Reminders and deadline

Formspring reminds signers who have not signed: first after 3 days, then every 3 days, at most 3 times per signer, and never once they have signed or declined, once the request has ended or expired, or when their mail bounced. In an ordered request only the people whose turn it is get a reminder. Automatic reminders can be held back during quiet hours in your workspace time zone. You can also press Send reminder; a signer waits an hour between manual reminders, and a manual reminder does not use up the automatic allowance. Resending an invitation does not refill the reminder allowance.

When a request is voided or expires, the people who were waiting to sign get a short notice that their link no longer works.

Decline and hand over

A signer can decline with an optional reason. Declining closes the request, every other link stops working and you are told by email. A declined request cannot be reopened: make a new one.

If you allowed it, a signer can ask you to hand the request on to someone else, with a name, an email address and a reason. Nothing changes until you decide, and the signer cannot change the recipient or carry on silently. If you approve, a new linked draft replaces the original with the new person in the signer's place, and the original is voided; you review and send the new request. Nothing signed so far carries over to it. If you decline, the signer can sign as planned. The history records the proposed address only as a hash.

Delivery

Each recipient shows where their invitation and reminders stand, separately from the status of the request: queued, accepted by the mail service, delivered, bounced, suppressed, failed, or outcome unknown. "Accepted" means the mail service took the message; "delivered" comes from the service. Opening an email is never reported and never counts as review. A bounce or spam complaint is written to the request's history, and a complaint pauses new signing requests for the workspace until it has been reviewed. Requests that are out and every record stay as they are. See Failed delivery.

Finishing a request

When the last required person signs, the request moves to Finishing up and Formspring builds the completed files: it assembles the signed PDF and the evidence bundle, checks their digests, and only then marks the request Completed and tells everyone. A signature is never lost if this takes longer:

What you see What it means
Finishing up Every signature is recorded and the files are being prepared. Usually a short wait.
Finishing up, retrying An attempt failed and will be retried automatically.
Needs attention The automatic attempts are used up. The signatures are safe and the history is intact. Contact support with the reference shown on the request.
Completed Final files exist and match their digests.

A request is announced as completed once, and only after its files exist. A request that is finishing up cannot be voided. If you have push or browser alerts on, you get a generic alert, "A signing request needs attention", when a request needs attention, a message to a recipient failed, or a recipient asked to hand the request on. It names no document or person; opening it asks you to sign in with access to the request.

Completed files and evidence

Everyone who signed gets an email with a link to the completed document. Nothing is attached, and the email shows no other signer's address. The link asks the signer to confirm their email address with a new code, then offers the signed PDF and a short summary through download links that work for a few minutes. Every download is recorded in the history. A declined, voided or expired request shows a status page only.

Your team downloads the signed PDF and the evidence bundle from the request. See Download the signed document and evidence.

Every step is written to an append-only history in which each entry contains the fingerprint of the one before it, so a changed or removed entry can be detected. The request shows History intact, or the first event where the history was altered. The visible mark on the page is a representation of the signature; the history and the manifest are an application record. They are not an independent timestamp or seal.

Contacts, automations, events

A recipient is linked to a contact only by the exact address they verified, never by a company domain or an address nobody confirmed. A role or title a signer states while signing is stored separately and always labelled as claimed by the signer. Signing appears on the contact's timeline. Erasing a contact unlinks the recipient and never deletes the signed record.

Automations can start from signing events (created, sent, recipient verified, recipient signed, completed, declined, expired, voided, delivery failed, finishing failed) and can prepare a draft from a response, ask a person to review it, send it, remind, void and tell an existing connection that a request is complete. A completed signature never approves a payment, a refund or a project by itself. Events carry no document and no signature.

Retention

Drafts, unfinished requests and completed records follow a retention policy, and a legal hold keeps one request out of every deletion. See Retention.

Plans and allowances

Plan Signing requests per month
Free Not included
Pro Not included
Team Not included
Scale 750

A request counts once, when you send it and the invitations are queued. A recipient who does not get the mail, a reminder, a resend or a replacement of a failed delivery does not count again. A replacement request is a new request and counts when you send it; the review step tells you before you send. A request that cannot be prepared or sent does not count. Downloading records you already hold does not need a plan with signing.

Safety limits per request: up to 10 signers and 10 copy recipients, 100 pages, 20 MB per PDF and 200 fields. They protect the service and may change.

Permissions

Permission Allows
documents:read See documents, requests and their status
documents:create Upload and prepare requests
templates:manage Create, publish and archive templates
signing:send Send, remind, replace and approve a drafted request
signing:void Void a request
signing:export Download the signed PDF and the evidence bundle
signing:settings Retention periods and legal holds

Administrators have all of them. Editors can read, prepare, send, remind, replace and void. Viewers can read. A staff member cannot sign for a customer, whatever their permissions.

API and agents

Everything a person can do on the sender side, except signing, is available over the API and to agents through the MCP server: list and filter requests, create a draft, place fields, check readiness and preview, send, remind, void, replace, decide a hand-over request, verify the history, and download the signed PDF and the evidence (an agent gets a short summary and a reference, not the file). Approving a draft that an automation prepared is done by a person, in the dashboard or over the API; no agent tool approves it. A token must carry the ability as well as the member holding the permission. Sending is a high-risk action that an agent has to confirm. No tool and no endpoint signs, records consent or verifies a recipient on anyone's behalf.

Errors use stable codes such as revision_conflict (the request changed, read the current version first), recipient_not_active, request_expired, request_voided, artifact_pending (the completed files are not ready), quota_exceeded and preparation_failed. A send or a replacement can carry an idempotency key, so repeating the call sends once.

A signing request outlives the response it was made from. After a response is deleted the signed request is retained under your retention policy and stays available by its own id, in the same project.

Limits of the evidence

Formspring records that a person with control of an email address chose to sign a specific frozen package at a specific time, with the consent wording they were shown. It does not verify a government identity, it does not check that the signer may bind an organisation, and it does not add a qualified timestamp or a seal. The history also records the network address and browser details of a signer's own actions as context. They do not prove who someone is. Higher-assurance signing by an outside provider is not available.