A land opportunity isn't a location with a price attached. It's a chain of decisions: can the site carry the intended use, can the scheme actually fit, do the numbers support the risk, and is there enough evidence to spend more time on it?
The exact rules differ between India and the USA, and they differ again from one jurisdiction to the next. The evaluation logic is still portable, though. A disciplined first pass should answer the same five questions in both markets, while keeping the local evidence separate.
1. What is the site, really?
Start with the boundary and its confidence level. Is it a surveyed boundary, a title-plan boundary, an approximate map polygon, or a shape supplied for an early conversation? Those are different inputs and shouldn't be treated with the same certainty.
Then record the physical facts that can change the envelope — access, road edges, irregular corners, slope, water, easements, existing structures, neighboring constraints. The first useful output isn't a rendered building. It's a clear line between the mapped parcel and the part a scheme can reasonably occupy.
2. What can the site carry under the applicable local rules?
The headline entitlement is only one input. A real first pass has to connect the relevant local rules to the geometry — use, density or FAR/FSI, setbacks, height, parking, access, open space, and any exclusions or incentives that actually apply.
This is where India and the USA need different source paths. The question isn't whether some global database has a plausible number. It's whether this specific site links to the correct state, city, county, district, overlay, or other governing source — with that source's status visible when it's incomplete.
If the governing source is missing, the answer isn't a confident default. Say what's verified, what's provisional, and what a planner or local professional still needs to confirm.
3. What scheme would make the opportunity worth pursuing?
A site rarely has one meaningful answer. Test a small number of scenarios that represent real decisions — a compact scheme, a lower-intensity scheme, a different use mix, or a version that preserves more flexibility for later design.
Give every scenario the same scorecard: buildable envelope, achieved area, unit or program mix, parking and access treatment, cost and timeline assumptions, and the constraint most likely to change the result. The point isn't to manufacture options. It's to surface the trade-offs before the team falls in love with one layout.
4. Do the numbers work before the design gets expensive?
Early feasibility is a decision screen, not a promise of returns. The model should show what's been assumed about saleable or usable area, rates, construction cost, soft costs, finance, program, and timing — and each assumption needs a provenance and a sensitivity range for where the outcome depends on it.
For a developer, the useful question is often not "what's the exact return?" It's "which assumption would make me stop?" A small shift in land price, achievable area, cost, or time-to-market can matter more than a polished base-case headline.
That's why a good land-intelligence workflow keeps geometry and underwriting linked. Change the scheme, and the commercial picture should change with it. If the source or geometry is uncertain, the financial result should carry that uncertainty forward instead of hiding it inside a single number.
5. What evidence earns the next round of diligence?
The first pass should end with a next-action list, not just a score — which facts are worth verifying first, who needs to verify them, and what decision the verification unlocks.
For one site, the first action might be confirming boundary and access. For another, it might be checking a local district standard, or testing whether the requested program still fits after parking and open-space constraints. For a third, the right call may be to stop, because the opportunity rests on an assumption nobody can support yet.
This is also what makes comparison possible. A developer can rank opportunities by evidence quality and decision value, not just by asking price or an attractive map location.
India and the USA: same decision chain, different evidence
The framework is shared. The sources aren't. A site in India may require one set of state, city, development-control, and project-specific checks; a site in the USA may require a different combination of state, county, municipal, district, and overlay sources. A good system preserves that difference instead of flattening it into a universal rule.
That distinction matters for software as much as it matters for a human analyst. A global product can standardize the questions, the evidence states, and the comparison scorecard. It can't honestly standardize a local entitlement that hasn't been verified for the site in front of it.
The decision a land screen should produce
At the end of an early land screen, the team should be able to say one of three things:
- Proceed to full diligence — the opportunity clears the first constraints, and the remaining unknowns are worth paying to resolve.
- Hold for one specific verification — the opportunity may work, but one named fact controls the decision.
- Pass for now — the site fails a binding constraint, or the evidence is too weak to justify more effort.
That's the actual job of land intelligence. It doesn't replace professional diligence — it helps a development team spend its scarce attention on the sites where a better answer could actually change the decision.
---
This is a methodology piece, not site-specific planning or investment advice. It intentionally uses no jurisdiction-specific regulatory values, market prices, cost benchmarks, or return claims. Any real site still needs current local-source verification and professional review.