Stair layout with IRC reference check

A pre-flight against commonly-cited bands — not a ruling under the code

The layout begins as a division. The rise is converted to inches and divided by a target riser of about seven inches — the aim the pack declares — then rounded to the nearest whole count, because a stair cannot own a fraction of a riser. The actual riser height is the rise shared evenly across that count, and the tread count is one fewer, the upper floor serving as the last walking surface.

From the counts, the footprint. Treads multiplied by the tread depth give the total run — the floor space the stair claims — and the stringer length is the diagonal across rise and run, the first figure to hold against the lumber rack. A deep tread buys comfort at the price of plan area; the arithmetic makes the trade visible before any framing does.

Then come the bands. The pack declares reference values mirroring the commonly-cited residential limits: a window the riser height should sit inside, a floor beneath which the tread depth should not fall, and a comfort band for the old carpenter’s sum of twice the riser plus the tread. Each check is a warning with its own message, and each message ends the same way: verify with the governing code.

Failing a band does not silence the calculator. A layout outside the limits is still computed in full — counts, heights, run and diagonal — because a failing geometry is exactly the one worth inspecting: the numbers show which lever to move, whether that is a deeper tread, a different count, or a longer run than the plan allows.

And none of it is the IRC. The pack’s own description calls this a reference model whose thresholds mirror commonly-cited bands, and that honesty is the page’s too: adopted editions differ, local amendments differ more, and dimensions are only one chapter of what a code asks of a stair. Treat a clean result as permission to keep designing, not permission to build.

When this calculation is used

• Testing whether a measured floor-to-floor rise can yield a comfortable straight stair before any design work begins.
• Sanity-checking a sketch or an existing stair by reproducing its counts from the rise and tread depth.
• Seeing what a deeper or shallower tread does to the run, the diagonal, and the comfort sum at a fixed rise.
• Estimating the stringer diagonal early enough to influence what stock gets ordered.

Worked example

The pack’s golden vectors walk one stair three ways: an eight-foot rise on the default tread, the same tread under a nine-foot rise, and the eight-foot rise again over a much shallower tread.

The eight-foot rise divides into fourteen risers a little under seven inches each, thirteen treads, a run just short of twelve feet and a stringer diagonal a little over fourteen feet — and the pack records it as compliant with the declared bands. The nine-foot companion lands fifteen risers and a comfort sum the pack’s own vector records as drifting past its band; the shallow-tread companion keeps the same riser height but falls below the declared tread minimum. One arithmetic, three verdicts — all carried by the warnings, not the numbers.

Every figure here is computed by the certified engine at the moment the calculator loads and checked against the signed pack’s declared test vectors — the page holds no stored answers. Notice that the two failing layouts still return their complete geometry: in this model the warnings carry the verdict, and the verdict itself always defers to the governing code.

What each input represents

Assumptions and limits

• The stair is a single straight run from floor to floor; landings, winders and turns divide the problem into separate flights, each with its own rise.
• The bands are commonly-cited reference values the pack declares, mirrored from a widely used residential model code — they are not the adopted code of any jurisdiction, and local amendments routinely differ.
• Dimensions are all this model sees: nosing, headroom, width, guards, handrails and landing requirements are chapters of the real code it never opens.
• Nothing here is structural: stringer section, span and support belong to the construction documents and the professionals responsible.

What the guards protect against

• The rise must be strictly positive, and the pack ships the zero-rise refusal as a declared test vector: a stair with no height to climb is a measurement that never happened, and the engine refuses it rather than laying out an imaginary flight.
• Layouts outside the bands are computed, never refused — both of the pack’s declared failing vectors return their full counts, heights, run and diagonal, with the failure recorded as a warning, so a bad stair is named rather than hidden.
• The bands are checked independently: one declared vector fails only the comfort sum while its riser height sits inside the riser window and its tread clears the minimum — evidence that passing one band never certifies the others.

Provenance

Commonly-cited IRC residential stair bands (rule-of-thumb reference model)

Rise converted to inches and divided by a target riser of about seven inches, rounded to a whole count held at one or more; riser height as the rise over that count; treads as one fewer; run as treads times tread depth; stringer as the diagonal of rise and run; warnings raised against the pack’s declared riser, tread and comfort-sum bands.

Educational reference only, never building-code advice: the code that governs a stair is your locally adopted code as amended, read and enforced by the authority having jurisdiction, and this model claims only to mirror commonly-cited bands. The signed pack carries its own citation, and the page reports the verification state of the release it mounted.