7 Assets for a Commercial Solar Champion's Internal Case

Your buyer-side contact likes the commercial solar concept. Then the forwarding begins.

Finance asks which scenario the numbers describe. Facilities wants to see affected roof areas, access constraints, and operating responsibilities. Procurement asks what is included. An executive wants the requested decision in one paragraph. The person carrying the project internally now has a slide deck, a proposal, several email answers, and no safe way to tell which item is current.

That person needs more than persuasive copy. They need a compact content system built around one controlled project record. The seven assets in this guide let a commercial solar marketer separate the decision, facility facts, options, assumptions, risks, proof, and final request without allowing those parts to contradict one another.

This is an enablement method, not a way to manufacture agreement. The internal champion can route material, collect questions, and explain the next step. They do not become the buyer’s engineer, finance authority, lawyer, procurement owner, utility, tax adviser, or executive approver. The buyer retains its own governance, and every consequential conclusion still belongs with the responsible person.

The commercial solar consensus workflow explains how to document decision rights, support states, objections, and group disposition. This article has a narrower job: give the champion a linked set of content assets that make the next internal review easier to inspect.

What makes an internal-case asset useful?

An internal-case asset is useful when it answers one reviewer decision, identifies the exact project and scenario, exposes its sources and assumptions, names the responsible owner, and states what remains unresolved. The seven assets should work as different views of one evidence spine, not as separate stories optimized for different audiences.

The distinction matters because a polished file can still be unusable. A financial summary without the scenario ID cannot be reconciled with the design. A roof plan without a survey status can be mistaken for an approved layout. A risk FAQ written from memory can conflict with a contract appendix. More content only multiplies the ambiguity.

Start the package with a small set of shared controls:

• one project ID and facility identity;
• one named decision and requested disposition;
• one current option or a clearly identified set of alternatives;
• one scenario ID for every modeled output;
• an evidence state for each material item;
• a source location, owner, review status, and date;
• explicit limitations, open questions, and return triggers;
• a package version that changes when a material asset changes.

Use evidence-state labels that describe what the reader is holding. “Observed” might refer to a site measurement or utility record. “Customer-supplied” identifies information the buyer provided but the project team has not independently verified. “Modeled” names an output from stated inputs and configuration. “Assumed” preserves a placeholder or scenario choice. “Pending review” marks a consequential item awaiting a responsible person. “External outcome” covers a utility, permitting authority, lender, insurer, landlord, or other party whose decision is not controlled by the seller or champion.

“Observed” describes how a record was obtained; it does not mean the observation is accepted for every use. A measured dimension still needs its method, location, date and review boundary. A utility file can be authentic while its meter scope or period is unsuitable for the scenario. Record source provenance separately from verification status.

The labels are not grades. They prevent a chain of retelling from turning an assumption into a site fact. They also let reviewers focus on the items within their remit.

EPA’s on-site project development pathway separates goal setting, site and utility-data collection, procurement, proposal evaluation, contracting and commissioning. Build the package around the buyer’s current stage: permission to investigate is a different request from selecting a proposal or signing a contract. The seven-asset format below is an editorial workflow recommendation, not an EPA requirement.

O*NET’s solar sales representative and assessor task inventory includes needs gathering, proposals and presentations, technical information, site assessment, production estimates, and design-related material. Those tasks explain why sales content touches several specialist domains. They do not grant the marketer authority over any of them.

Which seven content assets help a commercial solar champion build an internal case?

Give the champion a decision brief, facility evidence sheet, option comparison, financial assumptions sheet, risk and dependency register, proof and source pack, and decision memo. Each asset has one primary job, but all seven use the same project, option, scenario, evidence-state, owner, and revision labels so internal readers never reconcile competing narratives.

This is a package, not a mandatory sequence of attachments. A facilities reviewer may need only the facility sheet, risk register, and linked source records. A finance reviewer may start with the option comparison and assumptions sheet. An executive may read only the decision brief and decision memo. The controlled package preserves what they did not read and lets a question travel back to its owner.

1. The one-page decision brief

The decision brief is the champion’s front door. It should say what is being considered, why it is being considered now, which facility and option are in scope, what decision is requested next, and what is not yet decided. Keep the main statement short enough to forward without losing the qualifiers.

A useful brief distinguishes the business context from the proposed answer. “The facility is reviewing future electricity-cost exposure” is context. “Approve this exact solar option” is a request. Neither sentence proves that the project is feasible, economical, financeable, permitted, or approved.

Include the current package version, scenario ID, date, and named owners. Add a small status box for verified inputs, modeled outputs, assumptions, pending reviews, and external outcomes. If an executive reads nothing else, the brief should still reveal the material holds.

Do not turn this page into a compressed proposal. Pricing detail, equipment schedules, calculations, contract clauses, and source documents belong in their controlled assets. The brief points to them.

2. The facility evidence sheet

The facility sheet grounds the case in the buyer’s building, site, energy record, and operating constraints. It can identify the address or site ID, relevant roof or land areas, available drawings, energy-data period, operating schedule, known load changes, access conditions, ownership or tenancy context, and records still needed.

For each field, show the value, source, date, evidence state, and owner. “Roof area from customer drawing, drawing revision C, pending field verification” is more useful than “ample roof space.” “Interval data supplied for the stated period, gaps not yet reviewed” is safer than “complete usage profile.”

EPA’s on-site renewable project development process identifies utility policy, regulation, permitting, ownership structure, and geographic variation as parts of commercial-solar decision context. Use it for the broad project-development sequence; decisions still require current, location-specific evidence and qualified review.

The sheet should not announce project fit. Its job is to show which facility facts have been supplied, observed, modeled, assumed, or left open. Engineering, structural, electrical, fire, environmental, utility, permitting, landlord, insurer, and other reviews remain with the responsible parties.

3. The option-comparison matrix

The option matrix prevents the champion from comparing a detailed solar case with a vague status quo or a differently scoped alternative. Name each option, its boundary, its version, the criteria selected by the buyer, the available evidence, and the uncertainty that could change the comparison.

NASA’s decision-analysis guidance describes characterizing alternatives against decision-maker priorities and the state of knowledge, including uncertainty, in NASA systems work. The bounded analogy is valuable: compare defined alternatives on visible criteria, and do not hide what is unknown. NASA does not govern a commercial solar purchase.

Criteria may include site use, delivery model, owner obligations, operating interfaces, commercial boundary, schedule dependencies, risk allocation, or evidence maturity. Do not assume every criterion has equal weight or that the seller selects the weights. Record who owns each criterion and whether it is a threshold, preference, professional determination, external requirement, or discussion item.

If the buyer has not defined a credible alternative, label that gap. Do not fill the status-quo column with zeros, omit its risks, or use unmatched time periods. The matrix supports comparison; it does not decide which option is best.

4. The financial assumptions and scenario sheet

The financial sheet makes the economic view reconstructable without asking the champion to defend a black-box number. Identify the scenario, analysis date, currency, period, cost boundary, source for each input, modeled or contractual status, owner, sensitivity, exclusions, and qualified review state.

Separate source records from calculated outputs. A utility bill is a source record. A future tariff path is an assumption unless an appropriate record and treatment establish otherwise. A modeled production value is not measured production. A proposed financing term is not an executed agreement. An incentive, tax treatment, accounting classification, or depreciation assumption is not available to the buyer merely because it appears in a worksheet.

The financial assumptions audit for solar proposals provides the deeper review control. In this package, the champion needs the approved scenario and its material limits, not an invitation to edit the model.

Hold this asset when a reviewer cannot identify what costs are included, which project version the scenario uses, who owns a material input, or what would reopen the result. Route investment, accounting, tax, financing, tariff, and legal conclusions to qualified people.

5. The risk, dependency, and reviewer FAQ

Combine a compact risk register with the questions reviewers are likely to ask. The register names the uncertain event or condition, evidence available, potential consequence, responsible owner, response, target review, and trigger that changes the case. The FAQ translates those records into usable answers without pretending every risk is resolved.

Useful categories include source-data gaps, facility access, design maturity, equipment assumptions, interconnection, permitting, ownership or tenancy, procurement, contract terms, finance, insurance, schedule, operations, and claims. Categories are prompts, not a universal list. The project owner and qualified reviewers decide what is material.

Translate each open issue into visible ownership. Each reviewer FAQ answer should say what is known, who is reviewing the issue, which source record supports the answer and what would reopen it. Use this as a local package-control rule, not a claim that an external authority has approved the project.

Avoid defensive answers such as “not a concern” or “handled during installation.” If a question depends on a future survey, utility response, contract negotiation, or professional review, say so. A pending item with an owner and return condition is more credible than a confident sentence that no one can support.

6. The proof and source pack

The proof pack is the package’s memory. It connects every material claim, chart, diagram, comparison, and quotation to a source, evidence state, owner, permission record, limitation, review status, and expiry or refresh trigger. It can contain product documentation, approved project records, reviewed model outputs, customer-supplied files, public authorities, and clearly labelled illustrative material.

FTC advertising guidance says United States advertising must be truthful and non-deceptive and objective claims need evidence. An internal asset can later travel into a proposal, presentation, email, or public channel, so preserve claim support at creation. Qualified legal review must address the actual company, audience, statement, channel, and jurisdiction.

A testimonial or case study is not generic proof. Permission, project context, period, selection, and limitations stay attached. The commercial solar case-study guide explains how to control a public story from a real project. This proof pack has a different role: substantiate the current case without implying that another project predicts this one.

Mark withdrawn, superseded, or expired material. A beautiful chart from an older scenario should not remain available simply because it is convenient.

7. The decision memo and approval request

The final asset names the exact decision, the person or body that holds authority, the option and package version under review, the conditions or objections recorded, the evidence reviewed, and the permitted disposition. Useful dispositions include approve, approve with named conditions, return for specified evidence, hold, escalate, reject, or close without decision.

The memo should never treat a meeting invitation, email open, verbal encouragement, or champion summary as approval. It also should not collapse specialist review into one executive signature. A finance review does not supply engineering judgment. A technical review does not approve commercial terms. Procurement participation does not necessarily establish final budget authority.

For distributed decisions, use the multi-stakeholder proposal checklist to check the complete document release and the consensus workflow to preserve participant rights and dispositions. The decision memo merely closes the content package around one named request.

How do you assemble the seven assets without contradictions?

Build the package in seven passes: define the decision, freeze project identity, inventory sources, assign evidence states, create the seven views, run asset-specific review, and release one controlled version. Return any material change to its source asset and affected reviewers instead of patching a forwarded copy or asking the champion to reconcile it.

1. Define the next internal decision. Write the decision, authority holder, in-scope facility, current option, alternatives, and allowed disposition. If the next step is only permission to investigate, say that. Do not write an approval brief for a case that is still collecting feasibility inputs.

2. Freeze the evidence spine. Assign the project ID, facility ID, option IDs, scenario ID, package version, owners, and review date. Identify the current design and financial scenario. Mark earlier versions superseded for this decision package before creating audience views, while retaining historical records and approvals under their own scope. A new audience view does not itself cancel an executed contract or an external approval; the responsible owner determines whether a material change reopens it.

3. Inventory source records. List buyer-supplied energy records, drawings, site notes, model runs, equipment inputs, commercial records, public sources, permissions, and external decisions. Record location, date, owner, and access. Missing evidence remains a visible gap.

4. Classify every material item. Use specific labels such as observed, customer-supplied, modeled, assumed, pending review, and external outcome. Add the responsible reviewer and limitation. Avoid broad labels like “confirmed” unless the record says what was confirmed, by whom, for which purpose, and when.

5. Create seven views from the same record. Give each asset one reader decision and only the detail required for that decision. Reuse identifiers and source links rather than rewriting facts. The role-specific solar messaging guide can help shape the reading path without changing the evidence.

6. Run claim-specific and domain review. Content reviews clarity and traceability. Facilities reviews site and operating statements. Technical owners review design and performance. Finance reviews the economic boundary. Add tax, accounting, legal, utility, procurement, privacy, accessibility, advertising, contract, insurer, landlord, or executive review when applicable.

7. Release and reopen as a package. Record the approved package version, asset hashes or versions, reviewers, date, distribution list, and reopen triggers. A changed site input, model, equipment choice, cost, tariff, permission, external response, or material claim should identify which assets and approvals need renewal.

The workflow does not require every reviewer to edit every file. It requires one owner to know where a statement came from and which views depend on it. A simple dependency map is enough: source record to scenario, scenario to affected assets, assets to reviewers, reviewers to disposition.

Use hold rules instead of hopeful footnotes

A qualifier at the bottom of a slide cannot rescue a conclusion that should not have been released. Set asset-level holds before drafting.

These rules give the champion a safe answer when a colleague asks for a cleaner slide: the package can be simplified, but the evidence boundary cannot be removed.

What should the copy-ready asset manifest include?

The copy-ready manifest should identify the project, facility, option, scenario, package version, requested decision, authority holder, and owner. For every asset, record its reader, source records, evidence states, reviewer, status, limitations, and hold condition. Finish with distribution, approval, expiry, correction, and reopen controls so forwarded copies remain traceable.

Use this template as the package index. Keep the completed record in a shared controlled location, not only in the champion’s inbox.

COMMERCIAL SOLAR INTERNAL-CASE ASSET MANIFEST

PACKAGE CONTROL
Project ID:
Facility ID and approved description:
Decision requested:
Decision authority or governing body:
Current option and alternatives:
Design scenario ID and status:
Financial scenario ID and status:
Package version, owner, and review date:

SHARED EVIDENCE STATES
Observed records:
Customer-supplied records pending verification:
Modeled outputs and configuration:
Material assumptions and owners:
Pending specialist reviews:
External decisions and responsible parties:
Prohibited inferences:

ASSET 1 | DECISION BRIEF
Reader decision:
Source records:
Owner and reviewer:
Status, limitations, and hold condition:

ASSET 2 | FACILITY EVIDENCE SHEET
Reader decision:
Source records:
Owner and reviewer:
Status, limitations, and hold condition:

ASSET 3 | OPTION COMPARISON
Reader decision:
Alternatives, criteria, and boundaries:
Owner and reviewer:
Status, limitations, and hold condition:

ASSET 4 | FINANCIAL ASSUMPTIONS SHEET
Reader decision:
Scenario, sources, period, and boundary:
Owner and reviewer:
Status, limitations, and hold condition:

ASSET 5 | RISK, DEPENDENCY, AND REVIEWER FAQ
Reader decision:
Open items, owners, responses, and triggers:
Owner and reviewer:
Status, limitations, and hold condition:

ASSET 6 | PROOF AND SOURCE PACK
Claims, charts, quotations, and source locations:
Permissions, reviews, expiry, and withdrawal:
Owner and reviewer:
Status, limitations, and hold condition:

ASSET 7 | DECISION MEMO
Exact request and permitted dispositions:
Conditions, objections, and unresolved authority:
Owner and reviewer:
Status, limitations, and hold condition:

RELEASE CONTROL
Approved asset versions or hashes:
Approved reviewers and dates:
Distribution locations and recipients:
Correction owner and withdrawal route:
Refresh, expiry, and reopen triggers:
Final disposition and next action:

The repeated fields are intentional. They let the package owner see whether an asset changed the reader but also changed the facts. Teams can implement the manifest in a document system, spreadsheet, or content workflow. Tool choice does not replace record ownership.

Illustrative example: a facility sheet changes after the brief is forwarded

This example is fictional, contains no customer result, and does not describe a complete project.

A marketer prepares the seven assets for a distribution facility. Package version 0.3 uses a customer-supplied roof drawing and a modeled layout called Design Scenario DS-03. The facility sheet labels the drawing “customer-supplied, field verification pending.” The decision brief asks only for permission to continue technical and commercial review. It does not request project approval.

Facilities then identifies a roof-access constraint not shown in the supplied drawing. The package owner records the observation, source, date, and facilities owner. DS-03 is now affected, so the layout and its dependent energy and financial outputs move to “revision required.” The owner does not patch only the facilities sheet or ask the champion to explain the difference verbally.

The affected decision brief, option matrix, assumptions sheet, risk register, proof pack, and draft decision memo are marked held. A qualified technical owner determines how to revise the design. The project team issues a new scenario and reviews downstream outputs. Package version 0.4 states what changed, which earlier assets were superseded for this package, and which reviews reopened. Retain version 0.3 as history, withdraw its affected audience copies from current use, and notify the recorded recipients where practicable. Record any external approval separately rather than declaring it cancelled through a marketing revision.

The champion can still update internal colleagues. Their safe message is that a new facility constraint was recorded and affected scenarios are under review. There is no invented delay estimate, no claim that the constraint is minor, and no informal approval carried forward from version 0.3.

Keep the manifest beside the action plan

The manifest says what evidence package exists now. The mutual action plan checklist says which buyer and seller events are expected next. Link them through the same project and decision ID, but do not combine them. A future meeting date does not prove that the current evidence is ready, and an approved asset does not schedule its own review.

Where can SurgePV support the internal case, and where does it stop?

SurgePV can support 3D roof modeling, array layout, shading analysis, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. Reviewed outputs can feed the facility sheet, option matrix, assumptions sheet, risk discussion, proof pack, and proposal. Buyer governance and qualified reviewers still own inputs, conclusions, permissions, and approvals.

SurgePV’s design and proposal workflow can provide source material for several content assets. A reviewed array layout can support a facility discussion. A named energy and financial scenario can support an assumptions sheet. Bill-of-materials and electrical-workflow outputs can help responsible reviewers locate the current design basis. Proposal generation can assemble customer-facing material from the approved scenario.

Keep the output state visible. Software does not know that a customer drawing is outdated unless the workflow supplies and identifies the correct information. A model result depends on inputs, assumptions, equipment models, configuration, integrations, and review. Moving a value into a branded PDF does not make it measured, contractual, approved, or suitable for a different jurisdiction.

The generation and financial tool can help keep reviewed design, energy, and financial scenarios connected. It does not decide whether the buyer should invest, validate tax or accounting treatment, approve a tariff interpretation, or replace finance review.

SurgePV also does not identify the internal champion, map stakeholder authority, record consent, run the buyer’s approval committee, grant engineering sign-off, issue utility or permit decisions, negotiate contracts, or substantiate every marketing claim automatically. Keep those records in the systems and professional workflows responsible for them.

The clean boundary is this: use software to produce and preserve inspectable solar work. Use the seven-asset package to route that work with its sources and limitations. Let authorized people make the decisions.

Frequently Asked Questions

What is a commercial solar champion?

A commercial solar champion is a person inside the buyer’s organization who helps the project reach the right reviewers and keeps questions moving. The role does not automatically carry budget, engineering, legal, procurement, utility, or executive authority. Confirm actual decision rights instead of inferring them from enthusiasm, seniority, or job title.

Should every stakeholder receive all seven assets?

No. Keep all seven assets in the controlled package, then give each reviewer the shortest useful path for their decision. Finance may begin with assumptions and options; facilities may begin with site evidence and risks. Each view must retain the same project ID, scenario, status, source notes, limitations, and revision date.

Can a case study replace the proof pack?

Usually not. A permissioned case study can illustrate a past project’s context, method, and limitations, but it does not validate a new site’s inputs or economics. The proof pack for the current decision should point to current source records, reviewed models, product documentation, permissions, and claim-specific evidence instead of borrowing another project’s outcome.

What happens when information is missing?

Mark the field pending, name the person or external party who can resolve it, record the consequence, and set a return condition. Do not hide the gap or substitute a convenient assumption. If an approved scenario uses an assumption, label it, retain its source and sensitivity, and route it to the responsible reviewer.

Where can SurgePV help with these assets?

SurgePV can support array layout, shading analysis, energy-yield and financial modeling, electrical workflow, bill-of-materials output, and proposal generation. Those reviewed outputs can feed several assets. People must still validate source data, engineering, finance, tax, utility, contract, legal, procurement, advertising, accessibility, privacy, and final approval decisions.

Give the champion a case they can route safely

An internal champion should not have to choose between forwarding a giant proposal and rewriting technical, financial, and commercial answers from memory. Give them seven controlled views of one project. Make every material statement traceable, every assumption visible, and every unresolved conclusion returnable to its owner.

A cleaner internal decision record does not guarantee consensus or approval. It gives the next conversation specific terms: which option, which evidence, which reviewer, which condition, and which decision comes next.