Deliverable Tracker gives post producers a purpose-built, shareable way to organize edits, cutdowns, crops, versions, formats, and the relationships between them.
Interactive example of a nested Deliverable Tracker campaign matrix.
Built for
The people responsible for this part of the work.
Built first for post producers, with clear views and exports for agency producers, post supervisors, editors, vendors, clients, and creative operations teams.
The current workflow
A flat sheet can list the files. It cannot show how the work branches.
Commercial deliverables rarely arrive as one tidy list. Main edits become cutdowns; cutdowns become crops; crops become formats, language versions, and masters. The matrix keeps changing while bids, schedules, staffing, and client expectations depend on it.
Why purpose-built
The hierarchy is the point.
Tracker models parent-and-child relationships directly. Collapse the project to discuss the major creative outputs, expand it to account for every file, and move the same information into the spreadsheet, message, deck, or folder structure the next person already uses.
What it helps you do
A focused system for the actual task.
01
Build the tree your project needs
Add, duplicate, rename, reorder, and nest deliverables without forcing every campaign into one template. Add notes and color when they help your team read the work.
02
Change the view, not the underlying plan
Collapse the tree to its top level, open every individual output, or stop anywhere between. Show the amount of detail appropriate to the conversation.
03
Communicate outside the tool
Create a password-protected read-only view or export portable text, CSV, a structured Google Sheet, and an empty hierarchical folder tree as a ZIP.
04
Keep scope changes legible
Save named snapshots as the deliverables evolve. If useful, paste a client brief or message into the opt-in AI intake and review its suggested structure yourself.
After your first session
Leave with something useful.
Turn a rough brief into a deliverables tree your team can understand, then copy, export, or share the version that belongs in the next conversation.
Tracker defines and communicates expected deliverables; it does not create, review, schedule, or deliver the media itself.
Shared collaborators can update the same project, but editing is not simultaneous cursor-level or live-multiplayer collaboration.
AI intake is optional and produces suggestions for a producer to review, not an authoritative interpretation of the brief.
Google Sheets export is built in. Google Slides is not a direct integration; the text export can be pasted into a presentation.
Questions, answered
The practical details before you begin.
What is a deliverables matrix?
It is the working definition of every edit, cutdown, crop, version, format, localization, and master a project must produce. Tracker represents those outputs as a collapsible hierarchy instead of only a flat set of rows.
Why not keep using a spreadsheet?
Spreadsheets remain useful for handoff, which is why Tracker exports to them. Tracker is built for defining the relationships first: it can show both the major creative branches and every resulting file without maintaining separate versions of the plan.
Can clients and collaborators see the tracker?
Yes. You can create an interactive read-only view, optionally protect it with a password, or invite collaborators to the project. Collaborative editing is shared, but not currently live multiplayer.
What can I take out of the tool?
You can export text, CSV, a structured Google Sheet, or an empty folder hierarchy as a ZIP. You can also share the collapsible browser view and save named snapshots of the project over time.