TSA Bootstrap — auto-generate work plans

Bootstrap is the step between having the document and having a program. It reads the imported addendum and produces outline work plans per workstream, along with the tracker rows behind them.

Why it exists

The addendum already says what has to happen: which services run, for how long, on what notice, and what has to be true before each can stop. Retyping that into a plan is a week of work that adds nothing. Bootstrap does the mechanical part so your time goes on the judgment.

Running it

1. Import the addendum first and let the extraction finish.
2. Run the bootstrap from the TSA Methodology page.
3. Review the drafted plans workstream by workstream.

Reading the output properly

Treat it as a competent first draft by somebody who has read the contract and not met your people. It will have the services right and the sequence broadly right. It will not know that your Finance lead is leaving in March, or that the seller's IT team has form for missing dates. Those corrections are the work.

What it does not decide

It will not tell you which services to exit first as a recommendation. It gives you the entanglement analysis, from Walk the Walls, and the notice arithmetic, from the tracker, and the sequencing decision stays with you. On most carve-outs the standalone services go first and the three-plus-dependency ones are where the seller has leverage, but that is a judgment about your deal.

After bootstrap

The plans behave like any other work plan: edit them, assign them, set status, and they feed the Roadmap and the reporting like everything else.