Why does the expo pass fall apart during a busy dinner rush?

Volume outruns memory

During a rush, the number of open tables exceeds what any expediter can hold in their head. Once memory is the system, things start slipping.

The first casualties are usually modifiers and split-table timing, because those need attention the rush does not allow.

Verbal callouts collide

When everything is shouted, the loudest voice wins and quieter tickets wait. Cross-talk between stations turns into missed fires.

A shared screen replaces most callouts with a glance, which lowers the noise and the error rate at the same time.

No single source of truth

If the printer, the rail, and each cook's memory disagree, there is no way to settle what is actually outstanding. That is where plates get remade or forgotten.

One live pass that every station reads from ends the disagreement, because everyone is looking at the same list.

Protect the pass role

The expediter should run the pass, not also plate, garnish, and answer the phone. Overloading that role is what actually collapses it.

Give the pass a clear view and a light enough load to use it, and the rush becomes busy instead of chaotic.