Implementing the Bhagidari Programme: A Path to Effective Civic Management

Civic management works best when the people who live in a city and the officials who run it sit across the same table. The Bhagidari programme, launched in Delhi in late 1999, was built on exactly this idea, turning a top-down complaint culture into a structured partnership between Resident Welfare Associations (RWAs) and Public Utility Departments (PUDs). But partnership on paper means little without a clear method of execution. So how does Bhagidari actually get implemented on the ground? The answer lies in a carefully designed sequence of steps that move an issue from a neighbourhood grievance to a jointly owned solution.

The spirit behind realising Bhagidari 🔗

Before looking at the mechanics, it helps to understand the intent. The word Bhagidari means partnership, and the programme rests on the belief that citizens and government officials are equal stakeholders in governance rather than adversaries. Placed within the Chief Minister’s Office, the Bhagidari Cell coordinates the entire process, monitoring commitments made by RWAs and PUD officials, while the Asian Centre for Organisation Research and Development (ACORD) facilitates the process using social science methodologies.

The programme was decentralised across nine revenue districts, with the Deputy Commissioner (Revenue) acting as the district coordinator. This structure matters because implementation is not a centralised exercise handed down from the Secretariat. It is a layered process where issues rise from colonies, get refined at the top, and return to the neighbourhoods as jointly agreed action plans.

Step one: Issue generation 🔗

Every cycle of Bhagidari begins with identifying what actually troubles residents and what challenges officials face. Residents typically bring forward concerns around water supply, sewage, power cuts, garbage collection, street lighting, park maintenance, and policing. Officials, on the other hand, raise their own operational bottlenecks, things like inadequate public cooperation, encroachments, billing disputes, or limited manpower.

This two-way generation of agenda items is what distinguishes Bhagidari from a standard grievance redressal system. Instead of citizens lodging complaints into a void, both sides contribute to the list. The issues are collected through RWA federations, district-level consultations, and feedback from PUDs such as the Delhi Jal Board, MCD, NDMC, BSES, NDPL, DDA, and Delhi Police. Local officials of these departments sit with RWA representatives to deliberate upon common civic problems and find acceptable solutions.

Step two: Top team discussions 🔗

Once issues are collected, they move to the Top Team, which consists of senior officials from the concerned PUDs, CSAs, and the Bhagidari Cell. Their job is to filter the long list into a workable agenda. Not every problem can be tackled in a single cycle, so the Top Team prioritises based on urgency, feasibility, resource availability, and cross-departmental coordination requirements.

For example, if the Delhi Jal Board is the anchor department for a particular round, the top team might frame a theme such as ‘DJB – Be Every Customer’s Delight’ with a clear purpose of ensuring clean water to every household. This thematic framing is important because it gives the entire workshop a focus, rather than letting discussions wander across every possible civic issue. The Top Team also identifies the stakeholders who must be present, both internal officials at various levels and external representatives from RWAs and MTAs.

Why prioritisation matters 🔗

A typical Bhagidari cycle takes up around five issues at a time, which keeps discussions focused and outcomes measurable. If a workshop tries to solve twenty problems in one sitting, none get resolved. This disciplined filtering is what allows the programme to produce action points rather than wish lists.

Step three: Design team workshops 🔗

After the Top Team sets the theme, a Design Team is formed. This group usually includes mid-level officials from the anchor department, representatives from related agencies, RWA members, and facilitators from ACORD. Their task is to translate the theme into a detailed blueprint for the Large Group Interactive Workshop that follows.

The Design Team workshop typically runs for a day or two and does three things. First, it finalises the list of participants, ensuring that every function and every level of the anchor department is represented, along with external stakeholders at each discussion table. Second, it prepares an information pack containing facts, data, and background on each issue so that participants arrive informed. Third, it works out the table groupings and the flow of sessions.

The deeper purpose of this stage is ownership. When mid-level officials and citizen representatives themselves design the workshop, they walk into the main event not as passive attendees but as champions of the process. The design team workshop creates a strong sense of involvement and makes its members ambassadors for the LGIW that follows.

Step four: Large group interactive workshops 🔗

The Large Group Interactive Workshop (LGIW) is the centrepiece of Bhagidari implementation. This is where the theory of partnership meets the practice of problem solving. Each workshop brings together 200 to 400 participants seated at around 30 to 35 tables, with each table hosting four RWA citizens from two neighbouring colonies and five to six officials from the concerned PUDs and CSAs.

The seating arrangement itself is designed to break hierarchy. Nodal area officials are deliberately seated at the same table as residents from their area, so that the people solving the problem are the same people who live with it. The table-based dialogue is a form of horizontal decision making, which generates trust that traditional hierarchical meetings cannot.

How the dialogue unfolds 🔗

LGIWs draw on the techniques of large group dynamics and real-time strategic change management. Interactive workshops of this kind use facilitated group activities where participants work together to explore problems and solutions within a defined time frame. Facilitators guide participants through structured rounds of discussion where each table first identifies what is working, then surfaces what is not, and finally agrees on action points.

The output of an LGIW is a concrete set of joint commitments. RWAs might commit to supervising door-to-door garbage collection, overseeing sanitary staff, or running awareness drives on water conservation. Officials might commit to faster bill correction, better streetlight maintenance, or specific timelines for sewage cleaning. These are not vague promises but time-bound action points with named owners on both sides.

Monitoring and review: Where many programmes fall short 🔗

Good workshops without follow-through produce nothing. Bhagidari’s designers understood this, which is why monitoring is built into the programme’s architecture rather than bolted on as an afterthought.

Fortnightly and monthly meetings 🔗

At the ground level, Area Officers hold fortnightly meetings with the RWAs in their jurisdiction, while District Officers of the public utilities monitor and coordinate the work of these Area Officers. Monthly reviews are then conducted by the Heads of Departments and the Deputy Commissioners. This cascading review system means that progress on any given action point is checked multiple times in a month, across multiple levels of authority.

Quarterly and steering reviews 🔗

At the top of the pyramid, quarterly reviews are conducted by the Chief Secretary and the Steering Committee headed by the Chief Minister. These reviews do two things. They hold senior officials accountable for delivery on commitments made at the LGIWs, and they keep the political leadership engaged with what is happening in neighbourhoods. The presence of the Chief Minister in the review process signals that this is not a peripheral scheme but a governance priority.

Institutionalising accountability 🔗

To make sure officials take the programme seriously beyond workshop days, the Department of Personnel and Training introduced performance appraisal for Delhi Government officers based on their contributions to sustaining Bhagidari. This single administrative change did more than any exhortation could, because it linked career progression to citizen-centric behaviour.

Action plan evaluations 🔗

Beyond routine meetings, periodic evaluations assess whether the action plans produced at LGIWs have actually moved the needle on civic service delivery. These evaluations look at measurable outcomes such as reduction in water leakage complaints, improvements in garbage collection coverage, drop in billing disputes, or increase in the number of parks maintained jointly by RWAs and DDA.

A concrete illustration comes from the power sector. When complaints surfaced about new electronic meters running faster after power privatisation, feedback from RWAs led the Delhi Electricity Regulatory Commission to re-test the meters, identify deficiencies, and reprimand the concerned DISCOM with orders for corrective installation. This is exactly how the feedback loop is supposed to work, citizens flag an issue, the review mechanism channels it upwards, and the regulator acts.

What makes this implementation model work 🔗

The design of Bhagidari’s implementation carries a few features that any participatory governance initiative can learn from. The process moves from broad issue gathering to a focused thematic workshop, which prevents the familiar trap of consultations that discuss everything and decide nothing. Every stage has clearly identified owners, from the Bhagidari Cell at the top to Area Officers at the bottom. Monitoring is not a single review at the end of the year but a continuous rhythm of fortnightly, monthly, and quarterly checks.

The programme has also delivered visible results in several areas. RWAs have taken on roles such as switching streetlights on and off, regulating traffic in colonies, and handling water bill collection, and a survey cited in the Journal of Civil Society found that 96% of residents considered Bhagidari useful while 74% said it improved quality of life.

The caveats worth knowing 🔗

No model is perfect, and Bhagidari has had its critics. Studies have pointed out that participation of lower-level officials has often been poor, and the programme has been criticised for being predominantly middle-class in character. Programmes like Bhagidari typically include only RWAs based in planned neighbourhoods, which leaves out residents of slums and unauthorised colonies. Realising Bhagidari in its fullest sense, therefore, requires expanding participation beyond its original base and ensuring that front-line staff are as engaged as senior officers.

From process to outcome 🔗

The real test of any implementation framework is whether it changes behaviour, both in administration and in citizenship. On that count, Bhagidari has pushed officials to step out of departmental silos and has pushed residents to see themselves as co-producers of civic services rather than passive recipients. The structured sequence of issue generation, top team prioritisation, design team preparation, large group dialogue, and multi-layered review is what converts the abstract idea of partnership into everyday governance.

What do you think? If you were asked to adapt the Bhagidari implementation model for your own city or locality, which element would you keep intact and which would you redesign? And how would you ensure that the partnership genuinely includes voices from informal settlements and the urban poor, rather than stopping at the gates of planned colonies?

References

1. https://www.orfonline.org/research/bhagidari-programme-of-delhi-government
2. https://egyankosh.ac.in/bitstream/123456789/25833/1/Unit-10.pdf
3. https://revenue.delhi.gov.in/revenue/bhagidari
4. https://www.studocu.com/in/document/university-of-delhi/political-science/bhagidari-scheme-pub-ad/95431362
5. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3937100/
6. https://old.ccs.in/internship_papers/2003/chap7.pdf
7. https://www.orfonline.org/research/new-urban-governance-exemplars-a-glance-at-delhis-bhagidari-model
8. https://en.wikipedia.org/wiki/Resident_Welfare_Association