1. Provide your published severity level definitions (e.g., P1/P2/P3/P4 or equivalent), including the customer-impact criteria that determine each level.
Why it matters. Severity definitions drive every downstream SLA commitment. Vendors who define severity unilaterally and narrowly can deflect legitimate production incidents into lower tiers, eroding the practical value of the SLA. Buyers need to see the criteria in writing to compare across vendors.
- Provides written, versioned severity definitions tied to customer-impact criteria.
- Allows customer input on initial severity classification.
- Includes examples of incidents at each severity level.
- Severity assigned solely at vendor discretion with no appeal path.
- Definitions exist only in sales decks, not in the support policy or MSA.
- Only P1 has a meaningful response commitment.