Skip to main content
GullySystem
A practical guide

Solar subsidy and net metering file tracker: who is holding it up

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 4 min read

In this guide 6 sections
The short answer

Break every utility file into its approval stages and record, for each, the person it waits on and the date it arrived there. A stalled file then shows itself. Chase the oldest waiting stage first and attach the proof of every submission, whether that is an acknowledgement number, an email or a scanned receipt.

Why files stall without anyone noticing

A net metering file passes through the installer, the customer, the utility’s technical office, an inspector and sometimes also a subsidy agency. Each believes someone else holds it.

The liaison coordinator keeps status in memory or a phone chat, so nobody else knows whether the feasibility letter arrived or the meter inspection was booked.

Customers feel it first. They ring the sales rep who sold the system months ago, and the rep has nothing to say because the file sits in a coordinator’s phone.

Stages worth tracking

List the stages your utility uses, such as application filed, feasibility or technical approval, installation complete, inspection, agreement signed, meter swap and subsidy claim. Regions differ, so copy the order from your last ten completed files, not from a neighbour’s checklist or a website that may be years out of date.

For every stage, store four things. Store the date it started, the person or office it waits on, the document that proves it started, and the next expected date.

Pending tells nobody anything. Waiting on inspector since the ninth is a sentence that someone can act on this morning, so write every status in that shape.

  • Stage name and the date it began
  • Holder: installer, customer, utility or agency
  • Proof: acknowledgement number, email or receipt
  • Next expected date and reminder owner

Name the holder, not the status

Group the board by holder. Expect the installer’s pile to surprise you, because missing signatures, a wrong sanction load or an unreadable single line diagram stay on your desk. The utility is not at fault there.

A pending bank loan or a roof not ready appears as a customer holder with a date, so sales can call before the utility rejects the application.

Utility delays need evidence. A note that says followed up twice, with dates and names, is worth more in an escalation letter than any general complaint about slow offices.

Set ageing rules that trigger a call

Choose a waiting limit per stage, perhaps two weeks for technical approval and one week for inspection, and let any file that crosses its limit turn amber. Amber files join the coordinator’s morning list.

Write down who escalates and to whom. The first call goes to the section engineer, the second to the divisional office, and the third goes through the customer or an association. A fixed ladder keeps files moving.

Give every closure a reason code. Rejected for load mismatch, returned for documents and approved are enough to start, and after a quarter these codes show which mistakes your own team keeps repeating.

  • Amber at the limit, red at double
  • Daily list of files past a limit
  • Escalation ladder with names and numbers

Give customers a status they can read

Once stages and holders are recorded, a link or short message can tell the customer where the file is, who holds it and what happens next.

That cuts calls to the sales rep and sets expectations about the meter swap, and the customer sees why commissioning is waiting before the final payment falls due.

Start this week with a plain sheet. Take every open file, fill in the stage, holder and since-date, sort by oldest, and make the first ten calls before lunch.

Utility file tracker

Keep one row per customer file, with columns for file number, customer, system size, current stage, holder, days waiting, proof reference, next action and escalation level. A side block lists the stage names in order with the waiting limit for each, and a footer block records the closure reason code.

Open a blank worksheet to print

Questions owners ask

Which stages should the tracker cover?

Use the stages your own utility and subsidy agency require, in their order, copying them from your last few completed files and adjusting whenever the rules change. Do not invent your own.

How do I know if the delay is mine or the utility’s?

If the holder is the installer or the customer, the delay is yours to clear, and if it is the utility, dated proofs support your escalation. Record the holder at every stage.

Who should update the tracker?

The liaison coordinator should update it on the same day a document is submitted or received, because a tracker updated weekly is already out of date by Friday. One owner, one tracker.

Can customers see their file status?

They can, if you share a simple status with the stage, the holder and the next step, and keep escalation ladders and internal notes behind the staff login. Share the status, not the strategy.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements