Managing a DTP vendor on your Approved Vendor List is different from managing a translation vendor, and treating them the same way is where most AVLs fall short.
Foliage Solutions works inside LSPs’ AVL processes specifically as a DTP specialist entry, which means the intake criteria, the scorecard metrics, and the compliance documentation all need to reflect what actually breaks in DTP work, not a generic vendor template built around translation quality alone.
This matters for Vendor Managers building or maintaining an AVL that includes specialist DTP capacity alongside translation vendors.
Why DTP vendors need their own AVL criteria
GALA’s own guidance on vendor management makes a useful distinction: a buyer’s translation maturity shapes their vendor management approach. Less experienced buyers often default to a single vendor or a small pool managed with informal criteria. More mature buyers run structured, multi-vendor processes with defined intake, scoring, and review cycles.
DTP vendors sit awkwardly in AVLs built primarily around translation quality metrics, because the failure modes are different. A translation vendor’s core risk is linguistic accuracy. A DTP vendor’s core risk is structural: broken CAT tool round-trips, layout failures under text expansion, accessibility work that doesn’t survive translation. An AVL entry built to catch the first kind of risk will miss the second kind entirely.
The three core vendor management tasks that apply to any vendor category, finding and selecting the right resource, vetting and onboarding them properly, and maintaining the relationship over time, all need DTP-specific criteria at each stage. Selecting on translation-quality metrics alone finds you a translator, not a DTP specialist. Vetting without CAT tool round-trip testing misses the exact failure mode most likely to cost you a translation memory asset. And maintaining the relationship without DTP-specific scorecard tracking means drift in quality or capacity goes unnoticed until it surfaces on a live project.
What belongs in a DTP vendor’s AVL intake
Format capability, named specifically. Not “handles design work” but which formats: InDesign, FrameMaker, QuarkXPress, PowerPoint, e-learning formats like Storyline and SCORM. A vendor who cannot name their exact format coverage has not been asked precisely enough.
CAT tool compatibility, tested not assumed. Which CAT tools does the vendor build files to round-trip cleanly through: Trados, memoQ, Phrase, Smartling, XTM, Wordfast. This is a testable claim, not a checkbox, and it belongs in intake documentation with evidence, not just a yes.
Capacity commitment. What volume can this vendor genuinely absorb during a spike, and what is their actual surge capacity versus their steady-state capacity. A vendor who cannot answer this concretely is a single point of failure waiting to surface during exactly the week you need them most.
NDA turnaround and GDPR-compliant workflow. How quickly can this vendor execute an NDA when a new project requires one, and does their file-handling process actually meet GDPR requirements for client data, not just claim to. These sit in intake because they gate whether a vendor can even start a time-sensitive project.
What a DTP vendor scorecard should actually track
A scorecard built around translation-vendor metrics, primarily linguistic quality scores, misses what actually predicts whether a DTP vendor will cause you a problem. The metrics that matter for DTP specifically: revision rate against a Clean Delivery standard, meaning how often a file needs a fix before it can go to the client; turnaround adherence against committed capacity, not just against a quoted timeline; and TM contamination incidents, meaning how often a vendor’s file handling has introduced formatting errors into translation memory after the fact, discovered on a later project.
That third metric rarely appears on a standard vendor scorecard, because it is invisible at the point of delivery. It only shows up later, in degraded match rates on a subsequent project, and by then the connection to the original vendor is easy to miss unless someone is actually tracking it.
Why a single DTP entry on the AVL is a structural risk
An AVL with one DTP vendor is not really a vendor list. It is a single point of failure with a formal-sounding name. When that vendor is at capacity, on a deadline, or simply unavailable, there is no fallback that has already cleared intake, NDA, and compliance review, which means the fallback search happens under time pressure instead of in advance.
This does not mean every AVL needs three or four DTP vendors. It means the number should be a deliberate decision based on actual volume and risk tolerance, not an accident of never having revisited the list since the first vendor was onboarded.
The redundancy question is worth deciding deliberately rather than by default. A high-volume LSP running steady multilingual DTP work across several format types has a different risk profile than one handling occasional overflow. The first genuinely needs a second cleared vendor on standby. The second may reasonably decide that a strong primary relationship with clear surge-capacity terms is sufficient, provided that decision was actually made rather than assumed.
What Foliage provides as an AVL entry
Named format coverage across 31+ formats, tested CAT-tool compatibility across the major tools LSPs actually use, documented capacity for surge volume, and a track record against a Clean Delivery standard: publication ready on first handback, zero revision requests as the measurable target, not an aspiration.
On compliance specifically: NDA execution is not a multi-week process, and our file-handling workflow is built around GDPR-compliant data handling as a baseline, not an add-on negotiated per project.
We also document our own scorecard-relevant metrics proactively, rather than waiting for a Vendor Manager to build the tracking from scratch. That includes the TM-contamination-relevant metric most standard intake processes miss: how our file preparation protects the CAT-tool round-trip specifically, not just how the finished file looks.
This proactive documentation exists because we would rather a Vendor Manager evaluate us against real numbers than take a general capability claim on faith. An AVL entry is only as useful as the accuracy of what is in it, and that accuracy is the vendor’s responsibility to maintain, not something to leave for the next audit cycle to catch.
A practical intake checklist
For a Vendor Manager building or auditing a DTP entry on an AVL, five questions cover most of what matters: which formats, named specifically, not generally. Which CAT tools, with evidence of round-trip testing, not just a claim. What is genuine surge capacity, not steady-state capacity. How fast can this vendor execute an NDA and confirm GDPR-compliant handling. And what does this vendor’s own data show about revision rate and turnaround adherence, if they track it at all.
A vendor who has clear, specific answers to all five has been managing their own quality proactively. A vendor who answers vaguely on more than one of these is asking you to discover the gap during a live project instead of during intake.
Consider two DTP vendors responding to the same intake questionnaire. One lists InDesign, FrameMaker, and PowerPoint by name, states they test against Trados and memoQ specifically with documented round-trip checks, and quotes a same-day NDA turnaround with a GDPR-compliant file handling policy they can share on request. The other lists InDesign and general Adobe software, says they are compatible with most CAT tools without naming which ones or how that is verified, and takes NDA requests to their legal team with no committed timeline. Both might pass a generic vendor questionnaire. Only one has actually shown you what happens when a real deadline arrives.
How often to actually review the entry
A once-a-year review cycle is a reasonable default for most AVL entries, timed to coincide with a broader vendor audit rather than run as its own separate process. Two events should trigger a review outside that schedule regardless of timing: a vendor missing a committed capacity threshold on a live project, and any change in the vendor’s own tooling or team that could affect CAT tool compatibility or format coverage.
The review itself does not need to repeat the full intake process. It needs to confirm that what is documented on the AVL entry still matches reality: the same named formats, the same tested CAT tools, the same actual capacity, not the capacity that was true when the vendor first onboarded. A five-minute confirmation call catches most drift before it becomes a live-project surprise.
Building this into a review cycle, not a one-time intake
AVL entries that never get revisited become stale. A DTP vendor’s actual capacity, format coverage, and quality track record can shift meaningfully over a year, and an AVL that treats intake as a one-time gate rather than an ongoing review misses that drift until it surfaces as a problem on a live project.
An AVL is only as strong as its weakest documented entry, and a DTP specialist entry built on generic vendor-questionnaire answers is often exactly that weak point, discovered at the worst possible moment rather than caught during a routine review.
Talk to Foliage Solutions about what an AVL-ready DTP vendor entry should look like for your specific volume and compliance requirements.