Quick Answer
A solar land feasibility study is a staged decision process, not a module-fit layout. It tests land control, title, boundaries, access, land use, environmental and social constraints, terrain, drainage, and ground conditions. It also tests grid route, constructability, energy assumptions, schedule, and commercial risk. Each conclusion needs evidence, uncertainty, expiry, and action.
A solar land feasibility study should decide whether to secure, investigate, redesign, hold, or reject a parcel. A module-fit layout alone cannot prove title, permission, connection, constructability, or commercial suitability.
Start with a defined project and decision date. Then move from low-cost screening to field and specialist work only when earlier gates pass.
Quick Answer
A solar land feasibility study is a staged decision process, not a module-fit layout. It tests land control, title, boundaries, access, land use, environmental and social constraints, terrain, drainage, and ground conditions. It also tests grid route, constructability, energy assumptions, schedule, and commercial risk. Each conclusion needs evidence, uncertainty, expiry, and action.
This guide makes no parcel, title, land-use, environmental, grid, yield, cost, schedule, or approval conclusion. Every requirement and result must remain jurisdiction and project specific.
Solar land feasibility study decision basis
Feasibility is meaningful only against a defined project route and risk appetite. Record the decision that the study must support.
Project basis
Identify developer, project company, land counterparty, intended direct-current and alternating-current ranges, technology, ownership route, and offtake route. Record the development stage.
State the target connection point, voltage, evacuation concept, construction window, operating horizon, and decision date. Mark unconfirmed items as assumptions.
Define risk appetite for title, schedule, grid, environmental, geotechnical, cost, and community uncertainty. Different investors may reach different decisions from the same evidence.
Decision options
Use explicit outcomes:
- proceed to the next investigation gate
- proceed with stated conditions
- hold until evidence arrives
- redesign capacity, boundary, route, or technology
- evaluate an alternative parcel or connection route
- reject the parcel for the defined project
Do not reduce every decision to go or no-go. A redesign or evidence hold can preserve value without pretending the parcel has cleared diligence.
Use staged feasibility gates
Release the next spend only after the preceding gate meets its acceptance criteria. A later investigation should answer a defined uncertainty.
| Stage | Main question | Minimum output | Stop example |
|---|---|---|---|
| Project definition | What development decision is being made? | Controlled project basis and risk appetite | Intended route or decision remains undefined |
| Desktop screen | Is an obvious mismatch visible? | Parcel screen, constraints map, and evidence gaps | Known exclusion prevents the intended use |
| Rights and title | Can required land and routes be controlled? | Specialist report, control schedule, and conflicts | Required parcel or corridor cannot be secured |
| Field reconnaissance | Do desktop assumptions match visible conditions? | Dated observations, photos, access, and change list | Unsafe access or major undisclosed occupation |
| Survey and site studies | What are the measured boundary and physical conditions? | Accepted survey, hydrology, geotechnical, and specialist records | Data quality cannot support the next decision |
| Grid and concept | Is there a credible project and connection concept? | Route evidence, layout, studies, energy cases, and risks | No viable route survives current evidence |
| Commercial decision | Is further development spend justified? | Cost cases, schedule, register, and signed outcome | Unpriced blocking risks exceed appetite |
Each stage needs owner, inputs, outputs, acceptance, expiry, and change triggers. Keep desktop opinions separate from measured or authority evidence.
Classify evidence and uncertainty
Create an evidence ledger before interpreting results. Every important statement should identify source, date, parcel, coordinate system, scope, confidence, and reviewer.
| Evidence class | Appropriate use | Limitation |
|---|---|---|
| Official record or portal | Discover a record, layer, application, or current process | Does not prove title, approval, capacity, or field condition beyond scope |
| Owner statement | Identify claimed rights, use, history, and constraints | Needs independent verification for material decisions |
| Consultant observation | Record what a qualified person observed on a stated date | May not establish legal status or hidden conditions |
| Remote sensing | Screen terrain, land cover, water, access, and change | Resolution, date, season, classification, and field currency matter |
| Measured survey | Establish accepted surveyed features within defined accuracy | Does not itself decide legal title or all hidden conditions |
| Laboratory result | Characterize sampled material under stated method | Samples may not represent unsampled areas or future conditions |
| Authority response | Record the authority’s stated decision or guidance | Scope, conditions, expiry, appeal, and continuing validity matter |
| Network study | Evaluate stated connection conditions and assumptions | Does not guarantee later capacity, schedule, cost, or agreement |
| Assumption | Permit controlled preliminary analysis | Must carry owner, sensitivity, expiry, and closure action |
Evidence status
Mark each item verified, supplied, observed, assumed, conflicting, expired, or unknown. Do not relabel a missing result as conservative without justification.
Track conflicts between land records, owner statements, survey, occupation, maps, authority information, and site observations. Name the evidence needed to resolve each conflict.
Decision expiry
Set a review date and change triggers. Recheck after changes to boundary, capacity, technology, route, regulation, grid, hydrology, land use, environment, schedule, or commercial basis.
A still-live portal entry does not keep an old feasibility conclusion current. Record the date and scope of every recheck.
Verify parcel, title, control, and possession
Use jurisdiction-specific land, cadastral, registration, revenue, survey, and legal specialists. No central portal or consultant can prove clean title for every parcel.
The Department of Land Resources DILRMP page describes national context for state-led land-record modernization. A portal record or digitised map is not a parcel legal opinion.
Parcel register
Record parcel identifiers, coordinates, gross area, record source, registered owner, claimed possessor, land use, encumbrances, disputes, acquisition history, and legal-review status.
List options, leases, purchases, licences, easements, access rights, cable rights, substation land, construction rights, and operating rights separately. Capture term and conditions.
Identify mortgage, charge, lien, tenancy, inheritance, co-owner, government, common, community, grazing, cultivation, possession, and litigation issues where applicable.
Reconcile 4 boundaries
Compare legal parcel description, cadastral representation, measured boundary, and visible fence or occupation. They may not align.
The Survey of India’s boundary-survey guidance distinguishes several boundary processes. General guidance does not settle a parcel dispute.
Do not shift a surveyed line to match a desired layout. Resolve discrepancies through the appropriate specialists and process.
Land control schedule
For every required parcel and corridor, record counterparty, right type, area, term, consideration basis, conditions, access, assignment, financing, default, termination, restoration, and handback.
Check whether rights cover survey, drilling, construction, roads, drainage, cable, substation, operations, security, vegetation, water, and emergency access.
An owner signature may not bind every interest holder. Qualified counsel should review authority and enforceability under the actual jurisdiction.
Reconcile access, corridors, and third-party interfaces
A viable panel area can fail because the access road, cable route, substation plot, drainage outlet, or construction corridor cannot be controlled.
Access hierarchy
Trace public road to parcel entrance, internal roads, block access, substation access, emergency routes, and maintenance routes. Record ownership and legal rights.
Inspect widths, grades, curves, bridges, culverts, overhead lines, gates, settlements, seasonal conditions, axle limits, and turning space. Identify improvement scope and permissions.
Cable and evacuation corridor
Map proposed line, cable, crossing, tower or pole, bay, and substation land. Record every third-party parcel and crossing authority.
Identify roads, rail, rivers, canals, pipelines, utilities, forests, settlements, and sensitive areas. A straight map line is not an acquired or approvable corridor.
Construction and temporary rights
Define laydown, storage, batching, workforce, temporary utilities, parking, crane pads, spoil, borrow, waste, and demobilisation areas. Temporary use still needs control and restoration.
Record seasonal and community use. Construction access should not assume uninterrupted availability across harvest, monsoon, festivals, or local events.
Calculate usable land without a universal ratio
Gross acreage is not developable area. Build an auditable area reconciliation rather than applying one acres-per-MW shortcut.
| Area class | Definition | Evidence source |
|---|---|---|
| Gross | Entire stated parcel set | Current parcel schedule |
| Excluded | Area unavailable by law, rights, hazard, or fixed constraint | Specialist and authority evidence |
| Constrained | Area usable only with condition, mitigation, or cost | Constraint register |
| Developable | Area currently available for concept design | Controlled geometry and evidence date |
| Disturbed | Area affected by plant, roads, drainage, construction, or facilities | Concept and construction basis |
| Contingency | Reserved area for uncertainty, change, or execution | Documented risk basis |
Map boundaries, setbacks, water, drains, flood paths, slope, shade, habitats, structures, utilities, roads, substations, cable corridors, fire routes, and construction zones.
Use the solar land area calculator guide only after controlling inputs. A calculator cannot decide legal or environmental availability.
Run low, base, and high usable-area cases with explicit assumptions. These are parcel scenarios, not universal density claims.
Screen planning, environmental, and social constraints
Requirements vary by land classification, location, project route, capacity, technology, and jurisdiction. Use qualified specialists to build the applicability register.
The official PARIVESH portal supports clearance discovery, applications, and tracking. Presence or absence does not decide applicability or approval.
The PARIVESH Know Your Approvals workflow provides tentative guidance. Its output is not a legal or approval conclusion.
Land-use and planning screen
Record current and proposed land use, conversion or permission route, setbacks, zoning, local-body controls, building or development rules, and other applicable processes.
Do not infer permission from nearby solar development. A neighboring project may have different parcels, dates, rights, capacity, technology, or approvals.
Environmental screen
Map forests, protected or sensitive areas, wetlands, water bodies, drainage, coastal conditions, habitats, biodiversity, cultural resources, and cumulative impacts where applicable.
Record source date, buffer basis, field verification, season, specialist, applicability, and authority. A map layer should trigger review, not decide it alone.
Social and community screen
Identify settlements, structures, occupation, agriculture, grazing, access, livelihood, common use, vulnerable groups, resettlement, community assets, and stakeholder concerns.
Plan engagement through qualified teams and lawful processes. Do not describe silence, one meeting, or an owner statement as community acceptance.
Other interfaces
Screen aviation, defence, mining, quarrying, roads, rail, water, pipelines, utilities, fire, labour, and local emergency requirements where relevant.
Create separate applicability, evidence, action, and expiry fields. Avoid combining unrelated permissions into one “approvals clear” status.
Move from remote screening to measured survey
Remote sources help plan fieldwork. They do not replace accepted boundary, topographic, geotechnical, hydrology, or environmental evidence.
The Bhuvan thematic-data page describes Indian remote layers. Record layer date, scale, resolution, classification, accuracy, coverage, and field currency.
Desktop screen
Compile parcel geometry, elevation, slope, land cover, water, drainage, flood indicators, erosion, waterlogging, roads, settlements, utilities, and change history. Mark source limitations.
Compare multiple dates and seasons where material. One cloud-free image may hide monsoon water, crop use, vegetation, or temporary occupation.
Field reconnaissance
Plan safe access, permissions, route, weather, team, equipment, communications, emergency response, and stop-work triggers. Record date and observed conditions.
Verify visible boundaries, occupation, access, drainage, water marks, erosion, utilities, structures, vegetation, soil exposure, rock, dumping, and community use.
Survey specification
Define coordinate reference system, datum, benchmarks, accuracy, coverage, contour interval, breaklines, features, control points, quality checks, and acceptance.
Require drawings, point data, surfaces, reports, photos, control records, and native files. State what is excluded and who can rely on the work.
Use the solar drone survey guide and site survey checklist for field-work depth. Drone coverage does not settle title or hidden conditions.
Investigate terrain, hydrology, and ground conditions
Physical suitability depends on technology, layout, foundations, roads, drainage, climate, and operating plan. Design the investigation from the concept and risk register.
Terrain and earthworks
Analyze slope distribution, aspect, local breaks, ridges, depressions, cut, fill, retaining, erosion, haul, spoil, and construction tolerances. Avoid relying on average slope.
Test layout and road sensitivity across terrain cases. A parcel can fit modules while requiring unacceptable grading or retaining work.
Hydrology and drainage
Map catchments, natural drains, flood paths, water bodies, culverts, outlets, waterlogging, scour, groundwater, erosion, and downstream receptors.
Record rainfall basis, model method, boundary conditions, survey date, field evidence, climate assumptions, and uncertainty. Use the required jurisdiction-specific design criteria.
Do not block natural drainage with rows, roads, foundations, fencing, or spoil. Price land and outlet rights for drainage measures.
Geotechnical investigation
Plan boreholes, trial pits, tests, samples, depths, locations, laboratory scope, and reporting from the foundation and road concept. Record access and reinstatement.
Assess soil and rock profile, bearing, settlement, pull-out, drivability, corrosivity, earth resistivity, groundwater, variability, seismic context, and material reuse where applicable.
Use the geotechnical survey guide for investigation procurement. A few convenient samples do not characterize a large variable parcel.
Climate and operations
Screen wind, cyclone, heat, dust, salinity, fire, vegetation, soiling, cleaning water, security, and maintenance access. Link each issue to design and cost.
Establish a credible grid route
Grid feasibility is a separate workstream. A nearby line or substation does not prove capacity, connection rights, route, approval, cost, or schedule.
Define the route
Record project route, point of connection, voltage, ownership boundary, line length, corridor, crossings, bay, substation works, metering, protection, communications, and telecommunications.
Identify the applicable state, distribution, captive, open-access, or inter-state process. Do not transfer one route’s requirements to another.
The CERC current-regulations page supports inter-state regulation discovery. It does not apply automatically to every project.
The CTUIL connectivity procedures page supports inter-state application discovery. It does not prove a project’s connection or capacity.
Evidence ladder
Separate map proximity, enquiry, application, acknowledgement, queue, study, offer, approval, agreement, construction, testing, energization, and operating permission.
For each step, record assumptions, conditions, security, milestones, expiry, studies, upgrades, route rights, costs, curtailment, reactive power, power quality, SCADA, and metering.
Electrical safety and approvals
The CEA 2023 safety regulations page is a national reference. Actual design, inspectorate, testing, and approval duties remain project specific.
Do not promise connection before the responsible parties issue and maintain the required evidence. Keep route alternatives in the risk register.
Build concept layout and energy cases
A concept layout tests usable area, infrastructure, terrain, drainage, access, and capacity sensitivity. It is not construction-ready design.
Layout contents
Show exclusions, constrained areas, setbacks, blocks or tables, inverter or power-station areas, substation, cable corridors, roads, drainage, fire and emergency routes.
Include construction zones, laydown, spares, security, temporary works, maintenance access, and expansion assumptions. Keep coordinate system and version controlled.
Use the ground-mount design guide after the parcel clears the appropriate gate. Detailed ground-mount design services belong later.
Energy assessment basis
Record weather source, period, validation, horizon shading, near shading, terrain, albedo, soiling, temperature, clipping, electrical losses, availability, and grid constraints.
Run sensitivities for usable area, capacity, layout, losses, curtailment, and uncertainty. Do not present a modeled result as guaranteed generation.
The energy-yield assessment guide covers provider diligence. The P50 and P90 guide explains probability outputs and their limits.
Test constructability and operating access
Concept engineering must show how equipment, people, and services reach the site through construction and operations.
Logistics
Trace supplier or port route where relevant, roads, bridges, culverts, grades, clearances, turning, delivery windows, permits, crane access, and piling access.
Identify workforce, accommodation, utilities, water, power, communications, medical response, security, storage, workshops, and temporary facilities.
Seasonal constraints
Map monsoon, flood, heat, dust, wind, crop, fire, access, community, and environmental windows. Connect each restriction to fieldwork, construction, and schedule.
Interfaces and restoration
Define responsibilities for roads, drainage, grid works, utilities, fencing, waste, spoil, vegetation, landowner commitments, community commitments, and demobilisation.
Price reinstatement and handback. Construction feasibility should not assume permanent occupation outside controlled rights.
Use the ground-mount EPC guide only after defining this basis. EPC procurement does not replace development-stage feasibility.
Assign specialist roles and reliance
No single consultant should be assumed competent or independent across every discipline. Build a responsibility matrix.
| Role | Core responsibility | Boundary |
|---|---|---|
| Developer | Project basis, integration, decisions, budget, and risk | Does not replace specialist opinions |
| Landowner or counterparty | Supplies claimed rights and records | Statements require verification |
| Land lawyer | Jurisdiction-specific rights, title, documents, and risks | Does not survey physical boundaries |
| Cadastral or topographic surveyor | Measures defined boundary or site features | Does not decide ownership without legal process |
| Geotechnical specialist | Plans, samples, tests, interprets, and reports ground conditions | Results depend on investigation coverage |
| Hydrologist | Assesses catchment, drainage, flooding, scour, and outlets | Requires suitable survey and climate inputs |
| Environmental and social team | Screens, studies, engages, and supports applicable processes | Authorities make approval decisions |
| Grid consultant | Identifies route, studies, applications, and conditions | Network parties control their decisions |
| Designer and energy modeller | Builds concept, calculations, and sensitivities | Depends on controlled inputs |
| Commercial or tax adviser | Reviews costs, contracts, tax, and scenarios | Does not create technical suitability |
| Lender engineer or independent reviewer | Reviews evidence for stated reliance | Review scope must be defined |
Record competence, licences where applicable, conflicts, independence, insurance, subcontractors, data security, deliverables, reliance, liability, and duty of care.
Authorities, utilities, owners, and communities retain their own roles. A consultant cannot guarantee their decisions.
Stage the investigation spend
Create a release plan that spends against decision-changing uncertainty. Do not commission every specialist before the parcel clears basic rights and fatal-flaw screens.
Investigation package fields
Normalize proposals by parcel, area, route, stage, discipline, field days, boreholes or tests, survey coverage, accuracy, laboratory scope, reports, and native files.
Include revisions, meetings, travel, tax, third parties, schedule, assumptions, exclusions, reliance rights, insurance, data security, change process, and exit.
Hold points and stop triggers
Examples include unsafe field conditions, missing access permission, unresolved title conflict, boundary mismatch, sensitive-area trigger, flood evidence, or no credible grid route.
Define who can stop work and restart it. Protect field teams from commercial pressure to bypass safety or permissions.
Data room and RFIs
Use one controlled data room with versions, permissions, source, date, coordinate system, status, and superseded records. Preserve native deliverables.
Track requests for information with owner, question, source, due date, response, conflict, decision impact, and closure. Avoid decisions from unlogged messages.
Change control
Review boundary, capacity, technology, route, layout, survey, hydrology, grid, land-use, environment, schedule, and cost changes. Identify which conclusions must be rerun.
Model complete development and lifecycle cost
Classify every value as known, quoted, estimated, or unknown. Do not enter zero for missing rights, studies, mitigation, or connection work.
| Cost group | Required scope |
|---|---|
| Land and rights | Options, leases, purchase, access, cable, substation, taxes, and legal work |
| Surveys and studies | Boundary, topography, geotechnical, hydrology, environment, social, grid, and energy |
| Development | Applications, approvals, engagement, advisers, data, insurance, and management |
| Site preparation | Earthworks, retaining, drainage, erosion, roads, bridges, culverts, and clearing |
| Plant infrastructure | Foundations, fencing, security, water, communications, and operating access |
| Grid route | Corridor, line, crossings, bay, substation, studies, security, and interfaces |
| Mitigation | Environmental, social, livelihood, restoration, monitoring, and commitments |
| Risk and time | Contingency, escalation, financing delay, season, redesign, and unknowns |
| Operations and exit | Access, vegetation, drainage, security, restoration, handback, and decommissioning |
Run low, base, and high cases for capacity, usable area, earthworks, drainage, foundation, grid, mitigation, schedule, and unknowns. Show every assumption.
Do not publish universal land values, investigation costs, returns, or schedules. Use parcel-specific evidence and current adviser input.
Maintain the constraint and decision register
Classify each issue fatal, blocking, redesign, commercial, monitor, or accepted with condition. Define these terms for the project.
| Class | Meaning | Required record |
|---|---|---|
| Fatal | Prevents the defined project under the accepted basis | Evidence, approver, and no-go consequence |
| Blocking | Must close before a stated gate | Owner, evidence, due date, and stop condition |
| Redesign | Requires changed boundary, route, technology, or capacity | Options, cost, schedule, and approvals |
| Commercial | Can proceed if priced and accepted | Allowance, payer, residual risk, and authority |
| Monitor | Needs later recheck or operating observation | Trigger, frequency, owner, and threshold |
| Accepted with condition | Residual risk accepted under stated control | Condition, approver, expiry, and consequence |
Finish with a signed decision register. Include outcome, decision date, evidence cut-off, open conditions, next spend, responsible approver, and expiry.
Evaluate Heaven Designs under identical gates
Disclosure: SurgePV and Heaven Designs have a commercial relationship. Heaven Designs receives the same scope, competence, independence, specialist, fieldwork, accuracy, acceptance, reliance, security, schedule, price, and exit checks as every consultant.
The Heaven Designs land-feasibility page is related-party first-party scope discovery. It mentions contour mapping, soil testing, earth resistivity, and geotechnical reports.
Those statements do not prove parcel-specific title, cadastral, legal, environmental, hydrology, grid, laboratory, approval, reliance, accuracy, field coverage, or certification scope.
Use the Heaven Designs services page only to start a parcel-specific proposal. Require disciplines, people, fieldwork, deliverables, exclusions, schedule, price, reliance, and specialist boundaries.
This page gives Heaven Designs no rank and makes no approval, title, grid, capacity, yield, cost, schedule, or outcome claim.
Approve the next action, not the entire future
Feasibility should release a defined next action with controlled evidence. It should not imply construction readiness when specialist work remains pending.
Update the data room, constraint register, cost cases, schedule, and decision after each gate. Close or reclassify every material issue with evidence.
SurgePV is separate solar design software. It does not perform field surveys, title review, legal diligence, environmental studies, geotechnical work, grid studies, approvals, or land-feasibility services.
Frequently asked questions
What does a solar land feasibility study include?
It should cover decision basis, land control, title review, boundaries, access, land use, environmental and social constraints, surveys, terrain, drainage, and ground conditions. It should also cover grid route, concept layout, energy assumptions, constructability, schedule, cost, and residual risk.
Does an online land record prove clean title?
No. A portal record or digitised map supports discovery within its scope. Use jurisdiction-specific land, registration, cadastral, survey, and legal specialists to verify ownership, encumbrances, boundaries, possession, conversion, rights, and transaction documents.
How much land is needed per MW of solar?
There is no universal acreage ratio. Calculate gross, excluded, constrained, developable, disturbed, and contingency areas from technology, terrain, setbacks, drainage, roads, blocks, substations, cable routes, environmental conditions, construction zones, and expansion assumptions.
Is a desktop solar land study enough?
Desktop work can reject obvious mismatches and plan investigations. It cannot replace parcel-specific title review, boundary survey, field reconnaissance, topography, geotechnical work, hydrology, environmental and social review, grid studies, or authority decisions.
What is a fatal flaw in solar land feasibility?
A fatal flaw prevents the intended project under the defined evidence and risk basis. Examples can include unavailable land control, an unresolvable route, prohibited use, or an unmitigable impact. Classification remains parcel and jurisdiction specific.
Does a grid portal or application prove connection capacity?
No. A portal, queue position, acknowledgement, or preliminary response has only its stated meaning. Confirm the applicable route, studies, point, voltage, capacity, line rights, conditions, agreements, approvals, costs, schedule, and continuing validity.
What should a solar land survey deliver?
Define boundary and topographic scope, coordinate reference, datum, benchmarks, accuracy, coverage, contours, features, exclusions, utilities, drainage, access, and control points. Also define field dates, equipment, quality checks, drawings, reports, native files, and acceptance criteria.
How long does a solar land feasibility study take?
No universal duration applies. The schedule depends on parcel records, access, season, survey area, field safety, laboratory work, and specialist availability. Authority processes, network studies, conflicts, revisions, stakeholder engagement, and the decision stage also matter.
How should Heaven Designs be evaluated for land feasibility?
Treat its pages as related-party first-party scope discovery. Apply the same competence, independence, specialist, fieldwork, accuracy, deliverable, acceptance, reliance, security, schedule, price, change, and exit checks used for every consultant.
