A Job Title That Matched Nothing on the Official List

The situation

What kept Niran up at night was not the idea of a rejection letter itself, it was picturing what came after one: refiling from scratch, losing another year or more of processing time, and Ratana stuck in limbo on a temporary status that was never meant to stretch this long. He worked as an anesthesiologist in Wallaceburg, a schedule that left little room to untangle a bureaucratic problem on his own, and the more he read about what his wife's application actually required, the more that fear felt specific rather than vague.

Ratana had spent nearly six years working abroad before the couple married and she came to Canada, employed the whole time by an engineering firm where her cousin Anahit was a partner. Her role there had grown organically, the way jobs do in a smaller firm run by family, and by the time she left she was coordinating client relationships, managing project handoffs between engineering teams, and handling a fair amount of contract administration. Anahit had always called her title 'client liaison,' a description that made sense inside the firm and meant nothing to anyone outside it.

That mattered because the couple's application depended in part on Ratana's foreign work experience being credited against a recognized occupation category, one of the pieces that supported both her own standing and the broader case Niran was building as her sponsor. When Niran started assembling the file himself, he searched the official occupation list for 'client liaison' and found nothing that matched. Every adjacent title on the list described duties that sounded close but not quite right, and none of them used Anahit's language for the job at all.

Ratana's instinct, and Anahit's when Niran called to ask for help, was to simply have Anahit write a letter confirming the title she had always used and let the officer sort out where it fit. Niran was not comfortable leaving that decision to chance, not when the consequence of guessing wrong was the exact outcome he had been dreading. That was the point at which the couple came to us, before anything had been filed and before the gap between the title and the list had become anyone's problem but their own.

There was an added layer of discomfort in raising the question with Anahit at all. She had given Ratana her first real job, mentored her for years, and treated her more like a younger sister than an employee, and Niran worried that questioning the accuracy of a title Anahit had chosen herself might read as ingratitude, even though nobody doubted that Ratana's work had been genuine and valuable to the firm.

What the other side was relying on

There was no opposing party in the usual sense here, but there was a reviewing officer on the other end of the eventual application, and that officer's process was built around matching claimed experience to a defined list of occupations with established duty descriptions. A job title alone tells an officer very little; what the process actually weighs is whether the tasks a person performed line up with the tasks a recognized occupation describes, regardless of what a small firm happened to call the role internally.

Anahit, understandably, was relying on the informal legitimacy that comes from being family and from having genuinely employed Ratana for years. In her mind, a letter from her, confirming the title and the dates, should have been enough, because she knew firsthand that the work was real. That confidence was exactly the risk. A reference letter from a relative who ran the business carries an inherent question mark for a reviewing officer regardless of how honest it is, because the officer has no way to independently verify that the description was not shaped, even innocently, by the closeness of the relationship rather than the actual content of the job.

Ratana was relying on something similar in a different form: the assumption that six real years of work would speak for itself once someone read the letter. Real experience is not the issue an officer is checking for, though. The issue is whether the experience, as described, maps onto a category the program recognizes, and a title invented inside a family firm was never going to do that mapping on its own, however accurately it captured what Anahit meant by it.

What was actually at risk was not whether Ratana had done the work, which was never in question, but whether the file, as it stood, gave a reviewing officer any way to say so with confidence. Filing on the strength of a title and a family reference alone would have put that judgment call in an officer's hands with almost nothing concrete to base it on, and a call like that going the wrong way was precisely the scenario Niran had been afraid of from the start.

There was one more thing the family had not fully weighed: the closer the relationship between an applicant and the person confirming their work, the more a reviewing officer might read routine generosity, a family firm keeping a relative on staff through slow periods, or giving her broader duties than her formal role required, as a sign the position itself had been shaped to help with an eventual application rather than run according to the business's actual needs. None of that was true here, but the file had to make that clear on its own rather than asking an officer to take it on faith.

What we did

1. Set the job title aside entirely as the starting point, because arguing over what 'client liaison' should mean was a losing framework, and instead asked Ratana to describe, week by week if needed, what her actual work involved over the six years, drawing out details she had never thought to mention because they felt too ordinary to matter.
2. Built a duties-based description from Ratana's own account, breaking her role into discrete, concrete tasks, coordinating client communications, managing handoffs between engineering teams, tracking contract milestones, so that the description stood on its own without needing the original title to make sense to anyone reading it cold, since a reviewer would never have set foot inside the firm to know what 'client liaison' actually meant there.
3. Matched those duties against the occupation list independently of anything Anahit or Ratana had assumed, identifying the category whose official duty description most closely mirrored what Ratana had actually done, rather than the category whose name sounded closest to 'liaison,' which turned out to be the wrong instinct entirely and would have undercut the whole filing had it gone unchecked.
4. Asked Anahit for a revised reference letter written to the duties, not the title, walking her through why a letter describing specific tasks and their frequency would carry more weight than one repeating the informal job title she had always used, even though both described the same job, and she rewrote it once she understood what was actually being tested.
5. Separated Anahit's letter from independent corroboration by identifying colleagues and clients from the same period who could confirm elements of Ratana's work, reducing how much the file depended on a single letter from a family member, which addressed the credibility concern directly rather than hoping it would go unnoticed by whoever reviewed the file, and gave the application more than one voice describing the same set of duties.
6. Organized supporting records from the firm itself, including project documentation, internal correspondence, and old client emails that showed Ratana's name attached to the kind of work described, giving the file physical evidence to sit alongside the written accounts rather than relying on recollection alone, six years after most of it happened and long after some of the smaller details would otherwise have faded.
7. Addressed the family relationship directly in a short cover explanation instead of hoping nobody would ask, disclosing plainly that Anahit was Ratana's cousin and that independent corroboration had been gathered specifically because of that relationship, so the file anticipated the exact question a careful reviewer would otherwise have had to raise on their own, later and with more suspicion.
8. Reviewed the complete package against the occupation's official duty list line by line before submission, checking that every duty claimed was both accurate and supported by at least one document in the file, so nothing in the description outran what the evidence actually showed, and nothing the evidence showed went unmentioned in the description, closing any gap a careful reviewer might otherwise have noticed and questioned.
9. Walked Niran and Ratana through the finished file before it was submitted, explaining how each piece of evidence supported a specific duty and why the package as a whole no longer depended on any single document, so they understood exactly what they were filing and why it addressed the fear that had brought them to us, rather than simply trusting that the work had been done correctly on their behalf.

The outcome

The application was filed with a work experience claim built entirely around documented duties rather than an informal title, and it was accepted on that basis without a request for further evidence about Ratana's employment. The specific rejection Niran had been afraid of, the version where a mismatched title cost the couple another year or more, never happened, because the file never gave an officer a reason to doubt where the experience fit.

Getting there cost the couple time up front that a straightforward filing would not have needed: weeks spent reconstructing years of work into a duties-based account, tracking down former colleagues and clients willing to corroborate details, and asking Anahit to rewrite a letter she had thought was already fine. Anahit took the request in stride once she understood the reasoning, though it meant more work for her than the single confirming letter she had first offered, and the process gave her a clearer sense of what her own future reference letters for other former employees should actually look like.

The family relationship, which had felt like a liability at the start of the process, ended up strengthening the file once it was handled openly instead of glossed over. Disclosing the connection to Anahit and building independent corroboration around it meant nobody reviewing the application could later suggest the closeness had been hidden or that the work experience had been inflated to help with an application, which is a very different position than the one Ratana had originally been in.

Ratana's status has moved forward on schedule, and Niran no longer spends his evenings running worst-case scenarios about a rejection letter that, as far as the couple is concerned now, was never going to happen anyway once the file was built the right way. The experience left both of them more careful about how they describe Ratana's earlier work in any future government correspondence, treating the title Anahit gave her as a nickname rather than a category.

What you can learn from this