HumanExpert or SmartEdit? A Practical Guide to Choosing the Right WorkflowFor direct clients and translation agencies: how Alafranga's four translation workflows compare
The question we are asked most often before a project starts is some version of this: do you use AI, and if so, where exactly?
The answer depends on what you send us. We run four workflows: two fully human, two with an AI draft. The choice between them is not a matter of budget alone. It is a matter of what the document is for, who signs off on it, and what happens if a sentence is wrong.
This page sets out all four in full, so that you can select a workflow before you request a quote, and so that your own compliance and procurement records can be completed without a further round of questions.
|
▮Choosing in one minute
The document will be filed with a regulator, signed by a party, submitted as a sworn translation, or read by someone operating a machine. Choose HumanExpert Pro. No generative AI, and a second specialist checks the translation against the source.
The content must not reach any AI provider, and it will be used internally or reviewed on your side before use. Choose HumanExpert. No generative AI, one specialist.
The document is technical, repetitive, or an update to material we have translated before, and it will be reviewed on your side before use. Choose SmartEdit.
The document is high volume but carries real consequences if it is wrong, and you want a second independent human stage without the cost of two full human translations. Choose SmartEdit Pro.
If you send us content that does not match the workflow you selected, we tell you before translation begins rather than after delivery.
▮The four workflows compared
| HumanExpert | HumanExpert Pro | SmartEdit | SmartEdit Pro | |
| Best for | Confidential content that must not reach an AI provider, used internally or reviewed on your side. | Contracts, regulatory filings, medical, safety-critical and sworn content. | Technical, repetitive content and updates, reviewed on your side before use. | High-volume content that carries consequences if it is wrong. |
| Generative AI involvement | None. No generative AI is used at any stage. | None. No generative AI is used at any stage. | Yes, at draft stage only. The draft is generated through an API connection inside the CAT tool. | Yes, at draft stage only. Identical draft stage to SmartEdit. |
| Human stages | One. A specialist translator, who checks their own work before delivery. | Two. A specialist translator, then an independent reviewer. | One. A domain specialist edits every segment of the draft. | Two. A domain specialist edits every segment, then an independent reviewer checks the edited text. |
| What the reviewer works from | Not applicable. There is a single human stage. | The source text. The reviewer does not simply read the translation, but checks it against the original. | Not applicable. There is a single human stage. | The source text, checked against the edited target. |
| Named specialists per project | One. | Two, minimum. | One. | Two. |
| Standard | Produced under our quality management system, which operates to ISO 17100:2015. With a single human stage, conformity with the standard is not claimed. | ISO 17100:2015. Translation and independent revision follow the process requirements of the standard. | ISO 17100:2015 does not cover post-edited machine output, so conformity is not claimed. Translator qualification, terminology governance, QA and record keeping are those of our ISO 17100:2015 quality system. | Same position as SmartEdit. The second human stage raises the level of checking, but the origin of the text is a machine draft. |
| CAT tool | memoQ or Trados, configured per client. | memoQ or Trados, configured per client. | memoQ or Trados. The AI draft is generated inside the CAT tool through an API connection, not pasted in from a separate tool. | memoQ or Trados, same configuration as SmartEdit. |
| Translation memory | Client-specific memory, built and maintained across every project. | Client-specific memory, built and maintained across every project. | Client-specific memory, applied before the first segment is generated and enforced during human editing. | Client-specific memory, applied before generation and enforced across both human stages. |
| Terminology governance | Client glossary applied and maintained. Terminology decisions are locked for all translators on the account. | Same as HumanExpert, checked a second time at revision. | Client glossary constrains the AI draft from the first segment, and is enforced again during human editing. | Same as SmartEdit, checked a second time at review. |
| AI models used | None. | None. | GPT, Claude or DeepL, selected per project by content type and language pair. The model used is recorded in the project file. | GPT, Claude or DeepL, recorded in the project file. |
| Prompt construction | Not applicable. | Not applicable. | Prompts are built around content type, domain and client terminology, and are versioned per account. | Same as SmartEdit. |
| Where your content is processed | Inside the CAT tool and our project system only. No content is sent to an AI provider. | Inside the CAT tool and our project system only. No content is sent to an AI provider. | Source segments are sent to the selected AI provider through a business account under which the provider does not use the content to train its models. A current list of AI sub-processors and their retention terms is available on request. | Same as SmartEdit. |
| Checks before delivery | Terminology, numbers and formatting, checked by the translator and through automated QA. | Terminology consistency, numerical accuracy, formatting and fidelity to the source, carried out by the independent reviewer. | Terminology, numbers and formatting checked centrally across all files in the project before delivery. | Central checks plus the independent review stage. |
| Speed | Standard. One full human stage. | Slowest. Two full human stages. | Fastest on volume. The draft stage removes most of the first pass. | Between SmartEdit and HumanExpert Pro. |
| Cost | One specialist fee. | Highest. Two specialist fees. | Lowest on repetitive and high-volume content. | Between SmartEdit and HumanExpert Pro. |
| Sworn translation | Not available. Sworn work requires independent revision. | Available. Required for sworn translation. | Not available. | Not available. |
| Regulatory filings | Not recommended. Regulatory content goes to HumanExpert Pro by default. | Default workflow. CE technical files, medical device documentation, pharmaceutical files, KVKK, BDDK, SPK and EPDK submissions. | Not recommended. | Only where you have carried out and recorded your own assessment. |
| Safety-critical documentation | Not recommended. | Default workflow. Machinery manuals, operating and safety procedures, hazardous materials documentation. | Not recommended. | Assessed case by case, in writing, before we accept the project. |
| Language pairs | Every pair in our active network. | Every pair in our active network. | European, Middle Eastern and Asian pairs where draft quality meets our standard. Where it does not, we switch to a human workflow and tell you why. | Same pairs as SmartEdit. |
| When we propose a change | When the content turns out to be legal, regulatory or safety-critical, we recommend adding independent revision. | When volume and terminology stability make an assisted workflow sensible, we say so. | When the content becomes legal, regulatory or safety-critical, we stop and tell you before translation starts. | Same as SmartEdit. |
▮When independent revision is required
Independent revision is on by default for contracts, regulatory submissions, safety-critical documentation, and medical and pharmaceutical content. It can be removed only on your written instruction. For sworn translation it cannot be removed.
▮The same in all four workflows
Some things do not change with the workflow you choose. These apply to every project we accept.
- Your own experts contribute directly. Your engineers, lawyers or product specialists can record terminology decisions with us. Once recorded, those decisions apply automatically to every later project on the account.
- Repetition and match discounts. Applied against the human stages in all four workflows. There is no separate per word charge for AI output.
- Project records. All work runs on our own installation of ]Project Open[, hosted inside the EU and in continuous use since 2009. Records show which specialist handled which file and when, and for the AI-assisted workflows they record the model used.
- Named specialists. The identity and qualifications of everyone who worked on your project are available to you on request.
- Written declaration of AI involvement. A signed statement naming the workflow used, and therefore whether generative AI was involved, is issued with delivery on request. It can be set as standard for your account.
- Confidentiality. A non disclosure agreement is standard on every project, and applies to every specialist assigned to it.
- Working inside your systems. Where you require us to work in your own tools, we do so under your access controls and your retention rules. Tell us at quotation stage.
- Work for other language companies. All four workflows are available under your brand, inside your tools, with a non disclosure agreement as standard.
▮For your supplier records
Corporate buyers now keep a written record of where AI sits in their supply chain. The four statements below are written to be entered directly into that record. If your form asks a question these statements do not answer, send it to us and we will answer it in writing.
|
HumanExpert
|
|
HumanExpert Pro
|
|
SmartEdit
|
|
SmartEdit Pro
|
▮Questions We Hear Before Every Project
- Can you guarantee in writing that no AI was used? Yes, for HumanExpert and HumanExpert Pro projects. We issue a signed statement naming the workflow and confirming that no generative AI was involved. This can be set as standard for your account so that it arrives with every delivery.
- What is the difference between HumanExpert and HumanExpert Pro? The independent reviewer. In HumanExpert, one specialist translates and checks their own work. In HumanExpert Pro, a second specialist checks the translation against the source text. Choose HumanExpert for confidential content you will review yourselves, and HumanExpert Pro wherever the text will be filed, signed or relied on without further review.
- Which workflows conform to ISO 17100? HumanExpert Pro. ISO 17100:2015 requires translation followed by independent revision, and it does not cover text produced from machine output. HumanExpert has a single human stage, and SmartEdit and SmartEdit Pro start from a machine draft, so conformity is not claimed for them. All four run under the same quality management system, with the same vetted specialists and terminology controls.
- Which AI models do you use, and can I exclude one? GPT, Claude and DeepL, selected per project by content type and language pair. You can exclude any provider on your account, and we will record the restriction so it applies to every future project without you having to repeat it.
- Does my content train anyone's AI model? No. AI drafts are generated through business accounts under which submitted content is not used for model training. The current list of AI sub-processors and their retention terms is available on request.
- Can I switch workflows during a project? Yes, before translation starts, and we will tell you what changes in price and delivery date. If the content turns out to be legal, regulatory or safety-critical, we raise it ourselves rather than continuing on the workflow you first selected.
- Do you offer these workflows to other language companies? Yes. All four run under your brand, inside your tools, with a non disclosure agreement as standard. We work in more than forty languages; Turkish is our founding language, active since 2002. read more..
- Not sure which one your content needs? Send us a sample file and tell us what it will be used for. We will tell you which workflow applies, and if it is the more expensive one, we will explain why. Send a sample file