For more than a decade, Rollingwood's official position on the MoPac South expansion was some version of no. The city adopted a resolution in April 2015 opposing elevated lanes. Mayors wrote letters. Council members flagged design flaws at open houses. Then on April 22, 2026, Rollingwood joined West Lake Hills in sending the Central Texas Regional Mobility Authority a letter of conditional support.
That word, conditional, is doing more work than most residents realize. Rollingwood didn't soften its stance because the project got less disruptive. It shifted because the draft Environmental Assessment, published in February 2026, finally got specific enough that the city could name exact terms and put a number on what it wanted in return. The story here isn't that MoPac South is moving forward. It's that Rollingwood figured out what it could extract from a project it can no longer stop, and the number attached to that ask is bigger than anything CTRMA has promised the region as a whole.
What the City Actually Signed
The April letter listed three conditions required before Rollingwood and West Lake Hills would support the environmental assessment:
- Fund a diverging diamond interchange (DDI) at the MoPac and Bee Cave Road intersection
- Extend traffic noise barriers to the Rollingwood side of the highway, matching what's already planned on the Zilker side
- Maintain the previously designated lane elevation, rather than raising it further
The second condition is easy to miss but tells you something about how the project has been shaped so far. The draft EA's noise wall recommendations, the first time CTRMA has specified locations, currently extend farther on the Zilker side of MoPac than on the Rollingwood side. Rollingwood is asking to be treated the same as the neighborhood across the highway, not for something new.
The lane elevation condition traces back to a concern West Lake Hills Mayor James Vaughan raised in December 2024, when the design still showed an elevated overpass reaching its highest point directly above the Bee Cave Road and MoPac intersection. Vaughan described the merging pattern that would result as a kind of traffic joust, with drivers trying to reach the regular lanes crossing paths with drivers exiting toward Cesar Chavez, in both directions. The concern wasn't hypothetical distance from Rollingwood. It was the exact intersection Rollingwood residents use every day to get on and off MoPac.
The Number Rollingwood Is Actually Buying
CTRMA's own headline numbers for MoPac South are modest. By its 2045 traffic model, drivers who stay in the free lanes would save about four minutes traveling northbound and five minutes traveling southbound during peak commute hours, compared to doing nothing. Toll lane users could make the Slaughter Lane to Cesar Chavez run in eight minutes instead of sixteen, but that's a corridor-wide projection, not a Rollingwood-specific one.
Compare that to what Vaughan cited for the diverging diamond Rollingwood is holding out for: a 48% to 58% reduction in peak-hour delays at the Bee Cave Road and MoPac intersection specifically, broken down as 33% to 50% for eastbound traffic, 57% to 83% for westbound, and 75% for northbound. Those aren't projected regional averages. They're the delay reduction at the one intersection every Rollingwood commuter has to cross to reach either direction of MoPac.
That's the gap this post is built around. The project's marquee benefit is a few minutes shaved off an eight-mile corridor by 2045. The benefit Rollingwood negotiated for is a same-decade fix to the single chokepoint that actually governs how long it takes to leave the neighborhood. One is a regional average. The other is a local number that would show up in every resident's daily commute, assuming it gets built.
The Part That's Still Unfunded
Here's where the conditional part of conditional support matters most. As of the March 25, 2026 city council packet, the diverging diamond at Bee Cave Road is listed by CTRMA as "pending funding coordination with local municipalities." It is not part of the base schematic. Preliminary estimates put the intersection improvement at under $5 million, a small figure relative to the project's overall $825 million cost, but CTRMA has not committed that money, and Rollingwood's leverage to get it committed is exactly the conditional support it's now offering.
| Today | Under the current MoPac South design |
|---|---|
| Northbound MoPac express lane entrance near 15th Street | That entrance is eliminated under the proposed design |
| Access to Bee Cave Road from the southbound MoPac express lanes | That access point is also eliminated |
| No diverging diamond at Bee Cave Road and MoPac | A DDI is proposed but remains unfunded, contingent on coordination with Rollingwood and West Lake Hills |
| Noise barriers concentrated on the Zilker side of the highway | Rollingwood's support is conditioned on barriers extending to match on its side |
Those first two rows are both listed on Rollingwood's own city website as design elements the city has formally objected to. Losing the southbound Bee Cave Road exit from the express lanes means drivers headed home from downtown lose a direct express option at the interchange they actually use. This is the kind of detail that led Rollingwood City Administrator Ashley Wayman to flag express lane access, not overall travel time, as the design's single biggest impact on the city.
What Changes This Fall, and What Doesn't
Nothing about your commute changes yet. The public comment period on the draft EA closed May 3, 2026. CTRMA is now reviewing that input before submitting a final version to the Texas Department of Transportation, which will decide whether the project can proceed under a Finding of No Significant Impact or whether it needs to go back for a full Environmental Impact Statement instead, a more rigorous review that groups including the Save Our Springs Alliance and the City of Austin's Urban Transportation Commission have been pushing for, citing concerns about the Edwards Aquifer recharge zone that MoPac crosses. CTRMA's executive director James Bass has said that decision is expected sometime this fall.
Nothing has been funded for design or construction. The diverging diamond at Bee Cave Road stays theoretical until CTRMA and the two cities work out how to pay for it. The current express lane entrance near 15th Street keeps operating as-is. The elevated ramps proposed near Barton Skyway and Bee Caves Road, meant to let frontage road traffic reach the toll lanes mid-highway, exist only on paper.
What is real, and closer to home than most coverage of this project mentions, is the footprint the draft EA lays out just east of Rollingwood. The environmental assessment identifies 3.84 acres of temporary construction use inside Zilker Park, plus work that would affect the Butler Hike and Bike Trail and require widening the MoPac bridge over Lady Bird Lake, using construction barges and restricting boat access during the work. None of that touches Rollingwood's residential streets directly, but it's the same bridge and the same stretch of MoPac that connects Rollingwood to downtown, and it gives you a sense of scale for how far this project reaches before it even gets to the intersection Rollingwood actually cares about.
What to Watch
The fall 2026 TxDOT decision is the next real marker. If TxDOT clears the project under a Finding of No Significant Impact, watch for whether the diverging diamond at Bee Cave Road gets funded as part of that clearance or gets pushed into a separate, later negotiation. If TxDOT instead requires a full Environmental Impact Statement, the whole timeline extends, and the express lane access changes near Bee Cave Road stay a design on paper rather than a construction schedule.
Rollingwood's own MoPac South page keeps a running record of every letter the city has sent since 2015, which is a useful way to track how the city's position has actually moved over a decade, not just this spring. CTRMA's project site at mopacsouth.com hosts the draft environmental assessment and the technical reports behind it, if you want to see the traffic model and noise wall recommendations directly rather than take a summary's word for it.
This isn't a story about a neighborhood losing a fight it's been having for more than a decade. It's a story about a neighborhood that figured out the fight had changed shape, from stopping a highway to pricing the one intersection that actually matters to how it lives.
If you're weighing what a project like this means for a specific address in Rollingwood, whether you're buying, selling, or just trying to read the fine print on a listing near Bee Cave Road, Deep Parikh tracks these kinds of local mechanics as part of the job, not as an afterthought. Let's Connect.
