How We Review Submissions and Handle Disputes

A behind‑the‑scenes look at how BusOva reviews new entries, edits and reports, and how disagreements over data are resolved.

What moderators look for

Moderation is about consistency and evidence, not “who is right”. Submissions are checked against a few simple principles.

• Verifiability - is there a clear source, photo or explanation for the data?
• Internal consistency - do operator, fleet number, registration and model all make sense together?
• History safety - will this change accidentally overwrite useful historic information?

How conflicting edits are handled

Occasionally two users will submit different information for the same bus. Moderators will slow down and check more carefully in these cases.

• Compare the timing of photos and notes - newer evidence usually wins if the bus has obviously changed.
• Check external sources where available, such as official fleetlists or company announcements.
• If nothing is conclusive, data may be left in a “best known” state with notes explaining the uncertainty.

Disputes and etiquette

Disagreements are normal in any enthusiast community. How they are handled matters as much as the outcome.

• Focus on evidence and sources, not on the person who made a previous edit.
• Avoid edit wars - if you strongly disagree, use report/feedback tools rather than repeatedly overwriting each other.
• Moderators may temporarily lock or freeze details while a tricky case is investigated.

How you can help moderators

Good submissions make reviews faster and more accurate.

• Use the notes field to explain non‑obvious details (re‑bodies, special contracts, re‑registrations).
• Provide clear, well‑captioned photos that show registrations, fleet numbers and key features.
• Flag possible issues early rather than letting incorrect information spread across related entries.

Related guides