METHODOLOGY / SOURCE BOUNDARIES
Processing-time methodology
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.
01 / CURRENT SIGNALThe source value comes first.
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.
02 / TWO DATESReport date is not check time.
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.
03 / OBSERVED HISTORYA saved point is not a forecast.
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.
04 / QUEUE SIGNALScale is not personal position.
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.
05 / REVIEW LOGFreshness checks and editorial review are different.
Asset check recorded Nov 5, 2026, 12:07 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
What was checked for this release?
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.
IRCC data refresh and release reviewNov 4, 2026, 8:13 p.m. UTC
The November 4 refresh updates the temporary-residence report date from October 29 to November 4, 2026; the permanent-residence report date remains October 9. The six English/French feeds, derived summaries, checksummed manifest, language mirrors, and sitemap continuity were reviewed before publication.
Official feed alignmentPassed
All six official IRCC feeds were fetched. Temporary country and general feeds report November 4, 2026; permanent-residence feeds remain on October 9, 2026. Numeric values align across the English/French mirrors.
Data quality and release boundaryPassed
The release passed checks for all 28 permanent programs, four temporary country groups, report-date consistency, required units, the general-route eTA signal, valid JSON, public-data patterns, and all 30 manifest-backed file checksums. The eTA signal is five minutes in both languages and remains outside the country-specific tables.
Temporary-value anomaly reviewPassed
Compared the October 29 and November 4 summaries: 208 country values and five general-route values changed. The largest observed movement was the Eswatini visitor-outside-Canada estimate from 856 to 139 days; both official language feeds report 139. Liberia and Sierra Leone study values changed from unavailable to 18 weeks in both feeds. These are retained as current source values; no causal explanation is inferred.
Route freshness and sitemap continuityPassed
The sitemap baseline still contains the same nine canonical URLs. The refreshed source dates remain the basis for route freshness.
Published-point grainPassed
Raw captures may include repeated observations of the same IRCC report date. The derived permanent-residence series keeps one published point per unique report date, while every capture remains in the provenance index.
Public availabilityUnknown
This candidate has not been published. The current public manifest differs from the refreshed November 4 release; public data bytes and route availability require verification after publication.
Search Console statusUnknown
This environment is not authenticated to Google Search Console. HTTP availability and page directives are not evidence that a search engine indexed a URL.
INTENDED REVIEW CADENCE
Source availabilityHourlyAutomated feed fetch, required-key validation, archive write, and notification check.
Anomaly reviewIntended weeklyLook for unexpected source changes, missing route values, or implausible unit shifts.
Methodology and contentIntended monthlyRecheck explanations, source links, caveats, page usefulness, and launch disclosures.