On a team, the expensive question is "is this asset final?" The approval workflow answers it by giving every asset a clear status - and keeping that status next to the asset, not in a separate spreadsheet.
The states
Each asset moves through a simple, legible pipeline:
- WIP - work in progress, not ready to rely on.
- Review - ready for a lead or peer to check.
- Approved - signed off and final.
- In Use - live in the project and depended on.
Why status belongs with the asset
When approval lives in a chat thread or a separate board, it drifts out of sync with the actual files. Keeping WIP → Review → Approved → In Use attached to the asset in the same dashboard where you scan and validate means status and reality stay together. A producer can see at a glance what is safe to build on before a milestone.
For teams of any size
You do not need a heavyweight production tracker to get this value. The workflow is deliberately light, aimed at solo devs and studios who want clarity without ceremony. Combine it with the Blueprint manager so Blueprint status is visible, and export a report of approvals for a milestone.
Frequently asked questions
What are the approval states?
WIP, Review, Approved and In Use. Each asset moves through them so the team always knows what is final and what still needs work.
Does it replace our project management tool?
No. It is a lightweight status layer attached to your assets, not a full tracker. It complements tools like Jira or Perforce rather than replacing them.