- The Federal Court ruled that completeness returns are justiciable and subject to judicial review.
- Justice Battista found IRCC’s assessment unreasonable, ordering reprocessing by a new officer for the applicant.
- The ruling is vital for PGP applicants where intake caps make resubmission virtually impossible without an invitation.
What you’ll need before you act
- Your full returned package (every page IRCC sent back).
- Proof of what you submitted (copies, courier tracking, portal receipts, fee payment record).
- The exact PGP document checklist and form versions that applied on your submission date.
- A timeline of events (invitation date, submission date, return date, any reconsideration request).
Section 1: Overview of the ruling
On January 16, 2026, the Federal Court held that IRCC’s practice of returning applications for incompleteness is justiciable and subject to judicial review. That matters because a return of the application as incomplete often ends the process in real life.
Processing stops. Your file never enters the processing stream. Justice Battista’s decision confirms that a “completeness assessment” is not immune from court oversight under s. 18.1 of the Federal Courts Act.
Applicants now have a clearer path to challenge an unreasonable incompleteness return, especially where it operates like a refusal without the safeguards that usually come with a refusal. Readers looking for how review options can differ by outcome may also compare general concepts discussed in denied application processes.
Section 2: Case background
Devgon applied under the PGP to sponsor her parents. IRCC returned the application as incomplete, so the family could not move forward on the merits.
For many PGP families, a simple “fix and refile” is not realistic. A return can erase the chance created by an invitation.
PGP is governed by capped intake and invitations issued through Ministerial Instructions under the Immigration and Refugee Protection Act. That structure means an incompleteness return can function as a de facto final decision, even if IRCC labels it as administrative.
Ongoing frustration with PGP mechanics has been widely reported, including PGP in 2025 and the impact of PGP application pauses.
Section 3: Ruling details and reasoning
Justice Battista set aside IRCC’s incompleteness return after finding the officer’s completeness assessment unreasonable. Put plainly, the court found errors in how IRCC applied the completeness requirements to Devgon’s file.
That legal framing matters. “Reasonableness” review focuses on whether the decision makes sense in light of the record and the rules. IRCC argued that an incompleteness return is “non-justiciable,” meaning it is not a reviewable “matter” under s. 18.1 of the Federal Courts Act. The Federal Court rejected that position.
The remedy was direct: the application was returned to IRCC for processing by a different officer. No approval was ordered. The court also did not decide the separate “refusal to reconsider” issue because the initial incompleteness return was already set aside.
Impact level: High. The short takeaway: incompleteness returns can be reviewed, and an unreasonable return can be sent back for reprocessing by a new officer.
The interactive tool below will summarize the ruling timeline and key reasoning points for quick review. Use that tool to explore the sequence of events, findings, and remedial steps in more detail.
Section 4: Legal implications and precedent
A completeness assessment might look like a preliminary screening step. In PGP, it can affect substantive interests because it can erase an invitation-based opportunity that you cannot simply recreate.
That is the core shift in the case. The Federal Court treated the incompleteness return as something that can carry real legal consequences.
Not every incompleteness return can be reviewed; outcomes depend on the record and factual errors identified. To succeed, applicants typically must show a reviewable problem, such as a material factual mistake, an unreasonable interpretation of the checklist or form requirements, or a procedural fairness concern tied to how IRCC assessed the package. Thinking in “threshold” terms may help, similar to how decision points are discussed in prima facie review, but the legal tests are not identical.
Section 5: Context and comparisons
This ruling is Canadian. It operates within the Canadian Federal Court framework, the Immigration and Refugee Protection Act, and s. 18.1 of the Federal Courts Act. That scope matters if you are tempted to compare it to U.S. developments.
USCIS is a different system with different statutes, remedies, and court structures. Some U.S. cases about fees or stopping certain terminations can feel loosely analogous, but they do not provide a direct blueprint for PGP or for IRCC completeness assessments.
Use comparisons only for perspective. Do not assume a U.S. approach would transfer to Canada, or vice versa. Even cross-border reporting on improper case-ending steps, like improperly terminating, should be read as context rather than precedent.
Section 6: Practical takeaways for applicants and practitioners
Start with the paperwork. Then decide whether escalation makes sense.
- Identify the exact deficiency IRCC claimed. Read the return letter closely and match it to the checklist line-by-line.
- Verify versions, signatures, and dates. Many completeness returns turn on a missing signature, outdated form version, or an unchecked box that IRCC treats as mandatory.
- Confirm fees and proof of payment. Make sure the payment matches the required amount and that the receipt is the correct one for your submission method.
- Rebuild your “record” immediately. Save screenshots, portal confirmations, courier tracking, and a full copy of what you sent. That record often drives what a court can assess later.
- Assess the harm from the incompleteness return. In PGP, harm may be acute because Ministerial Instructions and caps can make resubmission impossible without a new invitation.
- Consider a reconsideration request carefully. A targeted request may help where the return is clearly based on a factual misunderstanding. Keep it specific and evidence-based.
- Discuss judicial review early if the stakes are high. Court timelines can be tight, and strategy depends on what the written record shows. If successful, the remedy may look like Devgon’s: the file goes back to IRCC for reprocessing by a different officer. It does not guarantee acceptance or approval.
Action: What applicants should do now if their file was returned as incomplete
- Gather your full submission record and the return letter.
- Map IRCC’s stated deficiency to the checklist and the form instruction guide.
- Write down why the alleged defect is wrong or immaterial, using documents and screenshots.
- If PGP caps or Ministerial Instructions block refiling, speak with qualified counsel promptly about reconsideration or judicial review options.
This article discusses a legal decision and is intended for informational purposes. It does not constitute legal advice.
Individual results may vary based on facts. Consult a qualified lawyer for advice on your case.
