The land development process: from raw land to finished lots

By Adam Chandler, founder of Pangea · August 31, 2026

The land development process is how raw land becomes buildable, serviced property: you evaluate a site, put it under contract, prove it works, win the approvals to change it, engineer the plans, build the streets and utilities, record the new lots, and then either build on them or sell them. Most practitioners describe it in seven phases — feasibility, due diligence, entitlement, engineering and permitting, horizontal construction, platting and acceptance, and vertical construction or lot sale.

The order matters more than the names. Nearly every expensive mistake in land development comes from spending money in one phase on a question that belonged to the phase before it.

What is the land development process?

It is the sequence of approvals, engineering, and construction that turns a parcel into legal lots that can be built on and served by public infrastructure. Development is not one transaction — it is a chain of conditional steps, each worth paying for only if the one before it came back clean.

Two things separate it from vertical construction. Most of the risk is regulatory rather than technical — the hard question is usually not can we build this but will they let us, and on what conditions. And a pro forma written at acquisition rests on assumptions about approvals, densities, fees, and infrastructure costs that nobody will confirm for a year or more.

What are the phases of the land development process?

Seven, in this order. Names vary by firm; the sequence rarely does.

1. Site selection and feasibility. Screening parcels against a program: what the market wants here, what the zoning allows today, what the land is worth entitled versus raw, and whether a path between the two exists. Cheap on purpose.
2. Acquisition and due diligence. The parcel goes under contract with a feasibility period and refundable deposit, and you spend real money testing assumptions: title and ALTA survey, geotechnical borings, a Phase I environmental site assessment, wetlands delineation, floodplain, traffic, utility capacity letters, impact fees. The deliverable is a go/no-go before the deposit goes hard.
3. Entitlement. The discretionary approvals that establish what may be built: rezoning, conditional use permits, variances, subdivision maps, site plan and environmental review. Decided in public, by people who can say no, and where most of the value is created — see the entitlement process in real estate.
4. Engineering and permitting. Civil engineers produce construction drawings — grading and drainage, erosion control, streets, water, sewer, dry utilities — and run them through agency review until improvement plans are approved and permits issue. Comment-and-resubmit rounds live here.
5. Horizontal construction. Clearing, mass grading, storm and sanitary sewer, water mains, dry utility trenching, paving, curb and gutter, sidewalks, lighting, and the erosion controls that keep the site legal throughout.
6. Platting, acceptance, and bond release. The final plat is recorded, each lot gets a legal description, public improvements are inspected and dedicated to the municipality, the warranty period runs, and bonds are released. Money stays tied up until this closes.
7. Vertical construction or lot sale. The developer either builds, or sells finished lots to builders. Many land developers never do vertical work at all; delivering paper lots is the whole business.

How long does the land development process take?

Longer than the pro forma says, and no honest single number exists. The spread is wide: a by-right infill parcel in a permissive jurisdiction can go from contract to permits in under a year, while a greenfield subdivision needing a rezoning, an environmental review, and an off-site sewer extension can run several years before a truck moves dirt. Be skeptical of anyone quoting an average, sellers included.

What predicts the schedule is a short list of yes/no questions. Does the project need a legislative approval, or only administrative ones? Does it trigger environmental review? Are there wetlands, floodplain, or protected species on site? Is there capacity in the sewer and water systems, or does someone have to build it? Each yes adds a review body, a hearing cycle, or a permit with its own queue. Two habits are worth more than any estimate: run reviews in parallel wherever the agency allows it, and schedule to the resubmittal rather than the submittal — assuming zero comment cycles is how a schedule becomes fiction.

What is the difference between horizontal and vertical development?

Horizontal development builds everything that serves a lot; vertical development builds on the lot. Grading, streets, curb and gutter, storm drainage, water, sewer, and dry utilities are horizontal. Foundations, framing, and buildings are vertical.

The distinction splits the industry, not just the vocabulary. The two are financed separately — a land development loan for improvements, a construction loan for the buildings — and usually built by different contractors, often different companies entirely: a land developer delivers finished lots, and a builder takes it from there.

Which approvals and permits does a land development project need?

More than the local ones, which is what surprises first-time developers. Underneath the visible local track sit federal and state permits that attach to the physical work rather than the land use, with their own timelines and agencies.

• Local entitlements — rezoning, plat approval, site plan review, conditional use permits, variances.
• Improvement plans and construction permits — grading, right-of-way, utility connection, sometimes demolition.
• Stormwater permit coverage. Under the federal NPDES program, construction disturbing one acre or more of land — or less, when the work is part of a common plan of development or sale that will ultimately disturb one or more acres — requires permit coverage. That last clause catches phased subdivisions that assume each small phase stands alone. It does not.
• Section 404 permit. Discharging dredged or fill material into waters of the United States, including wetlands, requires a permit from the U.S. Army Corps of Engineers under Section 404 of the Clean Water Act, with EPA oversight. Whether a feature on your site is jurisdictional is a question for a delineation during due diligence, not a hope you carry into engineering.
• State and utility approvals — highway access permits, sewer extension approvals, water rights or will-serve letters.

Requirements vary by state and jurisdiction. Confirm them with the agencies that have authority over your site — this is an overview, not legal advice.

What actually delays land development projects?

Rarely a surprise in the ground — almost always a gap in the record, or an untracked dependency:

• Utility capacity discovered late — a will-serve letter that turns out to be conditional, or a lift station upsized on your dime.
• Conditions of approval nobody reread after approval day. Conditions carry trigger points — before grading permit, before first plat. Missing one stops the phase it gates.
• Resubmittal churn — a comment answered in a meeting but never reflected in the drawing set, so it returns next cycle.

The land development records worth keeping

A land development project runs for years, across a dozen consultants, several agencies, and a team that will not be the same at the end. Keep these per project, from the first pre-application meeting:

• Approvals and permits matrix — every approval required, the agency that grants it, its status, and its dependencies.
• Conditions of approval tracker — each condition, the responsible party, its trigger point, evidence of compliance, and sign-off.
• Meeting record — every pre-application, staff, utility, and consultant meeting: who was there, what the agency said it would require, what your team committed to, what stayed open. Turnover is the quiet killer: the person who heard the commitment is often gone by the time it matters.
• Comment and response matrix — each agency comment, the response, and the sheet where the change actually lives.
• Submittal log — what went in, when, what came back, and the resubmittal date. This proves whose delay it was.
• Bond register and expiration dates — what each bond secures and how it is released; and the lapse date of every approval, permit, and option, since extension requests have their own deadlines.

That discipline carries into construction, where the preconstruction meeting hands those conditions to the field team and the daily log holds them.

Where Pangea fits

Pangea is an AI notetaker built for architecture, engineering, and land development firms. It records meetings without a bot sitting in the call, writes minutes in your firm's own format, and files every meeting, decision, and document to the right project automatically. Ask it a project question and it answers with sources cited, and it pushes approved updates into the project management software you already run.

For land development the useful part is continuity. A due diligence call in February, a hearing in October, and a utility coordination meeting the following spring all belong to the same file — and whoever needs to know what the city engineer said about the sewer stub may not have been in the room. The FMI and PlanGrid study Construction Disconnected put time spent looking for project data and dealing with conflict at roughly 5.5 hours per person per week. That is the tax a project memory removes. If a coordinator on your team is the one holding all of this together, that is the role Pangea was built around. See it at pangeanotes.com; the trial is 14 days with no credit card.