{"id":5273,"date":"2026-02-27T17:44:26","date_gmt":"2026-02-27T12:14:26","guid":{"rendered":"https:\/\/blog.spike.sh\/?p=5273"},"modified":"2026-07-06T15:26:49","modified_gmt":"2026-07-06T09:56:49","slug":"understading-l1-l2-l3-escalation-policy","status":"publish","type":"post","link":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/","title":{"rendered":"Understanding L1, L2, L3 escalation policy"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Level 1, Level 2, Level 3 (L1, L2, L3) is one of the common ways to structure an <a href=\"https:\/\/spike.sh\/blog\/what-is-an-escalation-policy\/\" type=\"link\" id=\"https:\/\/spike.sh\/blog\/what-is-an-escalation-policy\/\">escalation policy<\/a>. The idea is simple: an incident triggers and lands with the first responder. If it needs more attention, it moves up the chain to someone with more expertise. This guide explains how each level works, when this structure makes sense, and what to keep in mind when setting one up.<\/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\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"what-l1-l2-and-l3-actually-mean\" class=\"wp-block-heading\">What L1, L2, and L3 actually mean<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">L1, L2, and L3 are simply levels in the escalation chain. Here&#8217;s how teams think about them:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>L1 is the first contact.<\/strong> Usually an <a href=\"https:\/\/spike.sh\/glossary\/oncall-responder\/\" type=\"link\" id=\"https:\/\/spike.sh\/glossary\/oncall-responder\/\">on-call responder<\/a> who picks up the incident, <a href=\"https:\/\/spike.sh\/glossary\/triage\/\" type=\"link\" id=\"https:\/\/spike.sh\/glossary\/triage\/\">triages<\/a> it, and attempts a fix.<\/li>\n\n\n\n<li><strong>L2 is someone with deeper system knowledge.<\/strong> Often a subject matter expert or senior engineer who steps in when L1 needs <a href=\"https:\/\/spike.sh\/glossary\/backup-responder\/\">backup<\/a>.<\/li>\n\n\n\n<li><strong>L3 is the final escalation point.<\/strong> A manager or specialist who comes in if the incident is still unresolved after L2.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Most <a href=\"https:\/\/spike.sh\/glossary\/critical-incident\/\">critical incidents<\/a> get resolved at L1 or L2. And L3 is more of a safety net.<\/p>\n\n\n\n<div class=\"wp-block-group\" style=\"padding-top:var(--wp--preset--spacing--30);padding-right:var(--wp--preset--spacing--40);padding-bottom:var(--wp--preset--spacing--30);padding-left:var(--wp--preset--spacing--40)\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-container-core-group-is-layout-7949ca13 wp-block-group-is-layout-constrained\">\n<p class=\"has-background wp-block-paragraph\" style=\"border-top-left-radius:13px;border-top-right-radius:13px;border-bottom-left-radius:13px;border-bottom-right-radius:13px;background-color:#cbd0d8\">L1 doesn&#8217;t always have to mean junior. Some teams put their senior engineers at L1 because speed at the first step matters to them. Others use L1 as a learning position with a more experienced engineer at L2 as a backup. Both approaches work. The choice comes down to what your team is optimizing for.<\/p>\n<\/div><\/div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"when-does-the-l1-l2-l3-escalation-policy-make-sense\" class=\"wp-block-heading\">When does the L1, L2, L3 escalation policy make sense?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>L1, L2, L3 escalation policy makes sense when expertise varies across your team.<\/strong> A small team with a simple setup probably doesn&#8217;t need it. But once you have specialists who own specific services, a defined chain means they only get pulled in when the incident actually needs them.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"what-an-l1-l2-l3-escalation-policy-actually-looks-like\" class=\"wp-block-heading\">What an L1, L2, L3 escalation policy actually looks like<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here are two examples showing how L1, L2, L3 escalation policy plays out.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a high-priority incident:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Step 1:<\/strong> Phone call to L1 (on-call responder)<br>If not acknowledged in 5 mins, move to level 2<\/li>\n\n\n\n<li><strong>Step 2:<\/strong> Phone call to L2 (subject matter expert or senior engineer)<br>If not acknowledged in 5 mins, move to level 3<\/li>\n\n\n\n<li><strong>Step 3:<\/strong> Phone call to L3 (engineering manager)<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"846\" height=\"622\" data-attachment-id=\"5349\" data-permalink=\"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/screenshot-2026-03-04-at-5-18-02-pm\/\" data-orig-file=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.18.02-PM.png\" data-orig-size=\"846,622\" data-comments-opened=\"1\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"Screenshot 2026-03-04 at 5.18.02\u202fPM\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.18.02-PM.png\" src=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.18.02-PM.png\" alt=\"L1, L2, L3 escalation policy for high-priority incidents (designed on Spike)\" class=\"wp-image-5349\" srcset=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.18.02-PM.png 846w, https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.18.02-PM-300x221.png 300w, https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.18.02-PM-768x565.png 768w\" sizes=\"auto, (max-width: 846px) 100vw, 846px\" \/><figcaption class=\"wp-element-caption\">L1, L2, L3 escalation policy for high-priority incidents (created on <a href=\"http:\/\/spike.sh\" type=\"link\" id=\"spike.sh\">Spike<\/a>)<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For a low-priority incident:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Step 1:<\/strong> Email to L1 (on-call responder)<br>If not acknowledged in 2 hours, move to level 2<\/li>\n\n\n\n<li><strong>Step 2:<\/strong> Email to L2 (subject matter expert or senior engineer)<br>If not acknowledged in 2 hours, move to level 3<\/li>\n\n\n\n<li><strong>Step 3:<\/strong> Mobile notification to L3 (engineering manager)<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"850\" height=\"627\" data-attachment-id=\"5345\" data-permalink=\"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/screenshot-2026-03-04-at-5-10-35-pm\/\" data-orig-file=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.10.35-PM.png\" data-orig-size=\"850,627\" data-comments-opened=\"1\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}\" data-image-title=\"Screenshot 2026-03-04 at 5.10.35\u202fPM\" data-image-description=\"\" data-image-caption=\"\" data-large-file=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.10.35-PM.png\" src=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.10.35-PM.png\" alt=\"L1, L2, L3 escalation policy for low-priority incidents (designed on Spike)\" class=\"wp-image-5345\" srcset=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.10.35-PM.png 850w, https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.10.35-PM-300x221.png 300w, https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/Screenshot-2026-03-04-at-5.10.35-PM-768x567.png 768w\" sizes=\"auto, (max-width: 850px) 100vw, 850px\" \/><figcaption class=\"wp-element-caption\">L1, L2, L3 escalation policy for low-priority incidents (created on <a href=\"http:\/\/spike.sh\" type=\"link\" id=\"spike.sh\">Spike<\/a>)<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In both cases, the incident moves through L1, L2, and L3 in the same order. What changes is how urgently it moves and how it reaches each person.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>In <a href=\"http:\/\/spike.sh\">Spike<\/a>, you can set up an L1, L2, L3 escalation policy in less than 2 minutes. And updating it later is just as quick.<\/strong><\/p>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-fe48e5de 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\" style=\"border-style:none;border-width:0px;border-top-left-radius:9px;border-top-right-radius:9px;border-bottom-left-radius:9px;border-bottom-right-radius:9px\">Try Spike for free<\/a><\/div>\n<\/div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"what-happens-if-nobody-responds-at-l3\" class=\"wp-block-heading\">What happens if nobody responds at L3<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">It&#8217;s worth deciding this before the policy goes live. Here&#8217;s how you can handle it in one of two ways.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Option one is to loop the incident back to L1 and start the chain again.<\/strong> This makes sense when the no-response was likely a timing issue rather than a sign that the incident is beyond the team&#8217;s capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Option two is to open a broader response.<\/strong> A dedicated Slack channel, a group call, or a message to the wider team. This makes more sense when the incident has already been through the full chain without resolution and clearly needs more hands.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Either approach is fine. The important thing is that the policy has a clear answer rather than leaving it open-ended.<\/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>How often should we review our L1, L2, L3 policy?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A good time to review is after a significant incident or when the team composition changes. If incidents are regularly reaching L3 before getting resolved, that&#8217;s a signal worth paying attention to. It usually means something in the chain needs adjusting, whether that&#8217;s the wait times, the people at each level, or both.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What happens to an incident once L2 or L3 acknowledges it?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The escalation chain stops as soon as someone acknowledges. The incident stays with that person until it&#8217;s resolved. If you want a safety net for incidents that get acknowledged but never closed, Spike&#8217;s&nbsp;<a href=\"https:\/\/docs.spike.sh\/incidents\/resolve-timer\" target=\"_blank\" rel=\"noreferrer noopener\">Resolve by Timer<\/a>&nbsp;can help. It automatically resolves an incident after a set duration, so stale incidents don&#8217;t linger on your dashboard or block new alerts from the same source.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How does an L1, L2, L3 policy interact with on-call schedules?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The two work closely together. An on-call schedule decides who is responsible for incidents during a given period. The escalation policy decides what happens when that person doesn&#8217;t respond. L1 in the policy often points to whoever is currently on-call rather than a fixed person. That way, the two stay in sync automatically.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each level, and what it looks like in practice.<\/p>\n","protected":false},"author":263547072,"featured_media":6194,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_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,"_wpcom_ai_launchpad_first_post":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"{title}\n\n{excerpt}\n\n{url}","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":"eyJpbWciOiJodHRwczpcL1wvYmxvZy5zcGlrZS5zaFwvd3AtY29udGVudFwvdXBsb2Fkc1wvMjAyNlwvMDJcL2wxLWwyLWwzLWVzY2FsYXRpb24tcG9saWN5LTItMTAyNHg1NzYucG5nIiwidHh0IjoiVW5kZXJzdGFuZGluZyBMMSwgTDIsIEwzIGVzY2FsYXRpb24gcG9saWN5IiwidGVtcGxhdGUiOiJoaWdod2F5IiwiZm9udCI6IiIsImJsb2dfaWQiOjIzMzEzODkwMH0.H0ZLmaDDK_FibzC1vTA5Ha9c3YhlV4W77eI1fnDyyOcMQ"},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[1467],"tags":[],"class_list":["post-5273","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Understanding L1, L2, L3 escalation policy<\/title>\n<meta name=\"description\" content=\"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each tier, and what it looks like in practice.\" \/>\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\/understading-l1-l2-l3-escalation-policy\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Understanding L1, L2, L3 escalation policy\" \/>\n<meta property=\"og:description\" content=\"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each tier, and what it looks like in practice.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/\" \/>\n<meta property=\"og:site_name\" content=\"Welcome to Spike.\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-27T12:14:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-06T09:56:49+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/l1-l2-l3-escalation-policy-2.png\" \/>\n\t<meta property=\"og:image:width\" content=\"4800\" \/>\n\t<meta property=\"og:image:height\" content=\"2700\" \/>\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=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/\"},\"author\":{\"name\":\"Sreekar\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/eb31f40342cbe6a94ef67a1c0bf20923\"},\"headline\":\"Understanding L1, L2, L3 escalation policy\",\"datePublished\":\"2026-02-27T12:14:26+00:00\",\"dateModified\":\"2026-07-06T09:56:49+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/\"},\"wordCount\":861,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/l1-l2-l3-escalation-policy-2.png\",\"articleSection\":[\"Guides\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/\",\"name\":\"Understanding L1, L2, L3 escalation policy\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/l1-l2-l3-escalation-policy-2.png\",\"datePublished\":\"2026-02-27T12:14:26+00:00\",\"dateModified\":\"2026-07-06T09:56:49+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/eb31f40342cbe6a94ef67a1c0bf20923\"},\"description\":\"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each tier, and what it looks like in practice.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/l1-l2-l3-escalation-policy-2.png\",\"contentUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/l1-l2-l3-escalation-policy-2.png\",\"width\":4800,\"height\":2700},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/understading-l1-l2-l3-escalation-policy\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.spike.sh\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Understanding L1, L2, L3 escalation policy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/\",\"name\":\"Welcome to Spike.\",\"description\":\"In this space, our team talks about all things incidents, response, oncall, and share our journey of building Spike.\",\"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":"Understanding L1, L2, L3 escalation policy","description":"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each tier, and what it looks like in practice.","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\/understading-l1-l2-l3-escalation-policy\/","og_locale":"en_GB","og_type":"article","og_title":"Understanding L1, L2, L3 escalation policy","og_description":"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each tier, and what it looks like in practice.","og_url":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/","og_site_name":"Welcome to Spike.","article_published_time":"2026-02-27T12:14:26+00:00","article_modified_time":"2026-07-06T09:56:49+00:00","og_image":[{"width":4800,"height":2700,"url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/l1-l2-l3-escalation-policy-2.png","type":"image\/png"}],"author":"Sreekar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Sreekar","Estimated reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#article","isPartOf":{"@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/"},"author":{"name":"Sreekar","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/eb31f40342cbe6a94ef67a1c0bf20923"},"headline":"Understanding L1, L2, L3 escalation policy","datePublished":"2026-02-27T12:14:26+00:00","dateModified":"2026-07-06T09:56:49+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/"},"wordCount":861,"commentCount":0,"image":{"@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/l1-l2-l3-escalation-policy-2.png","articleSection":["Guides"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/","url":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/","name":"Understanding L1, L2, L3 escalation policy","isPartOf":{"@id":"https:\/\/blog.spike.sh\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#primaryimage"},"image":{"@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/l1-l2-l3-escalation-policy-2.png","datePublished":"2026-02-27T12:14:26+00:00","dateModified":"2026-07-06T09:56:49+00:00","author":{"@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/eb31f40342cbe6a94ef67a1c0bf20923"},"description":"This guide breaks down the L1, L2, L3 escalation structure, how incidents move through each tier, and what it looks like in practice.","breadcrumb":{"@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#primaryimage","url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/l1-l2-l3-escalation-policy-2.png","contentUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2026\/02\/l1-l2-l3-escalation-policy-2.png","width":4800,"height":2700},{"@type":"BreadcrumbList","@id":"https:\/\/blog.spike.sh\/understading-l1-l2-l3-escalation-policy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.spike.sh\/"},{"@type":"ListItem","position":2,"name":"Understanding L1, L2, L3 escalation policy"}]},{"@type":"WebSite","@id":"https:\/\/blog.spike.sh\/#website","url":"https:\/\/blog.spike.sh\/","name":"Welcome to Spike.","description":"In this space, our team talks about all things incidents, response, oncall, and share our journey of building Spike.","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\/l1-l2-l3-escalation-policy-2.png","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfMe4Q-1n3","_links":{"self":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5273","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=5273"}],"version-history":[{"count":35,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5273\/revisions"}],"predecessor-version":[{"id":5354,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/5273\/revisions\/5354"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media\/6194"}],"wp:attachment":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media?parent=5273"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/categories?post=5273"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/tags?post=5273"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}