Meet a made-up coordination team that arranged logistics for people travelling abroad for surgery, and share the afternoon they realised how much of their work was simply waiting. Nothing in it is clinical. It follows the administrative threads that surround any medical trip: records, invitation letters, travel bookings, accommodation confirmations, payment receipts. The team’s discovery was that a modest waiting-for list could stop those threads from tangling. The tale is invented to illustrate the habit, and it offers general information only.
The Monday that went wrong
The team had a quiet office, three desks and a shared inbox. On a rainy Monday, the lead coordinator opened the inbox to find a message from a traveller’s relative asking whether the airport transfer had been confirmed. Nobody could say. The booking had been requested from a partner agency nine days earlier. The reply had come, but it was buried under a hundred newer emails, and the agency’s note actually asked a question that nobody had answered.
A morning of phone calls followed. The transfer was saved with hours to spare, yet the team felt shaken. Nothing had been refused. Everything had simply been left unattended.
Looking for the pattern
That afternoon, the group laid every open request out on a long table, using sticky notes. There were more than anyone expected. Each note was a promise another party had made: a hotel confirming dates, a records office releasing copies, an agency answering a question, a payment desk issuing a receipt. Most had no recorded date. Several had no clear owner on the other side.
One of the junior colleagues said what everyone was thinking: the problem was not effort, it was memory. The team was working hard but relying on an inbox as though it were a filing system.
Building the list
They agreed on a simple page, kept in a shared spreadsheet. Every row carried the same fields: what was requested, which party owed it, the date and channel of the request, the expected reply date and the day to follow up. A rule was added that whoever sent a request filled in the row before sending the next message.
The group also decided on two conventions. The first was a short code instead of any traveller’s name, so the sheet held no private details. The second was a colour for rows past their chase date, so overdue items stood out without anyone reading every line.
The first week of using it
The change was less dramatic than the team expected, and more useful. Each morning one person read the page from the top and sent short nudges to every party whose date had arrived. In the first week, three items that would once have gone unnoticed were chased. One turned out to need a missing attachment from the team itself, which was quickly supplied.
Messages changed in tone too. Instead of “any update?”, they began to read: “Following up on the request sent earlier this week; the traveller’s arrival plan depends on this confirmation, and we are glad to provide any detail that would help.” Replies arrived faster.
What happened when a nudge failed
A few weeks later, a hotel failed to answer two nudges. In the old days, the team would have drifted on and hoped. Now they had dates. The coordinator contacted the hotel’s manager, quoted the dates of the first request and the two follow-ups, and received an apology and a confirmation the same day. The team noticed that a calm, factual message with a trail behind it resolved things more quickly than urgency alone ever had.
How the page grew over a season
As months passed, the sheet gained small improvements. A column for the reference number each partner gave was added, because quoting it saved explaining what each message was about. A filter showed only rows due that day, which cut the morning review to a few minutes. When the team took on more travellers, they added a rule that no row could be closed until the reply was saved beside the original request, so the evidence of each answer stayed in one place.
They also started a short Friday habit: scan for rows that had sat open longest and decide whether each needed a firmer message, a call or a polite closure. The practice kept old items from fading into the background, and it gave new colleagues a clear picture of what was in flight the moment they joined.
What the team learned
- Silence is the usual cause: most delays came from unattended requests, not refusals.
- Dates make follow-up easy: a chase date removes the need to remember or to decide when to ask.
- Owners need names or roles: “the agency” cannot be chased; “the agency’s bookings desk” can.
- One list beats many inboxes: a single page prevents requests hiding in different threads.
A wider reflection
Not long afterwards, one of the team started helping a relative who was thinking about buying a flat. The questions to agents, the paperwork and the replies looked uncannily familiar, and they began a list for that too. For general research, they used Propraahi, a website about property research for people buying homes in India, as a place to gather reading material, and kept the follow-ups on their own page.
Borrowing the idea for your own trip
A team is optional. Anyone arranging a trip, however modest, can keep a page with five fields and a daily check. For readers planning care abroad, this blog also has a checklist on the questions worth raising before travelling for surgery and a piece about the way careful hospital comparison safeguards a trip for surgery. These are general reading, and decisions about care remain a matter for you and your own doctors.
As for the fictional team, they still keep the sticky notes from that first afternoon, pinned to the wall. The page now does the remembering, and the office is quieter. This story is invented and offers general ideas about organising only, not medical advice.