← PROCESSING RADARUNOFFICIAL COMMUNITY MONITOR

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 SIGNAL

The 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 DATES

Report 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 HISTORY

A 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 SIGNAL

Scale 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 LOG

Freshness checks and editorial review are different.

Asset check recorded Sep 24, 2026, 3:48 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 reviewSep 24, 2026, 3:50 p.m. UTC

The September 24 IRCC refresh moved the temporary-residence report date to September 22, 2026 while the permanent-residence report date remains September 3, 2026. The six official English/French feeds, derived histories, checksummed manifest, route freshness, and release boundaries were reviewed before publication.

  • Official feed alignmentPassed

    The six official IRCC JSON feeds were fetched successfully. Temporary country and general feeds changed to the September 22, 2026 report date; permanent feeds remain on September 3, 2026. English and French mirrors were checked together.

  • Data quality and release boundaryPassed

    The refreshed release passed required program-key, language, unit, eTA-scope, JSON, public-data, history, and SHA-256 manifest checks. The build excludes local hourly captures and exposes only the 29 manifest-backed release files.

  • Route freshness and sitemap continuityPassed

    The generated route metadata and sitemap use the September 22, 2026 temporary report date without changing the nine-URL canonical sitemap contract.

  • 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 review was completed before the refreshed source state was deployed to the canonical origin. Public data bytes, redirects, security headers, and crawlability must be re-verified after publication.

  • Search Console statusUnknown

    The verification environment was not authenticated to Google Search Console. HTTP availability and index directives are not presented as proof that a search engine indexed a URL.

INTENDED REVIEW CADENCE

Source availabilityHourly

Automated feed fetch, required-key validation, archive write, and notification check.

Anomaly reviewIntended weekly

Look for unexpected source changes, missing route values, or implausible unit shifts.

Methodology and contentIntended monthly

Recheck explanations, source links, caveats, page usefulness, and launch disclosures.

PUBLIC CAVEAT

Use the official source for authority.

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.