Questions every developer runs into eventually.

"Buildable" and "zoned correctly" are two different questions, and conflating them is one of the most common ways developers get burned on a site. Zoning tells you what's legally permitted; buildability is about whether the site can physically and financially support that use.

Before you make an offer, you want answers to at least these:

• Utilities. Is there water and sewer capacity at the site today, or would you need to extend service — and who pays for that?
• Floodplain and wetlands. FEMA flood maps and wetland delineations can quietly eliminate a big chunk of a parcel's usable area.
• Access. Does the parcel have legal, recorded access to a public road, or does it rely on an easement that could be contested?
• Topography and soils. Steep slopes, poor drainage, or bad geotechnical conditions can add real cost before you pour a foundation.
• Encumbrances. Deed restrictions, easements, and HOA covenants don't show up in a zoning lookup, but they can restrict use just as effectively as zoning does.

A site can be zoned exactly right and still be undevelopable. A site can also be zoned wrong today and still be a great buy, if the path to rezoning is realistic. The zoning designation alone answers neither question.

A low price is often the market pricing in a problem you haven't found yet. Watch for:

• No utility line anywhere near the site, and no public commitment to extend one.
• A landlocked parcel with no recorded, unambiguous access easement.
• Floodplain, wetlands, or steep-slope overlays that weren't disclosed in the listing.
• Open code violations, liens, or active litigation tied to the parcel.
• A zoning designation that requires rezoning, in a jurisdiction with a recent history of denying similar requests nearby.
• A seller who can't produce a clean survey, or whose legal description doesn't match the plat.

None of these automatically kill a deal — plenty of great projects start on sites with one of these issues. But each one should change your price, your timeline assumptions, or your due-diligence budget before you go under contract, not after.

Longer than most developers think. Land prices react to development activity that's already visible — a permit filed, a rezoning approved, a road project announced. By the time a market shows up in casual conversation as "the next area," a lot of the upside is already priced in.

The earlier signals move slower and get less attention: capital improvement plans that commit to a road or utility extension years out, planning commission agendas with early-stage annexation requests, comprehensive plan updates that designate future growth corridors. These are public record, usually months to years ahead of the land search itself, and they're exactly what tells you where infrastructure — and therefore development — is actually heading, rather than where it already arrived.

These get used interchangeably in casual conversation, but they're distinct legal mechanisms with different timelines and different odds of approval:

• Zoning is the district designation currently on the property (R-1, C-2, M-1, and so on) — it defines what's allowed by right.
• Rezoning changes that designation entirely, through a vote by the governing body (typically after a Planning Commission recommendation). This is the slowest and most public path, because it changes what's legally permitted on the land itself.
• A variance is a narrow exception to a specific dimensional standard — a setback, a height limit, a lot-coverage maximum — usually granted by a Board of Zoning Appeals, not the full governing body. It doesn't change the zoning; it excuses one specific requirement, and typically requires showing a hardship unique to the property.
• A conditional (or special) use permit covers a use that the zoning code already allows in that district, but only with case-by-case review and conditions attached — a daycare in a residential district, for example. The use is permitted in principle; the permit is what lets you actually do it on your specific site.

Picking the wrong mechanism is a common way to waste months. A use that needs a conditional use permit doesn't need a full rezoning, and a dimensional problem that only needs a variance doesn't need either.

There's no single answer — it depends entirely on the jurisdiction — but the shape of the process is usually similar: staff review and a completeness check, a required public notice period, a Planning Commission hearing and recommendation, then a final vote by the City Commission or Council. In a straightforward case with no opposition, that sequence commonly runs somewhere in the range of two to four months from a complete application to a final vote.

The vote itself is almost never the bottleneck — once a Planning Commission recommends approval, the final governing-body vote often follows within a few weeks. What actually extends a timeline is everything around it: an incomplete initial application that has to be resubmitted, a contested public hearing that gets continued, a companion plat or site plan that has to move in parallel, or a utility capacity question that needs to be resolved before staff will recommend approval at all.

Because staff recommendations and Planning Commission recommendations are exactly that — recommendations. Planning staff evaluate technical conformance: does this comply with the zoning code, the comprehensive plan, the subdivision regulations. Planning Commissions weigh that technical review alongside public input and their own judgment, and in most states they can recommend denial even against a clean staff report. The final governing body (City Commission or Council) is even less bound — it's an elected, political body, and it can approve, deny, or attach conditions regardless of what came before it.

In practice, the things that flip an on-paper-clean project are usually raised live at the hearing: neighborhood opposition over traffic or character, a commissioner's concern about a use that technically conforms but doesn't feel right for the corridor, or a precedent worry about what approving this site means for the next request. None of that shows up in a staff report. It's exactly why reading the actual hearing history for a jurisdiction — not just its written code — matters before you assume an entitlement is routine.

Yes, through one of a few paths, roughly in order of how much they change: a variance if the issue is a specific dimensional standard rather than the use itself; a conditional use permit if the use is allowed in that district with conditions; a full rezoning if the use isn't permitted in the district at all; or, in many jurisdictions, a Planned Unit Development (PUD) or similar overlay, which lets you negotiate a custom set of standards for the site in exchange for more design review and public process up front.

Which path makes sense depends entirely on how far your plan is from what's currently allowed, and how the specific jurisdiction has historically treated similar requests — which is usually the more decisive factor.

This varies more by jurisdiction and project type than almost anything else in development. A simple single-family permit in a smaller city with an efficient plan-review process might clear in days to a couple of weeks. A commercial project requiring fire, health, and utility sign-off on top of the standard building review can run months, particularly if the initial submission is incomplete and triggers a resubmission cycle.

The single biggest lever you control is submission quality. A complete, code-compliant set on the first pass avoids the review-comment-resubmit loop that accounts for most of the "why is this taking so long" frustration developers report — that loop can add weeks or months per round, and there are often two or three rounds on a complex project.

A handful of causes show up again and again:

• Incomplete submissions that trigger a review-comment-resubmit cycle, sometimes more than once.
• Utility capacity or extension negotiations that weren't resolved before the permit application went in.
• Environmental review triggers — projects with federal funding attached, for instance, can be subject to NEPA review, which runs on its own timeline independent of the local approval process.
• Inspection scheduling backlogs, especially in fast-growing jurisdictions where inspector capacity hasn't kept pace with permit volume.
• Mid-construction change orders from conditions discovered once work starts — unexpected soil conditions, undocumented utility lines, and similar surprises.
• Material and equipment lead times that are set by the broader supply chain, not the project itself.

Most of these are foreseeable, if not fully preventable. The projects that stay closest to schedule are usually the ones that budgeted time and contingency for at least one of them, rather than assuming a best-case timeline.

Don't assume a line running past a site means it can actually serve your project — proximity and capacity are different things, and that gap catches developers regularly. The right first move is a direct conversation with the city or utility district's engineering department, not a GIS layer alone: ask specifically about available capacity at the site, not just whether a line exists nearby. Many jurisdictions require a downstream sewer or water capacity analysis for any project above a certain size, precisely because an existing line doesn't guarantee there's room left in it.

If service needs to be extended, who pays is jurisdiction-specific and often negotiable: some cities fund extensions through their capital improvement plan if the project aligns with a growth corridor already in the plan; others require the developer to fund the extension up front, sometimes with a reimbursement or recovery agreement if later development on adjacent parcels ties into the same line. Get this answer in writing before you finalize a pro forma — utility extension costs are one of the most common reasons an otherwise-solid deal stops working financially.

A feasibility study is a structured look — before you're committed — at whether a specific project on a specific site actually works: does the zoning support the use, is there market demand at a price the site can support, what do utilities and site work realistically cost, and does the resulting pro forma clear your required return. Done well, it also flags entitlement risk and permitting timeline honestly, rather than assuming the best case.

It's tempting to skip it on a site that "feels obviously right," but the cost of a proper feasibility pass is almost always small relative to the cost of a deal that falls apart six months into carrying costs, entitlement fees, and design work — or one that gets built and doesn't perform because a step was assumed rather than verified.

The specific tools vary by state and city, but a few show up repeatedly:

• Tax Increment Financing (TIF) captures the future increase in property tax revenue a project generates and redirects it toward eligible project costs — typically infrastructure — for a defined period.
• Industrial Revenue Bonds (IRBs) let a city issue bonds on a developer's behalf, often paired with a property tax abatement, usually tied to job creation or capital investment thresholds.
• Property tax abatements or PILOT (payment in lieu of taxes) agreements reduce or restructure the tax burden on a project for a set number of years.
• Opportunity Zone investment offers federal capital gains benefits for qualifying investments in designated census tracts.

Almost all of these require a public hearing and a vote by the governing body, and many jurisdictions apply some version of a "but for" test — the project has to demonstrate it wouldn't be feasible without the incentive. That test, and the public process around it, is often what determines the realistic timeline more than the mechanics of the incentive itself.

A Planning Commission is typically an appointed body of residents tasked with reviewing land-use requests against the zoning code and comprehensive plan, and making a recommendation. It's usually the more technically focused body, and its meetings are where most of the substantive back-and-forth on a project happens.

The City Commission or City Council is the elected governing body that takes the final vote — on rezonings, annexations, incentive packages, and anything requiring an ordinance or resolution. In most states, the governing body isn't bound by the Planning Commission's recommendation and can vote against it, though doing so against a strong staff and Planning Commission recommendation is less common and often politically costly. Tracking both bodies' agendas matters: a Planning Commission recommendation tells you where a project is headed, but it isn't the final answer.

Almost everything that eventually becomes news was public record months earlier. Planning Commission and City Commission agenda packets list every rezoning, annexation, and conditional use request before the hearing happens. Capital improvement plans lay out years of planned road, water, and sewer investment. Permit records show where builders are already active. Most of this is published on a city's own website, just spread across a dozen different departments and formats, and rarely indexed in a way that's easy to search by area or by strategy.

That gap — real signal, buried in public record, scattered across sources — is the specific problem Groundbreakable is built to watch continuously, so you're seeing it as it happens rather than reconstructing it after the fact from a permit filing or a news story.

An MLS or a public GIS/zoning portal is a lookup tool — you go to it with a specific address or parcel already in mind, and it hands back whatever record it has on file. It doesn't know what you're trying to build, doesn't tell you what changed recently, and doesn't connect a rezoning three miles away to the site you're actually watching.

Development intelligence starts from the other direction: it's built around a strategy — what you build, where, and what makes a site work for you — and continuously watches the public record for signals that match it, across planning activity, permits, infrastructure spending, and zoning changes, then explains why a given signal is relevant. It's the difference between a tool you have to know to search, and one that's already watching on your behalf.