Revising compensation rates mid-programme without creating two classes of PAP

Compensation rates change during implementation. A district schedule is updated, a benchmark study finds the original rates short, inflation forces a revision, or a grievance succeeds and the project accepts a higher figure for a category. Whatever the cause, the programme now has households paid under two different rate sets for the same loss.

Why this cannot be handled quietly

It will become known. Affected communities discuss compensation amounts in detail, and a neighbour paid more for the same crop in the same season is the most legible unfairness a programme can produce.

Handled badly it produces three things at once: a surge of grievances from the earlier-paid group, a collapse in trust in the valuation process generally, and a strong incentive for remaining households to delay agreement in the expectation of another revision.[1]

The question is not whether people will find out. It is whether the project has a stated policy before they do.

Decide the policy in advance

The plan should state, before any payment is made, what happens when rates change. There are three coherent positions:

• Prospective only. The rate applying is the one in force at assessment. Simple, defensible in law, and hardest to explain to someone paid last year.
• Retrospective top-up. Everyone is brought to the revised rate, with earlier recipients receiving the difference. Expensive, administratively heavy, and by far the easiest to defend on equity.
• Indexed baseline. All assessments are expressed at a common valuation date and adjusted to the payment date by a published index, so revisions for inflation do not create classes at all.

The third is the most robust and requires the discipline to be adopted at the outset. The second is the usual remedy once the problem has already appeared.[2]

Distinguish the reason for the change

Not every revision has the same equity logic. A rate increase that corrects an error — the original rate was below replacement cost — is a finding that earlier payments were inadequate, and inadequate compensation is a compliance issue rather than a matter of generosity. A revision reflecting general inflation over two years is a different case, and indexation handles it.

Stating which of these has occurred, in the disclosure, does more to keep the process credible than the amount itself.[3]

Re-disclosure is not optional

A revised rate is a change to the entitlement framework that was publicly disclosed, so it has to be disclosed again — publicly, in the local language, with the effective date and the treatment of already-paid households stated explicitly.[4]

Households whose entitlement changes should be individually notified rather than left to hear it, and the record should show which version of the matrix applied to each determination. A register that stores only the current rate cannot answer that question, which is why versioned entitlement rules matter more here than anywhere else.

Operational checklist

1. Policy on revisions written into the plan before the first payment.
2. Matrix versioned, with each determination stamped to a version.
3. Reason for the revision stated in the disclosure.
4. Individual notification to anyone whose entitlement changes.
5. Budget provision for retrospective top-ups if that is the chosen policy.
6. Grievance team briefed before disclosure, not after the queue forms.