A video or content production runs through phases that don't tolerate much slippage — pre-production planning, a shoot day that's expensive to reschedule, post-production with multiple review rounds, and a final delivery deadline the client is expecting. Each phase depends on the one before it actually finishing, and a delay in edit review has a very different cost than a delay in initial scripting. Production and asset management software handles the media files themselves well. What it doesn't handle is the coordination around getting from concept to delivered final cut.
Raw footage, edit files, and final assets belong in your media asset management or storage system, which is built specifically for that. Asana's role is coordinating the production process around those assets — scheduling, review rounds, approval status, delivery deadlines — linking to where the actual files live rather than storing them.
Mapping a project's sections to the actual production phases — pre-production, production, post-production, review, delivery — keeps the structure aligned with how the team and the client both naturally think about progress, with dependencies between phases ensuring editing genuinely can't begin until footage is actually delivered, not just assumed to be on its way.
A shoot day involves confirming crew, equipment, location, and often talent or client attendance, all needing to land correctly on one date that's expensive to reschedule. A checklist task for each shoot, with confirmation status tracked for every dependency, surfaces a missing confirmation while there's still time to resolve it rather than discovering it on the shoot day itself.
Post-production typically moves through several review rounds, and keeping track of which cut is with the client, what feedback came back, and whether it's been actioned is one of the more common sources of confusion in this work. A task representing each review round, with the client's feedback captured as a comment and linked to where the actual cut lives in your storage system, creates a clear, timestamped record of what was reviewed and what was requested — protecting against the "I thought we already fixed that" confusion that unstructured feedback threads tend to produce.
Like the event work covered in more depth in our events management guide, a delivery deadline is typically fixed and non-negotiable — a broadcast slot, a campaign launch date. Working backward from that date with a countdown timeline, covered in our Timeline and Gantt chart guide, and building in buffer for at least one more review round than you expect to need, protects against a tight post-production schedule collapsing entirely if one review runs long.
Production companies running several projects at different stages simultaneously benefit from the same portfolio structure used across other industries: one project per production, rolled up into a shared portfolio giving studio leadership a single view of which productions are in pre-production, which are shooting, and which are in review — without checking each timeline individually.
Clients generally want to see current status, pending reviews awaiting their feedback, and the delivery timeline — not internal crew scheduling or studio capacity planning. Scoped guest access to a project built with this separation in mind, the same principle covered in our professional services guide, supports that split cleanly without needing a separate client-facing system.
Media production has a specific rhythm — phase-dependent, deadline-fixed, review-heavy — that a generic project template doesn't account for. This is what we build into every production-focused implementation.
We build dependencies so editing genuinely can't start ahead of confirmed footage delivery.
We structure clear, timestamped feedback records so nothing gets lost between review rounds.
We scope guest access so clients see progress without exposure to internal studio operations.
Production work rarely fails because of the shoot itself — it fails in the gaps between phases, where a missing confirmation, an unclear review note, or a schedule with no buffer quietly threatens a fixed delivery date. Structured around real phase dependencies, tracked review rounds, and a countdown to delivery, Asana closes that gap without duplicating your media asset systems.
If your last delivery came down to the wire more than it should have, book a free consultation with SassyOS and we'll show you what a properly structured setup looks like.
Core Asana Services
Feature Guides
Related Industries
Reporting
We'll build your Asana workspace around real production dependencies, tracked review rounds, and a countdown to your delivery date.
Book a Free Consultation Get in Touch