The Rejection Notice Named a Person Who No Longer Existed on Paper

The situation

The second rejection letter was the one that made Bogdan call our office. It stated, in the same flat language as the first, that the name on his renewal application did not match the name on file, and that the application could not proceed until the discrepancy was resolved. Nothing in the letter explained what document would actually resolve it.

Bogdan had lived in Kincardine for several years, working as a sales director for a company that supplied industrial equipment across the region, a role that required frequent travel and, by extension, a permanent resident card that reliably matched his passport at every border crossing. Kasia, a commercial pilot on a route that regularly brought her through Ontario, had first come to Canada on a visitor status years earlier during a layover stopover that turned into a longer stay while she and Bogdan got to know each other. Two years ago they travelled together to Poland and married, with her brother Piotr standing as a witness at the civil ceremony, and the two had jointly adopted a hyphenated surname combining both of their family names, a legal and common practice under Polish civil law. Bogdan updated his Polish-issued passport to reflect the new name without much difficulty. Updating the Canadian side of his identity, starting with his permanent resident card, turned out to be a different matter entirely.

His original PR card, still valid for another year at the time of the marriage, carried his old name. When it came up for renewal, he submitted the renewal application using his new passport and new name, along with a copy of the Polish marriage certificate as proof of the change. He had first taken the file to another lawyer, who advised him simply to submit the renewal with the new documents and assumed the marriage certificate alone would carry the explanation. That application was rejected. A second attempt, prepared the same way with minor additions, was rejected again.

By the time Bogdan came to us, the first lawyer's retainer had ended, the file had two rejection letters on it, and his existing PR card, still bearing his old name, was approaching its expiry date, which meant the clock on his ability to travel and re-enter Canada without complication was running out.

What the law actually said

The rejection letters both cited a mismatch between the applicant's name and the name on record without describing, in plain terms, what closes that kind of gap. That is common; refusal and rejection notices tend to state the problem in the language of the rule rather than translate it into the specific document a person needs to produce. The first lawyer had read the letters as confirming that the marriage certificate was insufficient proof and had responded by adding supporting materials around it — a notarized translation, an affidavit from Bogdan describing the marriage — without actually establishing what the government needs to accept a name change on a renewal submitted alongside it.

The actual requirement was narrower and more procedural than either rejection letter suggested. There is no separate registration step that has to be finished before a renewal can rely on a new name. The legal document behind the change, in Bogdan's case the marriage certificate, is filed with the renewal application itself, together with government-issued identification in the new name, and the card is issued in that name on that basis. What both earlier submissions were missing was not a prior step but a properly usable version of that document: a certified English translation of the Polish marriage certificate, formally attached to the renewal as the specific instrument establishing the name change, rather than included as a plain photocopy of a foreign-language original alongside a form that otherwise still read, in places, as though it belonged to his old name. Submitting a renewal that assumed an uncertified copy would speak for itself, however genuine the marriage, gave the reviewing officer nothing it could actually rely on to certify the new name, which is functionally why it kept coming back.

This distinction, between proving a marriage occurred and presenting that proof in a form an officer could act on, was the entire substance of what had gone wrong. Kasia's own paperwork was not in question at any point; the issue was purely about how Bogdan's own documentation was assembled and presented, something neither rejection letter said outright and something the first lawyer's approach, reasonable on its face, had not identified.

It is worth being precise about what the first lawyer did wrong, because it was not carelessness. Faced with a rejection that cited a name mismatch, the natural instinct is to add more proof that the name change is real: more documents, more corroboration, more explanation. That instinct is usually right for a substantive dispute, where an officer doubts a fact and more evidence resolves the doubt. It is the wrong instinct for a presentation problem, where the officer is not doubting the marriage at all but simply has no certified document to attach the new name to. No volume of additional proof fixes a document that is not yet in the form the process requires; only replacing it with one that is does.

What we did

1. Requested the full file history from the previous lawyer. Before assuming anything about what had gone wrong, we obtained copies of both prior submissions and the complete rejection correspondence, to see exactly what had been submitted and exactly what language the government had used in response. This mattered because Bogdan's own recollection of two rejections received months apart was understandably hazy on the details, and building a new strategy on a guess about what the old one contained would have risked repeating the same mistake a third time.
2. Identified the actual documentation gap. Comparing the submitted documents against the government's actual requirements for supporting a name change on a renewal, we confirmed that the marriage certificate had gone in both times as an uncertified photocopy, without the certified English translation an officer needs to rely on a foreign-language document. This single gap explained precisely why two well-documented, carefully assembled submissions had both been returned, and it reframed the whole file from what looked like a missing prior step back into what it actually was: a document not yet in a form the government could act on.
3. Obtained a certified translation of the marriage certificate. Rather than resubmitting the renewal a third time with the same uncertified copy, we arranged a certified English translation of the Polish marriage certificate and assembled it alongside Bogdan's reissued Polish passport, so that everything supporting the new name would go to the government in a single, complete, consistent package.
4. Resubmitted the PR card renewal with the complete package. We filed the renewal application together with the certified translation, the reissued passport, and consistent documentation across every identity document involved, in one submission rather than treating any piece as preliminary. This gave the officer reviewing it a document it could actually certify the new name against, rather than an uncertified translation with no way to verify it, which is what had sunk both earlier attempts.
5. Advised Bogdan on his existing card's expiry window. Because his old card was approaching expiry throughout this process, we tracked the timeline closely and advised him on what travel he could safely undertake on the existing card while the renewal was pending. A sales director whose job depends on crossing the border cannot afford a surprise at a checkpoint, so we made sure he always knew exactly what document covered him on any given day.

The outcome

The renewal application, filed with a properly certified translation and consistent supporting documents, was approved without further correspondence or delay beyond ordinary processing time. Bogdan received a new PR card in his current legal name, matching his Polish passport and every other identity document he now carries, and the mismatch that had generated two rejection letters did not resurface.

The clear win here was not a matter of arguing a difficult legal position. It came from putting the marriage certificate in the specific form the government could actually rely on, even though nothing in the original rejection letters explained that requirement in terms a layperson, or a lawyer unfamiliar with the specific process, would necessarily catch on the first attempt. Once the file matched what the rule actually required, rather than a reasonable assumption about what it required, the approval followed cleanly.

Bogdan's old card did expire a few weeks before the new one arrived, which meant a short stretch where he had to plan travel more carefully than usual, relying on his valid passport and confirmation of his pending application rather than a current card. That stretch was manageable and did not affect his ability to work or to re-enter Canada when needed. The larger cost had already been paid before we were retained: two rejected applications, a first lawyer's fees, and months of delay spent solving the wrong version of the problem.

Kasia's own path through the system, meanwhile, stayed straightforward throughout, since her permanent status had already been settled before this file began and none of it turned on Bogdan's card. Piotr's role stayed exactly what it had been from the start, a family witness to a marriage that was never actually in doubt. The only real fight in this file was administrative, and once it was fought correctly, it was over.

What you can learn from this