Skip to content

Tag Hierarchy

Parent-child relationships between tags for better organization.

Definition

Tag Hierarchy allows you to create parent-child relationships between Tags, organizing them into a tree structure for better categorization and filtering.

Structure

Parent-Child Relationships

💼 Work Related (Parent)
├── 📊 Project Management (Child)
├── 👥 Team Meetings (Child)
└── 📚 Training (Child)

🎯 Personal Development (Parent)
├── 📖 Reading (Child)
├── 🎓 Online Courses (Child)
└── ✍️ Writing (Child)

Multiple Levels

You can nest tags multiple levels deep:

💼 Work
├── 📊 Projects
│   ├── Client A
│   └── Client B
└── 👥 Meetings
    ├── Team Standup
    └── Client Calls

Recommended depth: 2-3 levels maximum

Creating Tag Hierarchies

Set Parent Tag

  1. Create or edit a tag
  2. Tap Parent Tag field
  3. Select the parent tag
  4. Save

Example:

  • Create "Project Management" tag
  • Set parent to "Work Related"
  • Result: Work Related → Project Management

Build Hierarchy

  1. Create parent tags first
  2. Create child tags
  3. Assign parent relationships
  4. Organize logically

How Hierarchies Work

Inheritance

Child tags inherit context from parents:

Example:

  • Tag: "Team Meetings"
  • Parent: "Work Related"
  • Context: Work + Meetings

Filtering

When filtering by parent tag:

  • Shows tasks with parent tag
  • Shows tasks with any child tag
  • Inclusive filtering

Example: Filter by "Work Related":

  • Shows tasks tagged "Work Related"
  • Shows tasks tagged "Project Management"
  • Shows tasks tagged "Team Meetings"

Display

Tags show hierarchy in lists:

💼 Work Related
  📊 Project Management
  👥 Team Meetings
  📚 Training

Indentation shows relationships.

Common Hierarchy Patterns

By Life Area

💼 Work
├── Projects
├── Meetings
└── Admin

🏠 Personal
├── Home
├── Family
└── Health

🎓 Learning
├── Reading
├── Courses
└── Practice

By Context Type

📍 Location
├── Office
├── Home
└── Travel

⚡ Energy
├── High
├── Medium
└── Low

👥 People
├── Solo
├── Team
└── Client

By Project Phase

🚀 Product Launch
├── Planning
├── Development
├── Testing
└── Marketing

By Tool/Resource

💻 Digital
├── Computer
├── Phone
└── Tablet

📝 Physical
├── Office
├── Paper
└── Equipment

Using Hierarchies Effectively

Broad to Specific

Organize from general to specific:

  • ✅ Work → Projects → Client A
  • ✅ Personal → Home → Kitchen
  • ❌ Random nesting without logic

Consistent Structure

Use similar patterns across hierarchies:

Work
├── Type A
├── Type B
└── Type C

Personal
├── Type A
├── Type B
└── Type C

Meaningful Relationships

Parent-child should make sense:

  • ✅ Work → Meetings (logical)
  • ✅ Learning → Reading (logical)
  • ❌ Office → High Energy (unrelated)

Hierarchies in Perspectives

Filter by Parent

Create Perspective filtering by parent tag:

"All Work Tasks":

  • Filter: Has tag "Work Related"
  • Result: Shows all work tags (parent + children)

Filter by Child

Or filter by specific child:

"Project Management Only":

  • Filter: Has tag "Project Management"
  • Result: Shows only this specific tag

Combine Filters

Mix parent and child filters:

"Work Projects at Office":

  • Filter: "Work Related" (parent) + "Office" (location)
  • Result: Work tasks doable at office

Hierarchies vs Groups

Tag HierarchyTag Group
Parent-child structureFlat collection
Shows relationshipsControls selection
Nested organizationSelection rules
InheritanceNo inheritance

Use both: Hierarchy for organization, groups for selection control.

Best Practices

Keep It Shallow

  • 2-3 levels maximum
  • Deeper = harder to navigate
  • Simple is better

Logical Grouping

  • Related tags together
  • Clear relationships
  • Intuitive structure

Don't Over-Organize

  • Not every tag needs a parent
  • Some tags work standalone
  • Add hierarchy when it helps

Review Regularly

Monthly check:

  • [ ] Are hierarchies still useful?
  • [ ] Any to simplify?
  • [ ] Any to reorganize?

Use for Big Systems

Hierarchies shine when you have:

  • 20+ tags
  • Multiple life areas
  • Complex workflows

Managing Hierarchies

Moving Tags

Change parent relationship:

  1. Edit child tag
  2. Select new parent
  3. Save

Tag moves to new hierarchy.

Removing from Hierarchy

Make tag standalone:

  1. Edit tag
  2. Select "No Parent"
  3. Save

Tag becomes top-level.

Reorganizing

Restructure hierarchies:

  1. Plan new structure
  2. Update parent tags
  3. Move child tags
  4. Test in perspectives

Example Setups

Simple (2 Levels)

Work
├── Projects
├── Meetings
└── Admin

Personal
├── Home
├── Health
└── Learning

Detailed (3 Levels)

Work
├── Client Work
│   ├── Client A
│   └── Client B
├── Internal
│   ├── Team Projects
│   └── Admin
└── Development
    ├── Training
    └── Research

Context-Based

Location
├── Office
│   ├── Desk
│   └── Meeting Room
├── Home
│   ├── Office
│   └── Anywhere
└── Outside
    ├── Errands
    └── Travel