How Do You Display an Overnight Schedule Clearly?
From the earlier reference collection. Read the current software blog.
Group overnight trips by service day and label after-midnight arrivals so the date and time convention remain clear.
Choose a stable grouping
An overnight schedule can become confusing when a departure appears on one date and an arrival on the next. Group trips by their service day, the date whose calendar rules determine whether those trips operate. Keep that grouping consistent even when individual stop times cross midnight.
If trips are grouped only by the calendar date of each stop, one journey may seem to disappear from the day it began or appear disconnected from its service. A stable service-day grouping lets a rider follow the same trip from origin to destination.
Explain the time convention
If the underlying timetable uses extended values, show a brief note explaining that 24:00 and above indicate the next calendar day. For example, “25:10 (Saturday 1:10 a.m.)” makes both the schedule-day position and the ordinary clock reading visible.
A schedule may instead show ordinary clock values with explicit date labels. Either format can work if the screen makes the relationship clear. GTFS allows service-day times beyond 24 hours, reflecting that a service day can extend into the following calendar date. [GTFS schedule reference](https://gtfs.org/documentation/schedule/reference/)
Keep date context beside the time
Do not make readers infer the date from color alone or from a legend far away. A row can identify “Friday service” and mark an arrival as “Saturday, 1:10 a.m.” This is especially helpful in a trip planner, where an origin search date and destination arrival date may differ.
For example, a trip leaving a terminal at 11:40 p.m. Friday and reaching its endpoint at 1:10 a.m. Saturday should read as one trip. Its row can show both local times with date markers while retaining Friday as the service date.
Support scanning and assistive reading
Use consistent labels for “service day,” “next day,” and local times. Ensure that a screen reader can encounter the date relationship in the text order, rather than relying on visual placement or a color cue. Sorting should use the full service-day timeline, not just the displayed hour and minute.
Clear overnight presentation reduces errors for both riders and software operators. The reader can see which date activates the trip, when each stop occurs, and how the timetable’s time notation maps to a familiar clock.