Internal communications asset management: version control and brand libraries

TLDR: Internal communications asset management fails less through poor software than through the absence of two rules – one place, one current version, with a named owner for both. Where those rules are missing, sites quietly run on superseded files and the inconsistency is blamed on discipline rather than on structure. What changes the outcome is deciding what counts as the master and making the current version easier to find than the old one.

The safety poster on the wall at the Doncaster site is from 2023. It is still there because it looks fine, nobody owns removing it, and the person who put it up has moved on. The site manager who needed a version last month searched the shared drive, found four files with similar names, and picked the one with the most recent date in the filename – which happened to be a draft renamed by someone in a hurry.

This is not a discipline problem. It is a findability problem, and findability is what internal communications asset management is for. People do not use old files out of preference. They use them because the old file was the one they could find in the four minutes they had.

Internal communications asset management is the unglamorous structure underneath everything else – campaigns, employer brand consistency, translation, approvals. When it is absent, each of those areas develops its own workaround, and the workarounds are where inconsistency originates.

What is internal communications asset management?

Internal communications asset management is the practice of holding every communications file in one location, with one identifiable current version, a named owner, defined access, and a record of what may be done with each item.

It is not a piece of software, though software helps at scale. The smallest workable version is a well-structured folder with strict naming, an owner and a written rule about what the master is. The largest is a full digital asset management system. Both work. Neither works without the rules.

The distinction that matters is between a store and a library. A store holds files. A library tells you which file is the right one. Most organisations have several stores and no library.

Why internal communications asset management fails in distributed organisations

Six recurring causes, all structural rather than behavioural.

There is no single location. Files exist on a shared drive, in an intranet media library, in an agency’s system, in a project folder, and in the email inbox of whoever last sent them. Each is authoritative to somebody.

Nothing distinguishes the master. Four files, similar names, one is final. Nothing in the file itself says which. The reader picks by date, which is often wrong because a minor re-save updates the date.

Nobody owns removal. Adding is easy, deleting feels risky, so nothing is ever retired and the store grows until search stops being useful.

Access is too tight. When only three people can reach the library, everyone else keeps a local copy. Local copies are how a version fork begins.

Local production is unsupported. A site needs something no template covers. They make it. It never enters the library and cannot be updated centrally.

Language versions drift apart. The English is updated and the other languages are not flagged, so sites run on superseded translations for months. This is one of the sharper failure modes covered in multilingual internal communications.

How do you set up a brand library that people use?

The sequence below can be run in a fortnight for a mid-sized estate. It is deliberately ordered so the painful step comes second, when the scale of the problem is clear but before anyone has invested in structure.

1. Inventory before you organise

List every location where communications files currently live, including the ones that are not supposed to exist. Note who uses each and what they get from it. You are looking for the two or three that carry real traffic.

2. Decide what is a master and what is an output

A master is the editable source. An output is a rendered file for a specific use. Masters need version control. Outputs need to be regenerable and disposable. Conflating them is why libraries fill with 400 PDFs of the same poster.

3. Retire aggressively, once

Everything superseded moves to a dated archive folder that is excluded from search but not deleted. This is uncomfortable and it is the step that makes the rest work, because a library people trust is one where everything visible is current.

4. Set a naming convention people can follow without a manual

Four elements is usually enough: what it is, who it is for, the date in year-month-day, and the version or language. Written down in one line, visible in the library itself. A convention nobody can remember is not a convention.

5. Give everything an owner and a review date

Every master gets a named owner and a date at which someone will confirm it is still current. Items with no owner are the ones that end up on a wall three years later. A quarterly list of items past review date is enough governance for most organisations.

6. Open access wider than feels comfortable

Read access for anyone who might need a file. Edit access for a defined few. Restricting read access to prevent misuse reliably produces local copies, which is the worse outcome.

7. Support local production explicitly

Provide editable templates for the things sites actually make – the one-page notice, the shift board, the toolbox talk. Give sites a route to request something that does not exist. Unsupported need does not disappear when it is not supported; it just gets made in Word.

8. Record rights alongside the file

Licence terms, consent status and permitted uses stored with the asset, not in an email. The question two years later is always whether this image was cleared, and it needs a fast answer. The rights checklist in internal communications aseet management is designed to run at this point.

9. Make the current version easier to find than the old one

The final test of any library. If finding the current file takes longer than reusing the one already on someone’s desktop, the desktop wins. Every time.

What to hold in the library

A workable scope for internal communications asset management in a distributed organisation:

• Brand core: logos in every format, colour specifications including print equivalents, typefaces and licensed fallbacks
• Editable templates for high-frequency local production
• Photography, with consent and licence status recorded per image
• Campaign masters, with all channel variants together
• Language versions, linked to their source so an update flags every dependant
• Supervisor and manager briefing materials
• Print-ready and mono versions of core assets
• A short written standard for words as well as marks – terminology, plain-English rules, the terms the organisation uses and does not. GOV.UK’s content design guidance is a reasonable public model to adapt

What not to hold: rendered outputs that can be regenerated, working drafts, and anything superseded. All three make search worse, and search quality is what determines whether the library is used.

Do you need dedicated software?

Below a certain scale, no. A structured folder system with strict naming and a clear owner works for organisations producing a moderate volume across a handful of sites, and it costs nothing.

Dedicated software earns its place in internal communications asset management when three conditions are present at once: high asset volume, many distributed users producing locally, and a real need to track rights and expiry per item. At that point the search, permissions and metadata handling of a proper system saves more time than it costs to run.

The order matters, though. Software imposed on an unstructured estate reproduces the disorder with better search. The rules come first, and they are the part that determines whether it works. The same caution applies to AI-assisted tooling, discussed in AI workflow for internal comms – it accelerates whatever structure it is given, including the absence of one.

A working checklist

• One documented location that everyone knows is authoritative
• Masters and outputs distinguished, with different rules for each
• Superseded material archived out of search, not left in place
• A four-element naming convention, visible in the library
• Named owner and review date on every master
• Read access wide, edit access narrow
• Editable templates for the items sites produce most often
• A route for sites to request what does not exist
• Rights, licence and consent status recorded per asset
• Language versions linked so a source update flags every dependant
• A quarterly list of assets past their review date
• Someone accountable for removal, not only for addition

The structural point

Internal communications asset management is usually framed as a compliance matter and treated as a question of individual discipline. It is neither. It is a findability problem with a structural fix, and the fix is mostly a small number of rules applied consistently rather than any particular technology.

Internal communications asset management done well is invisible – nobody notices that every site is running the current version, because nothing goes wrong. Done poorly it surfaces as a brand consistency problem, a translation problem or an approvals problem, and gets solved in three places at once. Where the underlying library has never been established, CommsKit is a good place to start.