Prescriptive vs performance-based codes

A prescriptive requirement is a recipe: this thickness, this spacing, this rating. It is checkable by inspection, predictable in cost, and demands no analysis — at the price of forbidding better solutions it never imagined. A performance requirement states the outcome — the structure withstands these loads, the occupants evacuate before untenable conditions — and leaves the method open, admitting innovation at the price of a verification burden: someone must demonstrate, by analysis and evidence, that the chosen solution performs, and someone with authority must accept the demonstration.

Modern systems are deliberate hybrids, typically structured as mandatory performance requirements paired with deemed-to-satisfy prescriptive routes — follow the recipe and compliance is presumed; depart from it and carry the proof. Fire engineering lives on the performance route almost everywhere; Kazakhstan's 2015 reform rebuilt its whole construction base on this pattern; the EU's regulation architecture is the same idea at the legislative level.

The failure modes mirror the philosophies. Prescriptive: recipes applied outside the situations they encoded. Performance: the freedom taken without the burden — alternative solutions asserted rather than demonstrated, arriving at review with innovation and no evidence, which converts the flexibility back into a rejection.