Disaster management and relief: the DM Act and the revenue machinery

Every flood, drought, hailstorm and heavy-rain event turns the revenue department into the relief department. The legal frame is the Disaster Management Act 2005; the money frame is the SDRF/NDRF dispensation; the field craft is enumeration. The structure below is stable; the operative norms, rates and formats come from the government instructions in force at the time of the event, and those must be checked fresh each season — an officer paying last year’s rate from memory is creating next year’s audit para.

The DM Act structure

The Act builds three tiers:

• NDMA — the National Disaster Management Authority, chaired by the Prime Minister (s. 3), setting national policy, plans and guidelines, with the NDRF as the specialised response force and the NIDM for training and research.
• SDMA — the State Disaster Management Authority, chaired by the Chief Minister (s. 14), laying down state policy, approving the state disaster management plan, and coordinating its implementation.
• DDMA — the District Disaster Management Authority (s. 25), chaired by the Collector as District Magistrate, with the elected head of the district local body as co-chairperson. The DDMA is the district’s planning, coordinating and implementing body: it prepares the district disaster management plan, oversees prevention and mitigation, and directs the response when disaster strikes.

The Act gives the district authorities wide powers during a notified disaster — requisitioning resources and personnel, directing evacuation, controlling movement, and issuing directions that departments and local authorities must follow. From s. 51 onwards it penalises obstruction of officers, refusal to comply with directions, and false claims for relief — worth remembering when enumeration lists are being padded. For a Deputy Collector the practical meaning is simple: in a disaster, the Collector’s authority runs through you, and the RDO–Tahsildar–VRO line is the DDMA’s field arm. There is no separate “disaster department” underneath; you are it.

The money: SDRF and NDRF, in outline

The State Disaster Response Fund is the standing fund with the State (shared central–state contributions under the Finance Commission dispensation) from which relief for notified calamities is paid at prescribed norm rates — input subsidy per hectare of damaged crop, gratuitous relief, house-damage and cattle-loss assistance, ex gratia for loss of life, clothing and utensil grants for damaged households. The NDRF supplements the SDRF when a calamity of severe nature exhausts state capacity — released on the strength of the State’s memorandum and a central team’s assessment. Two disciplines follow:

• The rates are norms, not estimates. Payment is at the notified rate per unit of enumerated loss — so much per hectare, per house category, per animal by type. The arithmetic is trivial; the enumeration is everything.
• The thresholds are conditions. Under the central norms, crop-loss assistance attaches at 33 per cent damage and above in a given holding — which makes the damage-percentage column of the enumeration the single most contested entry in the exercise.

A calamity outside the notified list, or losses outside the norms, can only be met from state schemes announced for the occasion — check the instructions rather than promising SDRF money for everything the field reports.

Relief administration: the revenue craft

Immediate relief comes first and cannot wait for enumeration. Evacuation, rescue coordination, relief camps with food and drinking water, medical camps, and immediate gratuitous relief in cash or kind run from the first hours on the DDMA’s authority. Camp registers — who came, from where, when they left — are themselves relief records that later verification leans on.

Enumeration is the foundation of everything paid later. Assistance flows only to enumerated loss. Crop-loss enumeration is a field exercise — joint teams of revenue and agriculture or horticulture staff walking affected villages, recording survey-number-wise damage: crop, extent, damage percentage, cultivator. It leans directly on the azmoish tradition: the pahani’s crop columns say what stood on the field before the event, and the inspection records what remains. The discipline is the same — recorded at the spot, village by village, signed by the team — with the modern additions of geo-tagged photographs and same-season data entry where the instructions prescribe them. Weak enumeration is unfixable later; the lists become the basis of payment and of every grievance, appeal and audit afterwards.

Consolidation and the memorandum. Mandal lists roll up to the division, the division to the district damage report, and the district reports into the State’s memorandum seeking central assistance — the document on which central teams assess and NDRF allotments issue. Deadlines for these consolidations arrive in the instructions with the event; missing them costs the district money in the most literal sense.

A worked example: the Errakunta tank breach

A September cloudburst in a mandal of erstwhile Warangal drops 22 cm of rain overnight; the Errakunta tank breaches at 3 a.m., and floodwater passes through two villages — call them Gollapalli and Ramannapet — before spreading over the paddy of the ayacut. The RDO’s fortnight:

1. Night one. The Tahsildar’s vardi reaches the RDO at 4 a.m.; the DDMA machinery wakes. Both village low-lying hamlets are evacuated to the school buildings; camps open with cooked food and water tankers by mid-morning; the irrigation department is put on the breach; the electricity board isolates submerged transformers. One death — a herdsman swept off the tank bund — is recorded, with the inquest machinery moving in parallel and ex gratia processed at the notified rate under the current instructions.
2. Days 2–3. Preliminary damage figures — houses inundated, acreage submerged, cattle lost — go up in the prescribed first-report format. Immediate gratuitous relief and utensil/clothing assistance are paid to camp families per the norms in force, receipted family by family.
3. Days 4–10. Enumeration. Three joint teams (revenue plus agriculture, one horticulture member for the turmeric patches) walk the ayacut survey number by survey number with the pahani extracts: crop as recorded, extent damaged, damage percentage assessed against the 33 per cent threshold, cultivator as found — with the tenant-versus-pattadar question recorded as found in the field, flagged where the two differ, and resolved per the instructions in force rather than by the team’s sympathy. House damage is enumerated on the same walks by category — fully destroyed, severely damaged, partially damaged — with photographs against each door number. Draft lists are read out in each village — the gram sabha reading — and objections recorded and re-verified before the lists close.
4. Days 11–14. The mandal consolidations roll up; the RDO tests samples — five per cent re-verification, the entries just under and just over 33 per cent especially — before signing the divisional report into the district damage report that feeds the State memorandum.
5. Payment. When the allotment issues, payment lands by direct transfer against the enumerated lists. The grievances that follow — “my field was skipped”, “my neighbour with the same damage got more” — are answered from the signed village-wise record, which is the only answer there is.

Edge cases and common mistakes

• Enumerating after the field is cleared. Farmers must clear and replant; evidence vanishes in days. Teams that start late end up enumerating testimony instead of damage. Speed of enumeration is a substantive duty, not an efficiency.
• The 33 per cent line. Damage percentages clustering suspiciously at 35 per cent invite audit; percentages honestly at 30 sink genuine claims. The defensible file shows how the percentage was assessed — crop stage, extent flattened or silted, photographs.
• Pattadar versus actual cultivator. The pahani’s possessor column and the person who actually lost the crop can differ — tenants especially. Record what the field shows, flag the difference, and apply the operative instructions on who is paid; silently paying the recorded pattadar over a visible tenant is how relief riots start.
• Double counting across departments. The same house appearing in the revenue list and a housing-scheme list, or crop loss claimed in both agriculture and horticulture lists, surfaces in reconciliation as an excess payment — recoverable, with your signature on it.
• Padded lists. Names added at the village stage without spot verification are s. 51-territory false claims for someone and a disciplinary file for the enumerator. The gram sabha reading and sample re-verification exist to catch this before signature.
• Promising beyond the norms. In a camp full of angry farmers it is tempting to announce round figures. Announce the process and the notified rates; the number an officer promises beyond the norms becomes a grievance no one can lawfully satisfy.
• Forgetting the parallel files. Deaths in the event need inquests; a breach traced to maintenance failure will draw an enquiry; camps need closure reports. Relief is several files, not one.

Questions you’ll actually get

“Farmer: my two acres are fully gone — how much will I get, and when?” At the notified input-subsidy rate per hectare for your crop category, on the enumerated extent, after the lists close and the allotment issues — and the honest answer includes showing him his entry in the village list at the gram sabha reading.

“Sarpanch: half the village’s names are missing from your list.” The list is the team’s spot record, read publicly precisely so omissions surface. Named omissions are re-verified in the field and added if the damage is there — not negotiated in the office.

“MLA’s PA: announce enhanced compensation at the camp today.” Enhancement is the Government’s to announce, not the division’s. What can be said is what the norms provide and when payment follows — anything more manufactures a broken promise.

“Collector: why is your division’s damage figure double the neighbouring division’s for the same rain?” The answer must live in the enumeration record: tank breach versus mere waterlogging, crop stage, ayacut extent. If the record cannot answer it, the figure was built wrong.

“Auditor, a year later: justify these payments at 35 per cent damage.” The signed survey-number-wise enumeration, the photographs, the sample re-verification memo and the gram sabha objection register are the justification. If they exist, the para closes; if not, nothing said now will.

Field notes for a probationer

Before the first monsoon of your posting, get three things on your desk: the district disaster management plan, the current SDRF norm rates as per the latest instructions, and last season’s enumeration format actually used in your division. Then walk one enumeration with the Tahsildar’s team when the first heavy-rain vardi comes in — the gap between the format and the field is where relief goes wrong, and it can only be learned on wet ground.