{"id":5234,"date":"2026-02-26T01:49:56","date_gmt":"2026-02-25T20:19:56","guid":{"rendered":"https:\/\/blog.spike.sh\/?p=5234"},"modified":"2026-03-06T03:21:54","modified_gmt":"2026-03-05T21:51:54","slug":"compass-for-setting-up-escalation-policy","status":"publish","type":"post","link":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/","title":{"rendered":"A compass for setting up your escalation policy"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Setting up an\u00a0<a href=\"https:\/\/spike.sh\/blog\/what-is-an-escalation-policy\/\" target=\"_blank\" rel=\"noreferrer noopener\">escalation policy<\/a>\u00a0for the first time can feel like standing at a crossroads with no clear sign pointing the way. You could escalate based on severity, by team, or by who&#8217;s available and all of them are valid. Knowing which one fits your situation is the hard part. Think of this guide as your compass for that decision. The five approaches below are the different directions you can take and a combination of two or three usually covers most situations well.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Table of contents<\/strong><\/p>\n\n\n\n<nav aria-label=\"Table of Contents\" class=\"wp-block-table-of-contents\"><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#approach-1-severity-and-priority-based\">Approach 1: Severity and priority-based<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#approach-2-role-based\">Approach 2: Role-based<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#approach-3-channel-based\">Approach 3: Channel-based<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#approach-4-team-based\">Approach 4: Team-based<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#approach-5-time-based\">Approach 5: Time-based<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#faqs\">FAQs<\/a><\/li><\/ol><\/nav>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"approach-1-severity-and-priority-based\" class=\"wp-block-heading\">Approach 1: Severity and priority-based<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Severity and priority-based policies are probably the most common approach to escalation. <strong>Each incident gets a severity or priority label and that decides which escalation policy it follows.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Severity describes the impact of an incident. Priority describes how urgently it needs to be addressed. Teams usually define three tiers for each: <code>SEV-1<\/code>, <code>SEV-2<\/code> and <code>SEV-3<\/code> for severity and <code>P1<\/code>, <code>P2<\/code> and <code>P3<\/code> for priority. Some teams go up to <code>P4<\/code> or <code>P5<\/code> as their incident volume grows and their classification gets more granular.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A SEV-1 incident like a payment service going down, triggers a phone call to the on-call responder. With no acknowledgment after five minutes, it moves to a senior engineer. A P1 incident like an enterprise customer losing access to a core feature, gets an urgent response because the business impact is high. A SEV-2 or P2 incident like a non-critical service running slower than usual, might trigger a phone call only during business hours.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One thing worth sorting out before you set up these policies is a shared definition of what each severity and priority label actually means for your team. Without that agreement, the same incident gets classified differently by different people and the policy behaves inconsistently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A useful question to ask when deciding what counts as critical: which incident would wake you up at 3am? That&#8217;s your SEV-1 or P1.<\/strong> Everything else falls below it.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Learn more about escalation policies for <a href=\"https:\/\/spike.sh\/blog\/escalation-policy-for-critical-incidents\/\" type=\"link\" id=\"https:\/\/spike.sh\/blog\/escalation-policy-for-critical-incidents\/\">critical incidents<\/a> and <a href=\"https:\/\/spike.sh\/blog\/escalation-policy-for-low-priority-incidents\/\">low-priority incidents<\/a><\/strong><\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Severity and priority-based routing is a solid first choice for almost any team. If you&#8217;re just getting started and aren&#8217;t sure where to begin, this is probably the right first step. It also scales naturally as your incident volume grows and your definitions get sharper.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>In&nbsp;<a href=\"https:\/\/spike.sh\/\">Spike<\/a>, <a href=\"https:\/\/spike.sh\/alert-rules\">Alert Rules<\/a> automatically route incidents to the right escalation policy based on their severity or priority.<\/strong><\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"approach-2-role-based\" class=\"wp-block-heading\">Approach 2: Role-based<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Role-based escalation policies route incidents based on people&#8217;s roles in the team rather than what the incident is.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The most common version is a three-tier structure:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>L1<\/code>: The on-call responder. Gets first contact and owns the initial response.<\/li>\n\n\n\n<li><code>L2<\/code>: The team lead or senior engineer. Steps in if L1 doesn&#8217;t acknowledge or needs support.<\/li>\n\n\n\n<li><code>L3<\/code>: The engineering manager or incident commander. Enters the chain for high-impact incidents that need broader coordination.<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Learn more about <a href=\"https:\/\/spike.sh\/blog\/understading-l1-l2-l3-escalation-policy\/\" type=\"link\" id=\"https:\/\/spike.sh\/blog\/understading-l1-l2-l3-escalation-policy\/\">L1, L2, L3 escalation policy \u2192<\/a><\/strong><\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Each role has a clear responsibility in the chain. L1 triages the incident and attempts a fix. If the incident isn&#8217;t resolved within a set time, it moves to L2. L3 comes in when the situation needs someone with the authority to make bigger decisions or pull in more people.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Role-based policies work well when your team has distinct functions and clear ownership across different parts of the system.<\/strong> If you want incidents to follow a structured path rather than land with whoever happens to be free, this approach is worth setting up alongside your severity-based policies.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"approach-3-channel-based\" class=\"wp-block-heading\">Approach 3: Channel-based<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Channel-based policies focus on how an incident reaches someone rather than who receives it. A phone call at midnight communicates urgency in a way a Slack message simply doesn&#8217;t. That difference is intentional. <strong>The channel itself is part of the message<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Critical incidents usually warrant a phone call. A phone call demands attention. Lower-severity incidents where team awareness matters more than immediate action are a good fit for a Slack or Microsoft Teams notification. A failed email notification to a single user or a non-critical service running slower than usual probably doesn&#8217;t need to wake anyone up. A channel post is enough.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Channel-based thinking also works well as a starting point for teams that haven&#8217;t yet defined severity levels.<\/strong> Rather than asking &#8220;is this SEV-1 or SEV-2?&#8221;, the question becomes simpler: does this need a phone call or a Slack message? The channel carries the urgency signal. It&#8217;s an easier decision to make and still gets the right incidents to the right people quickly.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"approach-4-team-based\" class=\"wp-block-heading\">Approach 4: Team-based<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Team-based policies route incidents to the team that owns the affected system. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A security breach goes to the security team<\/li>\n\n\n\n<li>A database failure goes to the SRE team<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Each team only sees the incidents that belong to them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>This approach suits larger organisations where distinct teams own distinct parts of the system.<\/strong> It keeps teams focused on their area and stops the wrong people from being pulled into incidents outside their work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For smaller teams where everyone owns most things, this level of separation probably isn&#8217;t necessary yet. A five-person engineering team rarely needs separate escalation paths for separate sub-teams. As the team grows and system ownership becomes more specialised, team-based policies start to make more sense. It&#8217;s more of a direction to grow into than something to set up from day one.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"approach-5-time-based\" class=\"wp-block-heading\">Approach 5: Time-based<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Time-based policies are less a standalone approach and more a layer you add on top of any of the others. The incident itself doesn&#8217;t change. What changes is your team&#8217;s availability and how quickly a response is needed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same P1 incident might call for an immediate phone call at 11pm but only a Slack message at 10am when the team is likely already online.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A time layer is worth adding once your core policies are in place. Many teams add it a few weeks in when they notice the same policy doesn&#8217;t quite fit every time window. It doesn&#8217;t require rebuilding anything from scratch. It just makes every existing policy more precise.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>In Spike, you can set up time-based conditions in <a href=\"https:\/\/spike.sh\/alert-rules\">Alert Rules<\/a> to load different escalation policies depending on the time of day. A separate escalation policy for business hours and another for off-hours. Alert Rules then decide which one gets applied when an incident triggers.<\/strong><\/p>\n<\/blockquote>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-ee856660 wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link has-midnight-gradient-background has-background wp-element-button\" href=\"http:\/\/app.spike.sh\/signup\">Try Spike free for 14 days<\/a><\/div>\n<\/div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">There&#8217;s no single escalation setup that fits every team. What matters is that the policies you put in place reflect how your team actually works. <strong>Most teams find that a combination of two or three approaches covers most situations well.<\/strong> Something as simple as a severity-based policy with channel and time conditions layered in goes a long way.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Go ahead and try something. You&#8217;ll refine it as you learn.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"faqs\" class=\"wp-block-heading\">FAQs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Can the same person appear in multiple escalation policies?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, and that&#8217;s quite common. For instance, your engineering manager might sit in the last step of several escalation policies. The main thing is to make sure that the person knows they&#8217;re in the chain and understands how and when they&#8217;ll be contacted.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How many escalation policies does a team typically need?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There&#8217;s no fixed number. Many teams run well with two or three. The number usually grows naturally as you learn your incident patterns. It&#8217;s rarely worth trying to predict the right number upfront.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Can incidents from the same integration follow different escalation policies?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. In <a href=\"https:\/\/spike.sh\" type=\"link\" id=\"spike.sh\">Spike<\/a>, alert rules let you route incidents based on their content. Two incidents from the same integration can follow entirely different policies if the payload carries different severity labels or keywords.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There&#8217;s no single way to set up an escalation policy. This guide walks through five approaches and helps you figure out which combination fits your team.<\/p>\n","protected":false},"author":263547072,"featured_media":5419,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","_import_markdown_pro_load_document_selector":0,"_import_markdown_pro_submit_text_textarea":"","_lmt_disableupdate":"","_lmt_disable":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":true,"token":"eyJpbWciOiJodHRwczpcL1wvYmxvZy5zcGlrZS5zaFwvd3AtY29udGVudFwvdXBsb2Fkc1wvMjAyNlwvMDJcL0Jhc2ljcy1vZi1JbmNpZGVudC1NYW5hZ2VtZW50LTEtMy0xMDI0eDU1NS5wbmciLCJ0eHQiOiJBIGNvbXBhc3MgZm9yIHNldHRpbmcgdXAgeW91ciBlc2NhbGF0aW9uIHBvbGljeSIsInRlbXBsYXRlIjoiaGlnaHdheSIsImZvbnQiOiIiLCJibG9nX2lkIjoyMzMxMzg5MDB9.FlgA9bhucnuA_Oz5AUisGV7TsPyoMizVP8LsaMVLXboMQ"},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[1467],"tags":[],"class_list":["post-5234","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>A compass for setting up your escalation policy<\/title>\n<meta name=\"description\" content=\"Not sure how to set up your escalation policy? Here are five approaches to help you pick the right one for your team.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"A compass for setting up your escalation policy\" \/>\n<meta property=\"og:description\" content=\"Not sure how to set up your escalation policy? Here are five approaches to help you pick the right one for your team.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/\" \/>\n<meta property=\"og:site_name\" content=\"Spike&#039;s blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-25T20:19:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-05T21:51:54+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2080\" \/>\n\t<meta property=\"og:image:height\" content=\"1128\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Sreekar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Sreekar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/\"},\"author\":{\"name\":\"Sreekar\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/eb31f40342cbe6a94ef67a1c0bf20923\"},\"headline\":\"A compass for setting up your escalation policy\",\"datePublished\":\"2026-02-25T20:19:56+00:00\",\"dateModified\":\"2026-03-05T21:51:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/\"},\"wordCount\":1283,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Basics-of-Incident-Management-1-3.png\",\"articleSection\":[\"Guides\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/\",\"name\":\"A compass for setting up your escalation policy\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Basics-of-Incident-Management-1-3.png\",\"datePublished\":\"2026-02-25T20:19:56+00:00\",\"dateModified\":\"2026-03-05T21:51:54+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/eb31f40342cbe6a94ef67a1c0bf20923\"},\"description\":\"Not sure how to set up your escalation policy? Here are five approaches to help you pick the right one for your team.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Basics-of-Incident-Management-1-3.png\",\"contentUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Basics-of-Incident-Management-1-3.png\",\"width\":2080,\"height\":1128},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/compass-for-setting-up-escalation-policy\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.spike.sh\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"A compass for setting up your escalation policy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/\",\"name\":\"Spike&#039;s blog\",\"description\":\"Learnings and opinions in a changing world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blog.spike.sh\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/eb31f40342cbe6a94ef67a1c0bf20923\",\"name\":\"Sreekar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cb2a2f53f3fd9e9619b7d3aaca20588e6101b5d239f52e0137823bd5d6cd0941?s=96&d=robohash&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cb2a2f53f3fd9e9619b7d3aaca20588e6101b5d239f52e0137823bd5d6cd0941?s=96&d=robohash&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/cb2a2f53f3fd9e9619b7d3aaca20588e6101b5d239f52e0137823bd5d6cd0941?s=96&d=robohash&r=g\",\"caption\":\"Sreekar\"},\"url\":\"https:\\\/\\\/blog.spike.sh\\\/author\\\/sreekar98\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"A compass for setting up your escalation policy","description":"Not sure how to set up your escalation policy? Here are five approaches to help you pick the right one for your team.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/","og_locale":"en_GB","og_type":"article","og_title":"A compass for setting up your escalation policy","og_description":"Not sure how to set up your escalation policy? Here are five approaches to help you pick the right one for your team.","og_url":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/","og_site_name":"Spike&#039;s blog","article_published_time":"2026-02-25T20:19:56+00:00","article_modified_time":"2026-03-05T21:51:54+00:00","og_image":[{"width":2080,"height":1128,"url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png","type":"image\/png"}],"author":"Sreekar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Sreekar","Estimated reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#article","isPartOf":{"@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/"},"author":{"name":"Sreekar","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/eb31f40342cbe6a94ef67a1c0bf20923"},"headline":"A compass for setting up your escalation policy","datePublished":"2026-02-25T20:19:56+00:00","dateModified":"2026-03-05T21:51:54+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/"},"wordCount":1283,"commentCount":0,"image":{"@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png","articleSection":["Guides"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/","url":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/","name":"A compass for setting up your escalation policy","isPartOf":{"@id":"https:\/\/blog.spike.sh\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#primaryimage"},"image":{"@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png","datePublished":"2026-02-25T20:19:56+00:00","dateModified":"2026-03-05T21:51:54+00:00","author":{"@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/eb31f40342cbe6a94ef67a1c0bf20923"},"description":"Not sure how to set up your escalation policy? Here are five approaches to help you pick the right one for your team.","breadcrumb":{"@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#primaryimage","url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png","contentUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png","width":2080,"height":1128},{"@type":"BreadcrumbList","@id":"https:\/\/blog.spike.sh\/compass-for-setting-up-escalation-policy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.spike.sh\/"},{"@type":"ListItem","position":2,"name":"A compass for setting up your escalation policy"}]},{"@type":"WebSite","@id":"https:\/\/blog.spike.sh\/#website","url":"https:\/\/blog.spike.sh\/","name":"Spike&#039;s blog","description":"Learnings and opinions in a changing world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.spike.sh\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Person","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/eb31f40342cbe6a94ef67a1c0bf20923","name":"Sreekar","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/cb2a2f53f3fd9e9619b7d3aaca20588e6101b5d239f52e0137823bd5d6cd0941?s=96&d=robohash&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/cb2a2f53f3fd9e9619b7d3aaca20588e6101b5d239f52e0137823bd5d6cd0941?s=96&d=robohash&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cb2a2f53f3fd9e9619b7d3aaca20588e6101b5d239f52e0137823bd5d6cd0941?s=96&d=robohash&r=g","caption":"Sreekar"},"url":"https:\/\/blog.spike.sh\/author\/sreekar98\/"}]}},"modified_by":"Sreekar","jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-1-3.png","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfMe4Q-1mq","jetpack-related-posts":[{"id":5273,"url":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/","url_meta":{"origin":5234,"position":0},"title":"Understanding L1, L2, L3 escalation policy","author":"Sreekar","date":"27th February, 2026","format":false,"excerpt":"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each level, and what it looks like in practice.","rel":"","context":"In &quot;Guides&quot;","block_context":{"text":"Guides","link":"https:\/\/blog.spike.sh\/category\/guides\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-8.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-8.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-8.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-8.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-8.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-8.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":5690,"url":"https:\/\/blog.spike.sh\/severity-and-priority-based-routing\/","url_meta":{"origin":5234,"position":1},"title":"Routing incidents the way their severity and priority demand","author":"Sreekar","date":"29th March, 2026","format":false,"excerpt":"Should this incident get a phone call or a Slack message? Severity and priority answer that question. This guide shows how to build routing rules around both.","rel":"","context":"In &quot;Guides&quot;","block_context":{"text":"Guides","link":"https:\/\/blog.spike.sh\/category\/guides\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-7.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-7.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-7.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-7.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-7.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-7.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":5266,"url":"https:\/\/blog.spike.sh\/escalation-policy-for-critical-incidents\/","url_meta":{"origin":5234,"position":2},"title":"Escalation policy for critical incidents","author":"Sreekar","date":"27th February, 2026","format":false,"excerpt":"Getting your escalation policy for critical incidents right takes a few careful decisions upfront. This guide helps you work through them.","rel":"","context":"In &quot;Guides&quot;","block_context":{"text":"Guides","link":"https:\/\/blog.spike.sh\/category\/guides\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-9.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-9.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-9.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-9.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-9.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-9.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":5246,"url":"https:\/\/blog.spike.sh\/escalation-policy-for-low-priority-incidents\/","url_meta":{"origin":5234,"position":3},"title":"Escalation policy for low-priority incidents","author":"Sreekar","date":"26th February, 2026","format":false,"excerpt":"This guide walks through low-priority incidents, why they need attention, and how to setup an escalation policy for them.","rel":"","context":"In &quot;Guides&quot;","block_context":{"text":"Guides","link":"https:\/\/blog.spike.sh\/category\/guides\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-10.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-10.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-10.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-10.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-10.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-10.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":5227,"url":"https:\/\/blog.spike.sh\/what-is-an-escalation-policy\/","url_meta":{"origin":5234,"position":4},"title":"What is an escalation policy? (And why every team needs one)","author":"Sreekar","date":"25th February, 2026","format":false,"excerpt":"This guide breaks down escalation policies: what they are, what they look like, and how they fit with your on-call schedule.","rel":"","context":"In &quot;Guides&quot;","block_context":{"text":"Guides","link":"https:\/\/blog.spike.sh\/category\/guides\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-2-3.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-2-3.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-2-3.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-2-3.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-2-3.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Basics-of-Incident-Management-2-3.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":335,"url":"https:\/\/blog.spike.sh\/getting-started-on-alerts-with-escalation-policy\/","url_meta":{"origin":5234,"position":5},"title":"Getting Started on Alerts with Escalation Policies","author":"Gurneet Kaur","date":"23rd October, 2023","format":false,"excerpt":"Discover the key to effective incident management \u2013 setting up alert escalation policies. Learn how to get started with our step-by-step guide to ensure timely responses and minimal downtime during critical incidents.","rel":"","context":"In &quot;Alerts&quot;","block_context":{"text":"Alerts","link":"https:\/\/blog.spike.sh\/category\/incident-management\/alerts\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/10\/Getting-started-on-alerts-with-Escalation-Policies.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/10\/Getting-started-on-alerts-with-Escalation-Policies.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/10\/Getting-started-on-alerts-with-Escalation-Policies.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/10\/Getting-started-on-alerts-with-Escalation-Policies.png?resize=700%2C400&ssl=1 2x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5234","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/users\/263547072"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/comments?post=5234"}],"version-history":[{"count":27,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5234\/revisions"}],"predecessor-version":[{"id":5443,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5234\/revisions\/5443"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media\/5419"}],"wp:attachment":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media?parent=5234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/categories?post=5234"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/tags?post=5234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}