Workflow Template
Contract Amendment Workflow
Manages the end-to-end process of amending an existing contract: intake from the contract owner, legal review with redline cycles, approver sign-off, execution by the contracts administrator, and status tracking throughout.
Contract amendments often stall between the contract owner, legal, and the approver, with redlines and status updates scattered across email threads. This workflow captures the amendment request, runs it through legal review and redline cycles, routes it for approver sign-off, and hands it to the contracts administrator for execution and signed copy storage. Contract owners, legal, approvers and the contracts administrator each work from tasks tied to a single record with a live status.
Business Outcomes
- Fewer amendment requests lost or stalled in email threads
- Clearer visibility into where each amendment sits — review, revision, approval or execution
- Faster turnaround on redline cycles with revisions tracked on the record
- Reduced manual chasing of contract owners, legal and approvers for status updates
- A complete timeline of each amendment from submission through to signed copy
Workflow Steps
Steps
- 1Create Amendment Recordcreate record
Creates the contract amendment record from the submitted form.
- 2Set Status to Submittedupdate record
Marks the amendment status as Submitted.
- 3Email Acknowledgementsend email
Sends the contract owner an acknowledgement with their reference number.
- 4Set Status to Legal Reviewupdate record
Marks the amendment status as Legal Review.
- 5Legal Reviewcreate task
Legal reviews the amendment and records commercial/legal impact, redlines, and the review result.
- 6Save Legal Review Detailsupdate record
Persists the legal review findings to the record.
- 7Route on Review Result
Routes based on whether the legal review requires changes or is ready for approval.
review_result: "Changes required"→Set Status to Owner Revisionreview_result: "Ready for approval"→Request Approver DecisionDefault→End - 8Set Status to Owner Revisionupdate record
Marks the amendment status as Owner Revision.
- 9Owner Revisioncreate task
The contract owner addresses the redlines and uploads the revised amendment.
- 10Save Revised Amendmentupdate record
Persists the revised amendment upload to the record.
- 11Return to Legal Reviewrestart from step
Restarts the workflow from the legal review step so the revised amendment can be reassessed.
- 12Request Approver Decisionrequest approval
Asks the contract approver to approve or reject the amendment.
- 13Route on Approval Outcome
Routes based on whether the contract approver approved or rejected the amendment.
approval_status: "approved"→Set Status to Ready for Signatureapproval_status: "rejected"→Set Status to RejectedDefault→End - 14Set Status to Rejectedupdate record
Marks the amendment status as Rejected.
- 15Email Rejection Noticesend email
Notifies the contract owner that the amendment was not approved.
- 16Set Status to Ready for Signatureupdate record
Marks the amendment status as Ready for Signature.
- 17Store Signed Amendmentcreate task
The contracts administrator records the signed date and stores the signed copy.
- 18Save Signed Detailsupdate record
Persists the signed date and signed copy to the record.
- 19Set Status to Executedupdate record
Marks the amendment status as Executed.
- 20Email Execution Noticesend email
Notifies the contract owner that the amendment is signed and stored.
Fields
Show all 16 fieldsShow fewer fields
FormContract Amendment Request
- Contract Owner Name*· Text
- Contract Owner Email*· Email
- Agreement Reference*· Text
- Counterparty*· Text
- Requested Change*· Long text
- Business Reason*· Long text
- Change in Contract Value*· Number
- Current Agreement (Upload)*· File upload
TaskLegal Review
- Commercial Impact*· Long text
- Legal Impact*· Long text
- Redlines*· Long text
- Review Result*· Choice
TaskOwner Revision
- Revised Amendment (Upload)*· File upload
TaskStore Signed Amendment
- Signed Date*· Date
- Signed Copy (Upload)*· File upload
Other fields
- Amendment Status· Choice
- Contract Owner Name*
- Contract Owner Email*
- Agreement Reference*
- Counterparty*
- Requested Change*
- Business Reason*
Forms
Contract Amendment Request
8 fields
Data Views
Contract Amendments
agreement_reference, counterparty, change_in_contract_value, amendment_status
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
How do I set up this contract amendment workflow?
Publish the template as-is and your workspace can start taking amendment requests through the public request form right away. The form fields, statuses and tasks are already configured, so there's no development project involved. You can adjust wording, add fields, or change routing later by describing the change in plain English or editing steps in the workflow editor.
Who is involved in running this workflow?
The contract owner submits the request and later addresses redlines during Owner Revision. Legal completes the review task, the contract approver makes the approve/reject decision, and the contracts administrator handles execution by recording the signed date and storing the signed copy. Each of these is a task assigned to a workspace member, with the contract owner interacting only through forms — no account needed.
What happens if legal requires changes to the amendment?
If the Review Result is 'Changes required', the status moves to Owner Revision and the contract owner is asked to address the redlines and upload a revised amendment. Once submitted, the workflow returns to the legal review step so the revised version can be reassessed. This loop can repeat until legal marks the amendment ready for approval.
What happens if the approver rejects the amendment?
The status is set to Rejected and the contract owner receives an email notifying them the amendment was not approved. The rejection and the approver's decision are recorded on the amendment's timeline. There's no automatic resubmission — a new request would need to be submitted if the amendment is revisited.
Can I customise the fields on the request form or the review steps?
Yes. You can add, remove or edit form fields like Agreement Reference or Change in Contract Value, and adjust what legal or the approver are asked to record. Changes can be made by describing them in plain English or by editing the steps directly in the workflow editor, and earlier versions of the workflow are kept.
How does the contract owner know the status of their amendment?
The contract owner receives an email acknowledgement with their reference number as soon as they submit the request. They're notified again if the amendment is rejected or once it's executed and stored, and the record's status is visible in table views and dashboards throughout.
What gets recorded on the contract amendment record?
The record captures the original submission details, legal's Commercial Impact, Legal Impact, Redlines and Review Result, any Revised Amendment upload, and finally the Signed Date and Signed Copy from execution. Each status change and task outcome is logged in the record's timeline, so you have a full history of the amendment. Each business should confirm this level of record-keeping meets its own compliance needs.
Does this workflow send notifications automatically?
Yes. Email is built into the platform, so acknowledgement, rejection and execution notices go out to the contract owner automatically at the relevant steps. A workspace can optionally route these emails through its own AWS SES account if it wants to send from its own infrastructure.
How long does it take to get this workflow live?
Since it's a ready-to-use template, a workspace can publish it and start running live amendment requests within minutes. There's no installation step or setup project required before it's usable.
Ready to use this workflow?
Create a free account and customise this workflow for your business.