One Request, Three Coordinators, No Single Answer

Introduction

A single scramble is easy to dismiss as a bad morning. What is harder to dismiss is the same request, for the same set, moving through three different people who each hold part of the answer and none of whom holds all of it. Here is what that looks like when the source of truth is a spreadsheet, a text thread, and three people's memories instead of a system.

The Afternoon Before

A rep gets an add-on case for the next morning and needs a specific set. She checks with the two reps nearest her; neither has it available. So she contacts operations in the afternoon, and the coordination begins. A coordinator opens the tracking spreadsheet and sees the set listed at a territory two hours away, marked available. He tells the rep it is confirmed and that he will arrange the transfer and overnight shipping.

What nobody checks is whether the spreadsheet is current. The last edit to that row was nine days earlier. In the days since, the set was pulled for a case at that territory, used, and not yet logged back. The record says available because nothing has told it otherwise.

The Morning Of

The overnight shipment does not arrive, because it was never actually sent; the rep who was supposed to hand off the set never had it to hand off. The first coordinator is out that morning. A second coordinator picks up the thread with only what is visible in the spreadsheet and a few lines of a text exchange, neither of which explains that the set was already gone. She starts calling reps in the region to find any equivalent set that can reach the case in time.

A third person, an ops manager, gets pulled in because the case is now at risk and the surgeon is scheduled. He knows something the spreadsheet does not: a set was transferred last week to a rep one territory over, as a favor, by phone. That transfer updated nobody's record. He remembers it only because he happened to be on the call. That set turns out to be the nearest available option, and it is not on any system anyone has looked at.

What Each Person Knew, and Did Not

The first coordinator knew what the spreadsheet said, which was already wrong. The second coordinator knew how to run a search under pressure, but started from the same stale record and a partial text history. The ops manager knew about an undocumented transfer, but only from memory, and only because he was personally involved. Three people, three fragments, and no single place where the three fragments came together. The set was eventually located and couriered same-day at several times the cost of a routine shipment. The case was covered. It took most of a morning and three people to cover it.

The Second Set Nobody Needed

There is a detail that only becomes visible afterward. While the second coordinator was calling around, she reached a rep who agreed to send a set from his territory, and that set was dispatched before the ops manager located the nearer one. For a few hours, two sets were converging on the same case. The rep's set arrived after the case was already covered. It now had to be logged, reconciled, and returned, and for the reporting period that followed, his territory showed as carrying less than it should while the set sat in transit back. A legitimate replenishment request he submitted the next week was questioned, because on paper his territory looked short, which it was, because of a set that left to cover a scramble that a current record would have prevented.

What This Pattern Actually Shows

A single instance of any of this looks like an ordinary bad morning. One request that required three people, a stale spreadsheet, an undocumented transfer surfacing only from memory, a second set dispatched unnecessarily, and a downstream replenishment flag, is not a bad morning. It is a signal that the coordination has no single source of truth, and that the truth is distributed across people and channels that do not reconcile with each other.

It also shows why adding coordinators does not fix this. The problem was never a shortage of effort. Three capable people worked the request hard. The problem is that none of them could see the whole picture, because the whole picture did not exist in any one place. More people searching the same fragmented record find the set faster, but they do not stop the next request from fragmenting exactly the same way.

This scenario is illustrative, built from patterns common across field inventory operations. It does not describe a specific company or customer.