Latest: CM Saini urges staff to end strike as talks with Gurugram administration fail
Haryana electricity employees began a three-day strike on the night of October 21 against a 25-year parallel distribution licence given to Eleven Power for Gurugram and Nuh. Outages, water shortages, halted factories and road blockades followed.
Local talks failed, Chief Minister Nayab Saini appealed to staff to end the strike, and Energy Minister Anil Vij called unions for talks and said the state would challenge the licence before the Appellate Tribunal. Summary updated 24 Oct, 08:56 IST
Why it matters: Millions of households and thousands of factories in the Delhi-NCR belt face power and water disruption, and the row raises wider questions about private entry into power distribution.
Archived on 31 Oct. No new coverage for 7 days. The summary, scores and article list are frozen as they stood, scored with rubric version 1. How it ended: outcome check pending. If new coverage appears, the story reopens with an update.
New developments are added here, newest first. When the headline, summary or other sections change, the earlier version is kept under “See earlier version”.
Summary before this update: Haryana electricity employees began a three-day strike against a 25-year parallel distribution licence given to Eleven Power for Gurugram and Nuh. Outages, water shortages and road blockades followed, while Energy Minister Anil Vij called unions for talks and said the state would challenge the licence.
Note before this update: Outlets agree on the disruption and its cause; they differ on whether the administration was unprepared and on the political blame.
“What's missing” before this update:
Based on 11 articles read in full. Scores describe each article's framing, not the outlet and not whether it is accurate.
Large outlets read: 6 of 15 (Hindustan Times, India Today, Aaj Tak, Republic, ABP, Times Now).
Outlets agree on the disruption and its cause; they differ on whether the administration was unprepared, on political blame and on some dates and figures.
Why: Covers workers' strike against back-door privatisation of power distribution, giving employees' view and state-owned utility concerns space; labour/public-sector sympathies lean left on statism, but reporting is mostly descriptive.
Why: Mostly a disruption report. It touches statism only lightly, explaining union fears of privatisation and the state's opposition, without taking a side on private distribution.
Why: Touches statism (privatisation vs public utility) but reports both sides evenly; focus is on outage impact, with no loaded framing, so it stays centrist.
Why: Touches privatisation of power distribution and labour strike, but reporting is mostly even-handed and event-focused; little loaded language, so ideology stays near centre with slight lean to labour concerns.
Why: Live blog on the strike's impact; it touches privatisation but takes no side on it. Voices from the minister, opposition and residents are balanced, and the framing is mainly about disruption.
Why: Covers a public-vs-private power distribution dispute. It gives the unions' concerns and explains the parallel licence neutrally, with no loaded language and no side taken. Touches statism only mildly.
Why: Mostly reports outages and voices from residents, industry, unions and the CM. Touches privatisation versus labour rights but takes no side in its own voice, so the ideology score is centred.
Why: Mostly reports outages and affected residents and industry; workers' privatisation grievance is mentioned but not argued. Touches statism lightly with no clear lean either way.
Why: Reports outages and the privatisation dispute evenly, giving both union concerns and the government's response. Touches statism lightly, with no loaded framing or clear lean either way.
Why: Mostly descriptive coverage of outages. Touches privatisation and labour concerns, giving union arguments space, but also industry impact and government response. Slight pro-public-sector lean; balanced overall.
Why: Civic report on a power outage during an employee strike; no religion, social-justice or statism framing. It does fault the administration for lacking a backup plan despite advance notice of the strike.
Critical, Neutral or Supportive, scored separately. It refers to the Union government unless the story is about a state. On the spectrum strip, each dot is an article: its position is the ideology score and its colour is the stance.
If an article would score differently with the parties' roles reversed, that signal is partisanship. It goes into the stance tag, not the ideology score.
High, Medium or Low, based on how much of the article was read, how many clear signals it has, and whether they agree.
Stories with fewer than five articles are marked. A blindspot is a contested story where we found coverage from only one side.
Articles that touch none of the three dimensions, such as a car launch or a match report, carry no ideology score.
This prototype is refreshed by hand (last on 17 Oct, 03:00 IST). At launch:
| Wires and the top 20 outlets | checked every 5 minutes |
| All other outlets | checked every 15 minutes |
| New story | goes up at 3 articles from 2 or more outlets, marked Limited coverage |
| Live stories | new articles added every 15 minutes; summary rewritten at most hourly |
| Home page order | every 15 minutes |
New facts go into a dated update log at the top of the story. New articles carry an “Added” tag. If a note or list changes, the earlier version stays viewable.
A story is Live while coverage arrives, Winding down after about 2 days without new coverage, and Archived after about 7. Nothing is deleted: links never change, archived scores are frozen, and stories stay on their issue pages and in search.
NDTV, India Today, Times of India, Hindustan Times, The Hindu, Indian Express, News18, ABP, Times Now and Mint block the reader used for this prototype, so their articles are missing. Each story shows how many of India’s 15 largest outlets we read. The launch pipeline will read outlets’ public feeds, TV transcripts and Hindi articles.
Editor-in-charge: S. Kalra, editor@thenazariya.com. The editor-in-charge sets Nazariya's editorial rules, reviews the AI desks' daily decisions, and is responsible for everything we publish.
How we work: AI reads and scores every article against our published rubric; an AI standards desk checks accuracy and fairness; people set the rules, review decisions and handle complaints.
Grievance officer under the IT Rules, 2021: to be confirmed (based in India). Until then, write to grievance@thenazariya.com. Complaints are acknowledged within 24 hours and resolved within 15 days. To report a factual error: corrections@thenazariya.com. Other questions: support@thenazariya.com.
Ownership: Nazariya is independently owned by S. Kalra, an Indian citizen.
Funding: Nazariya is currently funded entirely by its founder. It carries no advertising and takes no money from any political party, government or party-linked organisation. In future it will be supported by optional reader memberships. Any other funder, grant or investor will be listed here, with the amount and date.
Independence: No owner, funder or member can change a story, a score or a correction. Scores follow the published rubric, and anyone can appeal them.
Anyone, including the outlet that published an article, can appeal a score: tap any score on a story page, then "Appeal this score" to write to the editor. Outlets can also dispute a summary. The editor reviews every appeal, and any change is recorded below. Appeals: appeals@thenazariya.com.
No detail that could identify a child or a survivor of sexual violence (Juvenile Justice Act, POCSO, BNS section 72). Court cases are reported as what was said and alleged. No analysis of a poll in the 48 hours before voting there (Representation of the People Act, section 126). Press Council and NBDSA norms on communal incidents.