Kennisbank

Who decides what needs to be ready on Day 1

Day 1 is the day an acquisition becomes visible to everyone outside the deal team: employees, customers, suppliers, regulators. What needs to be in place that day is a shorter list than most plans suggest. The question that often remains unanswered is not what belongs on the list, but who decides that.

Three types of Day 1 items, three types of decision-makers

Not everything on a Day 1 plan has the same owner. Roughly speaking, there are three categories, and each category belongs to a different decision-maker.

The first category is legally or contractually required: it must be correct because a law, permit, or contract demands it. Think of which legal entity steps Day 1 requires or what needs to be arranged on Day 1 for a cross-border acquisition. Here, the decision usually does not rest with the integration team but with legal and compliance, with the deal team as the principal. There is little room for interpretation: it is either done or it is not.

The second category is operationally critical without legal enforcement: without action something stops, but no one breaks a rule. What happens to payments on Day 1 usually falls under this, as does which access rights need to be correct on Day 1. Here the decision lies with the functional owner — finance, IT — but the judgment of what is critical enough to belong on Day 1 rests with the operating partner or COO, because they oversee the operational impact.

The third category is discretionary: it can wait, but someone considers it important. A joint announcement, a new logo on the website, a team lunch. This is where Day 1 lists often become unnecessarily long, because no one asks whether it truly needs to happen that day. Decision rights here most naturally rest with whoever owns communications, often guided by what you communicate on Day 1, but the decision deserves a deliberate judgment call, not an automatic default.

Why the question itself needs to be asked more often than it needs to be answered

The mistake this categorization prevents is treating everything on the list as equally urgent because no one determined in advance who decides on it. If the CEO, the operating partner, and the legal advisor all three assume a point rests with one of the others, it remains undecided until the night before closing. A generator that builds the synergy baseline, the Day 1 plan, and the Day 100 plan can assign an owner and a decision line to each item — not because the system knows who decides within your organization, but because it structurally raises the question instead of leaving it to the meeting in the final week.

The question that recurs with every item

Even at Day 1, the question of whether something should be combined at all still applies. A system merged on day one is sometimes a system that would have been better left running separately until there is a reason to integrate it. A team placed under one leadership on day one is not automatically better off than a team that continues to function separately for another two quarters while the rest of the organization settles. Day 1 forces speed, and speed tempts you to adopt a standard list without asking whether each item adds value or merely adds activity. The decision right over what does not make the list is just as important as the decision right over what does.

What tooling does and does not do here

A generator for the Day 1 plan does not provide an answer to who in your organization makes the final call. That is up to the deal team and the people responsible after closing. What it does do: place each item into a category, propose a provisional owner based on that category, and make the dependencies between items visible so that a decision on one item does not accidentally block another. The integration office then keeps track of which decision has been made, by whom, and what depends on it — so that the day after closing does not begin with a discussion that could have been settled three weeks earlier.

There is no track record to point to here. This is tooling that brings structure to a decision you continue to make yourself, not a party that takes that decision over from you.

From deciding to executing

Once it is clear who decides and what needs to be in place on Day 1, the next question is who carries it out. A Day 1 list with dozens of items and a small integration team naturally raises the question of how much of that work actually requires staff hours and how much of it is a matter of transferring data, checking off checklists, and tracking statuses — work that can be structured before it can be automated. The FTE TO AI work scan calculates, per task, what share of it can be taken over by AI, so a Day 1 team knows where staff hours are needed and where software can handle the work.