Move a project to another phase

The project header carries a split button for phase changes. Its primary label names the next step — Ready for production, Ready for post-production or Ready for distribution — so advancing is one click. The caret next to it opens Move project to, listing every phase you can jump to.

When there is no obvious next step, the button simply reads Move phase.

Moving forward

Forward moves from this button happen immediately — there is no confirmation step, just a small confetti burst. The project lands on the first status of the phase you picked.

The handoff dialogs

Alongside the phase button, the header shows a Start Production, Start Post-Production or Start Distribution button when the project is at the right point to hand over. These take the same step but collect what the next team needs first:

• Start production — set the Shoot date, and optionally tick Update pre-production status.
• Start post-production — set a Deadline, Assign to editor and Notes for editor, with an Update production status tickbox. The confirm button reads Start editing.
• Start distribution — confirms the move into the distribution phase, ready to schedule and publish.

Cancelling a move leaves everything exactly as it was.

Moving backward

Backward targets are tagged in the menu and ask for confirmation first, under the heading Move project back? The dialog is explicit about what it does and does not touch: "Your deliverables keep their own status — nothing is reset. Any that are further along still show on the board." Use it when a project landed in the wrong phase — it is not a dead end.

Letting the work move the project

You usually do not need the control at all. Because phase is derived from status, moving your deliverables through the status ladder carries the project along. When every active deliverable reaches the last status of a phase, the app prompts you with "This phase is done — where should the project go next?" — accept it and the project advances.

What happens to the deliverables

A phase move advances the project. Nothing is bulk-moved and no work is destroyed — deliverables keep their own status in both directions, stay visible under the phase they are actually in, and show up on the new board in the Earlier phases group.

The move pins the project's status

Because the project is now ahead of its deliverables, moving it from the menu pins its status so the work does not immediately drag it back. The badge shows a lock icon.

That pin does not lift by itself. To hand control back to the deliverables, open the project's status badge and choose Auto (follow deliverables). Accepting the end-of-phase prompt is the exception — it advances the project without pinning it.

Switching the view without moving anything

The phase control also lets you look at an earlier phase's tabs — jumping back to the canvas or scripts while the project is in production, for example. Switching the view does not move the project. You can only look backward this way; phases the project has not reached yet stay locked.

Gotchas

• Completed projects are locked; the control collapses to a single Reopen button. Reopen first if you need to move the project.
• The project's URL contains its phase, so the address changes after a move. Old links still resolve to the project.
• Phase names follow your app language — a Dutch workspace sees Pre-productie, Productie and Post-productie.