A live passenger list prevents duplicate bookings and stranded members by showing every coordinator the same current seat count before they assign another rider. Yesterday’s spreadsheet cannot do that once registrations, cancellations, and route changes begin arriving from different phones.
In 1999, engineers at NASA’s Jet Propulsion Laboratory in Pasadena were trying to understand why the Mars Climate Orbiter was approaching Mars on the wrong path. The spacecraft had been built by Lockheed Martin in Denver. One side of the mission used metric units, while another supplied navigation data in pound-seconds. The mismatch was discovered after contact with the spacecraft was lost.
Arthur G. Stephenson chaired NASA’s Mars Climate Orbiter Mishap Investigation Board. Its report documented a small distinction with a costly result: two systems held numbers that looked usable until they were combined.
A Sunday transport list can fail in the same quiet way. One volunteer sees 12 seats. Another has already promised four of them to families who registered through a separate message. A third is working from a screenshot taken before two cancellations. Each person may be acting carefully. The shared record is the problem.
When capacity becomes a moving target
Picture the coordinator late on Sunday afternoon, watching two buses fill for an evening service. The sheet says 12 seats remain. Then duplicate bookings surface. A member who registered earlier has no seat assignment. Another family is told to wait at a pickup point, only to learn the bus is full.
The harm goes beyond an awkward apology. Members have planned their evening around the church’s instructions. Volunteers must make decisions under pressure. Drivers receive changing lists. The people left behind carry the uncertainty home with them.
A spreadsheet is useful for planning routes. It becomes fragile when it is asked to act as the live record for registrations, capacity, cancellations, waitlists, and boarding.
One record changes the conversation
Transport coordination needs one current list per route: who is confirmed, how many seats remain, who is waiting, and what changed most recently. When a bus fills, the next registration should move to the next available route or a waitlist, with the member receiving a clear update.
That gives coordinators a different kind of answer when the phone rings: “You are confirmed on this bus,” or “This route is full, and we have placed you on the next available option.” Both answers are better than “Let me check another sheet.”
ChurchWork is built around that operational reality. Members can register for a bus, coordinators can see route capacity, and status updates can go to the people assigned to that specific route. The goal is simple: fewer conflicting promises and clearer travel plans.
For related communication risks, see how Abena restored one source of truth.
Build a process that still works at 5:45 PM
Start with the moments when the list changes fastest. Registration should update capacity immediately. Cancellations should release a seat visibly. A coordinator override should leave a clear record. A bus delay should reach registered riders, not every member in a general WhatsApp group.
Then give volunteers one place to check before they promise a seat. A printed list can still help at pickup, but it should come from the current record, not become a competing record of its own.
NASA’s Mars Climate Orbiter was lost because connected teams were working from data that did not mean the same thing. Church transport carries smaller stakes, yet the operating lesson holds: when the record is shared, current, and clear, people can act with confidence.
Before the next major event, run one practical test. Register a volunteer, cancel the registration, fill a route, and make a route change. If every coordinator can see the same result without sending a screenshot, your members are far less likely to be left waiting for a seat that no longer exists.
Comments
No comments yet.