Additional assistance: what the vulnerability provisions actually oblige a project to do

Olule Solomon11 min read

Reviewed for publication

Abstract

Every major standard requires that particular attention be paid to people who are vulnerable to displacement impacts, and that they receive assistance beyond the compensation due to everyone. This paper examines the logic of that requirement — that equal treatment produces unequal outcomes where starting positions differ — and argues that the obligation fails most often not at identification but immediately after it. Projects identify vulnerable households competently and then attach no defined measure to the identification, producing a register that documents need without discharging it, and a data protection exposure with no corresponding benefit to the person recorded.

Vulnerable groupsAdditional assistanceDifferentiated impactsResettlement planningSafeguard obligations

1. Why equal treatment is not enough

A compensation programme that treats every household identically is, on its face, fair. The standards nonetheless require differentiated treatment, on the reasoning that identical inputs produce divergent outcomes where households differ in their capacity to convert compensation into restored livelihood. [1][5]

The mechanism is not subtle. A cash payment must be converted into replacement land or housing, which requires the ability to search a market, negotiate, transport, engage builders and manage a sum of money larger than the household has previously handled. An elderly widow, a household headed by a child, a household whose adult members are chronically ill, or a household whose head cannot read the agreement they are signing face materially higher conversion risk than a household with none of those characteristics.

The additional assistance obligation exists to close that gap. [2] It is not charity appended to compensation; it is what makes the compensation effective for households that cannot use it on the same terms as others.

2. Identification is the easy half

Vulnerability identification has become routine, and Guidance Note 5 sets out the categories a census is expected to flag. [2] Censuses record indicators — age, disability, illness, headship, income, tenure insecurity — and produce a register of households flagged as vulnerable. The exercise is competently done on most projects, and lender review focuses on it because it produces a countable output.

The failure follows immediately. A register exists; no measure attaches to being on it. Households are identified as vulnerable and then receive precisely what everyone else receives, on the same schedule, through the same process, with the same requirement to convert a payment into a replacement asset.

This is worse than not identifying at all, in one specific respect. [3] The project has recorded sensitive personal information — disability, illness, widowhood, poverty — creating a data protection exposure and, in some settings, a risk of stigma, without delivering the benefit that justified collecting it. The obligation was to assist, and the register is not assistance.

3. What a defined measure looks like

Assistance that closes the conversion gap is specific and operational: accompanied search for replacement land or housing; assistance with the transaction and with registration in the household's own name; physical help with moving; supervision of construction where the household cannot manage a builder; staged payment where a lump sum presents a risk of dissipation or of appropriation by others; and follow-up visits after relocation rather than at the point of payment.

Each of these has a cost and a responsible party, which is precisely why they are frequently omitted. IFC's livelihood restoration module treats accompanied assistance as a standard component of restoration for vulnerable households rather than an optional add-on. [4] A register costs a column in a survey instrument. Accompanied search for two hundred households costs staff time over months, and appears in the budget as a line someone must defend.

The design test is whether being on the vulnerability register changes anything a household experiences. If the answer is that the household is monitored more closely, the project has confused observation with assistance — a distinction that matters greatly to the household and not at all to the reporting.

4. Vulnerability is not static

Registers are compiled at census and treated as fixed, though the standards frame vulnerability assessment as continuing through implementation rather than closing at the baseline. [6][7] Vulnerability is a state, and displacement itself produces it: a household solvent before relocation may be in difficulty after, through illness, a failed enterprise, the loss of a support network that depended on proximity, or the exhaustion of a lump sum.

A register that is never revisited therefore identifies the households that were vulnerable before the project and misses those the project made vulnerable — arguably the more important group, since their condition is attributable to the intervention.

Periodic re-assessment during implementation and monitoring addresses this, and is uncommon. Where it is done, the finding is usually that the composition of the vulnerable population has changed substantially, which is itself an important monitoring result and one that a fixed register cannot produce.

5. Conclusion

The vulnerability provisions are among the clearest obligations in the standards and among the most reliably hollowed out in implementation. [1][5] The hollowing is not usually deliberate: projects do the identification work sincerely, report it as compliance, and never notice that no measure was attached.

The correction is a design rule that costs nothing to state and something real to honour — no vulnerability criterion enters the census unless a defined measure attaches to it. A project unwilling to fund the measure should not collect the data, because collecting it delivers the risk of the record without the benefit it was supposed to trigger.