Also known as: scope change, contract amendment
A change order is a formal amendment to an existing engagement that documents and prices new scope. When a client requests work beyond what was originally agreed, a change order captures the additional deliverables, timeline impact, and revised cost. Both parties sign before the new work begins. Change orders protect margin by making scope creep an explicit, priced conversation.
Where you'll see change order in day-to-day work inside Helm.
In Helm, the Project Manager agent detects scope expansion by reading project updates and new task creation beyond the original SOW. It drafts a change-order email with revised cost (calculated from your configured rates) and timeline impact, attached to the account. You review and send. Helm keeps the change-order document on the project record for historical reference.
Concepts that show up in the same workflows and reports.
Common questions and honest answers.
Any scope addition worth more than 2-5% of the original engagement should be a change order. The discipline of saying "this is change order territory" is worth more than the dollars. It trains clients to expect formal scope conversations.
Yes. Timeline-only amendments are common when the client causes a delay (missed feedback windows, slow approvals) but no additional work scope is added. The change order still documents the shift for future reference.
Strongly recommended. An unsigned change order is an accumulating dispute. Helm drafts the change-order document; e-signature happens via Composio integrations (DocuSign, HelloSign) on Pro and Business.
Helm is the AI work platform where these concepts stop being theory and start being your Monday morning.