A client sends a scanned contract and asks for a translated PDF that looks like the original. The word-count tool finds nothing, the translator can’t edit the scan, and the layout work appears only after the translation is underway. If your quote treats that file as ordinary translation, your agency can end up absorbing several different jobs under one word rate.
Yes, translation agencies should charge DTP separately when a scanned-document project requires OCR, file preparation, layout reconstruction, or formatting QA beyond translation. A scan doesn’t automatically call for every one of those tasks, though. Review the actual file, separate the work into clear stages, and price the scope the client needs rather than adding an unexplained scan surcharge.
The distinction matters because a client might need a plain translated text file, an editable document, or a PDF that follows the source layout. Those are different deliverables, and they can take different amounts of work. This guide explains how to scope them, choose a pricing unit, build a client-ready quote, and avoid charging for work the project doesn’t need.
What does DTP for a scanned document include?¶
DTP, or desktop publishing, is the work of preparing and formatting a document for delivery. On a scan-based translation job, DTP can include extracting text, cleaning the file for translation, rebuilding the translated layout, and checking the final document. The exact scope depends on the input and the output the client requests.
A scanned PDF typically contains an image layer rather than selectable, searchable text. OCR, or optical character recognition, identifies the text in that image and can make it editable for later processing. RWS distinguishes scanned PDFs from text-generated, searchable PDFs in its PDF processing guidance.
OCR doesn’t mean the whole job is done. A tool can recognize text but still leave a document with broken reading order, incorrect tables, missing page breaks, or formatting that needs work. RWS notes that complex layouts and scanned PDFs may need manual extraction into an editable format, so an agency shouldn’t quote on the assumption that OCR alone will produce a usable file.
A practical scope separates the work into three stages:
- OCR or manual text extraction. Identify text in the images and create an editable working file. Inspect recognition, reading order, and any unclear content.
- Pre-translation preparation. Clean up the extracted file so the translator can work with it. That can include page-break and formatting adjustments, and removing layout noise that would get in the way of translation.
- Post-translation DTP and QA. Rebuild or adjust the translated layout, check the file against the source, and review the final output for formatting problems.
The stages don’t always require separate line items. A small, clean scan may need very little file preparation. A complex document might need manual work at both ends of the translation process. Separating the stages in your estimate helps you explain that difference and revise the quote if the client’s requested output changes.
Trusted Translations describes a scanned-photocopy workflow that includes OCR and word counting, pre-DTP cleanup, and post-DTP layout work. The agency also distinguishes scanned photocopies from native design source files when scoping DTP, because the scan doesn’t contain the original editable source. See its DTP quoting workflow.
That distinction is especially useful when a client compares your quote with a word-rate estimate. A word count covers translated content. It doesn’t account for the time needed to turn image pages into an editable file, repair an inaccurate OCR result, or rebuild a layout after translated text changes its length.
Why can’t one scanned-document surcharge fit every file?¶
The word “scan” describes how a document was supplied, not how much work it will take to process. A clear, straight scan of simple pages can be much easier to handle than a low-quality photocopy containing columns, tables, folds, or handwriting. The price should reflect those differences.
RWS recommends a minimum scan resolution of 300 dpi to improve OCR, and warns that lower resolution has a negative effect on recognition. The same guidance identifies skewed pages, poor resolution, background and contrast problems, folds, stains, and handwriting as factors that can cause recognition errors or require manual extraction (RWS PDF processing guidance). The recommendation is technical guidance, not a guarantee that every scan at that resolution will produce a clean editable file.
A scan can also appear clear at a glance but still create extra work. A page might have a readable main paragraph and a faint stamp, dense table, or handwritten note. A client might consider those marks important, while a basic OCR pass may not capture them reliably. Make unclear areas visible during review rather than treating them as translation-ready text.
Layout complexity matters too. A page with a single text column is different from a page with nested tables, multiple columns, captions, logos, and tightly placed footnotes. Even when OCR finds the words, an agency may need to reconstruct the relationship between those elements so the translated version stays readable.
The target language can affect layout effort as well. Translation can change the amount of text, so the final layout may need reflow, resizing, or typography adjustments. Stepes describes those kinds of layout changes as DTP work that can sit outside the translation scope in its translation cost guide. Don’t assume that a translated file will fit into the same spaces without adjustment.
A useful example is a two-page scanned form with a clean background and short printed labels. The agency may be able to extract the text, prepare a simple working file, and return a translated version with modest formatting changes. A second file with the same page count could contain dense tables, faded text, and handwritten entries. The page total is identical, but the work is not.
Quoting pitfall: a flat surcharge per page can look simple and still be misleading if the pages vary widely. One page might need only a light check, while another needs manual extraction and substantial reconstruction. Price the page rate from a defined page profile, or move the uncertain work to an hourly estimate.
The client can help reduce avoidable work by providing a native source file or a searchable PDF when one exists. RWS recommends working from native files where possible and choosing searchable PDFs instead of scanned PDFs when a PDF must be used (RWS PDF processing guidance). A scan may be the only source available, but asking about originals can prevent needless reconstruction.
Which documents and details should you request before quoting?¶
A defensible DTP quote starts with the source file and the intended deliverable. A page count alone doesn’t tell you whether the agency is extracting text, correcting OCR, preparing a translator’s file, rebuilding a layout, or doing all of those things.
Request the items in this checklist before fixing a price:
| What to request | Why it matters to the quote |
|---|---|
| Complete scan, including every page | Missing or out-of-sequence pages can change the amount of extraction and layout work. |
| Native source or searchable PDF, if available | An editable original can avoid manual reconstruction from an image. |
| Page count and file type | These establish the size and basic format of the job, but don’t determine effort by themselves. |
| Target language and required output | The language and deliverable affect layout needs and the work the client expects. |
| Sample pages from different sections | A sample should show unusual tables, forms, images, or handwritten areas, not just the easiest page. |
| Fonts, images, and supporting assets, if available | Source materials can help the agency reproduce a layout more accurately and cost-effectively. |
| Turnaround expectations | A tight schedule can affect planning and the quote after file review. |
| Required level of layout matching | “Editable Word file” and “match the original page design” are not the same brief. |
| Treatment of unclear text | Agree on whether the agency should flag illegible areas, request clarification, or leave them marked. |
| Final file format and review requirements | The client may need a formatted PDF, an editable file, or both, with different QA expectations. |
Globalization Partners International identifies page count, source and target languages, file format, damaged or non-editable source files, anomalies, and QA as inputs to multilingual DTP estimates. The company also notes that source files and auxiliary materials such as fonts and images can support a more accurate, cost-effective quote (GPI budgeting guidance).
Ask for representative pages rather than relying on a single “typical” page chosen by the client. A file can shift from simple prose to a complex schedule or a page with stamps and handwritten notes. Checking those differences lets you describe the quote as an estimate based on the full file, not just a quick look at its cover.
A sample review should answer practical questions. Can you select any text in the PDF? Are all pages upright? Are the page edges and text visible? Does the file include tables, columns, stamps, seals, or writing by hand? Can you tell where headings and footnotes belong? Does the client want a visually similar output or simply an editable translation?
Trusted Translations gives a clear example of why the deliverable matters: scanned photocopies have no original editable design file, so a project may need work before translation and layout work afterward. Its DTP service quoting article describes that sequence. Use the same distinction in your own intake form, even if your agency combines the charges on the final invoice.
Quoting pitfall: don’t promise a layout-matched file before checking whether the source provides enough information to reproduce it. A scan can show the appearance of a page, but it doesn’t necessarily provide its original design assets, fonts, or editable structure.
How should an agency structure a separate DTP quote?¶
A quote should tell the client what the fee buys. “Scan surcharge” doesn’t explain whether the charge covers OCR, cleanup, layout reconstruction, QA, or a mix of tasks. Clear line items let the client choose a deliverable and make scope changes easier to discuss.
A simple estimate can separate three categories:
- OCR and text extraction: recognition, manual extraction where needed, and a check of the captured text.
- Pre-translation file preparation: cleanup of the working document so the translator can read and translate it efficiently.
- Post-translation DTP and QA: layout adjustment or reconstruction, output preparation, and a final check.
Those lines can be grouped where the job is small, but the estimate should still state what is included. For example, an agency can explain that the DTP fee covers an editable file with basic formatting, while exact visual matching or manual treatment of unclear handwriting falls outside the current scope.
Trusted Translations describes pre-DTP this way: “These types of projects will require pre-DTP, in which page breaks are removed and the text formatting is accommodated as best as possible so that the translator can begin his or her work.” Source: Trusted Translations
The point for your quote is that preparation occurs before translation, not just at the end. When a file needs cleanup for a translator to work on it, hiding all of that labor under post-translation DTP makes the estimate harder to explain.
Build the estimate around work units the client can understand. Translation is commonly measured by word count; DTP is often measured by pages, slides, sheets, or graphics. GPI explicitly distinguishes those measurement approaches in its multilingual DTP budgeting guidance. A separate DTP unit keeps the translation rate from carrying a cost that has little to do with the number of words translated.
Add assumptions to the quote. State that the estimate is based on the supplied file, specify whether manual extraction is included, say what kind of editable output the client will receive, and identify any known pages that need review. If the scan is unreadable in places, don’t imply that the agency can reconstruct content that isn’t visible.
Scope boundaries are useful, not unfriendly. An agency can state whether its price includes one final layout check, whether the client will receive a PDF or an editable source file, and how it will handle unclear marks. Define how new files or additional pages affect the quote. A client who understands the assumptions can compare options without treating every DTP estimate as the same service.
For higher-complexity work, keep time estimates separate from fixed-price assumptions. GPI notes that turnaround expectations can affect pricing after file evaluation and resource planning (GPI budgeting guidance). A rush request can change the resources available for a job; don’t silently absorb that effect into the translation word rate.
A defensible quote doesn’t need a long explanation. It needs enough detail for the client to see the difference between translation and file work. Describe the source condition, the requested output, the work stages, the pricing unit, and the assumptions that might change the estimate.
Should scanned-document DTP be billed per page or per hour?¶
Per-page and hourly pricing can both work. The better choice depends on how consistently the work repeats across the file and whether you can estimate the time before processing starts.
| Pricing model | Best fit | Main advantage | Main risk |
|---|---|---|---|
| Per page | Short materials with predictable page density and similar layouts | Clients can understand the fee from the page count | Pages with different layouts or scan quality can take very different amounts of work |
| Per hour | File preparation, desktop publishing, localization engineering, and complex formatting | The estimate can reflect the actual variety of work | The client needs a clear scope and a way to understand the time spent |
| Mixed model | A stable file with a few pages that need extra attention | Standard pages can use a set unit while unusual pages get separate treatment | The quote must define which pages count as exceptions |
Stepes says hourly pricing is commonly used for services that aren’t measured well by source word count, including file preparation, DTP, localization engineering, and complex formatting. The guide also describes per-page pricing as useful for short official materials with predictable page density, but less precise when pages vary in text density, tables, or layout (Stepes translation cost guide).
For a consistent set of forms, a page rate may be easy to apply. The agency can inspect a representative sample, establish what counts as a standard page, and note which exceptional pages need individual review. For a mixed file with tables, damaged scans, and different layouts, an hourly estimate can be more transparent than pretending each page has the same cost.
Available vendor figures can provide context, but they are not a market tariff. Logitope’s current pricing page lists manual PDF or image-to-Word conversion at USD 1-3 per page. The page also describes a separate basis of 2%-6% of the translation cost for manual conversion. Those figures use different units and scopes, so don’t treat them as interchangeable or as the price of complete post-translation DTP; confirm the task and quote directly with the vendor (Logitope conversion pricing). The pricing page’s publication date isn’t stated, so the figures should be treated as current page indications accessed during research, not permanent rates.
A public-sector contract schedule dated or posted in 2023 lists DTP/OCR formatting at USD 25.39 per hour for Spanish and USD 35.46 per hour for other languages. The prices belong to that specific contract schedule and aren’t universal agency rates (TIN 572 rate sheet). The figures are useful as an example of hourly billing, not as a rate card to copy.
Logitope writes, “Per-page prices for conversion are generally between USD 1 and USD 3.” Source: Logitope
That figure is for the vendor’s described conversion work. It isn’t evidence that a translation agency can reconstruct every scan and deliver a checked, translated layout for the same amount. Keep conversion, translation, and post-translation DTP distinct when comparing prices.
Laydox says DTP/OCR providers commonly quote per page or per hour, with price depending on page count, source complexity, target languages, and turnaround; its quote is fixed after reviewing source files (Laydox service page). The practical lesson is straightforward: don’t fix a price based on a page count when the file itself can change the work estimate.
A mixed model suits some projects. You might quote a defined rate for standard pages, then state that damaged pages, complex tables, or manual extraction are billed separately after review. Use that approach only when the quote makes the standard and exceptional page types easy to distinguish.
Which workflow option fits your agency?¶
Agencies can handle scanned-file work in-house, use a specialist, or use a document-translation tool for part of the workflow. The right choice depends on the file, the deliverable, and the kind of human review the agency needs to provide.
Option 1: Handle extraction and DTP in-house¶
In-house work makes sense when your team can review the scan, correct extraction, prepare a working file, and produce the output the client expects. Your agency controls the handoffs and can keep the preparation and layout stages close to the translation team.
The challenge is estimating effort consistently. If different project managers define “DTP” differently, two clients with similar scans may receive different scopes. Set a shared intake checklist and quote template. Ask staff to record whether the work involved OCR cleanup, manual extraction, layout repair, or final QA so future estimates have a more useful basis.
In-house handling also needs a clear response to unclear source content. OCR can misread numbers or names, while a poor image may not show the original text well enough to confirm it. The agency’s process should distinguish a recognition error from an unreadable source. A translator or DTP operator shouldn’t have to guess at missing content.
Option 2: Use a specialist for conversion or DTP¶
An outside DTP provider can take on conversion, reconstruction, or layout work when the agency doesn’t have the right capacity in-house. A specialist quote should define whether the service is only PDF or image conversion, or includes post-translation reconstruction and QA.
Check the scope before comparing the price. Logitope describes manual conversion into Word, reproducing formatting such as tables, columns, and automatic tables of contents, and checking converted files with a second person, with special attention to numbers extracted from scans (Logitope conversion service). That description can help agencies formulate questions, but the service’s stated scope shouldn’t be assumed to cover every type of translated layout.
A provider may quote per page or per hour. Ask what counts as a page, whether the quote covers all supplied pages, and how the provider will treat handwriting or damaged areas. Ask whether the output is intended as an editable working file, a reconstructed client deliverable, or both.
Keep accountability clear between your agency and the provider. Your client needs to know who handles the translator’s working file, who checks the final layout, and who raises questions about unclear text. Outsourcing a stage doesn’t make the scope disappear; it changes who performs it.
Option 3: Use an online document-translation tool for a suitable job¶
ChatsControl is an online document-translation tool that supports document translation, scanned files, and formatting-focused workflows. An agency can upload a supported document, use the resulting translated file as a draft, review the source and translation side by side, and edit the result before delivery. Its built-in QA validator can check issues such as numbers, names, terminology, and omissions. The tool runs in the cloud, isn’t a CAT tool or TMS, and isn’t built for handwritten or very poor-quality scans. Its pricing uses a free tier with a character allowance and paid top-ups for heavier use; the available product information doesn’t specify a price or turnaround to quote here.
That can suit an agency that needs a first draft and a reviewable document, but it doesn’t remove the need to judge whether the scan is readable or whether the client wants a faithful layout reconstruction. A human still needs to check the translation and the output, especially where the scan has unclear text or the deliverable has strict formatting requirements.
A document tool and a full DTP service aren’t the same thing. A tool may help create and check a formatted translated document; a specialist may be needed for extensive manual extraction, damaged files, complex design work, or a client brief that requires close recreation of the original. Choose based on the requested result, not on the assumption that one workflow fits every scan.
| Option | Useful when | What to verify |
|---|---|---|
| In-house team | Your staff can manage file preparation and final layout | Estimate consistency, review responsibility, and capacity |
| DTP specialist | Manual extraction or design-level reconstruction needs dedicated attention | Exact scope, file formats, QA, and treatment of unclear areas |
| Document-translation tool | The agency wants a formatted draft and a reviewable translation workflow | Scan quality, human review, output requirements, and data handling |
How do you quote a scanned PDF translation step by step?¶
A repeatable quoting process helps your team ask for the same information, identify the same kinds of risk, and explain any separate DTP fee consistently. The process starts with the source and ends with a scope the client can approve.
- Request the complete source and deliverable brief. Ask for the original scan, any native or searchable source, target language, output format, layout expectations, and deadline. Confirm whether the client needs an editable file or a visually reconstructed document.
- Inspect representative pages. Review the whole file when possible. Check image quality, page orientation, text density, tables, columns, stamps, handwriting, and visible damage.
- Choose the extraction method. Determine whether OCR can create a usable working file or whether manual extraction is needed. Don’t assume recognition quality based on one clean-looking page.
- Estimate pre-translation preparation. Include cleanup needed to give the translator a workable document. Keep the scope separate from translation unless your quote clearly combines the services.
- Estimate post-translation work. Decide what layout repair, reflow, formatting, and output checks the requested deliverable needs. A translated text file and a layout-matched PDF require different scope.
- Pick the pricing unit. Use page pricing when the pages are consistent and predictable; use hourly pricing when layout, quality, or extraction effort varies. Consider a mixed model only with clear rules for exceptions.
- Write assumptions and exclusions. State which files and pages the quote covers, how the agency will handle unclear text, and what happens if the source or deliverable changes.
- Review the quote with the client. Ask the client to confirm the output format and the level of layout matching before work starts. A clear agreement can prevent a later dispute over what “DTP included” meant.
A practical estimate can use a short, client-facing table:
| Line item | Scope to describe |
|---|---|
| OCR and extraction | What text will be made editable and what happens when OCR isn’t reliable |
| Pre-translation preparation | Cleanup needed to create the translator’s working file |
| Translation | The agreed translation scope and its pricing basis |
| Post-translation DTP | Formatting or reconstruction included in the requested output |
| QA | The final checks included for content, numbers, and layout |
| Assumptions | Source files, page types, turnaround, and treatment of unclear content |
The checklist works as an internal lead magnet too: keep it in your quoting template and give it to project managers before they make a commitment to the client. A reusable intake process is easier to audit than a pricing rule that says only “add a fee for scans.” Agencies building broader operating procedures can also use SOPs for Translation Agencies to document who reviews files, approves quotes, and handles scope changes.
Quoting pitfall: don’t call an estimate fixed if the team hasn’t inspected the source. Laydox says it fixes its quote after reviewing source files, while also describing page count, source complexity, target languages, and turnaround as pricing inputs (Laydox). A project quote should follow the same basic discipline: review first, define the scope, then set the price.
What can go wrong with the quote or workflow?¶
The most common failure isn’t necessarily a bad OCR engine. It’s a quote that hides assumptions. A client hears “translation included,” while the agency expects to charge for layout work later. Or the agency promises an editable file without checking whether the scan can support reliable extraction.
Mistake: treating every scan as an OCR job. OCR can be useful when the text is clear, but low resolution, skew, background problems, folds, stains, and handwriting can affect recognition. RWS identifies those factors in its PDF processing guidance. Review the file and distinguish automated recognition from manual extraction.
Mistake: charging by page without defining the page. A page rate needs a known scope. Specify whether it covers one standard page, whether tables or damaged pages count as exceptions, and whether the rate covers conversion only or post-translation DTP too. Stepes cautions that page pricing is less precise when text density and layout vary (Stepes translation cost guide).
Mistake: treating a vendor’s conversion price as a full DTP rate. Logitope’s current page describes a per-page range for manual PDF or image conversion and separately mentions a share of translation cost. Those bases don’t automatically mean the vendor has priced translation, post-translation layout reconstruction, or all final QA. Clarify the service unit and deliverable before using the figure to benchmark a client quote (Logitope).
Mistake: counting OCR output as verified content. Numbers, names, and small print can be misread. Logitope says its conversion process includes a second-person check and attention to numbers extracted from scans (Logitope conversion service). Whatever QA process your agency uses, say whether it includes checking recognized content and how unclear source text will be handled.
Mistake: omitting turnaround from the estimate. A client may ask for a deadline before the team has seen the file. GPI identifies turnaround as a factor that can affect pricing after file evaluation and resource planning (GPI budgeting guidance). Review the source and capacity before promising a delivery plan.
Mistake: assuming a scan is the only source. Ask whether the client has a native document or a searchable PDF. RWS recommends those options when available because they can avoid work associated with extracting text from a scanned image (RWS PDF processing guidance). Don’t charge for reconstruction from a scan before checking whether an editable original exists.
The right warning is specific and traceable, not dramatic: OCR can fail on scan conditions that are visible in the file, and DTP prices depend on the work included. No quoted source establishes one universal rejection case or one universal surcharge. Your agency should document its own project outcomes rather than adding invented examples to justify a price.
Before sending a quote, check that the client can answer these questions from the estimate: What file will I receive? Does the fee include OCR or manual extraction? Is the layout included? What happens to unclear text? What changes the price? If the estimate leaves those points open, revise it before work begins.
FAQ¶
Should translation agencies charge a separate DTP fee for scanned documents?¶
Yes, when the client needs an editable file or layout reconstruction beyond translation. Quote OCR or extraction, pre-translation preparation, and post-translation DTP as distinct tasks, and don’t add an identical surcharge to every scan.
How should an agency price OCR and DTP for a scanned PDF translation?¶
Inspect the source, then define the work for extraction, file preparation, post-translation layout, and QA. Use hourly pricing for variable work or per-page pricing when pages have similar density and predictable layouts.
What affects the cost of recreating a scanned document after translation?¶
Page count, image quality, layout complexity, target language, output format, turnaround, and the expected level of reconstruction can affect effort. Tables, columns, damaged pages, and non-editable sources need closer review.
Should scanned-document DTP be billed per page or per hour?¶
Per-page pricing fits short materials with consistent page density and similar layouts. Hourly pricing fits complex formatting and pages with varied extraction or reconstruction needs; define the scope before quoting either way.
What information should an agency request before quoting DTP for a scan?¶
Request the complete source, page count, target language, output format, native originals and assets if available, layout requirements, and deadline. Inspect image quality and representative pages before fixing the scope.
Does every scanned PDF need manual DTP after OCR?¶
No. A clear scan may need OCR and limited cleanup, while a complex layout or damaged image can require manual extraction and reconstruction. Review the file before quoting rather than assuming either outcome.