When One Letter in a Name Nearly Stalled a Family's PR Application

The situation

Arman worked as a grocery clerk and Reza as a landscaper, and together they were raising their son Bilal in Wasaga Beach. The family had come to Ontario from Iran several years earlier on temporary work permits, building steady if modest lives around shift schedules and seasonal landscaping contracts. When they became eligible to apply for permanent residence as a family unit, they gathered everything the application asked for: passports, birth certificates, a marriage certificate, police certificates, and the various forms that establish who someone is and how they relate to the people they are applying with.

They filed the application themselves, confident the paperwork was in order. Months into processing, they received a procedural fairness letter — a formal notice from the immigration officer reviewing their file, flagging a concern and giving them a chance to respond before a decision was made. The concern was not about their work history, their finances, or their conduct. It was about spelling.

What the paperwork revealed

Names transliterated from Persian script into English do not always land on a single, fixed spelling. A name can be rendered several defensible ways depending on which document was issued when, by whom, and under what transliteration convention was in use at the time. In this family's case, Reza's given name appeared as "Reza" on her passport and current government identification, but as "Raza" on the birth certificate issued decades earlier in Iran. Bilal's surname carried a similar one-letter variation between his birth certificate and his Canadian study documents, the product of an older transliteration used when his birth was first registered.

To the family, these were obviously the same people under the same names, just spelled differently by different clerks in different decades. To an immigration officer working from a file with no context, an unexplained discrepancy between a birth certificate and a passport is a red flag for identity fraud — one of the most serious concerns an officer can raise, because Canada's immigration law, the Immigration and Refugee Protection Act, allows applications to be refused where an officer is not satisfied of an applicant's identity or where information provided is inconsistent or misleading. The officer was not accusing the family of anything. The letter simply said the discrepancy needed to be explained and supported, and gave a deadline to respond.

The family had never had to think about this before. Every other document they held — driver's licences, health cards, school records — had been issued in Canada using the same current spelling. It was only the older, foreign-issued documents that told a different story, and nothing in the original application had explained why.

What made the letter unsettling was the silence around it. It did not say whether the officer suspected the family had used two identities on purpose, or simply needed the gap explained. That ambiguity is typical of these letters, and it is exactly why they should never be answered casually. A rushed, thin response risks reading as evasive; a response that ignores one of the two discrepancies risks leaving half the concern unaddressed and inviting a refusal on the part left unanswered.

What we did

1. Mapped every document against every name. We built a simple table of every identity document in the file, listing the exact spelling used on each one, in date order. This made the pattern visible at a glance: the older, foreign-issued documents used one transliteration, and every Canadian-issued document used another, with the change occurring around the time the family first arrived and their names were transliterated afresh for Canadian records.
2. Drafted statutory declarations for both affected family members. A statutory declaration is a written statement of fact, signed before a person authorized to take it, that carries legal weight because making a false one is an offence. For Reza and for Bilal, we prepared declarations explaining, in plain terms, that the individual named under each spelling was one and the same person, describing how and when each spelling had come into use and why.
3. Gathered corroborating evidence beyond the family's own word. A declaration explaining a discrepancy is stronger when something independent backs it up. We helped the family collect supporting documents that used both spellings and tied them to the same date of birth and family relationships — including school enrolment records, a bank record, and a translated notation from the original foreign registry confirming the birth certificate and the passport referred to the same individual.
4. Had the foreign documents professionally translated and certified. The original birth certificates had been translated some years earlier for an unrelated purpose, using a translator without formal certification. We arranged for certified translations that explicitly noted the name variation and its transliterated origin, since an inconsistency the officer could see explained on the document itself carries more weight than one explained only in a cover letter.
5. Responded within the deadline, addressing each family member separately. Procedural fairness letters carry a strict deadline, and missing it can result in a refusal without further opportunity to respond. We filed a single response package but structured it to address Reza's discrepancy and Bilal's discrepancy as two distinct issues, each with its own timeline of documents and its own declaration, rather than treating the family as one undifferentiated concern.

The outcome

The response resolved the concern for Arman and Reza. Their documents, once mapped and explained, told a consistent story that the officer accepted, and their permanent residence was approved as a couple within the following several months. Bilal's situation took longer to close out. His transliteration discrepancy involved a family surname affected by a second, older registration change on his father's side, which meant the supporting paper trail was thinner and required a further specific document — a formal confirmation from the original foreign registry — that took additional months to obtain and submit.

The outcome was not the clean, simultaneous approval the family had hoped for when they first applied together. Arman and Reza became permanent residents while Bilal's file remained open, still a dependent on their record but pending his own confirmation. It meant a period of real uncertainty for a young man watching his parents' status settle while his own stayed unresolved, and it meant the family absorbed the cost of a certified registry document and a further round of certified translation, on top of what they had already spent — together, a few hundred dollars they had not budgeted for on a landscaper's and a grocery clerk's income. Several months after his parents' approval, Bilal's additional document came through and his permanent residence was approved on the strength of the same declaration and reasoning that had worked for his mother, closing the file for the family as a whole. Throughout the wait, Bilal kept his existing temporary status current so there was no gap in his legal ability to remain and work in Canada while the extra document made its way through the foreign registry. That single decision — treating the interim period as something to actively manage rather than simply wait out — is often what separated a delay from a crisis in his case.

It was not the outcome anyone would have chosen over a first-time approval with no complications. But given where the file stood when the procedural fairness letter arrived, with a live identity discrepancy on the record and a hard deadline to answer it, getting two of three family members through on schedule and the third through a few months later, without a refusal or a fresh application, was a workable landing for everyone involved.

What you can learn from this