Send the current document
Prepare the version you intend to execute instead of attaching an old copy from a download folder.
For documents ready to be signed
Request signatures without losing the document behind them
Send the current document to the people who need to sign it, follow each response and retain the completed record with the client project.
A workspace keeps the document, the people involved and the next step in one place.
What it changes
A signature request should be more than an attachment with a deadline.
A signature request is the execution step after a document has been reviewed and settled. It should clearly identify what the recipient is being asked to sign, keep the request attached to that version, and show the sender what has happened without another round of “did you receive it?” emails.
EveryTask keeps the signature request with the document record. That gives the sender one place to prepare the file, place signature fields, send the invitation and retain the completed result alongside the proposal, scope or agreement that led to it.
The capability
More than one action on a file
Place signature fields
Mark where each recipient needs to act before the request leaves the workspace.
Track the response
See when a request is pending, completed or declined, without asking recipients for a status update.
Keep the completed record
The signed document and its request activity stay in the client project for the next person who needs context.
A deliberate handoff
Move to signing only when the document is ready, rather than confusing review feedback with execution.
Context after completion
Retain the document history around the completed signature instead of treating the final PDF as an isolated file.
Useful when
For agreements that are ready to become a record.
A proposal becomes an agreement
Send the settled version only after review is resolved, so the signature request has a clear commercial meaning.
A client needs one clear action
Give a recipient a focused signing step instead of asking them to interpret an email thread and attachment.
The team needs proof later
Keep the request, response and completed file in the same client project as the work that explains it.
How it works
Start with the document. Keep the context.
- 01
Create or open the document in its client project and confirm the version is ready to sign.
- 02
Add the recipient, place their signature field and send the request from the document.
- 03
Follow the response from the workspace, then retain the completed document with the project record.
Questions, answered
Using this capability with confidence.
Can I request a signature without giving the recipient an EveryTask account?
Yes. Recipients use the secure signing link sent for the document. They do not need to join your workspace.
Is requesting a signature the same as signing a PDF myself?
No. Self-signing completes a document yourself. A signature request is for sending a prepared document to another person and following their response.
Can I see whether a recipient has acted?
The document record shows the request state so the sender can see whether it is pending, completed or declined.
Should I send a signature request before review is complete?
Usually no. Review is for feedback and changes; signing is the execution step for the version that is ready to stand.
When the work needs to stay
Put the document in a workspace.
Signature requests belong in a workspace because the document, its current version and the completed result need to remain connected.
Create a free workspace Beta- One project per clientKeep the brief, PDF and final version together.
- Working drafts preserve progressIssue a revision when a document is ready to become the next record.
- Comments stay with the fileReview decisions do not disappear into email.
Explore document workflows
Keep the document moving.
Ready when you are
Create a free workspace
Open the document, get the work done, and keep it in a workspace whenever there is a next step.
Create a free workspace Beta