Why Tags Matter in Task Management
Projects and folders give your tasks a home. Tags give them dimensions. A task lives in one project, but it can have multiple tags that describe its context, energy requirement, type, and status. This multi-dimensional organization is what makes tags powerful and, when misused, what makes them overwhelming.
Consider a task like "Write the Q3 marketing proposal." It belongs to the Marketing project. But it is also a writing task, it requires deep focus, it involves the client Acme Corp, and it is blocked until you receive the budget numbers. A project folder captures one of these dimensions. Tags capture all of them.
The value of tags becomes apparent when you need to answer questions that projects alone cannot:
- What can I work on right now that requires low energy?
- What tasks am I waiting on from other people?
- What deep-focus work do I have queued up for tomorrow morning?
- Which tasks involve client communications?
These are the kinds of questions that drive effective daily planning. Tags make them answerable.
Flat vs. Hierarchical Tag Systems
Flat Tags
Flat tags are simple labels with no parent-child relationships. Every tag exists at the same level.
Examples: writing, deep-focus, client, waiting, quick-win
Advantages:
- Simple to create and apply
- Easy to understand
- Fast to search and filter
- Low overhead
Disadvantages:
- Can become unwieldy at scale (50+ tags)
- No built-in organization
- Prone to redundancy ("meeting" vs "meetings" vs "call")
Hierarchical Tags
Hierarchical tags use prefixes or nesting to create structure.
Examples: context/office, context/home, energy/high, energy/low, type/writing, type/admin
Advantages:
- Organized and scalable
- Clear categorization
- Easier to browse and discover
- Reduced redundancy
Disadvantages:
- More complex to set up
- Requires discipline to maintain consistency
- Some tools do not support true hierarchies
Recommendation
Start with flat tags if you have fewer than 15 tags. Move to hierarchical if you consistently use more than 15. The structure of hierarchical tags prevents the chaos that flat tags create at scale.
Essential Tag Categories
Context Tags (Where/When)
Context tags, inspired by David Allen's GTD methodology, describe where or with what resources a task can be done:
| Tag | Meaning | Example Tasks |
|---|---|---|
| @computer | Requires a laptop/desktop | Code review, document drafting |
| @phone | Can be done from phone | Quick messages, approvals |
| @office | Requires being in the office | In-person meetings, equipment access |
| @home | Best done at home | Personal tasks, focused writing |
| @errands | Requires going somewhere | Post office, store runs |
| @anywhere | Location-independent | Reading, thinking, planning |
Context tags are most valuable when your work context changes throughout the day. If you work from home at a desk all day, context tags add little value. If you split time between office, home, and travel, they are transformative.
Energy Tags (How Much Effort)
Energy tags describe the cognitive demand of a task:
| Tag | Meaning | When to Schedule |
|---|---|---|
| high-energy | Requires deep focus and creativity | Peak energy hours |
| medium-energy | Moderate cognitive demand | Mid-day |
| low-energy | Routine or mechanical work | Low energy hours, afternoons |
Energy tags enable energy-matched scheduling. Instead of forcing yourself to do creative work when you are exhausted, you can filter for low-energy tasks and save the demanding work for when you are sharp.
This pairs naturally with daily capacity planning. When you build your daily plan, selecting tasks that match your energy curve produces a more realistic and sustainable schedule.
Status Tags (What State)
Status tags track the current state of a task:
| Tag | Meaning |
|---|---|
| waiting | Blocked on someone else |
| in-progress | Currently being worked on |
| blocked | Cannot proceed due to a dependency |
| needs-review | Completed but needs someone's review |
| someday | Interesting but not committed |
Some task managers have built-in status fields, making these tags redundant. Use tags only when the built-in fields do not cover the states you need.
Type Tags (What Kind of Work)
| Tag | Meaning |
|---|---|
| writing | Content creation, documentation |
| coding | Software development |
| design | Visual or UX design work |
| admin | Administrative and operational tasks |
| communication | Emails, messages, calls |
| research | Investigation and learning |
| planning | Strategy and planning activities |
Type tags are useful for time analysis. At the end of a week, you can see how your time distributed across types of work and decide whether the allocation matches your priorities.
People Tags
Tag tasks with the people involved:
@sarahfor tasks that involve or are delegated to Sarah@client-acmefor tasks related to a specific client@team-marketingfor tasks involving the marketing team
People tags make preparation for one-on-ones and meetings easy. Filter by @sarah before your one-on-one and you have a ready-made agenda of shared tasks and items to discuss.
Building Your Tag System
Start Minimal
The biggest mistake with tags is creating too many too soon. Start with 5 to 8 tags that address your most common filtering needs. Add new tags only when you encounter a recurring need that existing tags do not serve.
Document Your Tags
Create a simple reference document listing each tag, its meaning, and when to use it. This prevents drift and inconsistency, especially on teams. The document does not need to be elaborate. A table with three columns (tag, meaning, examples) is sufficient.
Enforce Consistency
Decide on naming conventions and stick to them:
- Singular or plural? Pick one. ("meeting" not "meetings")
- Lowercase or capitalized? Pick one. ("deep-focus" not "Deep Focus")
- Hyphens or spaces? Pick one. ("high-energy" not "high energy")
- Abbreviations? Avoid them. ("communication" not "comm")
Prune Regularly
Every month, review your tag list. Remove tags you have not used in the past 30 days. Merge tags that overlap. The goal is a lean, useful tag system, not a comprehensive taxonomy.
Tags in Practice: Filtering and Views
Tags create value through filtering. The most useful filter combinations:
The "What Can I Do Right Now" Filter
Context: current location + Energy: current level
Example: @computer + low-energy shows all computer tasks that do not require deep focus. Perfect for that 3 PM slump.
The "Meeting Prep" Filter
Person: the person you are meeting with + Status: not completed
Example: @sarah + open tasks shows everything you need to discuss with Sarah.
The "Deep Work Session" Filter
Energy: high + Type: your primary work type
Example: high-energy + coding shows all demanding development tasks. Pick one and enter a focus session.
The "Quick Wins" Filter
Estimated time: under 15 minutes + Status: not blocked
This does not always require tags. Some tools let you filter by estimated duration directly. If yours does not, a quick-win tag serves the same purpose.
Tags on Teams
When multiple people share a task management system, tag consistency becomes critical. Without governance, everyone creates their own tags, leading to a cluttered, unusable system.
Team Tag Governance
- Designate a tag owner: One person (or rotating role) who approves new tags
- Publish the tag dictionary: Shared document listing all approved tags with definitions
- Review quarterly: Remove unused tags, merge duplicates, add new ones as needed
- Limit personal tags: Allow a small number of personal tags but require team tags for shared work
In SettlTM's team workspaces, tags are available across the organization, so team members can filter shared projects using the same tag vocabulary.
Common Tagging Mistakes
Too Many Tags
If you have more than 20 active tags, you almost certainly have redundancy and tags that are not pulling their weight. More tags means more decisions when creating tasks and more noise when filtering.
Tags That Duplicate Other Fields
Do not create a high-priority tag if your task manager has a priority field. Do not create a due-this-week tag if you can filter by due date. Tags should add information that other fields do not capture.
Inconsistent Application
A tag system only works if you apply tags consistently. If half your tasks are tagged and half are not, filtering produces incomplete results, which erodes trust in the system. Either tag everything or use tags selectively for a specific purpose.
Tags as Projects
If you are using tags to group tasks that belong together and have a shared goal, you probably need a project instead. Tags describe attributes of tasks. Projects describe collections of tasks that produce an outcome.
Advanced Tagging Patterns
The Time-of-Day Tag
Some tasks are best done at specific times regardless of project or priority. Tag tasks with time-of-day markers when relevant:
morning-routine: Tasks for the first 30 minutes of the dayend-of-day: Tasks for the last 30 minutes before shutdownafter-lunch: Low-cognitive tasks for the post-lunch slumpdeep-afternoon: Demanding tasks for the afternoon peak
These tags complement energy tags by adding temporal specificity. While a high-energy tag tells you the task needs your best hours, an after-lunch tag tells you exactly which slot it fits.
The Outcome Tag
Most tags describe the nature of the task. Outcome tags describe what completing the task produces:
revenue: Tasks that directly contribute to revenuecost-savings: Tasks that reduce expensesrisk-reduction: Tasks that mitigate business or personal riskrelationship: Tasks that build or maintain important relationshipslearning: Tasks that develop skills or knowledge
Outcome tags help you evaluate your work allocation at a higher level. At the end of a month, if 80 percent of your completed tasks are tagged admin and only 5 percent are tagged revenue, that distribution tells an important story about how you are spending your time versus how you should be spending it.
Seasonal Tags
Some tags are only relevant during certain periods. Examples include q4-close for year-end tasks, tax-season for tax preparation, launch-sprint for product launches, and conference-prep for pre-conference work. Create these tags when the season begins and archive them when it ends. This prevents tag bloat from accumulating temporary tags over time.
Tag Analytics and Insights
If your task manager supports analytics or if you export your data periodically, tag-based analysis reveals powerful insights about your work patterns:
Time Distribution by Tag
How much time do you spend on writing versus meetings versus admin versus coding? This distribution shows whether your time allocation matches your priorities. If you were hired for your coding skills but spend 60 percent of your time in meetings and admin, something needs to change.
Completion Rate by Tag
Which types of tasks do you consistently complete, and which do you consistently defer? If writing tasks have a 90 percent completion rate but research tasks have a 40 percent rate, you may need to break research tasks into smaller pieces or block dedicated research time.
Priority Accuracy by Tag
Do certain types of tasks get systematically over-prioritized or under-prioritized? If your admin tasks are frequently marked high priority but rarely have meaningful deadlines, you may be inflating their importance at the expense of genuinely important work. These analytics require consistent tagging over time, which is another reason to keep your tag system simple and sustainable. A complex system that you abandon after two weeks provides no data. A simple system you maintain for six months provides actionable insights.
The Tag Lifecycle
Tags are not permanent. They have a lifecycle that mirrors the evolution of your work:
Creation
A new tag is born when you identify a recurring filtering need that existing tags do not serve. Before creating the tag, check whether an existing tag covers the same ground. Only create new tags when they fill a genuine gap.
Active Use
During active use, the tag should appear in your daily filtering and weekly reviews. If you created a tag but never filter by it, the tag is not serving its purpose and should be questioned.
Decline
As your work evolves, some tags become less relevant. A project-specific tag outlives the project. A client-specific tag persists after the engagement ends. These declining tags clutter your tag list and slow down tag selection when creating new tasks.
Retirement
Retire tags that have not been used in the past 30 days. Do not delete them immediately in case you need them again. Most task managers allow you to archive or hide tags without deleting them, preserving historical data while removing them from your active workflow.
This lifecycle approach prevents the common problem of tag proliferation, where new tags are constantly created but old ones are never removed, leading to a bloated and confusing tag system that nobody trusts.
Tag Naming Conventions for Teams
When multiple team members share a task management system, consistent tag naming prevents confusion and duplication. Establish conventions early and document them in your team handbook. Common conventions include using lowercase with hyphens for multi-word tags, prefixing with the category name for hierarchical organization, avoiding abbreviations that team members might not understand, and using singular rather than plural forms consistently.
Key Takeaways
- Tags add dimensions to your tasks beyond project membership. They describe context, energy level, type, status, and people involved.
- Start with 5 to 8 tags that address your most common filtering needs. Add more only when you have a recurring unmet need.
- Use hierarchical prefixes (context/, energy/, type/) when your tag count exceeds 15 to maintain organization.
- The value of tags is in filtering. Design your tags around the questions you need to answer: what can I do right now, what should I work on next, what is blocked.
- Prune your tags monthly. Remove unused tags, merge duplicates, and keep the system lean.
Frequently Asked Questions
How many tags should I use per task?
One to three tags per task is the sweet spot. More than three suggests your tags may be too granular or overlapping with other task fields.
Should I use tags or folders to organize tasks?
Use projects/folders for the primary organizational structure (what goal does this task support). Use tags for cross-cutting attributes (what kind of work is this, what energy does it require, who is involved).
How do I get my team to use tags consistently?
Start with a shared tag dictionary, limit the number of approved tags, and review tag usage in your team retrospectives. Make it easy by keeping the system simple.
Can I use colors instead of tags?
Colors are visual tags, effectively. They work well for a small number of categories (3 to 5) where the meaning is obvious. Beyond that, text-based tags are more informative and scalable.
What if my task manager does not support tags?
Some tools use labels, categories, or custom fields instead. The concept is the same regardless of the terminology. If your tool truly has no tagging mechanism, consider prefixing task titles with tag-like keywords as a workaround.