Pre-Development Risk: The Checklist AI Can Run for Developers

The Pre-Development Risk Checklist, Answered First

Pre-development risk is everything that can kill a development deal between site control and construction start, and the checklist is the fixed set of checks that catches it while you can still act. AI runs the checklist by holding every risk category at once and flagging where a site fails or where data is missing, so no category gets skipped under a deadline. The categories are consistent across deals: entitlement and approval risk, constructibility, market, cost and financing, site and environmental, and timeline carry. What AI automates is the completeness, running every check every time and surfacing the gaps. What it does not do is clear a flag. A human decides whether each risk is fatal, workable, or priceable. The output is a ranked risk picture that turns a vague bad feeling into a specific, addressable list before you commit.

This checklist supports the whole feasibility decision the hub describes. The full pipeline is in AI feasibility analysis for real estate development.

What Actually Kills Deals Before Construction

The pre-construction phase is where development risk concentrates, and the data backs the intuition. A Federal Reserve Bank of Atlanta study of multifamily projects found 15.3 months on average from project announcement to construction start, more time than the construction itself (Atlanta Fed). That is over a year of exposure before a single unit generates revenue, and most of what goes wrong in a development goes wrong in that window. The cost of the approval process is part of why: regulation runs an average of 40.6% of multifamily development cost per a joint NAHB and NMHC study (NAHB and NMHC), and a separate NAHB study put it at 23.8% of a new single-family home's price (NAHB).

"The deals that die before construction almost never die of one big obvious thing. They die of the small thing nobody bothered to put on a list, on the one site where it mattered." Lucas Eschapasse, NextAutomation

The pattern in failed deals is not exotic risk, it is missed routine risk. A checklist exists because human attention is uneven under pressure, and the value of running it with a system is that the twentieth site gets the same complete pass as the first.

The Checklist, by Category

The list below is the spine. Each category is a cluster of specific checks; the table names the category and the question it answers, and each links to the deeper build where one exists.

Two categories carry the most weight and have their own deeper builds. Entitlement and approval is priced in entitlement risk modeling with AI, and the cost and timeline carry sensitivity lives in the AI development pro forma. The checklist is what ensures the other four categories get the same rigor, rather than being waved through because the first two looked fine.

Completeness Is the Feature

The point of running a risk checklist through a system is not that a machine is smarter about any single risk. It is that a machine does not get tired, does not run out of Friday, and does not decide that this site is probably fine because the last three were. Completeness is the feature. A flagged risk you decide to accept is a managed risk; a risk you never checked is the one that shows up as a surprise in month four, when your option period is gone and your capital is committed.

The forward-looking version of this discipline has a live proof surface. The architecture that watches approval status across a developer's jurisdictions and traces a change to a schedule impact is our permit tracking and entitlement monitoring system, which runs the same "catch the flag, route it to a human" pattern the checklist runs, on permits already in motion.

Turn the Checklist into a Go, Kill, or Renegotiate

A risk checklist is only useful if it drives a decision, and the three honest outcomes are go, kill, or renegotiate. A clean pass with priceable risks is a go. A fatal flag, an easement through the buildable area, an approval the jurisdiction will not grant, is a kill, and finding it early is the checklist paying for itself. The most valuable outcome is often the third: a real but addressable risk that becomes a price adjustment or a longer option period. A checklist that only ever says yes or no is missing the outcome that makes most deals better.

Run early, the checklist protects your capital and your calendar both, which in development are the same thing. How the whole pre-development stack gets built and deployed on your terms is in our developer implementation work.

Frequently Asked Questions

What is a pre-development risk checklist?

It is the fixed set of checks that catches everything that can kill a development deal between site control and construction start: entitlement and approval risk, constructibility, market, cost and financing, site and environmental, and timeline carry. Run through AI, every category gets flagged for failures or missing data so none is skipped under a deadline. A human still clears each flag; the output is a ranked, specific risk picture rather than a vague bad feeling.

What actually kills development deals before construction?

Missed routine risk, not exotic risk. Most of what goes wrong in a development goes wrong in the pre-construction window, which a Federal Reserve Bank of Atlanta study found averages 15.3 months from announcement to construction start, longer than the build itself. Deals rarely die of one big obvious thing; they die of the small check nobody put on a list, on the one site where it mattered.

Why run the checklist through a system instead of by hand?

Because completeness is the feature. A system does not get tired, does not run out of Friday, and does not assume this site is fine because the last three were, so the twentieth site gets the same complete pass as the first. A flagged risk you decide to accept is managed; a risk you never checked is the surprise that shows up in month four when your option period is gone and your capital is committed.

Does the checklist just give a yes or no?

It should drive three outcomes, not two: go, kill, or renegotiate. A clean pass with priceable risks is a go. A fatal flag is a kill, and finding it early is the checklist paying for itself. The most valuable outcome is often the third, a real but addressable risk that becomes a price adjustment or a longer option period. A checklist that only says yes or no misses the outcome that makes most deals better.

Which risk categories carry the most weight?

Entitlement and approval risk and the cost-and-timeline carry, because that is where development exposure concentrates. Regulation runs an average of 40.6% of multifamily development cost per a joint NAHB and NMHC study, and 23.8% of a new single-family home's price per a separate NAHB study, and the approval calendar drives the carry. Both have deeper builds, but the checklist exists to ensure the other four categories get the same rigor rather than being waved through.