Task Status Updates

ftrack tasks move through statuses such as ready, in progress, and approved as work passes across a project. A Beam agent watches for a status change, for example when a reviewer marks a shot approved, and applies the account's rule for what happens next: updating a linked task in another system, notifying the artist assigned to the following step, or closing a dependent task. Cases where the rule does not clearly apply, such as a rejected note with no obvious next task, are routed to a human coordinator to decide before anything moves forward.

Review Session Notes

Review sessions in ftrack hold the notes and annotations reviewers leave on a version during a screening. A Beam agent reads new notes as they post, applies the approved rule for routing, for example forwarding a note tagged for revision to the artist and opening a follow up task, or marking a note resolved once the artist responds. Notes that are ambiguous, conflict with an earlier note, or come from a reviewer outside the approved list are routed to a human coordinator to interpret before any downstream task changes.

Project and Shot Structure

ftrack organizes work by project, sequence, and shot, with tasks nested under each one. A Beam agent reads this structure to find which shots or tasks match a customer-approved condition, such as a shot entering a specific pipeline stage, then updates the related task status or notifies the assigned artist and coordinator. The same structure lets the agent apply one rule across dozens of shots instead of a coordinator checking each one. When a shot carries no assigned task, an unclear pipeline stage, or conflicting schedule entries, the agent leaves the record untouched and routes the case to a human to sort out.