The example is made up. Marisol is an HR consultant at Brookfield People Partners, and her client Harbor & Pine Foods needs its remote work policy in Spanish for its staff. The lesson is a practice copy of DeepL built from its public help center in October 2026 and not tested in the real app, so your screens may look a little different.
What are the most common DeepL translation mistakes?
| # | Mistake | Fix |
|---|---|---|
| 1 | Pasting text instead of translating the file | Use Translate files |
| 2 | The wrong target language | Open the target language box and check it |
| 3 | The default tone on a policy | Set the tone to Formal |
| 4 | Skipping the layout check | Open the downloaded copy before you send it |
| 5 | No fluent reader | Have a fluent speaker read it before staff do |
| 6 | Accepting DeepL Write edits blind | Turn on Show changes |
| 7 | Uploading without checking the rules | Check your firm's and client's rules first |
Which mistakes happen before you translate?
1. Pasting text instead of translating the file. This is the costly one. The lesson's business case puts it in numbers (example numbers, so use your own): about 90 minutes a document when you paste, translate and rebuild the layout, against about 20 minutes when the whole file is translated and the job is the check. In DeepL, click Translate files, then click the upload area and select the file, or drag it into the window. DeepL's help center says file translation keeps the original formatting, images and fonts.
2. The wrong target language. After you select the file, click the target language box and choose the language your readers use. The lesson's list includes English (American), French, German, Portuguese (Brazilian) and Spanish. Variants matter: if a language has more than one option, pick the one your readers expect. The translate button then names it: Translate into Spanish.
3. The default tone on a policy. A document from an employer should read formally. The lesson sets the tone to Formal before translating. A casual tone in a policy can read as careless, or as less binding than it is. DeepL's help center says you can also choose a glossary or a language model; the lesson leaves the glossary at None.
Try it free, step by step
DeepL: Translate a Client Document and Keep Its Formatting. Translate a client's Word policy into Spanish with DeepL file translation, keep its headings and table, set a formal tone, then polish the English cover email with DeepL Write. You do every step yourself in a practice copy of DeepL, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts.
Start the free lessonWhich mistakes happen after you translate?
4. Skipping the layout check. The lesson's preview shows the same title and table in Spanish, and the copy downloads as Harbor-Pine-Remote-Work-Policy ES.docx. But DeepL's help center notes that differences in word length can shift the layout, and Spanish runs a little longer than English. Open the downloaded file and look at every heading, table and page break before it goes anywhere.
5. No fluent reader. This is the step people skip because the translation looks good. The lesson's finish screen is clear: have a fluent speaker read anything staff will rely on, especially policies and contracts. A wrong word in a policy can change what staff think they are allowed to do. In the lesson, Marisol's cover email asks the client for exactly this: someone on their team who speaks Spanish reads it before it is sent to staff. That reader is human in the loop, placed where the risk is.
What goes wrong with DeepL Write?
6. Accepting edits blind. DeepL Write improves text in the same language. In the lesson, Marisol pastes a rough English email into the left-hand box; DeepL detects the language and shows an improved version on the right. Before copying it, click the Show changes toggle to see exactly what changed, so you agree with every edit. In the lesson the changes are small (a capital letter for Spanish, a question mark, "I've attached") and the meaning stays the same. If an edit changes your meaning, don't take it. DeepL's help center says you can pick alternatives for words or whole sentences. Then click the copy icon and paste the email, with the translated file attached.
Don't confuse the two tools: the Translator changes the language, and Write keeps the language and improves the wording.
What about confidential documents?
7. Uploading without checking the rules. A client's HR policy is the client's document. The lesson's module page says to check your firm's and your client's rules before you upload confidential documents to any online tool. If you are unsure what counts as confidential, the AI data classification lesson walks through sorting it, and Safe AI at work covers the everyday habits. Plans and file limits differ, so check DeepL's plans page too.
Key takeaways
- Translate the file, not pasted text, so the layout survives.
- Check the target language and set Formal for policies.
- Open the downloaded copy: translated text often runs longer.
- A fluent speaker reads anything staff will rely on.
- In DeepL Write, turn on Show changes and agree with every edit.
- Check the confidentiality rules before you upload a client's document.
The DeepL document translation FAQ answers the how-to questions, and the DeepL glossary entry explains the tool in a paragraph.
Frequently asked questions
- Can DeepL keep tables and headings?
DeepL's help center says file translation keeps the original formatting, images and fonts. In the lesson the title and the table come through in Spanish. Word length can still shift the layout.
- Is a DeepL translation good enough for a contract?
Treat it as a draft. The lesson says to have a fluent speaker read policies and contracts before anyone relies on them.
- Do I need a DeepL account for the lesson?
No. It is a practice copy. No file is uploaded and no DeepL account is touched.
- Can I use DeepL Write on the translated Spanish text?
DeepL Write improves text in the same language. The lesson uses it only on the English cover email, so check DeepL's own help for the languages it supports.
