Bihar became the first state to scrap the MLA Local Area Development Fund scheme (MLALAD).  According to news reports, Nitish Kumar, Bihar’s Chief Minister, is planning to replace it with the CM Area Development Programme, which would be implemented at the District level.  The schemes would be selected by a district selection committee headed by the minister-in-charge and MLAs and MLCs of that district as members.  The implementation shall rest with a body of engineers, headed by Engineer-in-chief.  The district magistrates would only monitor implementation and contractors would be chosen through open tendering in which a representative of the Comptroller and Auditor General of India (CAG) would be present.  The state government would allocate funds as per requirement. The MPLAD and MLALAD scheme was introduced in December 1993 by former Prime Minister, P.V. Narasimha Rao to enable legislators to execute small works of a local nature to meet the urgent needs of their constituents.  Under the scheme, each legislator may identify projects and sanction upto Rs 2 crore per year for public works in their constituencies.  The scheme was mooted after MPs demanded that they should be able to recommend certain development projects in their constituencies.  The projects include assets building such as drinking water facilities, primary education, public health sanitation and roads.  The initial amount allocated was Rs 5 lakh per year to each MP. It has however not been smooth sailing for the scheme.  Besides the many implementation lapses (as pointed out by the Standing Committee on Finance in 1998-1199, the CAG and the Planning Commission), the constitutionality of the scheme has been questioned by various scholars and experts. In 2002, the National Commission to Review the Working of the Constitution recommended immediate discontinuation of the MPLAD scheme on the ground that it was inconsistent with the spirit of federalism and distribution of powers between the centre and the state.  Former MP, Era Sezhiyan in a booklet titled ‘MPLADS – Concept, Confusion and Contradictions’ also opposed the scheme and recommended that it be scrapped since it ran contrary to the Constitutional provisions which envisaged separate roles for the Executive and Legislature.  However, the Committee on MPLADS in its 13th Report and its 15th Report stated that there was nothing wrong with the scheme per se except some procedural infirmities and recommended among other things a change of nomenclature to the Scheme for Local Area Development.  The debate continued with the 2nd Administrative Reforms Commission’s report on “Ethics in Governance” taking a firm stand against the scheme arguing that it seriously erodes the notion of separation of powers, as the legislator directly becomes the executive.  However, in response to a Writ Petition that challenged the constitutionality of the MPLAD scheme as ultra vires of the Constitution of India, in May 2010, a five-judge bench of the Supreme Court ruled that there was no violation of the concept of separation of powers because the role of an MP in this case is recommendatory and the actual work is carried out by the Panchayats and Municipalities which belong to the executive organ.  There are checks and balances in place through the guidelines which have to be adhered to and the fact that each MP is ultimately responsible to the Parliament. Meanwhile, some MPs are pushing for hiking the amount allocated under the scheme to Rs 5 crore.  However, no decision has been reached yet.  The Ministry of Statistics and Programme Implementation has suggested that a single parliamentary committee be formed comprising of members of both Houses of Parliament to monitor MPLAD schemes. While the question of constitutionality of the MPLAD scheme may have been put to rest by the Supreme Court ruling, other issues related to implementation of the scheme still remain.  Unless problems such as poor utilisation of funds, irregular sanction of works, delay in completion of works are tackled in an efficient manner, the efficacy of the scheme will remain in doubt.

In law, the addition or deletion a single punctuation or a single word can have a major impact on the effect of that law.  One such example can be seen from the recommended changes in the Civil Liability for Nuclear Damage Bill, 2010 by Parliament’s Standing Committee. The Civil Liability for Nuclear Damage Bill, 2010 was introduced in the Lok Sabha on May 7, 2010.  The Bill was referred to the Parliamentary Committee on Science and Technology, Environment and Forests, which submitted its report on the Bill yesterday (August 18, 2010).  The Committee has made a number of recommendations regarding certain clauses in the Bill (See summary here).  One of these may have the effect of diluting the provision currently in the Bill.  The main recommendations pertain to:

  • Preventing the entry of private operators.
  • Allowing the government to increase the total liability for a nuclear incident by notification, but not decrease it.
  • Increasing the liability of the operator to Rs 1,500 crore from Rs 500 crore.
  • Increasing the time limit for claiming compensation to 20 years from 10 years.
  • Changing the provision giving operators a right of recourse against persons actually responsible for causing damage.

Clause 17 of the Bill which gives operators a right of recourse against those actually causing damage had been opposed as it was felt that it was not strong enough to hold suppliers liable in case the damage was caused by them.  Clause 17 gave a right of recourse under three conditions.  The exact clause is reproduced below: The operator of a nuclear installation shall have a right of recourse where — (a) such right is expressly provided for in a contract in writing; (b) the nuclear incident has resulted from the wilful act or gross negligence on the part of the supplier of the material, equipment or services, or of his employee; (c) the nuclear incident has resulted from the act of commission or omission of a person done with the intent to cause nuclear damage. Under this clause, a right of recourse exists when (a) there is a contract giving such a right, or (b) the supplier acts deliberately or in a grossly negligent manner to cause nuclear damage, or (c) a person causes nuclear damage with the intent to do so.  If any of the three cases can be proved by the operator, he has a right of recourse. The Committee has stated that “Clause 17(b) gives escape route to the suppliers of nuclear materials, equipments, services of his employees as their willful act or gross negligence would be difficult to establish in a civil nuclear compensation case.” It recommended that Clause 17(b) should be modified to cover consequences “of latent or patent defect, supply of sub-standard material, defective equipment or services or from the gross negligence on the part of the supplier of the material, equipment or service.” The Committee also recommended another change in Clause 17.  It recommended that clause 17(a) may end with “and”. This provision may dilute the right of recourse available to operators.  The modified clause 17 would read as: The operator of a nuclear installation shall have a right of recourse where — (a) such right is expressly provided for in a contract in writing; and, (b) the nuclear incident has resulted as a consequence of latent or patent defect, supply of sub-standard material, defective equipment or services or from the gross negligence on the part of the supplier of the material, equipment or services.; (c) the nuclear incident has resulted from the act of commission or omission of a person done with the intent to cause nuclear damage. This implies that for Clauses 17(b) or (c) to be applicable, the condition specified in clause 17(a) has to be compulsorily satisfied.  Two examples highlight the consequence of the recommended change in Clause 17(a) of the Bill:

  1. A person X deliberately commits sabotage in a nuclear plant and causes damage.  Under the Bill, the operator has recourse under Clause 17(c).  If the recommendation regarding clause 17 is accepted, the operator may also have to also prove the existence of a pre-existing contract with X in addition to clause 17(c).
  2. If a supplier supplies defective equipment, but does not have a contract in writing stating that he will be liable for damage caused by defective equipment, the operator may not have a right of recourse against the supplier under 17(b).

The effect of the changes recommended by the committee may thus dilute the provision as it exists in the Bill.  The table below compares the position in the Bill and the position as per the Standing Committee’s recommendations:

Right of recourse - The Bill gives operators a right to recourse under three conditions:  (a) if there is a clear contract; (b) if the damage is caused by someone with intent to cause damage; (c) against suppliers if damage is caused by their wilful act or negligence. In the Bill the three conditions are separated by a semi-colon.  The Committee recommended that the semi-colon in clause 17(a) should be replaced by “and”. This might imply that all three conditions mentioned need to exist for an operator to have recourse.
Right to recourse against suppliers exists in cases of “willful act or gross negligence on the part of the supplier”. (Clause 17) The Committee felt that the right of recourse against suppliers is vague.  It recommended that recourse against the supplier should be strengthened.  The supplier is liable if an incident has occurred due to (i) defects, or (ii) sub-standard material, or (iii) gross negligence of the supplier of the material, equipment or services. The variance with the Convention continues to exist.