Tracker · Delivery workspace
Clear plans. Visible progress.
Track flow delivery, assign tasks, and run published workflows. Keep the work connected to the spec.
Plan and usage limits apply. View pricing
Product walkthrough
Tracker, in context.
Demo project data shown for illustration.
Screen 01 / 03
Flow delivery pulse
Tracker follows delivery across the approved flows and phases
A closer look
The details,
when you need them.
Explore the workflow, what it produces, and how access works.
How Tracker works
Tracker follows revision-aware flow delivery across epics and phases. Use Work for native tasks and saved list or board views, and start workflow runs from a published flow. Every task can link back to the behavior it delivers.
- Start in Flows to filter delivery by phase, update flow or step progress, and read the recalculated pulse across epics.
- Create numbered tasks manually, from a template, from a flow, or from reviewed extraction proposals, then arrange them in saved List or Board views and scoped task lists with their own audience and chat channel.
- Start a run of a published flow: each human step becomes a task when the run reaches it, software steps wait for signed webhook results, and the run history records every path chosen.
A practical example
A delivery lead wants one place to turn an approved flow into owned work, see what is in flight, hand people the steps a running process reaches, and read how logged time compares with the estimate.
What you get
An operational plan tied to the spec
- A phase-aware delivery pulse that preserves partial work inside multi-step flows
- Tasks with custom statuses, labels, assignees, estimates, reminders, dependencies, and linked flows, plus runs with a step-by-step history
- Time analysis per list that compares logged hours with task estimates and workflow step budgets
Using Tracker
Flow progress, tasks, and runs persist independently of revision publishing. People with read access can inspect the workspace; creating or updating work requires project write access, and a stopped run keeps its history but cannot be resumed.
Keep exploring