We start with the authority that can actually set or administer the rule.
A useful travel-document answer depends on who is asking for the evidence. Visa-document requirements can come from a mission or visa centre. Entry conditions can come from immigration. Boarding checks can involve the airline. FlightVerified therefore records not just the rule, but the source and the context in which that source applies.
Primary authorities
Immigration departments, foreign ministries, embassies, consulates, official visa portals, and government-published entry or visa guidance are preferred whenever they directly address the requirement.
Official operating channels
Where a government delegates application handling, FlightVerified can use the official visa-application centre or authorized government-linked portal for the relevant country or consular district.
Airline context
Airline guidance can matter for check-in and boarding document checks. It is treated as carrier-specific context rather than automatically becoming a universal immigration rule.
Secondary material
Blogs, travel forums, provider marketing pages and social posts can help identify questions worth researching, but they do not become the source of a verified route rule on their own.
A source is not a route rule until its scope is defined.
FlightVerified separates dimensions that generic travel pages often collapse together. Depending on the question, a rule can be scoped by passport nationality, passport type, application or departure country, destination, travel purpose, entry scheme, residence or application status, and travel date.
- A rule for applications lodged in Singapore is not automatically a rule for applications lodged in India.
- A visa-exemption condition is not automatically a condition for travelers entering with a residence permit or pre-arranged visa.
- An airline document check is not automatically an immigration requirement for every carrier.
- A rule with an effective date should not be applied to travel outside the supported date window.
Confidence is shown instead of hidden.
The source directly supports the scoped statement.
The route rule matches the relevant destination, purpose and other required dimensions, and the cited source supports the decision FlightVerified is making.
Useful official evidence exists, but an important variable is still unresolved.
For example, the source may establish that onward evidence can matter without proving that every passport, airline or entry scheme faces the same requirement.
FlightVerified does not yet have enough reviewed evidence to assert the route.
The checker should say so clearly and direct the traveler to the relevant authority instead of borrowing an answer from a superficially similar route.
Rules carry freshness and review controls.
Travel rules can change quickly. Route records therefore include a review date and, where relevant, effective-from or effective-to dates. Internal regression checks help make sure changes to the rules engine do not silently change previously tested routes.
- Current means the internal review-by date has not passed.
- Review soon means the rule is approaching its next scheduled review.
- Overdue means the rule needs human review before it should be treated with the same confidence.
Travel guidance and provider approval are separate evidence problems.
Knowing that a traveler may need a reservation does not prove that a particular reservation service is reliable. FlightVerified keeps provider testing separate from route intelligence. A provider must be evaluated for reservation authenticity, independent verification where supported, actual validity, delivery, support, refunds and commercial transparency before the public product can present it as approved.
See provider standards →What FlightVerified will not claim.
- We do not guarantee visa approval, admission at the border, or boarding.
- We do not treat a generated PDF as proof that a real reservation exists.
- We do not convert one embassy's checklist into a worldwide rule.
- We do not label a commercial provider approved only because its affiliate terms are attractive.
- We do not hide missing evidence behind generic wording.
Corrections and source changes belong in the product loop.
If a source changes, a route result looks inconsistent, or a traveler finds an official instruction that conflicts with a FlightVerified summary, the right response is to re-check the underlying rule rather than defend the old wording. Use the support page to flag the route and include the authority or source link when possible.