TSA exit failure modes are not random. The same ten patterns appear across carve-outs, across industries, across deal sizes. Recognising the patterns is what lets disciplined buyers avoid them. This article catalogues the patterns that cause the most exit failures and connects each one to the broader TSA exit strategy framework.
Failure mode one. The application inventory is incomplete. The seller provides a list of in scope applications during diligence. The buyer accepts the list. By month six, additional applications surface that were not on the original list but that the Newco depends on operationally. Each late discovery extends the timeline. The fix is a buyer led application discovery in the first 60 days, validated against actual transaction flow.
Failure mode two. Integration count is understated. The seller documents the major interfaces. The minor interfaces, the legacy file drops, the spreadsheets that move data between systems, the manual cut and paste operations, all of these are usually missing. By cutover weekend, the team discovers integrations no one documented. The fix is an integration discovery exercise that maps every data flow into and out of the Newco perimeter, including manual flows.
Both failure modes share the same root cause. The seller's documentation is a starting point, not a deliverable. The buyer's team has to validate every assumption against the operating reality. The work is unglamorous and time consuming. It is also the difference between an exit on schedule and an exit that slides into extension territory. The readiness assessment in the first 60 days is where this work belongs.
Scope underestimation compounds. A missed application surfaces a missed integration which surfaces a missed business process which surfaces a missed master data set. Catching the first scope miss early prevents the cascade. Catching it late means every downstream miss is found in production.
Failure mode three. Governance is monthly when it should be weekly. The TSA governance committee meets monthly to review status. By the time a slip surfaces in the monthly meeting, four weeks have already been lost. Decisions queue up across meetings. The exit drifts. The fix is workstream level weekly governance with the program governance committee meeting biweekly, not monthly.
Failure mode four. The seller's program manager runs the meetings. The seller controls the agenda, the slides, the status reporting. The buyer's team responds rather than directs. Decisions favour the seller. The fix is for the buyer to chair every meeting, set every agenda, and own the status reporting. The seller's input is welcomed. The seller's control is not.
Governance is the discipline that converts a plan into an executed program. Without weekly cadence, blockers fester. Without buyer ownership of the agenda, the seller's preferred sequencing wins. Both of these are easy to fix and frequently neglected. The implications are covered in TSA exit governance best practices.
The third element of governance is escalation. A blocker that cannot be resolved at the workstream level needs a defined escalation path to the program governance committee within 48 hours, not at the next monthly meeting. Without a defined escalation path, blockers sit. Sitting blockers become slip drivers.
Failure mode five. Data quality in the source system is worse than expected. Duplicate master records, broken referential integrity, incomplete history. Conversion takes longer than planned. The first mock conversion fails to reconcile. Subsequent mocks fail too. Cutover dates slip. The fix is a data quality assessment at the start of the program with explicit decisions on each issue before conversion logic is built.
Failure mode six. The Newco team is understaffed. The buyer assumes the systems integrator will fill the gaps. The integrator only does what is in scope. Decisions that the Newco team should make sit unmade. Documentation that the Newco team should produce is missing. By month nine, the program is short the people it needs and the schedule slips. The fix is staffing the Newco team to 70 percent of steady state by month three, not waiting until the operating model is finalised.
Both failure modes are about treating the work as physical reality, not a paper exercise. Data conversion takes the time it takes. The Newco team has to exist in real terms. Programs that treat these as line items to be optimised end up underfunded in the work that matters most.
Resource discipline starts at deal close. The operating partner approves the Newco standup budget independently of the TSA cost. The Newco hires permanent staff, not just contractors. The systems integrator scope is for delivery, not for substitution of permanent staff. Each of these choices reflects a buyer who understands that the Newco is a real business that needs real capacity, not a project to be optimised.
Failure mode seven. Change requests accumulate without commercial discipline. The seller proposes scope changes throughout the program. Each one adds cost. Each one moves a deadline. The buyer's program team signs off because the operational pressure to keep moving outweighs the commercial discomfort of pushing back. By month nine, the TSA total cost is 20 to 30 percent above the original baseline. The fix is a change control protocol with operating partner sign off for any change above a defined threshold.
Failure mode eight. Extension fees are paid without renegotiation. The TSA defines extension fees that escalate by quarter, often by 50 percent each quarter. As the cutover slips, extension fees accumulate. The buyer pays. The seller has no incentive to accelerate. The fix is to renegotiate the extension fee curve at the first sign of slip, not at the moment the fee is invoiced. The seller's leverage is highest when the buyer is desperate. Renegotiation 90 days before the extension date is much cheaper than 30 days after.
Commercial drift is the most expensive failure mode. The other failure modes have direct operational consequences. Commercial drift is invisible until the year end review shows that the TSA cost the buyer 30 to 50 percent more than planned. Buyers who track TSA cost on a monthly basis against a defined baseline catch drift early. Buyers who do not, find out at the end.
The commercial workstream is often missing from the buyer's program structure. Most buyers staff IT, finance, HR, procurement separation. Few staff a commercial workstream with a named owner who manages TSA cost, change requests, and extension fee exposure. Creating the role is the single most leveraged staffing decision in the program.
Failure mode nine. The cutover decision is forced. The team knows the cutover is not ready. The reconciliation has variances. The integration testing has open issues. The data conversion has unresolved gaps. The cutover happens anyway because the date was committed and the team does not exercise the rollback option. Production issues surface in the first week. The Newco runs in degraded mode for six to eight weeks while issues are fixed in flight. The fix is to write the no go criteria in advance and use them.
Failure mode ten. Hypercare is undersized. The team assumes operations will run normally after cutover. Production issues consume resources that were meant to roll off the program. The Newco operations team is exhausted by week three. Quality of life issues compound. Resignations follow. The fix is to size hypercare at 150 percent of steady state for the first two weeks and 120 percent for the next two weeks, with explicit handoff criteria before resources roll off.
Both failure modes share a root cause. Programs feel the pressure to declare victory once the cutover lands. Resources move on. Attention shifts. The reality is that the four weeks after cutover often have more program risk than the four weeks before. Disciplined buyers treat the post cutover period as part of the cutover, not as a separate phase. Detailed milestone setting is covered in TSA exit milestones, explained.
The pattern across all ten failure modes is the same. Each is predictable. Each is preventable. The fix in every case is a discipline that the buyer's team commits to before the program starts and enforces throughout. Programs that fail rarely fail because the work was technically impossible. They fail because the discipline gave way under pressure. The discipline is what separates the buyers who land on schedule from those who pay extension fees.
The committee structure, the cadence, and the escalation paths that keep an exit on track.
Read the article →The buyer's view of how long a TSA exit actually takes and where the gates sit.
Read the article →The diagnostic that surfaces the failure modes before they surface in production.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →

Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →