Skip to content
PM Surya Ghar hub · troubleshooting

PM Surya Ghar application stuck at "feasibility approved": what to do next

A status-by-status guide for EPC coordinators and homeowners — what each stalled stage really means, whose turn it is, and the exact next step to push the application forward.

By the SuryaHub team Updated 19 June 2026 12 min read
TL;DR
  • Many "stuck" PM Surya Ghar applications are waiting on you, not the DISCOM.
  • "Feasibility approved" is your cue to install and report — it rarely moves on its own.
  • "Net meter pending" usually needs the metering request logged and the fee paid.
  • Status not updating after inspection? Get the result in writing and ask the DISCOM to update.
  • First diagnose whose turn it is, then take the matching action, then escalate if it is genuinely overdue.
  • Status labels and stage gates vary by DISCOM and change — verify against the current National Portal.

A PM Surya Ghar application that sits on one status is the quiet killer of an EPC pipeline. The job is not failing — it is just not moving, and cash is tied up. The fix starts with one question for each stalled status: whose turn is it? This guide answers that for every common stuck stage.

Why PM Surya Ghar applications get stuck

PM Surya Ghar applications get stuck mostly because the next action sits with someone who has not done it yet — often the EPC, sometimes the DISCOM, sometimes a backlog. The portal status is a snapshot of where the file waits, not a sign that something is broken.

Three kinds of "stuck"

There are three honest reasons a file stalls. First, your turn — feasibility is approved and you have not installed or reported yet. Second, the DISCOM's turn — an inspection, a meter, or a data update is pending on their side. Third, a data problem — a query you missed, a mismatch, or a bug. The right action depends entirely on which of the three it is.

Audience note: coordinators and homeowners

EPC coordinators track many files and need to triage which are genuinely overdue. Homeowners usually have one file and want to know if it is normal or stuck. The diagnosis is the same for both: read the status, decide whose turn it is, and act or wait accordingly.

The PM Surya Ghar stages, in order

Knowing the normal order makes a stuck status easy to read. The full application workflow runs roughly like this: apply → feasibility approval → install → report installation → joint inspection → commissioning and net meter → subsidy claim → DBT payout.

Each gate hands off to someone

At every gate, the file passes between you and the DISCOM. Feasibility approval hands the ball to you. Reporting the install hands it back to the DISCOM for inspection. The net-meter step is shared. The final payout depends on the customer's bank seeding. When you know who holds the ball at each gate, "stuck" stops being a mystery.

Labels differ — read the meaning, not the word

The exact status labels differ by DISCOM and change with portal updates. One DISCOM's "feasibility approved" may read differently elsewhere. Focus on the stage the label represents, not the precise wording, and verify the current flow against the National Portal.

Stuck status → next action table

Match your current status to its likely cause and the next action. Treat the causes as commonly reported patterns; the precise labels and gates vary by DISCOM.

Application submitted (no movement)
Cause: DISCOM queue, document query pending, peak load
Action: Check for any portal query or document request; respond fast; wait through the queue, then follow up with the DISCOM.
Feasibility approved (then nothing)
Cause: Ball is in your court — install not done or vendor not assigned
Action: This is your cue to proceed: confirm the vendor, install the system, then request the next step on the portal.
Installation reported, inspection not scheduled
Cause: Slot not booked, site not confirmed ready, DISCOM backlog
Action: Book the joint-inspection slot; confirm readiness and customer presence; chase the DISCOM if no slot appears.
Inspection done, status not updated
Cause: Defect note pending, DISCOM data-entry lag
Action: Get the inspection result in writing; if passed, ask the DISCOM to update the portal; fix any defect and re-inspect.
Net meter pending
Cause: Meter not installed, DISCOM metering backlog, fee/paperwork pending
Action: Confirm the metering request is logged and any fee is paid; follow up with the DISCOM metering team.
Commissioned, subsidy not credited
Cause: DBT/bank seeding issue, claim under processing
Action: Check the bank-seeding and claim status; this is the disbursement stage, not a portal stall.

Source: commonly reported portal experience and the National Portal flow; status labels vary by DISCOM — verify the current process.

Stuck at "feasibility approved"

If your application is stuck at "feasibility approved", the next move is almost always yours. Feasibility approval means the DISCOM has confirmed the connection can take the rooftop system — it is a green light to install, not a step that progresses by itself.

What to do

Confirm the vendor is assigned, complete the installation to spec, capture the geotagged stage photos and serials, then report the installation on the portal. That report is what triggers the joint inspection. Until you report, the status will not change, no matter how long you wait.

Systems up to 10 kW

Systems of 10 kW or less generally have deemed feasibility under the Electricity (Rights of Consumers) Rules, which can speed this gate. Even so, the install-and-report step is still yours. Verify the current feasibility rule and any size threshold for your DISCOM, as these can change.

Stuck after the inspection

If the joint inspection is done but the status has not moved, the cause is usually a pending defect note or a DISCOM data-entry lag. The inspection result decides the next step, so get it in writing first.

Passed but not updated

If you passed and the portal still shows the old status, that is often a data lag on the DISCOM side. Ask the DISCOM, with the application ID, to update the portal to reflect the pass, and keep the written result in the job file.

Failed or defect raised

If a defect was raised, the file waits for you to fix it and re-inspect. Treat the defect note as a punch list, correct every item with photo evidence, and rebook. Our inspection-failures guide covers the eight common defects and how to clear them.

Stuck at "net meter pending"

"Net meter pending" means the bidirectional meter is not yet installed or recorded by the DISCOM, and it is one of the most common slow points. The net-metering step is shared between you and the DISCOM, so check both sides.

Check the request and the fee

First, confirm the metering request is actually logged on the portal, not just assumed. Then confirm any metering fee or charge is paid and recorded, because an unpaid fee silently holds the step. Once both are clear, follow up with the DISCOM metering team for the install slot.

Backlogs are real

Net-meter installation can sit in a genuine DISCOM backlog, especially in high-demand areas. Net-metering steps, fees, and timelines vary by DISCOM and change. Verify the current process and expected wait with your DISCOM, and chase politely with the application ID if it runs long.

When and how to escalate

Escalate only when a stage sits well past its usual window with no portal query and no DISCOM response to a polite follow-up. A clear, evidence-backed escalation moves faster than a vague complaint, and escalating too early just adds noise.

The escalation ladder

Start with a documented follow-up to the DISCOM helpdesk, quoting the application ID and the date the stage was reached. If that fails, use the portal's grievance or complaint route. Keep every interaction in the job file. Our subsidy-tracking guide covers the disbursement-stage follow-up in detail.

Verify the current path

The escalation channels, helpdesk numbers, and grievance routes change. Verify the current path against the National Portal before you raise a case, and avoid stating a fixed "guaranteed resolution time" — there is no such promise, only the published process.

Prevention checklist

Most stalls are caught early if someone is watching every file. Build these habits so a stuck status never goes unseen for weeks.

Keep applications moving
  • ✓ Assign an owner to every application so no file is orphaned.
  • ✓ Record the date each stage was reached, so you can spot an overdue one.
  • ✓ Treat "feasibility approved" as a task — install and report promptly.
  • ✓ Respond to any portal query the same day it appears.
  • ✓ Confirm the net-meter request and fee are logged, not assumed.
  • ✓ Capture inspection results in writing for every job.
  • ✓ Keep serials, capacity and documents matched to the portal record.
  • ✓ Follow up with the DISCOM before a stage becomes badly overdue.

How SuryaHub helps you clear stuck applications

SuryaHub gives you one view of where every PM Surya Ghar application sits and flags the ones that have stalled past their usual window. The status dashboard shows each file's current stage and how long it has been there, so an overdue "feasibility approved" or "net meter pending" never hides in a spreadsheet. The government-workflow module prompts the next action and keeps documents matched to the portal record. SuryaHub reads your own work, not the government portal — it does not change a status on the DISCOM's system. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and the figures here are scheme facts, not guarantees.

See every stuck file at a glance

See how SuryaHub flags overdue applications and prompts the next step.

Book a Demo

Frequently asked questions

Why is my PM Surya Ghar application stuck at "feasibility approved"?+

A PM Surya Ghar application sits at "feasibility approved" because the next move is yours, not the DISCOM's. Feasibility approval means you can install. Assign the vendor, complete the installation, then report it on the portal to trigger the inspection. If it stays stuck after you report, follow up with your DISCOM.

Why is my PM Surya Ghar status not updating after inspection?+

A PM Surya Ghar status that does not update after inspection usually means a defect note is pending or the DISCOM has a data-entry lag. Get the inspection result in writing. If you passed, ask the DISCOM to update the portal; if a defect was raised, fix it and request a re-inspection. Verify the current flow.

What does "net meter pending" mean on PM Surya Ghar?+

On PM Surya Ghar, "net meter pending" means the bidirectional net meter is not yet installed or recorded by the DISCOM. Confirm the metering request is logged and any fee is paid, then follow up with the DISCOM metering team. Net-metering steps and timelines vary by DISCOM, so verify the current process.

How long should each PM Surya Ghar stage take?+

PM Surya Ghar stage times vary widely by DISCOM, season, and load, so there is no fixed number. Feasibility and inspection can take days to weeks, and disbursement commonly runs 30 to 90 days or more in practice. Treat any timeline as an estimate and verify the current pace with your DISCOM.

When should I escalate a stuck PM Surya Ghar application?+

Escalate a stuck PM Surya Ghar application when a stage sits well past its usual window with no portal query and no DISCOM response to a polite follow-up. Use the portal grievance route or the DISCOM helpdesk with the application ID and evidence. Verify the current escalation path before you raise it.

How does SuryaHub help with stuck PM Surya Ghar applications?+

SuryaHub shows where every application sits, flags the ones that have stalled past their usual window, and prompts the next action so nothing waits unseen. SuryaHub reads your work, not the government portal. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL.

Sources & references

Status labels and stage gates differ by DISCOM and change with portal updates. The notes here come from primary government sources and commonly reported experience — verify against the current National Portal flow before you act.

Written by the SuryaHub team · reviewed against MNRE & National Portal sources · updated 19 June 2026.

Method: Status diagnoses are drawn from commonly reported portal experience and re-checked every 30 days. Status labels and gates vary by DISCOM and change — verify against the current National Portal flow. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.

Change log: 19 Jun 2026 — first published.

The decision · now onboarding pilot EPCs

Run your whole solar business
on one platform.

Stop stitching together Tally, Excel, Sheets and WhatsApp. See the operating system built for India's solar EPCs — on your real projects.

India-first · PM Surya Ghar ready · Cloud or on-prem

Run your solar business on one OS.
Book a Demo