The project tracker says "In review." Great. In review where? Which file? Which cut of the video? Is the feedback about the version the designer exported this morning, or the one from three days ago that's still sitting in a Slack thread? Nobody can tell from the card alone, so someone has to stop what they're doing and ask.

Between what the tracker claims and what's actually happening on the file is where creative projects actually fall apart. A status label only helps when it lives on the asset it describes, not floating in a separate tool that points at a file somewhere else.

There's a catch though: task lists, timelines, and capacity planning still belong in a project management tool like Asana, Monday, or ClickUp. But the status of the actual creative work belongs in the asset library, right next to the work.

This piece covers why task-based tracking breaks down on creative work, what asset-level status fields and Kanban views look like in practice, and how one deliverable moves through its full lifecycle.

Project management tools model work as a task with a due date and an owner, but creative work doesn't move that way. A single deliverable is really many versions of many files, and each version carries its own review state at any given moment.

That structural mismatch produces a few specific failures: status that stops syncing with the file it describes, feedback scattered across half a dozen tools, and approvals nobody can trace back later.

The status is on the card instead of the file

A card that reads "Hero image — in review" tells you almost nothing useful. Which export is under review? The 9:16 crop or the 16:9? The version with the updated tagline or the one before? To answer, someone has to leave the tracker, find the file, and confirm. That's friction on every single lookup.

Worse, the split creates a translation layer between two systems that constantly fall out of sync. One person maintains the tracker while another maintains the files. Within a few days, the card and the actual work no longer agree.

The alternative is to make status a property of the deliverable itself. When the state lives on the file, the two can never separate, because they're the same object.

Feedback ends up in multiple places at once

Creative feedback has a way of landing everywhere except where the next person will look. On any given project it scatters across:

• Slack threads that scroll away by lunch

• Email replies buried in a chain

• Comments inside a PM tool

• Verbal notes from a review call nobody wrote down

• Marked-up screenshots pasted into a doc

The downstream cost is that designers waste time reconciling conflicting notes. Six weeks later, nobody can explain why a layout changed because the decision trail evaporated.

Air handles this differently. Reviewers pin visual annotations directly to images and timestamp comments on video timelines, keeping feedback attached to the exact asset and version.

Nobody can prove what was approved

You know the pattern: Someone approves the work in a meeting. A thumbs-up emoji appears. None of it records who signed off, on which version, and when. So the approval happened, but there's no real evidence of it.

For brand stewards and executive approvers, that's a genuine risk. An unapproved or outdated file ships to a client, and the cleanup costs more than the review ever would have. The fix, which we'll get to, is approval states that live on the asset as structured data, complete with a visible record of who moved the status and when.

Teams that track creative project status on the asset build it from three simple pieces:

• Structured fields on every file

• A Kanban view driven by those fields

• Version stacks that keep the history intact.

Together they replace the tracker-plus-folder workaround most teams are living with. Here's how each one works.

Status, owner, and dates as fields on every asset

Air ships with a set of default fields on every asset: status, rating, usage rights, and assignee come standard on each workspace, and on the Enterprise plan, you can customize them to fit your needs. On top of those, you can add due dates and expiry dates, so each deliverable carries its own state and named ownership from the moment it lands.

Custom fields extend this for campaign-level tracking. You can add extra information to any asset, file, or board in Air, which makes it easier to track usage rights, asset owners, expiration dates, and social post dates.

For example, a single asset's field set might read: Q3 Launch / Paid Social / 9:16 / Needs Approval / Assignee: Maya / Due Aug 12 / Expires Dec 31.

Because status is metadata, "show me everything in Needs Approval for Q3 Launch" becomes a filter. Expiry dates earn their keep for any team managing licensed photography, talent releases, or influencer content, since the file itself flags when its usage window closes.

A creative project status Kanban built on real files

The Kanban view sits directly on your board's data, so there's no second system to update. The columns match the values of a single-select custom field in your workspace. Drag a card from one column to the next and you've changed the asset's status. No double entry, no reconciling a card against a file.

Each card is the asset itself, with a visual preview. Reviewers see the actual work rather than a text description of it. The board becomes a creative project management tool built on the files themselves.

One more advantage: a single asset can appear across multiple boards without duplicating storage. That means the creative team's production board and marketing's campaign board can look at the same file from different angles. Update a field in one place and it updates everywhere.

Version stacks that keep the approved file obvious

Version stacking keeps the workspace clean while preserving the full trail of creative decisions. When someone uploads a new iteration, it stacks on top of the original rather than sitting beside it as another near-identical file. That means instead of "hero-v2" cluttering the board next to three lookalikes, you get one canonical asset with its history tucked underneath.

The practical payoff is a single file to link to, plus the ability to compare versions or revert if a change went the wrong direction. And when status lives on the stack, the current approved file is always identifiable.

That's the single biggest safeguard against publishing an outdated variant.

Here's how to manage creative projects in your asset library by following one deliverable through its full lifecycle. Each stage adds context to the same asset instead of handing it off to another tool, so the file gets richer as it moves rather than getting lost in translation.

Stage 1: Intake without another login

Creative work starts with getting the raw material in the door, and that's usually where teams lose the first week. A Content Collection form solves it with a public upload link. Collaborators outside your workspace can add files directly to your boards through a unique link you share. No account, no seat, no login.

Submitters never get access to the workspace afterward, which keeps intake wide open without opening the library itself. Make the key fields required on the form so assets arrive already sorted. Ask for campaign, channel, deadline, and intended use up front, and nothing needs triage later.

For an agency team, this replaces two weeks of chasing clients over email. Send one link at kickoff and collect logos, product shots, and brand files in a single organized place.

Stage 2: In progress with a clear owner

Once a file is in, set its Status and Assignee on upload. Now every work-in-progress deliverable has a named owner and a visible state, and there's never a mystery about who's holding it. 

Boards organize the full deliverable set for a campaign and a stacked filter surfaces everything still in progress across every campaign in one view.

Movement updates reach the team without anyone opening the tool. Air's Slack integration pushes notifications for uploads and activity, so the people who need to know get pinged in the channel they already live in. That keeps the work visible without forcing everyone to babysit a board all day.

Stage 3: Review with feedback pinned to the work

A review round runs entirely on the asset. Mention the approver on the file, drop pinned comments on the exact area of an image or timestamped notes on the video timeline, then upload the revision as a new version on the same stack. Everything stays in one place.

Because the comments live on the asset, the next designer to open it inherits the whole decision history instead of reconstructing it from Slack.

The reasoning behind every change travels with the file. Large video files stay quick to review, too, since Air generates lightweight proxies and scrubbable previews. Reviewers aren't waiting on multi-gigabyte downloads to leave a note.

Stage 4: Approval that documents who signed off

Creative approval status tracking works through the status field itself. Build a structured approval workflow using values like "Needs Approval," "Changes Requested," and "Approved," then sync them to Kanban columns. Now approvers work a queue instead of digging through a thread.

Every move documents who approved what and when, which retires the ad-hoc approval chain for good. A saved filter for everything marked Approved becomes the team's live source of truth for what's safe to ship. Anyone can check it in seconds without asking a single person whether a file cleared review.

Stage 5: Approved work that gets reused

Approval should start an asset's useful life, not end it. Approved files stay searchable through AI-generated Smart Tags, custom fields, and conversational search, so the work you already cleared is easy to pull back up months later, which means the value doesn't get buried the moment the campaign ships.

From there, teams adapt approved work in Canvas without leaving the library or restarting the whole approval cycle. Resize a hero shot for a new channel, batch-swap backgrounds across a set of product images, or trim a cut for a shorter placement.

Skills takes it further by letting you save a repeated edit as a named, reusable workflow the whole team can run across a batch of approved assets at once. The point is plain: multiply what's already approved instead of rebuilding it from scratch.

The tracker-that-points-at-a-file model adds a translation layer to asset management that breaks within days, and so keeping status on the work removes it entirely.

This path is straightforward:

1. Collect requests through intake forms that need no seats

2. Set status and owner on every asset as it arrives

3. Review with pinned and timestamped feedback that stays on the file

4. Document approvals in structured fields synced to Kanban

5. Adapt approved work instead of rebuilding it

Air keeps assets, versions, approvals, and context in one visual workspace, and it pairs cleanly with whatever PM tool your tasks already live in. Your producer runs the tasks in Asana, Monday, or ClickUp, for example. Air runs the work.

Start a free Air workspace and put one campaign's deliverables through the full lifecycle, from intake to reuse.

Is Air a project management tool?

No. Air doesn't offer task lists, timelines, or capacity planning, and it isn't trying to replace Asana, Monday, or ClickUp. It manages creative projects around the assets themselves, tracking status, ownership, and approvals on each file. And it connects to your PM tool where the tasks live.

How is asset-level project status different from task-based project tracking?

Task-based tracking models work as a card with a due date, which sits separate from the actual file. Asset-level status lives on the deliverable itself, so the version, owner, reviewer, and approval state can never drift away from the work they describe.

Can clients and stakeholders see creative project status without an Air account?

Yes. Share a board via a share link and external stakeholders can view it with no login required. The Kanban view shows up on the share link once metadata and custom fields are enabled and the workspace has at least one single-select custom field.

Can status changes sync automatically between Air and Asana, monday, or ClickUp?

Yes, on Business and Enterprise plans through Zapier, Make, n8n, or the API rather than native connectors. A trigger like "Board Custom Field Updated" from Air can fire an action such as "Add Tag to Task" in Asana, connecting the two apps to automate your workflow.

What happens to comments and approvals when someone uploads a new version?

New versions stack on top of the original asset, and the comment and decision history stays attached to the stack. The next person opening the file inherits the full context instead of rebuilding it from scattered threads.

Can Air replace a full enterprise DAM for a lean creative team?

For most brands, retailers, and media teams producing high volumes of visual content, yes. Air combines asset management, AI-powered search, feedback and approvals, and built-in editing in one workspace. That covers what a lean team needs without the overhead of a heavy enterprise DAM.