Stopping a Removal Long Enough for a Sibling's Appeal to Matter

The situation

What Anjali and Bikash were actually afraid of had nothing to do with courtrooms. It was a birthday. Their son Rui was going to turn twenty-two in five months, the outer edge of the age at which Canadian immigration law will still treat a child as a dependent on a parent's application. Ordinarily that is not the trap it sounds like: a dependent child's age is locked in on the date the application is properly filed, so a birthday that lands during years of processing does not, by itself, disqualify anyone. The family's application had been filed years earlier, well before Rui's twenty-second birthday, and on its own terms that should have protected him completely.

Anjali worked as a technology executive and Bikash as a surgeon, and the family's application for permanent residence had been moving, slowly, for over two years. It was not Rui's case that was stuck. It was his aunt's — Anjali's sister, whose own sponsorship appeal was tied procedurally to the same family unit and whose outcome would determine whether Rui's dependent status under the family's application survived or lapsed. If the family's file was treated as abandoned or had to be refiled from the beginning for any reason, the age-lock protection would reset too: a new application would lock in Rui's age on whatever date it was filed, and by then he would already be past the cut-off. The connection between the two files was the kind of structural quirk in immigration processing that makes intuitive sense to a caseworker and almost none to a family living through it.

Then a removal order arrived, tied to a separate compliance issue on an earlier temporary status document that had lapsed during the long wait. On paper it was a narrow, technical problem. In practice it threatened to end the family's case before the aunt's appeal — and Rui's window — could resolve at all. If the family was removed from Canada before that appeal concluded, Rui's claim to dependent status would very likely become moot, regardless of how strong the underlying case was.

Bikash described the weeks after the removal order as the strangest kind of stress the family had ever managed. There was no dramatic hearing, no confrontation. Just a date on a letter, a birthday circled on a different calendar, and the sense that the family's future depended on two clocks that had nothing to do with each other lining up in time.

Why this was harder than it looked

A stay of removal is, at its core, a request that a court pause enforcement of a removal order while a more substantial legal question is resolved. Courts do not grant them freely. The applicant generally has to show there is a serious legal question to be decided, that real and irreparable harm would follow if removal proceeded before that question was answered, and that the balance of considerations favours waiting. Each of those elements had to be built carefully in Rui's family's case, and none of them was straightforward.

The serious legal question was the easier piece: the family's removal, if carried out, risked forcing the whole application to be treated as abandoned, which would erase the age-lock protection that had kept Rui's dependent status safe up to that point. That raised a genuine question about whether removal should proceed at all while a connected proceeding remained undecided. The harder piece was irreparable harm. Courts are cautious about accepting that ordinary disruption — even significant disruption — meets that bar, and the government's position was that the family could pursue their case from outside Canada if it ultimately succeeded.

That argument technically had force. In principle, a successful application does not require the applicant to be physically present in Canada throughout. But it ignored the practical reality tying Rui's status to a specific window of time. If removal happened and the family's file lapsed as a result, any application filed afterward, once the aunt's appeal eventually succeeded, would lock in Rui's age on that later filing date rather than the original one — and by then he would already have turned twenty-two, outside the window entirely. No later success on the appeal could restore a dependent status that had already lapsed by age. The harm was not generic disruption. It was a fixed, irreversible date working against the family regardless of the outcome anyone eventually won on paper.

The twist in the file was that once that argument was made clearly, the actual fix did not need to come from a judge at all. Government counsel, once shown the timing problem in plain terms, had room to agree to something short of full litigation — but reaching that room required the stay motion to be filed and taken seriously first. Nobody negotiates urgently over a problem that has not yet been made legally real.

What we did

1. Mapped the two file timelines against each other precisely. We built a single timeline showing the aunt's appeal schedule, the family's removal date, and the date Rui's age would lock in under a fresh application, because the family's fear — that the dates would collide badly — needed to be demonstrated with specific evidence, not described in general terms, for a court or government counsel to take it seriously.
2. Filed an application for leave and for judicial review of the removal-related decision. This was the procedural vehicle that made a stay motion possible; without an underlying application challenging the decision, there is nothing for a stay to attach to, so this step came first and had to meet its own filing deadline under real time pressure, while we simultaneously began preparing the stronger evidentiary record the stay motion itself would need.
3. Brought an urgent motion for a stay of removal. We asked the court to pause enforcement of the removal order until the underlying judicial review, and by extension the aunt's connected appeal, could be resolved, framing the harm not as general hardship but as the specific, irreversible loss of Rui's dependent status window once a new filing date replaced the original one.
4. Built the record around irreparable, date-specific harm. Generic disruption rarely satisfies a court on a stay motion. We supported the motion with a sworn statement laying out exactly how many months separated the removal date, the appeal's expected resolution, and the point at which Rui's age would pass the dependent-child threshold on any refiled application, making the timing collision concrete rather than speculative.
5. Opened a parallel conversation with counsel for the Minister. Once the stay motion was filed, we contacted the government's lawyers directly to flag the timing issue in plain terms and ask whether a negotiated pause made more sense than contested litigation, since the government had little to gain from fighting a stay it was likely to lose on these particular facts and a strong evidentiary record already on file.
6. Negotiated a consent arrangement pausing removal. Rather than proceed to a contested hearing, government counsel agreed to hold the removal order in abeyance until the aunt's appeal concluded, avoiding a hearing while achieving the same practical protection the family needed, on terms that required Anjali and Bikash to keep the government informed of their whereabouts and to refrain from international travel throughout.
7. Coordinated with the family's other counsel on the aunt's appeal. Because Rui's outcome depended entirely on that separate file, we stayed in regular contact with the lawyer handling the appeal to track its progress and confirm, once it resolved, that the result would flow through cleanly to protect Rui's status under the original application without requiring the family to open a second, separate dispute.

The outcome

The removal order was paused before it could take effect, and it remained paused until the aunt's appeal concluded several months later in the family's favour. Once that happened, Rui's dependent status was preserved under the family's application, and the underlying judicial review was formally discontinued as no longer necessary — the negotiated pause had done its job without needing a full hearing.

This was a partial outcome, not a clean vindication, and it is worth being clear about what was given up. The family did not win a declaration from a court that the removal order itself was wrong; that question was never actually decided. The government's agreement to pause enforcement was a practical compromise, not an admission of error, and it came with conditions — the family had to maintain contact with immigration officials throughout and could not travel outside Canada while the pause remained in effect, which complicated Bikash's work commitments for several months.

What the family kept, though, was the thing they were actually afraid of losing. Rui remained a dependent on the application. The birthday that had felt like a countdown to the end of the family's case came and went without consequence, because the legal work had already neutralized its significance. Anjali said afterward that the hardest part had never been the paperwork — it was living for months with a date on the calendar that could unmake everything, and having that date defused before it arrived was worth more to the family than a win on principle would have been.

What you can learn from this