8 Audit Steps Compliance Teams Must Show for ISO 18587 Requirements
ISO 18587 sets requirements for the process of full human post-editing of machine-translated content and the competences post-editors must hold. It applies only to content that has passed through a machine translation (MT) system, and it targets language service providers, their clients, and individual post-editors. The standard does not certify MT engines; it certifies the documented process wrapped around them, and it typically works alongside ISO 17100 rather than replacing it.
Table of Contents
What Is ISO 18587? Scope and Definitions
ISO 18587:2017 covers one specific activity: full, human post-editing of output from an MT system. It does not apply to translation produced entirely by humans, and it does not apply to unedited raw MT output. The scope split matters because clients often ask for “post-editing” without specifying which kind they mean, and the two kinds have different deliverables entirely.
The standard distinguishes two outcomes:
Full post-editing — the edited text must read as if produced by a human translator, matching the quality bar ISO 17100 sets for style, grammar, and terminology.
Light post-editing — the edited text only needs to be accurate and comprehensible; stylistic polish is explicitly out of scope.
ISO 18587 governs full post-editing specifically. Light post-editing is mentioned in the standard’s definitions but is not the process it sets requirements for. Translation service providers (TSPs), post-editors, and the clients commissioning MTPE work are the three parties the standard is written for.
Post-Editor Competence: Records Auditors Will Ask For
An auditor reviewing ISO 18587 compliance is not looking for a polished mission statement. They want proof, in the form of records, that specific people are qualified for specific jobs. That distinction between having a policy and having records is where most gap assessments run into trouble.
The standard requires documented competence in four areas:
Translation competence — demonstrated ability to produce a target text equivalent to source content.
Domain and linguistic competence — subject-matter knowledge and command of both source and target languages, matched to the content type assigned.
Post-editing competence specifically — the ability to assess MT output quality, decide how much correction is needed, and know when a segment should be retranslated rather than patched.
Research and technical competence — the ability to use TM/TB tools and resolve terminology questions independently.
Roles need clear boundaries too: who post-edits, who reviews, and who verifies the final file before delivery cannot be the same undocumented person by default. Each role needs an assignment log tying a named individual, with recorded credentials, to a specific project.
Pro Tip: Build a single competence matrix that cross-references each post-editor against education, years of domain experience, MTPE-specific training completed, and the content types they’re cleared for. Auditors consistently ask for exactly this document, and reconstructing it retroactively from scattered HR files is where certification timelines slip.
The ISO 18587 Workflow: From Intake to Delivery
ISO 18587 requirements for the workflow itself follow a sequence, and skipping a step is one of the more common nonconformities auditors flag.
Assess suitability before accepting the job. Not every MT output is a good candidate for post-editing. The TSP has to evaluate whether the source MT quality, content type, and turnaround expectations make MTPE viable, or whether the project needs full human translation instead.
Capture project specifications. Client instructions, target audience, purpose of the text, and any terminology constraints get documented before work starts, not inferred afterward.
Integrate translation memories and term bases. TM and TB assets get loaded and applied consistently so the MT output and the post-editor’s corrections stay aligned with existing client terminology.
Assign the right resource. Based on the competence records from the previous section, a specific post-editor gets matched to the specific domain and language pair.
Perform the post-edit. The post-editor corrects the MT output to meet the full or light post-editing target agreed for the project.
Run quality assurance. A reviewer checks the edited output against the project specification and flags any deviation.
Handle nonconformities. Anything that fails QA gets logged, corrected, and the correction gets recorded, not just fixed silently.
Deliver with a record trail. The final file ships alongside documentation showing each step above actually happened.
How ISO 18587 Fits With ISO 17100 and the Path to Certification
ISO 18587 is built to extend ISO 17100 translation requirements, not to stand alone. Operationally, that means an organization pursuing 18587 certification without an ISO 17100-aligned quality management framework already in place is usually building on a weak foundation, since MTPE competence and process controls assume the broader translation service structure ISO 17100 defines.
A practical gap review before applying for certification should check service agreements, project procedures, job descriptions, qualification records, revision workflows, and records from completed MTPE jobs.
Certification bodies typically move through four stages:
Application and scope definition — confirming exactly which services and locations the certificate will cover.
Document review — checking that policies, procedures, and job descriptions exist and align with the standard’s clauses.
Operational assessment — sampling real project files to confirm procedures were followed, not just written.
Corrective action and closeout — resolving any nonconformities found before the certificate issues.
The most common finding at the operational stage is a mismatch between what the documentation claims and what the project files actually show.
ISO 18587 Compliance Checklist for Implementation Teams
Run a formal gap review comparing current procedures against every ISO 18587 clause, using the competence and workflow requirements above as the checklist.
Write down the procedures that don’t exist yet on paper: intake criteria, suitability assessment, resource assignment logic, post-editing steps, and QA sign-off.
Assemble competence records for every post-editor and reviewer currently doing MTPE work, filling gaps in training documentation as you find them.
Run at least one pilot MTPE project end to end under the new documented process, and keep every record it generates.
Compile the audit pack from the pilot’s records and select a certification body experienced with translation-sector standards.
Pro Tip: Treat the pilot project as your dress rehearsal for the actual audit. If your own team can’t produce a clean paper trail from that single project, an external auditor won’t find one either.
Real-World Compliance Examples and Common Failure Points
A regulated technical manual translated through MTPE, with a subject-matter expert signing off before delivery, is a workable compliant pattern: suitability assessed up front, terminology locked to an existing term base, and a documented reviewer separate from the post-editor.
The failures auditors report most often cluster around three things:
No suitability assessment on file — the project just started, with no record of why MTPE was the right call for that content.
Thin competence evidence — a post-editor assigned to medical content with no domain training documented anywhere.
Weak TM/TB governance — inconsistent terminology because the term base wasn’t actually enforced during post-editing.
Operational records from real projects are what auditors weigh most heavily; a documented policy with no matching project evidence rarely survives review. The mitigations are unglamorous but effective: mandatory documented sign-off before any project starts, terminology checks built into the QA step rather than left to individual judgment, and a corrective-action log that closes out every finding with a dated fix.
ISO 18587:2017 Status and the Draft Revision to Watch
The current published edition is ISO 18587:2017, and it’s the version certification bodies audit against today. A draft revision, ISO/DIS 18587, is under development and listed on the ISO Online Browsing Platform with its own life-cycle status.
Certification issued against the 2017 edition remains valid under that edition until ISO formally supersedes it.
Organizations mid-implementation should still build against the 2017 requirements, since a DIS is a draft, not a replacement.
Once a revision publishes, certified organizations typically get a transition window rather than immediate invalidation, following ISO’s standard practice for revised standards.
Checking the ISO OBP entry periodically is the reliable way to catch a status change before it affects an audit cycle.
Mapping an AI+HUMAN Hybrid Workflow to ISO 18587 Controls
AD VERBUM’s AI+HUMAN hybrid workflow follows a sequence that mirrors what ISO 18587 asks for structurally: asset integration of client TM and TB first, LLM-based generation constrained by that terminology, subject-matter expert review for technical accuracy, then QA aligned to ISO 17100 and ISO 18587.
The requirement that matters most in practice isn’t the technology generating the draft. It’s whether a qualified human reviewer, with documented domain competence, signs off before delivery, and whether that sign-off is recorded somewhere an auditor can find it later.
For regulated content, that decision condition, documented reviewer competence plus a retrievable audit trail, is what separates an ISO-aligned procurement choice from a vendor that simply claims “human review” without records behind it.
What Actually Separates Compliant Teams From the Rest
Most organizations treat ISO 18587 as a paperwork exercise: write the policy, file it, move on. That’s backwards. The certification bodies that reject applications most often aren’t rejecting bad policies. They’re rejecting good policies with no project files behind them, which tells you the standard is really testing operational discipline, not documentation skill.
The conventional advice, “get your procedures written down,” undersells the harder part. Writing a suitability-assessment procedure takes an afternoon. Proving that every post-editor assigned to cardiology content in the last six months actually had cardiology training on file takes an actual competence-tracking system, maintained continuously, not assembled the week before an audit.
If there’s one place to start, it’s the competence matrix, not the workflow diagram. A team can post-edit competently with an imperfect workflow document. No team survives an ISO 18587 audit with brilliant workflow documentation and no evidence that the people doing the work were qualified to do it. Fix the records first. The process documentation is comparatively easy to catch up.
— Eric Brown
Getting to ISO 18587 Compliance Without Starting From Zero
Building ISO 18587 compliance from scratch, competence matrices, workflow documentation, pilot projects, and audit packs, takes months when a team is starting cold. AD VERBUM runs that structure already: an AI+HUMAN hybrid workflow with certified subject-matter experts reviewing every MTPE project, QA aligned to ISO 17100 and ISO 18587, and operations hosted on EU infrastructure for teams with data sovereignty requirements.
For organizations weighing whether to build internal MTPE compliance or work with a provider that’s already audited against it, the practical path is a gap assessment against your current volume and content types, followed by a pilot project run under AD VERBUM’s documented process before any long-term commitment. If you handle regulated content in life sciences, legal, finance, or manufacturing, get a scoped quote for multilingual localization and see how the workflow maps to your existing terminology assets.
Sources
FAQ
Is ISO Certification Accepted in the USA?
Yes. ISO standards are international, and US-based organizations routinely hold and rely on ISO 17100 and ISO 18587 certifications issued by accredited certification bodies operating in the American market.
What Documentation Do You Need Before Starting an MTPE Project?
You need a suitability assessment confirming MTPE fits the content, documented client specifications, and confirmation that TM/TB assets are loaded and current before assignment.
Is Machine Translation Post-Editing Worth the Effort?
For high-volume, time-sensitive content with strong terminology assets, MTPE under a documented ISO 18587 process is typically faster than full human translation while maintaining audit-ready quality controls; the effort pays off most clearly in regulated, repetitive documentation.
What Does MTPE Mean in Translation?
MTPE stands for machine translation post-editing, the process of a qualified human editing MT output to meet either full or light post-editing quality targets under ISO 18587.
Does AD VERBUM Follow ISO 18587 Requirements?
Yes. AD VERBUM’s AI+HUMAN hybrid workflow applies QA aligned to ISO 17100 and ISO 18587, with subject-matter expert review built into every MTPE project.
Recommended
