Technology diligence has done its job only when a material finding changes a decision, an owner, a date, or a budget before close. A report that ends with observations and risk ratings is evidence, not a workplan.

The pre-close tech workplan is the bridge between those two artifacts. It should tell the deal team what must happen before signing or close, what can wait until Day 1, what must be funded, and what protection is needed if the assumption fails. It is not an early version of the post-merger project plan. Its job is narrower: preserve options, remove uncertainty from the critical path, and make the first operating day safe enough to run the business.

That distinction matters because pre-close time is limited and legal boundaries are real. The buyer and target remain separate businesses until the transaction closes. The Federal Trade Commission’s guidance on pre-merger negotiations and due diligence warns that information sharing and coordination must be controlled; clean teams and third-party advisers may be needed for competitively sensitive material. A workplan can prepare for integration. It cannot give the buyer control of the target before close.

Start with decisions, not the findings register

The first mistake is to copy every diligence finding into a tracker. That creates activity without priority. The workplan should begin with the decisions the transaction cannot afford to get wrong.

Ask four questions for each finding:

  1. What deal decision does this affect? Price, structure, funding, close conditions, Day-1 posture, TSA scope, or value timing.
  2. What must be true for the decision to hold? Name the evidence, access, system capability, contract right, or business owner.
  3. What is the earliest action that preserves an option? This is often a management ask, a contract review, a data extract, or a design decision—not a large implementation.
  4. Who can make the call and by when? A task owner is not always a decision owner. The distinction should be explicit.

If a finding does not affect one of those decisions, put it in the post-close backlog. This is a deliberate filter. A long list of low-consequence remediation tasks makes the few deal gates harder to see.

Use four workplan lanes

Every action should sit in one lane. The lanes stop teams from treating all work as equally urgent.

Lane 1: Evidence and decisions before signing

This lane closes gaps that can change the investment case or the transaction terms. Typical actions include:

  • reconcile IT run-rate to the general ledger and vendor invoices
  • confirm whether a core application can be assigned, transferred, or continued after a change of control
  • map shared identity, network, ERP, reporting, and integration dependencies in a carve-out
  • validate the first-close, payroll, order-to-cash, and procure-to-pay operating assumptions
  • decide whether a value lever depends on a system change that the buyer cannot deliver in the assumed period

The output is a decision, not a completed technology program. If a contract review shows that the license cannot transfer, the workplan should record the negotiation path, the fallback, and the effect on price or timing. It should not pretend that a full replacement can be delivered before close.

Lane 2: Close and Day-1 protection

This lane covers the minimum operating state at close. It should include access, support, security, data boundaries, critical transactions, and escalation. For each item, define a pass/fail test and a fallback.

Examples are concrete:

  • named users can authenticate and reach the applications needed to sell, ship, invoice, pay, close, and support customers
  • service accounts, certificates, batch credentials, and API keys have an owner and a tested rotation path
  • the first payroll, payment file, invoice run, and close-critical report have a known execution path
  • incidents have a buyer, seller, and NewCo escalation route with response expectations
  • data that cannot cross the transaction boundary has an agreed alternative, such as a restricted extract or a seller-operated service

The Day-1 lane is where the workplan protects operations from assumptions. “Access will be provided” is not an action. “Seller IT owner confirms access for named roles, tests the path with a buyer endpoint, and supplies a break-glass procedure by T-14” is an action.

Lane 3: First-100-day value gates

This lane turns the investment thesis into a short set of technology conditions. A value gate is not “start CRM integration.” It is “the customer and product identifiers required for the first cross-sell wave reconcile, have an owner, and are available to the approved users.”

Good gates are tied to an outcome:

  • procurement savings can be measured because supplier, contract, and purchase-order data are joined
  • pricing changes can be controlled because the relevant price lists and approval rights are owned
  • working capital actions can be tracked because inventory, receivables, and payment data reconcile
  • reporting can support the board pack because KPI definitions and source systems are locked
  • TSA exit can proceed because the replacement service has passed process, data, security, and support tests

The gate should control when the model counts the benefit. If a gate is missed, finance changes the timing or the deal lead escalates the action. The workplan should not report the benefit as delivered because a project milestone was marked green.

Lane 4: Funded backlog

Some issues are real and still do not belong in the pre-close critical path. Application modernization, broad data cleanup, architecture redesign, and long-tail control improvements can wait when the business can operate safely without them.

Put them in a funded backlog with a decision date, expected value, and dependency. “Later” without an owner is abandonment. “Post-close discovery, target-state decision by Day 90, budget request after baseline is validated” is a controlled deferral.

Build an action card for every deal gate

A useful workplan row is small enough to review in a meeting and complete enough to make the next decision. Use these fields:

Field What to record
Finding The evidence-backed fact, with source and date
Deal consequence Price, cash, timing, TSA, Day-1, EBITDA, or risk impact
Action The smallest step that changes the decision or reduces uncertainty
Owner Person accountable for delivery; include the seller owner where needed
Decision owner Deal, finance, legal, business, or technology executive who can accept the trade-off
Gate Observable pass/fail condition and due date
Dependency Seller access, contract consent, data, people, vendor, or regulatory approval
Funding One-time cash, run-rate cost, TSA fee, or “not yet quantified” with a date to quantify
Fallback What the business will do if the gate fails

The “deal consequence” and “fallback” fields prevent the tracker from becoming a project-management list. They force the team to connect technology work to the transaction.

Sequence the work by constraints

Technology teams often sequence work by system size. Deal teams should sequence it by constraint. Four constraints usually set the clock.

Rights. Can the buyer use the software, data, network, brand, or vendor relationship after close? A missing assignment right can stop a cutover even when the build is ready.

Data. Can the buyer identify, extract, reconcile, and use the records needed for operations and reporting? If the answer is no, more design workshops will not make the exit safe.

People. Which seller employees, contractors, vendors, and business users hold the knowledge? If the same controller, plant lead, or integration engineer is required for close and separation, capacity belongs in the schedule.

Environment. Which systems and interfaces are shared, and what can be isolated without changing the retained business? Identity, certificates, batch jobs, EDI, reporting, and master data frequently matter more than the visible application list.

Sequence from the constraint that takes longest to remove. If data extraction requires seller support and the seller will not commit to a date, negotiate the right before funding a migration team. If a TSA expires before the minimum replacement service can be tested, change the TSA posture before the schedule becomes a crisis.

Separate “can start” from “can finish”

The pre-close workplan should distinguish work that is legally and operationally permitted before close from work that must wait. This is especially important when the parties compete.

Planning a target-state network, defining a Day-1 support model, and estimating transition cost can often begin with controlled information. Directing the target’s pricing, customer decisions, hiring, vendor negotiations, or day-to-day technology operations is different. Counsel should set the clean-team rules, approved data flows, and decision boundaries; the tech lead should put those constraints in the workplan.

Use a simple status for each item:

  • Plan: scope, owner, and decision date are defined; execution waits for close or approval.
  • Prepare: permitted evidence collection, design, or contract work is under way.
  • Protect: a closing condition, covenant, TSA term, or fallback is required.
  • Execute after close: the action is intentionally deferred with a funded owner and gate.

This avoids the false comfort of showing a pre-close program as a high-percentage completion when the key activity cannot legally or practically start.

Put economics beside the action

An action is not prioritized until its economics are visible. Use a short bridge for each material item:

baseline cost or value → required one-time work → run-rate add or saving → TSA or delay cost → net deal effect

The numbers do not need to be precise at the first review. They do need an owner and a date for refinement. A workplan that says “build standalone identity” without showing licensing, implementation, support, and delay implications has not made the decision easier.

Also record what happens if the action is not funded. The options are usually limited: move the value date, accept a TSA extension, narrow the Day-1 scope, retain a manual process, change the purchase price, or walk away from the lever. Naming the option makes the trade-off discussable.

Assign the right owners

The workplan needs one accountable owner across the deal, with specialist owners below that person.

The deal lead owns which findings enter the investment case and when unresolved items are escalated. The finance lead owns the cost, value, and timing bridge. The technology lead owns evidence quality, technical gates, and feasibility. The business owner owns whether the process can run and whether a fallback is acceptable. Legal and antitrust counsel own the permitted information flow, contract protections, and closing mechanics. The integration or separation lead owns the handoff into the Day-1 and first-100-day program.

Do not assign “IT” as an owner. IT cannot unilaterally secure a vendor consent, accept a revenue delay, or approve a business workaround.

Run a short pre-close cadence

Once the workplan exists, governance should be light and regular.

The weekly deal review should cover only four things:

  1. gates due before the next decision or close milestone
  2. dependencies blocked by the seller, vendor, counsel, or business owner
  3. changes to cost, value timing, or Day-1 posture
  4. decisions that require executive escalation

Keep the detailed task list with the workstream owners. The deal review is for decisions. A red item without a requested decision is just a status color.

At the end of each review, update three artifacts together: the workplan, the investment thesis or deal model, and the Day-1 assumptions. If only the workplan changes, the economics will drift. If only the model changes, the operating team will inherit an impossible date.

Decision triggers that should stop the default plan

Use explicit triggers so the team does not negotiate with the calendar.

  • If a Day-1-critical service has no tested fallback by the final readiness review, escalate the issue to the deal lead and executive owner. Do not call it a documentation gap.
  • If the required build, migration, testing, and training path is longer than the TSA term plus its available buffer, negotiate an extension or choose a different separation posture before close.
  • If a value lever needs data or access controlled by the seller, secure the right in the TSA or transaction documents. A verbal promise is not a dependency plan.
  • If the action changes a model assumption, move the value date, cost, or protection in the model at the same review where the finding is accepted.
  • If the action uses competitively sensitive information or could influence target operations before close, stop and obtain counsel’s approved process before collecting more data or assigning execution.

These triggers are useful because they convert disagreement into a choice. The team can accept risk, add protection, fund a bridge, or change the plan. It cannot claim that the risk is managed simply because the row has an owner.

What to do in the next 10 business days

The deal lead and technology lead should hold one focused workplan session with finance, legal, the integration or separation lead, and the owners of the first value levers. Leave with five outputs:

  1. the five to ten findings that can change price, structure, funding, timing, Day-1, or TSA posture
  2. an action card for each finding, including owner, decision owner, dependency, gate, cost, and fallback
  3. a critical-path view showing which rights, data, people, and environments set the clock
  4. a one-page list of decisions that must be reflected in the model and transaction documents
  5. a handoff pack for Day-1 and the first 100 days, with explicit exclusions and funded backlog items

The test is simple: ask the workplan to name the next action, the person who can make the decision, the economic consequence, and what happens if the gate fails. If it cannot, the diligence finding has not become deal execution yet.

Technology work before close is not measured by how many tasks are opened. It is measured by how many bad assumptions are removed while the buyer still has negotiating room.

Primary reference