Answer
Solar version control comes down to six rules: give each project one identifier, label every released design and proposal revision, record why each change was made, link dependent outputs to the revision they came from, lock released files, and mark superseded documents. Together they let anyone see which version a customer actually received.
Last updated: November 2026
Version control is not only a software-engineering idea. In a solar opportunity, it is the difference between “the proposal” as an ambiguous file name and a traceable package of layout, assumptions, commercial terms and next actions. It matters most when sales speed makes informal sharing tempting.
This guide gives six rules a small installer or EPC can adopt without new tooling. For the wider revision workflow, including how stale PDFs reach customers, see the guide to solar design revision management.
Why Version Control Belongs in the Project Workflow
Solar proposals combine site facts, design assumptions, modeled outputs and commercial information. A change in one can make another less reliable. A version-control habit shows what is confirmed, what is estimated and what must be revisited before release.
This article is desk research for installers and EPCs. It is not engineering advice, a site survey, or a guarantee of production, approval, savings, cost or delivery outcomes. Use applicable local rules, equipment documentation, utility requirements and qualified review for the project at hand. For technical background on PV modeling, see the National Laboratory of the Rockies PV research pages, which do not replace project review.
Key Takeaway
A revision is only useful if a reader can answer three questions in under a minute: which version is current, what changed, and who approved it. The six rules below exist to make those answers easy.
Keep design revisions tied to the proposal
See how a connected design and proposal workflow can keep layouts, material lists and customer documents on the same revision.
Book a DemoChecking cost first? See the SurgePV pricing page.
Rule 1: Give the Project One Identity
Start with a stable project ID that appears in the design record, the proposal, key drawings and the handoff documentation. Customer names and street names are useful search terms, but they are not reliable identifiers. They can be similar, change, or be abbreviated differently across teams.
A simple pattern works: a short prefix, a year and a sequence number. Whatever pattern you choose, issue the ID once, at opportunity creation, and never reuse it.
Rule 2: Label Released Revisions Plainly
Use labels that a nontechnical teammate can understand: Design D03, Proposal P02, a release date and a status. Avoid filenames such as “final-final-new.” A clear label tells a recipient whether a document is current and makes it possible to reference a specific customer conversation later.
| Label element | Example | Purpose |
|---|---|---|
| Project ID | SP-2026-0142 | Ties every file to one opportunity |
| Artifact type and number | Design D03, Proposal P02 | Shows which document and which revision |
| Release date | 2026-11-04 | Orders the history |
| Status | Draft, In review, Released, Superseded | Separates revision number from approval state |
The examples are illustrative formats, not a required standard.
Rule 3: Record Why a Revision Exists
A revision log should identify the trigger, the source of new information, the owner, the affected outputs and the approval status. This turns change history from a blame record into decision context. It also helps a new team member distinguish a deliberate customer option from an outdated calculation.
Here is a minimal log entry, using invented values:
| Field | Example entry |
|---|---|
| Revision | Design D03 |
| Trigger | Customer asked to add a battery option |
| Source | Customer email dated 2026-10-28 |
| Owner | Designer on the project |
| Affected outputs | Layout, bill of materials, Proposal P02 |
| Approval | Technical review pending |
Pro Tip
Make “affected outputs” a required field. Most stale-document errors happen because the layout changed but nobody listed the bill of materials or the financial scenario as affected.
Rule 4: Link Design to Commercial Output
When a proposal uses a layout, production estimate, bill of materials or financial scenario, record the design revision it came from. If you are evaluating solar design software, check which revision references it keeps for you and which links you would still maintain by hand in the offered configuration.
The same principle applies to production numbers. A generation estimate belongs to the layout and assumptions that produced it, so quote both together. The PVWatts calculator from the National Laboratory of the Rockies makes the same point: it cautions that its predictions rest on many assumptions and uncertainties, so a result is only meaningful next to its inputs. When a layout changes, see layout-change checks for how to find the dependent outputs.
Rule 5: Protect Released Artifacts
Once a design or proposal is released, do not silently edit the file in place. Make the change in a new revision, show what is superseded, and decide whether the customer needs the update. This protects both the buyer and the installation team from working with an appealing but obsolete document.
Locking can be as simple as moving the released PDF to a read-only folder and creating the next revision as a copy. Software with permissions makes it easier, but the rule does not depend on it.
Rule 6: Mark Superseded Documents and Review Exceptions at Handoff
Mark a replaced document as superseded and point to its successor. Do not delete it, because you may need to show what a customer received on a given date.
Fast-moving projects create exceptions: a supplier substitution, a late site photo, an altered tariff or a new roof constraint. Each organization should define who can release exceptions and what record is required at handoff.
Record the Changed Baseline
NASA’s configuration-management guidance describes identifying baselines, controlling changes and maintaining status records. It lists five elements: planning and management, identification, change management, status accounting and verification. These are record-management principles, not a solar permitting standard. The responsible project roles still determine technical review and any authority or utility submission requirements.
The first figure comes from the NASA page above. The other two count items in this guide and are not market data.
| Record | What to retain |
|---|---|
| Project and artifact identity | Stable project ID, document type and revision |
| Release basis | Source revisions, reviewer, date and intended use |
| Distribution | Recipients, replacement notice and acknowledgment status |
| History | Superseded copy and reason for change |
A later filename or upload date alone does not prove that a document is released. Record a draft, review or released status independently of its revision number. Reading or acknowledging a replacement notice is not automatic technical approval.
Try the six rules on a live project
Walk through a design-to-proposal revision with a SurgePV specialist and see which links stay automatic.
Book a DemoChecking cost first? See the SurgePV pricing page.
For a related checklist, see why version confusion can kill confidence in an otherwise strong proposal. To see the workflow on your own projects, book a SurgePV demo.
Frequently Asked Questions
What should be versioned in a solar project?
Version layouts, assumptions, energy and financial models, material lists, drawings, proposals, and customer-facing options when they are revised or released.
Why not overwrite an old proposal?
Preserving the old version makes it clear what the buyer received, why it changed, and which information is no longer current.
Who should approve a solar revision?
Assign approval according to the change type and the team’s documented roles. Material technical or commercial changes should not be released without the appropriate review.
How should solar design revisions be named?
Use a plain label that a nontechnical teammate understands, such as Design D03 or Proposal P02, plus a release date and a status. Avoid names like final-final-new, which say nothing about which file is current.
Is a file’s upload date enough to show which proposal is current?
No. An upload or modified date does not show whether a document was reviewed or released. Record a draft, review or released status separately from the revision number.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.


