|
HumanExpert or SmartEdit? A Practical Guide to Choosing the Right Workflow
For direct clients and LSP partners — a clear comparison of Alafranga's two translation workflows
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 three workflows. 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 three 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, or read by someone operating a machine. Choose HumanExpert. No generative AI is used at any stage.
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 three workflows compared
| HumanExpert | SmartEdit | SmartEdit Pro | |
| Generative AI involvement | None. No generative AI is used at any stage of the workflow. | 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 | 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 | The source text. The reviewer does not simply read the translator's output, but checks it against the original. | Not applicable. There is a single human stage. | The source text, checked against the edited target. (alternative wording: the edited target text, checked for terminology, numbers and consistency) |
| Number of named specialists per project | Two, minimum. | One. | Two. |
| Standards and certification | ISO 17100:2015. Both stages meet the requirements of the standard. | ISO 17100:2015 does not cover post-edited machine output, so we do not claim conformity for this workflow. Translator qualification, terminology governance, QA and record keeping are those of our certified system. | Same position as SmartEdit. The second human stage raises the level of checking, but the origin of the text is a machine draft. |
| Certification audited by | Bureau Veritas. | Bureau Veritas, for the quality management system under which the work is produced. | Bureau Veritas, for the quality management system under which the work is produced. |
| CAT tool | memoQ or SDL Trados, configured per client. | memoQ or SDL Trados. The AI draft is generated inside the CAT tool through an API connection, not pasted in from a separate tool. | memoQ or SDL Trados, same configuration as SmartEdit. |
| Translation memory | 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. | 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. | 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. | 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. | 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 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. Two full human stages take longer than an assisted draft. | Fastest on volume. The draft stage removes most of the first pass. | Between the two. |
| Cost | Highest. Two specialist fees per project. | Lowest on repetitive and high volume content. | Between the two. |
| Sworn translation | Available. A fully human workflow is required. | Not available. | Not available. |
| Regulatory filings | 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 | 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. Where machine draft quality does not meet our standard for a pair, we apply HumanExpert whatever workflow was requested, and tell you why. | European, Middle Eastern and Asian pairs where draft quality meets our standard. | Same pairs as SmartEdit. |
| When we propose a change | 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. |
The same in all three 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 three 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 three 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 three 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
Generative AI used: No, at no stage.
Human stages: Two. A specialist translator, then an independent reviewer working against the source text.
Content sent to AI providers: None.
Records: Held in Alafranga's own installation of ]Project Open[, hosted inside the EU, in use since 2009.
Certification: ISO 17100:2015, audited by Bureau Veritas.
Responsibility for the delivered text: Alafranga Europe Ltd, registered in England and Wales, company number 16711244.
SmartEdit
Generative AI used: Yes, at draft stage only. Model recorded per project. No segment is delivered without human editing.
Human stages: One. A domain specialist edits every segment.
Content sent to AI providers: Source segments only, through a business account under which the content is not used to train the provider's models. Sub-processor list and retention terms available on request.
Records: Held in Alafranga's own installation of ]Project Open[, hosted inside the EU. Model and reviewer recorded per project.
Certification: Produced under Alafranga's ISO 17100:2015 certified quality management system, audited by Bureau Veritas. ISO 17100 does not cover post-edited machine output and conformity is not claimed for this workflow.
Responsibility for the delivered text: Alafranga Europe Ltd, registered in England and Wales, company number 16711244.
SmartEdit Pro
Generative AI used: Yes, at draft stage only. Model recorded per project.
Human stages: Two. A domain specialist edits every segment, then an independent reviewer checks the result.
Content sent to AI providers: As SmartEdit.
Records: As SmartEdit, with both specialists recorded per project.
Certification: As SmartEdit.
Responsibility for the delivered text: Alafranga Europe Ltd, registered in England and Wales, company number 16711244.
Common questions
Can you guarantee in writing that no AI was used?
Yes, for HumanExpert 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.
Is SmartEdit ISO 17100 certified?
No, and we are precise about this. ISO 17100:2015 does not cover text produced from machine output. SmartEdit is produced inside our certified quality management system, using the same vetted specialists and terminology controls, but conformity with the standard itself is claimed only for HumanExpert.
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 three run under your brand, inside your tools, with a non disclosure agreement as standard. Turkish is our founding pair and remains the centre of our work, with more than forty languages available through our vetted network.
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.