Change Summary
Concise description of the modification: what is changing and why, with reference to original contract sections and any relevant purchase order or job number.
A WCO clarifies scope, protects contractual rights, and documents agreed cost and time changes. It preserves an auditable record for invoicing, progress payments, and claims while reducing later disputes by establishing mutual assent and specific acceptance criteria.
Typical users include project managers, contracting officers, procurement staff, and legal or finance representatives responsible for approving scope changes.
Different signatories may be required for budgetary approval, legal review, or client acceptance depending on organization size and delegated authority.
Concise description of the modification: what is changing and why, with reference to original contract sections and any relevant purchase order or job number.
Precise technical description of added, removed, or altered tasks, materials, and deliverables so implementers and inspectors can verify work and acceptance.
Line‑item or lump‑sum cost adjustments, taxes, and allowances; include basis for pricing such as rates, time-and-materials, or unit prices.
Revised start/finish dates, milestone revisions, and any liquidated damages changes; state how calendar and business days are calculated.
Signature blocks for each party with printed name, title, company, and date; record who is authorized to approve under the master agreement.
Supporting items such as revised drawings, cost worksheets, photographs, or vendor quotes that justify the change and form part of the record.
| Field | Configuration |
|---|---|
| Approver Order | Sequential approvals by role or user group |
| Required Fields | Scope, cost, effective date, signatures mandatory |
| Notifications | Email and SMS reminders on pending actions |
| Document Storage | Auto-save executed WCO to contract repository |
Verify platform encryption (TLS/AES), retention controls, and role-based access to meet internal policy and regulatory obligations; plan for automated distribution to stakeholders after execution.
Submit WCO proposals within 7–14 days of identifying the change to minimize disputes.
Allow 3–5 business days for finance and legal to assess cost and compliance implications.
Request approval or counterproposal within 10 business days to keep the schedule intact.
Process invoices in the next billing cycle after signed WCO is received by accounting.
Retention begins on the executed date; note in document metadata for records management.
Field team or client raises the change with a proposed scope and estimate.
Finance and project management review and accept cost and schedule effects.
Authorized parties sign the WCO and the document becomes binding.
Store the executed WCO, notify teams, and update ERP and schedule records.