Build a causation timeline

Start here

For “Build a causation timeline”, evidence. Why it matters. Pre-install roof condition/photos. Shows whether a defect existed earlier. Installation/mounting drawings. Locates roof penetrations and attachment points. Date leak first appeared. Links timing to installation or later weather/work. Rain event and leak pattern. Helps reproduce or diagnose the water path. Photos of penetrations/flashing. Preserves.

What applies to this exact problem

Check these first

• Evidence: Why it matters.
• Pre-install roof condition/photos: Shows whether a defect existed earlier.
• Installation/mounting drawings: Locates roof penetrations and attachment points.

Fix it in this order

1. Evidence: Why it matters.
2. Pre-install roof condition/photos: Shows whether a defect existed earlier.
3. Installation/mounting drawings: Locates roof penetrations and attachment points.
4. Date leak first appeared: Links timing to installation or later weather/work.
5. Rain event and leak pattern: Helps reproduce or diagnose the water path.
6. Photos of penetrations/flashing: Preserves condition before repair.
7. Installer and roofer reports: Creates competing/independent technical explanations.

Evidence to keep

• Signed quote and scope — keep it with the evidence for “Build a causation timeline”.
• Module/inverter serials and warranty — keep it with the evidence for “Build a causation timeline”.
• DISCOM/portal application IDs — keep it with the evidence for “Build a causation timeline”.
• Generation data, photos, and installer tickets — keep it with the evidence for “Build a causation timeline”.

Do not make it harder

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

If this still isn't resolved

1. Installer/vendor grievance State the unresolved issue explicitly: “Build a causation timeline”.
2. DISCOM/portal grievance route State the unresolved issue explicitly: “Build a causation timeline”.
3. Consumer forum or other official remedy where appropriate State the unresolved issue explicitly: “Build a causation timeline”.

Parent-guide references

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

• National Rooftop Solar Knowledge Centre
• National Consumer Helpline
• MNRE solar standards and quality-control documents

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