A translation request form covers who’s requesting the work, what language pair is needed, what files to translate, and any certification or critical term notes.
A product spec, a safety sheet, or app copy needs translation, and the risky part is always the same: one missed term or warning can turn into a real problem. The Translation Request Form gives a translator the project details up front, so the right files, languages, and non negotiable wording don’t get guessed at later, with brass accents under Space Grotesk headings that read more like a checklist than a pitch.
The opening note explains what the form is collecting and why, and a second note asks for the files, languages, and any must follow instructions for the job. From there the questions move through contact details, what the work is needed by, the source and target language or languages, a file upload for reference material, and a clear yes or no on certified translation... then a final space to spell out certification details, fixed terms, and critical warnings that can’t drift in localisation or document translation.
- Translation Request Form A short intro explains what the translator will review and where timeline and next steps get confirmed.
- Project details A second written section asks for files, languages, and must follow notes before any translation & localisation starts.
- Languages and deadline The questions capture when the translation is needed, plus the source language and target language or languages.
- Files and certification The form collects uploads and flags certified translation needs, with space for certification details and critical warnings.
Once the form is in your workspace, you publish it as one of your forms that collect answers and files so the request arrives with attachments and the required fields already filled in.
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.
What to include in a translation request form
| Part | What it covers |
|---|
Translation Request Form | An opening note explains what details the translator needs before starting translation and localisation, and what happens after the files are reviewed. |
Your name | A required name field ties the request to a real contact before any files get handled. |
Email address | A required email field gives a clear place to confirm timeline and next steps after review. |
Needed by (delivery date for launch, print run or publication) | A date field captures the delivery date, so the request is anchored to a launch, print run, or publication deadline. |
Project details | A short prompt asks which files and languages are involved, plus any notes the translator has to follow for software localisation or other localisation work. |
Project name or file title | A field for the project name or file title helps match the request to the right document set. |
Source language | A required field states the source language, so the translator knows what they’re working from. |
Target language or languages | A required field names the target language or languages, including multi language deliveries where needed. |
Upload source files and reference material | A required upload field collects the source files and reference material in the same request. |
Do any documents need a certified translation? | A required yes or no question flags certified translation requirements early, before quotes or scheduling get confirmed. |
Certification details, fixed terms and critical warnings | A long text field holds certification details, fixed terminology, and critical warnings that have to stay intact in the target market. |
Who it is for
Translation agencies, localisation teams, and freelancers handling anything from document translation to subtitling where the requester needs the right files, languages, and terminology captured before work starts.
The form in full
Translation Request Form
This form collects the project details I need before I start the translation and localisation you booked. I will review your files and confirm timeline and next steps.
- Your name (required)
- Email address (required)
- Needed by (delivery date for launch, print run or publication)
Project details
Tell me which files, languages and must-follow notes for this job.
- Project name or file title
- Source language (required)
- Target language or languages (required)
- Upload source files and reference material (required)
- Do any documents need a certified translation? (required)
- Certification details, fixed terms and critical warnings
