Skip to content

Severity and priority

Adrià Castany 2 min

What is severity and priority?

Severity measures how much damage an issue causes and priority decides the order in which it is handled. Severity comes from the impact on the customer and does not change with who is affected. Priority adds business context, such as the customer’s plan, the committed deadline or an upcoming renewal.

Also called

severity level, priority level, P1, SEV1, urgency

Topic
Support concepts
On this page
  1. Why they are not the same
  2. Why it matters
  3. Severity versus priority
  4. An example of severity levels
  5. How priority is decided
  6. Who can change them
  7. How Intake handles it
  8. Frequently asked questions

Why they are not the same

A bug that stops one small customer from working is high severity and may still not be first in line.

A typo on the largest customer’s invoice is low severity and gets fixed today. When the two scales are merged into one field, everything ends up marked urgent and the scale stops sorting anything.

Why it matters

Without both scales, whoever pushes hardest wins.

Severity lets support and engineering talk about the same damage in the same words, and priority puts on record why one case goes before another. SLA targets are almost always set by priority.

Severity versus priority

Severity describes the issue and priority describes the decision.

SeverityPriority
What it measuresThe damage the issue causesThe order it is handled in
Depends onImpact and whether a workaround existsSeverity, the customer and deadlines
Who sets itSupport, against written criteriaWhoever allocates the work
Changes over timeOnly if the impact changesYes, as a deadline approaches

An example of severity levels

Four levels are usual, defined by what the customer cannot do.

Names vary from one company to the next.

  • Critical. The service is down or data is being lost, with no workaround.
  • High. A main function fails and the workaround is costly.
  • Medium. Something fails but work can continue.
  • Low. A minor defect, a question or an improvement request.

How priority is decided

Priority starts from severity and adjusts it with three business facts.

  • The commitment. If the customer has an SLA, the deadline rules.
  • The reach. How many customers or users are affected.
  • The timing. A renewal coming up, a go-live or a month-end close.

Who can change them

The customer describes the impact and the team assigns the level against written criteria.

If anyone can raise priority without justifying it, the scale fills up at the top within weeks.

How Intake handles it

Frequently asked questions

What is the difference between severity and priority?

Severity says how much damage the issue does and priority says when it gets handled. The first comes from impact and the second adds the customer’s context and committed deadlines.

Can something be high severity and low priority?

Yes. A serious failure in a function almost nobody uses, or one with a simple workaround, can wait longer than a minor defect hitting every customer on invoicing day.

What do P1, P2, P3 and P4 mean?

They are priority levels, from highest to lowest. P1 is handled immediately and P4 goes into normal planning. SEV1 to SEV4 name severity in the same way.

Who sets severity, the customer or the team?

The team, from what the customer reports and against written criteria both sides know. Publishing those criteria in the SLA avoids arguing about them mid-incident.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment