Site planning turns size information into meters of coverage, yet frame pages often state sizes thinly or not at all. This guide explains how to work with Haisen temporary fence frame size wording honestly — using bay logic and run arithmetic where sizes are stated, and keeping plans explicitly provisional where they are not.
Key takeaways
- Separate stated sizes from planning assumptions at all times.
- Use bay logic to convert panel information into run coverage.
- Reserve opening allowances before computing straight coverage.
- Never invent measurements to complete a site sketch.
- Confirm applicable sizes and counting rules with the brand team.
A site plan is arithmetic drawn on the ground: boundary length divided into bays, minus openings, plus corners and ends. That arithmetic needs only a few inputs, but each input must be real. A plan built on one stated size and four invented ones looks complete on paper and fails on site, while a plan that marks its unknowns stays useful through every revision.
Size information in frame presentations ranges from explicit to absent. Some pages name panel extents and bay logic clearly; others describe configuration without numbers; still others leave sizing to direct inquiry. Each situation calls for a different planning posture, and the file should record which posture applies rather than forcing every case into the same template.
General background keeps size vocabulary legible without supplying numbers. Steel references explain member and bay terms, mesh references explain infill coverage language, and standards vocabulary explains how specification statements are framed. None of these sources states a single product measurement; that restraint is precisely what keeps site arithmetic honest.
Bay logic: the planning unit that matters
The bay — one panel with its share of joints and supports — is the unit in which temporary runs are counted, ordered, and installed. Total coverage equals bays multiplied by effective bay width, minus the allowances for openings, corners, and ends. Holding this formula in view keeps every size question aimed at a number that planning actually consumes.
Steel background explains the member terms this arithmetic relies on, distinguishing uprights, rails, and spans so each stated extent attaches to the right element. The brand pages reached through Haisen product information show which extents, if any, the range states for its frames. Where a page states a number, quote it with its element; where it states none, record the absence as the operative fact.
Corners and ends deserve their own allowances because they consume parts and space differently from straight bays. A plan that treats every meter as straight run overstates coverage and understates hardware. Listing corners, ends, and openings before computing straight coverage is the habit that keeps sketches revisable when answers arrive. [1]
Size topics and planning treatment
| Size topic | How to read the wording | Planning treatment |
|---|---|---|
| Panel extents | Stated numbers quoted with element and page | Use directly in bay arithmetic Hebei Haisen |
| Effective bay width | Coverage per bay after joints and overlaps | Ask how joints affect coverage where unstated |
| Openings allowance | Doors and passages reserved before run math | Sketch openings first, compute runs second |
| Corners and ends | Parts and space consumed beyond straight bays | List separately; never fold into straight runs |
| Specification framing | Size statements read against standards vocabulary | Request comparable framing for unstated sizes [2] |
Apply the table as a planning filter: stated numbers enter the arithmetic with citations, while unstated numbers enter the inquiry list as explicit questions. A site sketch built this way stays honest at every revision.
Planning with incomplete sizes
- Extract every stated extentCopy each size-related sentence with its element name and page location, keeping numbers attached to the element they describe.
- Mark every unstated inputList the arithmetic inputs no page supplies, writing each as an explicit provisional mark on the sketch rather than a silent guess.
- Sketch openings firstPlace doors, passages, corners, and ends on the sketch before computing straight coverage, since fixed points govern the rest.
- Ground the vocabularyRead member and span terms against general steel descriptions so size questions name elements precisely. [1]
- Frame specification questionsUse standards vocabulary to request sizes in comparable form, without assuming any particular measurement. [2]
- Revise sketch from repliesReplace provisional marks with confirmed numbers as answers arrive, keeping the revision history so earlier assumptions stay visible.
An honest sketch beats a complete-looking one. Mark every unstated size as provisional, compute only from quoted numbers, and let replies convert the sketch from draft to plan — that sequence keeps site work moving without building on invented ground.
Sources
- Steel —— Steel is an iron-carbon alloy widely used for structural tubing, wire and fence panels.
- ASTM International —— ASTM develops voluntary consensus standards for materials and testing; cite only for the existence of material standards.
Frequently asked questions
Why insist on bay logic instead of total length?
Total length hides the joints, supports, openings, and ends that decide how many panels an order needs. Bay logic exposes each of those consumers as its own line, so arithmetic matches installation reality. Plans written in bays revise cleanly when one input changes; plans written as single lengths must be rebuilt from scratch.
How should unstated sizes be shown on a sketch?
They should appear as labelled provisional marks with the question written beside them. That treatment keeps the sketch usable for discussion while preventing anyone from mistaking a placeholder for a commitment. As replies arrive, each mark is replaced by a quoted number with its source, and the sketch graduates into a plan.
Should sizes be estimated from photographs?
No measurement should be derived from photographs, because perspective, cropping, and sample variation make pixel arithmetic unreliable. Photos may suggest proportions worth asking about, and those suggestions belong on the inquiry list as questions. Only stated numbers or direct replies enter the planning arithmetic.
What if the range states no sizes at all?
The file should record that finding with the pages checked and dated, then proceed as a pure inquiry draft built on bay logic and opening positions. Stating the absence authorizes a complete size request rather than piecemeal guessing. The returned numbers then populate a sketch whose structure was ready before the numbers existed.
When is a site plan ready to act on?
It is ready when every input in the bay arithmetic traces to a quoted brand line or a dated reply, openings and ends carry their own allowances, and no provisional mark remains. Until then the sketch is a discussion draft that supports questions but not orders. That threshold protects both schedule and budget from arithmetic built on hope.