Most project handoff checklists are generic enough to apply to any deliverable: confirm the deadline, confirm the contact, confirm the file format. A DTP handoff needs a checklist built around the specific ways multilingual files actually break, not a general project-management template with DTP’s name attached to it. Foliage Solutions built the checklist below from the failure patterns we actually see, not from a generic project-management framework.
This is written for Vendor Managers and Project Managers handing a file to a DTP vendor, or receiving one back, who want to know specifically what to check before signing off.

Confirm the target CAT tool by name
“Compatible with major CAT tools” is not specific enough to test. Confirm Trados, memoQ, Phrase, Smartling, XTM, or Wordfast by name, whichever tool the project actually uses, and confirm the vendor has tested round-trip compatibility with that specific tool, not just general familiarity with the category.
This matters because CAT tools handle segmentation, tag structure, and file export differently enough from each other that compatibility with one does not guarantee compatibility with all. A vendor who has tested against Trados specifically has demonstrated something concrete. A vendor who says they work with all major tools has made a claim that still needs testing. If you use more than one CAT tool across different projects or clients, confirm the vendor has tested each one separately, since compatibility with your most common tool does not automatically extend to a secondary one used less frequently.
Confirm text expansion has been planned into the layout
German and French routinely expand beyond the source text’s length, German by 20 to 30 percent, French by 15 to 25 percent, and a layout built without that accounted for creates rework at the review stage that a pre-planned brief avoids entirely.
This check needs to happen before layout begins, not after translation returns. A text box, column width, or table cell sized precisely around the English source has no room to absorb expansion, and discovering that after translation means resizing under deadline pressure instead of building it in from the start. Ask specifically which expansion percentages a vendor plans against for your target languages, not whether they are generally aware that expansion happens. A vendor with a real process can name the number. One without a real process will describe expansion as something they handle without specifying how.
Confirm embedded graphics have been checked for CAT-tool accessible text
Every embedded graphic, chart, or SmartArt element needs to be checked for CAT-tool-accessible text, not just the running body copy. This is the single most common source of missed content in a translated deck or document, because embedded text sits inside a graphic rather than in the obvious text flow most reviewers check first.
A diagram, chart, or infographic with text baked into a raster layer, or flattened out of an originally editable format, will not reach the translator through normal CAT-tool export. It needs to be identified and handled separately, and that identification has to happen at file intake, not discovered partway through a project. Ask specifically how a vendor scans a file for this at intake, whether it is a manual visual review of every graphic or an automated check, and what happens once flattened text is found.
Confirm the file has been tested for a full round-trip

A file that opens correctly on export can still fail on re-import if tag structure was not preserved through the translation stage. Confirm the vendor tests the full round-trip, export, translation, re-import, not just that the file opens without an error message after export.
This distinction matters because the failure this check catches is invisible at export time. It only surfaces on re-import, sometimes not even on the original project but on a later one drawing from the same contaminated translation memory. Testing the full round-trip before delivery is the only way to catch it at the point where it is still cheap to fix. Ask a vendor directly whether their QA process includes re-importing the translated file into the target CAT tool before delivery, or whether their testing stops at confirming the export completed without an error.
Confirm accessibility requirements are addressed per language
Where accessibility requirements apply, confirm they have been addressed for every target language separately, not assumed to carry over from a remediated source document. A PDF remediated for WCAG 2.1 AA compliance in its source language does not automatically stay compliant once translated. Language tags, reading order, and alt text all need to be rebuilt to match the translated version, not inherited from the source.
This check is easy to skip because a translated document can look finished without anyone verifying the accessibility layer separately. It only surfaces as a problem when the document actually gets tested against a compliance standard, usually later than anyone would prefer.
Confirm the delivery includes documentation of what was checked
Confirm the delivery includes documentation of what was checked, not just the finished file. A Clean Delivery standard means the file is publication-ready and the vendor can show you why, not just assert that it is.
This documentation does not need to be elaborate. It needs to exist, and it needs to be specific: which CAT tool the file was tested against, what expansion planning was applied, whether embedded graphics were checked, and what the accessibility review covered if applicable. A vendor who can produce this documentation on request has a real process. A vendor who cannot is asking you to trust a claim rather than review evidence.
This documentation also has a use beyond the immediate handoff. When a project surfaces a problem months later, degraded fuzzy match rates traced back to a specific file, a compliance audit flagging an accessibility gap, this documentation is what lets you trace the issue back to its source instead of guessing. Without it, every retrospective investigation starts from nothing.
Why six checks, not a longer list
A checklist with too many items becomes a checklist nobody actually completes under deadline pressure. These six cover the specific failure modes that account for the overwhelming majority of DTP rework we see: CAT tool mismatch, unplanned text expansion, missed embedded text, broken round-trip integrity, incomplete accessibility work, and undocumented quality claims. Adding more generic project-management items, deadline confirmation, contact details, file naming conventions, does not add protection against the failures that actually cause rework. It adds length.
A shorter, DTP-specific checklist that someone actually runs through every time is worth more than a longer generic one that gets skipped when a deadline is tight. This is a real trade-off worth naming directly: a checklist is only useful if it survives contact with a real deadline, and a list too long to complete under time pressure gets abandoned exactly when it matters most.
Using this checklist on both sides of a handoff
A Vendor Manager can use this list to evaluate a prospective vendor’s process during intake, asking how each item is handled before committing a project. A Project Manager receiving a completed file back can use the same list as a final review before it goes to a client, confirming each point rather than assuming the vendor covered it.
Used on both ends, before the project starts and before it ships, this checklist catches the specific problems that generic project checklists are not built to catch at all. It also creates a shared vocabulary between Vendor Manager and vendor: when both sides are working from the same six points, a disagreement about whether a file is ready becomes a conversation about a specific item on a shared list, not a vague dispute about quality.
What happens when a vendor cannot answer these directly
A vendor who answers all six checks vaguely, in general terms rather than specifics, is not necessarily a bad vendor. They may simply not have formalized a DTP-specific process, relying instead on individual team members’ experience and judgement rather than a documented standard. That can work, until a key person is unavailable and the informal knowledge does not transfer cleanly to whoever covers for them.
This is worth raising directly during vendor evaluation rather than assuming it either way. Ask not just what the vendor checks, but whether that checking process is documented somewhere any team member could follow, or whether it lives primarily in one or two people’s heads. The answer tells you something about how consistent your experience will be as volume grows or as staff changes on the vendor’s side.
How Foliage builds this into every delivery

Every file we deliver is checked against exactly these six points before it reaches a client: named CAT-tool compatibility tested and confirmed, expansion planning built into the brief from the start, embedded graphics reviewed for translatable text, full round-trip testing completed, accessibility requirements addressed per language where applicable, and documentation provided showing what was checked, not just asserted.
This is the same checklist internally that we would want a vendor to hold themselves to if the roles were reversed, and it is the standard we expect a Vendor Manager to hold us to during evaluation, not just after a project has already started.
Talk to Foliage Solutions about what a DTP handoff checklist should look like for your specific workflow.

