In this docket
Five interlinked artefacts, produced in sequence with a review gate between each.
About the app
What Electra Consumer is and who it serves.
The problem. Consumers of electricity distribution companies still depend on physical service centres, call-centre queues and disconnected portals for routine tasks — applying for a connection, paying a bill, reporting an outage. The experience is fragmented across consumer categories, opaque about status, and hard to use on a phone.
The product. One app for everything a consumer needs from their discom: guided, trackable, mobile-first flows for applications, complaints and payments — with transparent status, timelines and receipts — usable by first-time smartphone users across languages and low-connectivity conditions.
Key facts
What it covers
📝 Applications
- New connection (all categories)
- Load enhancement / reduction
- Disconnection & reconnection
- Category change · name transfer
- Rooftop solar / net metering (prosumer)
🛠️ Complaints
- No-supply / outage · billing disputes
- Meter & voltage faults
- Conversational AI (voice) intake
- Safety fast-path + helpline
- Ticket lifecycle with SLA & escalation
💳 Payments
- Electricity bills & prepaid recharge
- Application fees & security deposits
- Bottom-sheet breakdown → pay → receipt
- Auto-pay, history, refunds
👤 Account
- Multiple linked connections (CA numbers)
- KYC & document locker
- Language & comms preferences · DPDP consent
🔔 Notifications
- Bill due & payment alerts
- Application / complaint status updates
- Outage & maintenance notices
🔑 Auth & onboarding
- Two-step mobile-OTP login
- Link connection via CA number
- Guest bill-pay without login
Who it serves
Success targets (12 months)
How this docket was built
Sequential stages, each signed off before the next began — so every artefact is consistent with the ones before it.
Locked the fundamentals before writing anything: India discom context, mobile-first + responsive web, all consumer categories (domestic → temporary), and a staged delivery with review gates.
20 sections: vision, personas, scope, requirement tables with IDs + P0–P2 priorities + MVP/fast-follow/later phasing, non-functional requirements, KPIs, release plan, risks & open questions.
✓ Gate: reviewed & signed offNavigation model (tab bar + global header), full sitemap, screen inventory with per-screen states, four end-to-end flow diagrams, a nine-object entity model and the shared state patterns.
✓ Gate: reviewed & signed offA deliberately monochrome, grey-box clickable prototype — 25 screens wired to the IA — to lock structure and flows before any visual design.
✓ Gate: wireframes finalisedReference screens translated into a system — Figtree type, indigo accent, 4px corners, bordered badges, task cards, colored steppers — then refined through iteration: bottom-sheet payments, labelled FABs, hamburger drawer, two-step auth.
Thirty gradient-shaded SVG icons — receipts, bolts, charts, meters, payment methods — hand-built to the reference's 3D style and wired into every card, tile and row.
The design language was distilled into a portable, shareable spec; the entire docket (this page, PRD, IA) was restyled to the same system so the pack reads as one product.
✓ Docket complete — ready for review