hardhatU
Process phase

Idea & Feasibility

Step 1 in the construction process

What happens

Before a single drawing exists, someone has to decide the project is worth pursuing at all. This phase turns a want ("we need more warehouse space," "this land could become housing") into a defensible plan for spending real money. It's mostly invisible to everyone except the people directly involved: no permit gets filed, no ground gets broken, but the decisions made here quietly shape most of what the project will ultimately cost and how well it actually works once it exists. Take a developer eyeing a vacant lot for a small retail building. It starts with site selection: is the parcel zoned for this use, does it have the utility capacity (water, sewer, power) the project needs, is the soil stable enough to build on without an expensive foundation redesign, is there enough room on-site for the parking the local code requires. A land surveyor runs a preliminary site survey, sometimes alongside a geotechnical borings report, while a market study asks a separate question entirely: will anyone actually rent or buy this once it's built. In parallel, someone assembles a rough order-of-magnitude budget, an estimate built on very little detail, closer to an educated guess than the line-item estimate the project will eventually get, meant only to tell the owner whether the idea is in the right neighborhood financially. If outside financing is involved, a lender or investor reviews that budget alongside the market study before the owner commits anything. Beneath the site and money questions sits one more decision that shapes everything downstream: how the project will actually be delivered. Design-Bid-Build, Design-Build, CM at Risk, and CM as Advisor each split risk and control differently between owner, designer, and builder, and switching methods later is disruptive enough that most owners commit to one here, before a designer is even hired. By the end of this phase, the owner has a real decision to make: move into Design with a workable budget and a chosen delivery method, or walk away having spent a small amount of money finding out the idea didn't work, instead of a large amount of money finding that out later.

How long this takes

For a small, straightforward project, feasibility can wrap up in a few weeks. For a large commercial project that needs financing, environmental review, or a zoning variance, it can stretch past a year before design even starts, let alone construction. What stretches it: an ownership group still debating the basic program (how big, how many units, what use), a lender requiring a formal appraisal and market study before releasing funds, or a site with an unresolved zoning or environmental question. What compresses it: an owner who has built the same kind of project before and already knows the site works, or a developer buying a property that's already entitled for the intended use.

Why this timing matters

This is the cheapest point in the entire project to change your mind, which is exactly why it's worth taking seriously instead of rushing through. A flawed assumption caught here costs a rewritten paragraph in a feasibility report. The same flawed assumption discovered during Design costs a redesign. Discovered during Permitting, it costs a resubmission and months of delay. Discovered during Construction, it can cost actual demolition of something already built. Every phase after this one makes a bad idea more expensive to walk back, which is why this phase exists: to find the fatal flaws while they're still just sentences on paper.

Who's involved

Owner/DeveloperFeasibility ConsultantCivil EngineerLand SurveyorLender/InvestorCost Estimator

Common misconception

People often assume this phase is mostly about what the building will look like. In practice the first questions are site, zoning, and money, not design, and an architect may well be in the room helping test an early concept, but the concept only turns into real design work once those underlying questions are actually answered. Skipping ahead to a full design before feasibility is settled is one of the more common ways an owner ends up paying for drawings of a building that turns out it can't actually get permitted or financed.

What can go wrong

The most common failure here is an owner falling in love with a site or an idea and rushing past due diligence, only to discover a zoning restriction, a contamination issue, or a utility capacity problem during Design or Permitting, once real money is already committed to designers. A close second is an overly optimistic rough budget with no real contingency built in, which sets an expectation the project can't actually meet, and turns into a painful value-engineering fight later when the real numbers finally show up. Choosing the wrong delivery method here causes quieter, slower-building damage. A lump-sum Design-Bid-Build contract works well when the scope is well understood in advance, but forces expensive change orders on a project that's still evolving as it's designed. A fast-moving, ill-defined project often fits Design-Build or CM at Risk better, since those let the builder weigh in earlier. Getting this pairing wrong doesn't show up as a single dramatic failure; it shows up as friction and disputes that recur throughout the rest of the project.

In practice

Real projects sometimes blur this phase into Design rather than finishing it cleanly first. A developer might sketch an early concept with an architect specifically to test whether an idea is feasible, rather than confirming feasibility and only then hiring a designer, especially under a Design-Build delivery method, where design and feasibility are meant to overlap from day one. Some projects skip formal feasibility almost entirely: a retail chain building its fortieth nearly identical store already knows the format works, so the "feasibility study" is really just confirming this specific site doesn't have an unusual problem, not proving the whole concept from scratch.