District court calendars run on the assumption that the interpreter will be in the room when the case is called. When they aren’t, the case continues, the parties come back, and the calendar congests. The pattern is uniform enough that you can predict where the breakdown will happen on a Tuesday morning calendar by reading the cause numbers.
The three breakdowns
Late scheduling. The interpreter is requested less than 72 hours before the hearing. For the top three languages (Spanish, Somali, Hmong), this usually works. For Karen, Karenni, Oromo, or Pashto, it usually doesn’t. The roster is small. The interpreters are working.
No fallback when the primary cancels. The single-interpreter request model has no automatic second tier. When the primary cancels at 7am, the scheduler emails the next name on the list and waits. By 9am, the case is continued.
Modality mismatch. A telephonic appointment was scheduled. The hearing turns out to involve testimony from a vulnerable witness, body-language is load-bearing, and the judge wants on-site. The interpreter is two counties away.
What working programs do differently
They request interpreters at the point of case scheduling, not the day before. They request a primary plus a documented backup. They default to on-site for evidentiary matters and VRI for arraignments and case management calls. They keep a running log of which interpreters honor their commitments and which don’t, and they use it.
If you’re standing up this process from scratch, start with the calendar itself. Add interpretation as a scheduling block, not as an afterthought appended to the docket.