Skip to main content
These project sections help organize existing tasks. Their availability and edit controls follow project permissions.

​
Intake

Intake lists incoming Inbox work. Search requests, expand an item, and review its description and priority.
  • Accept moves suitable work toward Ready.
  • Accept and start requests execution through the task lifecycle.
  • Decline archives the request.
Execution still requires the platform’s approval, assignment, and transition checks. If the requested transition is unavailable or rejected, review the task in Task Detail and follow the allowed sequence. Do not assume a visible start button bypasses prerequisites. Create a new incoming request with Add intake item.

​
Cycles

A cycle is a time-boxed work period.
  1. Choose Add cycle.
  2. Enter a name, goal or description, and start/end dates.
  3. Create it; the end date must not precede the start date.
  4. Link the work items planned for that period.
  5. Review progress and update the cycle’s available status controls.
Cycle statuses include Draft, Upcoming, Current, and Completed. Archive a finished or unused cycle when appropriate, and restore it from the archived listing when needed. Cycle planning does not automatically set every task to Ready or Done.

​
Modules

A module groups work toward a milestone or related outcome.
  1. Choose Add module.
  2. Enter its name and intended outcome.
  3. Create it and link relevant work items.
  4. Review the lead, available dates, progress, and status.
Module statuses include Backlog, Planned, In progress, Paused, Completed, and Cancelled. Archive and restore modules using their permitted controls. A module is an organizational grouping. Each linked task retains its own assignee, dependencies, lifecycle, and proof requirements.

​
Choose the right structure

Use a Project for a stable scope, a Cycle for a delivery period, a Module for a related milestone, a saved View for a reusable way to see work, and task dependencies for actual prerequisites.