Collect the answers and
signature in one step

Collect form responses and signatures in a single step, automatically generating signed, tamper-evident PDFs without chasing signers for second-round approvals.

Free account · No credit card required

See how a form signature reaches the PDF

Draw in the field below and the same mark appears in the document preview. This demo stays in your browser and uploads nothing.

Add a signature to the form

Use a mouse or finger. With a keyboard, focus the pad and press Enter to use the full name. This demo sends nothing from your browser.

Signature
Signature drawing area
Sign here

Signature empty.

Preview the generated document

The signature appears in the position mapped on the template.

consent-form.pdf

Treatment consent

I confirm that the procedure has been explained to me, that I have had the opportunity to ask questions, and that I agree to go ahead on the date arranged.

Signature
Alex Rivera
Printed name

Awaiting signature

Trusted by teams at

From an empty form to a signed document

1

Place the form and document fields

Add a signature field to the form, then place its matching element on the document template. That mapping determines where the captured mark appears. The name, date, and other answers can be mapped beside it, so the signer sees one form while the recipient receives a structured document.

2

Give the signer a way in

Share a link, embed the form in a page, or open it on a tablet at a desk. The signer can use a finger, stylus, or mouse.

3

Route the completed document

Submitting renders the document with the signature and printed name in place, ready for S3, GCS, a webhook, or an inbox. The output stays connected to the submission that produced it, which removes the guesswork of matching a downloaded signature to the correct set of answers.

Decide whether you are creating a document or sending one

Send for signature

The document already exists

A completed contract needs to reach another party for review and signature. Dedicated signing platforms are designed for that ceremony, especially when the document moves between companies. They are the better fit when recipients need invitations, reminders, negotiation, or the provider's own completion record around an existing agreement.

Trigger that process from a submission through DocuSign, Adobe Sign, SignNow, RightSignature, Box Sign, or SignRequest.

Create with a signature

The answers produce the document

A patient gives consent, a parent authorizes a trip, or a customer accepts a quote. The document does not exist before that interaction; the answers and signature are the data that create it. Making the signature a form field keeps those inputs in the same submission instead of asking staff to compare a signed file with a separate intake record.

This workflow removes the separate collect, generate, and send-for-signature handoffs.

Workflows that do not need a second signing round

Consent before an appointment

Collect treatment consent, a photography release, or a liability waiver while someone books. The completed PDF is ready before the appointment instead of becoming paper that staff must print, scan, and match to a patient.

Parental authorization

Let a guardian complete trip permission or medical authorization on a phone. The school receives a PDF on its own letterhead without sending paper home and waiting for it to find its way back.

Accepting a quote

A customer chooses options, sees the total, and signs the result. The accepted quote is generated from those same choices, avoiding a separate document version that can drift from what the customer approved.

Delivery and collection

Capture a signature at the door on a driver's tablet and create proof of delivery for the matching order. Each stop produces its own completed document before the driver returns to the office.

Membership and enrollment

Collect personal details and agreement to the terms in the same gym, club, or course enrollment. The signed document can go directly to the member record instead of an inbox someone has to reconcile later.

Field and site sign-off

Have the person on site sign an inspection or completion report while the work is still in front of them. The report leaves the site complete instead of waiting for an office step days later.

Hand off to an approved signing provider when needed

Some counterparties require the platform their legal or procurement team already approved. Six provider connections let you collect the information and generate the document here, then send it through that required signing process. This keeps the handoff explicit: the form owns data collection, the template owns document creation, and the connected provider owns the signing ceremony its users expect.

  • DocuSignWidget on the form, or triggered from a submission
  • Adobe SignWidget on the form
  • SignNowConnector
  • RightSignatureConnector, with send-template on new submission
  • Box SignConnector
  • SignRequestConnector

Bring the signed file back into the workflow instead of leaving it in a provider inbox. Attach it to the right Salesforce record, post it to a webhook, or place it in your own storage bucket. The destination is part of the submission flow, so staff do not have to download the result, rename it, and upload it again before the system that owns the record can use it.

Keep the record around the signature

The drawn mark is only one part of a useful record. When someone later asks who signed, when the event happened, or whether the file still exists, the surrounding submission and audit history provide the answer. Keeping those pieces together also makes routine support questions easier: staff can start from the submission instead of searching storage, an inbox, and a signing account for versions of the same document.

Append-only audit events

New events are added rather than rewriting earlier ones. Search, filter, and export the history when you need to understand how a submission moved through the workflow.

Retention, deletion, and legal hold

Set retention and deletion as policies instead of relying on manual cleanup. A legal hold can suspend deletion for the records it covers without changing every other record.

Zero-retention document processing

Use secure mode and zero retention when documents must not remain in managed storage, with purge timing set for the workflow.

Named internal users, external signers

Your identity provider names the internal people who configure the form and work with its submissions. Public respondents and anonymous signers do not consume seats.

Prevent an unsigned form from entering the workflow

An optional signature field creates incomplete submissions that someone must chase. Make it required and the form cannot advance until the respondent supplies the mark.

? Their record Your storage
  1. Place the signature inside the document. Its template element sits alongside the name and date, so the finished PDF carries the mark in the intended position rather than as a separate attachment.
  2. Let people use the device already in their hand. A signer can draw with a finger on a phone, a stylus on a tablet, or a mouse on a computer. The smooth signature variant fits the stroke as it is drawn.
  3. Ask the right person to sign the right content. Conditional logic can request a guardian for a minor but not an adult. The document can follow the same branch, allowing one template to cover both cases.
  4. Create the completed document on submission. The answers and signature produce the file together, removing a later generation step and the reconciliation it creates. One finished document counts as one render.

Offer a fillable PDF when a web form does not fit

A contractor may work without a connection, or a client may need a file they can forward. Generate a PDF with real form fields instead of flattened boxes so they can complete it in Acrobat, Preview, or a browser and return the file through their usual process. The offline route preserves the document layout; the responsive web route is available when entering data directly on a smaller screen is easier.

Complete the same document online or offline

A browser submission returns structured data, while an offline recipient returns the completed file. Both routes use the same document design.

Reuse an existing PDF layout

Upload an existing PDF, detect its fields, and correct the mapping where needed. The recipient keeps the familiar layout, including regulated or organization-specific forms.

Pair the printable page with a responsive form

Pair the uploaded PDF with a responsive web form that updates it live. Someone on a phone can enter answers without navigating a page designed for print.

Keep the signature field in the file

A fillable PDF carries the signature element as part of the document, so the returned file keeps the field where the template placed it.

Use a dedicated platform for negotiated agreements

Form-native signatures and negotiated agreement signing solve different problems. The deciding question is whether the document exists before the signer enters the workflow. Answer that first and the rest of the system becomes easier to choose.

Use form signing when answers create the file

For a waiver, consent, accepted quote, proof of delivery, or enrollment, the answers and signature produce the document. Starting with a finished PDF would add a handoff because no such file exists before the person fills in the form.

Use send-for-signature for review and negotiation

A contract moving between legal teams may need redlines, several counterparties, and a provider-specific completion certificate. Connect one of the six supported signing platforms and let it handle that process.

Many organizations need both workflows. The connector keeps collection and document generation together here, while allowing the required provider to own the separate signing ceremony.

Questions about form signatures

Can a signer use their own signing platform instead?

Yes. Connect DocuSign, Adobe Sign, SignNow, RightSignature, Box Sign, or SignRequest to the form or its submission. You can collect the information and create the document here, then hand signing to the provider your counterparty requires.

What happens to the signed document afterwards?

Route it to the record or storage that owns it: attach it in Salesforce, post it to a webhook, or deliver it to your S3, Google Cloud Storage, or Azure bucket. Audit events are append-only and searchable, while retention, deletion, and legal hold follow policies you configure.

Can a signature be required before the form can be submitted?

Yes. Mark the field required and the form cannot advance without it. Conditional logic can show the right signature and document content for each respondent, so the same template can ask a guardian to sign for a minor without asking one to sign for an adult.

Do the people who sign count as users on our plan?

No. Public respondents and anonymous signers are not seats. Seats cover the people in your organization who build forms and work with submissions, so external signing volume does not add internal users.

How is this different from sending a document out for signature?

A send-for-signature tool starts with a document that already exists. Here, the signature is one of the form answers used to create the document, so the submitted form produces a PDF with the mark already in place.

Can people sign on a phone?

Yes. People can draw in the signature field with a finger on a touchscreen or with a mouse, and the form adapts to phone-width screens.

Where does the signature appear in the PDF?

In the position you set in the document designer. Place the corresponding element on the template and each submission renders the captured signature there.

What if I need a dedicated e-signature provider?

A submission can trigger a provider handoff when its signing process is required. Supported connections cover DocuSign, Adobe Sign, SignNow, RightSignature, Box Sign, and SignRequest.

Where is the signed document kept?

Keep it in managed storage served behind a CDN, or forward it to your own S3 or Google Cloud Storage bucket with the request. Included storage runs from 5 GB on the entry plan to 1 TB.

Which plan includes signing?

Signature fields, fillable PDFs, and provider hand-off are included on Business, from $89 a month for 20,000 renders, alongside form payments, conditional logic, and 5 internal users. Building and rendering documents starts at $9 a month for 1,000 renders.

Does the signature stay with the submission?

Yes. The finished document stays with the answers used to produce it, so the submission record shows both what the person entered and the document carrying their signature.

Can I collect more than one signature on a form?

Yes. Add a separate field for each person signing in the same session, such as a patient and a guardian, then place each signature separately on the document.

You get signature fields, fillable PDFs, and provider hand-off on Business, from $89 a month for 20,000 renders. Create the document from submitted answers, collect a signature with the form, or hand the file to a dedicated signing provider. Plans open at $9 a month for 1,000 renders, and the free account needs no card. See what each plan includes.

Create the document
with the signature in place

Build a form that turns submitted answers and a signature into a finished PDF.

No credit card required.