Start from the proposal template
Create a proposal from structured fields, with the workspace brand applied.
Proposal workflow
Take a proposal from first draft to signed document
A proposal should not become a trail of exported PDFs called final-v4. Keep the source, client feedback, approved version and signature request together.
Use the proposal workflowWhat this workflow is for
A proposal is both a sales document and the start of a client record.
Use a proposal workflow when scope, pricing and deliverables need to move from a working draft to a client commitment. The proposal may begin with a template, but the important part is what happens after it is created: internal review, client questions, revisions, approval and, when appropriate, a signature request.
Keeping those stages together avoids a familiar problem for agencies and service teams: the polished PDF gets sent, the scope changes in email, and the signed file lives in a separate system. A proposal workspace gives the commercial document one history from first draft to final agreement.
The workflow
One document, every next step.
- 01
Your team - 02
Your team Review the draft
Make internal edits and comments before the client sees the document.
- 03
Client Share it with the client
Send a review link so the client can review and comment without joining EveryTask.
- 04
Both Revise, approve and sign
Save the final revision, then request the signature from the same document record.
Choose the right next step
Use this for a commercial document that will keep moving.
The client needs to evaluate scope and price
A proposal workflow is for documents that invite a business decision. It gives the client space to ask about deliverables, timing or commercial terms before they commit.
The team needs to preserve the agreed scope
When a proposal changes, each revision should remain recoverable. That makes it easier to understand which version informed the final agreement.
The proposal may become the signed record
The final proposal can continue to signature without being downloaded, renamed and uploaded into another process.
Why keep it together
The file is the shared context.
- The client project gives the proposal a reliable home.
- A later revision does not erase the approved draft.
- The proposal can move from review to signature without a re-upload.
Keep the process clear
Protect the agreement hidden inside the proposal.
Separate an exploratory draft from a sendable proposal
Review the document internally before the client sees it. The client should receive a clear commercial document, not an unfinished version that creates unnecessary questions.
Record scope changes in the document
If the client changes deliverables, price or timing, update the proposal and keep the new version. That is clearer than treating an email thread as the authoritative scope.
Use signature for the final commitment
A proposal can be approved in principle and still need signature. Send the precise, agreed version once the commercial conversation is complete.
Questions, answered
Proposal workflow questions
Can we start a proposal from a template?
Yes. A template helps create the structured proposal, then the document can be kept in the client project for review, revision and the next step.
What if the client asks to change the scope?
Update the proposal and save the revised version. The earlier document remains part of the record, so the team can see how the final scope developed.
Should a proposal be reviewed before it is sent?
Usually, yes. Internal review helps ensure the pricing, deliverables and wording are ready before the client starts responding to the document.
Can the same proposal be signed?
Yes. When the proposal has become the agreed document, request the signature from the same document record rather than starting a detached signing process.
Start the workflow
Give the next document a place to go.
Free to start with one project and no card needed.
Use the proposal workflow