← Full guide: PM Surya Ghar Application Stuck at DISCOM: Escalation Steps

Locate the exact DISCOM stage before escalating

Locate the exact DISCOM stage before escalating. Check the cause, evidence to keep, recovery steps, and escalation.

Start here

A generic 'stuck' complaint is hard to resolve. Identify whether the application is waiting for technical feasibility, inspection, meter work, vendor action, document correction or portal synchronisation.

What applies to this exact problem

A generic 'stuck' complaint is hard to resolve. Identify whether the application is waiting for technical feasibility, inspection, meter work, vendor action, document correction or portal synchronisation.

The facts that change the answer

For this case, the answer can change when current portal stage and last status-change date, DISCOM application or service reference, pending action assigned to consumer, vendor or utility. Escalate the named bottleneck with the portal ID, dates and missing action. A stage-specific complaint is more actionable than 'application pending'.

Verify current status

Current portal stage and last status-change date.

Control point

DISCOM application or service reference.

Check first

Pending action assigned to consumer, vendor or utility.

Keep these records together

Keep portal screenshots with date, submitted documents, inspection or feasibility acknowledgement, DISCOM complaint references in one folder for this case. Name files with dates and retain original PDFs where possible.

RecordUse it to verifyWhy keep it
Portal screenshots with dateCurrent portal stage and last status-change dateSeparates a written fact from a sales statement.
Submitted documentsDISCOM application or service referenceCreates a dated record another reviewer can verify.
Inspection or feasibility acknowledgementPending action assigned to consumer, vendor or utilityLets you challenge the exact field, charge, date or obligation.
DISCOM complaint referencesCurrent portal stage and last status-change dateProtects the decision if a portal, account screen or verbal explanation changes.

What can derail the plan

Pause before the next irreversible step if the vendor says to wait but cannot name the pending stage, a document is re-uploaded repeatedly without checking the rejection reason, someone requests an unofficial payment to accelerate subsidy or meter approval.

  • The vendor says to wait but cannot name the pending stage.
  • A document is re-uploaded repeatedly without checking the rejection reason.
  • Someone requests an unofficial payment to accelerate subsidy or meter approval.

Practical sequence

  1. Pin down the first controlling fact: current portal stage and last status-change date.
  2. Reconcile it against portal screenshots with date and submitted documents.
  3. Test the decision under one realistic adverse case instead of assuming the best outcome.
  4. Record dates, reference numbers and the institution responsible for the next step.
  5. Escalate only the unresolved point; do not restart the case with a vague complaint.

Your go/no-go rule

Escalate the named bottleneck with the portal ID, dates and missing action. A stage-specific complaint is more actionable than 'application pending'.

Check these first

  • State the exact expected result and the exact result you have now.
  • Find the official record that owns the result and compare it with your evidence.
  • Change one thing at a time, then verify the final state before moving on.

Fix it in this order

  1. State the exact expected result and the exact result you have now.
  2. Find the official record that owns the result and compare it with your evidence.
  3. Separate hardware, installer, DISCOM/net-meter, portal, and subsidy status. They are different failure points.
  4. Record system size, module/inverter details, commissioning date, generation data, application IDs, and promised scope.
  5. Compare actual installation and generation with the signed quote, warranty, and portal/DISCOM records.
  6. Ask the responsible party for the exact pending action and owner of that action in writing.
  7. Do not close the job until safety checks, commissioning, monitoring, and applicable net-meter/subsidy records reconcile.

Build the proof pack

  • Signed quote and scope
  • Module/inverter serials and warranty
  • DISCOM/portal application IDs
  • Generation data, photos, and installer tickets

Avoid making the case harder

  • Paying the final amount before checking agreed milestones
  • Assuming low generation is automatically a bad panel
  • Treating installer completion as DISCOM/subsidy completion

How you know it is really fixed

  • The official record and your real-world result agree.
  • You have enough written evidence to prove the issue is finished if it returns later.

If it is still not fixed

  1. Installer/vendor grievance
  2. DISCOM/portal grievance route
  3. Consumer forum or other official remedy where appropriate

Official sources from the full guide

Need the complete context?

This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.

Open the full guide