A common modern task arrives as an email: a document attached, a request to sign it, and an expectation that it comes back signed the same day. No printer, no scanner, no post — just an inbox and a deadline. Done carelessly, that workflow is risky: an unread document signed in haste, a signature placed on the wrong line, a file sent to the wrong person, a recipient who needed a different kind of signature altogether. Done carefully, it is fast and safe. This post lays out the careful version, step by step.
The signing step uses Sign PDF, which places a drawn, typed, or uploaded signature on a PDF page and flattens it into the page, in your browser, so the document never needs to be uploaded to be signed. The workflow around that step — reading, checking, and returning — is where the safety lives.
Step one: read before you touch the signature tool
Open the attachment and read the whole document before signing anything. That sounds obvious, and it is the step most often skipped under deadline pressure. Read for three things in particular. First, what are you agreeing to — the obligations, dates, amounts, and conditions, not just the summary in the covering email. Second, are the details correct: your name spelled correctly, the right address, the figures you expect, the dates you agreed. Third, is anything blank that should not be — a blank amount, an undated clause, a missing attachment referenced in the text. A signature on a document with blanks invites those blanks to be filled in after you sign, in terms you did not agree to.
If anything is wrong or unclear, stop. Reply to the sender and ask, before signing. A signed document with an error is far harder to correct than an unsigned one with a question, and a sender who is annoyed by a question before signing will be far more annoyed by a dispute after it. Never sign a document you have not read, and never let a deadline pressure you into skipping the read. A deadline can be renegotiated; a signature cannot easily be withdrawn.
Also confirm, before signing, what kind of signature the recipient requires. In-browser signing is not the same as a certified or qualified electronic signature, and it may not satisfy a bank, a court, or a government form. If the recipient needs a certified signature, a placed signature image will not do, however neatly placed, and discovering that after you have signed wastes everyone's time. One question in your reply — "Will a signature placed on the PDF be accepted, or do you require a certified signing service?" — settles it.
Step two: sign carefully, then check the result
Once the document is read and the signature type is confirmed, sign it. Choose the signature style that fits the document — drawn for a personal feel, typed for clarity, uploaded for your real handwriting — and place it precisely on the signature line, at a size that fits the space. Check that it does not overlap neighbouring text, that it sits on the correct line when a page has several signature blocks, and that the date, if you must add one, is correct and in the format the document uses.
Then check the signed file before sending it back. Open the downloaded file fresh — not just in the signing tool's preview — and page through it. Confirm the signature is where you intended, that no other page was altered, and that the document is complete: all pages present, in order, legible. This check takes a minute and catches the placement slips that are invisible in a preview at small size. Because the signature is flattened into the page, it cannot be repositioned afterwards; a misplaced signature means starting again from the unsigned original, which you have kept. That is a minor inconvenience at this stage and a major one after sending.
If the document also needs form fields completed, do that before signing, not after: a signature should be the last mark on a finished document, not an early mark on a document still being filled in. Fill PDF Forms handles typed form fields, and completing them first keeps the signing step clean. If the signed file is sensitive, Protect PDF can add password protection before you send it back.
Worked example: a fictional rental renewal, by email
Imagine a fictional tenant, Sofia Almeida, who receives a fictional rental renewal by email from a fictional landlord at example.org. The covering email asks her to sign and return it the same day. Sofia follows the workflow.
She opens the attachment and reads it fully. The renewal term, the monthly amount, and the notice period match what she agreed verbally. One detail is wrong: her flat number is listed as 4B instead of 4A. She stops, emails the landlord pointing out the error, and receives a corrected file within the hour. Had she signed the first version, the error would have been embedded in a signed document, and correcting it would have required a new agreement rather than a corrected draft.
Sofia reads the corrected file, confirms the flat number is now right and nothing else changed — she compares the two versions page by page rather than assuming only the flat number moved — and confirms by reply that a placed signature on the PDF will be accepted. She then signs with an uploaded image of her pen signature, placed on the tenant signature line, checks the signed file fresh, and finds the signature clear, correctly placed, and clear of the date line.
Before returning it, Sofia runs three final checks. She confirms the recipient address is the landlord's address from the original thread, not a lookalike address from a forwarded message. She confirms the attachment is the signed file, not the unsigned original — a mix-up that happens more often than anyone admits, because the two files look alike in a file picker. And she writes a covering message that names the document, states that she has signed the corrected version dated with the fictional date shown in the file, and asks for a countersigned copy in return. She sends it, and files both the unsigned corrected original and the signed copy in her tenancy folder.
Step three: after sending, keep the record
Filing the signed copy is the workflow's last step, and it is the one that protects you months later. Keep the unsigned original, the signed copy, the covering emails in both directions, and the countersigned copy when it arrives, together, in a folder named for the matter. If a question arises later — which version was signed, when, on what terms — that folder answers it without a search through an inbox.
If the countersigned copy does not arrive, follow up. A one-sided signed document is an incomplete exchange: you have committed, and the other party's commitment is not yet in your hands. A polite follow-up after a reasonable interval — a few working days for most matters — is not impatience. It is the completion of the workflow, and it should not be left to chance.
For checking a returned version against the one you sent, the guide on comparing documents explains how to spot changes systematically.
Honest limitations
In-browser signing is not a certified or qualified electronic signature, and it may not satisfy a bank, court, or government form — always confirm the recipient's requirement before signing, and use a certified route where one is required. A flattened signature cannot be moved after download, so placement must be verified before sending, and the unsigned original must be kept for any re-sign. Email itself has limits: an attachment can be misaddressed, a signed file can be confused with its unsigned original, and email is not a secure channel for highly sensitive documents — for those, ask the recipient about a more secure return route rather than assuming email is acceptable. And the workflow's central rule stands above all: never sign a document you have not read, regardless of deadline pressure or a sender's assurance about its contents.
FAQs
How do I sign a PDF and return it by email?
Read the document fully, confirm the recipient accepts a placed signature, sign it in a browser tool, check the signed file fresh for placement and completeness, attach the signed file — not the unsigned original — to a reply that names the version signed, and file both copies with the correspondence.
Should I check anything before signing a document sent by email?
Yes: read the whole document, verify names, figures, and dates, check for blanks that should not be blank, and confirm what kind of signature the recipient requires. If anything is wrong or unclear, ask the sender before signing, not after.
What if the document I receive has an error in it?
Do not sign it. Tell the sender what is wrong and ask for a corrected version. When the corrected version arrives, compare it with the original page by page to confirm only the error changed, then sign the corrected version.
Is it safe to return a signed PDF by email?
For most everyday documents, yes, provided you verify the recipient address, attach the correct file, and keep a filed record. For highly sensitive documents, ask the recipient about a more secure return route, and remember that a placed signature is not a certified electronic signature.
Related reading: Filling the form before signing.
human review pending client designation