Docs Projects (Process Runs)

Projects (Process Runs)

A Project is a live run of a blueprint (or a one-off launched from the Sandbox, a form, or a ticket). It's where work actually happens.

How it works

Tasks appear in their stages with status (To do → In progress → Done), assignee, and any proof requirements.
Completing a task may require proof; everything (proof, comments, overrides) is captured as a completion attempt in the history.
Task-level permissions: you can only complete tasks assigned to you, your department, or someone of equal/lower rank. Higher-ranked managers can act on others' tasks.
Dependencies enforce order; blocked tasks require a reason and notify oversight.
Run status rolls up automatically. When the run completes, any configured follow-on blueprints launch.
Completing a step that has a sub-workflow launches it and notifies the people it routes to.

Launch a run from a published blueprint (Blueprints → Start, or Sandbox → Quick-launch), a form submission, or a ticket.
Assign or reassign tasks, set due dates and priority.
Track progress; watchers get notified of key events.
Review completion notes, files, and the full attempt history on each task.

List, Board, and Stage views for day-to-day tracking.
Timeline — a lightweight Gantt that plots every run from its start date to its due date, with a "today" marker, progress fill, and overdue runs highlighted. Click any bar to open the run.