Answer
Separate necessary unpaid work from avoidable recovery. Track where a solar opportunity required repeated entry, clarification, reprioritization or correction, then change the input or handoff that caused it. Keep technical checks and customer support that the work requires. Measure the result against comparable opportunities before claiming a saving.
Not every hour that lacks a separate invoice is waste. A design review, customer clarification or supplier check may be necessary to deliver the work you sold. The useful question is which effort exists because an earlier input or decision was missing, duplicated or wrong.
The following seven changes are operating suggestions for solar sales and delivery teams. They are not measured savings claims or instructions to remove required controls.
1. Separate useful work from recovery work
Review recent opportunities and label the reason for each extra task. Distinguish agreed customer work, required review and avoidable recovery. A second design check after a legitimate customer change is different from recreating a lost file.
Let the task owner challenge the classification. Otherwise, a target to cut unpaid hours can discourage people from recording essential work.
2. Choose one source for repeated project inputs
Identify where the team retrieves the site identity, selected scenario, equipment revision and customer contact. Link to the controlling record rather than asking every role to maintain another independent copy.
Document intentional copies, such as a customer PDF, and when they need to be regenerated. A copied field is not automatically current just because its destination looks complete.
NASA’s interface-management guidance describes defining interfaces and their characteristics when work is divided among parties. It is not a solar productivity study. Use it as a process reference for specifying what one role must pass to the next, not as evidence of a time saving.
3. Set an intake threshold before assigning design
List the inputs needed for the next design task. Permit preliminary work only where its assumptions and limits are understood. When something is missing, return a specific request rather than a message saying “need more detail.”
For example, ask which building the customer means when a parcel contains several structures. Do not spend design effort on a choice no one has confirmed.
4. Make the queue and priority decision visible
Record each job’s next action, owner and reason for its priority. When a manager changes the order, make the displaced work visible too. This gives the team a way to discuss capacity without repeatedly reconstructing the queue in chat.
Avoid treating every customer message as permission to interrupt the current task. Agree who can change priorities and what evidence they need.
5. Replace vague requests with a bounded brief
“Update the proposal” could mean change the equipment, add another finance scenario or correct a recipient. Ask the requester to identify the object, requested change, current revision and next decision.
A useful brief also states what remains unchanged. The recipient can then ask whether an apparently small change affects design, cost or customer commitments before starting.
6. Review returned work by cause
| Return reason | What to investigate |
|---|---|
| Wrong site or scenario | Identity confirmation at intake |
| Stale equipment or layout | Revision selection and notification |
| Unclear customer request | Brief and acceptance criteria |
| Missing technical evidence | Input requirements and escalation |
| Repeated commercial correction | Pricing ownership and release review |
Use the return record to improve the process, not to infer blame from the name of the last person who touched the file.
7. Retire reports only after identifying their users
Ask who uses a report, what decision it supports and whether another record already answers that question. A report with no identified use is a candidate for retirement, subject to contractual, recordkeeping and management needs.
If it is required, simplify its production before deciding that the review itself is unnecessary.
Check whether the change helped
Illustrative exercise: choose one recurring clarification, change the intake question that caused it, and compare the next similar opportunities. Record both extra effort removed and extra effort introduced. Keep project complexity and customer changes visible so a different job mix does not look like process improvement.
Use the project handoff worksheet to record the revised brief and return reasons. If the suspected problem is duplicate design-to-proposal entry, ask about that specific transfer when evaluating proposal software. Do not assume a product automates it without seeing the workflow.
Frequently asked questions
Should we eliminate all non-billable work?
No. Required reviews, support and coordination can be part of delivering the agreed service even when they are not invoiced separately. Focus on avoidable recovery and duplication while preserving necessary controls.
What should a return log include?
Record the opportunity, task, reason for return, missing or conflicting input, next owner and correction. Separate a legitimate scope change from a preventable error before deciding what process to change.
How should savings be reported?
Use recorded effort from comparable work, disclose the measurement period and account for effort added elsewhere. Without that evidence, describe the process change rather than advertising a time or cost saving.
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.
