B2B Referral Program Operations for energy technology companies: Governance Playbook

Govern the referral system as a service boundary

B2B referral program operations for energy technology can involve customers, installers, developers, utilities, advisors, distributors, technology partners, field teams, and regional operators. A referral may contain an account relationship, a site detail, a technical need, a commercial expectation, or a claim about a product result. A governance playbook makes eligibility, consent, routing, ownership, evidence, incentive, escalation, and recovery explicit.

Start with the decision rights: who may invite, approve, accept, reject, route, compensate, communicate, pause, investigate, and restore. A referral program is not automatically trustworthy because it has a landing page or an incentive. It needs a service contract that protects the referred person and the operating teams.

The GOV.UK Service Standard offers a way to ask whether user need, joined-up work, and measurable outcome remain connected. It is not a referral-program standard or energy-sector authorization; use it only to trace the referral to an accountable next action.

Define eligibility and non-fit rules

Document who can refer, who can be referred, the approved product or service, territory, relationship, consent state, customer status, partner status, and exclusion list. Define whether a referral is a lead, introduction, service request, support issue, partner opportunity, research contact, or unknown.

Non-fit conditions may include an unapproved region, a restricted site, a conflict of interest, missing consent, duplicate relationship, unsupported technical need, an existing support incident, a request outside capacity, or an incentive that could distort a regulated or safety-sensitive decision. Do not force an ambiguous referral into a positive state just to keep the queue tidy.

Assign decision rights and controls

Create a RACI-like map for program strategy, eligibility, partner approval, customer communication, claims, incentive policy, data, routing, field or engineering review, finance, privacy, security, support, and stop authority. For each role state propose, supply evidence, review, approve, execute, monitor, correct, communicate, and restore.

The playbook should define version, effective date, change window, audit evidence, conflict route, exception owner, and review forum. A small team can combine roles, but the person rewarded for referral volume should not be the only person deciding quality, serviceability, or incentive risk.

Specify inputs and outputs

Inputs include referral record, source, identity, consent, relationship, account, site or service context, product need, region, partner status, incentive rule, capacity, and existing customer state. Every input should have source, date, owner, purpose, quality state, and retention rule.

Outputs include accepted, rejected, duplicate, nurture, partner route, support route, specialist review, service hold, and unknown. Each output needs a reason, owner, destination, response expectation, communication, evidence, and next review. The Google Analytics campaign and traffic-source guidance can inform source-field collection checks; it does not define referral quality or incentive eligibility.

Protect claims, incentives, and relationships

Record incentive amount or type, eligibility, disclosure, trigger, approval, payment evidence, correction, reversal, and conflict handling. Record every public or private claim about savings, performance, availability, reliability, safety, service, or customer outcome with source, date, scope, reviewer, permission, caveat, and correction owner.

The FTC advertising and marketing guidance is a general substantiation context, not legal advice or approval for an energy referral message. Route technical, safety, regulatory, and financial wording to the relevant specialist. An incentive should never pressure a customer to accept a service that has not passed fit or feasibility review.

Run the operating cadence

Use separate rhythms:

1. Program operations: volume, source health, duplicates, consent, routing age, response, and capacity.
2. Quality and claims: eligibility, reason codes, serviceability, technical review, incentive exceptions, and correction.
3. Partner and customer review: experience, complaints, fairness, disclosure, handoffs, and unresolved relationships.
4. Performance and decision: mature referrals, downstream outcome, cost, learning, and resource trade-offs.

Each forum needs a versioned pre-read, decision requested, quorum, owner, dissent, action due date, escalation path, and next review. Preserve prior program rules and report versions so a new partner or incentive does not rewrite historical performance.

Add a monthly control review for inactive referrals, rejected incentives, duplicate relationships, unresolved partner questions, specialist wait, and customer complaints. The output should identify a pattern, an owner, a containment action, a correction deadline, and the evidence needed to decide whether the program rule or only the data needs repair.

Make evidence and quality visible

The NIST Information Quality Standards offer prompts for usefulness, objectivity, integrity, and correction. They do not certify an energy referral system. Label evidence observed, reported, inferred, disputed, stale, or unknown, and attach denominator, cohort, maturity, source, owner, and limitation.

Separate referral submission, identity validation, fit, acceptance, serviceability, response, opportunity, and mature outcome. A high submission count may reflect an incentive, a partner campaign, duplicate traffic, or an ambiguous offer. Do not claim referral success before the relevant cohort is mature.

Protect privacy and operational resilience

Map purpose, data minimization, roles, access, consent, retention, correction, deletion, regional boundary, subprocessors, export, incident contact, and offboarding. Apply the NIST Privacy Framework to structure purpose, control, communication, and protection questions; it is voluntary context, not legal authorization for an energy referral data flow.

Test an opt-out, duplicate account, changed relationship, withdrawn consent, site detail that should not be shared, partner removal, unavailable specialist, source outage, incorrect incentive, and a support incident arriving through the referral route. The safe path should suppress or reroute the record, preserve evidence, notify the right owner, and prevent an unserviceable promise.

Design escalation and rollback

Escalate when consent or purpose is unclear, a technical or safety claim lacks proof, an incentive conflicts with policy, a referred person is routed to an unsuitable service, duplicates rise, capacity is exceeded, a partner misrepresents the offer, or an audit trail is lost.

Contain first: pause the affected invite, source, partner, incentive, route, or message; preserve records; notify the stop authority; and set a recheck. Rollback should restore prior eligibility, routing, incentive, disclosure, partner status, suppression, report, and communication. Keep the decision log and distinguish correction from program failure.

Review the partner experience separately from the internal queue. A referral may be technically routed while the partner lacks context, the customer receives duplicate outreach, or an installer sees an obligation the program never approved. Add a partner-facing correction owner, a customer communication template, and a fairness check to the operating record.

Use the Energy-Technology Referral Governance Playbook

Complete one playbook record:

• Purpose: customer job, program decision, product/service, territory, objective, and non-goals.
• Eligibility: referrer, referred party, relationship, consent, account, region, serviceability, exclusions, and unknown.
• Decision rights: strategy, approval, claims, incentive, data, routing, specialist, finance, privacy/security, stop, and restore.
• Inputs: source, identity, consent, context, partner, incentive, capacity, quality, owner, and retention.
• Outputs: state, reason, destination, response, communication, evidence, owner, and next review.
• Claims/incentives: wording, source, scope, reviewer, disclosure, trigger, payment, correction, and reversal.
• Cadence: operations, quality/claims, partner/customer, performance, quorum, pre-read, and escalation.
• Evidence: stages, cohort, denominator, maturity, source, limitation, confidence, and unknowns.
• Controls: privacy, security, capacity, fairness, duplicate, incident, and audit trail.
• Rollback: invite, partner, incentive, eligibility, route, suppression, report, communication, and proof.

The playbook is complete when an energy technology company can show who may make each referral decision, what evidence supports it, how the referred person is protected, how exceptions escalate, and how the prior program state can be restored. Keep the playbook non-indexable until editorial, overlap, claims, specialist, analytics, privacy, security, and canonical reviews pass.