Project planning and translation delivery

ASTM F2575: Agreeing Translation-project Specifications

ASTM identifies F2575-25, Standard Practice for Language Translation, as the active edition. Its public scope concerns translation-project specifications and phases, including localization and transcreation, rather than a particular numerical quality metric. ASTM public listing.

The decision this reference helps frame

Before a project begins, the requester and provider need a shared account of the intended result. This guide uses that practical question as an entry point. It does not reproduce the ASTM document or reconstruct its clauses.

A project can fail even when the target text is grammatical. The audience may be wrong, the intended use may be misunderstood, or an important deliverable may be missing. The purpose of making expectations explicit is to reduce those mismatches.

An illustrative agreement problem

A company asks for a Spanish version of a product page. The writer assumes that adapting the page includes rewriting examples for a local audience. The requester expects a close translation with all examples preserved.

Neither expectation should remain implicit. Our recommended planning exercise is to write down the audience, the permitted degree of adaptation and the person authorized to approve changes. If the team disagrees, that disagreement can be resolved before the translation is assessed.

The exercise is original editorial advice. It is not labelled an ASTM checklist, and it cannot demonstrate conformity to F2575.

Connection to other references

This is a project-specification topic, thematically connected to LISA's concern with shared practices. It should not be presented as a successor edition of a LISA standard.

Read ISO 11669 for another project-planning reference. For the separate question of how to classify findings in a translation, explore MQM. For formats used during production, see XLIFF and TBX.

AI and implementation boundaries

For an AI-assisted project, useful discussion points include permitted source material, intended output, human responsibilities and the evidence needed at acceptance. These are our suggestions for a project conversation, not claims about the contents of F2575-25.

The standard's availability for purchase does not establish permission to reproduce it, translate it for republication or place its text in an AI system. Before using proprietary documents in a tool, check the publisher's applicable access and licensing terms.

Source record

ASTM F2575-25 publisher metadata and public scope. No full paid text was obtained for this article. Official requirements and implementation details must be consulted through an authorized copy.

Back to topBack to the standards catalogue