Stages are the rows of a Task Collection Template. They group the template's tasks into phases so a long workflow reads as a sequence rather than a flat list: Before the Job, Job Day, Processing, After Posting.

Working with stages

• New Stage adds a row. Click the stage name to rename it.
• Add Task on a stage creates a task in that row.
• Drag a task within a stage to reorder it, or to another stage to move it.
• Stages are ordered top to bottom; the order becomes the collection's default sequence.

What stages affect

• The Collection Stage column and Task Stage filter on the Tasks list, so a manager can see everything in Processing across all jobs.
• The Sequence graph of a collection, which starts laid out by stage.
• Cross-task notification rules that refer to the first, next, or previous task follow the stage order.

Stages have no dates or assignees of their own; they are purely organizational.

<aside> 💡

Name stages by when the work happens, not who does it. Assignment is handled per task, and a stage named Lab stops making sense the first time a non-lab task lands in it.

</aside>

Screenshot

Create different stages for your Task Collection Templates (Like “Pre Job” and “Processing” and “After Posting”. This allows you to split out tasks into a more organized and manageable flow. Click on the New Stage link, name the stage and start adding tasks: