Change control should identify who may request and approve a variation, the information required and the effect on price, schedule and acceptance. Preserve a record of disputed or urgent instructions. A written-change clause is useful, but conduct, correspondence and actual authority can still become important in a later dispute.
The business situation
A client asks for extra integrations during weekly project calls. The supplier proceeds to preserve the relationship and invoices later. The client treats the work as included; the supplier treats it as a variation. Neither can point to a settled change record.
A contract review should test how the complete document set behaves when an operational event occurs. A favourable clause can be displaced by a conflicting order form, a narrow definition or an exclusion elsewhere. Establish the applicable law, execution requirements and transaction structure before using a precedent.
What needs examining
01. Define the baseline before controlling changes
The statement of work should identify deliverables, assumptions, dependencies, exclusions and acceptance criteria. Without a coherent baseline, a change request becomes a debate about what was originally promised. Align proposal language with the final agreement and identify which documents govern if they differ. Keep the signed baseline accessible to the project team.
02. Give urgent instructions a practical route
Projects sometimes need work before a full variation can be signed. Define a limited interim-authorisation process with a scope boundary, spend ceiling and deadline for final agreement. Identify who can authorise it. A process that is too slow for the project may simply be ignored, leaving a trail of informal commitments.
03. Preserve the effect on time and cost
A change can affect milestones, staffing, third-party costs and warranty obligations even if the immediate task appears small. Record assumptions and dependencies alongside the quoted price. Where entitlement is disputed, communicate the position promptly and consider the contractual notice requirements. Do not retrospectively rewrite project history to fit a preferred claim.
Law, contract and recommended practice
The Indian Contract Act, 1872 supplies the general framework. Enforceability also depends on the transaction, applicable special legislation, stamping and registration requirements, and judicial interpretation. A commercially negotiated protection is not necessarily a statutory entitlement.
Connect the control to the evidence
Use this table to scope the review. The legal basis and the practical control are identified separately.
| Obligation or objective | Practical control | Evidence to retain |
|---|---|---|
| Contractual control Identify an authorised variation | Named approvers and change process | Signed change order or permitted approval |
| Recommended practice Maintain a reliable baseline | Version control for scope and assumptions | Approved statement of work |
| Contractual control Record consequential impacts | Price, time and dependency assessment | Impact note and revised milestone plan |
Records to prepare
Bring the complete, current record to the review. Preserve earlier versions where a change or disputed event makes them relevant.
Common questions
Can an email authorise extra work?
It may, depending on the contract, authority and surrounding facts. Check whether the agreed mechanism permits email and whether the sender could approve the change. Preserve the complete exchange.
Does a no-oral-variation clause end every dispute?
No. It is an important contractual control, but the entire factual and legal position still matters. Consistent operational use of the agreed process is more reliable than relying on the clause after informal changes have accumulated.
Turn the next project request into a traceable decision: included work, approved variation, limited interim instruction or disputed request. Each category should have a visible owner and record.
Legislation & official resources
These references identify the governing frameworks. Confirm the current text, relevant amendments and applicable judicial position for the matter.
- Indian Contract Act, 1872Government of Uttar Pradesh · Commercial Tax Department · Government-hosted statutory reference. Read with applicable amendments, special law and judicial interpretation.
This note is general information. The scenario is hypothetical and does not describe a client matter. The legal result depends on the facts, documents, jurisdiction and operative law. No individual lawyer review is represented by the preparation date.
Explore the AMLEGALS contracts practice