When a Birth Certificate Spelling Stalled a Citizenship File

The situation

Eleni had been a permanent resident of Canada for just over five years, working as an office manager for a mid-sized logistics company near Brampton. She was born in Cyprus, and like many people whose names originate in a non-Latin alphabet, her name had been transliterated into English more than once over the years — first by a translator when she applied for her original study permit, again when she later applied for permanent residence, and once more when her Cypriot passport was renewed at a consulate. Each transliteration was a reasonable rendering of the same Greek-alphabet name. None of them were identical.

Her wife, Sophia, a real estate agent, had become a Canadian citizen a few years earlier through a more straightforward process, and the couple assumed Eleni's application would follow the same path. Eleni gathered her documents — birth certificate, passport, permanent resident card, marriage certificate, old study and work permits — and submitted her citizenship application on her own, expecting a routine wait of a year or so before an interview and a ceremony.

What she did not expect was a request for additional information roughly eight months in, asking her to explain why her name appeared with three different spellings across the documents supporting her file.

What the review found

By the time Eleni came to Treadstone Law, she had already received the request and had about six weeks to respond. Immigration, Refugees and Citizenship Canada (IRCC) compares the biographic information across every document in a file — birth certificate, passport, permanent resident record, and any prior immigration applications — to confirm that the person applying for citizenship is the same person who was granted permanent residence in the first place. Small differences are common and usually harmless: a middle name included on one document and dropped on another, or an accent mark rendered differently. But when three separate spellings of the same first name appear across four different documents, with no explanation on file connecting them, the reviewing officer cannot simply assume they refer to the same person. The file gets flagged for what IRCC treats as an identity verification concern, and the application effectively pauses until the applicant resolves it.

The deeper problem was that nothing had ever formally connected the spellings. When Eleni's original study permit was issued, the transliteration used was a phonetic approximation typed by a caseworker overseas. Her later permanent residence application used a slightly different spelling, taken from a fresh translation of her birth certificate. Her most recent Cypriot passport, renewed after her PR was already approved, used yet a third spelling reflecting a change in her country's official transliteration standard. Each document was accurate in isolation. Read together, without anything tying them to one person, they looked like an inconsistency serious enough to question.

There was a second, smaller issue layered on top: because the request for information had already been sitting for several weeks by the time Eleni sought help, less than a month remained on the clock, and a missed deadline on a request like this can result in the application being closed entirely rather than merely delayed.

It is worth being clear about what this kind of flag is not. It is not an accusation of fraud, and it does not mean an applicant has done anything wrong. Officers see genuine transliteration variation constantly, particularly among applicants whose names originate in Arabic, Cyrillic, Greek, or South Asian scripts, where more than one defensible English spelling can exist for the same name. The problem is administrative, not personal: the file, as submitted, did not connect the dots for the officer reviewing it, and citizenship officers are not permitted to simply assume the connection on their own. Someone has to make the link explicit, in writing, with evidence behind it.

What we did

1. Mapped every spelling to its source document. We built a simple table showing each version of Eleni's name, which document it appeared on, who had produced the transliteration, and the date. This made the pattern visible at a glance: a caseworker's phonetic rendering, then a certified translator's version, then a passport office's version, all describing the same underlying Greek name.
2. Prepared a statutory declaration of name variation. This is a sworn statement, signed before a person authorized to administer oaths, in which the applicant formally declares that the differently spelled names all belong to them, and explains the reason for each variation. We drafted it in plain terms tied directly to the document table, rather than a vague general statement, so the reviewing officer could match each spelling to its cause without guesswork.
3. Obtained a supporting letter from a certified translator, Meera, confirming that all three spellings were reasonable transliterations of the same Greek-alphabet name, and that transliteration standards for that alphabet had genuinely changed over the period covered by Eleni's documents. This gave the sworn statement independent, professional backing rather than resting on Eleni's word alone.
4. Filed the response well before the deadline rather than close to it, with a cover letter that flagged the identity verification concern by name and pointed the reviewing officer directly to the declaration and the translator's letter, so the file did not need to be read twice to find the answer.
5. Advised Eleni to standardize her name going forward on every document she could still control — her employer's records, her provincial health card, her driver's licence — to the spelling used on her current passport, so that no new inconsistency would appear once the citizenship file closed.

The outcome

The response was accepted without further questions, and Eleni's file moved back into processing. But the pause itself had already cost her something real. Between the original request for information and the eventual resolution, close to a year passed. Eleni's citizenship test and interview, once scheduled, went smoothly, and she was approved and took the oath roughly fourteen months after her original submission — well beyond the timeline she and Sophia had planned around.

The concrete loss was a trip. Eleni's mother in Cyprus had been planning to travel to Canada for a family milestone, and the couple had hoped Eleni would be able to travel there herself as a citizen, on a Canadian passport, rather than navigating permanent resident travel document requirements. Because the file stalled, that trip happened with Eleni still travelling as a permanent resident, using her existing travel documents and re-entry procedures rather than a Canadian passport. It was not a legal problem — permanent residents can travel and return, provided their status documents are in order — but it added planning friction and cost that citizenship would have avoided, and the family did not get the outcome they had hoped for on the timeline that mattered to them.

The identity concern itself was resolved cleanly and did not resurface. Once the declaration and translator's letter were on file, no reviewing officer raised the spelling issue again, and Eleni's file did not require an in-person interview beyond the standard citizenship test process. The damage was contained to the delay itself, not compounded by a refusal or a reopened investigation.

What you can learn from this