Dirt Face Logo

Line Post Spacing and Panel Counts

How fixed and proportional line post spacing affect where posts are drawn and how many panels Dirt Face counts on takeoff.

6 min read

Open in app →

Overview

Line post spacing controls how Dirt Face places line posts along each fence section on the canvas. The same setting also changes how panel quantities are calculated when you run takeoff.

Panel count means the number of full-size panels you need to purchase for the job, not the number of gaps between posts.

Where in the app: Designer → Settings tab → Fence settings → Spacing method
Open: Estimates


Fixed vs proportional on the drawing

Both methods use the post spacing from your fence template (for example, 10 ft between line posts). They differ in how each section is divided.

MethodHow posts are placedTypical look
FixedPosts at the maximum spacing from one end; the last bay is shorter if the section does not divide evenlyMost bays are full width; one short bay at the end (or start if inverted). Best when you buy standard-length panels and want most bays at full width.
ProportionalThe section is split into equal bays, none longer than the template spacingAll bays in that section are the same width. Avoids a narrow, awkward-looking last bay, but every bay in that section may need to be cut.

Example: a 32 ft section with 10 ft spacing.

  • Fixed: posts at 10, 20, and 30 ft with a 2 ft remainder bay. Only the last panel in that section needs cutting (unless you invert spacing to move the short bay to the start).
  • Proportional: four bays of 8 ft each. All four panels are cut to 8 ft.

The number of line posts is the same for both methods. Only their positions along the section change.


How panel counts are calculated

Takeoff uses the spacing method when it totals panels for components that reference totalPanels in the fence template.

Fixed spacing (fewer panels when offcuts can be reused)

For each fixed-spacing section, Dirt Face counts:

  1. One full panel for each full-width bay (floor(section length ÷ post spacing)).
  2. One leftover bay per section when the length does not divide evenly (the short remainder at the end or start).

Leftover bays from all fixed sections are then combined. Dirt Face cuts those bays from shared panels and reuses the offcut when it is long enough for another leftover bay on the same job. Each cut also reserves a small allowance for kerf and trim (2 in on imperial jobs, 5 cm on metric jobs).

This matches how many installers order material: use full panels wherever possible, cut the short bays from extra panels, and use remnants on other short bays when they fit.

Example with 10 ft post spacing and two sections:

Section lengthFull baysLeftover bay
42 ft4 × 10 ft2 ft
53 ft5 × 10 ft3 ft

Fixed panel count: 10 panels (9 full bays + 1 panel for the 2 ft and 3 ft leftovers, which share one 10 ft panel).

Proportional spacing (more panels, no offcut reuse)

Proportional spacing is calculated per section. Every bay in that section may be a non-standard length, so offcuts from one cut are treated as waste and are not applied to other sections.

For each proportional section:

panels = round up (section length ÷ post spacing)

Example with the same two sections and 10 ft spacing:

Section lengthCalculationPanels
42 ftceil(42 ÷ 10) = 55
53 ftceil(53 ÷ 10) = 66

Proportional panel count: 11 panels.


Side-by-side example

Same job: 42 ft section + 53 ft section, 10 ft post spacing, panels sold in 10 ft lengths.

FixedProportional
Panel count1011
Full-width bays90 (all bays are cut to equal width within each section)
Offcut reuseYes, across fixed sectionsNo
Cuts per sectionUsually one short bayOften every bay in the section

When leftover bays are large or do not fit together on one panel, fixed spacing can still require more than the simple total-length formula would suggest. Dirt Face checks each leftover bay against available offcut length rather than assuming all remnants combine perfectly.


Impact on materials and cost

FixedProportional
Usually one partial panel per section (the short remainder bay)Every panel in the section may be cut to a non-standard width
Offcuts from fixed sections can be reused on other short bays when they fitOffcuts are treated as waste and are not reused across sections
Lower panel count when remnants combine (see examples above)Higher panel count because each section is rounded up independently

Impact on installation time

FixedProportional
Fewer cuts overall; most panels install at full widthEvery panel in the section typically requires a cut
Faster installation in the fieldMore cutting and fitting labor
Short remainder bay at one end of each sectionMore uniform bay widths along the section

Proportional spacing often looks cleaner on the finished fence even though it adds labor and material compared to fixed spacing.


Per-section override

The global spacing method applies to every section by default. You can override a single section:

Where in the app: Select a fence section on the canvas → upper toolbar → spacing options
Open: Estimates

  • A section set to proportional is counted with proportional panel math and does not contribute its offcuts to the fixed-spacing pool.
  • A section set to fixed under a proportional global setting is counted with fixed math and can share offcuts with other fixed sections.

Fixed spacing also supports invert, which moves the short remainder bay from the end of the section to the start. Inverting affects layout only; panel count stays the same.


When to use each method

Choose fixed whenChoose proportional when
You buy standard-length panels and reuse cutoffsAppearance matters more than material count
You want takeoff to reflect offcut reuseEvery bay in a section should look the same width
Most bays should install at full panel widthYou accept more cuts and higher panel counts

Post spacing itself comes from the fence template, not from the designer spacing toggle.

Where in the app: Sidebar → Fence → My Fences → template wizard → Fence step
Open: Fence Builder

See Template step: Fence for post spacing and other template fields.