A video production workflow you can see on the board

A stage that carries ownership, not just a name

Each stage has an owner, a dependency and the approval needed to leave it. Grade cannot start before the edit locks if you set that dependency. When something slips, what depended on it moves with it, and the board shows what moved.

A comment written on a stage stays on it. A watcher on the stage is updated when the status changes or a comment lands, without paging the whole studio.

A stage can carry an SLA in hours. A task entering it starts the clock. The state is ok until 80 percent of the window has passed, at risk from there to the deadline, and breached after. The Commercial and Corporate templates give the Edit stage 120 hours by default. A project can set its own value.

• Brief and schedule before the shoot opens.
• Edit, then internal review, before the client sees it.
• A door for approval, revisions, then delivery.

Labels that sort the queue

Mark a task as urgent, internal or waiting on the client. Board filters use the label, not a colour in a sheet. The same mark follows the work across views.

The queue stays readable when several productions are open, because the label sits on the task rather than on the side. A saved view can keep that filter, so Monday morning does not start by rebuilding it.

A label is not a status. Status is the stage. The label is how you find the urgent cut inside a stage that already has twelve items.

A template you start from, not an empty board

A new project opens from a template that matches the kind of work: commercial, brand film, documentary or social. The stages arrive with the owners the template gave, and you can edit them before the work runs.

A sprint on the project closes that week's work on the same board, without opening a second tool. A change to the template applies to new projects. A board that is already running stays as it is until you choose otherwise.

The Wedding film template makes the dependency concrete: its Ingest and backup stage has a task that must complete before the Highlights edit stage opens. You can add the same kind of wait to any project, not only to the templates that ship with it.

Internal review before the client sees it

The client should not be the first person to watch the cut. Internal review is a stage with an owner, not a hallway conversation. Notes from that pass stay on the version, and they can be carried to the next one.

A producer can see which version of the cut is current, how long it has been in the edit stage against its SLA, and which notes from the last review are still open, without asking the editor. Versions sit side by side. A note whose moment falls past the end of a shorter cut is flagged.

The edit itself stays in the editor's software. Tasked holds the versions, the notes, the time in stage and the decision that lets the cut leave.

Revisions counted on the same board

When a client asks for a change, a round opens on the same project, counted. After the agreed limit a billing mark appears. A project carries the number of rounds agreed: two by default, zero if nothing is included, up to fifty.

One round is one review of one version that came back asking for more work. A plain approval is not a round. The count is derived from the recorded decisions, not kept in a box someone has to remember to update.

Tasked does not charge the client for the extra round. The studio does, on its own invoice, with the board and the audit row to point at.

When something slips, what moves with it

A dependency is a rule the board enforces, not a note in a kickoff deck. If colour cannot start until the edit locks, a slip in the edit moves the colour start with it. The people on those stages see the new dates on the same board.

A watcher who joined a stage hears the status change. A watcher who joined only one task is not copied onto the rest. That is how a studio of twenty open productions stays quiet except where it should not.

Delivery is a stage with an owner too. The approved master, the approval record and the notes on it stay on the project. A deleted file's bytes are kept for 30 days, which is the window a client usually asks for a re-export.