Organising Photos, Video, and Approved Copy So People Find Them

Calculate what an asset is worth

Start with a number you can compute from your own records. Take the total cost of a shoot, including the photographer, the models, the location, the editing, and the internal hours, and divide it by the number of times the resulting images have appeared in your work. If the answer is large, the images sit unused somewhere and the shoot paid for very little. If your team can reuse each image twenty times instead of three, the cost per use falls sharply without anyone spending another dollar. That calculation gives you a reason to invest in organisation, and it gives you a way to show a finance partner why a library earns its keep.

Describe every asset with metadata

Folders alone fail because an image belongs in more than one place. A photo of a technician at a customer site belongs under the service line, the industry, the campaign, and the person, and a folder tree forces you to pick one. Metadata solves this by attaching descriptive fields to the file, so people can search or filter by any of them. A practical starting set is small enough to fill in during upload: subject, product or service, audience or industry, campaign, orientation, usage rights, approval status, and an owner.

The fields people skip are the ones that cause trouble later, so make the important ones required. Usage rights deserve special care, because a stock license with an expiry date or a model release limited to certain media becomes a liability the moment someone reuses the image outside its terms. Record the license type and the expiry date on the asset, and set a reminder to review anything expiring in the next ninety days, which turns a legal surprise into a calendar item.

Name files so they sort and explain themselves

A naming pattern costs nothing and pays back daily. Choose an order that sorts well, such as date, subject, descriptor, and version, written in lowercase with hyphens between words, and apply it from the first upload. A file called 2026-03-service-technician-site-visit-v2 tells a stranger what it holds, when it arrived, and which revision it is, while a file called final-final-3 tells them only that somebody was tired. Write the pattern on one page, pin it where uploads happen, and let the person who maintains the library gently rename the strays.

Treat approved copy as an asset

Words need the same care as pictures. Gather the company description in short, medium, and long versions, the product descriptions, the leadership bios, the standard disclaimers, and the answers your team gives repeatedly to prospects, and store each with an approval date and a named owner. Salespeople who can pull the current approved paragraph in ten seconds stop pasting from old proposals, and the old language, with its outdated claims and discontinued products, stops circulating. When a claim changes, the owner updates one entry and everyone who pulls from the library gets the new version.

Test whether people can find things

A library succeeds when strangers can use it, so test it that way. Pick five assets you know exist, ask five colleagues from different departments to find them, and time each search. Where people fail, you have learned something concrete: the search term they tried was missing from the metadata, or the asset sat under a label only its uploader understood. Fix the metadata, add the term they used as a tag, and repeat the test next quarter. Their vocabulary, which usually differs from yours, is the best specification the library will ever get.

Retire what has expired

A library that only grows eventually buries its best material. Each quarter, archive images of discontinued products, retired logos, former employees, and anything whose license has lapsed, and keep the archive searchable for administrators so history stays available without tempting anyone to reuse it. A smaller library with confident, current contents gets used more than a larger one that makes people wonder whether anything is still true.

Connect the library to the places you publish

The biggest gain comes when the library feeds the website directly. If your CMS pulls images and copy from the same system your team uses to find them, an update to one asset corrects every page that uses it, and nobody hunts through the site for the old logo after a rebrand. That connection is part of how Voyager builds sites, with asset management and the CMS working together, and you can approximate it on any stack by making the library the only place an image is ever replaced.

Your next move starts with an inventory. Spend an hour this week listing where your photos, videos, and approved copy live today, count the locations, and choose one to become the home for all of them. Then upload your twenty most-used assets with full metadata, run the five-person search test, and let the results tell you how much further to go.