RTI for MSPDCL Electricity Manipur Consumer Complaint

Electricity consumers in Manipur face some of the most persistent supply-reliability challenges in India — chronic load shedding, transformer failures that take days to repair, billing irregularities, and new connection applications that stall without explanation. Manipur State Power Distribution Company Limited (MSPDCL), the state-owned distributor responsible for electricity supply across the valley and hill districts, is a public authority under Section 2(h) of the Right to Information Act, 2005. For ₹10 and a single application, a Manipur consumer can compel MSPDCL to produce the meter reading records behind a disputed bill, the work order issued for a delayed transformer repair, the official load shedding schedule in force for a feeder, or the processing stage of a stalled new connection application. RTI does not promise a fixed outcome, but it creates the written, accountable record that transforms a verbal complaint into a documented grievance — and that record is far harder for any office to ignore.

What Can You Achieve with RTI to MSPDCL?

Filing an RTI application with MSPDCL can help you:

• Verify the basis of a disputed electricity bill — obtain the actual meter reading date and value, the tariff category applied, and any arrears or surcharges included in the total demand
• Establish whether estimated billing was used — find out if MSPDCL billed you on estimated rather than actual consumption, and for how many consecutive billing cycles
• Obtain a meter accuracy test result — confirm whether your meter has been tested since installation and, if not, compel MSPDCL to disclose the applicable testing policy and the procedure for a consumer-requested test
• Track transformer repair timelines — get the date a fault was reported, the date the repair was sanctioned, the officer responsible, and MSPDCL's own prescribed restoration timelines
• Monitor a new connection application — identify the exact processing stage and the officer handling the application, and compare against the MSERC-prescribed timeline
• Obtain the official load shedding schedule — get the approved roster for your feeder or locality in writing, which is the starting point for challenging outages that exceed the schedule
• Document unplanned outage records — get data on the frequency, duration, and stated causes of unscheduled power cuts on your feeder over a specified period
• Examine action taken on a filed complaint — find out what MSPDCL recorded as the resolution for a complaint you lodged with their helpline or divisional office
• Build a paper trail before escalating — an RTI response showing that MSPDCL has violated its own service norms or MSERC standards is essential evidence for a complaint to the Manipur State Electricity Regulatory Commission (MSERC), the Manipur Information Commission (MIC), or the District Magistrate

Where to File: The Right Authority

MSPDCL as a public authority: Manipur State Power Distribution Company Limited is wholly owned and substantially financed by the Government of Manipur. It is a public authority under Section 2(h) of the RTI Act and is required to designate SPIOs at each of its organisational levels — headquarters, divisions, and sub-divisions. The SPIO at MSPDCL Headquarters, Keishampat, Imphal handles RTI applications for the corporation as a whole.

Sub-Division and Division offices: For matters confined to a specific locality — a billing dispute relating to your consumer number, a transformer fault in your area, or a new connection application submitted at a local office — you should file with the SPIO at the relevant MSPDCL Sub-Division or Division office. Each sub-division is required to designate its own SPIO under Section 5 of the RTI Act. Filing at the Sub-Division level is often more effective for account-specific matters, as the records are held there. If you are unsure of the sub-division's SPIO details, filing at the Headquarters SPIO is a safe fallback; under Section 6(3), the Headquarters SPIO is obligated to transfer the application to the correct office within five days.

First Appellate Authority (FAA): If the SPIO does not respond or provides an incomplete response, file a First Appeal with the First Appellate Authority — the officer senior to the SPIO within MSPDCL, designated for this purpose.

MSPDCL vs. NHPC — an important distinction: The Loktak Power Station at Moirang, Manipur, is operated by NHPC Limited, a Central Government public sector undertaking under the Ministry of Power, Government of India. NHPC is a central government body — RTI against NHPC is filed through the central RTI portal and second appeals go to the Central Information Commission (CIC), not the Manipur Information Commission. Similarly, bulk power allocations from the central grid are handled by central bodies. MSPDCL handles electricity distribution within Manipur and is on the state track. Do not direct a distribution or billing dispute to NHPC, and do not assume that because Manipur's power supply involves NHPC that the second appeal for an MSPDCL matter goes to the CIC — it does not.

Second appeal: MSPDCL is a Manipur State Government body. All second appeals against MSPDCL under Section 19(3) of the RTI Act go to the Manipur Information Commission (MIC), established under Section 15 of the RTI Act, 2005 — not to the CIC.

How to File: Step by Step

Step 1: Gather Your Details

Before drafting the application, collect the following from your electricity bill and any complaint receipts:

• Your consumer account number (also called service connection number) and meter number — printed on every bill
• The billing cycle in dispute (month and year) and the billed amount
• The complaint or grievance reference number if you have already contacted the MSPDCL helpline or visited a divisional office
• Your new connection application reference number (if asking about connection status) and the date of submission
• The date and approximate location of the transformer fault (if asking about repair delay)
• The name of your sub-division or division office and the feeder name or number (printed on some bills, or available at the local MSPDCL office)

Step 2: Draft Your Application

Use the sample RTI draft on this page as a template. Include only the points relevant to your situation — you do not need to use all six. Keep the language factual and specific: mention the consumer number, the billing period, the connection reference, or the feeder name. RTI is an information request, not a complaint — do not ask MSPDCL to fix your problem in the application itself. Ask only for the records and information that document what happened.

Step 3: File Online or by Post

Visit rti.manipur.gov.in, the Government of Manipur's online RTI portal (verify the URL is current before filing, as state portals are revised periodically). Register or log in, select MSPDCL as the public authority, fill in the application form, upload your draft, and pay the ₹10 fee online. Save the acknowledgment with the registration number for tracking.

Alternatively, send the application by registered post to the SPIO, MSPDCL, Keishampat, Imphal, Manipur – 795001, with an Indian Postal Order (IPO) of ₹10 drawn in favour of "MSPDCL". BPL cardholders are exempt from the fee under Section 7(5) of the RTI Act; attach a self-attested copy of your BPL ration card. Do not send cash by post.

Step 4: Track and Follow Up

After filing, track your application using the registration number. MSPDCL must respond within 30 days from the date of receipt of the application. If the information concerns life or liberty — for example, a prolonged power supply disruption affecting a consumer who depends on electricity for medical equipment — the response is due within 48 hours under the proviso to Section 7(1) of the RTI Act.

Step 5: Appeal If Needed

First Appeal (Section 19(1)): If MSPDCL does not respond within 30 days, or if the response is incomplete, incorrect, or evasive, file a First Appeal with the First Appellate Authority (FAA) at MSPDCL. The First Appeal must be filed within 30 days of the date of decision or expiry of the 30-day response period, whichever is applicable. No fee is payable for a First Appeal.

Second Appeal (Section 19(3)): If the First Appeal is also unsatisfactory or goes unanswered, file a Second Appeal with the Manipur Information Commission (MIC) within 90 days of the FAA's decision or the expiry of the FAA's response deadline. The MIC can direct MSPDCL to disclose the information, impose a penalty on the defaulting SPIO of ₹250 per day up to ₹25,000 under Section 20 of the RTI Act, and recommend departmental action.

What Specific Information Can You Ask For?

Billing and Meter Records

1. The actual meter reading recorded for consumer account no. XXX for billing cycle Month/Year — the date on which the reading was physically taken and the kWh figure recorded
2. Whether the reading for the disputed cycle was taken physically or generated as an estimated or average figure — and the applicable MSPDCL or MSERC regulation permitting estimated billing
3. The complete bill computation for the disputed period — energy charges, fixed charges, fuel surcharge, any other regulatory surcharge, taxes, and arrears — with the MSERC tariff order and rate schedule under which each component was calculated
4. The number of consecutive billing cycles in the past 12 months for which the meter was not physically read and consumption was estimated or averaged
5. A copy of any demand notice, arrear recovery notice, or disconnection notice issued to the above consumer account in the past 24 months

Meter Testing and Replacement

1. The date of installation of the meter at address and the date of the most recent accuracy test conducted by MSPDCL
2. The percentage of error, if any, recorded in the meter test, and the result (pass or fail)
3. MSPDCL's policy or MSERC's order on the frequency of mandatory meter accuracy tests and the procedure for a consumer to formally request a test
4. Whether a meter replacement or consumer-requested test has been sanctioned for the above account — if yes, the date of sanction and the scheduled testing or replacement date

Transformer Repair and Supply Restoration

1. The date and time on which MSPDCL received the complaint or fault report for the distribution transformer serving locality / feeder name, District, and the complaint reference number
2. The date of the fault inspection, the fault diagnosis recorded, and the work order or indent raised for repair or replacement
3. MSPDCL's prescribed service restoration timeline after a distribution transformer failure — and whether that timeline has been exceeded in this instance
4. The name and designation of the officer responsible for supervising the repair work, and the expected completion date

New Connection Application

1. The date on which new electricity connection application Ref. No. XXX was received at Sub-Division / Division Office and the acknowledgment number issued
2. The current processing stage — whether site inspection, feasibility assessment, demand notice, estimate preparation, or execution is pending — and the specific reason for any delay
3. The MSERC or MSPDCL prescribed timeline for releasing new domestic, commercial, or agricultural connections from the date of receipt of a complete application
4. The name and designation of the officer currently responsible for processing the application, and the expected date of connection release

Load Shedding and Outage Data

1. The officially approved load shedding schedule currently in force for your locality / feeder / sub-division, District, Manipur — including the hours per day, the days on which scheduled cuts apply, the feeder or area code, and the authority or order under which the schedule was approved
2. The records of unplanned power supply interruptions on the feeder serving locality, District, during the period Month/Year to Month/Year — the date, time, duration, cause recorded, and time taken for restoration for each unplanned outage
3. The total number of hours of actual power supply available per day in locality / feeder during the period Month/Year to Month/Year, as recorded in MSPDCL's operational logs