Why this exists
The hard part of an immigration application is not usually the paperwork. It is the months afterwards, when there is nothing to do and nothing to read except a status page that says the same thing it said last week. You cannot tell whether you are near the front of the queue or nowhere near it. You cannot tell whether the silence means your file is moving or stuck. So you refresh, and the refreshing does not help.
This site exists to make that uncertainty smaller, not to pretend it is gone. Nothing here can tell you when your application will be decided, and anyone who claims otherwise is guessing. What it can do is give the wait a shape: how many applications were filed before yours and are still pending, how quickly that number is actually falling, and what range of dates that implies if the current pace holds. An uncertainty you can size is easier to carry than one you cannot, and it is a great deal easier than refreshing.
That is also why the estimates are shown as three scenarios rather than one confident date. The honest answer depends on assumptions the published data cannot settle, and the spread between them is the part worth paying attention to. A single number would be more comforting and less true.
Who makes it
I am Anirudh, a senior full-stack developer by trade. This is a personal project: one person, no company, no funding, and no connection of any kind to IRCC or to any government department. Nothing here is official, and nothing here has been reviewed or endorsed by anyone who decides applications.
I built it because the published data was sitting there in a form almost nobody could read, and because the question it answers is one a lot of people are asking at three in the morning.
I use AI coding assistants in my work, and I used them here: for parts of the code, for reviewing and reworking what was already written, and for drafting some of the prose on these pages.
Where the numbers come from
One source, and only one: the backlog figures IRCC publishes on its check processing times page, which reports how many applications are still pending ahead of each filing month. That feed publishes only the current backlog, so a history has to be kept by hand: each month's copy is archived here, and the movement between them is what makes any rate calculable at all.
Everything beyond those raw counts is arithmetic done on this site, and it is all written down. The methodology explains how the estimates are produced and, at more length, where they fall short. The monthly updates record what changed each time a new snapshot landed, including the months where the movement turned out to be bookkeeping rather than decisions.
How it is kept up to date
IRCC refreshes the feed about once a month. When it does, the site is rebuilt from the new snapshot and a short write-up goes on the monthly updates page describing what moved. Every figure in the tables, the estimates and the charts re-derives itself from the latest snapshot, so none of those can quietly go stale. The written parts, including the worked examples in the methodology, are checked by hand against the new data each time; if you ever find a sentence quoting a figure the tables no longer show, that is a mistake worth telling me about.
What it is not
- Not official. Unaffiliated with IRCC, and not a source they recognise.
- Not advice. Not legal or immigration advice, and no substitute for a qualified adviser.
- Not about your file. The site never sees your application. It knows only the filing month you pick, which is not sent anywhere: the estimate is calculated in your browser.
- Not a prediction. It is a projection from a handful of observations, and it moves when the data moves.
How it is paid for
A static site costs very little to run, which is the main reason this one can stay free and unconditional. There is a Ko-fi link for anyone who wants to leave a tip; it changes nothing about the site and nothing whatsoever about your application. There is no advertising here at all: the ad units came out in August 2026 and the ad script itself a month later, so the only third-party code left is Google Analytics. The privacy policy sets out exactly what that collects and how to opt out.
Getting in touch
Corrections are genuinely welcome, particularly if you think a number here is wrong. The contact page has the address, along with the honest list of what I can and cannot help with.