TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Immigration
№ 280 Case Study — Immigration

Keeping a Son's Path to Permanent Residence Clear of His Father's Error

When immigration officials flagged a misrepresentation on Dirk's file, his family worried it would drag down his son Bram's own path to permanent residence, even though Bram had done nothing wrong himself.

Immigration8 min readHawkesbury, OntarioFamily-wide misrepresentation fallout
All Immigration case studies
ClientThao, a bookkeeper trained as an accountant abroad, trying to protect her son Bram's own immigration file
The issueA misrepresentation finding against her husband Dirk threatened to affect their son Bram's separate permanent residence application
ServiceSeparated Bram's file from his father's finding and built the record needed to keep his application on its own footing
ResolutionBram's application proceeded on its own merits, with no misrepresentation finding attached to his own record

The situation

What Thao was afraid of, calling our office in the fall, was not the paperwork or the fines or even the years-long bar that can follow a misrepresentation finding. What she was afraid of was that her son Bram, halfway through a college diploma program in Hawkesbury and counting on his own permanent residence application to let him stay in Canada after he graduated, would be swept up in a problem that was, as far as she understood it, entirely his father's doing.

Thao had trained as an accountant in her home country before the family came to Canada. Her credentials had not transferred cleanly, and for the past several years she had worked as a bookkeeper for a small local firm, the only income the household had while her husband Dirk focused on stabilizing the family's immigration status. Dirk's own permanent residence application, filed a few years earlier, had listed his work history in a way that immigration officials eventually found did not match records they obtained independently. The department issued a finding that Dirk had misrepresented a material fact on his application, a serious finding that can carry consequences lasting several years and can, in some circumstances, extend to family members included on the same application.

Bram had not been included as a dependent on his father's application; he had filed his own permanent residence application separately, based on his Canadian college credential and work experience, once he became eligible in his own right. But the family did not know, when the finding against Dirk came through, whether that separation would actually protect Bram in practice, or whether an officer reviewing Bram's file would treat his father's finding as a reason to doubt the whole family's honesty.

Dirk and Thao tried, at first, to sort it out themselves, drafting a letter to the department explaining the discrepancy, hoping a straightforward explanation would resolve things before it affected anyone else. The letter went unanswered for months, and by the time Thao called our office, Bram's own application had reached the stage where an officer could request additional information at any time, and the family no longer felt they could afford to wait and see. Thao described the fear plainly on that first call: it was not about the money the family had already spent on Dirk's application, or the years-long bar that might follow his finding, it was the thought of her son, so close to finishing his diploma, having his future decided by a mistake he had never made and had no way to explain himself.

The complication

The complication was not simply that Dirk had made a mistake. It was that Bram's application, though legally separate, was not invisible to the officer who would eventually review it. Permanent residence files are not assessed in isolation from a family's broader immigration history; an officer can and often does look at whether other members of the same household have had findings against them, particularly when an address, a sponsor relationship, or supporting documents overlap between files.

Bram's application did overlap with his father's in a few small but real ways. Some of his early work experience, listed to support his own eligibility, had been at a business where Dirk had also once worked, and one of Bram's reference letters had been written by someone who had also supplied a reference for Dirk's now-discredited application. None of this meant Bram's file had a problem. But it meant an officer reviewing Bram's application, aware of the finding against his father, might reasonably want to satisfy themselves that Bram's own record held up independently, and might ask harder questions than they otherwise would.

The letter Dirk and Thao had already sent to the department, explaining his side of the misrepresentation finding, had unintentionally made this worse. It had been written informally, referred to family circumstances broadly, and in trying to contextualize Dirk's error, it mentioned Bram's application by name, effectively drawing a line between the two files that had not previously existed on paper. Once that connection existed in the department's records, it could not simply be unwritten.

Our first job, then, was not to relitigate Dirk's finding, that had its own separate process and its own timeline, and we were candid with the family that it was unlikely to be reversed. Our job was to make sure Bram's file could be assessed cleanly on its own facts, with a record that explained the overlaps that did exist rather than leaving an officer to wonder about them, and without inviting further scrutiny by raising the connection ourselves in a way that read as defensive. We were also careful about timing: Bram's application had not yet reached the stage where a decision was imminent, which gave us a real window to correct the overlaps before an officer picked the file up, rather than trying to explain them after the fact once a request for information had already gone out.

What we did

  1. Reviewed Dirk's finding in full. Before deciding how to protect Bram's file, we needed to understand exactly what the department had found against Dirk, which facts were disputed, what evidence the officer had relied on, and whether a reconsideration of that finding was realistic, because Bram's strategy would look different depending on whether his father's finding was likely to stand.
  2. Identified every overlap between the two files. We went through Bram's application line by line against what we knew of Dirk's, flagging the shared employer, the shared reference writer, and any other point of contact between the two records, so that nothing would surprise us if an officer noticed the connection later and started asking questions we had not already prepared for.
  3. Prepared independent corroboration for the overlapping points. For the work experience Bram had gained at the employer his father had also worked for, we obtained separate documentation directly from the business, payroll records and a supervisor's letter, that supported Bram's employment on its own terms, without relying on anything connected to Dirk's account of his own work history.
  4. Replaced the shared reference. Rather than leave a reference letter that had also been used to support Dirk's now-discredited application, we asked Bram to obtain a new reference from an instructor at his college who had no connection to his father's file at all, removing a link that served no real purpose in Bram's own case and only invited questions an officer had no reason to ask.
  5. Drafted a clarifying submission to accompany Bram's file. We prepared a short, factual cover letter explaining, without excuse or elaboration, that his application was filed independently, supported by his own record, and that the earlier informal letter referencing his name had been sent by his parents without our involvement and did not reflect the basis of his own claim.
  6. Advised the family to stop self-correcting. Part of the reason the file had gotten more complicated was the earlier letter Dirk and Thao had sent on their own, and we were direct with them that any further communication with the department about either file needed to go through us, so nothing else got said informally that could later be read as connecting the two matters.
  7. Monitored Bram's file through to decision. Once the corrected application was in, we tracked its progress and prepared responses in advance for the kinds of follow-up questions an officer might reasonably ask about the overlaps we had already addressed, so that if a request for information came, the response could go out quickly rather than triggering further delay.
  8. Confirmed the timeline with Thao before submitting. Because the family had been through a stressful few months already, we walked Thao through exactly what the submission said and why each piece of corroboration had been chosen, so she understood the strategy fully rather than simply trusting that the file would work, and so she could answer confidently if Bram ever asked her what had actually been done on his behalf.

The outcome

Bram's application was approved, without the department raising the overlaps with his father's file at all. Whether that was because our submission preempted the question or because the officer reviewing the file simply did not connect the two, we cannot say with certainty, departments do not explain why a question was not asked. What we can say is that the file was built so that if the question had come, the answer was already on the record.

Dirk's own finding stood. We had been honest with the family from the outset that undoing it was not something we were retained to do and not something we expected to happen quickly if pursued separately, and the family made the decision not to pursue a challenge, choosing instead to focus their resources on protecting Bram's path forward. That was, as we told them, a reasonable choice given what was actually at stake for each of them.

For Thao, the result meant her son finished his diploma and became a permanent resident on his own record, with nothing in his file suggesting doubt about his honesty. She told us afterward that what had frightened her most was not the possibility of a fine or a delay but the thought that her son's future could be shaped by a mistake he had not made, and that fear, at least, did not come to pass.

The family's early attempt to handle Dirk's finding on their own had cost time and had briefly complicated Bram's file by linking the two on paper. It did not, in the end, cost Bram his application, but it is part of why we tell clients early in any misrepresentation matter that informal letters written with good intentions can create connections a department did not previously have reason to draw. Thao still worries about what Dirk's finding will mean for him in the years ahead, but she no longer worries about Bram, and she told us that being able to separate those two worries, rather than carrying them as one undifferentiated fear, was worth more to the family than she had expected going in.

What you can learn from this

  • A finding against one family member does not automatically affect another person's separate application, but overlapping details, a shared employer, a shared reference, can invite an officer to look harder. Identify and address those overlaps before they are questioned, not after.
  • If you write directly to an immigration department to explain a problem, be careful what you name. An informal letter meant to provide context can create a written connection between two files that did not exist before, and that connection cannot be undone.
  • Get advice before trying to resolve a misrepresentation finding informally. What feels like a reasonable explanation, sent without legal guidance, can complicate a related file more than it clarifies the original problem.
  • When two family members' immigration files might be seen as connected, build independent corroboration for the file you are trying to protect, sourced separately from anything tied to the other person's account.
  • Decide, deliberately, which fight is worth having. Protecting a dependent's separate application was the priority here, even though it meant not pursuing a challenge to the other finding at the same time.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is an immigration problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →