The project must link the proposed term, context and customer decision while retaining the glossary version applied to each delivery.
Index
A late terminology choice may require revisions across files; centralizing a term is insufficient if the customer has not approved it.
The rule that changes the scope
The project must link the proposed term, context and customer decision while retaining the glossary version applied to each delivery.
A translation tool may manage memory; a custom portal supports external approval and tracking of blocking terminology decisions.
A term can need different alternatives by market, product or audience, so a glossary key should not be the isolated word alone. Include enough context to distinguish uses. Translation memory and customer acceptance are related but different artifacts. When commissioning, request a change applied to one product and not another; the report must identify affected files without suggesting an indiscriminate global replacement across every delivery.
Specify operational deliverables
- Present the term, usage context and suggested alternative to the customer's owner.
- Show which deliveries depend on an outstanding terminology decision.
- Keep glossary changes and the files requiring another review.
Test the exception before acceptance
In a hypothetical scenario, the customer changes a term after accepting one file; the portal must identify affected deliveries without marking everything updated.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a revised glossary and a terminology decision that changed files already prepared.