I've watched entitlement teams and construction teams work at cross-purposes on enough projects to know the pattern by heart. A developer hires a land use attorney and a zoning consultant. They spend months securing entitlements, getting approvals, and navigating city requirements. The design gets approved. Everyone celebrates. Then a general contractor shows up six months later to actually build the thing and discovers that the approved design doesn't work on the ground. Setback requirements kill crane placement. Height limits force an expensive structural system. Parking ratios mandate extra underground levels that destroy the project economics. By then, it's too late to redesign. The city has signed off. You have to build what you approved, even if it costs significantly more than it should.
I led entitlement work on Wilson Tower, a 45-story office development at 410 E 5th Street in Austin, and I'm currently overseeing construction on The Travis ATX, a 50-story mixed-use tower at 80 Red River. I've seen this exact problem play out, and I've also seen what happens when you integrate construction thinking into the entitlement process from day one. The difference in final cost, schedule, and constructability is measured in millions. This article is about why that integration matters and how to make it work on your next project.
The Standard Broken Model
Here's how the conventional approach works. A developer identifies a site, contracts with a land use specialist and zoning counsel, and begins the entitlement process. These professionals are excellent at what they do—they understand municipal code, they navigate the political process, and they move approvals forward. But their objective is singular: get the project approved. Constraints that make a project harder to build don't typically register in the entitlement discussion because the person negotiating the approval conditions isn't the person who will build the project. They've never watched a concrete crew, never sat through a crane coordination meeting, never managed construction sequencing around utility shutdowns.
So the land use team secures conditions that satisfy the city—reduced setbacks in some zones to get density, increased height in others, parking requirements calibrated to zoning. The design team then makes those conditions work aesthetically and programmatically. The project gets approved. Six months later, when the general contractor does a constructability review, problems emerge. The building sits too close to the property line, which means a tower crane can't operate from the site—you need an expensive derrick or mobile crane instead. The height limit forced a particular structural system that's not cost-competitive for the span. The parking ratio created four underground levels instead of two, which means deeper excavation, bigger shoring, longer schedule, higher foundation costs. These aren't design problems. They're entitlement problems. The approvals created constraints that nobody thought through from a construction perspective.
The Real Cost of the Disconnect
Let me be specific about what this costs. On a 50-story tower, a tower crane is typically one of your largest capital expenses and one of your longest lead-time items. If your site doesn't allow crane placement because entitlements forced tight setbacks, you lose the efficiency of a single crane managing the entire superstructure. Instead, you rely on mobile equipment, jumping cranes, or internal hoisting systems. A mobile crane costs $10,000 to $15,000 per day. Over an 18-month construction period, those costs are not a line item—they're a budget killer. You could have negotiated different setbacks during entitlement if someone had raised the question. The city cares about setbacks as a land use matter. They don't inherently require smaller setbacks. But if nobody asks, the default often tracks existing neighborhood character or a formula that doesn't account for construction equipment.
Height limits that force structural compromises are equally expensive. If you're trying to build a residential tower with typical 12-foot floor-to-floor, and the entitlement process locked you into a specific total height that's tight, the structural engineer might be forced to reduce floor-to-floor or use a more expensive system to gain height. Reducing floor-to-floor on a residential tower has cascading effects on apartment size, which affects rent, which affects project return. Using a more expensive structural system (post-tensioned concrete instead of conventional concrete, for instance, or a steel frame instead of concrete) adds hard cost and schedule time. These decisions were made in the entitlement phase by people thinking about land use, not construction cost.
Parking ratios are another classic example. Cities require X spaces per unit or per square foot of retail. The land use team negotiates the ratio. If they get a favorable ratio, great—parking cost goes down. But if the ratio is locked into something high, or if the site topography forces parking below grade, the construction team inherits a deep excavation, extensive shoring, expensive concrete work, and a long critical path activity. A 50-story tower with four basement levels costs substantially more to build than one with two basement levels. That cost is often not recovered in the project because nobody revisited the parking requirement during entitlement to ask whether the city would accept a reduced ratio, a parking structure, or a different parking strategy. The entitlement team secured what they thought was a good approval. They didn't run construction numbers.
How Entitlement Conditions Affect Construction Sequencing
Entitlements don't just set physical constraints. They set operational constraints that directly affect construction sequencing and cost. Conditional use permits often come with phasing requirements. You might get approval for a 50-story tower with a condition that you complete the ground floor and public plaza in phase one before proceeding to the tower. That sounds reasonable from a city perspective—it guarantees you'll deliver certain public benefits. But from a construction perspective, phasing requirements create dependencies and extended mobilization. You're on site, you're setting up, you're building structural elements for the tower, but you have to stop and complete the plaza before you can proceed with the vertical work. That's schedule extension and remobilization costs that could have been anticipated if a constructor was in the conversation when the conditions were negotiated.
Traffic mitigation conditions often restrict delivery hours or limit the number of trucks on site daily. Noise ordinances cap concrete pours to certain windows of time. Vibration limits affect pile driving and heavy excavation. These aren't arbitrary—cities impose them to protect neighbors and manage impacts. But they directly compress the construction window. If your entitlement process locked you into restricted delivery hours because the land use team didn't push back, your material sequencing becomes inefficient. You're coordinating fewer deliveries across a tighter window. Critical materials might not arrive when the schedule requires them. Work sequences have to be adjusted to fit the operational constraints. All of this is buildable, but it's more expensive and slower than it needs to be.
The Integration Argument
Now imagine a different approach. A developer identifies a site and brings a general contractor or construction manager into the site selection and entitlement phase. Not to replace the land use professionals, but to supplement them with construction expertise. The GC looks at setback requirements and explains that a 25-foot setback doesn't allow tower crane placement, but a 35-foot setback does. That's a 10-foot difference with no land use impact—the building still complies with zoning, the facade still works, the neighborhood character is preserved. But suddenly you save $2 million in crane costs. The GC reviews the height constraint and suggests that the structural engineer has flexibility if you're willing to discuss post-tensioned concrete, which the current height cap requires but conventional concrete couldn't achieve. That's a conversation the entitlement team might have had with the city—maybe the city is indifferent to the structural system. Maybe they care about visual height, not structural height.
The GC looks at parking requirements and does the math. Three underground levels makes sense. Four doesn't—the marginal cost of the fourth level exceeds the revenue from the additional parking. Is there a way to reduce the parking ratio or provide alternative compliance? Maybe bike parking or a reduced ratio for transit-adjacent sites? These are conversations that land use professionals have all the time. But they happen in a vacuum if construction cost isn't represented. When the general contractor shows up with numbers and says "that fourth basement level costs $8 million and generates $1 million in revenue," you now have information the entitlement team didn't have.
Why Builder-Led Entitlements Matter
The person who understands how a building goes together should influence what gets approved. That doesn't mean the construction team should make entitlement decisions. The land use professionals are experts in municipal process, politics, and code. But construction expertise applied at the right moment can materially improve project economics. On The Travis ATX, we integrated construction sequencing into the entitlement discussion early. We identified that the site's narrow width would create crane conflicts if we assumed a conventional tower crane operation. We negotiated an entitlement condition allowing a mobile crane on the public right-of-way during foundation and core construction, with the understanding that we'd remove it before exterior work. That condition was something the city would grant—it's not inherently problematic. But it only came up because a constructor was in the conversation and knew to ask.
Similarly, on Wilson Tower, the original entitlement approval included a traffic condition that severely limited construction vehicle access during peak hours. Our team flagged that during the construction impact assessment phase. We proposed an alternative that achieved the same traffic mitigation objective but allowed material delivery to occur during a broader window. The city accepted it because the objective wasn't the specific hours—it was managing traffic impact. Once we reframed the condition in terms of traffic flow rather than time windows, there was flexibility.
When to Bring Construction Into the Conversation
The answer is simple: day one of site selection. Not after zoning approval. Not after the project is approved. From the moment you're evaluating whether a site works, you should have a constructor involved. The architect and land use team evaluate aesthetic and regulatory fit. The constructor evaluates buildability, sequencing, logistics, and cost drivers. When all three perspectives are present, the entitlement team makes more informed decisions.
The constructor should review preliminary approvals and identify specific conditions that will create constructability challenges or cost premiums. The land use team can then explore whether those conditions are negotiable, whether there are alternatives, or whether the cost is acceptable. The developer can make an informed decision about whether to proceed with the project, redesign to accommodate the conditions, or negotiate different terms with the city. That's a rational decision-making process. The alternative—learning about major constructability issues after approval—is reactionary and expensive.
Practical Steps for Your Next Project
When you're selecting your entitlement team, add a construction manager or general contractor to the working group. Ask them to do a preliminary constructability review based on the site conditions and proposed development program. Specifically, have them flag any aspects of the design or anticipated approval conditions that create construction cost premiums or schedule impacts. Have them quantify those impacts. Then use that information in your entitlement negotiation.
Before submitting final entitlement applications, conduct a construction impact analysis. What does the proposed design cost to build? What are the material delivery logistics? Where are the schedule risks? Which entitlement conditions create cost or schedule exposure? Are any of those conditions negotiable without losing the underlying city objective? If a condition protects traffic flow, is the specific time window essential, or is a different operational restriction acceptable?
Most importantly, structure your approval timeline to allow for this integration. If you've got three months to get a project approved, you don't have time to bring construction expertise into the entitlement conversation. But if you've got six or nine months, you do. Spend time upfront understanding the constructability implications of the approval conditions you're negotiating. It's an investment in the entitlement process that pays dividends in construction cost and schedule.
The Bottom Line
Separating entitlements from construction thinking costs money. It costs it in crane logistics, in structural systems you didn't need to buy, in basement levels that don't pencil, and in operational constraints that compress your construction window. The best way to prevent that cost is to integrate construction expertise into the entitlement process from the beginning. That doesn't mean letting the construction team make land use decisions. It means making sure the person who understands how to build a project has a voice in negotiating the conditions that will govern its construction. On major projects, that voice saves millions.