Tags aren't labels. They're how the workflow knows what to do.
Aproove uses workflow tags at four levels: Project, Proof, Section, and Note. Tags are not just visual indicators. They drive dashboard visibility, filter and sort behavior, workflow routing, reporting, and downstream automations. Tags can be applied by reviewers as part of their normal work, set as defaults that auto-apply when a note is created, or generated by AI Agents during automated review. Humans and AI share the same tag taxonomy, so the same filter, the same view, and the same workflow rule act on both.
What it is
Workflow tags in Aproove are structured labels with semantic meaning the platform understands. The four workflow tag types attach at four different levels of the work:
- Project Tags label a whole project (Urgent, On Hold, Q4 Release). They surface as dashboard columns and feed filters that scope a portfolio view.
- Proof Tags label a proof, page, or set of pages (Customer Review, Like, Reject). They can gate visibility at workflow steps, support voting (when multiple users tag the same proof, the count surfaces), and drive sort and filter behavior in the Proof Plan View.
- Section Tags label a group of proofs organized into a Section (Legal Approved, Marketing Approved). One section tag can represent the approval of every proof in the section, replacing per-proof tagging with section-level decisioning.
- Note Tags label individual annotation notes (Dairy, Reject Note, Regulatory Flag). They can be required at note creation, restricted by permission, made mandatory with a justification field, used to control note visibility across teams, and reported on at granular level.
All four tag types share the same underlying mechanism: a controlled vocabulary configured by administrators, governed by permissions, and surfaced consistently across the platform.
How it works
Project Tags. Administrators define the workflow tag set (Urgent, On Hold, At Risk, Holiday Hold, Q4 Release, anything that matters at portfolio level). Project managers apply them when launching or updating a project. Tags display in dashboard columns and feed Advanced Filters, so a saved view like "Urgent Projects" surfaces the right work for the right people.
Proof Tags. Applied per proof or to multiple pages at once in Proof Plan View. Common patterns include creative options voting (designers upload variants, internal reviewers tag the strong ones with "Like", the Creative Director tags the finalists with "Customer Review"), step-gated visibility (only proofs tagged "Legal Review" are visible to the Legal team at the relevant workflow step), and quick sorting (filter the Proof Plan View by tag to focus on a subset).
Section Tags. When proofs are organized into Sections (web ads grouped by destination site, packaging artwork grouped by SKU, regulatory documents grouped by submission), a single Section Tag can carry the approval of every proof in that section. This replaces proof-by-proof tagging with section-level decisioning when the group genuinely moves together.
Note Tags. The richest tag type. Note Tags can be configured to:
- Auto-apply at note creation as Default Tags based on the user, the workflow step, the project type, or the form context. A Dairy merchandiser's notes are automatically tagged "Dairy" without manual action.
- Be made mandatory so a note cannot be saved without a tag selection.
- Require an explanation so applying a "Reject Note" tag forces the user to enter a justification before the action commits.
- Control visibility so notes tagged "Legal" are hidden from non-Legal users at certain steps, or notes tagged "Internal" stay invisible to the customer-facing workflow.
- Drive reporting so teams can analyze tag distribution across a project, across many projects, or across time to identify trends, bottlenecks, or quality patterns.
- Filter the notes panel so a reviewer can focus on the tag categories that matter to their role and hide the rest.
Voting on tags. When multiple users apply the same tag to the same element, Aproove counts the votes and surfaces the count. This works for Project, Proof, and Note Tags, and is especially useful at the Proof level for creative-options voting or internal preference polling.
Tags applied by humans or by AI agents
The same Aproove tag taxonomy applies to AI Agent output. When an AI Agent runs against a proof and identifies an issue, the resulting note can carry the same tags humans use. A brand-consistency Agent can tag every note it creates with "Brand Issue". A regulatory checker can tag with "Regulatory Flag". A copy-accuracy Agent can tag with "Copy Issue".
This matters operationally because every existing filter, view, dashboard column, visibility rule, workflow trigger, and report that already works for human-applied tags works for AI-applied tags too. The reviewer who filters the notes panel to "Brand Issue" sees both the AI's flags and the brand team's flags, in one view, sorted by the same criteria. The QA report that counts Regulatory Flags counts them whether a human or an AI applied them. The workflow step that gates on the presence of a "Final Approval" tag does not need to know who applied the tag.
AI-generated notes carry an [AI GENERATED] prefix in the note text so reviewers can always distinguish AI findings from human findings when that distinction matters. The tag itself is the same tag.
The result is one annotation language across humans and AI, one set of filters, one set of governance rules, and one source of truth for what was flagged on the proof.
Benefits
- One tag system across four levels. Project, Proof, Section, and Note Tags share the same controlled vocabulary, permission model, and filter behavior, so users learn one pattern and use it everywhere.
- Visibility control through tags. Tagged proofs can be made visible only to specific workflow steps or user groups. Tagged notes can be hidden or surfaced based on team and role.
- Mandatory tags and forced justification. Critical tags (rejections, approvals, escalations) can require the user to make a deliberate choice and explain it before the action commits.
- Default Tags for automatic classification. Notes can be auto-tagged at creation based on user, step, or context, so the right metadata attaches without manual effort.
- Section Tags for bulk approval. When a group of proofs moves together, one Section Tag represents the whole group, replacing per-proof tagging.
- Voting and polling. Multiple users tagging the same element surfaces the count, enabling lightweight internal preference polling on creative options.
- Tag-driven reporting. Note Tag distribution across a project, a portfolio, or a time period surfaces trends, bottlenecks, and behavioral patterns for QA, training, and process improvement.
- Human and AI share the same tags. AI Agent output uses the same tag taxonomy as human reviewers, so existing filters, views, and reports cover both without parallel infrastructure.
- AI provenance preserved. AI-generated notes are prefixed [AI GENERATED] so reviewers can always tell what came from where, even when the tag itself is identical.
Who it's for
- Project managers using Project Tags for portfolio status communication and Advanced Filters scoping.
- Creative teams using Proof Tags for internal voting and customer-facing proof selection.
- Legal, regulatory, and brand reviewers using Note Tags for findings classification with mandatory justifications and visibility scoping.
- Production and prepress teams using Section Tags to approve grouped artwork in bulk.
- Operations and QA leaders using tag-based reporting to spot trends, bottlenecks, and quality patterns across many projects.
- Teams running AI Agents who want AI findings to flow into the same filtered views and reports their human work uses.
Built for regulated environments where failures create real risk
Insurance, healthcare, and enterprise teams face unique approval challenges. Aproove handles state-by-state variations, mandated language, FDA submissions, and multi-geography brand governance without breaking a sweat.
Trusted by leaders
Used by teams that cannot afford uncertainty in their approval process.
"Implementing Aproove has dramatically reduced errors, increased motivation and satisfaction across the teams and importantly, saved the operation significant hard costs."
“The Aproove team are the best team in the world. I feel like I'm their only customer, they are always there for me.”
"Within a short period, we were able to reduce 25 workflows into a single workflow. The team saw a 15-week reduction in getting new marketing packages from idea to market. More importantly, it ensured that all the packages were compliant with regulatory requirements. All steps, comments, and approval are captured and saved for any audits."
More ways to streamline high-stakes workflows
See how workflow tagging with Aproove turns content into signal for humans and AI Agents alike
