Bleacher configurator rules: net seats, units for a seat target and site fit
The rules a bleacher configurator needs: net seats per size, units for a seat target, accessories per model and a site fit check including stairs.
Short answer: a bleacher configurator needs four rules: a seating table per model, row count and length; a sizer that turns a seat target into a number of units; accessory rules per model; and a site check that lays units, stairs and access against the space available. According to its library page, our example configurator shows models with net seat counts, a seat-target sizer, accessories and a site fit check with sample values; this guide proposes how you would write the rules behind them for your own bleachers.
Which parameters does a bleacher have?
The "Live in this demo" list of the bleacher configurator names the inputs [1]. The right-hand column is our proposal for how they should depend on each other in a project; it does not describe the demo's internal logic.
| Parameter | In the demo | Proposed dependency |
|---|---|---|
| Model | standard, raised, low-rise | sets allowed rows, lengths and accessories |
| Rows and length | per model, with net seat counts | only sizes from your table; seats read from the table, not a formula |
| Seat target | sizer for the units needed | gives units, surplus and total length |
| Frame, guardrail, footboards | options | allowed or blocked per model |
| Accessories | mud sills, rubber bumpers, transport wheels | depend on model and ground |
| Accessible layout, end stairs | options | change seats, depth or length |
| Site | fit check with outline | length and depth including stairs and access |
| Units | ft/in and mm | stored once in mm, converted for display |
Why a table rather than a formula?
It is tempting to calculate seats as length divided by seat width times rows. For real bleachers that rarely holds: centre aisles, stair runs, end rails and special spaces take width, and many makers offer fixed sizes with fixed seat counts. We therefore propose reading net seats from your size table. Each row holds model, rows, length, seats, depth and, if available, your part number. Sizes not in the table cannot be selected. Your table stays the single source, and the configurator cannot contradict it.
How does an audience size become a bleacher?
The sizer is the heart of a bleacher configurator, because the enquiry almost always starts with a number. We propose this rule: units needed = seat target divided by seats per unit, rounded up. The configurator should also show the surplus and the total length.
A worked example with freely chosen numbers that do not come from the demo: the target is 300 seats. A size with 84 seats gives 300 / 84 = 3.57, so 4 units with 336 seats and 36 spare. A larger size with 96 seats gives 3 units with 288 seats, 12 short, or 4 units with 384. Which is better depends on space, budget and use. A good configurator therefore does not give just one answer but shows the alternatives, for example with a note such as "3 units of the larger size leave you 12 seats short".
How are accessible spaces and stairs handled?
Accessible spaces change the bleacher: depending on the design, seats are removed or an area in front of the first row is kept clear, which adds depth. End stairs lengthen the layout. Both should feed into the seat count and the site check, not just appear on the model.
How many accessible spaces are needed depends on regulations and on the operator. We propose that the configurator uses the figure you as the manufacturer specify and labels it as your example or default value. It is no check against regulations; manufacturer and operator remain responsible for that.
How do you check the site?
The demo checks the site with an outline [1]. For a project we propose this rule: length needed = sum of unit lengths + gaps between units + stairs or access at the ends. Depth needed = depth of the chosen size + any accessible area. Both are compared with the length and depth the buyer enters. The result should appear twice: as a green or red outline on the model and as a sentence in the summary, such as "needs 34.5 × 6.2 m, available 30 × 8 m: not enough length". The numbers in that sentence are made up for illustration.
Gaps between units, stair widths and escape routes are set by you and the operator. The configurator uses your values as an example rule and says so.
Store one unit system, show two
If you supply markets that use feet and inches, you need both systems. The demo switches between ft/in and mm [1]. We recommend storing every value once in millimetres and converting only for display, enquiry and PDF. That way there is no second table to fall out of date.
What data do you provide?
For a configurator with your bleachers we need your size table with seats and dimensions per model, the allowed combinations of frame, guardrail and footboards, your accessories mapped to models, your values for accessible spaces, stairs and gaps, and the notes you want to show on set-up and approvals.
What comes out at the end?
According to the list, the demo lets you copy the enquiry text and download a PDF [1]. For a project we propose that text and PDF hold the same lines in the same order: model, size, units, net seats, accessories, site check result, location and dates for hire, and contact details. How that enquiry reaches sales or the hire desk, and what sits behind it technically, is covered in building configurators for trade fair and event structures.
Example configurator · fictional product
Bleacher configurator
Plan a bleacher: three models, rows and length with seat counts, a sizer for the seat target, guardrails and accessories – with a site fit check and a PDF enquiry.
Who such a configurator is for is covered in bleacher configurator for manufacturers and rental companies. For the project process, see 3D configurator development.
Send us your size table – we show which rules follow from it.
Frequently asked questions
Are the demo's seat counts binding?
No. They are simplified sample values of a fictional product. In a project your table applies.
Can it plan seating around a corner or on two sides?
That is a project requirement. The rule stays the same; the site check becomes more involved. We agree beforehand which arrangements you offer.
Does it check whether an approval is needed?
No. It can show a note that you write. Manufacturer and operator settle the question.
Sources
- Modelwright library, bleacher configurator, "Live in this demo" list and sample-values note, read 14 November 2026: modelwright.de/en/library/bleacher-configurator/


