Start with the audience, not a language label
Who will read the text, and where? A Netherlands business audience, students and users of a consumer app need different choices of vocabulary and formality. Specify the market and whether your brand uses “u” or “je”.
For Belgian Dutch or several Dutch-speaking markets, tell us explicitly so we can confirm the appropriate expertise. Avoid assuming that a single version suits every context.
From learning content to the next website release
Share reference pages, screenshots and your preferred terminology. For software and web content, identify variables, markup and length limits that must be preserved.
- Courses, training scripts and assessment content
- Business documents and institutional communication
- Website copy, product content and interface strings
- Existing Dutch translations needing bilingual review
An agreed review and handover
We confirm the source version, translation and review scope, file format and deadline. If you have an internal Dutch reviewer, nominate one approval contact and share their preferences before the first delivery.
For recurring updates, keep the glossary and approved examples available to the team. This helps maintain a consistent voice when new pages or modules are added.
Before you brief us
A few useful answers.
Can you check an existing Dutch AI translation?
Yes. Send the English original, Dutch draft and intended use. We can assess the draft and propose bilingual review or a fresh translation if correction would be inefficient.
Will you use formal or informal Dutch?
We agree the form of address with you. Brand references and a description of your audience help determine whether “u”, “je” or another approach is appropriate.
Do you also translate from Dutch into English?
Tell us the direction and target audience in your enquiry. We assess Dutch-to-English requests separately and confirm suitable availability and scope.