Reference Glossary
Stakeholder review
A structured checkpoint where designated reviewers — legal, brand, regional marketing, a client — approve or reject an asset before it moves to a publishable state.
Why it matters in a DAM
A DAM's review step is what stops an uncleared photo or an off-brand crop from reaching a live campaign — without it, 'approved' is just whoever uploaded the file deciding it's fine. Multi-market brands need more than one review lens: a hero image cleared for a US site might still need a separate pass for a market with stricter model-release or advertising rules.
A worked example
Common mistake
Review gets treated as a single yes/no gate with one reviewer, so an asset that's fine on brand but has a lapsed model release still gets approved because the person clicking 'approve' wasn't the one positioned to catch that.
Stakeholder review works because it splits approval into the specific lenses that actually need to check an asset — brand consistency, legal clearance, regional compliance, sometimes a client sign-off — rather than compressing all of that into one generalist’s judgment call. Each reviewer is looking for something different, and none of them can substitute for the others: a brand reviewer isn’t positioned to catch a missing model release, and legal isn’t the right check for whether a crop matches guidelines.
In a DAM, this is usually implemented as parallel or sequential approval steps attached to the asset’s workflow state, with each reviewer’s decision and any comments logged against the asset record. That log is what makes the review defensible later — if a wrong asset does ship, there’s a specific answer for who reviewed it and what they were checking for, rather than a shrug.
The review step is only as strong as the reviewers assigned to it. A single generalist reviewer approving on behalf of legal, brand, and region at once collapses the whole point of having separate checks.
Frequently asked
Why does stakeholder review use multiple reviewers instead of one approver?
Because each reviewer checks something different that the others can't substitute for — a brand reviewer isn't positioned to catch a missing model release, and legal isn't the right check for whether a crop matches brand guidelines.
What happens if an asset is approved by only a generalist reviewer?
It collapses the whole point of having separate checks — an asset that's fine on brand but has a lapsed model release can still get approved because the person clicking 'approve' wasn't positioned to catch that specific issue.
Why do multi-market brands need more than one review lens?
A hero image cleared for a US site might still need a separate pass for a market with stricter model-release or advertising rules, so regional review can reject an asset that already passed brand and legal.
What happens to an asset if one reviewer rejects it?
It gets returned to draft status pending the fix — for example, a banner approved by brand and legal but rejected by a regional reviewer for a missing model release goes back to draft until an updated release is obtained.
How is a stakeholder review decision logged, and why does that matter?
Each reviewer's decision and any comments are logged against the asset record, which makes the review defensible later — if a wrong asset does ship, there's a specific answer for who reviewed it and what they were checking for.
What's the practical difference between stakeholder review and publish state?
Stakeholder review is the checkpoint process itself — the reviewers and their decisions; publish state is the resulting lifecycle field, such as draft or approved, that the review outcome ultimately updates.