Design and proposals / Proposal production

Solar proposal production and acceptance workflow

Connect each proposal scenario to the technical and commercial inputs that must survive acceptance and the operations handoff.

Illustrative workflowProposal production
Record
Proposal package
Proposal scenario
Design version
Commercial quote
Current reviewSelect a reviewed design option
Configured during assessment
  1. 01
    Select a reviewed design optionCurrent decision
  2. 02
    Assemble commercial assumptionsNext controlled handoff
  3. 03
    Review the proposal scenarioNext controlled handoff
  4. 04
    Release the approved version to the customerNext controlled handoff
Why this workflow breaks

A solar proposal combines design, equipment, production, price, incentives, purchase terms, and legal assumptions. When those inputs live in disconnected files, the accepted customer offer may not match what delivery teams receive.

Solar1 starts by documenting the decisions and failure paths. Configuration follows only after the operating boundary is understood.

Workflow sequence

Keep the handoff visible from first review to accepted outcome.

  1. 01Select a reviewed design option
  2. 02Assemble commercial assumptions
  3. 03Review the proposal scenario
  4. 04Release the approved version to the customer
  5. 05Record acceptance and prepare the handoff

What to configure

Specific controls, qualified by implementation.

01

Map proposal sections to approved design and commercial source records.

02

Configure scenario and revision rules for equipment, storage, and purchase terms.

03

Route required technical, finance, and commercial reviews before customer release.

04

Record the accepted proposal version and the evidence needed for handoff.

Assessment output

A shared definition of the records, owners, and acceptance checks.

Records in scope
  • Proposal package
  • Proposal scenario
  • Design version
  • Commercial quote
  • Acceptance event
Roles in the decision
  • Sales representative
  • Design reviewer
  • Finance reviewer
Checks before rollout
  • List authoritative sources for price and equipment.
  • Define proposal approval and customer-release roles.
  • Test superseded, expired, and revised proposal paths.

Continue the workflow

Adjacent records rarely stop at one team.

Questions to settle

Questions to settle before configuring proposal production.

Can we offer cash and financed scenarios?

Relevant scenarios can be modeled after the team confirms the commercial records, approved terms, disclosures, and review ownership.

How is the accepted proposal preserved?

The selected version can retain its design, equipment, pricing, assumptions, documents, and acceptance evidence as a controlled snapshot.

Does acceptance create delivery records immediately?

Only when the installer policy permits it; commercial acceptance may still require finance, identity, document, or site-readiness review.

Next step

Assess proposal production using representative project records.

Bring the current records, owners, approvals, exceptions, and tools. The assessment turns them into a reviewable rollout boundary.
Book an assessment