USE CASE

Reading the curb before it fills

Airport taxi demand signals are early indications that the timing and size of the passenger flow leaving a terminal is about to change. DwellTime.aero is designed to produce them for taxi fleets, transfer operators, shuttle companies and parking sites, as a curbside demand reading tied to a time window. Ground transport plans against a schedule, and disruption is that schedule failing quietly.

What changes when a flight slips

The passenger count barely moves. The timing does.

  1. Arrival compression

    Three inbounds over forty minutes is routine. Three in twelve is not.

  2. Drivers drift away

    Idle drivers take city work, then the wave lands.

  3. Dispatch windows squeeze

    Holding cars bets on an arrival time that may already be wrong.

  4. Curb, parking, prebookings

    Delayed departures hold short-stay cars. Cancelled inbounds look like no-shows.

The signals you would watch

Three scores, read from the arrival side.

Headline

Curbside demand

Pickups, transfers, shuttles and parking movement, not general terminal activity.

Read the definition

Leading indicator

Passenger flow

Movement, not volume. Two hundred arriving together is different work.

Read the definition

Context

Airport disruption risk

Cancellations and diversions land here first, and may remove the demand entirely.

Read the definition

Longer dwell moves the curb peak later. The risk window attaches a time.

From signal to shift

Illustrative examples, not instructions.

Curbside demand HIGH, next 1 to 3 hours

Arrivals may compress into a shorter window.

Hold drivers in staging.

Disruption risk HIGH, diversion or cancellation

Some passengers may not arrive at all.

Check prebooked transfers before dispatching cars.

Dwell-time pressure HIGH on departures

Short-stay parking turnover may slow.

Watch exit lane staffing later.

Curbside demand MEDIUM, low confidence

The picture is unsettled.

Keep the plan, set a check-in point.

Curbside demand HIGH, 3 to 6 hours

The last wave may land after the shift.

Review shuttle timings with the late shift.

Illustrative scenario

A worked example

Early afternoon, a transfer coordinator sees curbside demand reach HIGH for the next one to three hours.

They add no cars. Drivers are held, two shuttle departures move back, and the desk re-confirms four pickups.

Two inbounds are already late: one phone call instead of two idle drivers.

Where the signal lands

Dispatch runs on a screen, so a webhook beats a dashboard. A digest lands before the shift.

  • Webhook into dispatch
  • Slack to the shift channel
  • Morning email digest

See all delivery channels

Honest limits

Disruption does not automatically mean more demand, and nothing here is live yet. Tell us more on the pilot page.

  • No view of dispatch It cannot see bookings, drivers or the rank.
  • No mode split Some take the train, some are collected by family.
  • No individual no-shows Only that a window is worth checking.
  • Local rules differ Curbside layout and holding capacity change your options.

Disruption happens. Preparation is your move.

DwellTime is in early development. Tell us about your airport and your business, and help shape the first pilot.

Join the pilot