Checking the Status of a Translated Policy Document
Record provenance and translation limitations.
Checking the status of a translated policy document means establishing and recording what the translation is, where it came from, how it was produced, who reviewed it, what use has been approved, and what remains unverified. It does not mean declaring the translation authoritative. Authority over a policy document's language versions rests with the issuing authority and the applicable legal framework; a commissioning organization's task is to document provenance and limitations so that readers can judge fitness for a specific decision.
What the status check should record
A status check is a document-control statement, not a compliment about translation quality. A translation can be accurate and still not authoritative. It can be fit for an internal briefing and unfit for public consultation. It can be complete in its main sections while omitting annexes, table notes or accessibility features that matter to the reader.
Record the source and the translation as a version pair. For the source, capture the issuing authority, title, reference or version identifier, date, language, and the channel through which the document was obtained. For the translation, capture the target language, version, date, file name, producer role, translation method, and whether it is complete. Then record the review and approval trail: who checked which sections, with what language and subject competence, and who approved the translation for what purpose.
Policy documents may pass through drafting, consultation and revision before publication. The European Commission's Better Regulation guidelines and toolbox illustrate how policy development and its evidence base can be documented in one public administration. They are a context reference, not a translation standard, and they do not confer authority on any translated text.
Separate authority, quality and fitness for use
These three questions are often conflated. They should be recorded separately.
| Question | What it asks | Who can resolve it |
|---|---|---|
| Authority | Which language version prevails, if any, for a given purpose | The issuing authority and qualified legal advisers in the relevant jurisdiction |
| Quality | Whether the translation conveys the source accurately and completely | A bilingual reviewer with relevant subject knowledge, supported by verification evidence |
| Fitness for use | Whether the translation is adequate for a briefing, consultation, board paper or research decision | The commissioning organization, against recorded limitations |
A translator or vendor cannot create legal authority by labelling a document "official" or "authoritative." A certification label may describe a translation process, but it does not by itself establish that the translated document is the operative version. Where the question matters to a decision, ask the issuer for its language statement and record the answer, including "not confirmed."
A translation-status and verification checklist
Use the checklist as an annex to the translated file. The evidence column records what supports the entry; where evidence is absent, the entry should say "not confirmed" rather than imply verification.
| Check | What to record | Evidence or verification action |
|---|---|---|
| Source identity and version | Issuer, title, reference, date, source URL or deposit location, access date, supersession status | Obtain from the issuer or an official channel; record an undated source as a limitation |
| Translation identity | Target language, version, date, file name, translator or vendor role, method (human, machine, post-edited or adapted), direct or relay translation | Compare file metadata and cover note; do not infer method from prose quality alone |
| Translation chain | Whether the source was itself a translation, or whether an intermediate language was used | Ask the producer; record unknown links in the chain as limitations |
| Completeness | Sections, annexes, tables, figures, footnotes, embedded text and accessibility features translated or omitted | Compare structure and sample sections; list omissions explicitly |
| Review and competence | Reviewer role, language and subject competence, review date, sections checked, unresolved comments | Check the review log; "reviewed" without a stated scope is not evidence |
| Terminology and concepts | Glossary, defined terms, acronyms, units, jurisdiction-specific concepts and provisional equivalents | Compare key terms against the source; record provisional choices |
| Dates, numbers and references | Dates, figures, currency, units, article or section numbers, cross-references and hyperlinks | Spot-check high-consequence items; note mismatches |
| Approval and permitted use | Approver, date, approved purpose (internal briefing, publication or consultation), conditions and expiry | Obtain written approval; translator sign-off alone is not organizational approval |
| Publication and supersession | Deposit location, access controls, status label, superseded versions and archive copy | Check version control; multiple undated copies are a red flag |
| Limitations and review triggers | Untranslated content, uncertain terms, absent legal review, issuer statement on authority, new source version or expiry | Record as a standing limitation and set a review date |
When the translated document will be published, check that heading levels, table headers, alt text and reading order have been preserved. A translation that loses these features may be textually complete but functionally weaker for public use.
Status labels for internal records
Labels should be defined in the organization's document-control rules. The following set is a starting point; it records process, not legal effect.
| Label | What it records | What it does not establish |
|---|---|---|
| Source only | No translation is held | No target-language text |
| Working translation — unverified | A translation exists but no review has been recorded | Not suitable for external use without further checks |
| Reviewed translation — defined use | Bilingual review has been completed for specified sections and a stated use | Not necessarily complete; not issuer-confirmed |
| Approved translation — publication | A named approver has authorized publication for a defined purpose | Does not by itself establish legal authority |
| Issuer-confirmed authoritative version | The issuer has stated that this language version prevails | Check the scope, date and any conditions attached to that statement |
Write the status note
The status note should travel with the file and appear in any evidence table or research annex. A short note is usually enough:
Source: [title], [issuer], [version/date]. Translation: [language], [version/date], produced by [method]. Review: [reviewer role] checked [sections] on [date]. Approval: [role] approved for [use] on [date]. Limitations: [omissions, uncertain terms, no legal review]. Authority: [issuer statement or "not confirmed"]. Review trigger: [new source version/expiry].
This note prevents a translated quotation from being treated as if its version and review were settled. It also helps the commissioner decide whether to commission a fuller bilingual review, restrict the translation to internal use, or seek a statement from the issuer. Those are scoping decisions, not conclusions about the policy itself.
Limitations to state plainly
The checklist supports document control; it does not determine legal authority, certify equivalence or guarantee fitness for a particular decision. A reviewer's sign-off is bounded by the sections and purpose recorded. Translation status is process evidence, not evidence of policy effect or stakeholder agreement.
Where a decision depends on rights, obligations or the legal effect of a language version, the organization should verify the applicable rules and obtain qualified advice in the relevant jurisdiction. The checklist helps frame the questions and preserve the record; it does not answer those questions on the organization's behalf.
Organizations commissioning policy, regional or social research can adapt the checklist as an annex to a research brief or evidence pack. To discuss how translated sources should be scoped in a commission, see commissioning research or contact.