Short answer
A DAM content audit counts and classifies the assets an organisation holds, where they live, who uses them and which are licensed, duplicated or obsolete. For libraries of more than 100,000 files, a random sample of about 1,000 files estimates duplicate and rights-unknown rates within roughly 3 percentage points at 95% confidence, which is precise enough for requirements and pricing.
What a DAM content audit is
A DAM content audit is a structured inventory that measures the volume, location, condition and rights status of every asset a DAM will hold.
The content audit is the first output of Checkpoint 1 of the Selection Route. The audit supplies the scale inputs that every later checkpoint needs. Requirements depend on asset types and user groups. Pricing depends on storage volume and growth. Migration effort depends on duplicates, metadata quality and rights gaps.
Three outputs make the audit useful:
- A volume baseline: asset count, storage and annual growth per asset type.
- A condition baseline: duplicate rate, rights-unknown rate and metadata coverage.
- A source list: every system and location that holds assets, with an owner per source.
DAMSelection assessment: buyers who skip the audit ask vendors to quote on guesses. The quotes then change at the first storage tier, and the migration plan starts without a scope.
What to count
A DAM content audit counts twelve measures, grouped into volume, condition and use, and each measure feeds a named decision later in the selection.
| Measure | Why it matters | How to measure |
|---|---|---|
| Asset count per type | Sizes the library and the migration | File system reports per location |
| Storage volume in TB | Drives storage-tier pricing | Folder size reports, current DAM admin report |
| Annual growth rate | Drives five-year cost | Compare volume now with volume 12 months ago |
| Video share of storage | Video grows storage fastest | Filter by file extension |
| Average file size per type | Tests large-file requirements | Volume divided by count per type |
| Duplicate rate | Sets migration clean-up effort | Hash comparison on the sample |
| Rights-unknown rate | Measures licence exposure | Sample review against licence records |
| Licensed assets with expiry | Sets rights management requirements | Stock and photographer contracts |
| Obsolete share | Defines what not to migrate | Last-modified date and product status |
| Metadata coverage | Shows the schema gap | Sample check of embedded XMP and IPTC fields |
| Locations and owners | Defines migration sources | Interviews and system inventory |
| User groups and request volume | Sizes seats and portal users | Access lists, two-week request log |
Count assets the way a DAM will count them. A master file and its renditions form one asset with several files. A layered design file and its exports may form one asset or several, depending on the future schema.
Where assets hide
DAM content audits in mid-sized organisations typically find assets in 8 to 12 locations, as a DAMSelection rule of thumb from PIMvendors selections.
Check each of these sources and record an owner for every one:
- Shared network drives and departmental folders
- Cloud file storage used by marketing, sales and product teams
- The current DAM or brand portal, if one exists
- Agency and photographer servers, including archives of past shoots
- PIM media attributes and CMS media libraries
- E-commerce platform image stores and marketplace uploads
- Collaboration tools where final files are shared in chats
- Print supplier and packaging prepress archives
- External hard drives held by creative teams
- Regional office drives outside the central IT estate
The sources outside central IT carry the highest rights risk. Agencies and regional teams often hold licensed images without the licence record.
Check rights in the sample
A DAM content audit checks the rights status of every sampled file against licence records, because unknown rights become a business case risk and a requirement.
Use the four rights classes of the DAMSelection core metadata model, plus one audit class:
| Rights class | Evidence that confirms it |
|---|---|
| Owned | Work-for-hire contract or internal production record |
| Licensed | Stock licence, photographer contract or agency agreement with terms |
| Restricted | Licence with limits on channel, region, period or a model release |
| Unknown | No record found within 15 minutes of searching |
| Expired | Licence period ended, file still in circulation |
For each licensed or restricted file, record the channels, regions and end date. Those three values become structured usage rights fields in the future schema. The 15-minute search limit is a DAMSelection rule of thumb that keeps the review moving.
Feed the rights-unknown rate into the Rights Exposure Estimator. The estimate turns the rate into a risk range for the business case.
Sampling method
Sampling estimates the condition of a large library from a small, random set of files, so the audit stays inside two to three weeks.
DAMSelection rule of thumb: for libraries of more than 100,000 files, sample 1,000 files across locations and extrapolate. Smaller libraries can be checked in full with file reports and hash tools.
- List every location with its file count.
- Allocate the sample to each location in proportion to its file count.
- Draw files at random within each location, using a file list and a random number column in a spreadsheet.
- Review each sampled file for duplicate status, rights status, metadata coverage and current use.
- Calculate each rate for the sample and per location.
- Extrapolate to the full library and state the margin of error.
- Record the method, the date and the reviewers, so the estimate is defensible to finance and procurement.
The margin of error for a rate depends on the sample size. The table uses the standard formula for a proportion at 95% confidence, with the most cautious assumption of a 50% rate.
| Sample size | Margin of error at 95% confidence | Use when |
|---|---|---|
| 400 files | About 4.9 percentage points | Quick first view of a single location |
| 1,000 files | About 3.1 percentage points | Standard audit for selection and pricing |
| 2,000 files | About 2.2 percentage points | Migration planning with tight budgets |
A larger sample narrows the margin slowly. Doubling the sample from 1,000 to 2,000 files only cuts the margin by about one percentage point.
Classify every asset
A DAM content audit classifies each sampled asset into one of four migration classes, which sets the migration scope before vendors quote.
| Class | Criteria | Action |
|---|---|---|
| Migrate | Approved, in use or needed for reference, rights known | Move with metadata |
| Migrate and fix | Valuable, but metadata missing or rights unclear | Move after metadata or rights repair |
| Archive | Out of use, but legally or historically needed | Move to archive tier or keep in cold storage |
| Delete | Duplicate, obsolete or unlicensed with no use case | Remove before migration |
The classes feed the DAM migration plan directly. DAMSelection assessment: the migrate-and-fix share is the best predictor of migration effort, because each file needs a person to decide.
Audit output
The DAM content audit output is one sheet with volumes, rates and sources, plus a short note on method and confidence.
Use this template for the audit sheet:
| Field | Example entry format |
|---|---|
| Total assets | Count, with date of count |
| Total storage | TB, with share per asset type |
| Annual growth | Percentage and TB per year |
| Video share | Percentage of storage |
| Duplicate rate | Percentage, with margin of error |
| Rights-unknown rate | Percentage, with margin of error |
| Licensed assets with expiry | Count or estimate |
| Obsolete share | Percentage |
| Metadata coverage | Percentage of sampled files with title, owner and rights fields |
| Sources | List with owner and file count per source |
| User groups | Internal, agency, regional, partner, with counts |
The sheet feeds four later outputs. Volumes and growth feed the five-year total cost of ownership and the TCO Calculator. Asset types, rights gaps and user groups feed the DAM requirements checklist. Sources and classes feed migration. User groups feed the stakeholder map.
Worked example
Worked example: a mid-sized manufacturer audits 340,000 files in nine locations before a DAM selection.
The file reports show 4.1 TB in total, up from 3.5 TB a year earlier. Annual growth is therefore about 17%. Video holds 38% of storage but only 4% of files.
The team samples 1,000 files in proportion to each location. The review finds 22% duplicates, 9% rights unknown and 31% obsolete. Extrapolated, the library holds about 75,000 duplicate files and about 31,000 files with unknown rights, each within about 3 percentage points.
The audit changes three decisions. The requirements gain a must-have for duplicate detection on ingest. The rights-unknown share becomes a business case risk line. The migration scope could drop by up to half once duplicates and obsolete files are removed, depending on how far the two groups overlap.
Timeline and roles
A DAM content audit takes two to three weeks for a mid-sized organisation, as a DAMSelection rule of thumb, with three roles doing most of the work.
- The DAM manager or project lead owns the sheet and the method.
- IT runs file system reports and hash comparisons per location.
- Two or three daily operators review the sample for rights, metadata and use.
Schedule the audit before requirement workshops. Workshop participants then discuss measured problems with numbers attached. The selection team reviews the sheet at the Checkpoint 1 gate.
Frequently asked
How long does a DAM content audit take?
A DAM content audit takes two to three weeks for a mid-sized organisation, as a DAMSelection rule of thumb. File reports and hash checks take a few days. Most of the time goes into finding sources outside central IT and reviewing a sample of about 1,000 files for rights, metadata and current use.
How many files should a DAM audit sample?
A sample of about 1,000 randomly drawn files suits libraries of more than 100,000 files. That sample estimates any rate within about 3 percentage points at 95% confidence. Allocate the sample to each location in proportion to its file count, so large locations do not dominate the result.
What is a good duplicate rate for a DAM library?
DAMSelection publishes no benchmark duplicate rate, because rates depend on history, tools and team structure. Treat the measured rate as a migration input: every duplicate removed before migration lowers storage cost and clean-up effort. Rates differ widely between organisations with a central DAM and those relying on shared drives.
Should we clean up assets before choosing a DAM?
Classify assets before choosing a DAM, and delete clear duplicates and obsolete files early. Leave metadata repair until the schema is final, because the chosen DAM's fields and vocabularies decide what to repair. Early classification also shrinks the volume vendors quote on.
Who should run the DAM content audit?
The DAM manager or project lead should run the content audit, supported by IT for file reports and by two or three daily operators for the sample review. Agencies and regional teams supply access to their archives and confirm licence records for the assets they hold.