Projects request template

Scope of work approval signing request template

A scope of work approval confirms, in writing, the exact deliverables a project will cover so both sides agree on what is in and out.

Send a scope of work approval request Browse all templates

What is a scope of work approval?

A scope of work describes the boundary of a project: what will be delivered, what is explicitly excluded, and the assumptions that define the edges. Where a full statement of work also covers pricing and acceptance, a scope of work approval focuses on getting agreement on the deliverables themselves before detailed planning or quoting goes further. It is the document that answers the question 'are we all picturing the same project?'

Capturing scope as a signed approval matters because most project friction comes from unclear boundaries rather than poor execution. When the client and project owner both sign the same scope, there is a shared reference point for every later conversation about whether something is included. That makes change requests visible and easier to price, instead of quietly expanding the work.

When to use a scope of work approval

Confirming project boundaries before producing a detailed quote or plan
Locking scope after a discovery or scoping workshop with the client
Setting a baseline so future requests can be assessed as in or out of scope
Aligning an internal project owner and client on deliverables before kickoff

What to include in a scope of work approval

In-scope deliverables: a clear list of what the project will produce.
Out-of-scope items: what is deliberately excluded, to prevent assumed inclusions.
Assumptions: conditions the scope relies on, such as access, data or client inputs.
Dependencies: third parties or prerequisites the work cannot proceed without.
Sign-off basis: who approves the scope and what their approval commits them to.

Pros and cons of sending a scope of work approval as a signing request

Pros

Records an agreed baseline both sides can point back to later
Tracks whether the client has previewed the scope before approving
Expiry stops an old scope being approved after circumstances change
The receipt timestamps exactly what scope was agreed and by whom

Cons and things to watch

Approval does not fix pricing unless the scope document also sets fees
Poorly worded exclusions can still leave grey areas after signing
It does not remove the need for a change order when scope grows
Signing confirms agreement, not that the scope is technically achievable

How to send a scope of work approval with Cosign

Upload the scope document and preview it to confirm in-scope and out-of-scope items read clearly.
Add the client approver and the project owner as signers so both sides record agreement.
Set an expiry of around 14 days, and use password protection if the scope reveals sensitive plans.
Send the private links, watch for opens and previews, then keep the signed receipt as your scope baseline.

Scope of work approval request details

Email subject

Scope of work approval

Default message

Please review this scope of work and sign to confirm the agreed deliverables.

Signer setup

Client and project owner

Suggested expiry

14 days

Button label

Approve scope

Best fit

Projects teams

Scope of work approval FAQs

Is an electronically signed scope of work valid in Australia?

Electronic signatures are generally recognised under Australian electronic transactions law when the signer consents and can be identified reliably. A signed scope approval is commonly treated as evidence of agreement, but this is general information and not legal advice.

What is the difference between a scope of work and a statement of work?

A scope of work centres on what is in and out of the project, while a statement of work usually adds pricing, schedule and acceptance terms. Many teams approve scope first, then issue a fuller statement of work.

Will my scope of work stay private?

Yes. Cosign sends the scope as a private link only to the signers you choose, and pages are not indexed by search engines. You can add a password for an extra layer if the contents are sensitive.

Can I see if the client actually read the scope before approving?

Yes. Cosign logs when each signer opens and previews the document, so you can tell whether the client reviewed the scope rather than simply approving it on trust.

What happens if the scope changes after it is approved?

A signed scope sets a baseline, so later additions should be handled as a separate change order. That keeps the original approval intact and makes the new work and its cost visible.