E-Signatures: Sending a PDF for Signature

If you just want to send a PDF for signature, the easiest way to start is from E-Signatures in the sidebar. You do not need to build a full form first.

This workflow is ideal when you want to:

• Upload a PDF and send it for signature quickly
• Add signature, text, and date fields to a document
• Share the form link or send the document to a named recipient by email
• Enable email verification for stronger signer proof

Start a New Document

1. Open E-Signatures in the sidebar.
2. Click Upload PDF.
3. Choose one of the two options:
   • Just get signatures — best for a lightweight document-signing flow
   • Collect extra data first — best if the signer should answer additional questions before reviewing the PDF
4. Enter an internal document name.
5. Upload your PDF file. The limit is 20 MB.
6. Decide whether to enable Email verification.
7. Click Create document.

After that, meetergo creates the underlying form for you automatically, with one field named Review and sign document. That field holds your PDF, and a signature is required on it by default.

Place Fields on the PDF

Once the document is created, you land in the document setup screen.

From there you can:

• Upload or replace the PDF if needed
• Place signature fields on the document
• Add text placeholders and date fields
• Configure whether a signature is required
• Enable email OTP verification for stronger signer proof

You can come back to this any time: open the form, go to the Automation tab, section Documents & Signatures, and click Edit PDF on the document card.

Send or Share the Document

There is no separate "signing link". Whichever route you pick, the signer opens the form that holds your PDF and signs inside it.

Send it to a named recipient

1. Open E-Signatures and click Send now on the document. The send dialog opens over the document's Results, Submissions view.
2. If you closed the dialog, open Results, select Recipients, and click Send form to reopen it.
3. Pick a CRM contact or type a name, and enter an email address or phone number.
4. Choose the channel: Email, Phone (SMS), WhatsApp or Both.
5. Optionally add a personal message and prefill fields, then click Send.

meetergo generates a personal form link for that recipient and sends it through the selected channel. The Recipients table tracks Not opened, Opened, Completed, and Expired per person. These states describe link activity, not message delivery.

Share the form link instead

Every document flow has a public form link (form editor → Settings → Public link). Anyone who opens it can review and sign the PDF, on every plan and without adding a recipient first. Turn on Email verification when you share the link more widely, so the signer's identity is confirmed before the signature is accepted.

Track Status

The E-Signatures page groups documents by status:

• Needs setup — the document exists, but the PDF or field placement still needs work
• Ready to send — the PDF is attached and the document can be opened for delivery

You can also open the linked form at any time if you want to adjust routing, extra questions, or recipient workflows.

After Signing: Who Gets the Signed Document

Once the signer accepts, meetergo appends the audit page to the PDF, signs it cryptographically and stores it with the submission. From there:

The signer's copy

The email is on by default. To check or change it, open the form → Settings tab → Notifications → Send signed document to the signer.

The signer receives a mail titled Your signed document: <document name> with the finished PDF attached, and the last page of that PDF holds the audit trail with timestamp and checksum. Two conditions have to be met:

• The form must capture the signer's email address. The copy goes to the email address on the submission, so a document flow with no email field has nobody to send it to. Documents you send from the Recipients view always have one.
• Documents over 8 MB are not attached. Below that size the PDF rides along in the email; above it the signer gets a download link in the same email instead.

If the mail cannot be sent, the signature is still valid and stored. Nothing about the signing itself depends on this email.

Your own copy

Open the form → Submissions tab → the submission → Download on the document field. The submission notification you receive when someone submits ("Email on submission" in the same Notifications section) lists the answers and links to the submission; download the signed PDF from there.

Plans and Monthly Limits

E-signatures are included on every plan under a monthly limit on signatures.

A few details that decide what counts:

• Every completed signature counts, whichever route produced it. A shared form link counts exactly the same as a send to a named recipient.
• Counting happens when someone signs, not when you send. A document nobody signs consumes nothing.
• If several people sign the same document, each person counts separately.
• The allowance is shared across the whole company and across every route (form link, the Recipients view and the signature API).
• Once the allowance is used up, the signature field pauses. Your form stays online and keeps accepting submissions, so you lose no enquiries. When the new month starts or you upgrade, you can send those people the document to sign.
• Sends to named recipients are blocked up front when your allowance no longer covers them, so you never send a document nobody can sign.
• Turning on Email verification (FES) on a document below Suite blocks the send with an upgrade prompt. Turn it off to use the same document as a simple signature (SES).

When to Use E-Signatures vs. Form Fields

Use E-Signatures when:

• your starting point is a PDF document
• you want the shortest possible path to “send this for signature”
• you only need light signer input

Use a regular Signature field when:

• you only need a hand-drawn signature image inside a form
• there is no PDF document involved
• the signature is just one answer among many form responses

FAQ

Do I still need forms to use this workflow?

No. The document-first flow creates the underlying structure for you automatically. Forms are only needed if you want additional questions, routing logic, or more advanced workflows.

Can I add email verification later?

Yes. Open the document in the Documents view and enable Email verification in the signature settings.

Can I upload a PDF first and map fields later?

Yes. You can create the document first, then return later to place fields or finish setup.

What if I need legally stronger signer proof?

Enable email verification. For more detail, see Fortified Electronic Signature (FES) and Email Verification.

Does the person who signed get the document automatically?

Yes. Send signed document to the signer is on by default, so the finished PDF goes out by email the moment they submit. See After Signing: Who Gets the Signed Document. You do not need a workflow or a webhook for this.

I clicked Send now and only see past submissions

Send now opens the send dialog over Results, Submissions, so once the dialog is closed you are looking at past submissions. Open Results, select Recipients, and click Send form to send again. If the view shows an upgrade notice instead of a recipient list, sending to named recipients is not part of your plan; share the form link instead.

Which e-signature provider do you use?

None. Everything runs inside meetergo on EU infrastructure, and the signer does not need an account anywhere. See Fortified Electronic Signature (FES) and Email Verification for what meetergo produces itself.

The signer says the signature button is hard to see

The signing page uses your brand color. If it is set to white, the button all but disappears on a white background. Change it under Branding.

Related Articles

• Using PDF Templates on Forms
• Fortified Electronic Signature (FES) and Email Verification
• Collecting E-Signatures on Forms
• Sending Forms Directly to Recipients