The spine of this desk
Twelve Things, in Three Moments
Sorted not by the order of a form but by the earliest moment the value can exist. Four things a caller knows before any journey is booked, four that need a ticket first, and four that are only true on the morning.
Why sorted this way
A form asks for everything at once and implies everything is equally knowable. It is not. Some of these can be answered the day somebody first thinks about a journey. Some cannot exist until a ticket does. Some are only true on the day, and treating those as settled is how a record ends up confidently wrong.
Sorting by moment makes that visible, and it tells a caller which answers the desk expects to be corrected.
The three moments
All twelve
- Known before a trip existsThe two ends, written as addressesA journey has two ends and the desk needs both of them as places, not as districts. It is the first thing asked and the one most often given loosely.
- Known before a trip existsHow many people the desk has to seatA count, not a vehicle. The desk writes down how many people are traveling and lets the operator decide what turns up.
- Known before a trip existsWhat has to go in with themLuggage is the quiet reason a booking fails at the curb. The desk records what has to travel and hands the number on without rounding it down.
- Known before a trip existsA number a callback actually reachesA quote is read back by voice more often than it is read on a screen, and a number that goes to a full mailbox is the same as no number at all.
- Known once a ticket existsThe calendar date, once something is bookedUntil a ticket exists the date is a preference. Once it exists the date is a fact, and only then can an operator say what it has open.
- Known once a ticket existsWhether the run goes toward the field or awayThe same two addresses on the same day are two different jobs depending on which way the car is pointed, and they fail in different ways.
- Known once a ticket existsThe hour the schedule saysThe hour printed on a ticket is a fact. The hour a car should arrive is a decision made from it, and the two are not the same number.
- Known once a ticket existsThe flight number, and what it is not forThe number is written down and handed to the operator. Nothing on this desk watches it, and a delay does not move a booking by itself.
- Known on the dayThe hour somebody is actually readyOn an inbound run this is the only hour that matters, and it is the one nobody has until the morning.
- Known on the dayAn end address that movedThe address on the record was right when it was written. Then a plan changed, and the car is going to the old one.
- Known on the dayA piece nobody countedThe count was honest when it was given. Then somebody arrived with one more thing, and space is the one constraint that cannot be negotiated at the curb.
- Known on the dayA second stopOne more collection on the way turns a run between two points into a run between three, and it is priced and allocated as a different job.
The three cells every entry carries
| Cell | What it holds |
|---|---|
| What the desk writes down | In the desk's own words, which are not always the words on the form |
| Why no number can be named without it | What an operator cannot answer if it is missing |
| What happens when it changes | Before a car is committed, and after |
What this is not
It is not form help, and it is not a list of fields. Two of the twelve exist mainly to record something the desk refuses to do: it does not watch a flight, and it does not decide that a change is too small to pass on.
It is also not a catalog of what other people confirm. A desk could just as well sort its questions by which side answers them. This one sorts by when a value can first exist, which is a fact about the traveler's own information rather than about anybody's willingness to reply.