Prepare a business handover: Transfer open work and access separately

During a business handover, your team should be able to continue ongoing work reliably. A change-of-ownership announcement explains the new contact for business management. Daily operations also need answers to specific questions: who decides on an open order, where is the last confirmed position recorded, and who can actually use the necessary working tools? Clarifying these points individually enables the people taking over to continue with a clear purpose.

Start with the organisational handover of business cases already in progress. The arrangements for business succession and their legal structure require their own professional framework. This guide considers the practical continuation of work: understandable cases, confirmed responsibility and appropriately configured access. Acceptance of an order and permission to operate a system are checked separately. Being able to reach a customer account does not establish who may make an outstanding decision.

Define the scope of the operational handover

First describe which work areas are to be transferred. A business can consider its entire ongoing organisation or prepare a defined area first. Name the activities involved and the people who know the previous process. A blanket note about handing over the office leaves it unclear whether quotations, ongoing orders, later queries and internal organisation are all included. A specific scope makes the subsequent decisions manageable.

Agree a common reference point for preparation. Which cases were open at that point, and what new work will arise before the actual transition? The business continues operating during preparation. Your overview therefore needs agreed maintenance so that an order confirmed in the meantime remains included in the handover. Those involved should be able to identify the work position to which a statement refers.

Consciously distinguish taking over stored material from continuing an activity. A folder can be complete while the next decision about its contents remains unresolved. For each area, therefore ask what work must continue after the handover. This aligns preparation with actual operations rather than merely counting transferred files, keys or lists.

Organise open cases by their next step

Review ongoing work according to how it is actually being handled. A quotation may await a customer decision, an order an internal discussion, and a completed service an agreed follow-up. Record the confirmed position and the next necessary step. The word open alone is insufficient because it tells the new owner of the work neither what to do nor when to look again.

Separate confirmed information from assumptions. Someone might remember a verbal query without knowing whether the reply has already arrived. Record that uncertainty as a clarification task. The person familiar with the history can establish the necessary connection. An unconfirmed assumption will then not inadvertently become the basis for a decision made on behalf of the business after the transition.

Associate documents with the relevant case where they are needed to continue it. The person taking responsibility should understand the relationship between the enquiry, the previous response and the outstanding work. A collection of individual files without a connection to the next step makes the takeover harder. Check the specific case to see whether the history is understandable from the existing context or needs an additional explanation from the previous responsible person.

Explicitly assign operational decisions

Clarify who will handle the work and who should decide outstanding questions. Both roles may belong to the same person, but need not. An employee might prepare a case and obtain feedback while another responsible person confirms a change to the service. The handover should reflect that actual process so that a new processing responsibility is not understood as unlimited decision-making authority.

Ask the person taking over to confirm the task explicitly. Entering their name in an overview is insufficient. They must know the current position, understand the next step and be able to identify open questions. If a necessary decision is missing, it remains visible as a separate item. You can then distinguish responsibility already accepted from matters requiring professional or organisational clarification before work proceeds.

Consider decisions previously concentrated in the outgoing owner’s hands. Exceptions may have been resolved in conversation without the team clearly understanding the decision path. Describe the trigger and the role responsible in future. The solution is not to transfer every previous habit unchanged to one new person. The business decides which understandable route will support the upcoming work in the intended new organisation.

Treat working access as a separate handover element

Identify the tools needed for the selected activities. These may include business applications, shared storage or agreed communication channels. Assign each required access to a specific work purpose. A complete catalogue of every conceivable application does not establish who should actually perform which work. The link to the transferred case helps clarify the necessary use with the relevant responsible people.

Distinguish an existing user account, permission to use it and the professional role within the business. Involve the responsible administrator or provider through the intended route for setup or changes. Another person’s personal login details do not become a handover document. Instead, check which individual access is intended and actually authorised for the confirmed task. Technically possible access does not replace that decision either.

Record outstanding access questions separately from tasks already accepted. Someone may understand their future responsibility but still be unable to use a necessary application. A specific preparation step is then missing. Conversely, an account may already be configured while the scope of work remains undecided. This distinction shows what kind of clarification is needed next and who can provide it.

Explain connections implicit in previous daily work

Ask the previous responsible people about connections that are hard to recognise from documents alone. Several individual orders might belong to a jointly agreed sequence. Or internal preparation may be necessary before an already planned response makes sense. Explain these connections on the relevant case. The person taking over needs the reason for the next step so that they can later assess a change independently.

Ask for specific work examples rather than only general advice. What question was clarified most recently, and what answer is still missing? Where was the decision recorded? Who can explain an unclear connection? These questions produce a usable explanation of open work. A lengthy account of former processes is helpful where it actually makes the transferred case easier to understand.

Include internal follow-up work too. A business transfers more than visible customer contacts: prepared coordination, documents still needing assignment, and planned queries to participating service providers may also matter. Capture work that actually exists. Its significance follows from the operational process, not from whether it already appears in a particularly detailed overview. Preparation can add missing context deliberately without inventing new tasks.

Use a practical takeover rehearsal

Choose a manageable open case and ask the person taking over to explain how they would continue it. Using their configured access, they open the intended documents and show which position is confirmed. They then identify the next action and the role responsible for its decision. This rehearsal connects access, understanding and responsibility. Merely signing into a system successfully would demonstrate only one of those elements.

If the person gets stuck, describe the specific gap. Is a document connection, a professional confirmation or authorised working access missing? Assign the necessary clarification to the appropriate responsible person. The rehearsal need not involve a real customer message or an order change. An explained walkthrough using existing information can already show whether the prerequisites for later processing are present.

Repeat the rehearsal selectively on a case with a different handover situation if relevant to your scope. A waiting quotation raises different questions from an ongoing order requiring internal coordination. The aim is to continue different transferred activities with an understandable basis. A successful rehearsal in one area is not a blanket statement about every activity in the business. The overview therefore identifies specifically what has already been checked.

Follow open points through to confirmation

Agree who will maintain the handover overview after the first discussion. Missing information may arrive later while another case progresses. Both incoming and outgoing responsible people need the same recognisable reference. Record changes on the relevant case rather than collecting general confirmations without context. You can then see which individual clarification is complete and which work still needs a response.

An open point needs a responsible person and an understandable trigger for reviewing it again. The new management might, for example, await a provider’s confirmation of intended working access. That specific response is then the next relevant trigger. The team should not have to infer what is missing from a general reminder. Activities already possible can continue with confirmed responsibility while the specific prerequisite is tracked separately.

At the end, confirm the areas actually taken over against their work position. Which tasks have an understandable assignment, which decisions are clarified and which necessary accesses work? Explicitly carry remaining points forward. The handover thus becomes a traceable operational transition. A signature under an unspecific master list would not explain outstanding prerequisites or give the new responsible person concrete help for the next working day.

Take in new work correctly during the transition

Decide how new enquiries arriving during preparation enter the handover. A customer may add something to an old order or submit an unrelated new enquiry. The responsible person assigns the incoming information to its actual context. It remains clear whether an already captured case has changed or new work with its own responsibility has arisen.

Also discuss communications that still reach the outgoing management personally. Where needed for work, the relevant information must reach the responsible handler through the agreed business route. A general ownership-change announcement does not prove every ongoing matter reaches its intended destination. Use an imagined incoming message to check how you would connect it to an existing case and inform the new responsible person.

If the former management remains available for certain professional queries, describe that role specifically. What question can they explain, who receives the explanation and who subsequently decides how to proceed? Supporting information differs from continuing responsibility for handling the work. The team should be able to rely on a clear working route rather than receive different decisions on the same case depending on who is available.

Finally, agree how to add an open case discovered later that was previously absent. Add its actual position, available documents and remaining clarification. The new management confirms the appropriate assignment. This keeps the handover open to concrete additions. It replaces neither careful preparation nor checking whether the newly found case is already being handled elsewhere.

Organise ongoing business cases in context

webRichtung core connects contacts, quotations, orders and invoices in their business context. Tasks and deadlines can be managed alongside the relevant case. Choose a specific handover case as your starting point and create your access through the module page. Agree organisational acceptance and necessary access decisions with the responsible people; the platform is not presented here as automatically transferring another person’s permissions.

Sources

The core module page describes the actual service connection to business cases, tasks and deadlines; read on 25 October 2026. The organisational handover approach described is an editorial recommendation. It does not assess company-law, tax or contractual questions of business succession.