Somebody in your company has a folder called Brand Assets. Somebody else has one called Brand Assets Final. A third person has the logo saved from an email in 2023. When a print job goes out, whichever of those three people is fastest to reply is the one whose file gets printed.
This is not a design problem or an IT problem. It is a records problem, and it produces the same handful of expensive outcomes: two offices with visibly different corporate blue, a brochure carrying an address the company left last year, and a 10,000 unit run reprinted because someone sent version four instead of version six.
What actually goes wrong
Four failures account for most of it.
The wrong version gets printed. Files named final, final2 and final-updated coexist, and the modification date does not tell you which one was approved.
The working file and the print file get confused. Someone sends an InDesign or Illustrator file where a print ready PDF was needed, or sends a low resolution PDF made for email review.
The file drifts. Each time a small change is made, the file is opened, edited and re-exported. Fonts get substituted, an image gets replaced with a lower resolution version, a spot colour turns into a CMYK build. None of this is visible on screen.
Nobody knows what was approved. The approval happened in a chat thread or a meeting, and six months later there is no record of who signed off what.
Separate three kinds of file, permanently
The single most useful structural change is to stop treating artwork as one thing. There are three kinds and they belong in different places.
- Working files: the editable source, with links and fonts. Owned by whoever produces artwork, internal or agency. Nobody else needs access.
- Approved print files: the exact PDF that was signed off and sent to a printer. Read only for everyone. This is what gets reordered.
- Reference files: low resolution PDFs and images for internal use, presentations and review. Clearly marked as not for print.
Keep them in separate locations, not in separate subfolders of the same one. The point is that somebody in a hurry cannot reach into the working files and grab something.
A naming convention that survives contact with reality
Conventions fail when they are long. Keep it to elements that someone can produce from memory:
Item, specification, version, date. For example: corporate-brochure-A4-8pp-v06-2026-03.pdf. That tells you what it is, what shape it is, which version, and roughly when.
Two rules do most of the work. Never use the word final, because it always acquires a suffix. Always increment the version number even for a one word change, because two files with the same version number and different content is the failure state you are trying to avoid.
Add the printer's job number to the filename once it has been printed. That connects the file to a physical result and makes reordering trivial, as our note on storing and reordering printed stock covers in more detail.
Record the approval, not just the file
A file is not evidence that anyone approved it. Keep a short record alongside each approved print file: who approved it, on what date, and against which proof. Three lines in a spreadsheet or a text file is enough.
This sounds bureaucratic until the first time somebody asks why the brochure says something it should not. With a record, that takes a minute to answer. Without one, it becomes an argument. Our guide to print approval workflows covers how to structure the sign off itself.
One owner per item
Every printed item should have a named owner who is responsible for its current version. Not a department, a person. Shared ownership of a file means nobody notices when it goes stale, and stale files are the ones that get reprinted with an old address on them.
What to hand a printer
Standardise what leaves the building. A print supplier should receive:
A print ready PDF with fonts embedded, correct bleed, and the colour space the job requires. A specification, ideally as a written sheet rather than in the body of an email. The quantity and the delivery requirement. And a reference to the previous job number when it is a reorder.
Sending working files instead invites the printer to make decisions on your behalf, and those decisions are made under time pressure without knowledge of your brand. Our note on turning brand guidelines into a print spec sheet suppliers can follow sets out what that document should contain.
Keeping brand colour consistent across files
Colour is where version drift causes the most visible damage, because two items printed from two versions of the same logo sit next to each other on a desk.
Define brand colours as numbers in the guidelines: a Pantone reference, a CMYK build for coated, a separate CMYK build for uncoated, and an RGB value for screen. Then make sure the approved print files use those values rather than whatever the file happened to contain.
The common failure is a logo file that has been through a conversion at some point and now carries a slightly different CMYK build. It looks identical on screen. It does not print identical. Auditing your approved files against the defined values once, properly, is worth a day of somebody's time.
When you have multiple offices
Distributed teams multiply every problem above. Two additions help.
Give each location read access to the same approved print files rather than sending copies. A copy sent by email becomes a local version within a week.
Route ordering through a single supplier arrangement where practical, so that stock and colour are managed centrally even when the ordering is local. Our guide to rolling out a rebrand across multiple sites covers the sequencing when the files themselves change.
How we work with corporate teams
We store the approved artwork and full specification for every job we print, indexed by job number, so a reorder does not depend on your team finding the right file. If you send us something that does not match the version we hold, we tell you before we print rather than assuming the new one is correct.
For teams with multiple orderers, we can set up an account where saved specifications are locked and only approved files are orderable, which removes the most common route to a wrong print. Details of what we produce are under digital printing services, and if you want help auditing your existing artwork before setting this up, talk to us about what you print regularly.
Frequently asked questions
Should artwork live in our document management system or with the agency?
Working files can stay with whoever produces them. Approved print files should live with you, because they are the record of what your company published, and agency relationships end.
How long should we keep approved print files?
Indefinitely for anything with regulatory or contractual content, and at minimum for as long as the item is in circulation plus a few years. Storage is cheap compared with recreating an item from scratch.
Is version control software worth it for artwork?
For most marketing teams, a disciplined folder structure and naming convention works better than a system nobody wants to use. The discipline matters more than the tooling.
What if the printer holds a different version than we do?
Treat that as a signal rather than a nuisance and reconcile it before printing. It usually means somebody sent a file outside your process, and finding out which one is correct now is far cheaper than after the run.
