This account is made up, though people who have run group trips around Chennai will spot the pattern at once. A small volunteer team, three people, plans a long weekend for forty visitors from out of town. Two weeks before the date, the lead organiser is called away to a family matter. The plan survives, but only just, and the way it survives is a lesson in how to hand over a trip plan.
The setting
The team calls itself the Marina group, after the beach where they first met. Kavya leads, Arun handles transport and Deepa looks after food and stays. Kavya has done most of the planning: a heritage walk in the old quarter, a coastal day, a temple visit in the early morning, a free evening for shopping. Bookings are scattered across her phone, a shared spreadsheet and a notebook she carries everywhere.
When she has to leave, she has four days of reduced availability and a plan that exists mostly in her head. What happens next is analytically interesting, because the team does two things in sequence: first the wrong thing, then the right one.
Attempt one: the forwarded folder
Kavya’s first move is the one most of us would make. She sends Arun and Deepa a link to the spreadsheet and a message saying, “Everything’s in there, shout if anything’s unclear.” It looks sufficient, but within a day three problems appear.
- Arun cannot tell which transport quotes were accepted and which were just enquiries.
- Deepa discovers that one guesthouse was only held verbally, with no confirmation anywhere.
- Neither knows that the early temple visit depends on a particular driver, who agreed on a phone call and nothing more.
None of these is a disaster alone, but each takes a morning to resolve, and each requires a call to Kavya at a time when she has least capacity to answer. The team has experienced what happens when information is shared but not handed over.
Attempt two: a note written for a stranger
On the fourth day Kavya sits down for forty minutes and writes a proper note. She divides it into five parts, and the team later says it was the part they used most.
- Finished: the ones that need no attention, such as the confirmed coach and the group list, with the date each was settled.
- Half done: the guesthouse that was only held verbally, the quote still under discussion and the heritage-walk guide who had agreed in principle. Each entry says what was last said and what the next step is.
- Where things are: the folder, the paper receipts in her notebook (photographed and added), and the person who holds the spare set of printed tickets.
- Watch out for: the old-quarter lanes being crowded at certain hours, the coastal stop being windy and uncomfortable for some older visitors, and the fact that the temple visit needs an early start.
- Who to ask: a named contact for each venue and a stated window, five more days, in which Kavya could answer short questions.
She then holds a twenty-minute call, asks Arun to repeat the transport plan in his own words, and corrects two details. The note and the call together do what the forwarded folder could not.
What the team did with the note
Arun and Deepa treat the half-done list as their work queue. Within two days, the guesthouse is confirmed in writing, the quote is settled and the guide’s availability is checked. Each time an item moves, they update the note, which becomes a living record instead of a one-off message.
Before finalising the days, they also consult the kind of background that helps any newcomer to the city. The overview on how newcomers should map out a first stay gives them a checklist of things they had not thought to ask the venues, and the short guide on fitting the main sights into a limited time helps them decide that the free evening should stay free rather than be packed with extras.
What the case shows
Looking at the sequence, a few observations stand out.
- Sharing is not handing over. The forwarded folder gave access but no interpretation. The second note gave status, location and caution.
- Verbal agreements are the weak points. Every item that existed only as a promise needed explicit mention, because it left no trace elsewhere.
- A time limit helps. Naming a window for questions kept Kavya’s obligation clear and gave the others confidence about when to ask.
- A read-back catches errors. Arun’s repeated summary exposed two misunderstandings in minutes.
Details that were easy to miss
Reading the final note, the team noticed how many entries concerned things nobody would have thought to put in a spreadsheet. The temple visit needed modest clothing, and Deepa had to arrange a spot for visitors to leave their shoes. The coach driver preferred to be told departure times the night before. One guesthouse locked its gate at a set hour, so late arrivals needed a phone number to call. Each of these lived in Kavya’s memory alone, and none would have survived a transfer by link.
Kavya later said that writing the watch-out section was the hardest part, precisely because she had stopped noticing these things. She solved it by walking through the whole weekend in her head, hour by hour, and writing down every moment where she had done something without thinking. Those moments, she realised, were the handover.
The cost of the first attempt
The team estimated, loosely and without numbers worth quoting, that the first four days of the weak handover cost them mainly in nerves and duplicated effort. The second attempt cost forty minutes of writing and twenty of talking. Few of us would choose the first option if the comparison were put that plainly, yet most of us default to it when pressed for time.
A parallel from the technical world
The same shape appears wherever work is passed between people, including short technical engagements. Portals such as DevOps FreeLancers present DevOps freelancers sorted by their country, a setting where engagements tend to be short, and the lesson from the Marina group carries over: an engagement is only truly finished once the next person has the status, the locations and the warnings in a form they can use.
Why the story is worth retelling
Most handover advice sounds obvious when stated and gets ignored when needed, because the person leaving is always short of time. A story gives the advice a shape you can borrow. Next time you are called away, you will remember Kavya’s four days of scrambling and her forty quiet minutes, and you will know which one to choose.
How the weekend went
The forty visitors arrived to a smooth programme. The heritage walk started on time, the guesthouse had their names, and the temple driver was waiting in the dark at the agreed spot. Nobody on the coach knew that the organiser had changed hands. That invisibility, as every good handover shows, is the best evidence it worked.
Taking the lesson home
If you organise anything in Chennai, or anywhere, try Kavya’s second attempt before you need it. Write the five parts for your current plan this week, even if nobody is taking over. If you cannot fill one of them, that is a gap in the plan itself, and finding it early is cheaper than finding it at the temple gate before sunrise.
