Submit a change order request for client approval when project scope or cost changes.
Includes required fields, attachments, and recipients
Takes <30 seconds. No setup required.
To
Add recipients
Cc
Add recipients
Bcc
Add recipients
Subject
Change Order change_order_number — project_name
change-order-document
Hi client_first_name,
As we've progressed through project_name, a scope change has come up that falls outside the original agreement. I'm submitting this change order for your review and approval before we proceed.
CHANGE ORDER DETAILS
• Change Order Number: change_order_number
• Project: project_name
• Description: change_description
• Cost Impact: +$cost_impact
• Schedule Impact: timeline_impact
WHY THIS CHANGE IS NEEDED
This work was not included in the original scope of work but has been identified as necessary (or requested) to achieve the project goals as currently understood. We never want to absorb undisclosed costs or proceed with work that hasn't been authorized — which is why we document these changes formally before moving forward.
WHAT HAPPENS NEXT
Please review the attached change order document and return a signed copy by approval_deadline. Once approved, we'll incorporate the additional work into the project schedule and invoice accordingly. If you'd like to discuss the change before signing, I'm available for a call at your convenience.
If there's a way to descope or phase this work to manage cost, I'm open to that conversation as well. Reach me at me::phone and we can talk through the options.
Use this workflow when project scope, cost, or timeline changes and the client needs to review and approve a formal change order.
This replaces manually writing scope-change emails, retyping cost and schedule impact, and checking whether the signature-ready change order document is attached.
Change orders need to be clear before work proceeds. A workflow helps teams document the business reason, approval deadline, cost impact, and timeline impact in a consistent way.
The workflow prepares the operational details your team should not have to rebuild by hand.
No. Toggles prepares the email request. Approval happens through your existing client approval and signature process.
Yes. This workflow can require the change order document before sending.
Yes. The Outlook draft is reviewable and editable.
Help operations teams send structured updates, project messages, invoice notices, and coordination emails from Outlook with fewer missing details.
Use the audit to compare repeatable Outlook emails by volume, risk, and complexity before choosing the first workflow for your team.
Standardize the full process, then let your team launch the same complete email whenever they need it.
Add this example to Outlook so the full email process is ready to use right away.
Install this workflow →
Launch it from the compose window where your team already works.
Review the remaining fields, then send with the right message already in place.
See how Toggles helps operations teams standardize repeatable client emails in Outlook.
See how Toggles helps customer success teams standardize repeatable client emails in Outlook.
See how Toggles helps legal teams standardize repeatable client emails in Outlook.

Discover how professionals can save hours each week by automating repetitive email tasks, ensuring consistency, and improving communication quality with Toggles for Outlook.

A step-by-step guide for getting started with Toggles for Outlook.

A step-by-step guide for getting started with Toggles for Outlook for your team with Business Pro.