Disambiguation by Skill or Time
Context
When classifying entities by function, some entities legitimately fit multiple categories. A worker performs tasks associated with two different occupations. A document addresses topics in two different domains. A product serves multiple use cases.
Problem
Without explicit disambiguation rules, coders make ad hoc decisions, degrading consistency and making the classification less useful for analysis.
Solution
Apply a two-tier disambiguation hierarchy:
- Skill tier: Classify to the category requiring the highest level of skill, expertise, or specialization
- Time tier: If skill requirements are equivalent, classify by where the entity spends the most time (or has the greatest concentration)
The SOC states it directly: “When workers in a single job could be coded in more than one occupation, they should be coded in the occupation that requires the highest level of skill. If there is no measurable difference in skill requirements, workers should be coded in the occupation in which they spend the most time.”
Why This Works
Skill-first classification captures the entity at its most differentiated point. A worker who does both administrative tasks and specialized analysis gets classified as an analyst, because that’s the distinctive capability. Time-second handles the truly ambiguous cases with a consistent, measurable criterion.
Limitations
Requires that “skill level” and “time spent” are assessable. In some domains, these aren’t observable or meaningful. The pattern works best when you have decent information about the entity being classified.
Related: 02-atom—task-based-classification, 06-atom—direct-match-concept, 06-atom—classification-principles-vs-coding-guidelines