TRANSLATION GUIDES

Translation Guides · Project Preparation

Translation Project Planning Guide

A practical guide for defining translation scope, choosing the right workflow, and coordinating people, files, deadlines, and approvals before work begins.

Stepes Resource Guide A practical briefing, scheduling, cost, and review framework
Read the key takeaways ↓

Project brief

Languages · Scope · Files · Approvals

Plan and assign responsibilities

  • Translation workflow
  • Quality review
  • Approved delivery
  • Clear requirements
  • Realistic scheduling
  • Defined ownership
  • Predictable handoff

Key Takeaways

Use this guide when planning a one-time document translation, a multilingual launch, or a recurring enterprise translation program.

Document audiences, language variants, files, content purpose, and acceptance criteria before requesting a quotation.

Budget for preparation, specialist review, formatting, in-country approval, and revision cycles—not only word count.

Name an owner for source changes and final approval so translation work is not blocked late in the schedule.

Define Scope, Languages, Files, and Review Requirements

Translation projects run more smoothly when the team agrees on the purpose of each deliverable, the target audiences, source-file readiness, terminology, quality expectations, and review responsibilities. Missing instructions at intake often turn into avoidable clarifications and late revisions.

Define What Success Means

Identify the intended use, language variants, key audiences, and acceptance criteria before selecting a translation method.

Identify Dependencies

Account for source approval, file preparation, external review, publishing formats, and stakeholder response times.

Avoid Late-Stage Ambiguity

Agree on how terminology questions, client changes, quality findings, and scope additions will be handled.

What to Include in a Translation Project Brief

A useful brief is concise but sufficiently specific to help translators, project managers, and reviewers make consistent decisions.

Practical considerations

  • Audience and Purpose Explain who will read the content, what they need to do, and whether it is public, internal, technical, or regulated.
  • Source and Target Languages Specify source locale, target-language variants, markets, and any mandated terminology or spelling conventions.
  • Content and File Inventory List document versions, word or string counts, file types, embedded text, images, and any source material not yet finalized.
  • Quality and Review Level Clarify AI-assisted versus professional translation, revision, in-country review, specialist approval, and QA expectations.
  • Terminology and References Provide product names, glossaries, translation memory, style guides, screenshots, and earlier approved translations.
  • Deliverables and Deadlines Define native file formats, layout requirements, review milestones, final approver, and release date.

WORKFLOW SELECTION

Choose a Workflow Based on Content and Risk

The lowest unit price or fastest first draft is not always the most suitable option. Consider review cost, business impact, source complexity, and downstream publishing needs when selecting the workflow.

AI-Assisted Translation

May suit selected high-volume, lower-risk, or preliminary content when the quality and oversight are appropriate.

AI Translation With Professional Review

Combines productivity with a linguistic validation step for many customer-facing or recurring content types.

Human-Led or Specialist Translation

May be appropriate where technical meaning, legal interpretation, brand tone, safety, or regulatory risk requires specialized expertise.

Additional Technical Services

Desktop publishing, subtitling, software testing, file preparation, and integration are separate scope components when needed.

Build a Project Schedule Around Real Dependencies

A deadline becomes realistic only when it accounts for source availability, analysis, language-pair staffing, translation, review, formatting, and final client approval. Large programs may run languages in parallel, but a technical clarification or late source revision can affect several languages at once.

Source Readiness

Confirm what is final, what may still change, and whether editable source files are available.

Review Availability

Agree on turnaround expectations for in-country reviewers, SMEs, legal approvers, or business owners.

Critical Path

Identify tasks that must finish before the next stage can begin, such as regulatory approval or graphics extraction.

Issue Escalation

Set a contact and response process for unclear source text, terminology conflicts, or unexpected file problems.

Example: Scope a Three-Language Product Documentation Project

Suppose a product team needs one user guide in French, German, and Japanese. The scope must cover the final English source, diagrams with embedded text, three target locales, terminology, technical reviewer availability, layout expansion, and approved delivery format. The plan should identify who resolves technical questions and signs off each language.

Worked example

Use these decision stages to structure a review of the situation described above.

  1. 01
    Input

    Approved manual and reference files

  2. 02
    Workflow

    Translation, review, layout checks

  3. 03
    Output

    Three reviewed language deliverables

A Project Planning Checklist

Review these steps with your internal team and translation provider before requesting the final quote or launch date.

  1. 01
    Confirm Business Need

    Set target audience, market, reason for translation, and desired outcome.

  2. 02
    Freeze or Version the Source

    Identify the approved files and how late source changes will be tracked.

  3. 03
    Inventory and Prepare Files

    Check editable formats, embedded text, tables, screenshots, videos, and existing language assets.

  4. 04
    Set Quality and Approval Rules

    Assign required translation, professional review, subject-matter input, and final release responsibilities.

  5. 05
    Estimate Effort and Timeline

    Account for language count, complexity, volume, file preparation, reviewer availability, and nonworking days.

  6. 06
    Agree on Delivery and Change Control

    Confirm output formats, acceptance criteria, issue escalation, and how revisions will be quoted and recorded.

Agree on What Happens After Translation Delivery

A complete project plan should describe how feedback is collected, who decides whether a comment is a correction or a preference, and how approved changes are applied. Without that agreement, teams may exchange different file versions or re-review the same changes several times.

Structured Feedback

Consolidate comments into one identified review set with clear document references.

Change Classification

Differentiate errors, terminology updates, source changes, and new client preferences.

Final Acceptance

Specify the sign-off owner, required deliverables, and any subsequent publishing or technical testing responsibilities.

Budget and Timeline Factors to Review Early

Translation quotes depend on more than word count. A complete estimate should account for the workflow and the final product that must be delivered.

Volume and Reuse

Distinguish new text from repetition and translation-memory matches when a validated language asset is available.

Language and Specialist Complexity

Consider target language, subject expertise, technical terminology, and availability of qualified resources.

File Engineering and Layout

Allow for scanned PDFs, tables, graphics, subtitles, software resource files, and multilingual DTP where relevant.

Review and Dependencies

Plan in-country feedback, technical approvals, source changes, and formal sign-off without treating them as instantaneous.

What a Complete Translation Brief Should Contain

Use this framework to compare requirements and identify decisions that need an owner before work begins.

Decision Information to provide Why it matters
Content and audience Document types, use case, user profile, and technical sensitivity Determines expertise and workflow
Language scope Source language, market variants, terminology and existing assets Prevents terminology and locale mismatches
Delivery Formats, working files, publishing use and review responsibilities Avoids rework and format problems
Commercial constraints Volumes, deadline, priority and acceptance process Enables a realistic project plan

Common Mistakes to Avoid

  • Supplying PDFs when editable source files and a consistent terminology list are available.

  • Requesting translation before source owners approve the content version.

  • Failing to reserve time for stakeholder review and implementation corrections.

Frequently Asked Questions

What should I send when requesting a translation quote?

Provide representative source files, languages, audience, purpose, delivery format, deadline, glossary or references, and any certification, formatting, or review requirements.

How can I estimate translation turnaround time?

Consider content volume, language pairs, complexity, available source files, specialist review, multiple languages, and internal approval stages. Ask for a schedule based on the actual scope.

Do I need translation memory for a one-time project?

Not necessarily, but existing approved translations and terminology can still improve consistency. Repeatable content programs benefit especially from maintained language assets.

Should an internal reviewer examine every translation?

The review model depends on content risk and business requirements. Assign a clear reviewer for important language, technical, branding, or regulatory approvals.

How should source changes be managed?

Identify the approved source version and record later changes. Determine whether the change affects translation, formatting, technical testing, or review in each target language.

Can an AI workflow reduce translation costs?

It may improve throughput for suitable material, but the business case should include review, correction, formatting, governance, and any risk-related controls—not draft translation cost alone.

Get a Translation Plan for Your Project

Share your files, target languages, intended audience, and delivery requirements. Stepes can help determine the appropriate workflow and prepare a project quotation.