Skip to content
Back to Business Operations
Business Operations

Clean Energy Pipeline Error Checklist: Symptoms, Causes and Corrections

Diagnose clean energy pipeline record errors with a symptom-and-correction table, evidence checks and a worked forecast-status correction.

Arshia Jahangiri
4 min

Table of contents

A clean energy pipeline error checklist helps a contractor distinguish a misleading record from a real buying decision. A sales pipeline is a record of decisions and evidence. If stages only describe what a salesperson has done, a full pipeline can hide projects that are not ready to progress. Review the following mistakes before buying another lead source.

Treating a contact as a qualified project

A name and a property address establish very little. Confirm the customer’s request, service fit, relevant decision-maker and willingness to complete an assessment. Do not exclude projects using assumptions about income, credit or roof direction that your team has not assessed.

Keep early research inquiries separate from active opportunities. Useful education can serve a person who is not ready to buy without inflating the revenue forecast.

Moving stages without evidence

“Proposal sent” proves delivery of a document, not that the scope is understood or a budget exists. Define entry and exit criteria for each stage. For example, technical review may require a completed assessment and documented constraints before a final price can be approved.

Allow an opportunity to move backwards when a roof issue or equipment change invalidates previous assumptions. Preserve the reason so the team can learn from it.

Hiding uncertainty inside a forecast

Keep estimated contract value, probability and expected decision date distinct. Revisit dates with the customer instead of rolling them forward automatically. Separate confirmed projects from speculative incentive-dependent scenarios.

A closed-lost record should describe the cause: scope, timing, competitor, financing or no decision. “Unresponsive” alone rarely explains the underlying issue.

Automating a broken handoff

Assign an owner and next action before sending more reminders. Stop sequences when the customer replies or withdraws. For commercial messages, review the CRTC’s consent and message requirements. CRTC guidance.

Closing sales without preparing delivery

Before marking work ready for installation, confirm the signed scope, unresolved approvals, promised dates and operational owner. Sales and delivery should share the same assumptions about site access, disruptions and customer responsibilities.

Review a small sample of stalled, lost and completed opportunities together. Choose one recurring process failure and correct it, then check whether the evidence improves. A cleaner forecast is valuable even when it initially makes the pipeline look smaller.

Match the symptom to a correction

Symptom Possible cause to investigate Correction to test
Many contacts, few defined projects. Intake records counted as opportunities. Separate enquiries from projects with a reviewed next task.
Late-stage cards lack current scope. Activity labels substituted for review evidence. Require the accepted document/version and relevant decision.
Forecast dates move every month. Internal targets entered as customer decision dates. Record the actual dependency and date confidence.
The same project appears several times. Multiple contacts or forms created duplicate opportunities. Reconcile identifiers and preserve the original touchpoints.
Delivery receives a different promise. Sales changes did not reach the accepted scope. Use a current handoff package and operations acceptance record.

These are diagnostic possibilities, not findings about your team. Inspect underlying records and ask the responsible people before deciding the cause. The same symptom can come from several different failures.

Work one forecast correction

In a fictional review, a card is marked proposal accepted because the buyer opened the document. There is no recorded acceptance or authority confirmation. Correct the status to reflect the evidence, retain the activity and ask the agreed next question.

The forecast may become smaller after correction. That does not mean the business lost a confirmed project; it means the earlier record overstated what was known. Preserve the correction reason so reporting can distinguish a data repair from an actual customer decline.

Assign the rule change to one owner and check the next comparable records. Review reopened projects and duplicates consistently rather than deleting inconvenient history. Better records should help the team choose its next action and communicate commitments accurately.

Share this article