EPUB Production Outsourcing for Publishers

EPUB Production Outsourcing for Publishers

Publishing teams usually consider outsourcing when the workload begins to exceed internal capacity.

The pressure may come from a growing backlist, a busy frontlist schedule, new accessibility requirements, or titles that need more specialist production work than the in-house team can absorb.

Outsourcing can solve that capacity problem. But it can also create new problems if production standards, QA, and approval are not clearly defined.

For publishers, the goal should not be to hand over control. It should be to add production capacity while keeping control of quality.

When does EPUB production outsourcing make sense?

EPUB production outsourcing is useful when the volume or complexity of work starts to affect schedules, quality, or internal resources.

A publisher may need support for a short production peak, a long-running backlist programme, or a group of technically demanding titles.

Typical situations include a backlog of titles waiting for conversion, accessibility remediation work, large-scale ebook production, or academic books with complex tables, notes, indexes, images, and cross-references.

Content created for printed books can also need structural changes when it moves into reflowable EPUB. The digital version must work across different screen sizes, reading systems, and user settings.

This means page count alone is not a reliable way to estimate the work.

A 250-page novel and a 250-page academic title with tables, equations, notes, and images may require very different production effort.

Outsource production, not publishing standards

A strong outsourcing model keeps an important distinction clear.

The production partner can take responsibility for conversion, file preparation, QA support, and corrections.

The publisher should continue to own the specification, accessibility requirements, acceptance criteria, and final approval.

That division creates a healthier workflow.

Instead of asking a vendor to “make an EPUB,” the publisher defines what an acceptable EPUB should contain.

That may include semantic structure, navigation, metadata, image treatment, notes, tables, validation, accessibility requirements, and delivery rules.

The clearer these expectations are before production begins, the easier it becomes to maintain consistency across hundreds or thousands of titles.

Classify titles before they enter production

One practical way to control a large EPUB programme is to classify titles by complexity.

A simple narrative book may follow a standard workflow. A title with tables and footnotes may need more review. A STEM title with equations, complex figures, or multi-level tables may need specialist production and additional QA.

A useful model is:

This helps publishers estimate cost, schedule, staffing, and QA more accurately.

It also prevents complex books from being treated like routine conversion work.

Use a representative pilot before scaling

Large outsourcing programmes should begin with representative titles, not the easiest title in the catalogue.

A good pilot should contain some of the conditions that will appear during full production.

For example, the sample could include a straightforward book, a table-heavy title, a title with notes or indexes, and a source file that needs more detailed remediation.

The pilot gives both teams a chance to confirm:

how the specification is interpreted, how complex content is handled, what QA is performed, how defects are reported, and how corrections are returned.

Once that process works consistently, the publisher can release larger batches with much greater confidence.

For large legacy catalogues, Gentize's guide to accessible EPUB backlist remediation also explains why older files often need more than format conversion. They may require work on structure, navigation, accessibility metadata, images, and validation. Gentize Innovations

Good EPUB QA goes beyond visual appearance

An EPUB can look correct and still contain structural problems.

A heading may look like a heading without being marked correctly. A footnote may display properly but have poor return navigation. A table may look identical to print but give a screen-reader user very little context.

Quality assurance should therefore review the EPUB as a digital publication, not just as a visual copy of the source.

Useful checks include semantic structure, navigation, metadata, internal links, images, notes, tables, and technical validation.

This also protects the reading experience. A valid EPUB is important, but readers should also be able to move through the publication without broken links, confusing navigation, or missing context.

Gentize's guide to EPUBCheck vs Ace by DAISY explains the difference between EPUB conformance checks, automated accessibility checks, and human accessibility QA. Gentize Innovations

Build accessibility into the workflow from the beginning

Accessibility should not be treated as a repair step after ordinary EPUB production has finished.

Many accessibility decisions are structural.

Heading levels, table markup, image descriptions, notes, page navigation, language information, and metadata may all be affected by decisions made during conversion.

If those decisions are wrong, repairing the file later adds extra work.

It is more efficient to define the accessibility requirements before production starts.

Publishers managing older catalogues may also need to decide which titles can be remediated and which need deeper reconstruction.

Gentize's accessibility work includes EPUB remediation and assistive-technology testing, while its publishing services include EPUB3, KF8, and reflowable ebook production. Gentize Innovations

Scanned source files need a different production path

Scanned backlist titles create another layer of risk.

OCR can recover text from a scanned page, but OCR output should not automatically become publication-ready EPUB content.

A missing decimal point, incorrect character, broken reading order, or damaged table can move directly into the final ebook if the source is not checked.

For scanned material, the workflow may need to look more like:

Scan → OCR → Verify → Structure → EPUB Production → QA

The required level of checking depends on how the text will be used.

If OCR output will become an EPUB, structured XML, or a reissued book, the quality requirement is higher because recognition errors become part of the published content. Gentize's OCR quality assurance for digitization guide covers this issue in more detail. Gentize Innovations

Corrections should always include retesting

Defects are normal in complex production programmes.

What matters is how they are handled.

A clear correction process should identify the issue, assign ownership, return the corrected file, and confirm that the change solved the problem.

Retesting is important because one fix can affect another part of the EPUB.

A change to navigation may affect links. A structural correction to a table may affect the way content is announced by a screen reader. A metadata change may introduce another validation issue.

The workflow should therefore be:

Find → Correct → Retest → Approve

not:

Find → Correct → Deliver

Publishers should also look for repeated defects. If the same issue appears across several titles, it may point to a weak production rule or an unclear part of the specification.

Fixing the process is more valuable than correcting the same problem title by title.

What should publishers ask an EPUB production partner?

Vendor selection should focus on process as much as capability.

Instead of asking only, “Can you produce EPUB 3?” ask how the team handles different levels of complexity.

Instead of asking, “Do you perform QA?” ask what the QA process actually checks.

And rather than asking whether accessible EPUB is available, ask how accessibility is built into production, how it is tested, and what happens when a problem is found.

A useful production partner should be able to explain:

• how titles are classified;
• how complex content is handled;
• what technical checks are performed;
• how accessibility is reviewed;
• how defects are corrected;
• how corrected files are retested.

These answers give publishers much more information than a service list alone.

How Gentize supports EPUB production at scale

Gentize Innovations supports EPUB 2, EPUB 3, accessible EPUB, OCR, XML conversion, complex publishing content, screen-reader testing, keyboard testing, and human accessibility QA.

Gentize has completed a 35,000+ title large-scale academic digitization project covering scanning, OCR, EPUB, POD, and accessible PDF. Pasted markdown

That type of project depends on more than conversion capacity.

Large publishing programmes need clear production rules, controlled batches, exception handling, QA, corrections, and reliable delivery.

For publishers that need EPUB3 and reflowable ebook production as part of a wider publishing workflow, Gentize's Book Publishing service provides the relevant production route. Gentize Innovations

Final takeaway

EPUB production outsourcing works best when the publisher keeps control of the standards and uses an external partner to add capacity and specialist production support.

The workflow can remain simple:

Specify → Pilot → Classify → Produce → Validate → QA → Correct → Retest → Approve

The objective is not to move work outside the business at any cost.

It is to create a production model that can handle more titles without losing consistency, accessibility, or quality.

For publishers facing a growing EPUB backlog, frontlist pressure, or complex digital-production requirements, that distinction matters.

Need additional EPUB production capacity?

If your publishing team has an EPUB backlog, a large backlist programme, accessibility work, or a group of complex titles, Gentize can begin with representative files before the project is scaled.

Share a sample title or production requirement to discuss the right EPUB production workflow.