Requesting a signature
Upload a PDF to an engagement and ask your client to sign it. They sign in their browser, and the signed copy comes back to you.
Signatures live on the engagement, next to the documents. The same client, the same link, the same conversation.
Sending one
- Open the engagement.
- Request a signature and choose the PDF to be signed, up to 25 MB.
- Send it. Your client is notified, and it appears on their portal to sign.
Following it
The request carries its state on the engagement:
- Sent to client: it is with them.
- Awaiting signature: still waiting.
- Signed: done.
- Signed copy returned: the completed document is back and downloadable.
- Sent back: you returned it to the client to redo.
An engagement waiting on a signature sits at the Awaiting signature stage, so your list shows what it is actually waiting on. See workflow stages.
If it is not set up yet
If signing has not been configured for your firm, the request still creates the row on the checklist and shows Signing setup needed. Nothing is lost, and nothing goes to your client until it is ready.
Getting the signed copy
Once signed, Download signed document gives you the completed PDF. It is yours to file wherever you file things.
If they sign the wrong thing
You can send a signed copy back the way you would reject any document, with a reason your client reads. The built-in reasons cover the usual: The document wasn't signed., Wrong document., The signed copy is hard to read.
Next: how your client signs.