Change control is where scope creep dies.

Why change control matters more than it looks.

The TSA on signing day defines a fixed scope, fixed pricing, and fixed performance expectations. Reality starts changing on Day One. The buyer needs a new report. The seller wants to change a delivery model. A regulatory requirement creates new work. A system upgrade alters the operating environment. Each of these is a change. Without a defined mechanism, each becomes a negotiation in itself, and the cumulative effect is scope creep and price inflation.

Strong change control turns those conversations into routine process. A change request arrives, gets scoped, gets priced, gets approved, and gets executed under the same contractual framework. The buyer knows what the change will cost before agreeing. The seller knows the buyer has approved before incurring cost. The relationship operates predictably even as scope evolves.

Weak change control creates the opposite. Changes get handled informally through email or governance meetings. Pricing emerges in arrears, sometimes months later. The buyer discovers the scope has expanded only when the invoice arrives. The seller has performed work the buyer never explicitly authorized. Disputes follow. Time and management attention get consumed. None of it is the seller's fault. The contract did not require discipline.

The full operational impact of weak change control surfaces in TSA exit failure modes, where scope drift compounds into delayed exit and elevated extension fees.

The four step change request process.

Step one is the written change request. Either party submits a written description of the proposed change. The request includes a description of the scope, the requested timing, and the rationale. Verbal requests do not count. The discipline of a written request prevents the casual conversation that turns into invoiced work.

Step two is the impact assessment. The seller, or the buyer for changes affecting buyer responsibilities, prepares an impact assessment within a defined window, typically five business days. The assessment covers the cost impact, the timing impact, the SLA impact, and any flow on effects on other services. The assessment is a document the parties can review and discuss with a common factual basis.

Step three is approval. The change is approved by an authorized representative of each party. The approval level should be tied to the scale of the change. Small changes under a defined threshold can be approved at workstream lead level. Medium changes go to the governance committee. Material changes go to executive approval. The approval ladder prevents both parties from inadvertently committing to expensive changes through informal channels.

Step four is the contract update. Approved changes are documented in a change order that becomes part of the contract. The change order describes the revised scope, the revised pricing, the effective date, and any other terms affected. The change order is signed and filed with the master agreement. Without that document, the change becomes contested in the future when memories diverge. The governance discipline that supports this is in TSA exit governance best practices.

Pricing changes under change control.

Pricing under change control should reference the cost-plus methodology already in the contract. A new scope item gets priced at the same cost-plus rate as comparable existing services. The seller does not get to invent a new rate for new work. The methodology is locked at signing. New work fits inside the methodology.

When the change request involves a service that does not have a clear comparable in the original contract, the pricing should still reference verifiable cost components. Hours, headcount, infrastructure, and pass-through costs. The seller documents the cost. The same mark-up percentage applies. The buyer can verify each component. Pricing should never emerge as a lump sum estimate without backup.

The change order should also address whether the new scope creates new pass-through costs or alters existing pass-through allocations. Without an explicit statement, pass-through allocations can shift quietly through the change process. The buyer should require any change order that affects pass-through to state the new allocation methodology explicitly. The mechanics of pass-through under contract are in TSA pass-through pricing.

Where a change reduces seller scope, the pricing should reduce proportionally. The seller's draft often retains full pricing even after a reduction, on the argument that the underlying cost structure is fixed. Sometimes this is fair. Often it is not. The buyer's posture should be that scope reduction produces price reduction unless the seller can document why the cost is unavoidable.

When change control breaks down.

Change control breaks down in three predictable ways. The first is the urgent request. The buyer needs something done immediately, the formal process feels slow, the workstream lead asks the seller to just do it. The seller does it. The invoice arrives three months later. The buyer disputes. The seller cites the verbal authorization. Nobody is wrong about the facts. Both sides are wrong about the discipline.

The second breakdown is the small change accumulation. Each individual change is small enough that the formal process feels like overkill. Twenty small changes later, the cumulative effect is a meaningful expansion of scope and cost. The buyer's invoices have crept up. No single decision was the cause. The contractual discipline should require change control regardless of size, with simplified processes for small changes rather than waivers.

The third breakdown is the scope clarification dressed as a change. The seller identifies an item in the original scope that the seller now wants to characterize as a change. The buyer believed the item was always included. The dispute consumes governance capacity. Strong change control distinguishes between clarification, where the buyer is correct that the item was always included, and genuine change, where the scope is being expanded. The audit rights that surface these distinctions are in TSA audit rights.

The buyer's operational discipline should be that nothing gets done without a written change order if it is outside the documented service catalog. The discipline is uncomfortable in the early weeks of the TSA when operational pressure is high. It is the discipline that pays off in months three through twenty four when the TSA is running normally.

Drafting change control that operates.

The change control clause should specify the standard form of a change request, the maximum response time for impact assessment, the approval thresholds tied to dollar value, the form of the change order, and the rule that nothing outside the change order changes the contract. Each of these specifics turns the clause from policy into operating procedure.

The clause should also specify the consequence of work performed without change order approval. The default should be that the seller cannot charge for unauthorized work, and the buyer cannot demand it without paying. Without that explicit consequence, both parties have an incentive to operate outside the process, because neither bears clean accountability.

The clause should provide an expedited process for genuinely urgent changes. The expedited process compresses timing but preserves the discipline. A written request, a same day impact assessment, written approval by authorized representatives, and a follow up change order within five business days. The expedited path exists so that urgency does not become the excuse to bypass the discipline.

Finally, the clause should integrate with the governance rhythm. The standing agenda at the workstream meeting and the governance committee should include change request status. Open requests should be tracked through to closure. Pending impact assessments should be flagged. The change log should be visible to both parties. The mechanism is light but disciplined, and the discipline is what makes the TSA operate as a commercial agreement rather than a slow drift into unbounded scope.

More on TSA negotiation.