How to Send a PDF for Signature: 4 Steps, Under a Minute
Upload the PDF, place the signature field, enter the signer's email, and hit send — here's the exact workflow.
Upload the PDF, place the signature field, enter the signer's email, and hit send — here's the exact workflow.

Someone's waiting on a contract, a release form, or a service agreement. You have the PDF, you know who needs to sign it, and you need it back today.
Sending a PDF for e-signature takes four steps. Here's exactly how — and the parts that trip people up the first time.
The signer gets an email with a link. They click it, sign, and submit. You get a notification when it's done, plus a copy of the signed PDF with an audit trail attached.
That's the whole workflow. Total setup time is under a minute if the document is already on your device. The sections below walk through each step in more detail — and cover the mistakes that bite first-time senders.
Open your signing tool and look for an "Upload" or "New document" button. Drag the PDF in, or browse to it. Most services accept standard PDFs; if you have a Word doc or a Google Doc, export it to PDF before uploading.
Three things worth checking before you upload:
The file is the final version. Once someone signs a document, the content is locked. If you need to adjust the scope, the price, or anything else, do it before you upload — not after a signature is pending.
The file isn't password-protected. Password-protected PDFs block the signing tool from adding interactive fields. If yours has a password, remove it first. You'll usually know because the tool will throw an error on upload.
The file size is manageable. Documents over 20–25 MB can be slow to load on a phone. Home inspection reports with embedded photos are the classic offender. If you're sending something like that, compress the images before uploading — the signer shouldn't have to wait 15 seconds for the page to render before they can sign.
Once the PDF is loaded, you'll see a preview of the document in the editor. Signing tools let you drag field types onto any page — click wherever you want the signature and the tool places an interactive field there.
The field types that matter most:
| Field type | What it captures |
|---|---|
| Signature | The signer's drawn or typed name |
| Initials | Brief initials on each page |
| Date | Auto-fills with today's date when the signer submits |
| Text input | Free text — printed name, job title, address |
| Checkbox | Acknowledgment lines ("I have read and agree to the terms") |
For a basic one-signer contract, you usually need one signature field, one date field, and sometimes a checkbox. That's it. Don't over-engineer the first one.
If you're building a template you'll reuse — a service agreement you send every new client, for instance — it's worth placing initials fields on every page. The per-page initials confirm the signer worked through the whole document, which matters if a dispute later centers on whether they read a specific clause.
Placing fields for mobile signers: Most people will open the document on their phone. Signature fields near the bottom of a page are the easiest to reach with a thumb. Fields crammed at the top of a dense page are easy to scroll past without noticing. If your document has a signature block at the top, consider moving it — or at minimum, test the mobile view before you send.
After placing the fields, the tool prompts you to add the recipient. Enter:
Most tools also give you a message field for the invitation email. Keep it short and direct:
"Hi Sarah — the service agreement is ready to sign. The link below takes you straight to the signature page. Takes about 30 seconds."
Don't oversell it. Don't apologize for asking. The document is the document; the email is just the delivery. The longer the note, the more it reads like you're nervous about the ask.
If multiple people need to sign — both parties to a vendor agreement, or co-signers on a lease — add each recipient separately and assign each person their own fields. Set the signing order before you send so the second signer doesn't receive the link until the first has completed their part.
Hit send. The signer gets the email immediately with a link.
What they see on their end:
You get a notification when they complete it. The signed PDF — with the original content plus a tamper-evident audit trail — lands in both inboxes. No attachment to chase, no "can you resend the signed version?"
Most documents get signed within an hour of sending. If it's been a full day:
Send a reminder through the tool. Every signing service has a "remind" or "resend" button. This sends one more email with the same link. Don't do this more than once per day — it reads as nagging and doesn't speed things up.
Check whether it landed in spam. E-signature emails sometimes get filtered, especially from a sender domain the signer hasn't seen before. Ask them to search their spam folder for your name or the document name.
Try a different channel. If your normal back-and-forth is by text, some signing tools let you send the signing link via SMS. A link in a thread they're already reading is harder to miss than a standalone email.
Pick up the phone. Sometimes the fastest move is a 30-second call: "Hey, I sent a contract — it's in your inbox, can you sign while I have you on the line?" You'd be surprised how often that closes it.
If it's been 72 hours and nothing, the document probably isn't coming back on its own. Make direct contact.
Sending before the document is finalized. Once a signing link is active, changing the document means voiding the link and starting over. The signer gets a "this document has been voided" email, which is confusing and occasionally alarming. Review the PDF top to bottom before you upload.
Typing the email address instead of pasting it. A one-letter typo sends the link to a nonexistent inbox. The delivery looks successful from your tool's perspective, and you won't realize anything went wrong until the signer says they never got it. Copy-paste the address directly from your contacts.
Skipping the mobile preview. Most signing tools have a "preview as signer" button. Use it. Walk through the document as if you've never seen it. Make sure every required field is visible, the fields don't overlap text, and the signature block is easy to reach on a small screen.
Uploading a PDF with signature lines already drawn in. Lots of contract templates come with a drawn line that says "Signature" underneath — a holdover from printing. The signing tool adds interactive fields on top of the document and doesn't care about the drawn line. You don't need to delete it, but place the interactive field overlapping or adjacent to the drawn line so the signer doesn't see two spots that look like signature blocks.
Every completed signing generates an audit trail — a log appended to the signed PDF. Here's what it typically captures:
The hash is the part that makes tampering detectable. If anyone modifies the signed document — even one character — the fingerprint stops matching and the tampering is apparent. The signed PDF and the audit trail are paired; you can't produce one without the other being traceable.
You don't manage any of this manually. The tool handles it automatically when the signer submits. But it's the reason that a signed PDF from a reputable e-signature service is meaningfully different from a screenshot of someone typing their name.
For more on what the signer experiences on the other end — including how it works on mobile — see How to e-sign a PDF on iPhone in under a minute. The signing side is the same workflow regardless of which device they use.
Upload. Place the field. Add the recipient. Send. That's the loop. The signer gets a link, taps through three screens, and submits. You get a notification and a signed PDF — without a printer, a scanner, or a PDF attachment coming back as a reply.
Once you've sent the first document, the second one is faster. Set up a reusable template for any document you send repeatedly and Step 2 drops to zero — the fields are already there, you just enter the recipient and hit send.