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

When DISCOM and portal blame each other

For “When DISCOM and portal blame each other”, save a dated screenshot of the portal stage.

Start here

For “When DISCOM and portal blame each other”, save a dated screenshot of the portal stage.

What applies to this exact problem

  1. Save a dated screenshot of the portal stage.
  2. Get the DISCOM/service reference for the same application.
  3. Ask the DISCOM: “What exact stage is complete, on what date, and what reference/data push proves it?”
  4. Ask portal support: “Which exact input/action is still missing from this application ID?”
  5. Put both answers in one grievance rather than opening unrelated tickets.
  6. If the vendor is the missing owner, ask for the specific document/installation completion submission they made.

Check these first

  • Save a dated screenshot of the portal stage.
  • Get the DISCOM/service reference for the same application.
  • Ask the DISCOM: “What exact stage is complete, on what date, and what reference/data push proves it?”.

Fix it in this order

  1. Save a dated screenshot of the portal stage.
  2. Get the DISCOM/service reference for the same application.
  3. Ask the DISCOM: “What exact stage is complete, on what date, and what reference/data push proves it?”.
  4. Ask portal support: “Which exact input/action is still missing from this application ID?”.
  5. Put both answers in one grievance rather than opening unrelated tickets.
  6. If the vendor is the missing owner, ask for the specific document/installation completion submission they made.
  7. Ask the DISCOM: “What exact stage is complete, on what date, and what reference/data push proves it?” Ask portal support: “Which exact input/action is still missing from this application ID?” Put both answers in one grievance rather than opening unrelated tickets.

Evidence to keep

  • Signed quote and scope — keep it with the evidence for “When DISCOM and portal blame each other”.
  • Module/inverter serials and warranty — keep it with the evidence for “When DISCOM and portal blame each other”.
  • DISCOM/portal application IDs — keep it with the evidence for “When DISCOM and portal blame each other”.
  • Generation data, photos, and installer tickets — keep it with the evidence for “When DISCOM and portal blame each other”.

Do not make it harder

  • Paying the final amount before checking agreed milestones For “When DISCOM and portal blame each other”, that can hide whether the underlying issue is actually resolved.
  • Assuming low generation is automatically a bad panel For “When DISCOM and portal blame each other”, that can hide whether the underlying issue is actually resolved.
  • Treating installer completion as DISCOM/subsidy completion For “When DISCOM and portal blame each other”, 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 “When DISCOM and portal blame each other”.
  • You have enough written evidence to prove the issue is finished if it returns later for “When DISCOM and portal blame each other”.

If this still isn't resolved

  1. Installer/vendor grievance State the unresolved issue explicitly: “When DISCOM and portal blame each other”.
  2. DISCOM/portal grievance route State the unresolved issue explicitly: “When DISCOM and portal blame each other”.
  3. Consumer forum or other official remedy where appropriate State the unresolved issue explicitly: “When DISCOM and portal blame each other”.

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