Sliding gate run-back, slope and quantity rules in a fence configurator
The rules a fence and gate configurator needs: cantilever gate run-back, stepped or raked panels on slopes, ground gaps, and panel and post counts.
Short answer: a fence and gate configurator rests on three rule sets. Run-back: does a sliding gate have a long enough straight, clear stretch beside the opening? Terrain: are panels stepped or raked on the slope, and up to what gradient? Quantities: how many panels, cut panels and posts does the layout need? Each can be written as a formula or a limit, and our example configurator runs all three with example values.
How should a configurator check sliding gate run-back?
A cantilever sliding gate carries a counterbalance tail behind the leaf and slides sideways behind the fence as it opens, so it needs a straight, unobstructed run-back. The example rule in our demo is:
- Counterbalance tail = the larger of 1.5 m and 45 % of the clear gate width
- Run-back needed = clear width + tail + a 300 mm margin
Worked example with the demo's values: a 6.00 m clear opening gives a tail of 2.70 m (45 % of 6.00 m, which is more than 1.5 m), so the gate needs 6.00 + 2.70 + 0.30 = 9.00 m of run-back. If the fence run ends at a corner before that, or a tree or wall stands in the way, the run-back zone on the ground turns red and the check states the length needed, the length free and the shortfall.
When run-back is blocked, the configurator offers one suggestion with an Apply button: run back to the other side, switch to a tracked sliding gate (which needs less run-back), or use a double swing gate (which needs none). If the buyer opens the gate anyway, the leaf slides over its carriages and stops at the obstacle, so the problem is visible rather than described.
We checked the run-back arithmetic by hand in 7 of 7 cases, and the "other side" suggestion turned the check green in the test.
How are slopes handled?
On sloping ground a fence is installed either stepped (level panels, steps at the posts) or raked (panels follow the ground). Each fence type in the demo has its own raked limit:
- Mesh panels: raked up to 8 %; above that the installation falls back to stepped, with a message.
- Palisade and vertical bar: raked up to 15 %.
- Aluminium slats: stepped only.
The step per panel and the raked limit are shown live. Slope can be set from −15 % to +15 % along the gate run. The gate leaf itself stays level, so a ground gap opens at the low end; the configurator shows it and warns from 200 mm that ground levelling at the gate should be planned. These are example rules: which installation your system allows is your decision.
How are quantities counted?
From the fence line, the post spacing and the gate position, the configurator counts live: fence length, panels including cut panels (shortened panels at the end of a run) and posts, gate posts included. On the default L-shaped site the demo shows 44.6 m, 19 panels of which 3 are cut, and 24 posts; we recounted this by hand and it matched.
For a real installation that count is the start of a bill of materials. With your part numbers, post lengths per height, fixings and gate hardware it becomes a list your estimators can price. That step is not in the demo; it is something we would build in a project.
Which inputs feed the rules?
| Input | Example values | What it drives |
|---|---|---|
| Fence type | Twin-wire mesh, welded mesh with V-beams, palisade, vertical bar, aluminium slats | Height list, post spacing, slope rule, toppings |
| Height | From a list per type, e.g. 830 to 2,430 mm for mesh panels | Only listed heights can be chosen |
| Posts | Spacing per type; rectangular, square or round; concreted in or base plate | Panel count |
| Fence line | Straight, L, U, all round, or up to 8 runs | Length, corners, run-back |
| Gate | Single or double swing, cantilever, tracked, none | Width range per type; accessories only with a gate |
| Obstacle | None, tree or wall, side and distance | Limits run-back or swing area |
Further example rules: the closing-edge strip and signal lamp need an operator first, and all gate accessories are shown as icons only, with no claim about function or safety. Spikes are available for palisade and vertical bar; slats take no topping or an outrigger only. A pedestrian gate with a 1.00 m clear width sits on the side without run-back. Out-of-range entries are adjusted with a message, for example a gate width above the range of the chosen gate type.
What comes out at the end?
The review step lists every input and every check. The enquiry text carries the same rows, and the three-page PDF adds a gate view, a plan with the run-back zone and a site view. In the demo, text and PDF are created in the browser only; nothing is sent.
Example configurator · fictional product
Fence & gate configurator
Plan fencing and a gate for a commercial or industrial site: draw the fence line, pick the gate and see on the ground whether the sliding gate's run-back is clear.
Try it in the fence and gate configurator. Who such a configurator is for is covered in fence and gate configurator software, and the technical build (geometry, opening animation, phones) in implementing door, gate and window configurators. For a project of your own, see custom 3D configurator development.
Frequently asked questions
Are these run-back values universal?
No. They are example values in this demo. In a project, the values of your own gate ranges apply.
Can it size foundations?
It can show foundation rules you give it as quantities or notes. It does not replace a structural design.
How many runs can a layout have?
Up to eight in the demo. In a project the limit follows your typical sites.
Sources
- Modelwright library, fence and gate configurator, "Live in this demo" list, read 14 November 2026: modelwright.de/en/library/fence-gate-configurator/


