Common priority scales
| Scale | Levels | Typical use |
|---|---|---|
| 3 levels | High, medium, low | Personal lists, small teams |
| P-levels | P0/P1 (critical) to P4 (lowest) | Software, IT, product teams (ClickUp's guide uses P0 to P4) |
| 1 to 5 | 1 = highest, 5 = lowest | Ticket systems |
| 0 to 1000 | 500 = default | Microsoft Project's priority field |
A 4-level scale with definitions
| Level | Definition | Example |
|---|---|---|
| P1, critical | Blocks work or causes harm now; drop everything | Payment system down |
| P2, high | Important with a near deadline; this week | Contract due Friday |
| P3, medium | Important, no near deadline; schedule it | Write the onboarding guide |
| P4, low | Nice to have; do if time allows, or drop | Rename old files |
Why everything ends up "high"
One label mixes two questions: how urgent, and how important. When a single scale carries both, people bump everything up. Splitting the two, as the Eisenhower matrix does, fixes most priority inflation: P1 is urgent and important, P3 is important but not urgent, and urgent-but-unimportant work gets delegated instead of labelled high.
| Urgent | Not urgent | |
|---|---|---|
| Important | 1. Do it now Deadlines today, crises, problems that get worse if you wait | 2. Schedule it Planning, learning, health, relationships, long-term projects |
| Not important | 3. Delegate or shrink it Interruptions, many messages and meetings, other people's priorities | 4. Drop it Busywork, mindless scrolling, tasks nobody would miss |
Cronos, by Gambit Studio, replaces a single priority label with two questions on iPhone and iPad: each task goes into one of four quadrants by urgency and importance.