METHODOLOGY / SOURCE BOUNDARIES
Processing Radar is a comparison layer over IRCC-published processing-time JSON. This page explains what the numbers mean, how dates are labeled, and where the archive is intentionally limited.
The dashboard reads the current permanent-residence and temporary-residence feeds published by IRCC. It normalizes units such as days, weeks, and months for display, while preserving the source wording when a value cannot be parsed.
IRCC report date identifies the published estimate being shown. Last checked identifies when the feed or archived asset was observed by this project. The two dates are shown separately so an hourly check is not mistaken for a new IRCC estimate.
Historical bars show what the source published on an observed date. Permanent-residence snapshots are periodic captures; temporary-residence history combines country-table anchors with general-route captures. Neither is a complete case-level time series or a prediction of an individual file.
Approximate queue volume is not your position in a queue. Processing estimates are also not commitments, guarantees, or legal advice. Use Canada.ca for eligibility, application instructions, and the authoritative current service information.
Asset check recorded Aug 26, 2026, 7:09 p.m. UTC. The source job checks availability hourly; anomaly review is intended weekly, while methodology and content review are intended monthly. A source check can confirm availability without claiming IRCC changed its report.
REVIEW LOG / RELEASE CHECKS
This record describes the latest documented release review. It is separate from the hourly source-availability check and does not claim that future editorial reviews have already happened.
The site was rebuilt as a plain static Vite artifact with no application server, edge worker, or hosting-provider binding. Every route prerenders with its full metadata, the nine-URL canonical contract is unchanged, and the published data still matches the checksummed release manifest. This build has not been publicly deployed; the availability record below describes the earlier release.
All ten routes prerender to static HTML carrying their titles, descriptions, canonical URLs, Open Graph and X metadata, and WebSite/BreadcrumbList structured data. The design-demo route is built but served noindex and stays out of the sitemap.
The serialized sitemap still contains exactly the nine indexable URLs, in the same order, with the same source-date freshness as the recorded launch baseline.
The release exposes no server runtime, request handler, or platform binding, and passes TypeScript checking. Because the framework runtime was removed, the two previously accepted development vulnerability exceptions no longer apply; the audit reports zero production and zero development findings.
The prerendered pages load no inline script, so the policy no longer permits inline script execution. Framing, plugins, and unexpected connect origins remain denied, and the served headers are checked against the generated host configuration.
The build regenerates no release data. Every published data file matches its recorded SHA-256 in the release manifest, unlisted files fail the build, and local hourly captures are excluded from the output without touching the source archive.
Raw captures may include repeated observations of the same IRCC report date. The derived permanent-residence series collapses those repetitions into one published point per unique report date, while every capture remains in the provenance index.
This rebuild has not been deployed to the canonical origin. Public reachability, certificate issuance, and search-engine access must be re-verified against a release commit of this build before any availability claim is made for it.
The verification environment was not authenticated to Google Search Console. Route availability and index directives were recorded against a locally served build, but they are not presented as proof that any search engine indexed a URL.
INTENDED REVIEW CADENCE
Automated feed fetch, required-key validation, archive write, and notification check.
Look for unexpected source changes, missing route values, or implausible unit shifts.
Recheck explanations, source links, caveats, page usefulness, and launch disclosures.
PUBLIC CAVEAT
Not affiliated with, endorsed by, or operated by the Government of Canada or IRCC. Figures are IRCC's published estimates, not predictions, commitments, or guarantees. Approximate queue volume is not your position in a queue. This tool is not legal advice and is not a substitute for an authorized representative.