Shane Murphy: A Cambridge Business Handover Should Start with the Unfinished Work

When a piece of work changes hands, the easiest material to collect is often the material least likely to explain its present condition. There may be a folder of documents, a long email chain and a list of completed tasks. The new owner still needs to know what requires attention tomorrow morning. My view is that a useful handover should begin with the unfinished work.

I am Shane Murphy, also known as Shane Ian Murphy, formerly of Cambridge and formerly of Limitless Mobile, where I was co-founder and Chief Business Development Officer. This commentary draws on a commercial perspective associated with my UK technology background. The Cambridge business described below is a hypothetical example, not an account of a client assignment or a claim about a particular company.

Imagine a small team preparing to introduce a new internal ordering process. One coordinator is moving to another responsibility, and a colleague will take over. The project folder contains draft instructions, supplier correspondence and several versions of a schedule. A document-by-document tour could consume an afternoon without establishing whether the team is ready to proceed.

I would open the handover with a short account of the present state. What is working? What has been agreed? What is still being considered? What must happen before anyone can describe the process as ready? Those questions create a usable frame for the documents that follow. They also reveal disagreements that a tidy folder structure can hide.

The first working list should separate actions from decisions. An action might be to obtain a corrected description from a supplier. A decision might be whether the team accepts the revised timetable. Combining the two can produce misleading entries such as “sort out the schedule”, which conceal both the missing information and the authority needed to resolve it.

For each open action, I would include a responsible person, the intended result and the most relevant supporting material. A due date is helpful only if its meaning is clear. Is it a firm commitment from the person completing the task, an internal target, or the date on which somebody intends to ask for an update? These distinctions prevent the handover from turning an expectation into a promise.

For each pending decision, the recipient needs the alternatives under consideration and the reason a decision has not yet been made. Perhaps a price has not been confirmed or an operational constraint remains unresolved. There is little value in knowing that a meeting is scheduled if nobody can explain what information will allow that meeting to reach a conclusion.

The second list should capture dependencies. If the instructions cannot be finalised until a supplier confirms a process, say so next to the affected work. Dependencies should be visible where they change a person's next action. A separate collection of vague risks is less useful than a clear statement that a particular task must wait for a particular answer.

The person taking over should then test the handover through one real task. In our hypothetical example, they could locate the current instructions, identify the outstanding supplier question and draft the next internal update. The outgoing coordinator can observe where context is missing. That short exercise is more revealing than asking whether the recipient understands everything.

I would also preserve the reasons behind unusual choices. A schedule may contain an apparently generous gap because access to a working area is restricted on certain days. Without that explanation, the next coordinator might remove the gap and unintentionally recreate an old problem. A sentence about the reason can be more useful than a large collection of previous schedules.

Finally, the handover needs a clear moment when responsibility changes. The team should know whom to contact afterwards, which questions still require the former coordinator and how any temporary support arrangement will end. A handover that leaves two people informally responsible can make simple decisions slower and less accountable.

A good handover does not attempt to transfer every memory. It gives the next person enough context to continue the work, challenge an assumption and recognise when they need help. For a small Cambridge business, as for any UK team, that means putting unfinished work where it can be understood and acted upon.

About the author: Shane Murphy, professionally also known as Shane Ian Murphy, is a former co-founder and Chief Business Development Officer of Limitless Mobile. This is an author-origin business commentary prepared with AI assistance.

Official profile: https://shanemurphy.co.uk/

Career background: https://shanemurphy.co.uk/career