Single-source publishing is a production approach where one structured, validated file is the authoritative master for a title. Every output (the print-ready PDF, the accessible ePub3, the audiobook assets, the ONIX metadata feed) is generated from that single source rather than maintained as a separate file. The content is authored once, structured once, and then transformed automatically into each required format.
The alternative is the approach most publishers still use: a layout file optimised for print, a separate export or conversion for digital, manual preparation of metadata, and a separate recording or text-to-speech process for audio. Each output is maintained independently. When content changes, whether an author correction, a legal amendment, or an updated figure, that change must be applied to every file individually. Errors get introduced. Files drift out of sync. The cost of corrections compounds with each additional format.
The structured source at the centre of a single-source workflow is typically XML, a format that makes the role of every element explicit. A heading is marked as a heading, not just as large bold text. A table cell is associated with its row and column headers, not just positioned on a grid. An exercise answer is tagged as an answer, not just placed below the question. This explicit structure is what allows automated pipelines to generate each output format correctly: the transformation rules know what each element is and how to handle it in each context.
For publishers managing multiple formats, the operational benefit is significant. A correction applied to the source propagates to all output formats automatically. Accessible ePub3 is generated by default because the structure required for accessibility is already present in the source. ONIX metadata can be generated from structured title information rather than keyed separately. For educational publishers managing multi-edition titles, or professional publishers running subscription products with frequent update cycles, single-source is not a nice-to-have but the only approach that keeps production costs manageable at scale.
Adopting single-source publishing requires an upfront investment in content modelling: defining what the structure of your content should be, and how each element maps to each output format. It also requires production tooling and template development. The return on that investment depends on how many titles you publish, how many formats each title requires, and how frequently content changes. For publishers in the right position, it typically pays back within one or two production cycles.
This whitepaper sets out the workflow in detail, including how to assess whether your current content is a good candidate for single-source production, what the transition looks like in practice, and how to avoid the common mistakes that cause single-source projects to stall. If you are evaluating this approach for your list, we are available to discuss your specific situation before you make any commitments.