Machine translation can enter a language-service workflow at several points, but ISO 18587 scope is considerably narrower than the use of machine translation itself. For language service providers, the central question is not whether machine translation is used. It is whether the organization delivers a defined full post-editing service that meets the standard’s requirements and can demonstrate control of that service during an audit.

ISO 18587 is intended for organizations that provide post-editing of machine translation output as a professional translation service. A correct scope definition prevents two common compliance failures: claiming applicability for services that are outside the standard, and implementing requirements without defining where they apply operationally.

What the ISO 18587 Scope Covers

ISO 18587 specifies requirements for the full post-editing of machine translation output. Full post-editing means that the final target-language content is expected to meet the level of quality agreed with the client and be suitable for its intended purpose. The service is not simply a technical review of an engine’s output. It is a managed language service with defined responsibilities, competent personnel, quality controls, and documented project processes.

The standard addresses the relationship between the client, the translation service provider, and the post-editor. It establishes requirements for areas including pre-production information, project specifications, the competence of post-editors, process management, and final verification. These requirements support the delivery of post-edited content that is fit for the agreed use, whether the content is intended for publication, regulated documentation, customer communication, product information, or internal business operations.

For an LSP, ISO 18587 may apply to a dedicated machine translation post-editing department, selected language combinations, particular content types, or the organization’s complete full post-editing service portfolio. The decision depends on the services actually offered and controlled by the organization.

Full post-editing is the key boundary

The distinction between full and light post-editing is material. ISO 18587 is focused on full post-editing, not on a reduced-effort process where the objective is merely to make content understandable or usable for a limited internal purpose.

Where a client requests light post-editing, raw machine translation, or automated output without human editing, the service should not be represented as conforming to ISO 18587. This does not make those services unacceptable. It means they require their own clear service descriptions, quality expectations, risk controls, and contractual language.

An organization that offers both light and full post-editing should define the distinction in its quotations, project instructions, workflow configurations, and delivery records. Auditors will look for evidence that staff can identify which workflow applies and that full post-editing projects receive the required controls.

What ISO 18587 Does Not Cover

The standard does not certify a machine translation engine, language model, translation memory system, or other technology. It does not establish that a particular engine is accurate for every domain, language pair, or content type. Technology selection remains an operational decision that should be supported by risk-based evaluation and client requirements.

ISO 18587 also does not apply to raw machine translation output that is delivered without human post-editing. Nor should it be treated as a general quality standard for every translation, localization, interpreting, or content-authoring service offered by an organization.

This limitation matters in commercial communication. A broad statement such as “all machine translation services are ISO 18587 compliant” may be misleading if the provider delivers services outside the defined scope, uses light post-editing, or supplies unedited output. Certification and conformity claims should identify the relevant service accurately.

The standard does not replace contractual specification either. Clients still need to define intended use, language combinations, subject matter, confidentiality requirements, reference materials, preferred terminology, delivery format, and acceptance criteria. ISO 18587 provides a structured framework for managing the service, but it cannot compensate for unclear project requirements.

Defining a Certifiable ISO 18587 Scope

A certification scope statement should be concise, accurate, and capable of being supported by objective audit evidence. It should identify the post-editing service covered without implying that unrelated services or locations are included.

A typical scope may refer to the provision of full post-editing of machine translation output for specified language services. If the organization operates from multiple sites, uses remote teams, or manages projects globally, the scope should reflect the actual management system and operational control. Remote delivery does not prevent certification, but processes, responsibilities, and records must remain controlled across the organization.

Scope definition should be tested against four practical questions:

  • Which full post-editing services are offered to clients?
  • Which legal entities, offices, departments, and remote operational functions control those services?
  • Which personnel, suppliers, and technological tools are used in the workflow?
  • Which services are expressly excluded, such as raw machine translation or light post-editing?

The scope should align with sales materials, quotations, service agreements, project management procedures, competence records, and audit evidence. Misalignment is a frequent source of nonconformity. For example, if a certificate covers full post-editing but sales personnel describe light post-editing as certified, the organization has a control problem even if its production workflow is well documented.

Scope boundaries in a multi-service LSP

Many providers operate integrated workflows that include human translation, machine translation post-editing, desktop publishing, localization engineering, terminology work, and linguistic quality assurance. ISO 18587 can apply to the full post-editing portion of that portfolio without automatically applying to every service.

Where ISO 17100 and ISO 18587 are both implemented, the organization should avoid treating them as interchangeable. ISO 17100 concerns translation services more broadly, while ISO 18587 addresses the specific requirements of full post-editing of machine translation output. Shared controls may exist, particularly for competence management, client communication, confidentiality, and quality management. However, the post-editing workflow must still demonstrate the requirements that are specific to machine translation output.

A combined management system can reduce duplication, but only when procedures clearly identify the applicable standard, workflow, roles, and records for each project type.

Audit Evidence for ISO 18587 Applicability

An ISO 18587 assessment examines more than a documented scope statement. Auditors need to see that the stated scope is implemented consistently from client inquiry through final delivery.

Evidence commonly includes controlled procedures for assessing incoming requests, determining whether full post-editing is appropriate, documenting the intended purpose, and confirming the level of service requested. Project records should demonstrate that relevant instructions reach the post-editor and that changes to client requirements are controlled.

Competence evidence is equally important. The organization should define requirements for post-editors and retain records showing how qualifications, professional experience, language competence, subject-matter competence, and post-editing capability are evaluated. If external resources are used, supplier qualification and ongoing performance monitoring must support the same service requirements.

Auditors also assess whether the organization has defined the post-editing process itself. This includes how machine translation output is made available, how terminology and reference materials are controlled, how queries are handled, how final verification is performed, and how delivery is authorized. The exact documentation format can vary, but the controls must be repeatable and traceable.

Commercial and Tender Implications

A clearly defined ISO 18587 scope is particularly relevant when responding to procurement questionnaires and tenders. Buyers may ask whether an LSP offers machine translation post-editing, whether full post-editing follows ISO 18587, and whether the organization can demonstrate qualified resources and controlled quality assurance.

The strongest response is precise rather than expansive. State the certified or assessed scope, define the applicable service, distinguish it from excluded services, and ensure that the description matches the certificate and operational reality. Overclaiming creates contractual and reputational exposure, especially in institutional, regulated, and high-volume procurement environments.

Before pursuing certification, management should decide which post-editing services it is prepared to control consistently, document the boundaries, and verify that project teams apply them in daily operations. A well-defined scope does more than support an audit. It gives clients a clear basis for trusting what the organization will deliver.