If a project is huge and typical TRO project support can’t handle it, you have options. Use one of these methods—in addition—just for your biggest projects. (Look for orphan protection, or compensate in your weekly reviews.)

  • Dedicated Project Field. A project name field keeps track of the project.
    • Unlimited tasks per project. Use Someday/Maybe to “pause” future next steps if that feature is not provided.
    • Orphan protection may not be available unless the tool is TRO-aware.
    • Projects list should be built-in.
  • Named Folders or Lists. Use named folders or lists for projects. You cannot use this unless tasks appear in all TRO task views, regardless of their folder or list. Also, the folder or list name should be visible in any grid views, so you can tell which project it belongs to.
    • Unlimited tasks per project. Use Someday/Maybe to “pause” future next steps.
    • Orphan protection is probably not an option, so your weekly reviews will be longer.
    • Projects list is the list of folder/list names.
  • Special Tags or Categories. Use specially-named tags or categories to track which project a task belongs to. The tag or category is the project name, starting with a unique special character like “=”, “#”, or “!”, like this: =Remodel, =Pilots License, =Pick a Grad School.
    • Unlimited tasks per project. Use Someday/Maybe to “pause” future next steps.
    • Orphan protection may be possible if complex custom task views are supported.
    • Projects list is your master contexts list (or equivalent).
  • Subtasks. A main task record allows subtasks. You use the main record as the project and the subtasks as next actions. CAUTION: This only works properly if 1) the main task record somehow appears with each subtask in any grid view, and 2) unprocessed subtasks appear in the Unprocessed Tasks list and not in your regular lists.
    • Unlimited tasks per project. Use Someday/Maybe to “pause” future next steps if that feature is not provided.
    • Orphan protection may not be available unless the tool is TRO-aware.
    • Projects list is the view that shows all your main tasks.
  • Hierarchical. Like subtasks, but with multiple levels, so any task or project can belong to a parent project.
    • Unlimited tasks per project. Use Someday/Maybe to “pause” future next steps if that feature is not provided.
    • Orphan protection is probably not available unless the tool is TRO-specific.
    • Projects list should be built-in.
  • Multi-Hierarchical. Any task or project can belong to any number of other projects. Very flexible for complicated work environments.
    • Unlimited tasks per project. Use Someday/Maybe to “pause” future next steps if that feature is not provided.
    • Orphan protection is probably not available unless the tool is TRO-specific.
    • Projects list should be built-in.