What common use really changes at the counter

A dedicated check-in counter belongs to one airline. Its computer runs that airline's application, its printers are configured for that airline's stock, and when the airline has no flight, the counter earns nothing. Multiply that by thirty carriers and a terminal is holding a great deal of idle hardware for the sake of a few busy hours each. Common use inverts the arrangement. The airport owns the position; the airline signs into it. CUPPS turns a counter into a workplace that becomes whichever airline is standing at it — its application, its boarding pass and bag tag printers, its scanners and readers — and hands the position back at the end of the shift. The obvious result is utilisation: more flights handled from the same counter estate, and a seasonal carrier that needs positions for four hours a day no longer has to be given them for twenty-four. The less obvious result is who is responsible for what. With one hardware standard for the airport instead of one per airline, a peripheral fault is the airport's to fix and the airport's to prevent. Agent training stops being airline-specific at the machine level. And a new carrier can be brought onto the terminal in the time it takes to allocate positions, not the time it takes to procure and install a counter. Then there is the reporting. When every acceptance passes through a platform the airport operates, the airport can finally answer its own questions: flights, passengers, infants, baggage counts and weights, by airline and by period — without asking each carrier for a figure and hoping the definitions match. That is the part that changes an airport's position in a negotiation. Shared counters are a cost saving. Owning the record of what happened at them is leverage.