Five es­sen­tial tips for a smooth trans­la­tion workflow

Back in Ja­nuary we shared five es­sen­tial tips for pro­du­cing a fluent and na­tural translation.Today we have five more tips to ensure that your trans­la­tion really hits the mark with rea­ders, that we can de­liver quickly and that you are fully satisfied.

Have you ever thought: “This won’t take long to trans­late” or “Let’s just use AI on this”?
Ge­ne­rally spea­king, it’s not all that easy 😉
A good trans­la­tion doesn’t happen by chance – it’s the result of a cle­arly struc­tured work­flow, careful pre­pa­ra­tion and cle­arly de­fined pro­ject parameters.

1. Our trans­la­tion levels: trans­pa­rent and struc­tured – the choice is yours

We offer four trans­la­tion levels: MTPE[1], CORE, EXPERT and PRE­MIUM. You choose the level de­pen­ding on how you intend to use the trans­la­tion. If an AI or ma­chine trans­la­tion al­ready exists, we highly re­com­mend human post-editing. For in­ternal work do­cu­ments, our CORE level trans­la­tion, car­ried out by a human trans­lator, is suf­fi­cient. At the other end of the spec­trum, EXPERT level com­plies with DIN stan­dards with two people working on the text – one trans­lator and one pro­ofreader. For chal­len­ging con­trac­tual do­cu­ments or mar­ke­ting texts, the best choice is PRE­MIUM; here, three spe­cia­list trans­la­tors ensure that the trans­la­tion is ac­cu­rate and authentic.

2. Tone: target group and re­gister – it’s up to you

Should the tone of your trans­la­tion be formal or in­formal? Who is the in­tended target group? Where will the trans­la­tion be used? What is its pur­pose? Let us know and our teams will adhere to your spe­ci­fi­ca­tions.
The more we know about the re­gister, in­tended use and the target group, the better your trans­la­tion will be. The de­sti­na­tion country is also key. Just think about the dif­fe­rences bet­ween US and UK Eng­lish or bet­ween Eu­ro­pean Spa­nish and Latin Ame­rican Spa­nish! In both cases, the “same” lan­guage is often used quite dif­fer­ently. There are cer­tain de­tails that may seem small, but are cru­cial to get right when it comes to the au­then­ti­city of the trans­la­tion and the im­pres­sion it makes. Lan­guage con­veys in­for­ma­tion, but how it does so all de­pends on the context.

3. Ter­mi­no­logy: de­fined and ad­apted – here we need your input

Some terms should not be trans­lated; others, ho­wever, must comply with cle­arly de­fined com­pany gui­de­lines or cor­po­rate lan­guage.
Send us your style guides, ter­mi­no­logy gui­de­lines and/or re­fe­rence files so that our trans­la­tion teams know how to ap­proach your texts. Please also let us know if we should strictly adhere to your glos­s­a­ries or if you are open to al­ter­na­tive sug­ges­tions. This allows us to ensure con­sis­tency with your con­tent ma­nage­ment. Today it is stan­dard prac­tice to store ter­mi­no­logy in CAT[2] tools and ar­chive both the source and target texts where pos­sible. We kindly ask that you let us know of any ch­anges you make in-house to the trans­la­tion – then we can update our sys­tems and ensure that the next trans­la­tion re­mains consistent. 

4. Basics: pro­ject pa­ra­me­ters and in­for­ma­tion – what we need from you

In order to pro­vide you with a quote, we need a contact person and all their de­tails. This allows us to com­mu­ni­cate ef­fi­ci­ently and clear up any po­ten­tial mi­sun­derstan­dings as soon as pos­sible. Please pro­vide us with a te­le­phone number in case we need to call you with a quick ques­tion. We also need all the im­portant in­for­ma­tion such as de­li­very date, de­tails re­gar­ding the scope of the pro­ject, language(s) and format re­quired as well as any ne­ces­sary NDAs. You can also keep it simple and just send us the text for trans­la­tion so that we can pro­vide you with a quote. If you accept our quote – which, of course, we hope you will! – we also need an order number (if ne­ces­sary) and your bil­ling address.

5. Feed­back: app­re­ciated and valued – let us know

Once your pro­ject is com­pleted, we’d love to hear your feed­back – wha­tever it may be. Only then can we get (even) better, fur­ther op­ti­mise our pro­cesses and tailor future pro­jects more clo­sely to your needs. These are the stan­dards we set for ourselves.

Con­clu­sion
A suc­cessful col­la­bo­ra­tion for ex­cel­lent trans­la­tions begins long before the first word has been written. With the right in­for­ma­tion, we can create a basis for ac­cu­rate, sty­li­sti­cally ap­pro­priate texts that are tail­ored to your target group – pro­fes­sio­nally im­ple­mented with no nasty surprises.

Now it’s your turn 👇
Was this in­for­ma­tion useful? Is there any­thing you may have over­looked when plan­ning a trans­la­tion pro­ject? What has worked par­ti­cu­larly well for you? We’d love to hear your feedback! 😊


[1] Ma­chine Trans­la­tion with Post-Editing

[2] Com­puter Aided Translation


Leave a Reply

Your email address will not be published. Required fields are marked *