A translator’s résumé may look convincing in a supplier file, yet it is not sufficient audit evidence on its own. When a client, tender authority, or certification auditor asks how to document translator competence, the question is whether the language service provider can demonstrate a controlled, repeatable decision – not whether it can produce a collection of credentials at short notice.

For organizations working toward or maintaining ISO 17100 certification, competence documentation must show that translators are qualified for the work assigned, that the qualification was verified, and that the record remains current. The same discipline supports defensible vendor management, consistent project allocation, and credible responses to buyer due diligence.

What Competence Documentation Must Prove

Competence is broader than bilingual ability. In an ISO-controlled environment, the provider should be able to show that each translator has the knowledge, skills, experience, and subject-matter suitability required for the assigned service. Evidence must be traceable to a named individual and capable of review by an independent auditor.

A practical competence file answers four questions: Who assessed the translator? Against which defined criteria? What objective evidence was reviewed? What was the resulting approval decision, including any restrictions?

This distinction matters. A degree demonstrates an educational achievement. A positive test translation may demonstrate capability at a particular point in time. A successful project history may demonstrate relevant experience. None of these documents, separately, proves that the organization has evaluated competence under a controlled process. The provider’s approval record connects the evidence to its operational decision.

For ISO 17100, organizations commonly establish qualification routes based on translation education, other higher education combined with documented professional translation experience, or extensive documented professional experience. The exact route used should be stated in the provider’s procedure and applied consistently. An auditor will normally look for evidence that the organization has not treated self-declaration as verification.

Establish a Competence Matrix Before Collecting Files

The strongest records begin with a defined competence matrix. This is the organization’s criteria for determining whether a translator is eligible for approval and which work they may receive. It prevents supplier approval from becoming a subjective decision made differently by each vendor manager or project manager.

The matrix should distinguish the languages, service types, and subject fields relevant to the organization’s scope. A translator approved for general marketing content into US English may not be suitable for regulated medical-device documentation, legal contracts, or financial reporting. Approval should therefore identify language direction and any subject-matter limitations, rather than simply labeling the individual as an approved translator.

A well-designed matrix commonly covers translation competence, linguistic and textual competence, research competence, cultural competence, technical competence, and domain knowledge. These categories should be translated into operational criteria. For example, technical competence may require demonstrated use of the organization’s required translation environment, terminology process, and secure file-handling procedures. Domain competence may require education, verified work history, a domain-specific assessment, or evidence from prior comparable assignments.

Avoid setting criteria that cannot be administered consistently. Requiring a detailed portfolio from every external translator may appear thorough but can create gaps if no one is responsible for evaluating it. Requirements should be proportionate to risk, documented in a procedure, and supported by records that the organization can maintain.

How to Document Translator Competence in an Auditable File

Each approved translator should have an individual competence record, whether managed in a supplier platform, quality management system, or controlled electronic folder. The format is less important than completeness, access control, version history, and retrieval during an audit.

The file should begin with clear identification: the translator’s name or controlled supplier ID, contact and contractual status, language combinations, approved service roles, subject fields, approval date, and approval authority. If the person performs more than one role, such as translator and reviser, approval for each role should be recorded separately. Competence requirements differ by role, and role confusion is a frequent audit weakness.

Supporting evidence should be retained in a controlled form. Depending on the approval route, this may include verified copies of degrees or certificates, employment confirmations, a detailed professional history, reference checks, test translation results, assessment forms, and records of relevant technical or domain training. The organization should record how authenticity was checked when relying on external documents. For high-risk or high-value assignments, a documented interview or practical evaluation may provide useful supplementary evidence.

The evaluator should not merely write “approved.” The assessment record should state which eligibility route was met, what evidence was reviewed, whether the translator passed any required evaluation, and any restrictions imposed. A defensible decision might state that a translator is approved for German-to-English technical translation in manufacturing and software, subject to project-manager review for safety-critical content. That level of specificity supports correct assignment later.

A controlled status is equally necessary for rejected, suspended, or expired suppliers. Deleting a file after a negative decision removes evidence that the organization applied its own process. Retain such records according to the documented retention policy, with appropriate privacy safeguards.

Verify Evidence Rather Than Filing It

The most common failure is mistaking document collection for verification. A CV can be incomplete, an online profile can be outdated, and a certificate can be unrelated to translation competence. The approval process should require an evaluator to validate relevance, sufficiency, and consistency.

Verification can be proportionate. A lower-risk general-content supplier may require a review of qualifications, work history, and a controlled test. A specialist supplier supporting pharmaceutical, legal, or public-sector work may require deeper scrutiny of field expertise, references, terminology capability, confidentiality controls, and previous performance. The level of evidence should reflect the consequences of an unsuitable assignment.

Document the verification action itself. A dated note such as “degree reviewed against issuing institution record, translation experience confirmed through employer reference, test translation assessed by approved reviewer” is far stronger than attaching documents without explanation. It also enables a different quality manager to understand the original decision months or years later.

Where evidence is in a language the evaluator cannot reliably assess, the organization should define an escalation method. This may involve a qualified internal reviewer, verified credential evaluation, or a documented third-party confirmation. Assumptions are not an audit method.

Connect Approval to Project Assignment

Competence records only create value if project teams use them. The supplier database or assignment procedure should make approval limitations visible at the point of selection. If subject-field authorization is stored only in a PDF buried in a folder, it is likely to be missed under delivery pressure.

Project records should show that the assigned translator met the applicable language, role, and subject criteria. For routine assignments, this may be achieved through a controlled vendor-management system with approved status and coded competencies. For exceptional assignments, the project file should explain why an exception was authorized, who approved it, what controls were applied, and whether the event triggered follow-up action.

Exceptions are not automatically nonconformities. They become a compliance risk when they are informal, undocumented, or repeated without changing the underlying resourcing plan. A temporary assignment to a newly assessed specialist may be justified. Assigning an unapproved translator because no approved supplier was available is a management decision that requires documented risk control.

Maintain Competence Through Monitoring and Reassessment

Initial approval is not permanent proof of competence. ISO-based management depends on continued evaluation. Organizations should define when translator files are reviewed and what events trigger reassessment. Relevant triggers include recurring quality issues, client complaints, extended inactivity, changes in service scope, new subject-matter claims, technology changes, or evidence that credentials are no longer current.

Performance monitoring should be linked to the competence record. Quality scores, revision findings, delivery reliability, responsiveness, confidentiality incidents, and corrective actions can show whether approved status remains justified. The aim is not to create an excessive scorecard for every supplier. It is to ensure that material evidence affects approval decisions.

When performance concerns arise, record the action taken. The translator may receive feedback, additional guidance, a restricted subject-field status, temporary suspension, or re-evaluation. If competence is restored, document the evidence supporting reinstatement. This demonstrates that the organization manages supplier quality rather than simply recording failures.

Protect Personal Data Without Weakening Audit Evidence

Translator competence files contain personal data and may include sensitive identification, education, and employment information. Access should be restricted to authorized personnel, retention periods should be defined, and records should be stored securely. These controls are particularly relevant where remote audits require evidence to be shared electronically.

Privacy requirements do not remove the need for objective evidence. They require a controlled method for providing it. During an audit, redacted documents, secure screen sharing, supplier IDs, and access-controlled records may be appropriate where they still allow the auditor to verify the approval decision and evidence trail.

A competence file should allow an independent reviewer to follow one clear line: defined requirement, verified evidence, documented assessment, controlled approval, appropriate assignment, and ongoing monitoring. When that line is visible, translator competence becomes more than a claim in a tender response. It becomes objective proof that the language service provider can place qualified people on work with confidence.