Follow the last bus across midnight
Imagine a transit agency releasing a winter timetable. A Friday bus leaves downtown at 11:55 p.m. and reaches the hospital at 12:20 a.m. Saturday. A rider finishing a late shift needs to know whether it runs on the night before a holiday. Before recruiting a “transit data specialist,” ask the scheduling manager to trace that trip from the approved timetable to the result a rider would see. The point where the team loses the answer tells you whom to hire.
The General Transit Feed Specification (GTFS) describes how agencies can publish scheduled service. Its distinction between a service day and a calendar date matters here. An arrival twenty minutes after midnight on the same service day can be recorded as 24:20:00. Calendar exceptions can add or remove service on a particular date. Those conventions explain how to encode an approved decision. The agency still has to decide which bus runs. GTFS Schedule reference.
Find the missing decision owner
Give the scheduler a small worksheet with the route, direction, boarding stop, service date and expected departure. Include an ordinary Friday, the holiday exception and the first day of the replacement schedule. Ask for the document approving each answer. If operations and planning disagree about the holiday trip, assign a service planner who can settle the discrepancy with the authorized schedule owner. Hiring a developer at this point leaves someone writing software to choose between two promises.
If the approved answers are clear, ask an analyst to trace one into the feed. Which trip references the service? Which stop sequence places the hospital after downtown? Which exception applies to Friday? If the answers exist but the export drops an exception on each rebuild, the assignment belongs with an integration engineer who can correct the transformation and test the next export. If the feed represents the trip correctly but a rider-facing application displays it on the wrong night, assign a tester to reproduce that discrepancy with the application owner before replacing the exporter.
Screen for the work the agency can hand over
Give every applicant for the same role the same fictional timetable and two small feed extracts. Include one holiday discrepancy and one harmless change, such as a revised route description. Ask the candidate which change would strand a rider, which dated journey demonstrates it, and whom they would consult before authorizing a correction. A candidate who flags an ambiguous instruction and asks the planner to resolve it has given you evidence of judgment. A list of validator warnings alone cannot answer whether a hospital trip was promised.
Tell the staffing partner who can supply the source schedule, when the next timetable freezes, whether an onsite observation is needed, and who covers a release outside ordinary hours. Confirm those commitments in writing before the start. A temporary engineer may be right for a repeatable export defect. An agency planner needs ongoing responsibility for approving calendar changes however the software is maintained.
Put the second timetable in the handoff
Have the agency’s designated backup generate the next test feed with a new exception while the consultant observes. The backup should trace the same journey, identify the effective feed and explain what riders will see after midnight. Keep the dated worksheet, feed version and unresolved application issues with the schedule owner. If a journey fails, that owner decides whether to hold or correct the release and asks rider information staff how to communicate the affected service. This applies the Vitaver Playbook’s Mission First practice of giving a named owner a result they can verify independently.