Land Pipeline

Where projects begin — a structured pipeline of every plot ever evaluated, with elimination memory.

What it is

The pipeline is the system of record for every plot has ever looked at — sourced, screened, eliminated, or carried forward. It captures sourcing channel, plot detail, DP remarks, and screening filter results. Crucially, eliminated plots stay in the system with their reasoning, so the same plot does not get re-evaluated blind when it surfaces again.

Inputs

Triggers

·New plot lead received from broker, JDP partner, direct sourcing, or internal scout
·Existing pipeline plot re-surfaced after elimination
·DP remarks review request from Liaison
·Periodic pipeline review by BD HoD

Data reads

·Eliminated plot history (so the same plot is not blind-screened twice)
·Micro-market intelligence and saleability benchmarks
·Existing land bank for proximity and adjacency checks
·Liaison knowledge of zoning and DP status

Artefacts consumed

·Broker / source communication and KYC
·Plot detail — area, address, ownership summary, encumbrance summary
·DP remarks document from Liaison

Tools & Techniques

Methods

·Auto-screening filters — location, ReDev/SRA status, micro-market, plot size
·Elimination memory lookup — has this plot been evaluated before, with what outcome
·Source channel tracking with conversion analytics
·DP remarks workflow with Liaison auto-notification

Policies

·sourcing strategy by micro-market
·Plot screening criteria policy (location, FSI potential, encumbrance tolerance)
·Elimination reasoning policy — what counts as a closed-out plot

Decision rules

·Shortlist requires DP review clean OR explicit BD HoD override
·Eliminated plots cannot be re-screened without senior approval
·High-priority plots auto-escalate to BD HoD within 48 hours

Outputs

Artefacts produced

·Pipeline record per plot (status, screening result, decision)
·Decision log with reasoning per plot
·DP remarks file attached to record

Data writes

·Pipeline status updated through screening lifecycle
·Elimination memory updated on closed-out plots

Downstream triggers

·Shortlisted plots auto-queue into M02 Feasibility
·Eliminated plots logged with reasoning for future reference
·Liaison notified for DP review on new plots

Stakeholders

BD TeamSources leads, captures plot detail, runs initial screening
LiaisonReviews DP remarks, flags reservation or zoning conflicts
BD HoDApproves shortlisting to feasibility or elimination
LegalNotified for title preliminaries when shortlisted

The flow

01Lead sourced (direct, broker, JDP, internal scouting)
02Pipeline record created with sourcing metadata
03Initial filter applied — location, ReDev/SRA status, micro-market
04Plot detail captured — area, address, ownership, encumbrance summary
05DP remarks review by Liaison
06Decision — shortlist for feasibility OR eliminate with reasoning

State change

Before

Plot is unknown to or sits in someone's WhatsApp.

After

Plot is a structured pipeline record visible to BD, Liaison, and (when shortlisted) the feasibility team.

Real-world example

A 1.2-acre plot in Marol East sourced through a broker on 14 May. Pipeline record created with broker reference, plot detail, and ownership summary. DP remarks come back clean — no reservation, residential zoning. Shortlisted for techno-commercial feasibility within 48 hours.

Artefacts

·Pipeline record (plot_id, sourcing, status, screening results)
·DP remarks document attached
·Decision log (shortlist or eliminate, with reasoning)

Pain today

Pipeline tracking lives across spreadsheets per BD team member. Eliminated plots are forgotten and re-evaluated when they surface from another channel.

Integrations

No external system integrations — module operates on internal records.