Project Management App Starter · Industry version
Creative Project Management Template
A tracker that thinks in deliverables and review rounds, not just tasks — generated into code your studio owns.
Creative work doesn't finish, it converges: version three of the hero film, round two of feedback, final_FINAL_v2 retired at last. This starter makes deliverables and review rounds first-class in the schema, so the tracker matches how a studio actually moves work toward approved.
- 6 core entities
- Kanban + list views
- Code you own
- Vibe + Governed modes
01 · The problem
Why a generic Project Management falls short
In a studio, the unit of delivery is not a task — it's an asset with versions. The thirty-second cut, the key visual, the six banner resizes: each exists as v1, v2, v3, each version drew feedback, and someone must know which version is current. A tracker with a single done checkbox per task is blind to the entire middle of creative work, which is where all the time goes.
Feedback arrives as rounds, not comments. Round one brings fourteen notes from five reviewers, half contradictory; someone consolidates, the team revises, round two brings six more. Generic tools scatter this across comment threads and email, so 'whose note won' is archaeology and round creep is invisible until the budget's gone.
And creative work ships in campaigns: one concept fanning out into film, stills, social crops, and a landing page, all against a launch date. Flat project lists can't show that the campaign is green except for the one asset that blocks the whole launch.
02 · Data model
The data model, adapted
Everything in the base Project Management starter —
projectsboardstaskssprintscommentslabels— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
deliverables | The assets being made — format, spec, current version, and approval state — the real unit of studio delivery. |
review_rounds | Numbered feedback cycles per deliverable, holding consolidated notes and the version they apply to. |
03 · Screens
Modules through the industry lens
Boards by deliverable stage
01Columns follow creative reality — brief, concept, in-progress, in-review, revisions, approved — and cards are deliverables carrying their version number and round count. A glance shows what's stuck in review versus what's actually still being made.
Round-aware planning
02Timeboxes plan around review cycles: two rounds budgeted per deliverable, with client review windows on the calendar. When round three opens, it's visibly beyond plan — which is the moment to invoke the revision clause, not discover it in the post-mortem.
Campaign burnup
03Progress charts roll deliverables up by campaign: approved versus total, review latency per reviewer, rounds per asset. The producer sees the launch at risk from the film's third round while the banners sit approved — a week before the deadline argues about it.
04 · In practice
Workflows it models
Brief to first presentation
01The campaign opens with its deliverable list — film, KV, five resizes, landing page — each with spec and due date. Concepts attach as versions, the internal round runs first, and the client sees round one only after the creative director's pass.
Round two, consolidated
02Client feedback lands in the round record, the producer merges contradictions into one actionable set, and the note that got overruled stays documented. Revisions post as version three against those notes — nothing lives in a reply-all thread.
Final delivery, without the folder hunt
03Approval flips the deliverable to final, locks the version, and the campaign's delivery view lists every approved asset at its current version. Handoff to media or the client is a link to the record, not a zip named FINAL_final.
Creative Project Management template — frequently asked questions
Does it store the actual creative files?
Versions carry files or links to your storage and pipeline tools — the tracker owns the state (which version, which round, approved or not) while heavyweight assets live where your studio already keeps them. Deeper integration is possible because the schema is yours.
How do client review rounds work?
Each round is a record: the version under review, the reviewers, their notes, and the consolidated direction the team acts on. Clients can be given review-only access, and rounds-per-deliverable becomes a reportable number — useful in the next contract negotiation.
Can it handle retainer clients and one-off campaigns together?
Yes — projects can be ongoing (monthly content retainers) or dated (a launch campaign), with boards configured per shape. Reporting rolls both up, so studio capacity is one picture rather than two systems.
What about freelancers on a single project?
Access scopes to a project or even a set of deliverables, so a freelance editor sees their cut and its rounds — not the client list. Since there are no seat fees, short-term collaborators cost nothing to add and nothing to forget to remove.
Related
Dual7 App Starters
Build your Creative Project Management on your terms
A tracker that thinks in deliverables and review rounds, not just tasks — generated into code your studio owns. Describe your version to start — the output is a project you own.