RESEARCH & UPDATES · METHODOLOGY · 2026-07-02 · 5 MIN
How flagwise verifies facts — and why we show what we can’t verify
Most relocation content has a trust problem: confident claims, no sources, no dates, and no way to tell researched facts from recycled forum lore. Flagwise is built around the opposite bet — that showing our working, including what we don’t know, is worth more than sounding complete. This is how the machinery works.
Every fact sits on a ladder
Each datapoint on a country report carries one of four trust levels. Verified means confirmed on an official source — a regulator, a government portal, the provider’s own page — and the fact links to that source with an “as of” date. Estimate is our model’s inference from general data (CRS participation, stability indicators, AML lists), honestly labelled as such. Reference is cross-cutting country context (tax rates, cost of living) sourced separately. And community-reported is first-hand experience — visible, useful, and structurally barred from ever becoming “verified”.
Verification is per field, not per page
A country page mixing one confirmed fact with ten guesses, all under one “verified” badge, would be a lie of averages. So verification happens per field: “remote opening: verified (source, March 2026)” can sit right next to “minimum deposit: estimate”. Promotion to verified is human-gated — an automated pipeline collects and stages candidates with their sources, but a person approves every single one. When two independent sources of sufficient authority agree, confidence rises; when they conflict, the fact stays in review instead of going live.
Community reports are a separate lane — by design
First-hand reports answer the questions no regulator publishes: how long the process really took, which documents were suddenly demanded, why an application was refused. We collect them from public forums and member submissions, then apply independence weighting: copy-paste chains collapse to one voice, one platform can’t dominate, and every report keeps its date. Reports age out of the headline numbers (nine months for banking, fifteen for residence — immigration law changes more slowly than bank policy). The cap is absolute: no amount of community consensus can flip a fact to “verified”. Frequency measures agreement, not truth.
Honest gaps beat confident guesses
Where we have nothing reliable, the report says so — a dashed “no data” chip, a “low evidence” badge in the Banking Reality Index, a country listed without a rank inflation. Abstention is a feature: it tells you exactly where checking for yourself matters most, and it keeps the verified layer meaningful.
Change is data too
Every promoted fact change lands in a dated changelog, and selected changes appear as “Latest updates” on the affected report — reviewed by a human before publication, with the modification date set only when something substantive actually changed. Rules and thresholds shift constantly in this space; a fact without a date is a rumour with good posture.
What we ask of you
Read the labels. Tap the sources. Treat community reports as orientation, not guarantees — and if you’ve opened the account, filed the application or formed the company yourself, share what actually happened. Every honest report makes the picture sharper for the next person. Information, not advice — but information you can check.
Flagwise provides information, not legal, tax or financial advice. Verified facts and community reports are labelled separately throughout.