For a Canadian citizenship by descent application to pass IRCC’s completeness check, the package needs correctly completed forms, documents proving the applicant’s identity, proof of the ancestor’s Canadian citizenship, and an unbroken chain of documents linking that ancestor to the applicant generation by generation.
In short
- A Canadian citizenship by descent package needs a family tree, an explanation letter, and generation color-coding regardless of the applicant’s situation.
- If the completeness check fails, the package is returned at the intake stage — the application has to be filed and processed from scratch.
- A name discrepancy anywhere in the document chain requires a bridging document and its own paragraph in the explanation letter.
- A missing official document for one generation isn’t grounds for refusal if every attempt to obtain it is documented.
- Don’t delay filing while waiting on a document that may never surface — document the gap instead and file the package.
Why the completeness check decides everything
IRCC won’t issue an Acknowledgment of Receipt (AOR) or a file number until it’s satisfied the application package is complete and meets requirements — in practice, this stage is known as the completeness check. It’s the first filter every application passes through at intake, and it’s what determines whether a file moves forward at all.
A complete package has four elements: correctly filled-out forms, documents proving the applicant’s identity, proof of the Canadian ancestor’s citizenship, and a chain of documents linking that ancestor to the applicant — generation by generation, with no gaps.
If the package clears the check, the applicant receives an AOR and a file number — from that point on, individual documents can be submitted later if something in the file needs clarifying. If the check fails, the package gets returned to the sender, and it’s returned at the intake stage, not at the back of the processing queue. That means the application has to be filed again — and the wait starts over, which can add months to the timeline.
What every package needs, regardless of the situation
Whatever the applicant’s specific document situation looks like, the package has to contain three elements.
- A family tree. One page, cleanly laid out: full names, dates, and the relationships between everyone involved clearly labeled. An officer should be able to understand the lineage just by looking at the diagram — without reading the explanation letter.
- An explanation letter. A written account that connects every document in the package to every person in the chain of descent. It doesn’t have to be elaborate, but it does have to be clear — and what it needs to cover depends on the applicant’s specific document situation.
- Color-coding by generation. Each generation gets its own color, so that picking up any document in the package, an officer can tell which generation it belongs to within seconds.
These three elements go into every file regardless of which type of document situation is involved.
A one-page family tree, an explanation letter that ties documents to people, and color-coding by generation go into every package, regardless of the applicant’s specific document situation.
Scenario 1: a complete set of documents with no discrepancies
The most favorable case: official documents exist for every generation — birth, marriage, and death certificates from vital records offices, provincial archives, or civil registries, with no gaps and no discrepancies in names.
- Build the explanation letter as a route. Walk the officer from the Canadian ancestor to the applicant, citing each document as it comes up: the ancestor’s birth certificate, their marriage certificate (if applicable), birth certificates for each intermediate generation, and birth certificates for the parents and the applicant. The story is told in chronological order — from ancestor to applicant.
- Organize documents by generation, not by country. Within each generation, use the color code and an index, in filing order — from ancestor to applicant.
- Don’t group the package by the country each document came from. That logic feels intuitive to the applicant, but officers read the package by generation using the color scheme: documents from three different countries grouped by country are harder to follow than the same documents grouped by generation.
That logic feels intuitive to the applicant, but officers read the package by generation using the color scheme
Building the explanation letter with a complete document set
Three steps for when documents exist for every generation and there are no discrepancies.
- Build the letter as a route from ancestor to applicantCite each document as it comes up in the chain
- Organize documents by generationColor code and index within each generation
- Don’t group the package by country of originOfficers read by generation, not by country
Scenario 2: names don’t match across the document chain
This is the most common of the three situations: every document is official, every generation is covered, but somewhere along the chain the names don’t match perfectly. A grandmother changed her surname after marriage, a grandfather’s name was spelled differently when crossing a border, a married name was never officially recorded anywhere — these kinds of discrepancies are typical for families who moved between countries or had records created in different languages.
Each discrepancy needs two things.
- A bridging document. This officially confirms that two versions of a name belong to the same person. A notarized statement, a declaration, a letter from an archive explaining the spelling variations, a census record, a marriage certificate, or a death certificate can all work — any official document showing the link between the names. What’s actually accepted in a given case depends on the applicant’s circumstances.
- A separate paragraph in the explanation letter. This lists each discrepancy individually: which version of the name appears where, which document created it, and which document is attached to tie it back to the rest of the chain. The color-coding and the family tree stay the same as in the first scenario — the letter simply gains this extra section.
If no bridging document is attached, IRCC typically sends a request for additional information or a letter asking for an explanation of the discrepancy. Given how long citizenship certificate applications currently take to process, waiting for that letter, responding to it, and then waiting again adds a real delay. A name discrepancy should be explained upfront, before an officer has to ask about it.
Every name discrepancy needs a bridging document and its own paragraph in the explanation letter. Skip that, and IRCC will send a request — adding more delay to already-long processing times.
Scenario 3: a document is missing for one generation
The third scenario: no official document exists at all for one generation — the registrar can’t issue a birth certificate, there’s no record in the archive, and church registers for the relevant region were either destroyed or were never accessible outside the country. This stops a lot of applicants in their tracks — and it shouldn’t: a missing document isn’t, by itself, grounds for refusal. IRCC doesn’t expect applicants to produce a paper that no longer physically exists.
In place of the document, what’s needed is evidence that an attempt was made to obtain it. The package should include:
- letters to vital records offices;
- requests to provincial and national archives;
- inquiries to church registries in the relevant region.
What matters is the fact that correspondence took place, not its outcome: even a reply saying “no record exists” becomes part of the evidence. Every letter gets printed, every request has its date logged and its reference number saved — building a paper trail for every attempt made. Whatever turns up from the search is attached to the package and described in the explanation letter.
What matters is the fact that correspondence took place, not its outcome: even a reply saying “no record exists” becomes part of the evidence
An official letter from an archive stating that no record exists is the cleanest form of confirmation, if the archive is willing to issue one. But it’s not a requirement: what matters isn’t whether that letter exists, but whether the effort is documented — correspondence, dates, repeated requests, and the responses received.

If a document for a generation physically doesn’t exist, that’s not grounds for refusal on its own. But in its place, you need a documented trail of every attempt to get it: letters, dates, reference numbers.
What to gather in place of a missing document
Should you wait for a missing document before filing
Applicants often wait far too long for a single missing document, trying to assemble a perfect package before filing. It’s an understandable impulse — nobody wants to send in an incomplete file — but if everything else is ready and the document may never surface at all, there’s no reason to hold the whole package back for it.
Instead of waiting, the move is to document the gap — the same documentation described above for a missing generation document — write the explanation, and file the package. A file that’s already in IRCC’s queue with one documented gap keeps moving through the process. A file sitting unfiled, waiting on a document that may never turn up, goes nowhere.
A file sitting unfiled, waiting on a document that may never turn up, goes nowhere
If a missing document may never surface, don’t hold the whole package back for it — document the gap and file the application.
Frequently asked questions
How long does it currently take to process a Canadian citizenship by descent application
At the moment, processing a citizenship certificate application takes around 34 months (almost 3 years), with a backlog of over 130,000 applicants. This matters when weighing the delay caused by an IRCC request or a returned incomplete package — refiling means waiting out that same timeline all over again.
Can you file if one relative in the chain has no identity documents at all
A complete absence of personal identity documents for someone in the chain isn’t addressed separately — the material covers cases where a specific document (a birth or marriage certificate) is unavailable for one generation, not a relative’s entire identity. For that kind of gap, you gather documentation of the attempts made to obtain the record and explain it in the explanation letter.
What if the name discrepancy involves the applicant rather than the ancestor
The material describes the logic for handling name discrepancies in general terms: each case needs a bridging document confirming that both versions of the name belong to the same person, plus a separate paragraph in the explanation letter describing where each version appears and what supports it. That logic isn’t tied to which person in the chain the discrepancy involves.
How many times do you need to contact an archive before IRCC accepts a negative response as evidence
A specific number of attempts isn’t defined — what matters isn’t the count of attempts but whether they’re documented: letters, dates, reference numbers, and the responses received, including a reply stating no record exists. Even a single official archive response confirming no record exists can become part of the evidence, as long as the other efforts are documented too.
How do you document a gap if you decide not to wait for a missing document
Gather letters to vital records offices, requests to archives, and inquiries to church registries; log the date and reference number for each one; attach every response received (including “no record exists”); and describe the gap in the explanation letter. The package is then filed with the rest of the ready documents, without waiting for the missing one to turn up.






Comments
Reader experience is useful, but it is not advice: check the rules on the official site.
No account needed: click Sign in, type any name, and you are done.