Autodesk kept ShotGrid's engine and changed only its name

The shot

In 2024, Autodesk began describing its production-tracking software as “Flow Production Tracking (formerly ShotGrid),” retiring the ShotGrid name across its product overview while keeping the underlying tool in place. Autodesk's own product page calls the software “an advanced production management and review tool for managing resources, tracking assets, and keeping people connected at every stage of production,” repeating “formerly ShotGrid” rather than describing a new release. By April 2024, an Autodesk-published case study about Jellyfish Pictures already used only the new name.

What the documents show

Autodesk's documentation draws a line between the rename and any feature change: the overview page's FAQ pairs “formerly ShotGrid” with continuity language about accounts and installation terms. The one feature Autodesk names as new is Flow Generative Scheduling, described on the same page, as the vendor's own claim, as software that “analyzes multiple scheduling scenarios, weighs trade-offs, and produces resource-optimized, balanced schedules in minutes.” No independent benchmark appears in the document. A second Autodesk piece, an account of the VFX pipeline behind ‘Challengers’, names Zero VFX and roughly 900 VFX shots, stating the studio used the renamed tool, with Maya, to track a previs sequence before the shoot — Autodesk's own case material, not an independent audit, but a named production rather than a demonstration reel.

The workflow

For a studio on ShotGrid already, the documented change is administrative: login, data and subscription tier persist under the new name, per Autodesk's own support text. Coordinators gain an optional scheduling layer that, by Autodesk's description, proposes scenarios rather than final assignments — a producer still weighs those against crew availability, union rules and client deadlines the software is not described as analyzing. The Zero VFX material frames the tool's role as pre-shoot planning, upstream of any shot generation, keeping it inside this site's workflow lane rather than the generation tools it schedules around.

What the tool does not change

A product rename, on its own, is not evidence of a technological leap, and Autodesk's materials do not claim one for the underlying tracker. The scheduling feature is documented as a scenario generator; deciding which scenario to run, and absorbing the human costs of a schedule change, remains a producer's job the cited pages do not describe as automated. This is an editorial distinction worth holding onto whenever a familiar tool reappears under a new name.

• Does a vendor's own documentation describe continuity of data and terms across a rename, or does it read like a new product launch?
• When a scheduling or tracking tool claims an AI feature, does the vendor's text describe it generating options for a human to choose, or making the choice itself?
• Does a vendor case study name the production, the studio and the specific pipeline stage involved, rather than offering only a general endorsement?

Naming changes travel faster than technical ones, and Autodesk's pages here describe the former without claiming the latter. Reading the documentation for what persisted — account terms, data, workflow structure — separates a rebrand from a rebuild, which matters for any production deciding whether the announcement is news at all.