Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Operations › Systems

Setting Up a Marketing Asset Library

How to turn shared folders into a marketing asset library: decide what belongs, collect approved files, add status, version, rights and expiry, and maintain it.
Tutorialintermediate11 min readUpdated

What makes a folder a library

The work management guide names the four pieces of information that turn a shared drive into a library: approval status, version, rights and expiry. Its job is to make the current, approved, licensed version of each asset the easiest one to find. When it fails, people reuse whatever they can find in an old campaign folder, and the superseded logo, the expired offer or the image whose licence has ended goes live again. When the cost shows up as one team rebuilding an asset another team already made, the diagnosis for marketing teams duplicating work traces whether the library is the join between them that failed.

This tutorial is the set-up procedure that guide leaves for later. It assumes nothing about software. Asset management tools sit among content tools in the map of martech categories, and if the team decides to buy one, the guide to choosing and evaluating marketing tools runs that decision with the requirements this tutorial produces. Many teams find that doing the set-up first, in the folders they already have, tells them whether they need a tool at all and exactly what it must do.

Three neighbouring procedures already exist and are linked rather than repeated. The creative production playbook sets the asset naming convention and makes the creative library the single home of approved creative. The creative approval SOP saves approved files to the library with their version and releases them only from there. And the branding pages gather a new identity's master files into the library during the identity project handover and remove retired files from it after a brand consistency audit. The library this tutorial sets up is the place all three point to.

Before you start

  • Name the library owner. One person owns the structure, the fields and the upkeep routine. Each asset also has an owner, usually whoever commissioned or approved it.
  • Have the work system in place. The library links to work items, so the work management set-up in the prerequisite guide should exist, even in a simple form.
  • Agree the naming pattern. Use the pattern in the creative production playbook, or the team's existing one if it already works. Naming is decided once, before files are moved, not during the clean-up.
  • Find the current brand guidelines. The brand guidelines template shows what they normally hold; the library's brand section should match them file for file.
  • Collect the contracts. Licences for stock and commissioned photography, creator agreements and any agency terms covering ownership. You need them to fill in rights and expiry, and gaps are easier to chase now than when an asset is about to run.
  • List every place assets live today. Shared drives, personal drives, agency portals, chat attachments, the ad platforms' own libraries, the website's media library and the email platform's image store.

The steps

  1. Decide what the library holds and what stays in working folders

    Write down the asset types the library holds: logos and other core brand elements, templates, product photography, lifestyle photography, video, approved copy blocks, creator content and finished campaign creative. Then write down what stays out: drafts, working files, rejected concepts, raw footage and anything not approved. The library is for what may be used now, with an archive of superseded versions; working material lives with the work item or in project folders. Treat core brand elements, such as the logo, colours, typeface and any signature imagery, as the brand's distinctive brand assets and give them their own top-level section, because they are reused most and the cost of a wrong version is highest.

  2. Collect what is actually in use

    Start from what customers can see, not from the folders. List the assets currently live on the website, in active ads, in email templates and automated journeys, on social profiles, in sales materials and with partners, and trace each back to its source file. This finds the assets that matter first and exposes copies held in places the team had forgotten: an agency portal, a platform's own media library, a salesperson's laptop. Then sweep the old folders for approved assets that are not live but are still meant to be used, such as next season's product shots. Anything that is neither live nor planned can wait in the old folders until they are closed. Affiliate partners are a common blind spot, because each received a pack of creative when they joined; the tutorial on onboarding and activating new affiliates points that pack at the library's approved copies so partners stop working from old downloads.

  3. Keep one approved copy of each asset and archive the rest

    For each asset, find the approved master and keep exactly one copy of it in the library, named to the agreed pattern. Superseded versions move to an archive section, marked as superseded, rather than being deleted, so the history is there if anyone needs to know what ran before. Duplicates and near-duplicates are the main reason the wrong file gets used: three copies of a logo with slightly different colours mean someone will eventually pick the wrong one. Where nobody can say which copy is approved, ask the brand or asset owner to decide, and record the decision.

  4. Give every asset the same fields

    Every asset carries the same set of fields, listed in the table after these steps. Keep the set short enough that people fill it in: a field nobody fills in is worse than no field, because it suggests information that is not there. Use controlled values where you can, such as a fixed list of statuses and asset types, so that the library can be searched and filtered reliably. Fill the fields as each asset is moved in, not afterwards; a library populated with files and a promise to add the details later stays a shared drive.

  5. Record rights and expiry for licensed and creator content

    For anything the business did not make itself, record where it may be used, for how long and with what restrictions, and enter the end date as the asset's expiry. The site's glossary entry on usage rights sets out the starting point for creator content: the creator owns what they make by default, so any reuse beyond their own post has to be licensed, with the uses, channels, markets and duration stated. Paid use needs its own licence, and the guide to amplifying creator content with paid ads keeps one record per creator with the licence period, markets and the platform authorisation's expiry; the library's rights fields should match that record. Assets made with AI tools keep the provenance record that the guide to AI copyright questions describes, stored with the asset. Where nobody can find the licence for an asset, mark its rights as unknown and restrict it until the owner finds the terms. Questions about what a licence or contract allows go to whoever handles contracts or to legal advisers; the library records the answer, it does not decide it.

  6. Store alternative text and usage notes with each asset

    Write the alternative text for each image once and store it with the asset, so every channel that reuses the image reuses the description too. The approvals and compliance guide treats accessibility as part of review against the Web Content Accessibility Guidelines, the widely used standard for web content, and recommends building it into templates; storing the description with the image is the same idea applied to assets. Add short usage notes as well: the placements and crops the asset was approved for, any channel it must not appear in, any claim or offer it carries, and anything a builder should know before using it.

  7. Set access for staff, agencies and suppliers

    Decide who may view, download, upload and approve. Most of the team can view and download approved assets; only the library owner and named approvers move assets into the approved section or change their status. Agencies and suppliers get access to the sections they work on, through their own named accounts rather than a shared login, so access can be removed when the work ends. Record who has access in the same list the team uses for its other tools, so the library is covered when access is reviewed. Superseded and expired assets stay visible to the library owner but are hidden from, or clearly marked for, everyone else.

  8. Link the library to the work system

    Each work item records the assets it uses, and each asset records the work items and channels that used it. The work management guide explains why: the link is what lets the team answer, quickly, where an asset is live when its rights expire or a claim in it must be withdrawn. Without it, the answer is a search through every channel by hand. Keep the link simple, such as the asset's name or identifier on the work item and a "used in" field on the asset, and make adding it part of the launch check so it is not forgotten. When something does have to come down, the tutorial on withdrawing an asset from every channel starts from these links.

  9. Close the old folders and set the upkeep routine

    Once the library is populated, make the old folders read-only, tell everyone the date they will be archived, and then archive them. As the brand consistency audit warns, a retired file that can still be downloaded will be used. Point every template, intake form and procedure at the library instead. Then set the routine that keeps it current: the library owner checks for assets approaching their expiry date and tells their owners, removes or archives anything expired, reviews assets with unknown rights, and confirms new approved assets arrived with their fields complete. Put the routine in the team's operating rhythm with a named owner, so it survives busy periods.

The fields every asset carries

The work management guide's four fields are the core; the rest make the library searchable and safe to reuse.

FieldWhat it holdsWhy it matters
NameThe file name in the agreed naming patternLets the same name appear in the library, the file and the ad platform
Asset typeLogo, template, photo, video, copy block, creator content, campaign creativeLets people filter to what they need
Approval statusApproved, superseded, expired, restricted, rights unknownSays whether the asset may be used today
VersionThe version label and the date it was approvedShows which iteration is current
Approved byThe reviewer or reviewers and the dateLinks to the approval record on the work item
OwnerWho commissioned or answers for the assetThe person to ask about rights, changes or withdrawal
RightsSource, permitted uses, channels, markets, edit permissions and restrictionsSays where the asset may run
ExpiryThe date after which the asset must not be used, if anyDrives the upkeep routine and withdrawal
Alternative textThe description to use wherever the image appearsKeeps accessibility consistent across channels
Usage notesApproved placements and crops, claims or offers carried, channels to avoidPrevents misuse by people who did not brief the asset
Used inThe work items and channels where the asset runs or ranAnswers where an asset is live when it must come down
ProvenanceFor AI-assisted assets, the record the AI copyright guide describesKeeps the facts needed if questions arise later

If the team wants a measure of whether the library is working, the share of live assets that came from the library with complete fields says more than the number of files it holds. Treat that as a health check on the system, not as a target for the people filling it in.

An outdoor clothing brand builds its library (illustrative)

Illustrative example — not a real result

Ixworra Outdoor builds its asset library

Ixworra Outdoor, an invented outdoor clothing brand selling online and through 40 stockists, kept its assets across 3 shared drives, an agency portal and the paid social team's own folder. The ecommerce manager was named library owner, and the team agreed to finish the set-up in 6 weeks.

Starting from what was live, the team listed 310 assets in use across the website, ads, email templates and stockist materials, and traced each to a source file. The sweep found 5 versions of the main logo, 2 of them in an old colour, and 140 product shots duplicated across drives. One copy of each approved asset went into the library; superseded versions went to an archive marked as superseded.

The rights step found the problem the team had feared. 12 licensed lifestyle images in the paid social folder came from a photography licence whose 2-year term had ended 4 months earlier, and 3 creator videos were licensed for organic posts only, with no paid use. Those 15 assets were marked expired or restricted, pulled from the ads they were running in, and replaced from licensed stock while the brand negotiated paid use for the strongest creator video.

Every asset received the same 12 fields, with alternative text written once for each image. Agencies got named accounts limited to campaign creative. Work items now record the assets they use, and the launch check confirms the link. The old drives became read-only in week 5 and were archived in week 6. The library owner now checks expiry dates at the start of each month, and in the first quarter the routine flagged 9 assets before their licences ended.

Common mistakes

  • Moving everything across. Copying every old folder into the new library recreates the shared drive with a new name. Start from what is live and approved.
  • Keeping several "approved" copies. If three versions of the logo are labelled approved, one of them will be wrong somewhere. Keep one master and archive the rest.
  • Leaving rights blank to fill in later. Later rarely comes; mark unknown rights as unknown and restrict the asset until they are found.
  • Treating an organic licence as a paid one. Creator content licensed for reposting does not cover ads, as the usage rights entry explains. Record each use separately.
  • Deleting superseded versions. The history matters when someone asks what ran; archive and mark them instead.
  • Writing alternative text in each channel separately. The descriptions drift and some images get none; store it once with the asset.
  • Sharing one login with agencies. Access cannot then be removed from one supplier without disrupting the rest.
  • Leaving the old folders open. A retired file that can still be downloaded will be used. Make them read-only, then archive them.
  • No upkeep routine. A library without an expiry check becomes a tidier way to run expired assets. The systems hub shows how the library fits beside the work system and data operations.

Frequently asked questions

Do we need dedicated software for a marketing asset library?

Not to start. What makes a library is the discipline: one approved copy of each asset, the same fields on every file, rights and expiry recorded and a routine that keeps it current. A well-organised shared drive with a register can do that for a small team. Dedicated software earns its place when the volume, the number of people needing access or the need to track where assets are used outgrows a register; choose it with the same evaluation you would use for any marketing tool.

What should not go into the asset library?

Drafts, working files, rejected concepts, raw footage and anything not approved for use. The library holds what may be used now, plus an archive of superseded versions marked as such. Working files belong in the work system or in project folders that the people building the asset use, and they move into the library only when they are approved.

Who should own the asset library?

One named person, usually in operations, creative or brand, owns the library's structure, fields and upkeep routine. Each asset still has its own owner, usually whoever commissioned or approved it, who answers for its rights and expiry. Without a named library owner the fields drift, folders multiply again and nobody runs the routine that flags expiring assets.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Web Content Accessibility Guidelines (WCAG) — W3C

Related