Generic project management software is very good at recording that a review happened. It is structurally incapable of holding what the review was about, and that gap is where creative teams lose their afternoons.
A ticket is the wrong shape
A ticket has a title, a state and a comment thread. A creative review has a frame, a timecode, a region of an image, a version, and five notes that each apply to a different one of those. Flattening it into a thread loses the anchoring, and anchoring is the entire value.
What gets lost in the flattening
“This is too dark” is actionable on a frame and useless on a ticket.
Once the note is detached from the frame it described, resolving it requires a conversation to reconstruct what it meant. Multiply by the number of notes in a round and you have rebuilt the meeting the review was meant to replace.
What to look for instead
Notes that attach to a version and stay attached. A visible state per note rather than per round. And a history that survives the asset being superseded — because the most useful question in a late production is what we already decided about this and why.
