{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
        "slug": "validate-exit-route-capacity-and-permanence-before-occupancy-changes",
        "url": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/validate-exit-route-capacity-and-permanence-before-occupancy-changes/"
        },
        "title": "Validate exit-route capacity and permanence before occupancy changes",
        "summary": "Use 29 CFR 1910.36 - Design and construction requirements for exit routes to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T12:12:34+00:00",
        "modified_at": "2026-08-27T13:04:10+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 608,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 29 CFR 1910.36 - Design and construction requirements for exit routes",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "29 CFR 1910.36 - Design and construction requirements for exit routes",
            "url": "https://www.ecfr.gov/current/title-29/section-1910.36",
            "published_on": null,
            "authority": "www.ecfr.gov"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Treat this document as a focused evidence review: Validate exit-route capacity and permanence before occupancy changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.ecfr.gov/current/title-29/section-1910.36\" target=\"_blank\" rel=\"noopener noreferrer\">29 CFR 1910.36 &#8211; Design and construction requirements for exit routes</a> from Occupational Safety and Health Administration via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 29 CFR 1910, the rule requires that more than two exit routes be available in a workplace if the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would not be able to evacuate safely during an emergency. The research record locates this support at <strong>29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2))</strong>.</li>\n<li>Under 29 CFR 1910, a single exit route is permitted where the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would be able to evacuate safely during an emergency. The research record locates this support at <strong>29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3))</strong>.</li>\n</ul>\n<p>Only the traced statements above are asserted as source facts. Apply the review to critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths after confirming that the source and deployed context match.</p>\n<h2>What the source does not establish</h2>\n<p>Federal workplace rule; building and fire codes, occupancy, alterations, and authority-having-jurisdiction decisions also govern egress design. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?</li>\n<li>How will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.</p>\n<p>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2))</strong>; <strong>29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3))</strong> through facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Record what was collected, where, when, by whom, and which system or role it represents.</p>\n<p>Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-29/section-1910.36\" target=\"_blank\" rel=\"noopener noreferrer\">29 CFR 1910.36 &#8211; Design and construction requirements for exit routes</a> — Occupational Safety and Health Administration via eCFR</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Validate exit-route capacity and permanence before occupancy changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 29 CFR 1910.36 – Design and construction requirements for exit routes from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\nUnder 29 CFR 1910, the rule requires that more than two exit routes be available in a workplace if the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would not be able to evacuate safely during an emergency. The research record locates this support at 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)).\nUnder 29 CFR 1910, a single exit route is permitted where the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would be able to evacuate safely during an emergency. The research record locates this support at 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths after confirming that the source and deployed context match.\nWhat the source does not establish\nFederal workplace rule; building and fire codes, occupancy, alterations, and authority-having-jurisdiction decisions also govern egress design. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nA reviewer should be able to retrace the decision from 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)); 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)) through facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Record what was collected, where, when, by whom, and which system or role it represents.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n29 CFR 1910.36 – Design and construction requirements for exit routes — Occupational Safety and Health Administration via eCFR",
        "content_markdown": "Treat this document as a focused evidence review: Validate exit-route capacity and permanence before occupancy changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [29 CFR 1910.36 – Design and construction requirements for exit routes](https://www.ecfr.gov/current/title-29/section-1910.36) from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\n- Under 29 CFR 1910, the rule requires that more than two exit routes be available in a workplace if the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would not be able to evacuate safely during an emergency. The research record locates this support at 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)).\n\n- Under 29 CFR 1910, a single exit route is permitted where the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would be able to evacuate safely during an emergency. The research record locates this support at 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths after confirming that the source and deployed context match.\n\n## What the source does not establish\n\nFederal workplace rule; building and fire codes, occupancy, alterations, and authority-having-jurisdiction decisions also govern egress design. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)), which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\n\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nA reviewer should be able to retrace the decision from 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)); 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)) through facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Record what was collected, where, when, by whom, and which system or role it represents.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [29 CFR 1910.36 – Design and construction requirements for exit routes](https://www.ecfr.gov/current/title-29/section-1910.36) — Occupational Safety and Health Administration via eCFR"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
                "url": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Validate exit-route capacity and permanence before occupancy changes",
                        "item": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/#article",
                "identifier": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
                "url": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/",
                "headline": "Validate exit-route capacity and permanence before occupancy changes",
                "description": "Use 29 CFR 1910.36 - Design and construction requirements for exit routes to review this narrow operational decision without extending the source…",
                "abstract": "Use 29 CFR 1910.36 - Design and construction requirements for exit routes to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Validate exit-route capacity and permanence before occupancy changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 29 CFR 1910.36 – Design and construction requirements for exit routes from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\nUnder 29 CFR 1910, the rule requires that more than two exit routes be available in a workplace if the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would not be able to evacuate safely during an emergency. The research record locates this support at 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)).\nUnder 29 CFR 1910, a single exit route is permitted where the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would be able to evacuate safely during an emergency. The research record locates this support at 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths after confirming that the source and deployed context match.\nWhat the source does not establish\nFederal workplace rule; building and fire codes, occupancy, alterations, and authority-having-jurisdiction decisions also govern egress design. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nA reviewer should be able to retrace the decision from 29 CFR 1910.36(b)(2) (eCFR anchor p-1910.36(b)(2)); 29 CFR 1910.36(b)(3) (eCFR anchor p-1910.36(b)(3)) through facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Record what was collected, where, when, by whom, and which system or role it represents.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n29 CFR 1910.36 – Design and construction requirements for exit routes — Occupational Safety and Health Administration via eCFR",
                "datePublished": "2026-08-27T12:12:34+00:00",
                "dateModified": "2026-08-27T13:04:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/validate-exit-route-capacity-and-permanence-before-occupancy-changes/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Validate exit-route capacity and permanence before occupancy changes"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    }
                ],
                "wordCount": 608,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "29 CFR 1910.36 - Design and construction requirements for exit routes",
                    "url": "https://www.ecfr.gov/current/title-29/section-1910.36"
                }
            }
        ]
    }
}