Global teams send local markets a locked PDF for a good reason: it protects what legal, brand and compliance have already approved. But local markets still have to make that file work for their customers. When the only way in is through the source file, even a small change means paying an agency to reopen, re-typeset and re-export a document that was never meant to be edited.
This post looks at where that cost comes from, why it keeps returning, and what PDF localization could look like when HQ and local teams both get what they need.
Why HQ locks the file in the first place
Locking the PDF isn't a mistake. It's a control, and usually a thoughtful one.
By the time a brochure reaches local markets, many careful hands have shaped it. Legal has checked the claims. Brand has signed off on the layout, colors, type and imagery. In regulated industries, compliance may have approved specific wording down to the footnote. Each of those approvals belongs to one specific version of the file.
Share an editable source file instead, and that version is hard to track. A headline gets rewritten, a claim drifts, a logo gets stretched, and soon what's in market no longer matches what was approved. A locked PDF is the simplest way to say: this is the approved version, please keep it that way.
The difficulty is that “keep it that way” and “make it work for your market” are both fair requests. Today, the file format makes teams choose between them.
A typical week in a local market
Picture a product brochure that has already cleared full approval at HQ. A local marketing manager in Brazil receives it and needs to make three changes:
swap two product images for ones that resonate with local customers
update a pair of outdated citations
remove a product line that isn't sold in that market
None of that is translation. It's adaptation: small, specific, low-risk changes that have little to do with language and everything to do with access. Without the source file and the design software, the request goes to an agency or waits until someone at HQ has time. Either way, the person who knows their market best can describe the change but can't make it.
What the round-trip looks like
The details vary by company, but the shape is familiar.
The request. The Brazil manager writes a brief covering the images, citations and section to remove, and marks up the PDF by hand.
The source hunt. The agency or HQ designer needs the original design file and its linked assets. If those sit with another agency or in an old project folder, someone has to find them first.
The rework. A designer swaps the images, edits the citations and removes the product section. Removing content means reflowing the surrounding pages, so the rest of the layout shifts too.
The check. Because the layout moved, someone has to confirm that nothing else broke: page breaks, captions, footnote numbering, the legal text on the back page.
The re-export. A new PDF comes back. The manager reviews it, spots one more thing, and the loop begins again.
Very little of that time goes into the change itself. Most of it is queueing, hand-offs and re-checking a layout that never needed to move. And nobody in this chain is doing anything wrong: the designer is working from a ticket, the local manager is working around a lock, and HQ is protecting an approval. The process simply asks capable people to work around a file.
Why it repeats every time
The real cost isn't a single round-trip. It's that the round-trip is tied to the file rather than to the change.
When HQ updates the brochure next quarter, Brazil receives a fresh locked PDF and makes the same three adaptations again, as does every other market with its own list. None of this work is hard. It just never stays done.
Translation vs. adaptation
It helps to separate the two, because they call for different owners and carry different risks.
Translation | Adaptation | |
|---|---|---|
What changes | The language of the text | Images, citations, product lines, local contact details, market-specific sections |
Who should do it | Linguists, AI translation with human review, in-market reviewers | The local marketing team, within limits HQ sets |
Risk level | Varies: claims and regulated wording need careful review | Usually low, as long as approved claims and brand elements stay untouched |
What it needs from the file | Text that can be translated without breaking the layout | Specific, defined areas that can be edited without breaking the layout |
Notice that both columns end in the same place. In each case, the hard part isn't the content. It's getting into a designed file and back out again without breaking it.
What changes when the PDF stays whole
So what should this look like? To be clear from the start, this section describes where things are heading, not something you can switch on today.
Local teams edit directly in the real layout, not in a flattened copy or extracted text, so a small change stays small.
HQ keeps the rules on what can and can't be touched, so the protection of a locked file doesn't disappear. It simply stops being the only option.
The agency step falls away for routine adaptation, because the barrier was never the content. It was the file format.
In that model, HQ still owns the approved version. It decides, element by element, which parts stay fixed and which parts each market may adapt. Legal and brand keep their assurance, designers focus on work that needs a designer, and local teams stop filing tickets for changes they're already trusted to make.
What you can do today
You don't need to wait for that future to reduce the round-trips. A few changes help right now.
Translate with the layout intact
A common habit is to copy text out of the PDF, translate it in a document or spreadsheet, then pay someone to re-typeset it: the same rebuild loop, applied to language.
With Smartcat, you can translate designed PDFs and keep the layout. AI PDF translation handles the first pass, glossaries keep product names and approved terms consistent, and AI review and QA agents help catch issues before a human reviewer looks. Reviewers then check the translation in the real layout, so they see each page the way the reader will. There's no copying out and no re-typesetting, so the people closest to the market can focus on judgment rather than formatting.
Write down what's adaptable
Most local requests fall into a short list: images, citations, contact details, product availability. Agree with legal, brand and compliance which of these local teams may change and which stay off limits, such as claims, logos and regulated wording. Even before any tool enforces it, a written rule turns each request from a negotiation into a checklist.
Keep a change log per market
Record what each market changed and why. When HQ updates the source, you can reapply those adaptations instead of rediscovering them, and compliance gets a clear record of how each local version differs from the approved one.
Batch adaptation requests
If adaptation still goes through an agency, collect changes per market for each source update and send a single brief. You pay for one round-trip instead of several, and the designer sees the full picture at once.
What we're building next
We're working on letting local teams make exactly this kind of market-specific edit directly, inside the rules HQ sets, without a round-trip through an agency or a ticket queue. This isn't available yet, it's what we're building toward, but it's the direction every conversation we've had about this points.
Until then, the quickest win is the one that already works: stop rebuilding PDFs just to translate them. And if you'd like to see where the rest of your content process stands, from approvals to local adaptation, take the Market Adaptation Assessment.
Frequently asked questions
Why do global teams send local markets locked PDFs?
To protect content that legal, brand and compliance have already approved. A locked file makes the approved version unmistakable and keeps claims, branding and regulated wording from drifting out of step with that approval.
What's the difference between translation and adaptation?
Translation changes the language of the text. Adaptation changes elements such as images, citations or product lines so the content fits a specific market. Adaptation often involves no translation at all, but it still requires a way into the file.
Can local teams edit approved PDFs in Smartcat today?
Not yet. Rule-based local editing of approved files, such as swapping images or removing a product section within limits HQ sets, is what Smartcat is building toward. It isn't available today. What you can do now is translate designed PDFs with the layout kept and review the translation in that layout.
How can we reduce agency costs for local PDF changes right now?
Translate with the layout intact rather than re-typesetting, agree in writing which elements local teams may adapt, keep a change log for each market, and batch adaptation requests for each source update.
