Short answer
A DAM RACI is a responsibility matrix that assigns one accountable owner, plus responsible, consulted and informed roles, to every recurring DAM task: uploading, describing, approving, publishing, expiring rights, changing the schema and onboarding users. Teams that sign the matrix off before go-live avoid the two common failures in DAM operations: tasks nobody owns and changes nobody approved.
What a DAM RACI covers
A DAM RACI covers every task that repeats after go-live, from a single upload to a schema change. The DAM implementation project has its own plan. The RACI governs the years of daily operation that follow it.
The four letters carry fixed meanings. Responsible (R) does the work. Accountable (A) signs off and answers for the result, and each task has exactly one A. Consulted (C) gives input before the decision. Informed (I) hears about the decision after it is made.
DAMSelection assessment: adoption decides DAM success, and adoption depends on predictable service. Users return to the DAM when uploads are described within a known time and requests reach a named person, as the user adoption guide shows. The RACI makes that service predictable. It also feeds the DAM governance model, which sets the rules the named roles enforce.
The DAM roles to name
A DAM RACI needs eight roles, and each role needs a named person before go-live. Small teams combine roles in one person. The matrix still lists them separately, so the combined workload stays visible.
| Role | Purpose | Typical home | Time commitment |
|---|---|---|---|
| DAM owner | Owns the business case, budget, vendor and renewal | Marketing, brand or content operations | Part of a senior role |
| DAM manager | Runs the platform day to day, describes and audits assets | Content operations or the library team | 0.5 to 1 FTE (DAMSelection rule of thumb) |
| Taxonomy owner | Owns the metadata schema and controlled vocabularies | Library team or product content team | 1 to 2 days per month |
| Creators | Produce and upload assets, internal and agency | Studio, agencies, photographers | Per upload |
| Brand manager | Approves assets for use and owns the brand portal rules | Brand or marketing | Weekly approval slot |
| Legal and rights | Owns usage rights, releases and licence terms | Legal or rights management | On request and monthly review |
| IT and integration owner | Owns SSO, integrations, security and data flows | IT or enterprise architecture | Per change and incident |
| Champions | Train peers and collect feedback in each team | One per team or region | 2 to 4 hours per month |
The time figures are DAMSelection rules of thumb from PIMvendors practice for libraries of 20,000 to 200,000 assets. Measure actual effort in the first quarter and correct the plan. The DAM manager role page describes that role in more detail.
Full DAM RACI table
The full DAM RACI table assigns one A to each of 22 recurring tasks across content, rights, schema, access, integrations and vendor management. Copy the table, replace the role names with your own and delete rows that do not apply.
Column key for the table:
- Own: DAM owner. Mgr: DAM manager. Tax: taxonomy owner. Cre: creators.
- Brand: brand manager. Legal: legal and rights. IT: IT and integration owner. Champ: champions.
| Task | Own | Mgr | Tax | Cre | Brand | Legal | IT | Champ |
|---|---|---|---|---|---|---|---|---|
| Upload new assets | I | A | R | |||||
| Add required metadata at upload | A | C | R | |||||
| Enrich and correct metadata | A/R | C | C | |||||
| Record usage rights and releases | R | C | A | |||||
| Approve assets for use | C | R | A | C | ||||
| Publish to brand portal and channels | I | R | A | |||||
| Share assets with external parties | A | C | C | R | ||||
| Expire or withdraw assets at rights end | I | R | I | A | I | |||
| Archive or delete assets | I | A/R | C | C | C | |||
| Add a metadata field | I | C | A/R | C | C | I | ||
| Add or change vocabulary values | C | A/R | C | I | ||||
| Change a workflow | I | A/R | C | C | C | I | ||
| Grant user access and roles | A/R | C | ||||||
| Map SSO groups to DAM roles | C | A/R | ||||||
| Onboard and train new users | A | R | ||||||
| Change an integration mapping | I | C | C | A/R | ||||
| Monitor sync failures and incidents | I | A/R | ||||||
| Review vendor release notes | A/R | I | C | I | ||||
| Run the monthly change board | C | A/R | R | C | C | C | C | |
| Run the quarterly quality audit | I | A/R | C | C | ||||
| Report KPIs | A | R | I | I | ||||
| Manage vendor contract and renewal | A/R | C | C | C | C |
Each row holds one A, and the A sits with the person who can say no. Rights expiry belongs to legal because legal carries the liability. Schema changes belong to the taxonomy owner because a field added without design breaks search for every team.
Handover rules between DAM roles
DAM handovers need a trigger and a target time, because most delays sit between two roles. The RACI says who acts. The handover table says when the next role picks up the work.
| Handover | From | To | Trigger | Target time (DAMSelection rule of thumb) |
|---|---|---|---|---|
| Upload to enrichment | Creators | DAM manager | Asset lands in the upload queue | 2 working days |
| Enrichment to approval | DAM manager | Brand manager | Required fields complete | 3 working days |
| Rights check | DAM manager | Legal and rights | Asset shows a person, a location or third-party content | 5 working days |
| Access request | Requester | DAM manager | Request form submitted | 1 working day |
| Schema request | Any user | Taxonomy owner | Request form submitted | Next monthly change board |
| Sync failure | Monitoring alert | IT and integration owner | Failed job or error queue above threshold | Same working day |
Creators can cut the enrichment step by embedding rights data at source. The IPTC Photo Metadata Standard defines embedded fields for rights information, such as the Web Statement of Rights. Agencies that fill those fields before upload hand the DAM manager a described asset. Write that duty into agency briefs and contracts.
Measure each handover from the timestamps in the DAM audit log. A handover that misses its target three months in a row signals a capacity gap or a missing deputy.
Rules for a DAM RACI that works
A DAM RACI works when it follows six rules that keep accountability single and workload real.
- Give every task exactly one A. Two accountable people means nobody decides.
- Put the A at the lowest level that holds the authority. A CMO as A on uploads creates a queue.
- Check that every R has time in the job description. An R without capacity is an empty box.
- Keep C to three roles or fewer per task (DAMSelection rule of thumb). Every extra C adds a waiting step.
- Name people, with a deputy for every A. Holidays and leavers otherwise stop approvals.
- Publish the matrix inside the DAM, linked from the help page, so users see who to ask.
The stakeholder map from selection usually supplies the first list of names. The selection team often continues as the first change board.
Typical owners by organisation size
Typical DAM owners shift with organisation size: small teams combine roles, and enterprises split them by brand or region.
| Role | Small team (under 50 users) | Mid-market (50 to 500 users) | Enterprise, multi-brand |
|---|---|---|---|
| DAM owner | Marketing lead | Head of brand or content operations | Global content operations director |
| DAM manager | Marketing coordinator, part time | Dedicated DAM manager | Central DAM team plus brand librarians |
| Taxonomy owner | Same person as DAM manager | DAM manager or product content lead | Central taxonomy owner with brand stewards |
| Brand manager | Marketing lead | Brand team | Brand manager per brand |
| Legal and rights | External counsel on request | Legal counsel | Rights management team |
| IT and integration owner | Vendor support plus IT generalist | Application owner in IT | Integration team and enterprise architect |
| Champions | Not needed | One per team | One per brand and region |
The user bands are DAMSelection rules of thumb. A 40-person team with five integrations needs mid-market roles. Integration count and brand count drive role splits more than headcount.
How to build and review the DAM RACI
The DAM RACI takes about two workshops to build and one review after the first quarter of use.
- List every recurring task from the governance rules, the workflows and the integration list.
- Run a 90-minute workshop with the eight roles and fill the matrix row by row.
- Resolve every row with zero or two A entries before the workshop ends.
- Check capacity: total the R entries per person and compare them with available hours.
- Publish the signed matrix in the DAM and in the go-live checklist.
- Review after 90 days, using support tickets and audit findings as evidence.
- Review again after every reorganisation, new integration, new brand or vendor change.
Support tickets show where the RACI fails. Tickets that bounce between teams mark tasks with no clear A. Tickets that wait for days mark an R without capacity.
DAM RACI failure patterns
DAM RACI failures follow five recognisable patterns, and each one has a direct fix.
- The administrator owns everything. Fix: move content and approval tasks to the business, keep configuration with the administrator.
- Agencies upload without metadata. Fix: make creators R for required fields and block uploads without them.
- Nobody owns rights expiry. Fix: make legal the A and automate expiry dates from the usage rights fields.
- Schema changes arrive by email. Fix: route every field and vocabulary request through the monthly change board.
- Champions exist on paper only. Fix: give champions a monthly hour in their objectives and a feedback channel to the DAM manager.
The rights management guide covers the expiry process in detail. The metadata model builder helps the taxonomy owner document fields before the change board reviews them.
Frequently asked
Who should own the DAM?
The DAM owner should sit in the business function that gains most from the DAM, usually brand, marketing or content operations. IT owns security, sign-in and integrations. A business owner keeps priorities tied to content outcomes, and the DAM manager reports to that owner for day-to-day operation.
What is the difference between a DAM manager and a DAM administrator?
A DAM manager runs the library: metadata quality, user support, audits and reporting. A DAM administrator configures the platform: roles, permissions, workflows and settings. Small teams combine both roles in one person. Larger teams separate them, and the administrator often sits in IT or with the vendor's managed service.
How many people does it take to run a DAM?
A library of 20,000 to 200,000 assets typically needs 0.5 to 1 FTE as DAM manager, plus part-time taxonomy, rights and IT roles (DAMSelection rule of thumb). Volume of new uploads, number of brands and number of integrations drive the effort more than total library size.
Who approves new metadata fields in a DAM?
The taxonomy owner approves new metadata fields and vocabulary values, after the monthly change board has consulted the DAM manager, brand and IT. One accountable owner keeps the schema consistent. Uncontrolled field creation is the fastest route to duplicate fields and failing search.
How often should a DAM RACI be reviewed?
Review the DAM RACI 90 days after go-live, then once a year and after every trigger event: a reorganisation, a new integration, a new brand or a vendor change. Use support tickets and audit findings as evidence for each change to the matrix.