An acquisition announcement gives an organisation a clear date to remember. The transaction has reached an important conclusion, and people reasonably want to understand what the combined business will become. I have learned to keep that date separate from the practical transfer of every service responsibility. A change in ownership does not by itself explain a client relationship to a new colleague, establish the permissions needed for a task or make local knowledge available to a receiving team.
This distinction is easy to accept in principle and harder to preserve in a programme report. Management wants a coherent account of progress. A timetable can make several different forms of completion appear to belong to one event. When the operating conditions are not ready, a local team may continue carrying the work informally while the central report calls the transition finished. That arrangement is convenient for the milestone and uncomfortable for the people left with a responsibility the organisation has stopped acknowledging.
Closing changes the organisation before it teaches the work
In 2016 our integration of three acquired offices identified nine service responsibilities for transfer. The legal completion of the transaction remained with the proper owners. My concern was the receiving account: what each responsibility involved, who would carry it and which conditions were needed before the transfer could work. The exercise did not itself move an insurance policy, settle a contractual permission or replace specialist authority. Those matters remained distinct from the internal operating timetable.
Six responsibilities moved by the original date. Three needed local ownership for another eight weeks. We funded US$680,000 in dual operation and cover, separate from acquisition consideration. A programme colleague objected that the continuation would make the integration look incomplete. I agreed with the description. It was incomplete in three defined respects, and our management account needed to preserve that fact. Calling the work finished would not improve the receiving conditions; it would only make the continuing dependence less visible.
The acquired teams did not possess indispensable knowledge merely because they had always performed the work. Some practices could be documented, changed or replaced. The receiving review needed to identify the actual requirement rather than defend every local convention. At the same time, a centrally familiar task name did not prove that the work was identical in every office. The relevant context could include an agreed service scope, a specialist referral route or a relationship whose next step depended on an earlier conversation.
I found it useful to ask the receiving owner to explain the responsibility back in their own words. What happens next, which decision can they make and when must another person be involved? That conversation could reveal a gap that a completed handover template did not. It also gave the local team a more precise way to describe what remained, instead of making a general claim that the new organisation did not understand its clients. The aim was usable responsibility, not a competition between central and local credibility.
Retained ownership needs an explicit end condition
An extension can become a form of avoidance if nobody states what it is intended to resolve. I did not want the three responsibilities left with local teams indefinitely because the revised date was less visible than the original one. Each needed a receiving owner, a description of the missing condition and a review point. The additional eight weeks were supported by defined work, not simply permission to continue the old arrangement until someone felt more comfortable.
The local owners also needed clarity about the responsibility they retained. A programme can create conflicting expectations when one team is told to step back while another has not yet accepted the work. During the extension, the account needed to identify who was acting, who was learning and who could authorise a decision. The distinction protected the integrity of the handover conversation. It did not remove the need for appropriate access, permissions or specialist review, and it did not create authority through the act of writing a name beside a task.
I wanted the receiving organisation to learn enough to carry the responsibility without asking the local colleague to remain an invisible fallback afterward. That meant examining the next likely question, not only the task completed during the demonstration. What happens if the expected document does not arrive, a client asks something outside the agreed scope or a specialist decision is needed? The answers should identify a process and an owner. They should not rely on a personal favour from someone whose role has supposedly ended.
The transfer of the six ready responsibilities remained a real achievement. Keeping the other three open did not invalidate it. Equally, success with six did not prove that the same conditions existed for the rest. Management needed a differentiated account rather than a single completion percentage used to silence the remaining question. A proportion can describe the report, but it cannot explain the operational significance of a responsibility that still lacks a prepared receiving arrangement.
Account for the extra weeks without hiding the reason
The US$680,000 mattered because the extension required people and support the original plan had not fully provided. I did not try to make the correction disappear inside the transaction price. Acquisition consideration and operating transition expense answer different questions. Keeping them separate allowed colleagues to understand what the business had paid for the organisation and what it then spent to carry its service responsibly through the change. The expense was not evidence of a realised financial benefit or a claim that the acquisition had failed.
There was also a management cost to revising the narrative. A programme sponsor had to acknowledge that an attractive date did not settle the receiving work. Local and central teams had to remain engaged after the first milestone passed. I considered those consequences preferable to a nominally completed integration whose remaining obligations surfaced later through repeated requests for help. The institution should know where it still depends on an old arrangement while it has an opportunity to manage that dependence deliberately.
The revised handover work concluded after the additional period. I kept the original delay in the retrospective rather than describe only the final state. That history explains why the next integration plan should test receiving conditions earlier. It does not establish that every acquired office requires an eight-week extension or that the same expense would be appropriate elsewhere. The case offers a way to examine responsibility, not a standard timetable for transactions with different legal and operating circumstances.
I now want an integration paper to say which event completes which obligation. A legal close, an access approval, a service handover and a team’s ability to answer the next client question may occur at different times. The leadership task is to connect those events without pretending they are identical. An acquisition can create a stronger institution, but the client’s continuing service still needs somebody prepared and authorised to carry it. That practical account deserves its own place beside the date the transaction closed.