Translate | ISO 23081-1:2017 Records Metadata, Provenance, Retention Events and Migration Evidence

To translate records metadata accurately, it is not enough to render file titles and labels into another language. Professionals searching for ISO 23081-1:2017 translation, multilingual records metadata, provenance terminology, retention-event translation and migration evidence must preserve the relationship between a record, the person or system that created it, the business action it documents and every subsequent change. A file described as ‘approved’ when it was only ‘submitted for approval’ can misrepresent an official decision.

ISO 23081-1:2017 covers principles for metadata used in records management. Its public ISO description connects records and their metadata with the processes, systems and organisations responsible for them. A translated record should therefore not become an isolated piece of prose. It must remain linked to unique identifiers, creation context, access restrictions, classification, version history and evidence of what happened over time.

This specialist guide answers one distinct translation question: how to localise records metadata and associated descriptions without inventing authorship, custody, authenticity, deletion authority or completed migration. It teaches terminology through reconstructed administrative cases, shows how to distinguish the original record from a descriptive copy, and provides review steps suited to bilingual archives, public organisations and document-management projects.

Quick answer: what every reader needs

For metadata for records, archival provenance, contextual links and evidence of record events, start with the actual record rather than a generic bilingual word list. Preserve identifiers, the origin of each claim, date roles, conditions, approval status and evidence references. The translated document must lead to the same practical decision as the original, including the decision not to act until verification is complete.

Keep source identifiers and values unchanged unless a controlled mapping demands otherwise.
Separate observation, request, review, approval, execution and verification.
Translate all method, access or applicability restrictions.
Flag missing evidence rather than making a plausible assumption.
Release only after bilingual and appropriate domain review.

Scope, limits and intended audience

ISO identifies ISO 23081-1:2017, edition 2, as a published and confirmed standard about principles governing metadata for records, the processes affecting records, the systems containing them and the responsible organisations. The public scope does not itself provide a universal retention period or an authorisation to destroy records.

This is an applied language and metadata guide, not reproduction of copyrighted ISO clauses or a replacement for archival policies, retention schedules, privacy law or electronic-discovery procedure. Examples are fictional and must be evaluated against the relevant controlled records system.

This guide is written for archivists, information managers, legal-operation translators, migration specialists and multilingual public agencies. The sample statements below were invented to teach precise translation and do not represent official laboratory results, archival files or ISO clauses. Whenever the source or a governing law is unclear, seek the authorised source owner rather than inventing a fact.

The underlying translation problem

A domain-specific translation is a reconstruction of reliable meaning: what entity is being described, what was actually observed or decided, when the event occurred, who is responsible and which restrictions survive. In metadata for records, archival provenance, contextual links and evidence of record events, a reader often needs to distinguish a raw fact from an approved conclusion. The sentence can be eloquent and still be wrong if it changes that boundary.

1. A record is more than text in a file

A record may document a decision, transaction or obligation and may exist as a paper form, message, structured database entry, audiovisual file or other format. Metadata provides context needed to identify and use it as evidence.

A translation of the content must remain connected to the actual record object. Do not confuse a translated description with the original documentary event or treat a later copy as if it were the first record.

The reader needs the record’s identity, context, status and history, not a polished paraphrase without provenance.

An immediate practice exercise is to remove the paragraph title and ask a colleague to identify the action and status using only the sentence. If the answer could describe both a completed event and a future plan, restore the missing qualifier. Technical brevity is helpful only after the meaning is stable.

2. Record ID and display title are different fields

The internal ID may be a persistent search key while the title is localisable for human readers. A title can change for clarity without changing the unique object’s identity.

Preserve fixed identifiers, accession numbers and external references. Where a display title is translated, link it to the untouched identifier and original-language title.

Otherwise a user may believe two labels refer to different records or that a document has been replaced.

Build a local term entry for the difficult expression and attach the document location that defines it. The term entry should say which close synonym is prohibited and why. Reviewers can then challenge a translation with evidence instead of preference or style.

3. Creators, contributors and custodians are not synonyms

The author of a letter, the officer who approved it, the clerk who scanned it, and the archivist holding it perform different actions. A metadata export might record all of them.

Use role-specific equivalents and preserve the temporal relationship: created by, reviewed by, signed by, received by, migrated by and currently maintained by.

Inventing an author or removing a custodian can distort the chain of accountability.

The subject expert should examine how the translated statement would be used in an actual workflow. Which record would the reader open? Which condition would stop an action? Which person would provide approval? A successful translation leaves these answers unchanged.

4. Business context explains what the record proves

A memorandum might be part of a procurement evaluation or a complaint-handling process. The same phrase ‘final recommendation’ does not necessarily mean an authorised purchase decision.

Translate the activity and decision state represented by the record, along with the process identifier. A record’s evidential meaning depends on what it documents, not merely its subject.

Reader-facing summaries should not confer decision-making power on an advisory document.

This difference must survive across tables, dashboards, summaries and emails, not just the main narrative. A brief exported label can travel far beyond the original paragraph. Write it with enough context to avoid an unsupported interpretation when detached from surrounding prose.

5. Creation date, receipt date and system timestamp differ

One record can carry authoring date, sending date, receipt date, capture date, last modification date and migration timestamp. They are not competing versions of a single date.

Preserve date roles and any time-zone offsets. If the source lists incomplete timestamps, do not invent midnight, a local timezone or an original signing event.

The metadata should explain when each event occurred, not conceal multiple events beneath ‘date’.

6. Authenticity is not a marketing adjective

An authentic record is a controlled evidential claim, not simply a file that looks official. Metadata may record provenance and integrity checks without automatically confirming a legal conclusion.

Translate ‘signature present,’ ‘hash matched,’ ‘verified copy’ and ‘authenticity assessment pending’ as separate states. Do not convert a technical integrity result into a broad judicial assertion.

An archivist or responsible authority must establish the relevant meaning of authenticity in context.

7. Retention and disposal require distinct powers

Records may be assigned a retention class, eligible for review or authorised for destruction under specific rules. Merely reaching a calculated date does not always mean an item was actually deleted.

Translate the trigger event, hold status, approver, disposal decision and execution evidence separately. Do not infer that a schedule is a destruction certificate.

Operational readers may take irreversible action based on one mistranslated verb.

8. Access control and privacy conditions matter

A record can be discoverable but restricted, accessible to a particular role, redacted for publication or sealed under a legal process. Public cataloguing does not automatically mean the underlying content is open.

Preserve access categories and restrictions including conditions or expiry dates. Do not promote a metadata description into permission to disclose sensitive content.

A bilingual portal needs to show what a user may see as well as what exists.

9. Versions, copies and derivatives

A scanned image, OCR text, redacted copy and translation can all be related to one source item but are not identical objects. Their status and fidelity may differ.

Keep source-to-derivative relationships explicit. A machine-extracted text file should not inherit the legal status of the original signed page by stylistic convenience.

Specify which file a quoted translation describes and whether an authoritative original is available.

10. Migration and integrity evidence

Moving records between systems may change encodings, containers, metadata mappings and access interfaces. A successful transfer count is not automatically proof that every file and relationship remained valid.

Translate migration plans, validation outcomes, checksums, exceptions, unresolved mappings and approval stages. Identify when a new format is a preservation copy rather than an original.

An evidence trail helps future users explain what changed and what did not.

11. Multilingual names and controlled vocabularies

Names of people, agencies, departments and record classes may have formal translated forms or historical variants. A normalised label can help search but must not erase the original naming evidence.

Store preferred labels, alternative labels, original script, stable identifiers and dates of name changes as different fields. Do not assume two similar department names are the same legal body.

The termbase should support search and preserve context rather than rewrite history.

12. The best test is reconstruction of the evidence chain

Ask a bilingual reviewer to reconstruct who created a record, which action it documented, who subsequently received or changed it, what restrictions apply and which version is authoritative.

Compare the source and target paths item by item. Missing relationships or exaggerated status claims are substantive errors even when the localised prose reads perfectly.

A publication is ready when another reader can perform the same discovery and evidential reasoning in either language.

Twenty worked meaning comparisons

These invented paired statements make common mistranslations visible. The control sentence expresses the meaning to preserve in any target language, not a demand for literal English word order.

Case 1: Submission versus approval

Source scenario: Application A-44 was submitted for review on 4 June. Wrong shortcut: Application A-44 was approved on 4 June. Meaning-preserving control: Application A-44 was submitted for review on 4 June.

Submission documents an incoming event, not an authorised outcome. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reconstruct the chain: identify what exists in the source, what changed during this event and what remains unverified. The translation should point to the same object and the same next human decision. Check workflow state and approver record. If the record is incomplete, mark the query as open rather than guessing.

Case 2: Creator versus scanner

Source scenario: Letter L-12 was written by Director P and scanned by Clerk R. Wrong shortcut: Clerk R authored letter L-12. Meaning-preserving control: Letter L-12 was authored by Director P and later scanned by Clerk R.

Digitisation activity does not transfer authorship. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Consider how this line appears in a spreadsheet or message preview, separated from its surrounding notes. Would a reader still distinguish the correct state and limitation? The cure is an explicit label or qualifier, not an invented assurance. Check creator and digitiser roles. Document the chosen term in the review log.

Case 3: Public description

Source scenario: Catalogue entry is public; source file access is restricted. Wrong shortcut: The complete record is freely accessible. Meaning-preserving control: The catalogue metadata is public; access to the source file is restricted.

Discoverability is different from permission to read content. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reverse the direction of the test: give the localised sentence to a second reviewer and ask them to restate it independently. Compare the actor, event, value, condition and certainty with the source. Check access control policy. A changed outcome indicates a substantive error, even if every word is grammatical.

Case 4: Retention trigger

Source scenario: Retention begins after the related contract closes. Wrong shortcut: Retention begins on the document’s creation date. Meaning-preserving control: The retention period is triggered by contract closure.

An incorrect trigger can change the earliest possible disposal date. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Before accepting an attractive synonym, locate the source evidence and identify the function of the sentence. Is it an observation, a decision, an instruction or a status report? Check schedule event definition. Use the correct function and preserve its restrictions so the reader cannot treat one kind of statement as another.

Case 5: Disposal eligibility

Source scenario: The record is eligible for disposal review. Wrong shortcut: The record has been destroyed. Meaning-preserving control: The record is ready for a disposal review, not yet disposed of.

Eligibility and completed destruction require different evidence. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

An independent specialist should be able to challenge the wording with a specific question rather than a stylistic opinion: what original field supports this claim? Check authorisation and execution logs. If there is no such field, do not add the claim. Retain uncertainty openly and route the issue to the record owner.

Case 6: Legal hold

Source scenario: Disposal is suspended because of an active preservation hold. Wrong shortcut: Disposal may proceed as scheduled. Meaning-preserving control: Disposal is suspended while the preservation hold remains active.

A hold overrides an otherwise routine disposal path. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reconstruct the chain: identify what exists in the source, what changed during this event and what remains unverified. The translation should point to the same object and the same next human decision. Check hold authority and release event. If the record is incomplete, mark the query as open rather than guessing.

Case 7: Migration status

Source scenario: Seventeen thousand files transferred; integrity review remains incomplete. Wrong shortcut: All 17,000 files were verified without error. Meaning-preserving control: 17,000 files transferred; integrity verification is not complete.

A transfer count does not settle byte integrity or metadata completeness. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Consider how this line appears in a spreadsheet or message preview, separated from its surrounding notes. Would a reader still distinguish the correct state and limitation? The cure is an explicit label or qualifier, not an invented assurance. Check reconciliation evidence. Document the chosen term in the review log.

Case 8: Hash confirmation

Source scenario: Checksum matches for file F-20 after transfer. Wrong shortcut: The original signature is legally authenticated. Meaning-preserving control: A post-transfer checksum for F-20 matches the recorded value.

File fixity is not identical to legal authenticity or signature validity. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reverse the direction of the test: give the localised sentence to a second reviewer and ask them to restate it independently. Compare the actor, event, value, condition and certainty with the source. Check checksum algorithm and context. A changed outcome indicates a substantive error, even if every word is grammatical.

Case 9: Record version

Source scenario: Revision 3 is superseded by revision 4. Wrong shortcut: Revision 3 is the authoritative current version. Meaning-preserving control: Revision 4 supersedes revision 3.

Version relationships affect which document readers should act upon. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Before accepting an attractive synonym, locate the source evidence and identify the function of the sentence. Is it an observation, a decision, an instruction or a status report? Check version register. Use the correct function and preserve its restrictions so the reader cannot treat one kind of statement as another.

Case 10: Translated abstract

Source scenario: Translated summary prepared by team T; original record remains in French. Wrong shortcut: The original record was authored in English. Meaning-preserving control: Team T prepared an English summary; the original record is French.

A derivative’s language is not the source language. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

An independent specialist should be able to challenge the wording with a specific question rather than a stylistic opinion: what original field supports this claim? Check language and derivative fields. If there is no such field, do not add the claim. Retain uncertainty openly and route the issue to the record owner.

Case 11: Date role

Source scenario: Captured in repository on 9 May; originally issued 2 May. Wrong shortcut: The record was issued on 9 May. Meaning-preserving control: Issued on 2 May and captured in the repository on 9 May.

Issuance and system capture are different events. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reconstruct the chain: identify what exists in the source, what changed during this event and what remains unverified. The translation should point to the same object and the same next human decision. Check event metadata. If the record is incomplete, mark the query as open rather than guessing.

Case 12: Time zone

Source scenario: Audit event occurred at 2026-04-18T16:30:00Z. Wrong shortcut: Audit event occurred at 16:30 local time everywhere. Meaning-preserving control: Audit event was logged at 16:30 UTC on 18 April 2026.

A UTC timestamp must not silently become another locality’s clock time. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Consider how this line appears in a spreadsheet or message preview, separated from its surrounding notes. Would a reader still distinguish the correct state and limitation? The cure is an explicit label or qualifier, not an invented assurance. Check timestamp offset. Document the chosen term in the review log.

Case 13: Redacted copy

Source scenario: Published version excludes personal addresses under an approved redaction decision. Wrong shortcut: The source record contains no addresses. Meaning-preserving control: The public derivative has approved address redactions.

Removing information in a derivative does not prove absence from the source. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reverse the direction of the test: give the localised sentence to a second reviewer and ask them to restate it independently. Compare the actor, event, value, condition and certainty with the source. Check redaction log. A changed outcome indicates a substantive error, even if every word is grammatical.

Case 14: Identifier migration

Source scenario: Legacy ID R-009 maps to new ID ARC-773. Wrong shortcut: R-009 was deleted and replaced by an unrelated item. Meaning-preserving control: Legacy ID R-009 corresponds to ARC-773 after migration.

Keep identity continuity across old and new systems. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Before accepting an attractive synonym, locate the source evidence and identify the function of the sentence. Is it an observation, a decision, an instruction or a status report? Check mapping register. Use the correct function and preserve its restrictions so the reader cannot treat one kind of statement as another.

Case 15: Authority record

Source scenario: Agency name changed in 2018; earlier records retain the historic name. Wrong shortcut: The new agency name appears on all historic originals. Meaning-preserving control: The historic creator name remains on earlier records; an authority link notes the 2018 name change.

Controlled names support discovery without rewriting earlier evidence. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

An independent specialist should be able to challenge the wording with a specific question rather than a stylistic opinion: what original field supports this claim? Check authority record and dates. If there is no such field, do not add the claim. Retain uncertainty openly and route the issue to the record owner.

Case 16: Missing attachment

Source scenario: Metadata lists attachment 3; the file has not yet been located. Wrong shortcut: Attachment 3 is available and verified. Meaning-preserving control: Attachment 3 is referenced but has not yet been located.

An index reference is not proof the object is present. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reconstruct the chain: identify what exists in the source, what changed during this event and what remains unverified. The translation should point to the same object and the same next human decision. Check missing-object incident. If the record is incomplete, mark the query as open rather than guessing.

Case 17: Custody transfer

Source scenario: Box B-77 was requested by archive team Q; transfer not yet completed. Wrong shortcut: Q has custody of box B-77. Meaning-preserving control: Q requested box B-77; custody transfer is outstanding.

Requested and executed handovers have different proof. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Consider how this line appears in a spreadsheet or message preview, separated from its surrounding notes. Would a reader still distinguish the correct state and limitation? The cure is an explicit label or qualifier, not an invented assurance. Check signed receipt. Document the chosen term in the review log.

Case 18: Reclassification proposal

Source scenario: Security class downgrade was proposed and awaits approval. Wrong shortcut: The record is now unrestricted. Meaning-preserving control: A change to the security classification is proposed, pending approval.

Proposal language must not lift an existing restriction. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Reverse the direction of the test: give the localised sentence to a second reviewer and ask them to restate it independently. Compare the actor, event, value, condition and certainty with the source. Check authorised class decision. A changed outcome indicates a substantive error, even if every word is grammatical.

Case 19: Disposal approval

Source scenario: Disposal of series S-21 is authorised; execution scheduled next month. Wrong shortcut: Series S-21 has already been destroyed. Meaning-preserving control: Disposal has been authorised for S-21; destruction is scheduled for next month.

Approval is not the physical act or its completion certificate. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

Before accepting an attractive synonym, locate the source evidence and identify the function of the sentence. Is it an observation, a decision, an instruction or a status report? Check disposal execution evidence. Use the correct function and preserve its restrictions so the reader cannot treat one kind of statement as another.

Case 20: OCR text

Source scenario: OCR version was generated automatically and not manually checked. Wrong shortcut: The OCR text is a certified exact transcript. Meaning-preserving control: Automatically generated OCR text has not undergone manual verification.

Machine extraction should not inherit a guarantee of fidelity. A translator may reshape the sentence naturally, but may not replace a recorded observation with a permission, a preliminary state with an approved result, or a precisely identified object with an unbounded generalisation.

An independent specialist should be able to challenge the wording with a specific question rather than a stylistic opinion: what original field supports this claim? Check OCR review status. If there is no such field, do not add the claim. Retain uncertainty openly and route the issue to the record owner.

Terminology notebook for multilingual reviewers

For metadata for records, archival provenance, contextual links and evidence of record events, terminology must be attached to examples, not left as an alphabetic list of attractive equivalents. Each entry needs a source definition, approved equivalent, rejected false friend, usage example, domain reviewer and date. The following twenty terms are candidates for explicit control.

records metadata: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
record identifier: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
creator: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
contributor: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
custodian: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
business context: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
record capture: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
accession number: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
authority file: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
retention trigger: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
retention schedule: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
disposal eligibility: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
disposal authorisation: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
legal hold: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
provenance: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
integrity check: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
checksum: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
derivative: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.
redacted copy: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve any associated date, number, unit and boundary. Attach one verified example that a second-language reviewer can audit.
migration mapping: identify the specific entity, quantity, role, event or evidential state denoted by this expression in the source. Document the contrast with its nearest misleading alternative. Preserve the responsible person, permitted action and state of approval. Attach one verified example that a second-language reviewer can audit.

Twelve-stage verification and release workflow

1. Confirm the source

Identify the authoritative file, original language, edition, issuing organisation and revision date. Avoid translating from screenshots or detached notes when an approved source exists. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

2. Define the user task

State what the target reader will need to identify, understand or decide. Risky sentences are those that can change an action or evidential conclusion. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

3. Lock invariant identifiers

Map all IDs, dates, quantities, units, unique names, role labels and reference numbers. These remain exact unless the system formally specifies a mapping. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

4. Mark status words

Highlight pending, provisional, approved, rejected, suspended, observed, completed, confirmed and superseded. Compare how the target language expresses their distinct force. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

5. Define terms in context

Create a small termbase with examples, rejected synonyms and owners. Do not resolve scientific or administrative ambiguity by intuition. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

6. Draft with natural grammar

Make the target sentence readable while retaining restrictions, attribution, degree of certainty and the actual record relationship. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

7. Check negation and conditionals

Find not, may, only, subject to, excluding, if and unless. Their omission can reverse the reader’s decision. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

8. Compare fields separately

Run a row-by-row data verification so that a correct paragraph does not disguise a wrong code, time, symbol or table label. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

9. Bilingual second review

Use an independent linguist to compare meaning directly with the source, not merely proofread spelling or punctuation. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

10. Technical or records-owner review

Resolve unresolved domain facts with the authorised responsible person. Do not treat translator confidence as documentary evidence. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

11. Blind task reconstruction

Ask someone to use the target text alone to locate the correct object, event, condition, evidence and next action. Compare with the source-language outcome. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

12. Approve and archive

Retain the final version, terminology notes, issue log, sign-off and source revision so future changes can be traced and corrected. For metadata for records, archival provenance, contextual links and evidence of record events, name a real document field or review record that demonstrates this step was completed. A bare checkbox without evidence may conceal the very error that the stage is intended to catch.

A four-week practice programme

Week one: source anatomy

Collect a small set of representative non-confidential records. Underline identifiers, evidence statements, stage verbs, qualifiers and missing fields. Ask the responsible expert which facts are essential for a decision. In this field, compare the same practical decision in both languages and ask whether the reader finds the same evidence and limitation.

Week two: controlled language

Create a bilingual termbase with definitions, contrasting false friends and sentence examples. Translate short extracts and keep unresolved questions visible. Record the source of each accepted choice. In this field, compare the same practical decision in both languages and ask whether the reader finds the same evidence and limitation.

Week three: blind testing

Have independent reviewers reconstruct the source events and decisions from target-language extracts only. Log errors by their consequences, including the risk of acting too early or trusting unsupported evidence. In this field, compare the same practical decision in both languages and ask whether the reader finds the same evidence and limitation.

Week four: sign-off and drift control

Reconcile technical issues, freeze versions, approve final terminology and document a correction channel. Run change-impact checks whenever the source records, system or governing rules change. In this field, compare the same practical decision in both languages and ask whether the reader finds the same evidence and limitation.

Frequently asked questions

1. Is a translated catalogue entry the original record?

No. It is a description or derivative and should remain linked to the controlled original and its identity. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

2. Can a document title be translated while keeping the ID?

Yes, where the system supports it. Keep the immutable identifier and original title available. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

3. Does a checksum match prove legal authenticity?

No. It supports a particular integrity check; broader authenticity depends on provenance, controls and the relevant context. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

4. Does a retention expiry date mean the file is destroyed?

No. Eligibility, approval, execution and evidence of disposal are distinct stages. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

5. What should be done with a missing attachment?

Retain the reference and mark the object as missing or unresolved; do not invent access. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

6. How should historical agency names be handled?

Preserve evidence of the historic name and, where appropriate, add a documented authority relationship to a successor or variant. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

7. What is the central migration translation risk?

Treating a successful transfer count as complete verification of files, metadata, relationships and permissions. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

8. Can AI fully approve archival metadata translations?

It can assist drafting and mapping, but domain validation, access decisions, provenance and authoritative status require appropriate human control. For external publication, a reviewer should also verify the underlying source, actual scope, version and responsible authority. Where that chain is incomplete, do not expand the original claim or remove the warning; ask for clarification and preserve uncertainty.

Editorial sources and learning connections

Official catalogue: ISO 23081-1:2017 at ISO. The public description establishes the standard’s scope and publication status; it is not a licence to reproduce protected clauses or a substitute for the controlled method or policy. Recheck the edition and status before professional use.

The conceptual parent is Master Art of Translation (EDKSG-TRANS-MASTER-WORLD-000). Related protected resources are the Vocabulary Learning Hub and How English Works: Translation and Meaning Across Languages. This article is a focused application, not a competing general translation hub.

Editorial verification: 5 November 2026. The twenty cases are original teaching hypotheticals, not actual standards clauses, laboratory releases, legal decisions or records-management authorisations.