15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Contract

Free Translation Contract Template

A translation contract covers the scope of translation and localisation work, deliverables, payment stages, revision handling, ownership, liability limits, and termination terms.

Translation Contract template preview

Language:

en

Last updated:

October 2026

Share template

A product needs translating, the deadline’s real, and nobody wants a small mistranslation hiding in a clause, a safety step, or a UI label. The translation contract gives both sides the words for how the work runs, what gets delivered, and what happens when the source files change halfway through. The layout uses verdigris green and bengara accents with Raleway headings over Roboto body text, so the key terms stay scannable when someone’s checking scope and sign-off points.

The agreement starts by naming the working relationship for translation and localisation, then moves into Scope of work, including the file realities that usually cause quality slips, like tables, tags, placeholders, screenshots, and UI strings. Payment fixes a 50% booking payment and a 50% balance on handover, with 14-day invoice terms and a pause on work if an account goes overdue, so delivery and scheduling don’t turn into guesswork. The later sections cover one included revision round through a bilingual review file, how change requests get quoted from the changed source only, who owns the translated deliverables after final payment, and where responsibility stops if the source text is wrong or edits happen after sign-off.

  • This working agreement sets out how Opens with how translation and localisation will run, including what the translator needs from the client and how bilingual review and sign-off happen.
  • Scope of work Defines languages, file types, workflow, and the deliverables list, including details like tables, callouts, tags, placeholders, screenshots, and UI strings.
  • Payment Spells out the 50/50 payment stages, 14-day invoice terms, and what happens to work and deliverables if an invoice goes overdue.
  • Revisions and changes Locks in one revision round through the bilingual review file, then explains how mid-project source changes and extra review rounds get quoted and approved in writing.
  • Ending the project Covers written notice, payment for completed work and committed costs, what gets handed over if the project ends early, and includes a Signature block.

Once the terms match your job, you fill in names, dates, and rates, send the contract, and the client signs online from wherever they open it.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What to include in a translation contract

PartWhat it covers

This working agreement sets out how

Defines how translation and localisation work will run, including what the translator delivers and what the client needs to supply and approve.

Scope of work

Describes the languages, file types, workflow, and the deliverables being handed over, including tricky content like tags, placeholders, screenshots, and UI strings.

Payment

States the 50% booking payment and 50% final payment, invoice timing, and what happens if payment runs late and deadlines are affected.

Revisions and changes

Explains the included revision round and how source changes after work starts get quoted from the changed source and approved in writing.

Who owns what

Says when the client owns the translated deliverables and what working files, QA checklists, and translation memory structures stay with the translator.

Problems and limits

Covers the checks performed, how errors get corrected, and the limits around unclear source text, post sign-off edits, and indirect losses.

Ending the project

Sets out written notice, early termination payments, handover of completed work, and includes the Signature section for acceptance.

Who it is for

Independent translators, localisation studios, and subtitling teams who need a signed agreement before starting document translation or software localisation work.

The contract in full

This working agreement sets out how we will run translation and localisation for you, on the project you have accepted.

Our job is to translate what you send, keep terminology consistent across files and versions, and return deliverables you can ship with confidence. Your job is to give us the right source files and the context we need to make accurate choices, and to review and sign off when we send the bilingual review file.

Scope of work

We will deliver translation and localisation for the languages, file types, and timelines set out in the project, and we will follow the workflow we have agreed for terminology, bilingual review, and QA. This scope includes handling the usual details that affect quality in real files, like tables, callouts, tags, placeholders, screenshots, and UI strings.

Your project deliverables are listed below, and that list is what we will deliver and hand over at the end of the project.

* Project glossary and termbase * Translated source files * Bilingual review file * Format and layout check notes * Subtitle and caption files * Final QA report

Payment

To book the project in our schedule, you pay 50% of the total price when the proposal is signed. We start work once that first payment is received and we have the agreed source files. The remaining 50% is due when we hand over the finished work.

We invoice at those two points, and each invoice is payable within 14 days of its date. If an invoice becomes overdue, we pause any further work and any release of remaining deliverables until the account is up to date. If a deadline is at risk because payment is late, we will tell you as soon as we can and agree a revised delivery plan in writing.

Revisions and changes

One revision round is included. This means you review the bilingual review file, collect comments in one place, and send them back to us, and we apply those edits to the translation and update the deliverables. That round covers corrections, clarifications, and style adjustments that stay within the agreed source.

If the source changes after we have started, for example legal text updates, product spec changes, or UI string updates, we treat that as a change. We will quote the revision from the changed source only, based on tracked changes or a clearly marked revised file, and we will wait for your written approval before we apply updates. Extra review rounds are also quoted before we do them.

Who owns what

Once the final payment is received, you own the translated deliverables we hand over for this project. You can use them internally and externally, publish them, and share them with your vendors as needed to ship the product or campaign.

We keep ownership of our working files, templates, QA checklists, and any tools we use to produce the work, including our internal translation memory and termbase structure. To help you stay consistent on future updates, we may reuse translation memory segments and terminology entries we created while working for you, unless you ask us not to in writing. If you provide your own TM or glossary, it stays yours, and we only use it for your project work.

Problems and limits

We take care with meaning, numbers, and terminology, and we run a second-linguist check plus format checks for tags, placeholders, tables, and line breaks. If you spot an error in something we delivered, tell us promptly and we will correct it and re-issue the affected files.

We cannot take responsibility for issues caused by source text that is wrong, ambiguous, or incomplete, or by changes you make after sign-off. We also cannot cover losses that sit outside the translation itself, like missed revenue, indirect knock-on costs, or decisions made from using draft text before you have approved the bilingual review file as the content sign-off.

Ending the project

Either of us can end the project by giving notice in writing. Because the right notice period depends on what stage the files are at, we will agree the notice period with you in writing at the time, and we will confirm what can still be delivered and when.

If the project ends early, you pay for the work completed up to the end date, including any non-recoverable costs we have committed for your project. Once that payment is made, we will hand over what we have completed in a usable form, along with any notes needed to continue the work elsewhere. If we end the project because required files, access, or approvals have not been provided, we will still hand over completed work on the same basis.

Signature

Legal Notice: Please consult legal advice and carefully review the content of this contract template before implementing this template in your business.

Questions about this contract template

What should a translation contract include?

A translation contract usually includes the scope, deliverables, payment stages, revision handling, ownership of the translated files, liability limits, and termination terms. The agreement also needs to say what happens when the source text changes mid-project.

Can a translator use our translation memory and glossary?

A translation contract can state that the client will provide a TM and glossary, and that the translator will use them for the project work. The agreement can also clarify what happens to terminology and translation memory segments created during the project.

What files and context does a translator need from the client?

Clients usually need to provide the right source files plus enough context to make accurate choices, then review and sign off when the bilingual review file arrives. The contract can make that handoff and approval step part of the workflow.

How do you handle revisions in translation projects?

Many translation agreements include one revision round, based on the client’s consolidated comments on a bilingual review file. Source changes after work starts can be treated as a change request that gets quoted from the changed source and approved in writing.

How do translation payments usually work?

Translation contracts often split payment into a booking payment and a final balance due on handover. This template uses a 50% upfront payment to book schedule time and 50% due when the finished work is delivered, with 14-day invoice terms.

Who owns the translated text after payment?

A contract can state that the client owns the translated deliverables after final payment and can publish and share them as needed. The same contract can also keep the translator’s internal working files, templates, and QA checklists separate from what gets handed over.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away