What to Do if There's an Error in a Document: Translate As Is or Fix It

You hand your translation to the notary, and she says: “Why does your translation say ‘John Smth’ just like the original? That’s an obvious spelling mistake - it should be ‘Smith’!” You try to explain: “But that’s what was in the original…” Yet she’s already doubting your work. On the flip side, if you silently correct the error, the embassy might reject the translation entirely - “the document has been altered.”

This is a real dilemma that translators, notaries, and people submitting documents face. And the answer isn’t as simple as it seems.

The Golden Rule: Official Translations Must Be Exact Copies¶

Let’s start with the most important rule for notarial, sworn, and official translations:

Errors from the original must be reproduced exactly as they appear.

This isn’t a translator’s choice or negligence. It’s a legal requirement in most countries. The UK’s Chartered Institute of Linguists (CIOL) is crystal clear: “If an error is present in the original document, it must also be replicated in the translated version.” Why? Because an official translation is a legal document. Your certification says: “I translated exactly what’s in the original, no changes, no corrections.”

The International Federation of Translators (FIT) states: “Every translation shall be faithful and render exactly the idea and form of the original - this fidelity constitutes both a moral and legal obligation.”

But there’s one crucial caveat.

How to Protect Yourself: [sic.] Notation and Translator’s Notes¶

When you reproduce an error, your job is to signal to readers that it comes from the source, not from you. There are two professional tools for this:

The [sic.] Notation (Simplest Method)¶

[Sic] is Latin for “sic erat scriptum” (“thus it was written”). Place it in square brackets immediately after the error:

• Original: “John Smth”
• Translation: “Juan Smth [sic]”

Or if the error is in word order:

• Original: “Document issued 2025 years”
• Translation: “Documento emitido 2025 años [sic]”

This notation instantly signals: this isn’t my mistake, it was in the original.

Translator’s Note¶

Add a fuller note at the beginning of your translation:

Translator’s note: Spelling errors and unusual word choices in this translation have been reproduced exactly as they appear in the source document.

Or more specifically:

Translator’s note: The surname appears as “Smth” in the original; this translation reproduces that spelling exactly.

This gives context to everyone reading it - the notary, the embassy official, the court - who sees the error in your translation.

Why This Matters: Real Consequences¶

You might be thinking: “Okay, I mark errors with [sic.] - isn’t that just a formality?” No. Errors in documents have real-world consequences.

Name Spelling Errors: Visa Delays for Months¶

In 2023, Canada’s IRCC publicly listed the most common reasons for document rejection. #1: inconsistencies in how names are spelled across documents.

Typical scenario: - Birth certificate: “Mohammad Ali Hassan” - Translation: “Mohammad Ali Hassan” - Passport: “Mohamed Ali Hassan”

The embassy sees three different spellings and raises a flag: “Do these documents belong to the same person?” Result: Request for Evidence, 2-8 week delay, or outright rejection.

ASAP Translate, which specializes in immigration documents, reports: “Even one letter difference can trigger months of delay.” And this happens precisely when a translator didn’t mark the source error. The embassy officer thinks: “The translator made a mistake” and demands a new translation.

Date Discrepancies: Universities Refuse Enrollment¶

When submitting to universities, even small errors can trigger rejection.

For example: your birth certificate shows “15.03.1986” but your passport shows “15/03/1985”. Which is correct? If the translation doesn’t flag this discrepancy, the university grows suspicious - is this a translator error or a document error?

In some countries (like the Netherlands), such mismatches require additional verification before admission. Some universities simply reject applications to avoid risk.

Global Consequences: Million-Dollar Cases¶

If you think a document error is trivial, look at real court cases where translation mistakes cost millions.

Everyone knows Willie Ramirez (USA, 1980s). An 18-year-old fell unconscious. The ER doctor, not speaking Spanish, used a random interpreter. The mother said: “My son has bad reactions to medications.” The Spanish word “intoxicado” means “adverse drug reaction,” but the interpreter translated it as “intoxicated” (drunk).

The doctor treated the boy for a drug overdose. The boy actually had a brain hemorrhage. Result: permanent paralysis and a $71 million settlement. One word cost millions.

Or Occidental Petroleum vs. Ecuador - mistranslated Ecuadorian court documents allegedly cost Ecuador a $1.77 billion tribunal judgment. For translation errors.

These are extreme cases. But they show: translation accuracy isn’t pedantry. It’s the foundation of justice systems.

Why You Can’t Just “Fix” Errors¶

Now let’s explain why, even when an error is obvious, you shouldn’t correct it in an official translation.

First reason: it’s your certification. An official translation certifies: “I translated exactly what’s in the source.” If you start “correcting” the source, you break that certification. The embassy officer thinks: “If the translator changed one thing, what else did they change?” Trust collapses. Your document gets rejected as “altered.”

Second reason: what looks wrong to you might be intentional. Sometimes apparent errors are features. Example: Soviet passports use archaic grammar. A modern translator thinks “That’s wrong!” But no - it’s authentic to the era. If you “fix” it, the Soviet document no longer looks authentic.

Another example: some foreign surnames have special spellings (like “Müller” with an umlaut). If your birth certificate says “Mueller” (no umlaut), and you “correct” it to “Müller,” you’ve altered the document. An embassy will catch this.

Third reason: if something goes wrong later, you’re liable. Say you corrected an error without permission. Later, the issuing authority needs to verify the original error existed. You’ll be blamed for hiding the truth. But if you marked it [sic.], you’re protected - you showed the error was in the source.

Professional Standard: Reproduce, Mark, Communicate¶

The International Federation of Translators and CIOL have established best practice. It’s three steps:

1. Reproduce the Error Exactly¶

If the source has an error, translate it as is. Even if it’s obvious.

2. Mark It with [sic.] or a Note¶

To protect yourself, place [sic.] immediately after or add a translator’s note.

3. Notify the Client¶

Before delivering, write your client: “I found an error in your original [describe]. I’ve translated it exactly as is, marked with [sic.]. Will this cause problems with your embassy or court?” This gives clients a chance to correct the original before submission.

This third step is critical. If your client says “Oh, I need to get a corrected copy from the issuing authority” - great, they have time. Some authorities (like Ukraine’s RACS or Germany’s STANDESAMT) can issue corrected copies quickly.

Error Types: Which Are Most Critical¶

Not all errors are equal. Some are minor typos. Others can cause serious problems.

Critical Errors:¶

Names and surnames - spelling inconsistencies between documents. Embassies are extremely sensitive here. If your passport says “Petrenko” and birth certificate says “Petrenko” (different letters), immigration officers flag it immediately.

Birth dates - even one reversed digit. 15.03.1985 vs. 15.03.1986 - these are different people to immigration systems. USCIS rejects documents with date mismatches as Requests for Evidence, adding month-long delays.

Document numbers - ID, passport, driver’s license. A number error means the document won’t verify.

Less Critical But Noticeable Errors:¶

Spelling mistakes - “Smth” instead of “Smith,” “Iván” instead of “Ivan”. Visible, but often explained as typographical errors.

Archaic grammar - in older documents, some language forms sound “wrong” to modern readers. But they’re authentic to that era. Don’t “fix” these.

Misplaced words - when the original author reversed word order. Mark with [sic.] and translate as is.

Real Scenario: What Professional Translators Do When They Find an Error¶

Here’s what should happen when you discover an error:

Scenario 1: Minor Spelling Mistakes¶

Your client submits a birth certificate with “Djohn” instead of “John”.

Step 1: Translate as is.
Step 2: Mark [sic.] - “Djohn [sic]”.
Step 3: Write your client: “Your birth certificate says ‘Djohn’. Is this a spelling error or a variant spelling? If it’s a mistake, you should get a corrected certificate before submitting documents to the embassy.”

Your client replies: “Oh, it’s an error - I’ll get it corrected.” Problem solved. If they say “Keep it as is,” they’re aware of the error, and responsibility shifts to them.

Scenario 2: Discrepancies Between Documents¶

Passport says “Mohammad Ali” but birth certificate says “Muhammad Ali”.

Step 1: Alert your client to the discrepancy.

“Your documents have an inconsistency: your passport says ‘Mohammad,’ your birth certificate says ‘Muhammad.’ Embassies flag these. Before you submit, confirm which spelling is correct.”

Step 2: Translate both versions as they appear, marking each with [sic.].

Step 3: Add a translator’s note to the translation:

Translator’s note: The spelling of the given name differs between documents (see passport vs. birth certificate). Both versions are translated as they appear in the original sources.

This gives the embassy officer all needed context. They see the discrepancy - but they also see you noted it, not hid it.

Scenario 3: Errors That Affect Meaning¶

Birth certificate reads: “Document issued 15 years” instead of a date.

The error distorts meaning! Still, translate as is with [sic.]. But add an especially clear note:

Translator’s note: The original reads “issued 15 years” (possibly a typo). The translation reproduces the source text exactly as written.

Or better - ask your client: “This phrase doesn’t make sense. Are you sure you should submit this document as is? You might want to request a corrected copy from the issuing authority first.”

Translator’s Checklist¶

Whether you’re self-translating or hiring a translator, use this checklist:

• [ ] I’ve read the entire document and identified errors
• [ ] For each error, I’ve decided: [sic.], translator’s note, or client consultation
• [ ] If the error could cause problems (name inconsistencies, date mismatches), I’ve notified the client BEFORE submission
• [ ] I’ve added a translator’s note if necessary
• [ ] I’ve re-read for accuracy - errors are marked, notes are clear, translation is faithful
• [ ] The client is aware of errors and agrees with my approach

One Exception: When You CAN Correct¶

There’s one important exception: if this is NOT an official translation but an informal working translation (not for embassy, court, or notary submission), you can discuss corrections with your client.

Examples: - Internal company documents - Translation for personal understanding - Translation not meant for official submission

In these cases, you could offer: “Would you like me to correct these errors for readability? I’ll note what I changed.”

But even here: always communicate, always mark, always protect yourself.

How ChatsControl Helps with Error-Prone Documents¶

If you use ChatsControl for document translation, the platform includes automated “QA Check” - it automatically flags potential errors:

• Name inconsistencies across documents
• Incorrect dates or formats
• Missing values in numeric fields
• Document number mismatches

When you upload a document, ChatsControl analyzes it and gives you a list of potential issues. You then decide: 1. Real error? Mark with [sic.] 2. Discrepancy across documents? Notify client before delivery 3. AI error? Fix manually before submission

It’s an efficient way to catch problems before they cause embassy delays.

Quick Takeaways by User Type¶

If You’re a Professional Translator:¶

1. Official translations - reproduce errors exactly, mark [sic.], add notes
2. Always communicate - notify clients about discovered errors
3. Protect yourself - [sic.] markings and notes shield you from quality accusations
4. Follow standards - adhere to CIOL/FIT professional guidelines

If You’re Submitting Documents:¶

1. Ask for error flagging - request your translator mark all errors
2. Verify discrepancies - if your documents have inconsistencies (names, dates), clarify with the issuing authority before submission
3. Expect translator’s notes - your translation should explain source errors
4. Keep originals - retain copies to prove errors were in the source

If You’re a Notary:¶

1. Check for notation - ensure errors are marked [sic.] or noted
2. Understand your role - you certify translation accuracy, not source accuracy
3. Educate clients - explain the difference between translator errors (their problem) and source errors (client’s problem)

Common Questions¶

The embassy rejected my translation saying “translator error.” But it’s actually in the original. What now?

Check whether the translator marked the error with [sic.]. If not, request a new translation with proper notation. If the translator did mark it but the embassy missed it, request the embassy reconsider - provide the original alongside the marked translation.

Won’t my translation look bad with hundreds of [sic.] marks?

No - it looks professional. Embassy officers think: “The translator knew about these errors and flagged them. This is reliable work.”

My translator charged €50/page and the translation has errors. Can I demand a redo?

Depends on error type. Errors in the original (marked [sic.]) aren’t the translator’s fault. Errors the translator didn’t mark with [sic.] ARE the translator’s fault. Demand revision with proper notation, or request a refund.

Remember: An error in a document isn’t a disaster if you know how to handle it. [sic.] marks, translator’s notes, clear communication - these are your tools. They protect both you and the person submitting documents.