Документы · локальный инструмент

Letter of Explanation для IRCC: структура, доказательства и границы

Letter of Explanation — не магическая форма и не место для длинной persuasive biography. Это контролируемый слой между конкретным вопросом формы/checklist и приложенными records. Сильный LOE называет issue, даёт проверяемые facts/chronology, индексирует evidence и формулирует узкий request. Он не создаёт отсутствующий CRS factor, не исправляет program ineligibility, не заменяет required document автоматически и не нейтрализует false or omitted information.

После ITA Открыть документы

Когда explanation уместно и чего оно не делает

IRCC Help Centre позволяет online applicant добавить explanation как optional document и использовать дополнительный document, если ответ не помещается. Для required document, который невозможно получить по причинам вне контроля, current supporting-documents page предлагает letter с причиной и evidence efforts; officer может запросить больше, дать time, продолжить без document или решить по submitted record — acceptance не гарантирована. LOE также помогает прозрачно исправить previous answer, сообщить change или объяснить unusual evidence. Но сначала correction/change проводится через правильный form/account/webform channel и пересчитывается impact. Если факт снижает CRS ниже cut-off, разрушает eligibility или затрагивает inadmissibility/misrepresentation, красивое explanation не является remedy и нужен case-specific review.

Прямой ответ · проверьте по связанным официальным источникам

Интерактивная навигация

Собрать privacy-safe каркас LOE

Выберите broad issue, availability required document, possible eligibility/score impact и evidence categories. Tool работает локально, не просит имена, даты, страны, employer, UCI, application number или narrative и возвращает только Issue → Facts → Evidence → Request outline и escalation flags.

Не вводите номер паспорта, UCI, номер заявления, медицинскую историю или подробные финансовые сведения.

Структура без личного narrative

Тип вопроса

Обязательный документ

Влияние на eligibility или score

Какие broad evidence categories доступны?Официальное подтверждениеДоказательство попытокХронология и version recordНезависимое corroboration

Сравните по одинаковым критериям

Четыре части LOE и их границы

Каждая часть отвечает на один вопрос. Evidence index важнее риторики, а correct submission channel важнее filename.

Сравнение по официальным источникам

Четыре части LOE и их границы
Критерий	Опубликованное правило	Что сверить	Чего вывод не доказывает
Issue	Назовите exact form/section/question, checklist slot, request letter или discrepancy, к которому относится explanation. Один LOE может иметь numbered issues, но каждый получает отдельную структуру.	Current instruction/checklist/request, old/new form values и concise issue label. Не вставляйте sensitive identifiers в публичный planner.	Общий заголовок “to whom it may concern” не объясняет, что officer должен reconcile. Naming issue не доказывает facts.
Facts	Дайте короткую chronology: что произошло, когда, почему records отличаются, что было известно на relevant date и какое correction/change внесено.	Contemporaneous official/personal records, source-of-truth timeline, old/new snapshots and effective dates. Facts отделены от assumptions.	Narrative не должен подгонять reality под program. Emotional importance, good faith или intent не заменяют objective requirements and accurate answers.
Evidence	Каждый factual statement связан с exhibit: required document, alternative record, issuer explanation, receipt/tracking, proof of efforts, translation or corroboration.	Index с filename/page, issuer, date and proposition. For missing document include correct-authority request, receipt, follow-up and official reason/delay where possible.	Volume не равен probative value. Self-created summary does not become independent evidence. Letter + efforts do not guarantee waiver/acceptance.
Rule/context	При необходимости cite direct official instruction that creates requirement or explains missing-document/update channel. Use only relevant excerpt in own words.	Current Canada.ca/Help Centre URL, checked date and applicable program guide. Dynamic interface is described, not frozen by screenshot alone.	LOE не является legal brief by default. Unrelated case law/blog quotes can obscure facts. Official rule cannot make an unsupported fact true.
Request	Formulate narrow procedural request: consider attached evidence, accept correction, note change, review alternatives or contact applicant if further document is required.	Request matches actual channel and powers. Include no demand for approval or invented extension; follow exact account/request deadline.	Applicant cannot instruct officer to ignore requirement, award points or waive inadmissibility. Request wording does not bind IRCC.
Submission/channel	Before submission use correct optional/client information/checklist slot. After submission send requested document through account and transmit it, or use web form for unsolicited change/update where instructed.	Upload/transmit confirmation, webform receipt, request deadline, filename and final package archive. Duplicate submissions are controlled.	“Uploaded—not submitted” is not transmitted. Sending repeated webforms can delay review. LOE in wrong slot may not cure missing required upload.

Issue

Опубликованное правило: Назовите exact form/section/question, checklist slot, request letter или discrepancy, к которому относится explanation. Один LOE может иметь numbered issues, но каждый получает отдельную структуру.

Что сверить: Current instruction/checklist/request, old/new form values и concise issue label. Не вставляйте sensitive identifiers в публичный planner.

Чего вывод не доказывает: Общий заголовок “to whom it may concern” не объясняет, что officer должен reconcile. Naming issue не доказывает facts.

Facts

Опубликованное правило: Дайте короткую chronology: что произошло, когда, почему records отличаются, что было известно на relevant date и какое correction/change внесено.

Что сверить: Contemporaneous official/personal records, source-of-truth timeline, old/new snapshots and effective dates. Facts отделены от assumptions.

Чего вывод не доказывает: Narrative не должен подгонять reality под program. Emotional importance, good faith или intent не заменяют objective requirements and accurate answers.

Evidence

Опубликованное правило: Каждый factual statement связан с exhibit: required document, alternative record, issuer explanation, receipt/tracking, proof of efforts, translation or corroboration.

Что сверить: Index с filename/page, issuer, date and proposition. For missing document include correct-authority request, receipt, follow-up and official reason/delay where possible.

Чего вывод не доказывает: Volume не равен probative value. Self-created summary does not become independent evidence. Letter + efforts do not guarantee waiver/acceptance.

Rule/context

Опубликованное правило: При необходимости cite direct official instruction that creates requirement or explains missing-document/update channel. Use only relevant excerpt in own words.

Что сверить: Current Canada.ca/Help Centre URL, checked date and applicable program guide. Dynamic interface is described, not frozen by screenshot alone.

Чего вывод не доказывает: LOE не является legal brief by default. Unrelated case law/blog quotes can obscure facts. Official rule cannot make an unsupported fact true.

Request

Опубликованное правило: Formulate narrow procedural request: consider attached evidence, accept correction, note change, review alternatives or contact applicant if further document is required.

Что сверить: Request matches actual channel and powers. Include no demand for approval or invented extension; follow exact account/request deadline.

Чего вывод не доказывает: Applicant cannot instruct officer to ignore requirement, award points or waive inadmissibility. Request wording does not bind IRCC.

Submission/channel

Опубликованное правило: Before submission use correct optional/client information/checklist slot. After submission send requested document through account and transmit it, or use web form for unsolicited change/update where instructed.

Что сверить: Upload/transmit confirmation, webform receipt, request deadline, filename and final package archive. Duplicate submissions are controlled.

Чего вывод не доказывает: “Uploaded—not submitted” is not transmitted. Sending repeated webforms can delay review. LOE in wrong slot may not cure missing required upload.

Проверка доказательств

Preflight для одного explanation issue

Рассматривайте каждый пункт как факт для проверки, а не как формальную отметку без подтверждающих документов.

Issue привязан к exact requirementЕсть form/section/question, checklist slot или request; не пишется универсальная autobiography.
Facts отделены от argumentChronology проверена; unknowns помечены; old/new values и effective date сохранены.
Eligibility/CRS impact рассчитанCorrection/change проверен до upload. Material issue escalated; LOE не используется как points substitute.
Required document status ясенDocument included, genuinely unavailable or delayed; applicable instruction reread.
Proof of efforts индексированRequest correct authority, receipt/tracking, follow-up and issuer response linked to missing document.
Каждый fact имеет exhibitFilename/page and proposition recorded; translation/original chain complete; no irrelevant bulk.
Request узкий и реалистичныйAsks consideration/review rather than approval guarantee, points restoration or waiver promise.
Correct channel и deadline подтвержденыOptional slot, required upload, account transmit or webform chosen from current instruction.
Final transmitted version archivedPDF opens after merge; receipt/confirmation, date and affected application version saved.

Шаг за шагом

Как написать LOE, который упрощает проверку

Двигайтесь по порядку и проверяйте определяющую инструкцию на каждом этапе.

1
1. Остановите drafting и классифицируйте issue
Определите missing document, correction, post-submission change, complex evidence or form overflow. Найдите official instruction and channel. If issue may affect score/eligibility/admissibility, complete impact review first; do not let wording decision hide substantive problem.
2
2. Постройте source chronology
Из records выпишите dates/events, old answer, correct/current fact, effective date and why discrepancy occurred. Use neutral language. Не заполняйте gaps memory guess. Mark what is proved, inferred or unavailable. One chronology feeds form correction, LOE and evidence index.
3
3. Соберите evidence hierarchy
Start with required/primary issuer record, then official corroboration, third-party records and applicant-created explanation. For unavailable document show correct request, payment/receipt, delivery/tracking, follow-ups and authority reason. Translate complete relevant content according to current requirements.
4
4. Draft Issue → Facts → Evidence → Request
One short opening identifies application section and purpose. Numbered facts follow chronology. Exhibit list states what each file proves. Final request is narrow. Remove repetition, predictions, emotional adjectives, copied legal phrases and any claim not supported by attachment.
5
5. Run contradiction and impact checks
Compare LOE with all forms, profile, Personal/Work/Address/Travel history, spouse records and documents. Recalculate CRS/program where relevant. Correction of one date can change police country, experience window or common-law start. Update every affected field, not only explanation.
6
6. Submit and prove transmission
Follow current checklist/account/request. Combine files only if slot instructs and keep readable bookmarks/index. After upload complete signature/transmit steps and save confirmation. For unsolicited post-submission change, use current web form instruction and avoid duplicate submissions unless directed.

Вопросы и различия

Частые вопросы

Короткие ответы о деталях, которые чаще всего меняют следующий шаг.

Letter of Explanation обязателен для каждой application?

Нет универсального mandatory LOE. Use it when current checklist offers optional/client information, answer needs space, document is unavailable, or a correction/change/evidence structure genuinely requires explanation. Unnecessary narrative can create contradictions. Required forms and documents still follow program checklist; explanation is subordinate.

Можно ли LOE заменить отсутствующий документ?

Not automatically. Current IRCC page says if document cannot be obtained for circumstances outside control, write why and provide supporting proof of efforts. Officer may request information, grant time, continue or decide on record. Acceptance is not guaranteed. Include correct authority request, receipts/tracking and official reason where available.

Какая лучшая структура LOE?

Issue → Facts → Evidence → Request. Identify exact requirement; provide concise verified chronology; index attachments and proposition each proves; make narrow request to consider record. Add official rule only when it clarifies requirement/channel. Avoid autobiography, repetition, outcome predictions and unsupported advocacy.

LOE исправит ошибку в Express Entry profile?

Current e-APR must contain truthful correction and affected fields/evidence must align. First determine old/new fact and recalculate program/CRS. If corrected score falls below round cut-off or eligibility is lost, explanation does not restore points. Material cases need review before submission; never preserve known false answer for consistency.

Как сообщить change после submission?

Use current IRCC web form for changes such as marriage/divorce, child, passport, job, education or language unless IRCC instructed another channel. If IRCC requests a document, follow account/request and transmit it. Save receipts. Explanation describes change/evidence, but sending through wrong or duplicate channels can delay handling.

Нужно ли цитировать закон и court cases?

Usually exact official instruction and facts are more useful than a generic legal essay. Complex refusal, inadmissibility, procedural fairness or misrepresentation issue may need licensed case-specific legal analysis. Do not paste cases without relevance or let citations substitute evidence. Public tool intentionally creates no legal argument.

Как оформить exhibits?

Use stable filename/index: Exhibit A — issuer/date — proposition — relevant page. Ensure original, translation and certified/affidavit components where required. Combine per upload limits without hiding pages. Every referenced attachment must be included in correct slot and readable after compression.

Можно написать, что ошибка была случайной?

Only if truthful, and explain concrete chronology/evidence rather than label. “Accidental” does not determine materiality or consequence. Correct all affected answers, quantify impact and disclose promptly through current channel. Good-faith assertion does not create points or erase false information; complex issue needs review.

После upload документ уже отправлен?

Not necessarily. Current requested-document guidance distinguishes Uploaded — not submitted to IRCC from successful transmit. Complete Next/sign/security/transmit steps and save confirmation. For webform save acknowledgement. Draft, selected file or payment screen is not proof IRCC received final version.

Можно объединить несколько issues в один LOE?

Да, если upload slot допускает один файл, но structure должна оставаться разделённой. Начните с короткого contents/index, затем Issue 1 → Facts → Evidence → Request, Issue 2 → Facts → Evidence → Request. Не смешивайте missing police certificate, work-date correction и family change в один narrative paragraph. Для каждого issue укажите affected form/field, effective date, exhibits and separate eligibility/CRS impact. Если issues требуют разных official channels or deadlines, submit through each controlling route rather than assuming one optional upload updates everything. Keep final filenames/page references stable, verify every exhibit is included and archive transmitted version. Multiple issues increase contradiction risk, so run full regression across profile, e-APR and histories before submission.

След доказательств

Официальные источники

Откройте определяющий источник и проверьте правило в исходном контексте.

How do I fill out an IRCC application? IRCC Help Centre
I need more space on an IRCC form IRCC Help Centre
Your IRCC application: Supporting documents Immigration, Refugees and Citizenship Canada
How can I update an IRCC application in progress? IRCC Help Centre
You asked me for a new document: how to submit it IRCC Help Centre
Upload supporting documents after an Express Entry application IRCC Help Centre
Express Entry: Apply for permanent residence Immigration, Refugees and Citizenship Canada
Consequences of immigration and citizenship fraud Immigration, Refugees and Citizenship Canada
Find IRCC application forms and instructions Immigration, Refugees and Citizenship Canada

Понятный следующий шаг

Верните outline в защищённый claim ledger

Заполните facts только из records, index exhibits, recalculate impact and submit through current channel. Public tool should remain free of personal case data. Before creating final PDF, compare every cited page with exact form answer, remove unsupported adjectives, confirm original/translation pairing and ask a second reviewer to reproduce issue from index alone. После transmission сохраните receipt securely and do not overwrite source version.

Открыть документы Проверить after-ITA workflow

Каркас Letter of Explanation

Верните outline в защищённый claim ledger