Why are common path and travel distance regulated separately?
Travel distance and common path of egress travel regulate two different evacuation risks. Travel distance limits the total time an occupant might be exposed to fire conditions while reaching an exit. Common path limits the portion of that travel during which the occupant has no choice of direction — if a fire blocks the only path, the occupant has to turn around and retrace their steps, increasing exposure. The two limits are independent: a route can satisfy total travel distance and still violate common path, or vice versa. Both must be satisfied for the design to comply. IBC Section 1006.2.1 sets common path; Section 1017.2 sets total travel distance. NFPA 101 places both in the occupancy chapter for each use. Common path is typically a much shorter limit (75 to 100 ft for most occupancies) because the risk is concentrated — the occupant cannot choose around the hazard.
How is common path of egress travel measured?
Common path of egress travel starts at the most remote point in an occupied space and runs along the natural path of travel until it reaches a point where the occupant has access to two distinct paths to two different exits. From that decision point onward the travel is no longer common path, even though it still contributes to total travel distance. Measurement uses the same path-following rules as travel distance — natural path, around fixed obstructions, one-foot diagonal at corners. The decision point is the location where two independent egress paths diverge; it is not simply the location where two doors are visible. If both doors lead through the same corridor to the same exit, the common path continues until the corridor branches. The most common error in common-path measurement is calling the entrance to a corridor the decision point when both ends of the corridor actually lead to exits that are remote from each other; in that case the entrance to the corridor is the true decision point and the common path ends there.
What are the common path limits by occupancy?
IBC Section 1006.2.1 sets common path of egress travel by occupancy. Unsprinklered: A, B, E, F, M, S, U at 75 ft; H-1, H-2, H-3 at 25 ft; H-4 at 75 ft; H-5 at 75 ft; I-2, I-3, I-4 per occupancy chapter; R at 75 ft. Sprinklered: A, B, E, F, M, S, U at 100 ft (B and F-2 may extend to 125 ft with sprinklers + voice evacuation in some editions); H-1, H-2 at 25 ft; H-3, H-4, H-5 at 100 ft; R at 125 ft for R-2 (75 ft for other R subgroups). High-hazard occupancies have shorter limits because the consequence of fire is more severe. Educational and assembly occupancies allow longer common paths where sprinklers are present, recognising that the population can be expected to respond to alarms quickly. For storage and warehouse, common path of travel must respect both the IBC limit and any additional limits from the rack-storage provisions, with the more restrictive controlling.
How do common path and dead-end corridor relate?
A dead-end corridor is a corridor that does not lead to an exit, requiring an occupant who enters it to retrace their steps. Dead-end limits (IBC Section 1020.5) and common path limits are both about portions of the egress where the occupant has no choice. A dead-end is always a common path violation if it extends beyond the common path limit, but a common path violation need not be a dead-end. For example, a long single-direction corridor that eventually opens into a lobby with two exits has zero dead-end but a long common path. Conversely, a 15-ft stub corridor leading to a single office has a 15-ft dead-end (within most limits) and a common path equal to the path from the back of the office to the corridor entry plus the 15 ft. Both limits apply, and both must be checked. The practical advice is to look at every corridor stub, every single-door-to-corridor room, and every exit access route and ask: how far does the occupant travel before having a real choice?
What design changes resolve a common path problem?
When a design exceeds common path, three remedies are commonly used. First, add a second exit access door from the affected space so the occupant has two doors to choose from immediately upon leaving the work area. Second, add a second corridor or route so the long single-direction corridor branches earlier into two paths leading to different exits. Third, reduce the depth of the space so the most remote point is closer to the decision point. Adding sprinklers to take advantage of the sprinklered allowance (75 ft → 100 ft) is occasionally used but is a poor remedy on its own because the cost and disruption are high relative to the common-path benefit. For existing buildings being renovated, sprinklering is sometimes the only practical option because adding doors or corridors is disruptive. Posted evacuation plans should clearly show the decision point and the alternative paths so occupants understand they have options as soon as they reach a corridor intersection.
How should common path appear on the posted evacuation plan?
Posted plans normally do not label distances in feet, but they should clearly show that occupants have a choice as soon as they leave the work area. Primary routes are drawn from each major occupied area to the nearest exit with solid green arrows. Secondary routes are drawn as dashed green lines, so the occupant immediately sees the alternative when the primary is unavailable. Decision points (corridor intersections, lobbies) should be drawn cleanly so the eye is drawn to the branching. Long common-path routes (a long corridor before any decision) should be evaluated to confirm the layout meets the code; if it does not, the posted plan cannot fix the design, but it can highlight the route so occupants understand the path before an emergency. EvacPlan Generator (www.evacplangenerator.com) lets designers draw primary and dashed secondary routes, place arrowheads in the correct direction and add text annotations at decision points — producing posted plans that visually emphasise occupant choice and route alternatives at every decision in the egress system.
How do you document common path compliance in the code analysis?
The code analysis for a project should explicitly document common path of egress travel for each significant space, just as it documents travel distance, dead-end length and required egress width. The documentation typically takes the form of a tabulation: room or area, most remote point, decision point, common path distance, applicable limit, compliance status. For a multi-story building this can be a tabulation per floor, with a representative path drawn on the floor plan and the distance noted. AHJs increasingly expect this tabulation as part of the code analysis sheet, not just as a verbal claim in the project narrative. The posted evacuation plan is a downstream product of the code analysis; if common path compliance is documented and the posted plan reflects the documented paths, the building has the strongest possible defense when inspected. The same analytic approach — measure, tabulate, document, then post — should be repeated whenever the building changes through renovation, tenant fit-out or space repurposing.