Answer
Panel count tells a homeowner how many modules are proposed, but not the system’s capacity, annual energy, appearance or bill impact. Explain the module rating, roof placement, modeled production and household demand together. Identify the inverter and battery scope, show assumptions beside the results, and name the checks that can change the final layout.
“Twenty panels” does not tell a homeowner what the array will look like, whether it fits the intended roof area or how the estimate relates to their electricity use. Sales and design teams should give the count a clear meaning rather than expecting the buyer to supply those connections.
This guide is a communication checklist for a preliminary proposal. It does not determine a site’s final engineering design or required approvals.
1. Convert the count into DC capacity
For identical modules:
Array DC capacity in kW = panel count × module nameplate watts ÷ 1,000.
If ratings differ, sum the module watts instead of multiplying by one assumed rating. Identify the exact module model and rating on the proposal, along with the separate inverter AC rating.
For example, 20 hypothetical 400 W modules total 8.0 kW DC; 20 hypothetical 450 W modules total 9.0 kW DC. Neither number is a promise that the system will produce that power continuously, and neither is annual energy. The Australian Government’s solar panel guide explains nameplate rating under standard test conditions and the distinction between power in kW and energy in kWh.
Ask the buyer to identify which number describes the array and which describes production. If the labels are unclear, fix the document rather than treating the confusion as a buyer’s lack of technical knowledge.
2. Show where those panels sit
Use a labeled roof view with the array locations, orientation and visible obstructions. Record imagery source and capture date where available, the model revision, and whether the outline is a preliminary reconstruction or field-verified geometry. A recent screenshot does not establish the underlying imagery date.
Mark proposed roof areas and the constraints still to be checked. Module dimensions, roof shape, access requirements, local setbacks, mounting approach and structural findings can affect how many modules can be installed. Do not calculate required roof area from count alone or present one jurisdiction’s spacing rule as a global design requirement.
Keep the same revision on the visual, equipment schedule and production estimate. If the layout changes, identify which other outputs need review.
3. Explain why equal counts can produce different energy
Two arrays with the same count can have different module ratings and operating conditions. Even if their DC capacity is equal, location, tilt, orientation, shading, losses and inverter configuration can change modeled energy.
Compare estimates with a common output boundary and period, such as first-year AC energy in kWh. List the weather data, geometry and loss assumptions rather than calling one output “more accurate” simply because it is higher. PVWatts identifies site and system inputs and explicitly cautions that its estimates have assumptions and uncertainties. It is a modeling reference, not evidence that a particular SurgePV output is validated or lender-approved.
For a shading discussion, review the shadow analysis workflow and keep material shading assumptions beside the annual estimate.
4. Connect production to household consumption
Show the household consumption source and period beside the modeled production. Note missing months, estimated bills and intended changes such as an EV, heat pump or occupancy change. A historical bill does not by itself establish a future load profile.
In an invented example, 9,000 kWh of modeled annual production divided by 10,000 kWh of household annual consumption gives a 90% annual energy offset. It does not mean 90% self-consumption. If 4,000 kWh of that solar production is used on site and 5,000 kWh is exported, self-consumption is 4,000 ÷ 9,000 = 44.4%, and solar supplies 4,000 ÷ 10,000 = 40% of household consumption. With no storage or other energy source in this simplified example, the household still imports 6,000 kWh.
Those are demonstration quantities, not a site forecast. A bill calculation additionally needs import charges, export credits, fixed charges and the applicable rules. Do not treat every exported kWh as if it avoided the retail import rate.
5. Make equipment boundaries visible
Panel count says nothing about whether the scope includes a battery, backup equipment, inverter changes or electrical upgrades. List what is included, optional, excluded and awaiting review.
Ask the buyer which outcomes matter: daytime load reduction, a future expansion or defined backup loads. Confirm the equipment and switching arrangement needed for those outcomes with the responsible technical team. Do not infer outage supply from a grid-connected array count or a battery’s presence alone.
6. State what site verification can change
Attach a short verification record to the proposal:
| Question | Current evidence | Open action |
|---|---|---|
| Does the array fit? | Dated roof model and module dimensions | Verify geometry and applicable clearances |
| What can shade it? | Observations and modeled obstructions | Check missing or changed obstructions |
| Is the roof suitable? | Available roof records and observations | Responsible structural review where required |
| What electrical work is included? | Available service evidence and equipment scope | Qualified assessment and release |
| What approvals remain? | Named jurisdiction and utility process | Confirm the current requirements and status |
This is a proposed communication record, not a complete survey or a compliance checklist. Give each open action an owner and the event that will close it. A blank status should not turn into a confirmed fact when the proposal is exported.
7. Use the count as a revision reference
Keep a dated version of the buyer-facing proposal. If an array changes from one count to another, explain why and identify the effect on capacity, roof placement, modeled energy and scope. Ask the buyer to compare the changed assumptions rather than simply treating the larger number as the better option.
Before sending, check that the count in the roof visual matches the equipment and modeled configuration. Confirm that annual kWh are labeled as an estimate, financial outputs use the current scope, and the buyer knows which checks remain.
To evaluate how the record is presented, review SurgePV’s generation and financial tool and bring a representative proposal question to a guided demo. Verify the actual output and workflow rather than assuming any particular integration or approval is included.
Frequently asked questions
How do you convert panel count to system size?
For identical modules, multiply the number of panels by the module nameplate watts and divide by 1,000 to obtain DC kilowatts. For mixed ratings, add the individual module ratings. The result is rated power, not annual energy or guaranteed output.
Can two systems with the same panel count produce different energy?
Yes. Module ratings, location, orientation, tilt, shading, losses and inverter configuration can differ. Compare modeled AC energy over the same period with its assumptions, rather than assuming equal counts produce equal kilowatt-hours.
Does matching annual solar production to annual consumption remove the electricity bill?
No. The timing of production and consumption, imports, exports, applicable tariff rules and fixed charges also matter. Annual energy offset alone does not establish self-consumption or a bill saving.
Is a proposal roof image a final installation design?
Not automatically. Label the image with its source, version and verification status. Identify the site, structural, electrical, permitting and utility checks still required before the responsible parties release work.
Sources
Primary research and reference material used for this desk-research article.
