Content operations
Creative workflow and proofing in and around DAM
Quick answer
Creative workflow and proofing cover the steps between a creative brief and an approved asset: request, production, review, approval and handover. Organisations run proofing in one of three places: natively inside the DAM, in a work management platform, or in a specialist proofing tool integrated with the DAM. The right choice depends on volume, media types and regulatory review needs.
Key takeaways
- Proofing can live in the DAM, in a work management platform or in a specialist tool; each option suits a different volume and complexity profile.
- Most marketing assets need 2 to 4 review rounds, and each unnecessary round adds 1 to 3 working days to delivery (practitioner estimate).
- Only the final approved version, with approver, approval date and rights metadata, should enter the DAM as a published asset.
- Regulated content, such as food labels under Regulation (EU) No 1169/2011 or pharmaceutical packaging, needs an auditable approval trail.
Creative workflow and proofing determine how fast a brief becomes an approved, publishable asset, and the DAM is where that asset should land. The decision for most organisations is where proofing lives: inside the DAM, in a work management platform, or in a specialist tool connected to the DAM. Teams that define this handover clearly cut review cycles and stop unapproved versions from reaching channels.
The five stages of a creative workflow
A creative workflow runs through five stages, each with its own owner and system:
- Request: a structured brief with objective, channels, formats, deadline and budget.
- Production: designers and agencies create files in tools such as Adobe Creative Cloud or Figma.
- Review: stakeholders annotate drafts and request changes, round after round.
- Approval: a named approver signs off, sometimes with legal or regulatory review.
- Handover: the approved final enters the DAM with metadata and is distributed to channels.
Stages 3 and 4 consume most of the elapsed time. Most marketing assets go through 2 to 4 review rounds, and each unnecessary round adds 1 to 3 working days (practitioner estimate). Better briefs and fewer, named reviewers shorten the cycle more than any software feature.
Three architecture options for proofing
Choose the proofing architecture on volume, media mix and review complexity. The table compares the three options.
| Option | Best for | Strengths | Watch-outs |
|---|---|---|---|
| Native DAM proofing | Teams with moderate volume and one platform strategy | One system, no handover, single audit trail | Annotation depth varies by vendor |
| Work management platform | Marketing teams that plan projects, budgets and resources together | Links proofing to tasks, timelines and capacity | Approved files still need a DAM connector |
| Specialist proofing tool | High-volume studios, agencies, video and packaging | Deep annotation, version compare, guest reviewers | Extra licence and integration |
Several vendors combine creative workflow with asset management. Lytho and Aprimo bundle request, review and DAM functions, while DALIM SOFTWARE is known for colour-critical packaging and print review. Brandfolder sits inside Smartsheet's work management suite. Specialist tools such as Ziflow and Filestage integrate with several DAM platforms through connectors.
Proofing features that matter
Score proofing features against your actual media mix. For images and layouts, look for pixel-level annotation and side-by-side version comparison. For video, require frame-accurate comments and timecode references. For packaging and print, require colour separation views and measurement tools.
Process features matter as much. Automated routing by stage, parallel and sequential reviewers, due dates with reminders and guest reviewers without paid licences keep cycles short. Regulated content needs a full audit trail: food labels under Regulation (EU) No 1169/2011 on food information to consumers, for example, carry legal liability for errors, so record every decision and version.
Handing approved assets to the DAM
Only the final approved version should become a published DAM asset. Work-in-progress versions belong in the proofing or production system, otherwise users find five near-identical files and pick the wrong one.
Pass metadata along with the file at handover: campaign, approver, approval date, usage rights, expiry and channel. This links the creative workflow to DAM governance and keeps rights tracking intact. Test the connector during selection, using the integration criteria in our DAM integrations guide. AI-generated or AI-edited drafts need a flag that survives the handover, as covered in generative AI in DAM.
Measuring creative workflow performance
Track four indicators monthly: review rounds per asset, cycle time from brief to approval, the share of deliveries on schedule and the share of approved assets entering the DAM with complete metadata. Set a baseline in the first month, then target a 20 to 30% reduction in cycle time within a year (editorial estimate for teams moving from email to structured proofing). Agencies and in-house studios can use the same metrics to price work, as described in DAM for agencies.
What to do next
- Map your current creative workflow across the five stages and note where time is lost.
- Count assets per month by media type to choose between the three proofing architectures.
- Standardise the brief template and limit each review to named decision makers.
- Define the metadata that must travel from proofing to the DAM at approval.
- Measure review rounds and cycle time for three months, then reset targets within your wider content supply chain.
Frequently asked questions
What is online proofing?
Online proofing is the review and approval of creative files in a browser, where reviewers comment directly on images, PDFs, video frames or web pages. The tool tracks versions, collects decisions and records who approved what and when. It replaces email chains and annotated PDFs.
Do I need a separate proofing tool if my DAM has approval workflows?
Only for some teams. DAM approval workflows handle publish or reject decisions on finished assets well. A separate proofing tool becomes worthwhile when teams need pixel-level annotation, frame-accurate video comments, side-by-side version comparison or colour-accurate packaging proofs at high volume.
How do proofing tools connect to a DAM?
Typically through a native connector or API: work-in-progress files are proofed in the review tool, and the approved final version is pushed to the DAM with its metadata. Some DAM platforms include proofing natively, so no handover is needed. Define which system holds the master version at each stage to prevent duplicates.