A translation project can have a skilled translator and still stall because the source file changed, the reviewer received an older draft or the client’s final deadline meant something different to each person. Translation project management connects those decisions. The aim is to make the current scope, file version, owner and next approval visible from intake through delivery, while preserving the context needed for financial follow-up.
Confirm the deliverable before assigning the work
Record the source and target languages, audience, subject, source files, requested output format and delivery date with its time zone. Ask whether the client needs translation only, a separate review, layout work or another agreed service. Separate the delivery deadline from internal translation and review milestones so the plan includes the whole handoff.
Identify the person authorized to clarify the source or approve a scope change. If several files are supplied, create a manifest with the agreed version of each. A clear scope makes it possible to recognize new work when a client adds pages or replaces a document after translation has started.
Make file versions and approval states separate
A newer file is not automatically an approved file. Give source, working, reviewed and delivery-ready versions a clear place in the project. Record which source version a translation was based on, who owns the next step and which version the client ultimately received. Avoid relying on filenames such as final-new-final as the only control.
Google Drive’s documentation distinguishes file activity from versions and explains that uploaded-file versions differ from Google document history. The operational lesson is to agree how your chosen file tools represent changes. Storage history can help locate a file; your project process must still establish what was reviewed and accepted.
| Project stage | Handoff evidence |
|---|---|
| Scope agreed | Source-file manifest, languages and deliverable |
| Translation ready for review | Working version and translator’s open questions |
| Review complete | Resolved comments and named approval |
| Client delivery | Identified delivered version and recipient |
| Financial follow-up | Agreed scope, approved work and exceptions |
Further reading: Google Drive: file activity and version history
Give translation, review and coordination distinct responsibilities
Name the person producing the translation, the person reviewing where review is included, and the coordinator resolving scope or deadline questions. Define how a question is raised and how the answer reaches everyone using the affected terminology or source material. A message sent to one person should not silently become a different brief for the rest of the team.
In a fictional example, a client replaces a source document after a draft is complete. The coordinator compares the agreed scope, identifies the affected work and confirms the revised plan before asking the translator to continue. The reviewer then receives the corresponding version. This prevents a technical upload from being mistaken for an authorized change in effort or deadline.
Check delivery as a project step
Before delivery, verify the requested languages, agreed file set, naming, format and approval status. Check that internal comments or working drafts are not included accidentally. Confirm the receiving contact and the method of delivery, especially if the person who requested the quote is not the person who receives the final documents.
Keep a simple record of what was sent, when and to whom. If the client requests a correction, distinguish a correction to the agreed work from a new source change or additional service. Assign an owner and response date so post-delivery questions remain connected to the project rather than beginning a separate inbox trail.
Connect project completion to approved effort and finance
Review approved time, agreed units or other scope information according to your commercial process. Resolve additional work and outstanding approvals before handing the project to finance. Project completion, client acceptance and invoice readiness may be separate decisions; define each instead of assuming a delivered file proves that every administrative step is finished.
MigiHub’s Document Translation module connects requests, files, translator and reviewer coordination, delivery and financial follow-up. It helps organize the project rather than establishing that every editing tool or file format is supported. Bring representative documents and a source-change scenario to a demonstration to confirm the formats, tools and connections needed for your implementation.
Frequently asked questions
Is translation project management the same as a translation editor?
No. Project management organizes scope, people, files, deadlines, review and delivery. Editing-tool and file-format support should be confirmed separately for the planned implementation.
How should an agency handle a revised source file?
Identify the changed version, assess its impact on work already performed and confirm the revised scope and schedule with the responsible people before proceeding.
Follow one translation project end to end
Bring a representative file set, review process and source-change example to discuss the workflow with our team.
Book a demo
MigiHub Editorial Team
Practical guidance on operations, customer relationships and service-business management.
