Work Item Types
Work Item Types defines the types tracked work can take, under Types, Fields, and Defaults tabs. The Types tab lists each type with its key: Program (program), Project (project), Deliverable (deliverable), Task (task), Plan Brief (plan_brief, off), and Deliverable Brief (deliverable_brief, off). Search filters the list; New creates a type.
Types on means sessions can attach that kind of work item; off means the type exists but is unavailable. Change fields and defaults only when the owning process changed, since sessions in flight reference them.
- Types tab lists each work item type with its key and on/off state.
- Fields tab defines per-type fields; Defaults tab defines per-type defaults.
- Program, Project, Deliverable, and Task ship on; Plan Brief and Deliverable Brief ship off by default.

The model behind the types
Section titled “The model behind the types”The four on-types are the work-item hierarchy: program to project to deliverable to task. Types on means sessions can attach that kind of work item from the Starting a session composer; off means the type exists but stays unavailable. Turning a brief type on makes it attachable everywhere at once, so the decision belongs to whoever owns the process, not to whoever wants it today.
- Fields tab defines per-type fields; reusable definitions live under Custom Fields. Reference fields between types are assigned from each type’s Relationships tab.
- Defaults tab defines what new rows start with. Defaults that match how the team actually works get accepted silently; defaults that fight it get overridden on every row, which is a signal the default is wrong.
- Statuses behind these types run inside Settings Workflows — a row moves only when the work actually moved.
- Repeatable shapes built from these types live under Templates; the lists themselves live at
/items/{typeKey}, documented on the Work items hub.
What next
Section titled “What next”-
Work items: the hub — hierarchy, lists, customization, workflows, approvals, sessions.
-
Workflows: the workflows that govern these types.
-
Starting a session: where the composer attaches a work item to a session.

