The established standards in the translation field define how the work is to be carried out: which steps are applied, what competence the people doing the work must have, how records are kept. This is an important assurance, but it has a limit that is often overlooked: a standard looks at the process, not at individual texts.
Scope of the standards
Process steps and competence requirements are defined. The scope is the process. The definition is structural.
Process focus
A standard regulates how the work is carried out. It does not measure the output itself. The limit is here.
What it gives no assurance of
Compliance does not show that every job will be flawless. The assurance is misread. The expectation is corrected.
Mandatory steps
Steps such as independent revision are treated as mandatory. Skipping them breaks compliance. The rule is clear.
Competence requirements
The qualifications the translator and the reviewer must have are defined. The criteria are listed. The requirement is written.
Record keeping
Process records are required to be kept. The record is shown at audit. A routine is set up.
Resource management
Supplier selection and evaluation are regulated. Pool management is part of the standard. The scope is wide.
Client communication
Request intake and feedback processes are defined. Communication also falls under the standard. The structure is complete.
Arrangements concerning machine translation
Editing after automatic translation is treated as a separate field. The scope is defined separately. The distinction is preserved.
Declaration of compliance
An organisation may declare that it complies with a standard. The declaration must be verifiable. A basis is sought.
Independent audit
Compliance can be audited by an independent body. The audit comes from outside. Assurance increases.
Unverifiable claims
A compliance claim whose basis cannot be shown is not used. Such a statement damages trust. The limit is preserved.
Scope of certification
Certification covers the processes of the organisation. It does not cover individual jobs. The distinction is explained openly.
Reading the scope statement
Which activity a certificate covers is written in the certificate. It forms no basis for work outside that scope. The line is read.
Appearing in client specifications
Some tender and procurement specifications require compliance with a standard. The condition is read from the specification. The expectation is learned.
Cost of compliance
Compliance with a standard creates a process and record-keeping burden. The burden is marked in small organisations. The decision is weighed.
Benefit of compliance
Written processes and a record-keeping routine naturally strengthen quality assurance. The benefit is independent of the certificate. The gain is lasting.
Practice without a certificate
An organisation can apply the requirements of a standard without holding a certificate. Practice is the real value. The certificate is secondary.
The standard builds a common language
The terms of a standard provide a common language between client and supplier. Concepts such as revision are understood alike. The benefit lies in communication.
Changing versions
Standards are updated from time to time. Which version is followed is stated. The information is kept current.
The real benefit of a standard
The most concrete contribution of standards is not a promise of quality but the way they force the organisation to put its own arrangements in writing; once these are in place, the gain remains even if no certificate is obtained. The value is in the process. The certificate shows it.
Limits of the approach
Compliance with a standard is no assurance of the quality of individual jobs. Measurement and review are still needed. The limit is stated openly.