On-Time Performance Point Check Log

This template records scheduled and actual arrival and departure times at defined timepoints along a route or trip. It helps you measure schedule adherence, identify where delays or early arrivals occur, and document exceptions for reporting. It is especially useful when you need a repeatable log instead of informal notes or memory-based reporting.

It fits fixed-route transit, shuttle service, campus transport, paratransit, school transportation, and other scheduled vehicle operations with defined timepoints. It also works for internal fleet routes where on-time performance is reviewed by trip, shift, or service pattern. If your operation does not use scheduled timepoints, a route inspection or dispatch log may be a better fit.

Use it for each monitored trip, route run, or service window depending on how often you review punctuality. Some teams complete it daily for high-visibility routes and weekly or monthly for spot checks and trend reviews. The right cadence depends on how frequently you need performance data for dispatch, operations, or customer reporting.

A dispatcher, supervisor, field auditor, or route observer usually completes the log, depending on how your operation is staffed. The person recording times should be able to observe the vehicle directly or rely on a trusted time source and understand the route schedule. A supervisor should review exceptions and sign off on any corrective action.

The log captures where variance starts, how long dwell time lasts, and whether delays are tied to a specific stop, segment, or service pattern. That makes it easier to distinguish a one-off delay from a recurring schedule problem. You can use the documented patterns to justify timetable changes, stop-time edits, or dispatch instructions.

Common mistakes include recording only one time instead of both arrival and departure, skipping the reason for the variance, and failing to note the route or vehicle identifier. Another frequent issue is using inconsistent time sources, which makes comparisons unreliable. The log works best when every monitored timepoint is captured the same way each time.

Yes. You can rename the timepoint fields, add more stops, change the acceptable variance threshold, or include route-specific exception codes. Many teams also add fields for weather, traffic, passenger load, or transfer impact when those factors affect punctuality. Keep the structure consistent so results remain comparable across trips.

Attach dispatch screenshots, GPS or AVL exports, time-stamped photos, radio logs, or incident notes when a delay or missed stop needs verification. The goal is to preserve the evidence behind the variance so reviewers can confirm what happened. If your organization uses a telematics or scheduling system, linking the record to that source improves traceability.