Imagine booking a venue for a product launch. The deciding detail, settled in the final email, was that the installation crew could get in at seven. Three days before the event a new coordinator sends a warm introduction and a form asking what time you would like access. You have paid the deposit. You are now wondering whether the most important part of the deal survived it.

Sales teams ask customers why they are buying, what might get in the way and who has the authority to decide. All that work is expensive, particularly in the buyer’s time. Its first real test comes when somebody who missed those conversations has to act on them.

GitLab publishes unusually specific instructions for that moment. Before the team introduces the person who will support an account, its handbook asks colleagues to review the customer’s goals, measures of success, obstacles, people involved and scope of the services. One detail is particularly telling. The people who sold the work should refrain from promising what the incoming customer success manager will personally do. That person gets to speak for themselves. It is a description of GitLab’s practice, available for anyone to inspect. 1

Let the person taking over do some of the talking

There is a counterpart in a field where handovers have been studied directly. Amy Starmer and colleagues studied the introduction of a structured handover programme at nine hospitals. Across 10,740 admissions, the medical error rate fell from 24.5 to 18.8 per 100 admissions. Staff received training, written tools and feedback as part of the programme. One element gave the person receiving a handover an opportunity to restate the plan and ask questions. The study compared periods before and after the full programme. It could not tell us what a single element would achieve in a venue or a sales office. It does suggest a question worth trying in either setting. What does the incoming person understand they have agreed to do? [2]3

For the venue, a practical handover might read as follows. This is an illustrative booking.

The detail What the coordinator receives
Customer commitment Installation crew may enter through the stage door at 07:00 on event day. Guest access starts at 09:00.
Reason The lighting rig needs two hours before guests arrive. A later start changes the event plan.
Evidence Final booking confirmation and customer acceptance, both linked from the booking record.
Delivery owner Event coordinator. Obtain the duty manager’s confirmation of who will open the door.
Open question Who is collecting the equipment cases after unloading? Confirm directly with the production lead by Wednesday.

The coordinator can now say, in their own words, that they will arrange access at seven and ask only about the cases. If they discover the building opens at eight, that discrepancy goes back to the seller and duty manager immediately. The customer deserves a prompt answer from someone with authority to resolve it. A guess silently copied into the event schedule is harder to undo.

An agreement can change. Keep the original booking confirmation and link any later agreement to it, with its date and the people who accepted it. Guidance published by Britain’s Government Digital Service describes a similar practice for technical decisions. It preserves the reasons for a choice, records its status and links a decision that has been replaced to its successor. The same habit lets a Saturday shift distinguish a superseded timetable from an instruction that still stands. 4

If you want to know how handovers work in your own business, open the most recent sale with an unusual request. See whether the person doing the work can tell you what was promised, where they checked it and what they will do next. At seven on the morning of the event, the customer should find a person at the stage door who already knows why they are there.