Domain knowledge is the advantage. Technology makes it move faster.
Bailey's land-use intelligence work is not generic AI layered on top of civil engineering. It is local planning judgment, repeatable process, organized records, clean drawings, and technology moving together so decisions get clearer earlier.
The useful future of AI in land development is not a chatbot guessing its way through a zoning code. It is a firm with real domain knowledge using better systems to find the right records, ask sharper questions, document what changed, and get human judgment to the decision point sooner. That is the work Bailey is building toward.
Public information is not the same as intelligence
Most of the raw material in land-use planning is technically public: zoning maps, comprehensive plans, staff reports, hearing minutes, approved conditions, utility maps, transportation comments, and old project records. Public does not mean usable. It usually means scattered across portals, PDFs, agendas, minutes, GIS layers, and institutional memory.
Intelligence starts when those records become answerable. Not just "what does the code say?" but "which part of the code will matter for this parcel, this jurisdiction, this reviewer, this hearing body, and this schedule?"
The advantage is knowing which questions matter
Technology can retrieve, summarize, compare, and watch for changes. That is useful. But on its own, it still does not know which question is worth asking. In land development, the expensive questions are specific:
- Can this parcel support the use the owner imagines? The answer lives across zoning, comp-plan alignment, access, utilities, drainage, and political precedent.
- What will slow the application down? Missing exhibits, unresolved agency comments, neighborhood concerns, and code conflicts all create different kinds of schedule risk.
- What has this jurisdiction actually approved? The adopted code matters, but so does the pattern of recent staff recommendations, commission findings, council conditions, and appeals.
That is why Bailey treats AI and automation as accelerators for human expertise. The tools help surface the work. The judgment still has to come from people who understand the development process.
From leadership direction to planning capacity
Shane Leavitt has pushed Bailey toward a simple idea: make the system clearer, and the outcomes get better. For a land-development firm, that means the work cannot live only in inboxes, memory, and one-off heroic effort. It has to become visible enough to manage and repeatable enough to improve.
Kelli Black turns that direction into operating discipline. The question underneath the work is blunt and practical: what are we doing twice, what is falling between handoffs, what should be documented, and what should become a tool?
On the planning side, Kindi Moosman brings the jurisdictional and entitlement judgment: how to read a code, understand an application path, prepare the right materials, and keep agencies moving. That kind of knowledge is the source material for better systems.
Aaron Sperry adds a new kind of planning capacity: process, automation, documentation, and technology support from inside the land-development workflow. His background in operations, business intelligence, and AI-native software makes him useful in the space between "we know how we do this" and "the next person can follow it, improve it, and run it faster."
Where Justin fits
Intelligence still has to land in a plan set. That is where Justin Moosman strengthens the production side of the work. As a drafter with AutoCAD, Civil 3D, and Bluebeam experience, Justin helps keep drawings clean, current, and aligned with the latest review path.
That matters because a planning insight that never reaches the drawings is just a note. A condition of approval that never makes it into the plan set becomes a delay. A changed exhibit that is not coordinated becomes a comment cycle. Drafting discipline is part of land-use intelligence because the record, the application, and the drawings all have to tell the same story.
The Bailey pattern
The pattern we are building is straightforward:
- Records become data. Staff reports, hearing outcomes, zoning code, project history, and submittal requirements are organized so they can be found again.
- Data becomes information. The team can compare sites, jurisdictions, timelines, constraints, and prior approvals instead of starting from zero.
- Information becomes judgment. Planners and engineers decide what actually matters for the parcel in front of them.
- Judgment becomes action. The right application path, exhibit package, plan update, or client recommendation moves forward.
What this means for developers
The point is earlier clarity. Before a client spends heavily on design, they should know where the entitlement risk lives. Before a submittal goes in, the package should match the jurisdiction's expectations. Before a hearing, the team should know the record, the likely questions, and the conditions that may matter.
That is where technology earns its place: not as a novelty, but as a way to make Bailey's domain knowledge move faster, travel farther, and show up earlier in the project.
Bring Bailey in before the expensive questions become expensive surprises. The earlier the record is clear, the more options a project still has.
