How to Identify and Reduce Print Production Costs

Print publication budgets are under pressure. Whether you're managing an in-house magazine, running a publishing agency, or producing annual reports, production costs can spiral quickly.

The challenge isn't always obvious. Most teams assume printing and paper are the biggest expenses. But for many publishers, the real costs hide in how work flows through your organization.

This guide walks through common workflow inefficiencies, how to identify whether they're affecting your budget, and practical steps to eliminate them. No assumptions. Just frameworks you can apply to your specific situation.

A note on this guide: The examples below are illustrative scenarios, not industry averages. Your actual costs and savings will depend entirely on your team size, hourly rates, current workflows, and how thoroughly you implement improvements. We encourage you to calculate your own numbers based on your specific situation.

‍

Where Your Time Actually Goes

Most publishers think about production costs in terms of major categories: printing, freelance design, editorial staff. But this misses where significant waste actually occurs.

The real question to ask: How much time do people spend on work that doesn't directly produce content?

Common examples:

• Finding the right file version in a folder structure
• Compiling feedback from multiple email threads
• Waiting for approvals from stakeholders
• Fixing errors caught late in the process
• Tracking project status in spreadsheets or email
• Coordinating between teams using back-and-forth communication

None of this produces content. But it all takes time, and time is money.

‍

Why This Matters

In a small team (4-5 people), even 30-45 minutes per person per day spent on administrative coordination adds up:

• 30 min/day × 5 people × 5 days/week = 12.5 hours of team time
• 45 min/day × 5 people × 5 days/week = 18.75 hours of team time

That's 12-19 hours per week your team isn't doing actual production work.

The question is: What is that time costing your organization?

‍

Identifying Your Specific Cost Drains

Rather than assuming industry averages, let's identify what's actually happening in your workflow.
‍

Five Common Bottlenecks

Most publishing teams struggle with some combination of these. See which resonates with your experience:

Version Control Chaos

Files exist in multiple places. Email attachments, Dropbox folders, Google Drive, shared servers. Someone asks "which version is current?" Multiple times per week. Someone opens an old version, makes changes, realizes it wasn't the latest. Work is duplicated or lost.

Questions to ask yourself:

• Do you have files with names like "Final_FINAL_FINAL_v3.indd"?
• Do people frequently ask which version is the current one?
• Have you ever had to redo work because the wrong version was edited?
• Do you use multiple storage systems (email, Dropbox, Google Drive, servers)?

If you answered yes: This is likely costing you time and creating frustration.

‍

Email-Based Approval Workflows

Feedback comes via email from multiple stakeholders. You compile feedback. Conflicting comments require clarification. Email trails grow long and hard to follow. Approvals take days longer than they should.

Questions to ask yourself:

• Do approval cycles typically take 5+ days?
• Do you have to send multiple follow-up emails asking for feedback?
• Do you receive conflicting feedback from different stakeholders?
• Is your email inbox cluttered with client feedback?
• Do you spend time copying feedback from emails into documents?

If you answered yes: This is likely extending your project timelines.

‍

Manual Content Handoffs

Editors and designers work sequentially rather than in parallel. An editor finishes copy, emails it to the designer. Designer integrates it, notices formatting issues, emails back. Wait for response. Repeat. Sequential work means longer project timelines.

Questions to ask yourself:

• Do editors and designers work on the same project at different times rather than simultaneously?
• Do people frequently wait for others to "finish" their part before they can start?
• Do you use email or messages to pass files between team members?
• Do people often need to refocus after waiting for someone else?

If you answered yes: This is likely extending your production cycle.

‍

Late-Stage Error Discovery

Errors caught during final review that should have been caught earlier. A headline is wrong. A photo is missing. A spacing issue makes the layout invalid. The page has to be redesigned from scratch. What should be a 10-minute fix becomes a 2-hour project.

Questions to ask yourself:

• Do you frequently find errors during final review?
• When errors are found, do they require significant rework?
• Do changes made late in the process frequently cascade (affect other pages)?
• Is there a gap between "draft complete" and "final review"?

If you answered yes: This is likely creating unnecessary rework.

‍

Unclear Project Status

The project manager doesn't have clear visibility into what's done, what's in progress, what's blocked. Spends time asking for status updates. Meetings are called to discuss status. People report status via email. Information is scattered.

Questions to ask yourself:

• Do you frequently ask "where are we on this project?"
• Do you spend time in status meetings that could be replaced by looking at a dashboard?
• Is project status tracked in spreadsheets or email rather than a shared system?
• Do team members work in isolation (you don't know what they're doing)?
• Do bottlenecks stay hidden until someone asks?

If you answered yes: This is likely creating coordination overhead.

‍

When to Consider Dedicated Software

After examining your current workflows, you may find that some problems persist despite better processes.

Signs that dedicated publishing software might help:

• Your team is geographically distributed and needs real-time collaboration
• You manage multiple concurrent publications
• Your approval processes involve 4+ stakeholders regularly
• Designers and editors frequently work on the same content simultaneously
• You need audit trails and version history for compliance
• File locking is critical (prevent simultaneous editing conflicts)
• Your workflows are too complex for spreadsheets to manage

‍

If you reach a point where you're exploring publishing software, here's what matters:

Integration with your current tools:

• Does it work with Adobe Creative Cloud?
• Does it play well with your storage system (Dropbox, Google Drive, etc.)?
• Does it require learning a new interface?

Core features you actually need:

• Real-time collaboration?
• Version control and file locking?
• Digital proofing and approval workflows?
• Project visibility and status tracking?
• Cost tracking and time logging?

Implementation and support:

• How long does implementation take?
• How much training do your team members need?
• Is customer support responsive?
• Can you integrate it gradually (not all-or-nothing)?

Total cost of ownership:

• Software cost per month
• Implementation cost
• Training cost
• Time to integrate

Compare this against the actual cost savings you measured in your workflows (not against industry averages or vendor claims).