# Use status labels to track what needs attention

Source: https://www.signoapp.com/en/blog/use-status-labels
Language: en-US
Author: Signoapp Team
Published: 2026-10-01T06:25:00.000Z
Modified: 2026-10-01T06:25:00.000Z

Use only the statuses that change what you do next, and remove any label that merely describes mood or importance.

## Put it into practice

Try a reference from a current project. Use only the statuses that change what you do next, and remove any label that merely describes mood or importance. Leave a note about what you changed and why.

## Choose what to do

Structure only where it changes retrieval

| Need | Lightest structure | Warning sign |
| --- | --- | --- |
| What to try | Use only the statuses that change what you do next, and remove any label that merely describes mood or importance. | Record whether the item stays, changes, or goes, and why. |
| Stable boundary | Collection or folder | The same item needs many homes |
| Cross-cutting trait | Tag | Two tags mean the same thing |
| Temporary state | Status | The state never changes an action |

## What the source supports

### Microsoft Research

Automation can reduce organization cost when people retain review and correction authority. Read Design and In-Situ Evaluation of a Mixed-Initiative Approach to Information Organization. We suggest this guide's steps as an exercise. The source did not evaluate their results.

[Design and In-Situ Evaluation of a Mixed-Initiative Approach to Information Organization](https://www.microsoft.com/en-us/research/publication/design-situ-evaluation-mixed-initiative-approach-information-organization/)

## Work through one real item

Work through one real item

1. Step 1: Start with the retrieval moment.
2. Step 2: Choose one stable boundary.
3. Step 3: Add only terms you can define.
4. Step 4: Test the structure with known items.

Try these steps with your own files. Keep the ones that help you find a reference or decide what to do with it.

## Check the result

- [ ] I recorded what happened in the test, even if it differed from what I expected.
- [ ] Each field changes search or action.
- [ ] Names make sense without private shorthand.
- [ ] Duplicates have one canonical record.
- [ ] Finished work leaves active views.

## When to use another approach

### When to use another approach

More structure raises maintenance cost. Stop adding fields when search already returns the right item and the next action is clear.

## Sources reviewed

- [Design and In-Situ Evaluation of a Mixed-Initiative Approach to Information Organization](https://www.microsoft.com/en-us/research/publication/design-situ-evaluation-mixed-initiative-approach-information-organization/): Microsoft Research. Automation can reduce organization cost when people retain review and correction authority.
- [Searching to Eliminate Personal Information Management](https://www.microsoft.com/en-us/research/publication/searching-to-eliminate-personal-information-management/): Microsoft Research. Search can reduce filing work when retrieval uses remembered context and content.