Why a Correct Panel Count Does Not Guarantee a Complete Solar BOM

A correct module count is an input to a solar bill of materials (BOM), not proof that the BOM is complete. The count may reconcile with a drawing while the project still lacks a defined inverter arrangement, mounting interfaces, electrical protection, monitoring equipment, site-specific accessories, or a clear record of which revision procurement is buying.

For installers and EPCs, the safest operating rule is simple: release a BOM only after it can be traced back to a specific design basis and forward to a procurement decision. The National Renewable Energy Laboratory’s solar cost work is a useful reminder that hardware is only one portion of a project’s cost structure. A missing small component, late substitution, or unclear owner can create disproportionate delay even when the module quantity is correct.

The Panel Count Is a Starting Point, Not a Procurement Scope

Panel count matters because it anchors DC capacity, array area, and often the first question a customer asks. It cannot answer the rest of the procurement question alone. Two layouts with the same number of modules can demand different rails, attachments, clamps, wire management, inverter quantities, stringing, disconnect arrangements, protection equipment, and labor planning. Roof type, module dimensions, electrical topology, code requirements, snow or wind context, access routes, and customer-selected options can all change the equipment package.

That is why teams should distinguish three statements that are often collapsed into one green status:

The third statement requires evidence that the first two do not provide. Treating them as interchangeable creates the familiar problem of a “complete” package that begins accumulating exceptions after purchase orders are requested.

Start With a Design Basis Record

A BOM becomes reviewable when it has a stable parent document. Before anyone adds distributor SKUs, write a compact design basis record. It need not be a long report. It must make visible the facts and assumptions that explain why each material category exists.

At a minimum, record the site identifier; drawing revision; array capacity; selected module make and model; array locations; planned inverter and stringing concept; mounting approach; known electrical points of connection; applicable market or authority requirements; and the outstanding questions that could alter equipment. Date the source files. If a survey photograph, customer statement, or remote image informed the design, label it as observed, customer-provided, or planning assumption rather than silently upgrading it to verified fact.

The U.S. Department of Energy’s Solar Energy Technologies Office publishes research resources, but no general guide can validate a particular building, utility, or authority requirement. The responsible project team must apply the correct local design, safety, and approval process. A desk-research article cannot provide project-specific engineering or procurement authorization.

Build the BOM by System Function

Working from function prevents an attractive but incomplete spreadsheet. Organize the initial BOM into groups that a reviewer can challenge independently. The exact breakdown changes by market and project type, yet the following categories create a useful baseline.

Array and mounting components

List modules by manufacturer, model, rating, quantity, and approved substitute policy. Do not assume that another module with a similar rating is a neutral substitution: dimensions, connectors, current characteristics, product approvals, loading, and warranty terms may matter. For mounting, identify the system family, rails or structural members, attachment type, flashings where applicable, clamps, splices, bonding elements, ballast or anchors where relevant, and wire-management components. A count of rails calculated from a layout should be checked against the mounting supplier’s documented design method and the responsible design role’s requirements.

DC electrical scope

Translate strings into a record that can be checked. Include the intended string count and modules per string, conductors and connectors, combiner or transition equipment if used, isolators or disconnects where required, grounding or bonding components, labels, and surge protection where specified. Do not let a generic “electrical miscellaneous” row conceal decisions that may affect approval, safety, or lead time. If conductor sizing or protection is pending engineering review, state that it is pending and block the line from purchase release.

Inverters, AC equipment, and monitoring

Identify inverter model, quantity, compatible accessories, communication hardware, AC isolation and protection components, metering or monitoring devices, and any gateway or network prerequisites. A monitoring line is not automatically a complete monitoring plan. Ask who supplies the internet connection, where equipment is mounted, what permissions are needed, and how commissioning ownership is documented. These questions are especially important when a customer expects a particular dashboard or reporting capability.

Site, safety, and closeout items

Depending on scope, the package may require roof-protection materials, access equipment, signage, rapid shutdown components, fire-safety interfaces, spares, packaging allowances, or documentation deliverables. Do not add such lines as a substitute for a proper site plan; list them only when the project evidence and responsible process support them. Explicitly list exclusions too. “Not included: structural remediation, service upgrade, utility-mandated equipment, or permits unless confirmed” is more useful than letting a blank cell imply inclusion.

Reconcile Three Views Before Release

The strongest quality check compares the layout, electrical narrative, and BOM rather than reviewing each in isolation. A mismatch often becomes visible only when someone asks the same question in three forms.

This is where a connected workflow can help. Solar Designing is positioned by SurgePV as part of a platform that brings layout, DC stringing, BOM generation, and project outputs closer together. That does not remove the need for professional review. It can, however, make it easier for a team to identify the source design and revise outputs together instead of manually copying the same quantities across unrelated documents.

Use Statuses That Mean Something

Avoid a single “BOM complete” checkbox. A small status model gives procurement and project management a more honest view of risk.

• Draft: quantities are generated for planning; design inputs may still move.
• Review required: a named role must resolve a technical, site, commercial, or approval question.
• Approved for pricing: suppliers may quote against the revision, but the order has not been released.
• Approved for purchase: the responsible release authority has accepted the defined scope and exclusions.
• Changed after release: an update has occurred; assess supplier, schedule, and field impact before acting.

The important discipline is not the labels. It is the rule behind them: no line should change status because a person assumes another person has checked it. Give every unresolved issue an owner, due point, and a decision that closes it. A comment such as “confirm roof fasteners” is not an accountable task until it names who confirms, what source is acceptable, and whether the answer can alter the order.

Treat Revisions as Commercial Events

Many BOM problems are not initial omissions. They arise after a design revision is issued but before every downstream document is updated. A moved array can alter module count, rail length, attachment positions, stringing, cable path, inverter loading, and the customer-facing proposal. If the operations system does not make the changed design revision obvious, an earlier BOM can look current simply because its filename lacks a warning.

Use a revision impact checklist whenever the design changes. Ask: did the module model or quantity change; did roof planes, setbacks, access, or obstructions change; did stringing change; did inverter or protection selection change; do mounting quantities need recalculation; do labels, monitoring, or closeout documents change; has a quote or purchase order already been issued; and which owner must approve the new state? Attach the answer to the project record rather than relying on a chat thread.

For material substitutions, capture the reason, requested alternative, data source, compatibility review, cost or schedule effect, and final authorization. “Equivalent” should never mean “looks broadly similar.” The person responsible for the applicable design decision needs enough evidence to determine equivalence in that project context.

A Release Meeting That Is Worth Having

A short, evidence-led release review can replace long messages after an order is already late. Bring the current drawing, design basis, BOM, exception list, and supplier quotation. The reviewer should be able to answer five questions in under ten minutes:

1. Which exact project revision is this order based on?
2. Which lines are confirmed by the design, and which are conditional?
3. Are material selections compatible with the intended electrical and mounting approach?
4. Are exclusions, lead times, substitutions, and owner decisions visible?
5. What event would require a new release or supplier notification?

If the answers are scattered across email, a spreadsheet tab, and a design file, the release process is not yet controlled. The goal is not paperwork for its own sake. It is allowing a person who did not create the first layout to judge whether purchasing is acting on the same project that design intends to deliver.

Frequently Asked Questions

Can a solar proposal use an estimated BOM?

It can use a clearly labeled planning estimate when the team explains what is provisional. It should not portray a preliminary material assumption as a confirmed construction scope. The appropriate disclosure, review stage, and local requirements depend on the project and customer agreement.

What is the most common BOM handoff failure?

The recurring failure is an uncommunicated revision: the drawing changes, but procurement works from a prior export. A revision identifier, impact check, and named release authority reduce that risk more effectively than adding more generic spreadsheet columns.

Does BOM automation replace engineering review?

No. Automation may accelerate quantity generation and make traceability easier, but it cannot assume responsibility for project-specific structural, electrical, code, utility, or site decisions. Those belong to the appropriate responsible roles.

How often should a solar BOM be reviewed?

Review it at the defined release points: after material design inputs are confirmed, before supplier pricing or purchase release, and after any change that could affect scope. The exact cadence should follow the company’s project controls and market requirements.