
NGO Partnership Delivery Formats: Five Scoped Contributions for Energy Vendors
Compare five NGO partnership delivery formats for clean energy vendors, with defined outputs,...

Review contractor lead scoring with transparent response routes, calibration checks and recorded human corrections, separate from consent and technical suitability.
A contractor lead-scoring review should check whether the queue gives each suitable enquiry an appropriate next action. Lead scoring can help a small team decide which inquiry needs a response next. It cannot establish technical feasibility, creditworthiness or rebate eligibility. Use it as a queueing aid with clear criteria and a way for staff to correct mistakes.
Service fit: is the requested work within your skills and service area? Does the person have authority to request the next step, or is an owner or building representative needed?
Readiness: has the person requested an assessment or quote, supplied relevant information and identified a realistic timeline?
Uncertainty: what needs investigation before a proposal—roof condition, shared-property approval, electrical capacity or a building assessment?
Do not automatically penalize tenants, condo owners, heritage properties or financing questions. These may need a different process or decision-maker, not a judgement that the person is a poor prospect.
Use “respond now,” “clarify first” and “future date requested” before adding numerical points. For each label, record the reason, responsible person and next action. If you later use a score, publish the internal rule and test it against actual serviceable projects rather than adopting invented weights.
An illustrative rule might prioritize an assessment specifically requested for an address in your service area, while routing an unclear ownership request to a clarification call. Neither action confirms that the installation can proceed.
A high score is not permission to send promotional email or SMS. Record the source, consent or other applicable basis, preferences and suppression status using CRTC guidance. A low score should not automatically place someone in a drip campaign.
Collect only information relevant to the next stage. Meaningful-consent guidance helps explain how property and contact data will be used and shared. Avoid speculative financial or personal labels in free-text notes.
| Example record | Response route | Reason to record |
|---|---|---|
| Assessment requested within the service scope. | Assign a person to arrange the next assessment step. | Requested task and service fit are known; technical suitability remains unverified. |
| Shared-building request with unclear authorization. | Ask who can authorize the next step. | Clarification is needed, not an automatic rejection based on tenure. |
| Customer asks to revisit after planned roof work. | Record the requested future decision point. | Current timing differs from an active booking request. |
| Record lacks a usable contact route. | Investigate the intake failure through the approved process. | A high numerical score cannot repair missing information. |
Keep permission status and any urgent service issue outside this priority label. Urgency needs an appropriate service response, not more points in a promotional queue. Staff should be able to explain and correct the assigned route.
Review a sample of high-priority, clarification and future-date records with sales and delivery staff. Ask whether the next action was appropriate, whether important information was overlooked and whether the customer received the requested response.
If a viable project was overlooked, record the original evidence, the rule that caused the route, the human correction and whether the rule needs changing. Preserve the reason rather than rewriting history to make the score look accurate.
Numerical weights, if used, need their own calibration record and version. Test them against comparable outcomes and review errors on both sides: overlooked suitable work and prioritized requests that still lacked essential facts. A small sample is a learning aid, not proof of predictive accuracy.
Compare response times, assessment quality, completed work and reasons for closure. Review whether the system overlooks viable projects or overvalues early interest that never becomes work. Let human judgement override the score with a recorded reason.
Treat partner-supplied labels as information to verify. “Qualified” or “rebate ready” should have a documented definition and should never replace the assessments required for a safe, suitable project.

Compare five NGO partnership delivery formats for clean energy vendors, with defined outputs,...

Reconcile partner referrals with an event-to-payment ledger for source history, duplicate...

Use co-marketing templates for clean energy partners to document the brief, landing-page...