Asana Structure
The rule — Each client is one Asana project. Initiatives are parent tasks; work items are their subtasks. The structure must match exactly or the app won't render the client.
Required project sections
Initiative sections: Active Initiatives, Future Initiatives, Completed.
Task sections: Active Tasks, Future Tasks, Completed.
A task sitting in a task-section with no parent initiative is flagged as an "orphan" — fix it by making it a subtask of the right initiative.
The three custom fields the app reads
| Field | Type | Drives |
|---|---|---|
| Status | dropdown | The stage strip, highlights, callouts (see Status Definitions) |
| Hours | number | Hours logged; rolls into reports |
| Review Link | text | The review-tool URL (set automatically) |
Decision pending — Two items from today's meeting are not yet settled, so they're left out of the canonical structure: (1) where the old deck's "Reference" section and
[Month] Process/[Month] Updatestasks live now (this affects where monthly time gets logged), and (2) whether the "Work Type" field (Initiative/Update/Revision) is kept as an operational field even though the app doesn't read it. Resolve these, then this page gets updated.