O que faz com que os prazos de tradução sejam perdidos?

If the project scope isn't well defined or reference material is missing, it will take some time to communicate about it. If the translator starts working right before the deadline, hoping that the project scope is defined and the reference materials are there. When that's not the case, extra communication is needed, sometimes with several follow ups. If the client and the translator are in very different time zones, that makes it even more challenging.

Clients may set unrealistic expectations for the daily capacity of high-quality translation, leading to rushed work and revisions. Overlooking translation needs in project schedules forces translators into tight timelines. Late delivery of essential reference materials disrupts workflow, requiring revisits to completed sections. Frequent, untracked changes in source documents necessitate continuous adjustments, impeding progress. Translators' lack of preparation, such as not fully understanding the document context or poor terminology management, can lead to inaccuracies. Lastly, poor quality of source documents, both linguistically and technically, can extend translation time.

Based on my experience projects get into trouble in most cases because of unrealistic deadlines which is tantamount to forcing translator to trade quality for time. Moreover, project terms should set clear conditions for any changes or additions to content. Samples from the content should be thoroughly reviewed to ensure reasonable quality of the source material.

Poor organization skills, but also underestimating the scope of the work and pressure from clients, who have no idea how long it takes for quality work to be done.

Translation deadlines can be missed due to various factors, including complexity of content, insufficient resources, high workload, unexpected changes or revisions, poor communication, technical issues, quality assurance, cultural nuances, unexpected events, and inadequate planning. To mitigate these risks, it's crucial to conduct thorough project planning, allocate resources, maintain open communication, anticipate potential challenges, and regularly update the project's progress.

Queries or the client's response to them are always a reason for delays in the project process. Especially in projects with several target languages, late questions and long waiting times for answers, which then have to be taken into account in all target languages, are a high risk for meeting deadlines.

Once I had a client who needed a translation. He contacted me and I said I would take a look at the file and let him know. The problem is that he assumed "take a look at the file" meant translate the file, when in fact, I meant "give you a quote on the file". So an easy misunderstanding really, especially when we work with large multilingual teams, who may not speak English as a first language. The solution is simply to improve communication. This is the responsibility of both sides, the translator and the client.

In translation projects, shifting from a linear to a concurrent workflow, where multiple translators and reviewers work simultaneously, can significantly reduce delays. This approach, however, requires robust communication to avoid miscommunication risks. Translators play a crucial role in flagging potential linguistic, technical, or personal issues early on. Despite professional standards, translators sometimes disengage unexpectedly when faced with challenges, leading to delays. Therefore, establishing clear communication channels, setting explicit guidelines, and having contingency plans are essential. This ensures that even if individual contributors face obstacles, the project continues smoothly.

In my experience I have faced numerous situation where it was lack of contact from the client side that caused the delays. Whether it is an external client, e.g., a company requesting translations from an LSP, or an internal client, e.g., a Game Designer requesting translations from the Localization team, it is essential to remember that the communication is hardly ever limited to sending documents at the beginning of a project and collecting translations at the end. Considering the contextual nature of languages, there will be multiple situations where certain questions need to be answered in order for the translators to be able to aptly convey the message present in the source text. Responsiveness brings benefits to both parties.

Cuando las traducciones versan sobre temas técnicos es muy importante que exista una colaboración cercana entre el autor del texto en el idioma de origen y el traductor. Si bien todo uso del idioma tiene matices que son propios de países y regiones, cuando se trata de lenguaje técnico, acertar en la elección de las palabras y las expresiones resulta una labor más crítica. Esto sólo se logra con la participación del autor, quien puede definir cuál acepción de un término técnico es la más precisa para que el traductor pueda escoger la mejor opción en el idioma de destino.

Quality is so subjective, because translation is intangible and every individual will have different quality preferences especially when quality paired with time and/or budget. We have had a case where two companies (one was a local and the other an overseas team – both were Azerbaijani nationals) were co-implementing a project and the unit rates were different. We usually assigned the same translator and editor for that project due to linguists' qualifications. After each delivery, the local team would call you on Saturday 9pm to complain while the intl. team were praising the quality (and requesting to assign the same linguists every next time). So it is important if client clearly tells what they need and provide the necessary tools.

Quality assurance (QA) is vital in translation, essential for ISO 17100 compliance. Clients often underestimate the time needed for proofreading, reviewing, and editing, leading to unrealistic deadlines. Despite technological advances, thorough QA remains a time-intensive, human-centric process. Language Service Providers (LSPs) must be given adequate time to ensure accuracy and responsibility in their work. An in-house QA team, collaborating closely with the Workflow Management team, greatly enhances translation quality. Project Managers (PMs) are also crucial, as they understand clients' specific needs and ensure translations meet these requirements. This comprehensive approach is key to achieving high-quality, consistent translations.

Well, for me, quality is the most important step. The translator should first thoroughly study the project and define the scope. Even if there are proofreaders who will revise the translation, the translator has to deliver a perfect copy to the customer. If the project is well studied, we should not worry about missing deadlines, and there should always be a plan B in case the translator missed the deadline due to proofreading or revision. This should all be discussed with the client before the beginning of the project.

An unrealistic deadline always brings low quality, whether it is given more or less time. Time and quality should be on a parallel axis.

Review, editing, proofreading, and checking the document for the nuance of the language often need additional time to ensure quality and consistency. Consistency of the writing style and terminology used is vital for the professional look and feel of the translated document. While committing to a deadline, keep some buffer time for these tasks from a QA perspective.

The complexity and difficulty of translation projects, especially legal and scientific texts, directly impact deadlines. Formal texts require precision and more time, while informal texts can be quicker to translate. The text's purpose and target audience also determine the effort needed. Not all texts are suitable for division among multiple translators due to the need for consistency. Specialized translations typically involve a three-stage process: translation, review, and editing/native proofreading, each adding to the overall timeline. Properly assessing these elements ensures resources and time are allocated effectively, maintaining quality while adhering to deadlines.

From my experience in the gaming industry I can tell that complexity indeed plays a crucial role in assessing the time needed to complete translation or localization projects. This is due to the fact that different approaches are required to translate complex media that video games truly are; there are narrative elements that require literary translation skills, there are instructions that require more technical approach, there are UI elements that have certain character limits and need to be as intuitive as possible, and that is not all. This makes it difficult to come up with system solutions that speed up the work, because each game element can pose different challenges and needs individual thought.

Estabelecer uma equivalência de termos técnicos (seja termos jurídicos, científicos ou de certa indústria) entre idiomas por vezes é uma das tarefas que toma mais tempo dos tradutores. Não se deseja jamais reinventar a roda, mas a depender do nicho em que se está a trabalhar, há a possibilidade de sua opção de tradução se tornar um termo usado amplamente pela indústria - daí a necessidade do tradutor quanto a investir tempo adequado na pesquisa acerca do domínio de conhecimento que se intenciona traduzir, tanto no idioma de origem como no idioma alvo da tradução.

Complexity and difficulty take a great piece in the overall quality. On top of what is given in the description, we have had a project where the availability of terminology was the main issue. The material was too technical, with a lot of telecom terminology that were missing alternatives in the target language, since the material was introduced to the local public for the first time in life. We used a 3rd language to cross-reference the terminology after the client failed to provide us with any hints – the discipline was new to them too (i.e. they needed it to study and to deploy the same standards domestically). After clearly analyzing & aligning the initial glossary and the files with client, we could built an internal glossary for them.

La tecnología es nuestra mejor aliada para ser más eficiente pero a veces la carga el diablo y un posible problema técnico de última hora puede provocar un retraso en la entrega de un traducción. Para evitarlo, debemos: 1. Planificar bien el tiempo que tenemos para traducir, marcarnos un calendario asumible. 2. Verificar todas las actualizaciones de software. 3. Exportar cada día el proyecto en el punto hasta el que hayamos avanzado. 4. Tener siempre copias de seguridad. Siguiendo estos pasos minimizaremos el impacto que un problema técnico pueda causar.

For technical issues regarding translations it is worth to mention the role of internationalization. Internationalization is about preparing your software of product for translation by, for example, allowing different alphabets, adjusting time and date formats or designing it in a way that allows longer or shorter text (as the length changes during translation.) By doing that beforehand, companies are able to save significant amounts of time and labour needed to address these issues later on when the product is ready. Products that are not internationalized tend to look unprofessional and unfinished, because there are single untranslated words, texts going out of buttons or getting so small that they are ineligible.

Absolutely, technical itches can cause translation delays. While some are are inevitable, some others could be avoided. I learned my lesson regarding this in a bitter way that I will never forget. Imagine having spent all day working on a huge brief and carefully ensuring that the file is being auto-saved as you go. Only for you to realize at the point of delivery that your work is no where to be found. Just imagine sweating so hot at the peak of winter. Something like that. Not funny, right? Yes, I was there. The antidote is to always back up your seemingly saved file in multiple devices. That way, you save yourself the embarrassment of missing deadlines and losing your client's trust especially if it becomes an habit.

The translation software we use can sometimes go wrong. It's fine if it goes wrong and spits out your file while going wrong, but sometimes, it does something like write a blank file over your existing file (and also over the backup). The only real solution for that is regular backups with file name changes and various other means.

Technical issues can be one of the reasons for missing a delivery date, especially if the linguist is working online or has electricity or internet problems. This should be avoided by having risk management plans to handle this kind of risks

Before you start with the translation job, make sure you can edit the files you got from the ordering party. Ideally you get some docx or pdf files, but some jobs require additional skills, such as extracting the text to be translated from the code. If you translate a user interface, be sure you have installed a text editor that will help you separate the text you will see on the screen from the code that is not visible and shouldn't be translated.

Unexpected events, even force majeure are of course not limited to the translation industry and while they cannot be projected at full, any project needs to have a critical path defined, which accounts - to the degree possible - for unforeseen factors. It will never be perfect, and trust, transparency and honesty are key, however reducing the risk as early on as possible aids with consistently achievable objectives across projects.

Here's a funny one about unexpected stuff. A translator we worked with was running out of time, and then "luck" came to him in the form of a meteorite falling near his town. He told us the meteorite stopped him from delivering the job on time. We figured he simply didn't manage time properly, but luckily, we had a time reserve and extended his deadline to the next day. Lesson learned: no one is immune to unforeseen events, but always have a time reserve just in case.

Comme cela est si bien défini, un cas de force majeure n'émane de la volonté de personne. une communication franche avec le client pour exprimer le cas de force en vue d'un moratoire s'avère nécessaire.

In any project, and translation is no exception, unexpected events jeopardize timely delivery. In translation, a team member fells sick, or a power outage occurs in the office, or a technical mishap occurs to the computer, and the client should expect delay. Any disruption to the work flow will definitely affect timely delivery.

Technical issues sometimes pushing to missing of translation in time needed. We must make sure there's no technicality issues in our daily translations. Thanks you for your inviting Jimmie True-man

Missing a deadline is closely related to skills: 1. Lack of proactiveness: Having or creating a buffer time before accepting a project for any unexpected events. 2. Lack of problem-solving skills: Being able to find a solution with a plan B or plan C when things are not going as expected. 3. Lack of determination and prioritization: A deadline is a target; you have to reach it by prioritizing your tasks. 4. Lack of organizational skills: The translation project should have been well studied and structured before the translator starts working on it to determine feasibility. 5. Lack of AI-translation technology skills: To use all available assistive functions of an innovative CAT Tool (e.g., BWX) to increase productivity and reduce effort.

Frequent additional changes to the original text and/or format by the client and unrealistic deadline expectations have been the main reasons for deadline misses in my experience.

Ensuring you never miss a translation deadline requires effective time management and strategic planning. These tips will empower you to ensure timely, high-quality deliveries. 1- Break down tasks into manageable chunks and prioritize them wisely. 2- Utilize project management tools to stay organized, and always allow buffer time for unexpected challenges. 3- Stick to a detailed schedule, communicate progress transparently with stakeholders, and maintain a continuous quality assurance process. 4- Focus on one task at a time to enhance efficiency, regularly review your progress, and learn from past projects to refine your approach. 5- Lastly, have contingency plans in place to tackle unforeseen obstacles.

Meeting deadline is often depends on source documents. Not clearly expressed or vague thoughts, unknown abbreviations or names, etc make translators search and waste their time.

Silly mistakes can happen. I remember once a client sent me two files with the same name (one was called "to translate" and the other "to translate (copy)". In his email the client referred to "the document". I opened and the two documents were identical. After finishing the translation of the one file the client had requested. They asked about the second file. Turns out it was only identical on page one but had some differences on pages 2-4. So the lesson is that the client should have stated that there were 2 files, not one, and also I should have checked and figured out why they were sending two files. I had just assumed it was a mistake on their part.