How to Prepare Legal Documents for Translation

Start With How the Translation Will Be Used

Two copies of the same legal document can require very different translation workflows depending on what happens to the translated version.

A contract translated so internal counsel can understand a transaction may have different review and formatting requirements from an agreement being negotiated with a counterparty. A court exhibit may be subject to filing instructions that do not apply to discovery materials being translated for internal review. A corporate document intended for an overseas registry may require formalities that would be unnecessary for due diligence.

Before translation begins, identify:

• the intended use;
• the people or organizations that will rely on the translation;
• the destination country or jurisdiction;
• the target language and locale;
• whether the document will be reviewed, negotiated, executed, filed, certified, or used as evidence; and
• any requirements supplied by the receiving organization.

Confirm the target locale, not just the language

“French,” “Portuguese,” or “Spanish” may not be specific enough when terminology, official conventions, or audience expectations differ between markets. When relevant, identify the required locale or destination market so appropriate linguistic resources can be selected from the beginning.

Tell the translation team what the document needs to accomplish

Resolving intended use early helps determine the appropriate translation, review, certification, formatting, security, and delivery workflow.

Identify the Final, Authoritative Source Version

Version control is one of the most important steps in preparing legal documents for translation.

Contracts are revised. Pleadings are updated. Transaction documents circulate in multiple drafts. Policies receive last-minute edits. Exhibits may be replaced shortly before filing. When several similarly named files are submitted without clear instructions, the risk of translating the wrong version increases.

Establish one clear baseline

Whenever possible, identify the final approved or authoritative version before translation begins.

If translation must begin from a draft, label it clearly and identify:

• which sections remain subject to change;
• when the final version is expected;
• whether the translated draft should be updated when the new source arrives; and
• whether tracked changes or a change log will be available.

Provide the final document and editable source when possible

The editable file should not be assumed to replace the authoritative version when the two differ.

Label reference-only files

Prior agreements, related pleadings, bilingual precedents, earlier translations, and other materials can provide valuable context without being part of the translation scope. Mark them clearly as reference only so there is no uncertainty about what should be translated.

Provide Complete and Legible Legal Documents

Legal content often depends on relationships between pages, provisions, schedules, exhibits, footnotes, definitions, and referenced documents.

A translation can only preserve those relationships when the source package is complete. Before submission, check that the files include all relevant:

• pages;
• schedules;
• exhibits;
• annexes and appendices;
• certificates;
• tables and footnotes;
• continuation and signature pages;
• stamps and seals;
• handwritten annotations; and
• supporting documents included in the scope.

Check scanned documents carefully

For scanned PDFs and image-based files, verify that:

• all pages are present;
• text is in focus;
• page edges are not cropped;
• faint stamps and handwriting remain visible;
• pages are oriented correctly; and
• the resolution is sufficient to read small text, numbers, dates, and identifiers.

Unclear source content should not be guessed. If a page, signature, handwritten note, stamp, or other element is partially illegible, resolving the issue before translation begins can prevent unnecessary queries later.

Do not overlook non-body text

Headers, footers, document numbers, exhibit labels, marginal notes, stamps, seals, signatures, handwritten content, and text embedded in images may be relevant to the document's use.

Tell the translation team whether these elements should be translated, transliterated, described, retained as shown, or treated according to the receiving organization's requirements.

Provide Editable Source Files When Available

Editable files generally make legal translation and multilingual formatting easier to manage.

Editable files can preserve document structure and reduce manual recreation of tables, numbered clauses, footnotes, cross-references, and other formatting. PDFs and scanned documents can also be translated. The important point is to provide the best available source and clarify what the finished deliverable must look like.

Plan for text expansion

Translated text may be longer or shorter than the source. This can affect tables, forms, text boxes, headings, signature areas, and fixed-layout documents.

If layout fidelity matters, make it part of the project scope at the beginning rather than treating formatting as a final cosmetic step.

Organize Large Legal Document Sets Before Submission

Clear organization becomes especially important when a matter includes dozens, hundreds, or thousands of files.

Use filenames and folder structures that allow the legal team and translation team to understand what each file is and how it relates to the rest of the project.

1. Use consistent document names.
2. Include dates or version identifiers where useful.
3. Group files by matter, document type, language, or priority.
4. Number files when sequence matters.
5. Keep exhibits with the documents they support.
6. Separate translatable files from reference-only materials.
7. Provide a master file list for larger document sets.

For urgent matters, identify the documents that need to be translated first rather than marking an entire document collection as equally urgent.

Share Defined Terms, Prior Translations, and Approved Legal Language

Legal documents frequently establish their own vocabulary, and consistency becomes more difficult when each translation begins without access to language that has already been reviewed or approved.

A defined term introduced on page one may appear throughout an agreement, its schedules, subsequent amendments, related statements of work, and future renewals.

Before translation begins, provide relevant:

• defined terms;
• legal glossaries;
• official entity and party names;
• bilingual contracts and previous translations;
• precedent clauses;
• counsel-approved terminology;
• regulatory terminology;
• product or technical terminology used within the legal documents;
• translation memories; and
• reviewer-approved language from earlier projects.

Previous translations can be particularly valuable

An earlier translation does not automatically need to be copied. It can, however, show how an organization has previously translated defined contractual terms, corporate names, recurring clauses, department names, regulatory expressions, product terminology, and specialized legal concepts.

Qualified linguists can evaluate that language in the context of the new document rather than recreating terminology without reference.

Confirm Certification and Filing Requirements Before Translation Begins

A document does not require certified translation simply because it is legal. Certification is usually determined by the document's intended use and the requirements of the organization receiving it.

A court, government agency, regulator, immigration authority, registry, university, financial institution, or other organization may establish its own requirements.

Before ordering translation for formal use, confirm:

• whether certification is required;
• whether prescribed certification wording applies;
• whether the translator must meet specific qualification requirements;
• whether notarization is required;
• whether a sworn, authorized, accredited, or court-recognized translator is required in the destination jurisdiction;
• whether the translated file must follow a particular format;
• how signatures, stamps, seals, and handwritten content must be represented;
• whether electronic delivery is accepted; and
• whether authentication, legalization, or another process applies separately to the underlying document.

Certified, notarized, and sworn translation are not interchangeable terms

Requirements and terminology differ among jurisdictions and receiving organizations. Do not assume that a certification format accepted by one organization will satisfy another.

Whenever possible, send the receiving organization's current instructions with the source documents.

Define How the Final Translation Needs to Function

“We need it to look like the original” is a common request, but visual similarity is only one part of document usability.

Before translation begins, decide how the finished document will be reviewed, compared, edited, submitted, or archived.

Also identify how the translation should handle clause and section numbering, page numbering, headings, cross-references, tables, footnotes, schedules, exhibits, signature blocks, stamps and seals, hyperlinks, comments, and tracked changes.

Formatting requirements are easier to accommodate when they are known before translation and document production begin.

Define Confidentiality, Security, and Technology Requirements Upfront

Legal translation can involve commercially sensitive information, personal data, intellectual property, transaction materials, investigation records, litigation content, financial information, or potentially privileged communications.

Security requirements should therefore be treated as part of project preparation rather than added after files have already been distributed.

Before sharing documents, identify any requirements involving:

• confidentiality agreements;
• restricted project access;
• secure file transfer;
• approved reviewers or vendors;
• personal or regulated data;
• retention or deletion policies;
• data-location requirements;
• use of subcontractors;
• translation memory or terminology reuse; and
• use of AI, machine translation, external language tools, or other automated processing.

State AI and technology restrictions explicitly

Organizations increasingly have their own policies governing generative AI, machine translation, cloud processing, and confidential data.

If your legal department, client, outside counsel, regulator, or corporate security policy limits how content may be processed, include those requirements in the project instructions before work begins.

The appropriate workflow should be selected around the content's intended use, confidentiality requirements, and risk rather than assuming one technology model fits every legal project.

Identify Who Will Review and Approve the Translation

A legal translation project can lose time when several stakeholders provide conflicting feedback or when no one has authority to resolve terminology questions.

Before kickoff, identify:

For multilingual projects, also determine whether reviews will be centralized or handled separately by regional or in-country teams.

Give reviewers the right context

If reviewers have previously approved terminology, standard clauses, or preferred language, supply that information before translation whenever possible.

Reviewer feedback is most useful when it improves the translation rather than introducing preferences that could have been established during project preparation.

Share the Real Deadline and Prioritize What Matters Most

Legal translation deadlines are often tied to something larger: a filing, transaction, hearing, closing, board meeting, contract signature, regulatory submission, employee communication, or internal review.

Share that underlying deadline rather than only providing the desired translation delivery date.

A realistic project schedule may need to account for:

• translation;
• linguistic review;
• client review;
• question resolution;
• certification;
• formatting;
• document-level QA;
• final revisions; and
• submission or delivery.

Prioritize urgent document sets

When a matter contains multiple files, determine which documents are actually needed first. Phased delivery can allow priority documents to move into legal review while work continues on the remaining material.

Avoid unnecessary source changes after kickoff

Sometimes changes are unavoidable. When a source document is revised during translation, provide a clearly versioned replacement or tracked changes so the affected content can be identified efficiently.

Uncontrolled mid-project revisions can create duplicated effort and make it harder to confirm which translation corresponds to which source.

Six Legal Translation Preparation Mistakes to Avoid

Many preventable delays begin with unclear files, incomplete scope, or requirements that are discovered only after translation is already underway.

Final Check Before You Send Legal Documents for Translation

Before submitting your files, confirm that the project package answers the essential questions a translation team will need to start correctly.

If these items are clear, the legal translation project can begin with a much stronger foundation.