Data Dispute Process

TravelHub prioritizes data accuracy and publishes a formal process for corrections. Airline policies can change without clear notice and crowdsourced evidence can evolve quickly. When you identify a potential error, we want it submitted with source evidence so it can be reviewed and resolved transparently.

When to submit a dispute

Submit a dispute when you have evidence that a specific value is incorrect. Common cases include changed baggage dimensions, outdated fee references, incorrect route operator assumptions, or airport facility details that no longer match official sources.

Required information

• TravelHub page URL containing the value in question.
• The exact value you believe is wrong.
• Your evidence link or screenshot with date context.
• The corrected value you propose.

How to submit

Email [email protected] with subject: Data Dispute - [page URL]. We acknowledge all disputes within 48 hours and assign a review reference.

Review workflow

Review includes source verification, evidence comparison, and decision output. Outcomes are correction, confirmation, or escalation where sources conflict. For material values, temporary Disputed status may be applied while verification is in progress.

Resolution standards

Most disputes are resolved within 5 working days. If additional source clarification is required, we provide an updated timeline. Where the published value is confirmed, we return the reasoning and source basis.

Strictness disputes

Strictness ratings are model outputs from combined evidence. The most effective challenge path is submitting additional high-quality traveller reports through Submit Report, which are included in recalculation cycles.

Five-step dispute workflow

1. Submit: Use the dispute form on this page and include flight date, route, airline, and evidence such as a boarding pass screenshot or gate receipt.
2. Triage: The dispute is logged in Strapi with status Disputed and reflected on affected dimension pages within 24 hours.
3. Review: Editorial review cross-checks submitted evidence against current policy and recent traveller reports in 3-5 business days.
4. Resolution: Data is corrected or confirmed. Status updates to Resolved or Confirmed, and submitters are notified when email is provided.
5. Propagation: If values change, strictness scores recalculate on the 03:00 UTC cron run and affected pages rebuild via Strapi webhook.

Example evidence format: "Flight FR1234, STN-DUB, YYYY-MM-DD. Gate agent charged EUR 50 for 40x25x20cm bag. Receipt attached." This level of detail allows faster verification and fewer follow-up queries.

Our response-time SLA is 5 business days from acknowledgement. If a case remains unresolved after 10 days, it is automatically flagged for senior editorial review to prevent stalled disputes.