Quick Answer
A solar team should label an output by what its inputs can support: a screening scenario explores a possibility, a proposal supports a commercial conversation with stated assumptions, and a technical release requires the evidence and review appropriate to its intended use. A polished drawing does not raise its confidence level.
A solar layout becomes more useful when its limits are visible. A team can responsibly use a preliminary model to decide whether a lead deserves a survey, but the same model may be unsuitable for equipment ordering or a construction instruction. The difference is not the rendering quality. It is the evidence behind the output, the assumptions still open, and the review completed before release.
This desk-research guide gives installers and EPCs a practical way to label that difference. It does not determine a project’s engineering, safety, code, utility, contractual, or financial position. Local requirements, qualified professionals, manufacturer instructions, site conditions, and the intended use of a document always control.
Direct Answer
Assign a confidence level to every customer or project-facing solar output. State the purpose of the output, the evidence used, the assumptions that can change it, and the review still required. Do not let an indicative model quietly become a procurement, permit, or construction decision.
Why Solar Teams Need a Confidence Label
Many project mistakes start with a reasonable early output used for an unreasonable later purpose. A salesperson may need a fast scenario to discuss roof area and an approximate system concept. A designer may then inherit that scenario as if it were a survey-confirmed scope. Procurement may receive a bill of materials whose layout has changed since the estimate. On site, the crew discovers an obstruction, a service limitation, or an access condition that was never verified.
None of those steps means the early work was useless. Early work is valuable when it is treated as early work. The problem is the missing transition between “useful to explore” and “safe to rely on.” A confidence label makes the transition explicit.
The U.S. National Renewable Energy Laboratory (NREL) describes PVWatts as an estimator of energy production and value for grid-connected PV systems. Its own documentation identifies inputs, assumptions, and model limits. That is the right mental model for commercial teams as well: a result comes from defined inputs and should be read in the context those inputs allow. A model is not field verification simply because it produces a number.
Use a label that a customer, designer, purchaser, and project manager can interpret without a private conversation. The point is not to create a new approval ritual. It is to prevent a document from carrying more authority than its record supports.
The Three Confidence Levels That Work in Practice
The following framework is deliberately simple. Teams can add local stages, but each level should have a clear permitted use and a clear boundary.
| Level | Typical purpose | Evidence usually available | What must remain visible | Not suitable for |
|---|---|---|---|---|
| Screening scenario | Qualify an opportunity or frame a first discussion | Address, customer description, available imagery, broad consumption information | Roof, electrical, tariff, access, and authority assumptions | Construction, procurement, permit submission |
| Proposal basis | Support a commercial option and explain the scope being discussed | Current bills or interval data where relevant, customer requirements, preliminary site information, selected equipment assumptions | Site findings still pending, scope exclusions, financial assumptions, change triggers | Final technical release unless the record meets that purpose |
| Release-ready package | Support the defined technical, purchasing, permitting, or field decision | Evidence and reviews required for that particular release | Revision number, approved deviations, remaining controlled conditions | Decisions outside the package’s stated scope |
The names are less important than the behavior they produce. “Preliminary” can be a useful label, but only if a reader can tell which inputs are preliminary and what must happen next. “Final” is often too broad. A drawing can be final for a sales meeting while not being final for a construction crew. Describe the purpose rather than relying on one loaded word.
Level One: Screening Is for Direction, Not Commitment
A screening scenario answers questions such as: Is the available roof area likely to be worth further work? Does the customer’s stated objective appear compatible with PV? What evidence should be requested before preparing a proposal? It may use public imagery, a rough load description, or a customer-provided annual bill.
At this stage, write assumptions where the reader can see them. For example: roof dimensions are estimated from imagery; shading has not been field-verified; annual consumption is based on one supplied bill; electrical service capacity is unknown; local authority requirements are not assessed. Those statements are not defensive filler. They tell the next person exactly where confirmation creates value.
Avoid false precision. A system size shown to two decimal places can imply a level of certainty that does not exist. Round a screening output appropriately, name it as indicative, and state the condition that could materially change it. If a planned re-roof, tenant change, unusual operating load, or export restriction is already known, surface it before a customer mistake becomes an internal rush.
Level Two: A Proposal Has to Explain Its Basis
A proposal can be more developed than a screen without being a construction package. It may combine a preliminary layout, a selected commercial configuration, production modeling, a financial scenario, and an explanation of scope. Its job is to help a buyer compare an option and decide whether to proceed, not to conceal every remaining condition.
For energy estimates, track the weather-data source, modeled losses, orientation, shading treatment, degradation assumption where used, consumption basis, tariff treatment, and whether export or storage behavior was modeled. NREL’s Best Practices in PV System Operations and Maintenance is not a proposal template, but it reinforces the larger discipline: operational outcomes depend on technical details, records, and defined responsibilities. A proposal should not collapse those details into an unconditional promise.
The proposal basis should also identify commercial assumptions. Is the price contingent on a survey? Is an electrical upgrade excluded? Does a quote use a particular equipment availability assumption? Does the economics view use a stated utility rate and escalation scenario? A reader should not have to inspect internal notes to find the variables that could change the decision.
Keep Design Inputs and Proposal Outputs Connected
See how SurgePV brings solar design, shadow analysis, generation and financial modeling, and customer-facing proposals into one connected workflow while your team retains responsibility for project review.
Book a DemoUse an active project question in a live walkthrough.
Level Three: Release-Ready Means Fit for a Named Decision
Release-ready should never mean “everything is known forever.” It means the record is sufficient for a named decision under the organisation’s process and applicable requirements. A procurement release may require a current bill of materials, equipment identifiers, quantities, approved substitutions, revision control, and a check that design changes have reached purchasing. A permit release may require a different evidence set. A field release may depend on survey results, access planning, safety documentation, and technical review.
The release note should name its audience and purpose. “Issued for procurement, revision C” says more than “approved.” It creates a useful question: what happens if an item is substituted, a roof condition differs, or a utility instruction changes? Define the change path before the change arrives.
Build the Evidence Record Before You Build the Label
A confidence system fails when labels are assigned from memory. Keep a compact evidence record with every material output. It does not need to be a large report. A structured set of fields is enough when it answers the right questions.
| Record field | Example | Why it protects the project |
|---|---|---|
| Intended decision | “Decide whether to schedule a site survey” | Prevents a screen from being mistaken for a release |
| Source and date | “Customer bill, billing period stated on document” | Shows whether the input is identifiable and current |
| Status | Confirmed, assumption, or required before release | Stops silent substitution of assumptions for facts |
| Material impact | “May change inverter selection” | Focuses effort on decisions that matter |
| Owner and due date | “Site assessor to verify before technical release” | Turns a gap into a work item |
| Revision link | “Proposal v2 uses layout revision B” | Makes downstream updates traceable |
The distinction between confirmed and assumed evidence deserves care. “Confirmed” does not mean universally true; it means supported enough for the stated decision by an identifiable source. A current electricity bill can confirm billed consumption for its period, but it may not confirm future operating loads. A survey photograph can document a visible condition, but it may not settle a structural question. Keep the claim proportionate to the evidence.
Decide What Can Change the Output
Not every missing detail deserves the same priority. Teams should identify change triggers: conditions likely to alter scope, price, equipment, performance modeling, schedule, safety planning, compliance, or customer expectations. The following questions help sort them.
- Would this item change whether the opportunity should proceed?
- Could it change the proposed system configuration or material list?
- Could it change an estimate, tariff treatment, or savings scenario?
- Does it affect a local requirement, utility process, or qualified review?
- Does it need field confirmation before a crew can act?
If the answer is yes, show the condition in the proposal or release record and assign it. A vague “subject to survey” note may be legally familiar, but it does not direct the next action. “Verify service rating before final inverter selection; owner: technical survey; required before electrical release” is useful because it describes both risk and route.
Use Review Gates That Match the Consequence
The appropriate reviewer depends on the output and the risk, not on a title alone. A sales manager may review proposal clarity and commercial scope. A designer may review layout consistency. A qualified engineer or local authority professional may be needed for issues outside the team’s ordinary remit. A project manager may confirm that a changed design has reached procurement and field operations.
Make the gate specific. “Technical review complete” is weaker than “layout revision B, selected equipment, identified electrical assumptions, and procurement quantities reviewed for the stated release.” The latter gives a later reader a way to understand what was checked without inventing a guarantee that every site condition is resolved.
Teams should also allow an output to move backwards. A proposal can return to screening if new data makes the original scenario unreliable. A procurement package can return to design if an equipment change affects electrical or structural assumptions. Treating that as normal revision work is healthier than forcing a document to remain “final” after its basis has changed. Teams using a connected Solar Designing workflow can keep the design record and its customer-facing output together; they still need to decide when evidence is sufficient for release.
Customer Language Should Match the Confidence Level
Confidence labels are a conversion tool when they reduce surprise. A buyer can act on a transparent preliminary option. They cannot make a sound decision when a modeled figure is presented as a guaranteed result and later reclassified after a survey.
Use direct language:
- “This is an indicative layout based on the materials available today.”
- “The production scenario uses the stated consumption and modeling inputs; the proposal lists assumptions that require confirmation.”
- “Before a technical release, we will verify the listed site and electrical conditions.”
Avoid phrases such as “fully confirmed” unless the scope of confirmation is stated. Avoid converting an estimate into a promise. Production, savings, schedule, approvals, equipment availability, and construction conditions can change. The aim is not to burden a buyer with internal complexity; it is to give them a clear next action and an honest basis for it.
A Five-Minute Confidence Check Before Sending
Before sharing a design, proposal, or release, ask:
- What decision is this output intended to support?
- Which inputs are confirmed, assumed, or missing?
- What three conditions could materially change the result?
- Does the revision identify what has changed since the last output?
- Has the relevant person reviewed it for this stated purpose?
If these answers are not visible, the document is not necessarily wrong. It may simply be mislabeled. Correct the label, request evidence, or route the work for review before its audience assigns it more weight than it can bear.
Practical Next Steps
- Add a purpose and confidence field to every design and proposal record.
- Require a visible list of high-impact assumptions before customer release.
- Define separate review checklists for proposal, procurement, permit, and field decisions.
Ready to Make Solar Project Decisions Easier to Trace?
Book a free SurgePV demo to explore connected solar design, Shadow Analysis, generation and financial modeling, and Solar Proposals.
Book a Free DemoFrequently Asked Questions
What is a confidence level in a solar design?
It is a statement of the evidence, assumptions, and review behind an output, together with the decision that output is intended to support. It helps a reader distinguish a screening concept from a proposal basis or a release-ready package.
Can a preliminary solar layout be used for a proposal?
Yes, when the proposal clearly identifies the preliminary inputs, exclusions, and conditions still requiring confirmation. It should not be presented as a construction or permit release unless the relevant evidence and reviews have been completed.
Who should assign a confidence level?
The person or role responsible for release should apply the label within the company’s process. They may rely on input from sales, design, field teams, engineering, or operations, but the intended decision and review boundary should remain visible.
