# How marketing teams manage video assets > Most marketing teams manage video assets with shared cloud storage and a naming convention that about half the team follows. Canonical URL: https://vivu.ai/guide/how-do-marketing-teams-manage-video-assets Most marketing teams manage video assets with shared cloud storage and a naming convention that about half the team follows. A smaller number run a dedicated asset management system with permissions, metadata, and someone whose job includes keeping it current. The two approaches fail in different places. The shared drive fails quietly, years in, when nobody can find the thing they know exists. The dedicated system fails at rollout, when everything has to be moved and re-described before anyone gets a single day of value out of it. Which one you need depends less on team size than on how often you have to reach back past a year. ## The default, and where it stops working The common setup is folders by year, then campaign, then a raw and final split, on whatever cloud drive the company already pays for. This is a real system and it works for a while. It survives on the memory of the people who created the folders, which is why it degrades on a schedule that tracks staff turnover rather than file count. Two things break it. The first is agency handoff, where a quarter's worth of material arrives with someone else's naming logic and gets dropped in as a single folder nobody opens again. The second is that folder names describe the project, and a year later people search for content: the line about the warranty, the shot of the packaging, the customer who said the thing. No folder tree has ever answered that question. ## The index people build by hand The next step teams take on their own is a spreadsheet: one row per asset, a link, a few columns for campaign and product and usage rights. This is worth doing and it holds up for about two quarters. It stays accurate for as long as the person who owns it stays interested, and it only covers finished assets, so the raw material stays dark. There is a homemade retrieval version of this too. People publish transcripts of their own video and podcast archives on their website and then use search-engine operators against their own domain, because searching a public index of your own words beats scrubbing timelines. It works, it is free, and the ceiling is obvious the moment the material is not public. ## Dedicated systems A digital asset management system is the version of the spreadsheet that other people maintain. It gives you permissions, expiry dates on talent and music licenses, version history, and a place where the legal answer to "can we still run this" is recorded next to the file. For a team that publishes across regions or works with outside agencies, that record is often the reason to buy, more than search is. The cost is not only the license. It is the migration, the taxonomy argument, and the ongoing requirement that someone fills in fields. Systems bought without an owner become expensive read-only archives. Before shortlisting anything, it is worth knowing [which of the two categories you are actually shopping in](https://vivu.ai/guide/what-is-the-difference-between-a-dam-and-a-mam), because production-oriented systems and brand-oriented systems solve opposite halves of this. Reading two established products [set next to each other](https://vivu.ai/guide/how-does-iconik-compare-to-frame-io) is a faster way to see what the category variables are than reading any feature list. ## Adding retrieval to the storage you already have A newer option leaves the storage arrangement alone and puts a search layer over it. Nothing moves, the folder structure stays as wrong as it always was, and the retrieval happens on content rather than filenames. The trade is that this does not solve rights, approvals, or distribution. It solves one problem, which is getting back to a specific moment inside a specific file. [Vivu](https://vivu.ai/solutions/marketing) goes after that one problem with an upload. Footage is copied into a private Vivu project and indexed there, and the team's own folders can stay as wrong as they were. The mechanics of what that search is doing under the hood are covered in [how content search inside footage works](https://vivu.ai/guide/how-does-ai-search-inside-video-footage), and they matter here mostly because the answer determines what you can ask for. ## When you do not need any of this If your video output is a few campaigns a year and the finished files live in one folder everyone knows, buying a system will cost more than the problem does. The same applies if your material has a genuine shelf life of one campaign, which is true of a lot of paid social creative. Asset management pays off when material has value after its launch window and when more than one person needs to find it without asking a colleague. ## Which side you are on The test is one question, asked honestly. When someone needs a clip from two years ago, what happens? If the answer is that a specific person finds it in ten minutes, you have a working system regardless of what it is made of, and you have a succession problem instead. If the answer is that someone gives up and books a new shoot, the storage is fine and the retrieval is what you are missing. Those two conclusions lead to different purchases, and teams that skip this question tend to buy the one that comes up first in a search rather than the one that fixes what is broken. ## FAQ ### Do we need a DAM, or is a shared drive enough? A shared drive is enough until two conditions hold at once: material stays useful past its campaign, and more than one person needs to find it without asking. Until then a drive plus a naming convention is the cheaper correct answer. The signal to upgrade is rarely storage volume. It is repeated re-creation, meaning someone shot or designed something the company already owned. Two or three of those in a quarter is a stronger buying case than any file count. ### Who should own video asset management on a marketing team? Someone in the production path, not in operations. The person who names files at delivery has to be the person accountable for the system, otherwise the metadata gets entered by someone who was not there and does not know what the footage contains. In small teams this is usually the producer or the senior editor. It should be written into the role explicitly, because it is invisible work that disappears the moment the person holding it leaves, and systems left without an owner rot faster than no system at all. ### What should a video file naming convention include? Date, a short project code, and a version marker will carry most of the weight. Anything past four segments gets abbreviated inconsistently by the third person who touches it. The thing worth adding that most conventions leave out is a final marker that means final, applied only once. Most retrieval pain in video is not finding the project, it is telling apart the six exports inside it. ### How do we handle raw footage separately from final cuts? Keep them in different places with different retention rules. Finals need permissions, rights tracking, and easy sharing. Raw needs cheap storage and the ability to search inside it, and almost nothing else. Mixing them means either paying premium storage rates for terabytes nobody browses, or applying a rights workflow to material that will never be published. The split also makes the delete decision possible later, since raw from a campaign whose talent release expired is genuinely dead weight.