Eligibility Is the Bottleneck

Every energy programme starts with a question that sounds like paperwork. Is this customer eligible? For demand aggregation, it depends on their meter, their network area and their existing retail contract. For rooftop solar, it depends on the roof, the connection and whoever holds the lease. For a storage subsidy, it depends on all of that plus a scheme rule that changed last quarter.

None of this is the interesting part of the business, which is exactly why it tends to be the part nobody owns.

What the delay actually costs

An eligibility check that takes three days does not cost three days. It costs the customer’s attention, which was highest the moment they applied. By the time an answer arrives, the competing quote has landed and the person who was ready to sign has gone back to thinking about it.

It also costs the same work twice. When the answer is “not yet, we need your meter number”, the application does not pause — it restarts. Somebody re-reads the file, re-establishes context, and re-sends a request that may have already been answered in a different inbox.

The pattern is consistent across the programmes we have worked on: the operational cost sits in the handoffs, not in the assessments. The assessment itself is usually a few minutes of judgement. The waiting either side of it is measured in days.

Rules change, so encode them as data

The instinct is to build the current scheme rules into the application flow. That works until the rules move, and scheme rules always move — thresholds shift, regions are added, an incentive is capped mid-year.

Programmes that survive those changes treat eligibility as a set of rules held as data, evaluated against what is known about the customer, and versioned so an approval made in March can still be explained in November. That last part matters more than it sounds. When a regulator or an auditor asks why a customer was accepted, “the system said so” is not an answer unless you can show which rules were in force at the time.

Give the customer the state, not a queue position

The most useful thing an applicant can see is not an estimated wait. It is what is outstanding and who has it. “We are waiting on your network’s confirmation” is a different experience from silence, even when the elapsed time is identical.

The same view helps the operational team. When a case is visibly waiting on a third party rather than sitting unassigned, nobody spends the morning working out whose turn it is.

Most of the gain here comes before any of it gets clever. Make the rules explicit, make the current state visible to everyone who touches the case, and the days spent re-establishing context stop being part of the process.