[curt.clifton]

Another way to deal with "post mortem" items is to make the by-project-deadline items into an action group. For example:

- Attended conference  (set to sequential, no due date)
  - Prepared for conference (due by date of conference)
    - Tasks to get ready for conference...
    - ...
  - Submitted expenses for conference (start date after conference)
  - From employer, reimbursement for conference

All the tasks to get ready for the conference in my example will inherit the due date of their parent, but the expense related tasks won't have a due date. Prepared for conference could be a sequential or a parallel action group depending on the nature of the tasks inside it.

Nesting action groups and changing their parallel/sequential status is a powerful way to express dependencies between tasks.