Questions to Organize an Acquisition Handover

New owner meeting with the existing team after a business acquisition

A closing date and a handover plan answer different questions. The first records a transaction milestone; the second asks who will handle particular responsibilities afterward. A useful working note makes those responsibilities, supporting records and unanswered questions visible. It does not predict the value of a business or promise that a fixed number of days will produce a successful transition.

Start with the actual handover commitments

What does the signed arrangement say the seller will provide, for how long and under what conditions? Identify the document and responsible reviewer rather than relying on a general impression that the seller will remain available. Keep proposed help separate from an agreed obligation. Questions about the meaning or enforceability of an agreement belong with the appropriate adviser reviewing that agreement.

Make a short list of the responsibilities that need a named contact: customer enquiries, supplier coordination, employee questions, records and decisions awaiting review. A name in a draft does not establish that the person has accepted the role. Record acceptance, an alternative contact and remaining uncertainty separately.

Prepare conversations without inventing assurances

Before preparing a message for staff or customers, distinguish confirmed arrangements from plans and unanswered questions. What can the person sending the message actually confirm? Which question requires another person's answer? A reassuring script should not substitute for evidence about pay, benefits, staffing, service or contractual terms.

For an introductory conversation, useful original questions include: Which responsibilities do you currently handle? Which decisions need an answer soon? Which records explain the current process? What would help the next person understand an exception? These prompts gather context; they are not a validated interview method or a promise about employee or customer retention.

Record dependencies before proposing changes

For a process under review, write down its purpose, the people who use it, the information it needs and the decisions it supports. Ask which exceptions have been omitted from the summary. Keep the seller's explanation, another employee's account and a record inspected by the reviewer as separate sources. Agreement between two accounts does not by itself establish that the whole process has been observed.

A proposed change needs its own question: what evidence supports it, who may authorize it, and which related responsibilities would be affected? This article supplies no blanket instruction to wait sixty days, change systems in week seven or make exactly one improvement. The timing and authority for a specific action remain questions for the people responsible for it.

Separate a status report from a completed handover

Use distinct labels for requested information, information received, information reviewed and an arrangement confirmed by the responsible person. For example, a request for a supplier contact list may have been sent while the list remains unavailable. A document in a shared folder may be readable while its period, completeness or authority is unresolved.

Keep sensitive account access and personal information within the organization's established procedures. A planning note can identify the responsible person and the status of an access question without copying credentials or assuming that possession of a password authorizes an action. No account transfer or security assessment has been performed for this article.

Define each comparison before interpreting it

If a review includes customer counts, staffing changes, collections or margins, record the definition, period and source next to the number. Ask whether the opening and later figures describe the same population and accounting basis. A changed count does not establish why it changed, and a resignation alone does not establish a cause.

Keep operational questions separate from an assessment of financing, accounting or tax treatment. Ask the relevant adviser which documents and definitions are needed for the particular question. No retention threshold, cash reserve, coverage requirement, forecast horizon or return estimate is recommended here.

Make the next review concrete

End the note with an open question, the evidence needed, a responsible person and a proposed review date. Mark a date as proposed until agreed. At the review, record what has actually changed and which questions remain open. Completing a checklist is not evidence that a business can operate without its owner or that a purchase has preserved or increased its value.

These are original editorial preparation questions. They are not a report of a buyer's experience, a quotation from Buying Wealth, a book chapter method or a review of a live transaction. Readers can explore information about Buying Wealth and the existing purchase options below.

Handover planning questions

Does a ninety-day schedule establish a successful handover?

No. A calendar label does not confirm accepted responsibilities, completed work or a business outcome. Record the particular arrangements and remaining questions.

Should a new owner always wait sixty days before changing a process?

This article makes no universal timing recommendation. Identify the evidence, relevant commitments and person responsible for authorizing the specific action.

What does a name beside a task establish?

It may identify a proposed contact. Record whether the person has accepted the responsibility and what remains unresolved.

How should a review describe an unexplained change in a metric?

Record its definition, period and supporting source, then preserve uncertainty about the cause. A numerical change alone does not explain a transition outcome.

About Dr. Connor Robertson, author of Buying Wealth.