Every regulatory claim carries a source
An official URL, the jurisdiction it belongs to, and the date we last read it. No source, no publication — even when we are confident.
Our standards
Everything else about this product is open to argument. These eight are not, because the cost of breaking them is paid by someone planning their life around the answer.
An official URL, the jurisdiction it belongs to, and the date we last read it. No source, no publication — even when we are confident.
Official requirement, editorial estimate and community experience are labelled separately. One individual's experience never rewrites a rule.
The first is a regulatory claim and needs a source. The second is admitting ignorance. Passing one off as the other could tell someone they may practise without a licence.
We never predict approval, timing or points. For points-based routes we explain the factors and link the official calculator, because calculating would be promising.
A salary floor without its year goes stale silently. Without its exception, it makes people rule themselves out over a number that never applied to them.
Text taken from permit A is never reused in a block shared with permits B and C. Each permit usually has its own legal test, so a true sentence in the wrong container becomes false.
If the authority's page does not say it, we do not publish it — even when the deduction turns out to be correct.
A new date over an old quotation asserts a review that never happened. When we recheck, both move.
No crawler, on purpose
Recognition rules and migration regimes move in cycles of years, not hours. An automated watcher across hundreds of government pages would produce noise, break constantly and still miss the change that mattered. So the refresh is deliberate and manual, and the mechanism that protects you is different: the date sits next to the link, and you can check it yourself in one click.
On that day, that official page said this. That is the entire claim, stated exactly.
It does not mean the rule is unchanged today, and we will never dress it up as if it did.
Found something wrong?
Send us the page and the official source. Regulatory fixes go to the front of the queue.