Between Signing and Close: Who Is Running Technology and Cybersecurity?

The interim period between signing and close carries real technology risk. Set consent rights, incident authority, and a Day One

Every acquisition has an in-between season. The deal is signed and announced, but ownership has not yet changed hands. The seller still runs the business. The buyer is already planning around it. And the technology keeps running, or does not, through all of it.

This interim period between signing and close lasts weeks in a simple deal and months in a regulated one. It is easy to treat as dead time. It is not. Key engineers get recruited. Planned maintenance gets quietly deferred. Access reviews wait for the new owner. And if a security incident lands in this window, two organizations can each assume the other is answering.

The short answer: the seller operates until close, but both sides need four agreements before the interim period begins: a written consent list for material technology changes, an incident protocol with named contacts, protection for the people the systems depend on, and a Day One access plan.

A little structure prevents most of it. Here is what I would put in place.

Agree on what requires consent before it requires an argument

Purchase agreements often restrict material changes to the business during the interim period. Technology deserves the same clarity in operational terms. Before the period begins, the parties should agree on which actions need the buyer’s knowledge or consent.

The practical list is short. New enterprise vendors or material contract renewals. Changes to administrative access models. Major system changes, migrations, or decommissions. Hiring or departure of the people who run critical systems. Anything that alters the evidence the buyer relied on in diligence.

The point is not control for its own sake. The point is that the buyer is about to own the consequences of these decisions, and the seller’s incentives during the interim period are not the same as they were before signing. A short consent list keeps both sides honest without turning the seller into a caretaker.

Decide who answers when something goes wrong

Security incidents do not check the deal calendar. If one occurs during the interim period, the first hour matters, and the first hour is exactly when unclear authority is most expensive.

Answer three questions in writing before the period starts. Who leads the response while the seller still owns the company? How and when is the buyer informed, and through which named contacts? And who has authority to approve extraordinary response spending or outside help?

Neither side should treat this as an accusation. It is the same courtesy two commanders would arrange before a handover: a clear picture of who holds the watch until the relief arrives.

Protect the people and the work the deal depends on

Diligence tells a buyer which people matter. The interim period is when those people are most likely to leave, because uncertainty is a recruiter’s best friend.

Identify the individuals whose departure would degrade the systems the buyer is acquiring, and treat their retention as a business decision, not an HR detail. In parallel, keep the ordinary disciplines alive: patches, backups, access reviews, monitoring. Deferring them for a quarter is invisible at close and expensive a quarter later.

Sellers should want this as much as buyers. A deterioration discovered after close reads as a diligence failure, and it lands on reputations, not just systems.

Build the Day One access plan now

The smoothest closes are boring. On Day One, the new owner already knows which credentials transfer, which administrator accounts exist, who holds them, and how control moves. That outcome is manufactured during the interim period or not at all.

Prepare an inventory of administrative access, service accounts, and critical integrations. Agree on the mechanics of the handover: what is transferred, what is reissued, what is revoked, and what is logged. Decide who on the buyer’s side receives control and who on the seller’s side remains reachable for a defined period.

None of this requires the buyer to touch the seller’s systems before close. It requires both sides to write down what will happen on the day they can.

A one-page interim period worksheet

Complete this as soon as the deal signs. Review it weekly until close.

Consent list. The technology and cybersecurity actions that require buyer knowledge or consent during the interim period, and the named contacts on both sides.

Incident protocol. Who leads a response, how the buyer is informed, and who can approve extraordinary measures.

Key people. The individuals the acquired systems depend on, and the retention decision for each.

Operating discipline. The maintenance, monitoring, and review activities that must continue unchanged, with their owners.

Day One access. The credential and administrator inventory, the handover mechanics, and who receives control.

Diligence preservation. Anything that could change the evidence the buyer relied on, and how changes will be surfaced.

Frequently asked questions

Who is in charge of cybersecurity between signing and close?

The seller operates the business until close, but both sides should agree in writing who leads an incident response and how and when the buyer is informed.

What changes require buyer consent before closing?

Typically new enterprise vendors, major system changes, changes to administrative access, key technical hires or departures, and anything that alters the evidence diligence relied on. A short written list prevents disputes.

What happens if there is a breach during the interim period?

The agreed incident protocol governs: a named response lead, named contacts on both sides, and clear authority for extraordinary measures. Decide this before the period starts, not during the incident.

When should Day One access be planned?

During the interim period. An inventory of administrator accounts, service accounts, and handover mechanics makes the first morning of new ownership boring, which is the goal.

The interim period is part of the deal

Buyers spend heavily to understand what they are acquiring. The interim period is when that understanding quietly expires, unless someone keeps it current. A signed consent list, a named incident contact, and a written Day One access plan cost almost nothing. Discovering you needed them costs considerably more.

CTO Input helps investors, acquirers, and sellers govern technology and cybersecurity through transactions, including the quiet weeks between signing and close. If a deal is in that window now, draft the consent list this week. It is the cheapest risk reduction in the entire transaction, and we can help you write it.

Search Leadership Insights

Type a keyword or question to scan our library of CEO-level articles and guides so you can movefaster on your next technology or security decision.

Request Personalized Insights

Share with us the decision, risk, or growth challenge you are facing, and we will use it to shape upcoming articles and, where possible, point you to existing resources that speak directly to your situation.