Why this matters: When a customer requests changes to a proposal or project, your team needs to act fast — updating pricing, notifying crew leads, or kicking off new workflows. Instead of manually tracking every change order, you can set up automation triggers that fire the moment a change order is created or a contract is signed. This keeps your pipeline moving and nothing slips through the cracks.

A change order is a formal request to modify the original scope of work on a proposal or project (for example, adding extra panels or upgrading an inverter). SubcontractorHub now lets you trigger automations based on these change-order events.

Scenario: SunPeak Solar uses change orders when homeowners decide to add battery storage after the initial proposal.

They create an automation on the Project module with a When Change Order → Contract Signed trigger. The automation: 1. Sends an email to the operations manager with the updated scope. 2. Updates the project stage to "Revised Design Needed." 3. Creates a task for the design team to update the system layout.

Result: The team no longer has to manually track change-order signatures — everything flows automatically within minutes.

💡 Name your automations clearly. Use a naming convention like "CO Signed → Notify Ops + Update Stage" so you can find them fast later.

💡 Combine with If/Else conditions. Add a condition to check the change-order dollar amount — for high-value changes, route to a senior PM; for small ones, auto-approve.

💡 Test before launching. Use SubcontractorHub's test feature to simulate a change order and verify the automation fires correctly.