Key Takeaways — brief reading, less than 30 seconds
  • Creative Ops vocabulary is borrowed from advertising production, project management, and marketing — and the same word means different things on each side of the handover.
  • A brief, a deliverable, and a project are three different units: the brief opens the work, the deliverable is the output, the project is the bounded container around both.
  • DAM, MAM, and PAM are not interchangeable — brand teams need a DAM, video teams need a MAM, and PAM is two unrelated categories sharing one acronym.
  • Approval, sign-off, and creative review are three distinct activities — conflating them is the single most common cause of slipped timelines.
  • Throughput is the metric Creative Ops Managers are graded on; review rounds and hand-offs are the variables that move it.

Editor's note: This is a working glossary, not an exhaustive one. Definitions are plain language; cross-references go to the deep-dives we’ve written. Suggestions welcome — the field is moving and the vocabulary is moving with it.

How to Use This Glossary#

Plain-language definitions, one per term, with examples where useful. Cross-references between related terms; deep-dive links where we’ve written a longer piece. Aim for the definition you wish someone had given you the first time the term came up in a meeting.

Many of these terms drift in meaning between teams. “Brief” means one thing in marketing and another in advertising production; “asset” means one thing to a brand team and another to a video studio. The definitions below pick the meaning most common across in-house creative teams as of early 2026; the cross-references show where the term sits in a larger system.

Open dictionary lying flat with a hand turning the page, columns of indexed entries visible.
A glossary is a working dictionary — alphabetized, cross-referenced, and never quite finished.

Terms: A–H#

AI tagging / Auto-tagging.
Machine-generated keywords applied to an asset at ingest, using image or video recognition to cut manual tagging. Fast and tireless; only as good as the model behind it and the review that follows. See AI Image Tagging.
Annotation / Markup.
The two halves of feedback on a proof: the markup is the shape or region drawn on the asset; the annotation (or comment) is the note attached to it. Together they make feedback specific instead of “something feels off in the corner.” See Comments vs Markups vs Annotations.
Approval workflow.
The defined sequence of reviews and sign-offs an asset moves through before it can be published or shipped to a client. Lives on the artefact, not in a chat thread.
Asset / Digital asset.
Any creative file the team produces, owns, or distributes — logo, photo, video, deck, social tile, brand template. The unit of work in a DAM. See What is Digital Asset Management for the foundational definition.
Audit / Creative asset audit.
An inventory of the team’s existing assets — what exists, where it lives, who owns it, what state it’s in. Usually the first step before adopting a DAM. See Creative Asset Audit.
Brand kit.
The canonical bundle of brand assets — logo, colors, fonts, templates, photography, voice guidelines — in one library that internal teams and external partners draw from. See Brand Management.
Brief / Creative brief.
The document that opens a creative project, specifying audience, message, deliverables, mandatories, and out-of-scope. Without one, the work starts unclear. See Creative Brief Template.
Campaign.
A coordinated set of creative assets and channels organized around a single objective and timeframe. The unit of work above “asset” and below “quarter.”
Change order.
A formal scope change after the brief has been signed. Adds new deliverables or modifies existing ones; should always trigger a timeline and budget review.
Channel.
The distribution path an asset ships through — web, email, paid social, organic social, OOH, print, broadcast, partner-syndication. Most rights and approval rules are channel-specific.
Contact.
An external person the team works with on a project — client, freelancer, agency partner, vendor. A contacts layer in a DAM (or in a CRM) keeps track of who’s involved without conflating identities with project records.
Controlled vocabulary / Folksonomy.
Two ways to source tags. A controlled vocabulary is an approved list everyone picks from; a folksonomy is free-text tags users invent — flexible, but inconsistent and hard to search at scale. The taxonomy decision every growing DAM faces. See DAM Metadata Taxonomy.
Creative ops / Creative operations.
The discipline of running the production line of a creative team — intake, project setup, resource allocation, tooling, throughput metrics. The role that owns this lives in The Creative Operations Manager.
Creative review.
A working session where stakeholders review draft creative and give feedback. Distinguished from approval (which is the formal sign-off afterwards). See Design Approval Process.
DAM (Digital Asset Management).
A platform that stores, indexes, and distributes creative assets — logos, photos, videos, decks — with metadata, version control, rights tracking, and access permissions. The brand-team-shaped tool. See DAM vs MAM vs PAM for the category disambiguation.
Definition of done.
The criteria a deliverable must meet before it’s considered complete. Usually written into the brief. Avoids the “is it ready?” conversation at the end of every project.
Deliverable.
A specific output the project produces — one banner set, one 30-second video, one landing page. The unit of project commitment.
Design review.
The same activity as creative review when the asset is design-led. Often used interchangeably; some teams reserve “design review” for craft-focused critique and “creative review” for stakeholder sign-off.
DRM (Digital Rights Management).
Technical enforcement that restricts how a file can be opened, copied, or shared. The security control a watermark is not — a watermark signals provenance, DRM prevents the act. Heavier to deploy, and rarely needed for everyday creative work.
Handover / Hand-off.
The moment a finished asset transfers from the producing team to the next stage — from design to dev, from studio to client, from brand to marketing. Hand-offs cost time; minimizing them is a creative-ops discipline.

Terms: I–Q#

Ingest / Ingestion.
Bringing assets into a DAM — uploading the file and extracting or attaching its metadata at the point of entry. Where a searchable library is won or lost: skip the metadata at ingest and no one adds it later.
Intake form.
The structured form stakeholders fill in to request creative work. Forces the basic brief fields up front; reduces back-and-forth before the project starts.
Kickoff meeting.
The first working session of a project where the team aligns on brief, timeline, deliverables, and roles. Runs from a template if the team is mature; from improvisation if it isn’t.
Library.
A collection of related assets — brand library, image library, template library. Often a top-level navigation concept inside a DAM.
MAM (Media Asset Management).
A video-first asset-management system optimized for long-form footage, timecode-based metadata, and broadcast workflows. Different category from DAM. Common players: Iconik(opens in new tab), Evolphin(opens in new tab), Avid(opens in new tab).
Mandatory.
A specific element the brief requires — a callout, a legal disclaimer, a brand-required color. The opposite of a suggestion. Mandatories should be enumerated in the brief, not communicated mid-project.
Metadata.
Structured information about an asset — tags, categories, source, license, expiry date, owner, project. Searchable and filterable. The thing that makes a DAM different from a folder. See DAM Metadata Taxonomy.
Milestone.
A scheduled checkpoint in a project — brief signed, design v1 delivered, legal review passed, asset shipped. Milestones structure the timeline; in our experience, a missed milestone is the first reliable sign of slippage.
Mood board.
A reference collection that signals the visual direction for a project — photography style, color palette, layout references. Lives in the brief or as an attachment to it.
On-brand.
Compliant with the brand’s visual and verbal guidelines. The judgement is the brand lead’s; the system that supports it is the brand kit.
Out of scope.
Explicitly listed in the brief as not part of this project. Prevents the “while you’re at it, can you also…” expansion at review time.
PAM (Product / Production Asset Management).
Two unrelated categories with the same acronym. Product PAM manages e-commerce SKU imagery and pairs with a PIM. Production PAM (ftrack(opens in new tab), Flow Production Tracking(opens in new tab), formerly ShotGrid) handles film/game pipeline workflow.
PIM (Product Information Management).
The system of record for product data — specs, copy, pricing, SKUs — that feeds e-commerce and catalogs. The structured-data counterpart to a DAM’s media; a product PAM sits between the two. See DAM vs MAM vs PAM.
Portal.
A branded, externally-accessible surface where clients or partners review and download assets. A controlled extension of the DAM into the client relationship.
Post-mortem / Campaign recap.
The structured review at the end of a campaign — what worked, what didn’t, what to do differently. The bookend to the brief. See Campaign Recap Templates.
Pre-production.
The planning phase before the make phase — storyboarding, location scouting, casting, asset prep. Where most of the savings on the make phase come from.
Project.
A bounded unit of creative work with a brief, deliverables, a timeline, and a defined end. Distinguished from a campaign (which can have multiple projects) and a folder (which has neither).
Proof.
A draft version of an asset shared for review, usually watermarked. The state between “in production” and “delivered.”
Proxy.
A lightweight, low-resolution stand-in for a large master file, used for fast browsing, review, and editing — the master is touched only at export. Standard in video and MAM workflows, where the originals are too heavy to move around.
Quality control.
The pass that verifies a deliverable meets specs before delivery — right dimensions, color profile, file format, brand compliance. Usually owned by the producing team, not the reviewing team.
Quick turn.
A short-cycle project — in our experience usually 24–72 hours, not an industry-standard window — with a stripped-down brief and abbreviated review cycle. The format social-and-email-heavy teams run weekly.
Tall library shelves filled with hardback reference books receding into the distance.
Reference is a stock you maintain — the shelves stay useful only if the index does.

Terms: R–Z#

RACI(opens in new tab).
An accountability matrix for a project: Responsible, Accountable, Consulted, Informed. Each role for each deliverable. Useful when stakeholder roles are unclear; overkill when the team is small.
Reference.
An external example used to communicate creative direction — a competitor’s campaign, a website, a still from a film. References belong in the brief, not in feedback rounds.
Rendition.
An auto-generated alternate version of an asset — a different format, size, crop, or color profile — derived from a single master. The grid thumbnail, the web-sized JPG, the social crop: all renditions of one source file.
Retainer.
A pricing model where the client pays a fixed monthly or quarterly fee for a contracted volume of creative work. Trades discount for predictability. Common between brands and external studios.
Retro / Retrospective.
A working meeting after a project closes where the team reviews what went well and what didn’t. Produces process changes for the next project.
Review round.
One full cycle of feedback from a stakeholder or stakeholder group. In our experience each round adds something like 3–5 business days — an operator estimate, not an industry-published figure. Counting them up front is how project timelines stay honest.
Rights management.
The discipline of tracking who owns what, what licenses cover which uses, and when expiry dates land. The layer below watermarking and above asset storage. See Image Rights Management.
Scope creep.
The gradual expansion of project deliverables beyond the original brief, usually without a corresponding timeline or budget adjustment. In our experience, the most common reason creative projects ship late.
Sign-off.
The formal approval that an asset can ship. Distinguished from a thumbs-up or a verbal “looks good.” Lives on the artefact in a system designed to record it.
Single source of truth (SSOT).
One authoritative, governed library where the current approved version of every asset lives, so teams stop working from stale copies scattered across drives and inboxes. The phrase every DAM vendor sells on; the outcome the tool is supposed to deliver. See What is Digital Asset Management.
Single-minded proposition.
The one thing the campaign is trying to communicate. Borrowed from advertising. The brief that can’t state one in a sentence is incomplete.
Stakeholder.
Any person who reviews, approves, or has a vested interest in the project. Can include people who don’t produce the work but can stop it from shipping.
Storyboard.
A sequence of sketches that plans a video or animation before production starts. Cheap to revise; expensive to skip.
Tag.
A keyword applied to an asset for searchability. Usually drawn from a controlled taxonomy rather than free-text.
Taxonomy.
The structured vocabulary of tags, categories, and metadata fields a DAM uses to organize assets. The thing that makes search work or fail.
Throughput.
The volume of creative work the team ships per unit time, measured in projects, deliverables, or revenue. The metric Creative Ops Managers are graded on.
Usage rights / Licensing.
The specific permissions a license grants — which channels, territories, and time window an asset may be used in before it expires. The object rights management tracks; the detail that turns a stock photo from an asset into a liability the day the license lapses. See Image Rights Management.
Version control.
The discipline of tracking which version of an asset is current, which is approved, which is in review. See Version Control for Designers.
Watermark.
A visible or invisible marker on an asset that signals provenance or stage. Useful for drafts and shared work; not a security control. See Watermark Protection.
Workflow.
The sequence of steps an asset moves through from intake to delivery. The thing creative-ops people optimize; the thing the team complains about when it doesn’t fit the work.
Workspace.
The DAM-level container for one team’s assets, members, and configuration. A single organization may have multiple workspaces (one per brand, one per business unit).

Suggest a Term#

Missing terms, terms with bad definitions, terms used differently in your team — we want to hear about all three. The glossary improves by being read by people who use the words for real.

The terms in this glossary land at 62 today. The number will grow as the field matures — AI-generated assets are introducing new vocabulary every month, retainer-economy practices are blurring brand-and-agency relationship terms, and the rise of in-house creative teams is shifting what production-side language survives the journey to the brand side. The glossary stays useful only if it stays current. If you spot a gap, send it.

Glossaries are tools, not reading material. Keep a shared definition to point at the next time “approval” and “sign-off” get used interchangeably in a stand-up, or the next time a vendor demo conflates DAM and MAM. Bookmark the page, link teammates to specific terms when the disagreement is really a vocabulary mismatch, and follow the cross-references into the deep-dives when a term turns out to be the one your team needs to actually fix.

Frequently Asked Questions #

Where do these terms come from?
A mix of advertising production (brief, mandatory, single-minded proposition), project management (RACI, milestone, scope creep), and DAM / MAM / PAM vendor categories (asset, workflow, taxonomy). The glossary picks the meaning most common across in-house creative teams in 2026, but the same word often carries a different sense in an agency or a broadcast environment.
Who is this glossary for?
Three groups: a new Creative Ops Manager learning the vocabulary of the role; a marketing or brand lead who hires a Creative Ops Manager and needs the shared language; and a DAM buyer comparing tools whose vendor decks throw acronyms around. If you sit between brand, creative, and project management, this is the working dictionary for the seams.
Where does Creative Ops sit in the org chart?
Usually inside marketing, reporting to a VP of Brand or VP of Marketing, with a dotted line to the head of design or creative director. The role owns the production line — intake, project setup, tooling, throughput — without owning the craft. In larger organizations it sits alongside Marketing Ops and Design Ops as a peer function.
Is this a Creative Ops vs Project Management glossary?
No — the two disciplines overlap heavily and the vocabulary travels in both directions. Project management contributes RACI, milestone, kickoff, and retro; Creative Ops contributes brief, mandatory, on-brand, and proof. A Creative Ops Manager uses project management vocabulary daily; a project manager running a creative project needs the brand-side terms here.
What is the one term every CMO should know?
Throughput — the volume of creative work the team ships per unit time. It is the metric that turns Creative Ops from an unmeasured cost center into a measured production function. Once a CMO can name throughput in projects per quarter, every other conversation — tooling, headcount, retainers, automation — has a denominator.
Share this article:

Related Articles