Skip to content
PM Surya Ghar hub · troubleshooting

Why PM Surya Ghar joint inspections fail: 8 reasons EPCs lose the subsidy

The joint inspection is the last gate before commissioning and the subsidy. Here are the eight things that fail it most often — and the site and QA habits that pass it the first time.

By the SuryaHub team Updated 19 June 2026 13 min read
TL;DR for site & QA teams
  • The joint inspection is the DISCOM's sign-off that gates commissioning and the subsidy.
  • Most failures are earthing/safety, an unready net meter, or non-ALMM modules.
  • Capacity mismatch and missing geotagged photos or paperwork are close behind.
  • Repeated missed appointments can stall or cancel an application (varies by DISCOM).
  • A failed inspection means fix the defect and re-inspect — the application stays pending.
  • Inspection scope and rules vary by DISCOM and change — verify your DISCOM's current SOP.

The joint inspection is where many PM Surya Ghar jobs stall. After install, your DISCOM inspects the system before it commissions the connection and clears the subsidy. Pass it, and the payout moves. Fail it, and the job sits in limbo. The good news: nearly every failure is preventable with a tight pre-inspection routine.

What the PM Surya Ghar joint inspection is

The PM Surya Ghar joint inspection is the DISCOM's on-site check that the rooftop system is safe, correctly built, and matches the approved application before it is energised. It is "joint" because the DISCOM official inspects with the installer present, and it gates commissioning, the net-meter connection, and the subsidy.

Where it sits in the flow

The inspection comes after installation and before commissioning in the application workflow. A pass leads to the net-meter connection and the subsidy claim; a fail sends the job back for correction. So this single visit decides whether weeks of work convert into a paid subsidy or a stalled file.

Scope varies by DISCOM

The exact inspection scope, the checklist, and the standards referenced (including CEA technical and safety norms) vary by DISCOM and change over time. Treat the reasons below as commonly reported failure patterns. Always verify your DISCOM's current inspection SOP before you book a visit, so you prepare for the right standard.

The 8 reasons joint inspections fail

Joint inspections fail most often on safety, metering, and equipment eligibility — the items the DISCOM is duty-bound to check before energising a connection. Here is each reason, why it happens, and the fix, ordered roughly by how often it appears.

1. Earthing and electrical safety not to standard

Poor earthing is a top failure. Loose or missing earthing, no DC isolator, exposed or undressed cables, and missing surge protection all flag a safety risk. Test earthing, fit the required DC and AC isolators, and dress and label every cable before the visit.

2. Net meter not ready

The inspection checks the metering and grid connection, so a missing, wrong-rated, or faulty bidirectional net meter fails it. Confirm the correct net meter is installed and working before you book the slot. See our stuck-status guide for what to do if metering holds the file.

3. Non-ALMM or non-DCR modules

The scheme requires ALMM-listed, DCR-compliant modules, and from 1 June 2026 List-II cells are mandatory. A module that is not on the current list, or that breaks the DCR rule, can fail the inspection and cause subsidy rejection. Match make, model, and serials to the application and the current list — our ALMM and DCR guide covers the detail.

4. Capacity or size mismatch

If the installed kW differs from the sanctioned load or the approved feasibility size, the inspection flags it. Subsidy is capped on the approved capacity, so match the install to the sanction, and document any agreed change before the visit.

5. Weak structure and mounting

Loose clamps, the wrong tilt or orientation, and poor roof anchoring are quality failures. Build to the design spec, secure the structure against wind load, and make sure the array's tilt and orientation match what was approved.

6. Wrong or missing paperwork

Mismatched serials, missing test reports, or an incomplete form stall the inspection even when the system is sound. Carry the full document set, and make sure serials and capacity match the portal record exactly. See the document checklist by stage.

7. Missing or non-geotagged photos

Many DISCOMs need clear, geotagged stage photos in the record. If they are missing or the geotag is absent, the inspection can be held. Upload complete, geotagged photos before the visit so the digital record is ready.

8. Missed or clashing appointment

An inspection where the site is not ready, the customer is absent, or the slot is repeatedly rescheduled wastes the visit — and can stall or even cancel the application at some DISCOMs. Confirm the slot, the customer's presence, and full readiness before the official arrives.

Reason → cause → fix table

Use this as a pre-inspection scorecard. Walk each row before you book the slot, and you remove the most common failure points. Treat causes as commonly reported patterns, not a single official checklist.

Earthing & safety not to standard
Cause: Loose or missing earthing, no DC isolator, poor cable management
Fix: Test earthing; fit DC/AC isolators; dress and label all cables before the visit.
Net meter not ready
Cause: Meter not installed, wrong rating, bidirectional meter missing or faulty
Fix: Confirm the correct net meter is installed and working before booking the inspection.
Non-ALMM / non-DCR modules
Cause: Module not on the current list, DCR rule not met
Fix: Use only ALMM-listed, DCR-compliant modules; keep make, model and serials matching the application.
Capacity / size mismatch
Cause: Installed kW differs from sanctioned load or approved size
Fix: Match installed capacity to the sanctioned feasibility; document any change before inspection.
Structure & mounting weak
Cause: Loose clamps, wrong tilt, no proper roof anchoring
Fix: Build to spec; secure the structure; ensure tilt and orientation match the design.
Wrong or missing paperwork
Cause: Mismatched serials, missing test reports, incomplete form
Fix: Carry the full document set; match serials and capacity to the portal record.
Photos / geotags missing
Cause: Required stage photos not uploaded or not geotagged
Fix: Upload clear, geotagged stage photos before the visit so the record is complete.
Missed or clashing appointment
Cause: No site readiness, customer absent, repeated reschedules
Fix: Confirm the slot, customer presence and readiness; a repeatedly missed visit can stall or cancel.

Source: commonly reported DISCOM inspection experience and the National Portal flow; scope varies by DISCOM — verify the current SOP.

Missed appointments and the cancellation risk

A repeatedly missed or rescheduled inspection appointment is a quiet way to lose a subsidy, because some DISCOMs may stall or cancel the application after several misses. The exact rule varies by DISCOM, so treat any missed slot as a real risk, not a minor delay.

Why visits get wasted

Most wasted visits trace to three things: the site is not actually ready, the customer is absent to give access, or there is a scheduling clash on the EPC side. Each of these is in your control. Confirm readiness the day before, brief the customer to be present, and protect the slot in your team's calendar.

Verify the rule, do not assume

We do not state a fixed "cancel after N misses" rule, because it differs by DISCOM and changes. Confirm your DISCOM's current cancellation and rescheduling policy, and how to formally request a new slot, before you rely on any number. When in doubt, treat the first slot as the only slot.

What to do after a failed inspection

After a failed inspection, fix every flagged defect, gather evidence of the correction, and request a re-inspection promptly — the application stays pending until you pass. A failure is a delay, not a dead end, if you act fast.

Work the defect note

Get the DISCOM's defect note in writing, and treat it as your punch list. Fix each item, take a clear before-and-after photo, and update the job record. Do not rebook until every flagged point is genuinely resolved, or you risk a second failure and more delay.

Re-inspection rules vary

Re-inspection timelines, and any re-inspection fee, differ by DISCOM and change. Confirm the current process — how to request the re-visit, the expected wait, and any charge — with your DISCOM. Keep the whole defect-and-fix trail in the claim file so the subsidy is defensible later.

Prevention checklist

The best inspection is a boring one — everything ready, nothing flagged. Run this checklist before you book the DISCOM slot.

Before you book the inspection
  • Earthing tested; DC and AC isolators fitted; surge protection in place.
  • Net meter installed and working, correct rating, bidirectional.
  • ✓ Modules are ALMM-listed and DCR-compliant; make, model, serials match the application.
  • Installed capacity matches the sanctioned load and approved size.
  • Structure secure; clamps tight; tilt and orientation per design.
  • ✓ Cables dressed and labelled; workmanship clean.
  • Geotagged stage photos uploaded; document set complete.
  • Slot, customer presence and access confirmed the day before.

For the full stage-by-stage version, use our pre-inspection checklist.

How SuryaHub helps you pass the inspection

SuryaHub turns inspection readiness into a routine your crew cannot skip. The mobile field app runs a pre-inspection checklist on site, captures geotagged stage photos and equipment serials, and flags anything missing before the DISCOM arrives. The project module keeps installed capacity, serials, and documents matched to the portal record, so the inspection has nothing to flag. SuryaHub does not perform the inspection — it makes sure you walk in ready. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and the figures here are scheme facts, not guarantees.

Walk into every inspection ready

See how SuryaHub runs the checklist and captures geotagged proof on site.

Book a Demo

Frequently asked questions

Why did my PM Surya Ghar inspection fail?+

A PM Surya Ghar inspection most commonly fails because of poor earthing or safety, a net meter that is not ready, non-ALMM modules, a capacity mismatch, weak mounting, or missing paperwork and photos. Fix the flagged item, then book a re-inspection. Inspection scope varies by DISCOM, so verify the current standard.

What happens after a failed PM Surya Ghar joint inspection?+

After a failed PM Surya Ghar joint inspection, the DISCOM records the defects, and you must correct them and request a re-inspection. The application stays pending until you pass. Keep the defect note, fix every flagged item, and rebook promptly. Re-inspection rules and any fees vary by DISCOM, so confirm the current process.

Can a PM Surya Ghar application be cancelled for missed inspections?+

Some DISCOMs may stall or cancel a PM Surya Ghar application after repeated missed or rescheduled inspection appointments, though the exact rule varies by DISCOM. Confirm the slot, the customer's presence and full site readiness before the visit. Verify your DISCOM's current cancellation and rescheduling policy before you rely on it.

Does the net meter need to be ready before the PM Surya Ghar inspection?+

Yes, in most cases the correct net meter should be installed and working before the PM Surya Ghar joint inspection, because the inspection checks the metering and grid connection. A missing or wrong-rated meter is a common failure. Confirm the metering step and sequence with your DISCOM, as the order can vary.

Will non-ALMM modules fail a PM Surya Ghar inspection?+

Yes. Non-ALMM modules can fail a PM Surya Ghar inspection and cause subsidy rejection, because the scheme requires ALMM-listed and DCR-compliant modules. Make sure the make, model and serials match the application and the current list. ALMM and DCR rules change, so verify the current requirement with MNRE before installing.

How does SuryaHub help pass PM Surya Ghar inspections?+

SuryaHub runs a pre-inspection checklist, captures geotagged stage photos and serials with the mobile field app, and keeps capacity and documents matched to the portal record, so fewer items get flagged. SuryaHub does not perform the inspection. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL.

Sources & references

Inspection scope, the cancellation-after-missed-appointments rule, and the standards referenced vary by DISCOM and change. The notes here come from primary government sources and commonly reported experience — re-confirm against your current DISCOM SOP before you act.

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

Method: Failure reasons are drawn from commonly reported DISCOM inspection experience and re-checked every 30 days. Inspection scope and the cancellation rule vary by DISCOM — verify the current SOP. 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