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

Use the stage, owner, proof method

What is stuck. Likely owner. Evidence to ask for. Application not reaching DISCOM / upload or edit problem. Portal/IT support.

Start here

What is stuck. Likely owner. Evidence to ask for. Application not reaching DISCOM / upload or edit problem. Portal/IT support. Application ID, error screenshot, backend/status reference. Technical feasibility pending. DISCOM. Feasibility application/service reference and decision/status. Installation done, inspection pending. DISCOM + vendor readiness. Completion submission and inspection request/acknowledgement..

What applies to this exact problem

What is stuckLikely ownerEvidence to ask for
Application not reaching DISCOM / upload or edit problemPortal/IT supportApplication ID, error screenshot, backend/status reference
Technical feasibility pendingDISCOMFeasibility application/service reference and decision/status
Installation done, inspection pendingDISCOM + vendor readinessCompletion submission and inspection request/acknowledgement
Inspection done, net meter pendingDISCOMInspection completion + net-meter work/order reference
DISCOM says complete, portal unchangedDISCOM data hand-off / portal syncCompletion/data-push timestamp and portal grievance
Commissioned, subsidy still pendingScheme/subsidy workflowCommissioning status, bank details, subsidy-stage reference

Check these first

  • What is stuck: Likely owner.
  • Application not reaching DISCOM / upload or edit problem: Portal/IT support.
  • Technical feasibility pending: DISCOM.

Fix it in this order

  1. What is stuck: Likely owner.
  2. Application not reaching DISCOM / upload or edit problem: Portal/IT support.
  3. Technical feasibility pending: DISCOM.
  4. Installation done, inspection pending: DISCOM + vendor readiness.
  5. Inspection done, net meter pending: DISCOM.
  6. DISCOM says complete, portal unchanged: DISCOM data hand-off / portal sync.
  7. Commissioned, subsidy still pending: Scheme/subsidy workflow.

Evidence to keep

  • Signed quote and scope — keep it with the evidence for “Use the stage, owner, proof method”.
  • Module/inverter serials and warranty — keep it with the evidence for “Use the stage, owner, proof method”.
  • DISCOM/portal application IDs — keep it with the evidence for “Use the stage, owner, proof method”.
  • Generation data, photos, and installer tickets — keep it with the evidence for “Use the stage, owner, proof method”.

Do not make it harder

  • Paying the final amount before checking agreed milestones For “Use the stage, owner, proof method”, that can hide whether the underlying issue is actually resolved.
  • Assuming low generation is automatically a bad panel For “Use the stage, owner, proof method”, that can hide whether the underlying issue is actually resolved.
  • Treating installer completion as DISCOM/subsidy completion For “Use the stage, owner, proof method”, that can hide whether the underlying issue is actually resolved.

How you know it is fixed

  • The official record and your real-world result agree for “Use the stage, owner, proof method”.
  • You have enough written evidence to prove the issue is finished if it returns later for “Use the stage, owner, proof method”.

If this still isn't resolved

  1. Installer/vendor grievance State the unresolved issue explicitly: “Use the stage, owner, proof method”.
  2. DISCOM/portal grievance route State the unresolved issue explicitly: “Use the stage, owner, proof method”.
  3. Consumer forum or other official remedy where appropriate State the unresolved issue explicitly: “Use the stage, owner, proof method”.

Parent-guide references

These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.

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