Roof-area feasibility check

What an area factor bundles, and why the margin is the answer that matters

The area factor is doing more work than it looks. It bundles the module’s own footprint with the spacing a real layout needs — walkways, edge setbacks, inter-row gaps on a flat roof — into one figure per kilowatt-peak. That is why it is larger than a datasheet module area alone would suggest, and why a pitched roof packed edge to edge can justify a smaller factor than a ballasted flat-roof layout.

Required area scales in a straight line with the target: double the array, double the roof it needs. The interesting output is therefore not the required area itself but the margin — available minus required. Positive margin is room to grow or room for the layout to breathe; negative margin is the roof saying no, and the pack declares a warning for exactly that case rather than letting the number pass in silence.

A failed check has two honest exits, and only one of them is shrinking the array. The other is challenging the factor: higher-efficiency modules genuinely need less area per kilowatt-peak, and a site-specific layout can beat a generic allowance. What is not honest is quietly lowering the factor until the check passes — the factor must come from a real module and a real layout, not from the answer you want.

The pack also declares the roof-first direction: fix the available area and let the engine run the relation backwards to the largest array the space supports. For many town roofs that reversed number — not the load, not the budget — turns out to be the binding constraint on the whole design.

When this calculation is used

• Immediately after sizing from load or budget, as the first physical test the paper array must pass.
• Screening a property before an installer visit, when the roof’s usable area is a measurement and everything else is still assumption.
• Comparing module choices, where a higher-efficiency module’s smaller area factor can rescue a target the roof otherwise refuses.
• Running roof-first: letting the declared reverse workflow report the largest array the available area supports, before any load arithmetic begins.

Worked example

Test the cluster’s reference design against a real surface: the five kilowatt-peak target from the sizing page, at the pack’s illustrative allowance of six square metres per kilowatt-peak, on a roof offering forty usable square metres.

The engine returns the area the array requires and the margin the roof has left. Here the margin comes back positive — the design fits with room to spare — so the interesting question becomes what the spare area is for: growth, a battery-ready layout, or simply easier maintenance access. A fit this comfortable also means the roof is not the binding constraint; load and budget still are.

Both figures come from the verified engine at load, and this scenario is one of the declared test vectors in the signed pack. A sibling vector declares the opposite case — a larger target on a tighter roof, where the margin goes negative and the pack’s own warning fires instead of letting the shortfall pass unremarked. The check is a screening estimate either way: a surveyed layout, not this page, decides what the roof truly holds.

What each input represents

Assumptions and limits

• One area factor stands in for the whole layout; a real roof with several faces, pitches or obstructions needs the check run face by face.
• Area is the only constraint tested — structural loading, wind uplift, shading and electrical routing are separate questions for a qualified installer.
• The factor already includes spacing, so pairing it with a gross roof footprint double-counts generosity; the available area should be the honest usable figure.
• Fit says nothing about performance: a roof can hold an array that faces the wrong way, and the yield pages in this cluster carry that judgement.

What the guards protect against

• A zero area factor is refused, and the pack ships that refusal as a declared test vector — with no area per kilowatt-peak, every array fits every roof, which is not a check at all.
• The area factor is bounded to the band real module layouts occupy, from a few square metres per kilowatt-peak to the mid-teens; a figure outside it is more likely a unit slip than an exotic module.
• Target size and available area must both be positive, each under a generous ceiling; and a negative margin is deliberately a declared warning rather than a refusal — an over-full roof is a finding to report, not an input error to reject.

Provenance

Rooftop feasibility screening, required area = target array size × reference module area per kilowatt-peak, compared against the available area

Product of the target array size and the reference area factor, returning the required area and the signed margin against the available area, with a declared warning when the requirement exceeds the space; the declared reverse workflow solves the same relation for the largest array a fixed area supports.

Screening and reference material, to be checked against a surveyed layout and a qualified installer or engineer; not a design determination. The signed pack carries its own citation, and the page reports the verification state of the release it mounted.