Workspace
The calculator's own fields, action and results arrive with the verified pack when you load it. Nothing is computed in this page.
Turn a fence line into an order: sections rounded up from the run and spacing, posts as one more than the sections, rails per section, and post-set concrete by the bag.
The calculator's own fields, action and results arrive with the verified pack when you load it. Nothing is computed in this page.
Sections come first: the run divided by the post spacing, rounded up, because a fence cannot end mid-air and a partial span still needs a whole panel’s worth of material. The exact, unrounded spans figure is reported beside the count, and the gap between the two is the short bay at the end of the walk — already paid for, worth knowing about before the panels are cut.
Posts are the sections plus the one that closes the line. It is the figure people undercount by exactly one when they order from memory, and it is the primary answer here because everything set in concrete flows from it.
Rails multiply the sections, and how many run through each section is a style decision the reader supplies: the default expresses a plain rail fence, and a taller or panelled design carries its own figure. The rail count never sees the posts — only the bays between them.
Concrete arrives as bags per post, another input rather than a rule: the default sets each post in a single bag, a heavier gate line earns more, and a driven or gravel-set run can enter none at all. The bag total simply repeats the post count that many times.
The post spacing itself is the reader’s to own. The default is the pack’s shipped figure; panel widths, wind exposure and gate positions all pull it around, and a bent line is better run leg by leg, because a corner interrupts the rhythm and restarts the count.
The pack’s golden vector: a run of one hundred feet at the default spacing, the default pair of rails in each section and a single bag under every post — beside a companion vector whose shorter run refuses to divide evenly, so the rounding has work to do.
In both vectors the post count sits exactly one above the section count — the closing post at the end of the walk — and with a single bag per post the concrete order simply repeats the post figure. In the companion vector the exact spans figure falls short of the rounded section count: that gap is the short final bay the order has already bought.
Each figure on this page is produced live by the certified engine and checked against the signed pack’s declared test vectors when the calculator loads; nothing here is a stored answer. Set the post spacing to zero and the engine refuses rather than divide by it — the pack declares that refusal as a vector.
The run of the fence line, in feet. A boundary with corners or gates is better entered leg by leg, each straight run with its own count, than summed into one figure the rhythm never actually walks.
The distance from post to post, in feet. The default is the pack’s shipped figure for an ordinary run; panel width and site exposure decide the real one, and every count on the page divides by it.
How many horizontal rails cross each bay. A style input, not a rule: the default suits a plain rail fence, taller designs carry more, and a panel system that brings its own rails can enter none.
How many bags of post-set concrete each post is bedded in. The default sets one bag per post; enter more for heavy or gate posts, or none for posts driven or set in gravel.
Standard fence run take-off arithmetic (spans-plus-one convention)
Sections as the run over the post spacing rounded up; posts as one more than the sections; rails and concrete bags as per-section and per-post multiples; the exact spans figure reported unrounded alongside.
Quantity reference to be verified against the site and the products actually ordered; post embedment, wind loading and boundary positions are never determined here. The signed pack carries its own citation, and the page reports the verification state of the release it mounted.