Answer
To investigate solar margin leakage, compare the agreed job scope and estimate with actual purchasing, labour, change and closeout records. Separate legitimate scope changes from preventable recovery, then assign a correction to the process that caused the gap. A lower task cost does not prove higher project margin if costs move elsewhere.
A project can finish at its quoted selling price and still require more work than the estimate allowed. Before raising equipment prices, examine how the estimate, design changes, purchasing and delivery records explain the result.
These six checks are a proposed management review, not financial advice or a promise of improved profit. Have the appropriate accounting owner define the cost and margin measures your business uses. Apply the same definitions when comparing jobs.
1. Reconstruct the job from enquiry to closeout
Gather the accepted scope, estimate, purchasing record, recorded labour, subcontractor costs, approved changes and closeout exceptions. Identify costs that sit outside the project report so they do not disappear from the review.
Separate information that was available when pricing from information learned later. Otherwise, the review can blame an estimator for an unknown condition instead of asking whether the offer handled that uncertainty appropriately.
2. Distinguish an estimate from an unsupported allowance
For material cost lines, record the supplier basis, quantity basis, date and applicable conditions. Mark assumptions and unresolved quotes. Give each an owner and a point at which it must be resolved.
Do not conceal a missing price inside an apparently precise total. Ask the commercial owner how the uncertainty should be represented in the offer and internal decision.
3. Connect design changes to purchasing and site work
| Change to inspect | Records that may need review |
|---|---|
| Equipment substitution | Design, supplier terms, quote and material list |
| Layout revision | Quantities, installation scope and customer visuals |
| Customer-selected option | Accepted scope, price and delivery instructions |
| Site finding | Relevant technical review, estimate and change authorization |
| Schedule change | Procurement and delivery commitments |
This is a review prompt, not a determination that each change has the same consequences on every job. Let the responsible owners identify the affected records.
NASA’s configuration-management guidance describes controlling changes and keeping product information consistent. That is a reference for tracing revised project records, not evidence that a particular solar process improves margin.
4. Give exceptions an owner and a decision point
Record what is unresolved, which work depends on it and who can decide. Ask when delay changes the available options. A note saying “waiting for confirmation” does not show whether a purchase or site booking should proceed.
Review exception age alongside its consequence. A recently opened issue may matter more than an older administrative question.
5. Review non-standard work before committing to it
A customer request may be worth accepting, but identify its design, procurement, review, installation and support implications first. Record who accepted the commercial treatment and what the customer was told.
Illustrative example: a proposed equipment substitution has a lower purchase price but requires additional design review and different installation work. Compare the complete revised scope before describing the substitution as a saving. No product prices or savings are assumed in this example.
6. Use completed jobs to improve the next estimate
Classify differences between estimate and actual outcome. Distinguish scope changes, measurement errors, supplier changes, productivity assumptions and avoidable rework. Update the estimate rule that the evidence supports, rather than applying one successful or difficult job to every future project.
Keep the revision and its basis so the next estimator understands why the allowance changed.
Define success before changing the process
Choose the measure and comparison group with the accounting and operations owners. Include correction effort and costs introduced elsewhere. Preserve project complexity and scope changes in the analysis.
A project handoff worksheet can help identify where a design or commercial change should reach the next owner. If software is part of the proposed improvement, ask vendors to demonstrate that particular transfer before attributing a financial benefit to it.
Frequently asked questions
Should a cheaper component automatically improve margin?
No conclusion follows from purchase price alone. Review the complete affected scope, including design, compatibility review, installation, supplier conditions and support. Use actual records and the business’s agreed cost definitions.
How should we handle customer changes?
Record the requested change, affected scope, review needs, commercial treatment and authorization. Distinguish a legitimate change from an estimating error before using it to revise future estimates.
Can this checklist predict a margin increase?
No. It identifies questions to investigate. A financial outcome requires consistent cost definitions, reliable project records and comparison of the actual result, including costs introduced elsewhere.
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.
