Resettlement on linear projects: transmission lines, roads and pipelines

A dam displaces a few thousand people from a defined area, all at once, physically. A 300-kilometre transmission line displaces a few thousand people across dozens of districts, over three years, mostly economically, and mostly by taking a strip of each of their fields.

Both are resettlements. Almost every operational assumption that works for the first fails for the second.

Economic displacement is the main event

On a typical linear project, physical displacement is a small fraction of impacts — the households whose homes sit inside the corridor. The large population is economically displaced: farmers losing a strip, traders losing a frontage, people losing access across a severed holding.[1]

Teams built around relocation logistics are equipped for the small group and under-equipped for the large one. The disproportionate effort goes to housing, while the majority of affected people receive a valuation for a partial taking and little else.

Partial takings and remnants

The defining valuation problem is the remnant. A tower footing or a wayleave strip takes part of a holding and leaves the rest — sometimes farmable, sometimes not. A remnant too small to work, severed from its water source, or cut off from its access route has lost value well beyond the area acquired.

Valuing only the acquired area systematically understates the loss, and it is the single most common source of grievances on linear projects. Where the remnant is unviable, the workable answer is usually to acquire the whole holding rather than leave a household with land they cannot use and compensation calculated as though they can.

On a linear project the question is rarely "what did we take?" It is "what is left, and can they still farm it?"

Restrictions without acquisition

A wayleave frequently does not transfer ownership. It imposes restrictions — no structures, no tall crops, restricted access — on land the household still holds. That is economic displacement through restriction on land use, and it is squarely within scope under both standards.[3]

Projects treating wayleaves as a licensing matter rather than a resettlement impact miss this population entirely. The tell is a RAP whose affected numbers are far lower than the corridor length would imply.

One cut-off date does not work

Enumeration on a linear project proceeds section by section over many months, sometimes years. Applying a single project-wide cut-off date to sections surveyed eighteen months apart is indefensible: it excludes people on the basis of a date that had not been disclosed in their area when it supposedly took effect.

The defensible structure is a cut-off date per section, each tied to that section's enumeration and disclosed locally, with the disclosure evidence held per section.[2] It is more administration and it is the version that survives a challenge.

Consultation across dozens of jurisdictions

A corridor crosses districts, sub-counties and parishes, each with its own leadership structures, land administration and sometimes language. There is no single public meeting that reaches the affected population, and no single local authority whose endorsement covers the route.

Practically this means a consultation programme replicated per section, with records kept per section, and a disclosure log that can answer "what was disclosed in this parish, when, in what language" — because that is the granularity at which the question will eventually be asked.

Field logistics change the data problem

Enumeration teams are dispersed across hundreds of kilometres, frequently without connectivity, submitting data over months. The consequences compound:

• Consistency drift. Teams enumerating in month one and month eighteen apply the instrument differently unless it is enforced by the collection tool rather than by training memory.
• Reconciliation of offline copies. Field teams working without connectivity produce datasets merged later, and merge decisions are rarely recorded.
• Re-finding assets. Verifying a disputed measurement two years later on a strip of farmland requires coordinates. Without geo-referencing, the asset cannot be relocated and the dispute cannot be resolved on evidence.

This is why offline-first, geo-referenced, validation-at-entry collection matters disproportionately on linear projects. It is not a preference — the alternative simply cannot answer the questions that arise.[4]

Sequencing against construction

Linear construction advances along the route, which means the compensation deadline is different for every section. A project-wide "compensation complete" milestone is the wrong instrument: what matters is whether compensation is complete for the section the contractor is about to enter.

Tracking that requires payment status by parcel, mapped against the works programme, visible to whoever authorises mobilisation. Projects that manage this in aggregate discover the gap when a contractor is already on site and the households in front of them have not been paid — at which point the choice is a stoppage or a breach.