Change control procedure: documents to prepare
A change control procedure protects both sides when a technology contract needs to move. It starts with a written change request, runs through impact assessment and approval, and ends with a signed change order. Miss one document and the change stays informal — and unenforceable. This page sets out what to prepare, who signs off, how long each stage typically takes, and where the point of no return actually sits.
What changes once the procedure starts
Before a formal request, either party can adjust scope by email and call it agreement. Once the change control clause is triggered, informal agreement stops counting. Only the documents named in the contract move the change forward from that point. This shift matters most when a timing dispute arises later: a court or arbitrator looks for the paper trail, not the conversation that preceded it.
Verbal instructions, chat messages and meeting notes rarely survive as evidence of a change. Teams that treat the change request form as optional often discover this only once the dispute has already started. The safer habit is to open the formal document on day one, even for a change that feels small.
The point of no return sits at the signed change order, not at the request and not at the approval decision. Before that signature, either side can withdraw the request without cost. After it, the variation binds both parties on the terms stated in the order itself, including any adjustment to price or schedule.
Documents to prepare
Most technology contracts define change control through a handful of recurring documents. The table below sets out the usual sequence and who typically produces each item.
| Stage | Document | Prepared by | Typical timing |
|---|---|---|---|
| Request | Change request form | Requesting party | Day 0 |
| Assessment | Impact assessment (cost, schedule, risk) | Receiving party | 5–15 business days |
| Decision | Approval or rejection notice | Change control board or nominated approver | Within the period set by the contract |
| Implementation | Signed change order | Both parties | On acceptance of the assessment |
| Record | Updated schedule or statement of work | Contract owner | After signature |
Two documents in this sequence are easy to skip and expensive to miss. The impact assessment is often treated as a formality; in practice it is the record a party relies on if the change later runs over budget or overruns the schedule. The updated schedule or statement of work is the only place the new baseline gets recorded — without it, the original scope stays the reference point in any dispute, regardless of what was actually delivered.
A short cover note is worth adding to the change request itself: the clause number relied on, the deadline for a response, and the name of the person authorised to approve on the other side. None of this is required by most contracts in a strict sense, but its absence is the most common reason a change control exchange drags on past its own deadline.
Who decides and how long it takes
The contract itself names the decision-maker. In most agreements this is a change control board, a single nominated approver, or — in smaller arrangements — the counterparty's contract owner directly. The decision period is set by the same clause: some contracts allow five business days for a response, others thirty.
Silence is rarely treated as approval. Most change control clauses state the opposite: no response within the stated period means the request lapses or must be resubmitted. Preparing the request with a clear deadline reference, stated plainly rather than implied, avoids this trap and gives you something concrete to point back to later.
Two scenarios worth planning for
If you are the party asking for the change, prepare the impact assessment yourself and attach it to the request, even where the contract puts that burden on the other side. A pre-filled assessment moves the decision along faster and reduces the room for a low-effort rejection.
If you are the party receiving the request, treat the assessment stage as the moment to raise cost and schedule concerns formally. An informal objection sent later, after the change order is signed, carries far less weight than one raised during assessment.
If the other side does not respond
If the contract sets a decision deadline and it passes without a response, check the clause for a default outcome first. Some agreements treat silence as rejection; a few treat it as deemed acceptance under specific conditions. Send a written reminder that references the deadline before assuming either outcome applies.
If the contract sets no deadline at all, the request has no formal expiry. In that case, a reasonable-notice letter — setting a new deadline and referencing the original request — restarts the clock in a way that is easier to evidence later, should the change ever be disputed.
Sources and limits
This page describes the procedural shape of change control: the documents, the sequence, and the decision points that most technology contracts share. It does not tell you what a specific contract requires — clause wording varies between agreements, and the deadline, the approver and the default outcome all have to be read from the document itself.
It also does not extend to disputes that arise once a change has already been implemented without sign-off; that question sits closer to breach and remedy than to procedure. Where the underlying question concerns what a counterparty record can actually establish before a dispute reaches that stage, see Counterparty in United Arab Emirates and what to prepare.
Where the dispute concerns a specific document rather than the counterparty behind it, the same logic applies in a different form: see Document in Norway explained for how a single document is checked before anyone relies on it.
Verified
This page was last reviewed on the date shown in the site footer. It reflects standard drafting practice in technology and outsourcing contracts, rather than a rule drawn from any single jurisdiction's statute. The team behind the underlying registry work is described on the The people behind the reports in detail page.
Related reading
A closely related procedure covers a different trigger point in the same type of contract: see Audit rights procedure: documents to prepare for what to prepare before an audit clause is invoked.
FAQ
How long does change control procedure take in practice? Most requests resolve within two to six weeks from submission to signed change order. The main variable is how quickly the impact assessment is completed and how quickly the approver responds.
Which documents are needed to start? A written change request describing the proposed change, its trigger, and the clause under which it is raised. Everything else in the sequence follows from that first document.
What happens if the other side does not respond? Check the contract's default rule first. Where none exists, send a written reminder with a new deadline; this restarts the process on a record you can point back to later.
Talk to us
If a change is already in dispute, timing usually matters more than argument, and the earlier the paper trail is checked the better. For a related question outside technology contracts, see When the creator disputes the mint and the deadline.