Blog
Why Speed Is a Design Constraint: How Modern Engineering Firms Deliver Infrastructure Faster
Speed is a design constraint: most Texas infrastructure delays come from how engineering firms are organized and bill, not from the agency review clock itself.
Quick answer
Most engineering delays on Texas infrastructure projects are not caused by regulatory timelines. They are caused by how the delivering firm is organized. Hourly billing gives a firm no structural reason to finish faster. Treating speed as a design constraint does. Every week a complete application reaches the agency sooner is a week sooner in the review queue, and a week less of carrying costs for the owner.
Why was the traditional engineering model never designed for speed?
Because it was built to record time, not to compress it. Most engineering firms in Texas run on a simple model: hire licensed engineers, bill hours against a multiplier, and deliver when the work is done.
That model was designed for a different era. Communication was slow. Drawings needed physical review. Projects moved at the pace of paper.
Today, clients are not asking for more time. They are asking for less. A firm billing by the hour earns the same whether a deliverable takes three weeks or six. The engineer keeps billing. The client absorbs the delay. The project loses calendar time it cannot recover.
That is not a critique of individual engineers. It is a critique of the model. I left that model behind when I started MES, and speed as a design constraint is one of the rules I built the firm on.
Where do traditional firms lose time on every project?
In the same four places, almost every time. The delays that stretch engineering schedules are not random.
Queue time. New projects enter a shared resource pool behind existing work. A developer who signs a contract may wait weeks before anyone opens the file. The proposal shows a start date. It does not show the queue.
Late information. When a firm starts design before upstream inputs are confirmed, it designs to assumptions. When those assumptions change, it redesigns. Getting utility confirmations, geotechnical data and the right TCEQ permit path settled before design starts removes the most common source of rework.
Internal approval bottlenecks. In larger firms, every deliverable passes through several review layers before it reaches the client. Each layer adds days. Modern tools catch many routine errors automatically. The multi-layer manual process was built for a world where every error was caught by hand.
Client coordination gaps. When the engineering firm is not part of the client's project rhythm, routine questions wait for scheduled meetings. A developer confirming a tap size should not have to wait for the next coordination call.
What actually changes when speed is a design constraint?
Speed stops being a goal and becomes a condition that every project structure and review process must meet. In practice, that changes three things.
Parallel workstreams instead of sequential handoffs
Hydraulic modeling, utility coordination, permit pre-application work and construction document production do not all have to happen in sequence. A firm organized around delivery maps which workstreams depend on each other and runs the rest at the same time. The schedule shortens without any single workstream being rushed.
Reusable frameworks instead of reinvention
A lift station serving a Texas subdivision is not a new engineering problem every time. The hydraulic principles are the same. The TCEQ design rules are the same. Reusable frameworks for standard infrastructure remove the work that does not need new engineering judgment.
The judgment still happens. A licensed PE still reviews every deliverable and seals the engineering documents. The routine work is simply already done.
Outcome-based pricing with skin in the game
When a firm is paid for delivering a defined scope rather than billing hours against it, the incentives change. The firm billing hourly has no structural reason to shorten the schedule. The firm paid for the outcome does. That is why we price around outcomes instead of hours.
What does this mean for TCEQ permitting timelines?
The agency's part of the clock is fixed. The part before submittal is not. TCEQ's review steps and the public notice requirements in 30 TAC Chapter 39 (opens in a new tab) set their own pace, and no engineering firm can shorten them.
What a firm controls is how long a project spends before it enters that process. Two developers with the same site and the same permit face the same agency review. The one whose complete, accurate application goes in sooner enters the queue sooner, gets a permit sooner and mobilizes sooner.
That is not a minor variable. It is often the difference between a project that holds its original pro forma and one that misses a construction season. Starting water and wastewater due diligence before closing on land moves that clock earlier still.
Has a permit delay ever cost your project a construction season? What would earlier engineering involvement have changed?
A note on limits: this is my view of how engineering delivery affects schedules, not a promise about any permit. TCEQ and other agencies set their own review times, and every project's path depends on its site, its permit and its review.
Frequently asked questions
What is outcome-based engineering pricing?
It ties a firm's pay to specific deliverables rather than hours. The firm agrees to deliver a defined scope, such as a permit-ready design, regardless of the time it spends. With hourly billing, revenue grows with hours. With outcome-based pricing, finishing sooner is rewarded.
When should a Texas developer bring in an engineering firm?
During due diligence, before the site purchase is final. Early involvement lets infrastructure constraints, such as service availability, system pressure and TCEQ permitting complexity, inform the purchase decision. It also starts the engineering clock earlier.
Can an engineering firm based outside a project's city handle Texas TCEQ permitting?
Yes. TCEQ's rules and submittal requirements are the same wherever the engineer sits. What drives permit efficiency is familiarity with TCEQ's review process and how its reviewers expect to communicate, plus a Texas PE license for the engineer who seals the work.
I'm a developer in Texas and my engineer keeps saying the design is waiting on information. How do I tell whether my schedule problem is the agency or the firm?
Ask for a dated list of what is outstanding and who owns each item. If the items are utility letters, survey or geotechnical data, they can usually run in parallel with design. If the application has not been submitted yet, the agency is not the delay.
Related resources
- How I Built a Civil Engineering Firm That Doesn't Follow Industry Norms
- How to Work With TCEQ Reviewers: What Slows Approvals and What Speeds Them Up
- What Engineers Submit to TCEQ and Why Your Application Gets Rejected
- What a Utility Feasibility Study Actually Tells You, and When to Get One
Is engineering, not the agency, the slowest part of your project schedule?
We build the schedule into the engineering from the first day, so a complete application reaches the agency as early as the project allows.
We specialize in:
- Water and wastewater system design for Texas subdivisions and master-planned developments
- TCEQ permitting and pre-application coordination
- Hydraulic modeling and infrastructure feasibility during due diligence
- Lift station, force main and pump station design
- Wastewater treatment plant design
- Construction administration
Modern Engineering Solutions, McKinney, Texas. Contact: (214) 833-6748 or mod-eng.com. Talk to an engineer about your project.
Talk to an engineer
Tell us about your project
An engineer reads it
Not a salesperson. Someone who can tell you whether the pathway is real.
You get a first answer
Your options, the agencies involved and the questions that decide cost and schedule.
You decide
No commitment to have the first call.
Prefer the phone? (214) 833-6748