The cost you can see is not the cost you are paying

A product manager asks for an updated datasheet. A designer, an internal DTP team or an agency produces it. An invoice arrives, or a time entry gets logged. On paper, that is the cost of the document.

In practice, the datasheet did not start with the designer. It started days earlier, when someone had to work out which specifications had changed, pull the latest pricing, chase a missing image, and explain all of it clearly enough for someone else to act on. It did not end when the file was produced either. A reviewer found an inconsistency. A second market needed a local variant. A translation had to be checked against the source. Someone had to confirm which version was final before it could go out.

None of that shows up as a production cost. All of it consumes time, and in most organizations, nobody is tracking where that time goes.

Visible production cost versus hidden workflow cost

The visible cost of document production is the production itself: the hours or the invoice tied to actually building the file. The hidden cost is everything required to get that output briefed, corrected, coordinated, handled, reviewed and approved before it becomes usable.

That hidden cost isn't wasted effort. Briefing, review and the coordination between the people who hold the data and the people who produce the document all have to happen somewhere. Almost none of it gets counted as part of what a document costs to produce, though: budgets and time estimates are built around the visible step, while the surrounding work quietly absorbs a comparable, sometimes larger, share of the total effort.

Five categories of hidden workload

Five categories cover most of what actually consumes the time inside that gap:

  • Rework — correcting or redoing work after a first version already exists: a wrong price fixed, a specification adjusted after the file was built, a layout redone because the source data changed late. Distinct from the original production effort.
  • Briefing — preparing the instructions, requirements and input production needs before it can start: working out what has to change, gathering the relevant facts, and explaining them clearly enough that someone else does not have to guess.
  • File handling — collecting, renaming, transferring and organizing the files and assets a document depends on. A PIM export, a spreadsheet update, a folder of images that needs sorting before anyone can use it.
  • Coordination — the follow-up, handovers and alignment between the people involved, inside one team or across an external partner: confirming who has the current version, who is waiting on whom, and what still needs a decision.
  • Review and approval — checking the document, collecting feedback and confirming it is ready to publish. Separate from rework, which is the work of acting on what review finds.

These five do not cover everything that touches a document. General product management, generic PIM maintenance, photography and brand strategy stay outside the count — real work, but work that would happen regardless of this particular piece of output.

Hidden workload compounds with scale

At low volume, none of this stands out. One datasheet, one market, one update a quarter — briefing, coordination and review still happen, but they get absorbed without anyone noticing the pattern.

The pattern is hard to ignore once the numbers grow. A product range that keeps expanding means more source data to brief, and more line items that can quietly go stale between updates. Add a few more output types — a technical sheet here, a price list there, a full catalog alongside the datasheet — and each one drags its own briefing and review cycle behind it. The same update pushed into a second or third market has to be checked, translated and approved again, usually by someone who is not looking at the same version as the last person who touched it. Compress the update cycle, and none of those steps gets any shorter; there is just less time to do them in. And once more people and teams are involved, every one of them is a handoff — a place where a file, a decision or a piece of context can get lost, or has to be explained all over again.

None of this makes the visible production step much more expensive on its own. What it does is multiply how often briefing, file handling, coordination and review have to happen around it — which is why organizations with large product ranges, multiple markets and several data sources feel this cost well before it shows up in a budget line.

Internal, agency and hybrid: same work, different hands

This workload exists in every operating model. Only where it sits changes.

Keep production internal, and the same categories stay inside the team: briefing, file handling and review still happen, they are simply less visible, because no invoice separates them from everything else the team does day to day.

Move production to an external agency, and the file leaves the building, but briefing, data verification, version confirmation and approval do not. Someone internal still has to explain what needs to change, supply the right files, and confirm the result is correct before it goes live — which is why routing every document through an external partner tends to make coordination and review more visible, not less necessary.

Split production between internal and external teams — often by document type or market — and both sides carry the same categories, plus a coordination cost between them that neither pure model has to deal with on its own.

Switching models changes who carries rework, briefing, file handling, coordination and review. It does not remove the need for any of them, and a comparison that only looks at production cost is comparing the wrong number.

Measuring the real cost baseline

Most organizations can state their production cost with reasonable confidence: a day rate, an agency invoice, a design hour. Far fewer can state, with the same confidence, how many hours go into briefing, file handling, coordination, review and rework across a year of document output.

A useful starting point is not a full time-tracking exercise. Two simple, observable numbers already say a lot: how long a typical document takes from request to publication, and how many correction rounds a typical document goes through before it is approved. Neither requires new tooling to collect — most teams already know the answer, even if nobody has written it down. Alongside those two, a rough estimate of hours spent per year on each of the five categories, even a conservative one, is usually enough to show whether the hidden workload is a minor addition to production cost or a comparable cost in its own right.

Automation changes the cost structure

Document automation does not remove the need for briefing, review or approval. Those steps depend on human judgment and stay necessary regardless of how a document gets assembled. What it does change is which categories carry the manual, repetitive load.

File handling shrinks first: data moves from source systems to output without a manual export-and-reformat step in between. Rework follows, since a correction made once in the source data propagates on its own instead of being repeated document by document. And once production draws on governed data rather than files passed from person to person, coordination drops too — there are simply fewer handoffs left to manage.

Briefing and review stay largely where they are, but they get more concentrated: less time moving and rechecking files, more time on the two things that still need a person — deciding what should change, and confirming the result is right.