How We Verify Baggage Data

Source priority and confidence model

• Priority 1: official airline policy pages and airport authority pages.
• Priority 2: secondary pages only used when official pages are unstable or ambiguous.
• Every row includes source URL, source type, last verified date, and next review date.
• Rows with higher enforcement risk are highlighted in checker results for conservative decision-making.

Current airline coverage: 31 airlines · 30 verified · 1 manual required.

Review cadence and stale handling

Global review cycle target is 90 days. If a row passes its next review date, the checker treats it as higher uncertainty and recommends manual confirmation before travel.

1. Re-check URL and screenshot page evidence.
2. Update dimensions, exceptions, and fee triggers if changed.
3. Reset last verified and next review dates.

All airlines data completeness

We publish airline-level completeness so users can judge confidence before relying on an auto decision. Missing counts mean that a specific bag type still needs extra source verification.

Conflict resolution rules

• If official pages conflict, we choose stricter numeric limits for default checker output.
• If fare classes differ, we add policy notes and exceptions instead of forcing one answer.
• If route-level policy differs, we mark higher enforcement risk and prompt user to verify route/fare.