Report updated May 30, 2026
PG&E Report It
For pG&E customers and residents within the service territory who need to report non-emergency electrical hazards.
PG&E Report It is a struggling reference app that is completely free. With a 3.1/5 rating from 134 reviews, it struggles with user retention. Users particularly appreciate quick resolution of reported safety issues by field inspectors following successful submission, though frequent application crashes during the report submission process prevent critical safety notifications remains a common concern.
What is PG&E Report It?
PG&E Report It is a utility app for iOS and Android that allows residents to report non-emergency electrical infrastructure hazards.
Users hire the app to alert the utility company to safety risks, serving the job of reducing local infrastructure hazards.
Current Momentum
v5.1 · 2w ago
Maintenance- Added video file viewing support.
- Improved accessibility features.
Active Nemesis
Fragmented niche
No dominant direct rival identified yet — see Other Rivals below.
Other Rivals
7-Day Rank Pulse 🇺🇸
ReferenceNo ranking data
Rating Pulse 🇺🇸
Recent User MoodAI-powered deep analysis surfacing high-signal insights. Still in beta, accuracy improves daily. For informational purposes only.
What makes this app unique?
What Does It Look Like?
How Is The App's Momentum Right Now?
Loading...
What Are The Key Features?
Submission of photos or videos of electrical equipment concerns with location data
View safety concerns and PG&E findings submitted by other users
Push alerts for updates on submitted safety concerns from review to closure
In-app gallery of safety issue examples to assist users in identifying hazards
How much does it cost?
- Free utility app with no paid tiers or in-app purchases
The app operates as a zero-cost utility tool provided by the utility company to manage infrastructure safety reporting.
Who Built It?
Pacific Gas & Electric Company
View Publisher Intel →Enrichment in progress
Publisher profile available very soon
What other apps does Pacific Gas & Electric Company make?
What do users think recently?
Low confidence · Latest 60 of 75 total reviews analyzed · Based on 75 reviews. Signal may be noisy.
How did the latest release land?
What is the recent mood?
Recent user voice shows a upset sentiment. Users appreciate quick resolution of reported safety issues by field inspectors following successful submission, but report frequent application crashes during the report submission process prevent critical safety notifications and excessive and intrusive permission requirements for media access discourage users from reporting hazards.
What Users Love
What Frustrates Users
What Users Want
What is the competitive landscape for PG&E Report It?
How's The Reference Market?
Market outlook for this category
Available very soon
The rivals identified
Peers
Leverages a massive network effect with thousands of municipalities already integrated into the platform
Automated issue routing technology significantly reduces the manual administrative burden on internal safety teams
Features a dedicated neighborhood services portal that contextualizes reports within specific local geographic zones
Provides a structured request tracking system that keeps users informed throughout the resolution lifecycle
Integrates a broad city services directory beyond just safety hazards, increasing daily active utility
Utilizes a centralized user account system that allows for persistent history of all service requests
Offers robust multi-language support to ensure accessibility across diverse urban demographic populations
Provides transparent case status tracking which builds higher user trust than blind submission workflows
New Kids on the Block
Employs an intuitive swipe-based interface that simplifies complex file management for non-technical users
The outtake for PG&E Report It
Strengths to defend, gaps to attack
Core Strengths
- Direct channel for infrastructure maintenance reduces liability
- Public feed transparency builds community trust
Critical Frictions
- Frequent submission crashes on current build
- Intrusive media permissions block reporting
- Authentication failures prevent core feature access
Growth Levers
- Integrate with municipal 311 platforms to increase visibility
- Expand safety education content to reduce invalid reports
Market Threats
- SeeClickFix's automated routing efficiency
- User migration to general-purpose municipal reporting apps
What are the next best moves?
Stabilize submission pipeline because crashes are the top complaint → increase successful report volume
Sentiment analysis identifies submission crashes as the primary barrier to utility.
Trade-off: Pause new feature development for the public feed — stability is the current bottleneck.
Audit permission requirements because users cite intrusive access as a reporting barrier → improve conversion
User feedback explicitly links media library access requirements to report abandonment.
Trade-off: Same-quarter capacity available — no major lever displaced.
A counter-intuitive read
The app's biggest risk is not its low rating, but its lack of integration with municipal 311 systems, which makes it an isolated utility in an increasingly centralized reporting market.
Feature Gaps vs Competitors
- Automated issue routing (available in SeeClickFix but absent here)
- Broad municipal services directory (available in MyLA 3-1-1 but absent here)
Key Takeaways
The app provides a necessary safety link but fails on core stability, so the PM must prioritize submission reliability over feature expansion to prevent total user churn.
Where Is It Heading?
Stable
The market for infrastructure reporting is consolidating around automated, multi-service platforms that reduce administrative overhead. PG&E Report It remains exposed due to its manual, single-purpose design and technical instability, which will continue to drive users toward more reliable municipal alternatives.
Frequent application crashes during the submission flow erode user trust and prevent critical safety data intake.
Recent updates focused on stability and accessibility, but failed to address the core permission-related churn drivers.