1. Turn the complaint into a question
“The line is bad” is a legitimate but broad experience. To audit, choose something observable: no vehicles showed up between 10pm and 11pm? Was the interval longer than 40 minutes? Were the buses grouped together? Did the line stop passing in a certain section?
The more precise the question, the easier it is to gather evidence and avoid a single record representing an entire day.
2. Record the context
Note the date, time period, direction, stop or route segment, route number, and any variant prefix. Take a screenshot that also shows the last update time. If a fleet number is available, record it.
- Confirm that the general map data is updating.
- Observe more than one update cycle.
- Do not add vehicles with different directions or variants without indicating this.
- Mark old positions as outdated data, not current location.
3. Compare with history and plan
Open the line page and check if the behavior appears on other equivalent days. Then, consult the current operational plan. A recurring difference is more informative than an atypical night; a difference between incompatible measures is not.
When publishing or sending the report, describe the method: “between 9 p.m. and 10 p.m., on four Tuesdays, these vehicles were observed...” is better than “this route never runs.”
4. Forward to the correct channel
BuzuRadar does not inspect or operate the buses. For line irregularities, Central 1746 requests information such as line, vehicle, location, days and times. A structured report increases the chance that the agency will be able to reproduce the problem.