Pension Verification Backlog in a Ward Secretariat
At a ward secretariat in a municipal corporation, 1,840 pension applications are pending verification. Of these, 212 show a mismatch between the Aadhaar name and the applicant's name in the ration card, 37 have bank passbooks without a printed account number, and 14 belong to persons whose names appear in the municipal death register but whose families have submitted life certificates. The state portal will close verification in four days. One of the two ward volunteers is on leave. A group of ward elders demands that nine applications, including that of a local leader's relative, be cleared first. The data-entry operator suggests marking all 1,840 as 'verified' and correcting errors later, arguing that rejection would deprive genuine beneficiaries. The ward secretary knows that a post-audit will sample 10 per cent of approvals and that wrongful inclusion can trigger recovery proceedings. A fresh applicant arrives with only a voter ID and a bank passbook in a different surname.
1. Rank the three flagged categories by risk and set a verification sequence for the four days.
Read the worked answer
The highest risk is the 14 death-register matches. Paying a pension after death is an inclusion error, wastes public money, and is difficult to recover; it can also conceal fraud. These must be frozen first and checked against the death certificate, cremation or burial record, and a statement from the family. The 212 name mismatches are next because they create exclusion risk: a genuine beneficiary may lose payment. Verify through Aadhaar demographic correction with consent, or through alternative documents such as ration card, voter ID and bank passbook. The 37 bank cases are lowest risk because payment failure can be corrected without wrongly approving an ineligible person. Day 1: freeze and verify the 14 death cases. Days 2-3: clear the 212 mismatches in batches. Day 4: resolve the 37 bank cases and the fresh applicant. Do not bulk-approve. Inclusion errors are harder to reverse than visible exclusion errors that can be appealed.
2. How should the secretary respond to the demand for priority clearance of nine applications?
Read the worked answer
The secretary should apply the same criteria to all nine and should not create a separate queue. If an application is complete and eligible, it can be processed in the normal sequence; if it is deficient, a written deficiency memo should be issued stating exactly what is missing. The request, the date, and the decision should be recorded. If the local leader's relative falls in the death-match or name-mismatch category, that verification must be completed before approval. The secretary should inform the supervisor in writing about the pressure, not to punish anyone but to protect the audit trail. The reasoning is that preferential clearance converts a verification backlog into a favouritism dispute and exposes the office to a sample audit. Equal treatment also gives the secretary a defensible answer to the elders: the rule is the reason, not personal reluctance.
3. What minimum record should be kept for each decision?
Read the worked answer
For every application, the register should show the application ID, category of defect, evidence actually seen, decision, date, name of verifying officer, and a short reason. Copies of the evidence should be retained, and oral requests or assurances should be noted with date and name. A daily count by category should be reconciled with the portal. This record matters because the post-audit samples 10 per cent of approvals and because recovery proceedings need proof of what was checked. A register that records only 'verified' cannot distinguish a genuine correction from a bulk approval. The secretary should also record why the fresh applicant was accepted or rejected on alternative documents, so that the same standard can be applied to similar cases later.