Retesting Without Losing a Place Already Earned

The situation

The call came in on a Thursday evening from a number with a long-distance prefix. Bogdan was on a rotation doing paramedic work at a remote camp several hours north of Midland, reachable only when the site had signal, and he wanted to know how much time he actually had left before a set of test results he had worked hard for simply stopped counting. He and his brother Marek, a respiratory therapist, had both come to Canada as refugee claimants several years earlier, and while their claims were still working through the process, both men had also built the kind of skilled, steady careers that made a parallel path toward permanent residence worth pursuing alongside the claim.

That parallel path required English test results, submitted as part of a profile placed into a pool of candidates ranked against each other for invitations to apply for permanent residence. The results are only valid for a fixed window, and once they expire, a profile built on them can lose the ranking points those scores contributed, which can be enough to drop a candidate out of contention even though nothing else about their file changed. Bogdan's scores were solid — strong enough to have kept his profile competitive — but they were going to lapse in a matter of weeks, and he was not in a position to simply walk into a test centre the next morning.

The remoteness was not incidental to the problem. Bogdan's work rotation kept him away from any city with a test centre for stretches of three and four weeks at a time, and the scheduling systems for the tests themselves booked up well in advance in the areas he could realistically reach. Marek's scores were on a similar clock, several weeks behind Bogdan's, which meant whatever solution we found for one brother needed to work for both, on different timelines, without either of them losing income by taking unplanned leave from work they could not easily step away from. A cousin, Piotr, had gone through his own economic immigration profile two years earlier and was the one who first warned Bogdan, in an offhand comment, that scores did not last forever — the reason Bogdan even thought to check the date before it was too late.

Underneath the scheduling problem sat a real fear neither brother said outright in the first call but which shaped everything: that losing their place in the pool would not just delay things, it would mean starting the profile over from a lower position, watching younger applicants with more recent scores pass them by while their own refugee claims were still unresolved.

What the law actually said

The rule at the centre of the problem is straightforward once it is stated plainly, and much of the anxiety in Bogdan's case came from not having anyone explain it to him clearly before he called us. Language test results used to support a permanent residence profile are valid for a set period from the date of the test, not from the date they were submitted or from any other milestone in the file. Once that period runs out, the results simply stop being usable evidence of language ability for that purpose, regardless of how the rest of the profile looks.

What the rule does not do, and what a lot of applicants assume it does, is force someone out of the pool the moment their scores expire. A profile with expired language results does not automatically get deleted — but it does stop being able to rely on the points those scores earned, which in a ranked, competitive pool can be functionally the same as losing your place, because a lower-ranked profile may simply never be reached for an invitation before the underlying eligibility itself expires on its own separate timeline.

The practical fix the rule allows is retesting and updating the profile before the old scores lapse, carrying the new results forward so there is no gap where the profile is relying on nothing. That sounds simple, but it depends entirely on timing that is unforgiving: a test taken too late, after the old scores have already lapsed, leaves nothing to fall back on if the new result happens to come back weaker in places for some unrelated reason, like fatigue after a work rotation.

None of this is about the refugee claim directly — the language testing rules sit inside the separate economic immigration system, and a pending claim does not exempt or extend those timelines in any special way. The two processes run on their own separate clocks, and the fact that Bogdan and Marek's status in Canada was still unresolved through their claims did nothing to slow down or pause the expiry date sitting on their test results.

There is also a scoring nuance that matters in practice more than applicants expect: results from two different tests cannot be mixed and matched component by component — whichever set gets used has to stand as a single, complete result. A new test does not erase the old one on its own; as long as the earlier result is still inside its validity window, that complete set can still be the one relied on, even after a retest has been sat. What a retest cannot do is let someone lift a weaker component out and replace it with a stronger one from a different sitting. That distinction is why timing and preparation both mattered so much here — the real danger of a rushed retest taken under fatigue after a long work rotation was not that a weaker score would automatically count, but that the original scores might lapse before a comparably strong replacement was safely locked in, leaving nothing stronger to fall back on.

What we did

1. Calculated the exact expiry date for each brother's results. We pulled both sets of test dates and worked backward from the validity period to establish firm deadlines, then built in a buffer of several weeks before each one to account for booking delays and the possibility of needing a second retest if a score came back lower than expected.
2. Mapped Bogdan's work rotation against available test dates. Because he could only reliably reach a test centre during specific windows between camp rotations, we worked with him to identify the two or three actual calendar dates that would work, rather than leaving him to search for openings reactively while off the grid with poor signal.
3. Booked the test slot remotely on Bogdan's behalf. With his authorization, we handled the registration and confirmation while he was still on rotation, so that by the time he had signal to check messages, the appointment was already secured rather than still needing to be chased down against a shrinking window.
4. Sequenced Marek's retest separately, several weeks later. Rather than treating the brothers as one file, we tracked their expiry dates independently and built a second, later timeline for Marek so that neither man's planning interfered with the other's, and so a delay in one did not create pressure on both.
5. Prepared a short written explanation for the file showing continuous eligibility. Once new scores came back, we drafted the update to the profile so it clearly showed no gap between the old results expiring and the new ones taking effect, which matters because a visible gap can itself invite closer scrutiny even if it is ultimately harmless.
6. Advised against an early retest that would have wasted a valid result. Bogdan initially wanted to retest immediately out of anxiety, which would have started a new, shorter validity clock running while his original scores still had months of life left. We talked him through why waiting until closer to the true expiry date preserved more total usable time.
7. Confirmed receipt and correct processing of both updated profiles. After each retest, we followed up to make sure the new scores had been properly linked to the right profile in the system, since a clerical mismatch at this stage is a known, avoidable way for otherwise good work to be undone.
8. Talked Bogdan through what a weaker retest would actually mean. Because components from two different tests cannot be combined and a still-valid original result is not automatically displaced by a new one, we walked him through why a lower retest score was not itself the danger — the real risk was letting the original scores lapse before a comparably strong replacement was locked in, so the decision to retest was made with the actual risk understood, not an imagined one.

The outcome

Both brothers retested within their planned windows and neither profile lapsed. Bogdan's new scores came back close to his original results, keeping his ranking within the pool essentially unchanged, and Marek's retest went smoothly several weeks later on its own separate schedule. Neither man lost his place in the pool or had to restart a profile from a lower ranking, which was the outcome that mattered most given how long they had each already been waiting.

The cost was mainly logistical rather than financial — coordinating test bookings around a remote work rotation, and the ordinary fee for retesting itself, which both brothers had budgeted for as a routine cost of keeping their options open. Nothing about their underlying refugee claims changed as a result of this work, and nothing about the language testing timeline had any bearing on how those claims would eventually be decided; the two processes remained entirely separate throughout, and both continued moving toward their own separate resolutions on their own separate schedules, unaffected by anything that happened here.

Neither brother lost income over the retesting, since we had deliberately built the plan around dates that fell inside existing gaps in Bogdan's rotation rather than requiring him to request time off. That detail sounds small, but for a household running on shift income with no built-in slack, avoiding an unplanned unpaid absence was as material to the family's actual situation as the immigration result itself.

What the file produced, beyond the retained ranking, was a clear shared understanding between the brothers of exactly how the two systems they were navigating at once actually related to each other, and did not. Bogdan has since kept a written note of both expiry dates going forward, checked before each new work rotation is scheduled, so that the next deadline is never again something learned about from a phone with one bar of signal and a shrinking window to act. He also passed the same warning on to Piotr's own son, who is now approaching his own retest window with several months of lead time instead of weeks, which is the kind of quiet, practical outcome that does not show up in any file but is arguably the more durable one.

What you can learn from this