Explainer
The Document Assembly Line
The Line
A Relay Race Nobody Chose
No one designs this workflow; it accretes. Drafting happens in Word because that's where review lives. Design happens in InDesign because Word output doesn't look published. The PDF exists because that's what InDesign exports, and the CMS upload exists because the website needs something. Each step was locally reasonable. The result is a document that passes through four tools and three handoffs on its way to a reader — and at each handoff, the previous version stops being authoritative without anyone declaring it.
The losses are predictable. The late edit that misses the design pass. The table a designer tidies into a different meaning. The web page paraphrased from the PDF until the two quietly disagree. And because a correction means re-running the entire line, small fixes queue for months waiting on an “edition” big enough to justify the labor.
The Alternative
One Source, Every Output
Single-source publishing retires the relay by making presentation a rendering step instead of a manufacturing stage. The document lives once, in a structured authoring system, where drafting and review happen. At publish time, templates generate every output from that one source: the typeset PDF, the web version served through a delivery platform, the data feeds other systems consume. A correction is made once and exists everywhere on the next publish — which can be the same afternoon, because publishing costs a click instead of a design pass.
This is the same discipline aerospace formalized decades ago — S1000D exists precisely so one set of data modules feeds every manual and viewer — arriving, at last, at ordinary enterprise documents. The InDesign question answers itself once it's asked honestly: the manual artistry matters for the brand brochure, and the template does the manual better. Keep the design tool for the work that is design. Let the document library run on structure, where every output — and every reader, human or machine — draws from one source that never had a chance to drift.
FAQ
Questions We Hear
What does the typical document assembly line look like?
Content drafts in Word, where review and tracked changes happen. A designer then re-lays it out in InDesign for the polished version. The InDesign file exports to PDF, and the PDF uploads to the website's CMS — sometimes with the same content re-keyed a third time as a web page. Four tools, three handoffs, one document. Every organization that runs this line believes their version of it is temporary.
Where does the assembly line actually lose content?
At the handoffs. A late Word edit arrives after the InDesign pass and someone patches the layout by hand — or forgets. The designer 'tidies' a table and changes its meaning. The web version is paraphrased from the PDF and drifts from it. Since no step is authoritative once the next begins, an amendment means re-running the whole line, so small corrections queue up until someone declares a new edition. The content is never wrong in one place; it's differently right in four.
What is single-source publishing?
One structured source that every output renders from automatically: the print-quality PDF, the web version, and any API or feed all generate from the same content at publish time. Layout is applied by templates, not by hand, so a correction made once appears everywhere on the next publish. The relay race collapses into a single step because presentation stopped being a separate manufacturing stage.
Do we lose design quality without the InDesign pass?
For most enterprise and regulated documents, no — modern rendering pipelines produce typeset-quality PDF from templates, and the template gets more design attention than any individual document ever did. What you give up is per-page manual artistry, which matters for a brand brochure and almost never for a manual, policy, or rulebook. Organizations that need both keep InDesign for marketing pieces and move the document library to single-source — the point is matching the tool to the content, not banning a tool.
Get In Touch
Still Running the Relay?
Count your handoffs. If a correction touches more than one tool before it reaches a reader, single-source publishing retires that entire chain — and we build it.