Landowner Compensation - Infrastructure

Landowner Compensation System for Infrastructureon Kotlin and Laravel

Field teams assessed land damage on paper and compensation was estimated by hand, so similar damage produced different amounts and landowners disputed the result. Kansoft digitised the full lifecycle with a structured Android field app and a rule-based calculation engine, cutting disputes by 70%.

70% · fewer landowner disputesOffline · field assessment in remote locationsRule-based · compensation calculation
The Client

Compensation decided on paper, disputed in the field.

Sterlite Power builds power transmission infrastructure, which means land acquisition and right-of-way clearance on every project. Construction damages land, and landowners are compensated for it. Getting that right is not a goodwill exercise; an unresolved dispute stops work on a corridor.

The assessment that determined each payment was made on paper by whichever field team was there, and the amount was worked out by hand afterwards. Nobody involved could see how the number had been reached.

Architecture diagram for this engagement is being drawn.

The Problem

Four reasons a manual compensation process generates disputes.

The issue was never the intent to pay fairly. It was that nothing in the process could demonstrate the payment was fair, to the landowner or to anyone reviewing it later.

01

Assessment varied by team

Field teams recorded damage on paper from direct observation. With no standard tool or digital capture, the same damage was described differently between teams and locations.

02

Inconsistent compensation amounts

Without a standard calculation framework, similar damage could produce materially different payments. That inconsistency is what landowners noticed, and what they contested.

03

Handoffs that lost documents

The flow from field assessment to compensation approval crossed field teams, regional offices and central management. Paper-based documentation created bottlenecks, lost records and processing delays.

04

No visibility for the landowner

Landowners could not see how their compensation had been calculated or where their claim stood. Grievances and repeat enquiries followed, and in some cases unresolved disputes delayed the project itself.

What We Recommended

Standardise the assessment first, then automate the calculation.

Automating a calculation built on inconsistent field input would only have produced consistent-looking wrong answers faster. The structured capture had to come first, which meant designing for a field team in a remote location with no signal.

PHASE 01

Lifecycle mapping

The complete compensation lifecycle traced from field survey through assessment, calculation, approval and payment, identifying every manual handoff.

PHASE 02

Field and office interfaces

An Android app for field assessment teams and a web gateway portal for office-based management, so each side works in the tool suited to its conditions.

PHASE 03

Standardised framework

A configurable assessment engine applying consistent criteria across land type, crop type, construction impact and regional rate, so the basis of a payment is explicit.

PHASE 04

Automation and scale

Automated calculation, rule-based approval routing and status notifications, architected for concurrent projects across geographies with differing compensation rules.

Technology Stack

Built for remote field capture and auditable calculation.

The app has to work where there is no network, and every amount it feeds into has to be explainable months later.

Kotlin / Android
Structured field assessment with photo capture and GPS tagging
Offline capability
Full assessment workflow in remote locations, syncing when signal returns
PHP Laravel
Gateway portal, approval routing and compensation lifecycle management
Calculation engine
Configurable rules across land type, crop type, impact and regional rate
REST APIs
Field-to-portal synchronisation and project system integration
Monitoring dashboard
Assessment progress, pending approvals and disbursement status
Measured Outcomes

From an estimate nobody could explain to a number that shows its working.

Four measured changes between the paper-based process and the digital platform now running across active projects.

70%↓
Landowner disputes
Standardised assessment and transparent calculation basis
Standardised
Damage assessment
Structured field workflow with photo evidence and GPS tagging
Automated
Compensation calculation
Rule-based engine replacing subjective manual estimates
Real-time
Assessment visibility
Progress across every active project in one dashboard
What Changed for the Business

Four changes that mattered as much as the numbers.

Fewer disputes is the measurable result. The reason behind it is that every payment now carries the evidence of how it was reached.

Assessments became comparable

A structured workflow with photo evidence and GPS tagging means two teams assessing similar damage produce comparable records, which is the precondition for consistent payment.

The calculation is defensible

Rule-based amounts applied to documented criteria can be explained to a landowner, reviewed internally and audited later, which is what removed most of the disputes.

Paper handoffs disappeared

Assessment, review, approval and payment initiation run through one system with rule-based routing, so records stop getting lost between a field team and a regional office.

Projects stopped waiting on claims

Real-time visibility into assessment progress and pending approvals lets managers clear bottlenecks before an unresolved compensation claim holds up construction.

Engagement

How the work was shaped.

Practice
Custom Software Development · API & Integration Development · Architect & Re-engineering · Dashboard Design & Development
Platform & stack
Kotlin · Android · PHP Laravel · REST APIs
Industry
Energy & Utilities
Timeline
Dedicated team, ongoing engagement
Why Kansoft

Field reality, not head-office assumptions.

Compensation systems fail in the field, not in the office. An app that assumes connectivity is useless on a transmission corridor, and a calculation engine that cannot explain itself to the person receiving the payment does not reduce disputes. Building for offline field capture, modelling the compensation rules as configurable criteria rather than hard-coded formulas, and architecting for concurrent projects with different regional rules is what makes the platform usable across a growing infrastructure portfolio.

Managing land acquisition or right-of-way compensation?

Tell us how your field teams assess damage today and how the amount gets decided. We will map the lifecycle and show where disputes are being created.

Book a Free Call