In Part 1 and Part 2 of this series, we looked at what digital delivery means and how it developed in other parts of the world. This final part focuses on what matters most to the people actually delivering projects: the consultants, subconsultants, and specialist firms that make up the project ecosystem.
As U.S. DOTs and prime consultants continue to explore digital delivery, expectations will evolve gradually. The shift is unlikely to be sudden or uniform, but there are clear patterns emerging from other regions that offer a useful preview of what project teams can expect.
Day-to-Day Changes
For most project teams, digital delivery does not fundamentally change what work is performed, but it does influence how that work is coordinated, reviewed, and handed over.
Common changes tend to include:
- More structured requirements around how project information is named, organized, and submitted
- Greater emphasis on coordination earlier in the design process
- Fewer standalone document exchanges and more reliance on shared project information
- Design reviews that happen more continuously rather than only at fixed milestones
Over time, teams typically spend less effort reconciling conflicting files and more time resolving coordination issues earlier.
Deliverable Expectations
One of the more noticeable shifts is how deliverables evolve. Drawings and reports remain important, but they are increasingly supported by data-rich digital information.
In practice, this often means:
- Deliverables are expected to align with agreed information requirements
- Models carry more responsibility for coordination and review
- Information is structured so it can be reused by others downstream
For most teams, this is less about producing more content and more about producing information in a clearer, more consistent way.
The Role of Technology
Digital delivery does not typically require project teams to adopt unfamiliar tools. In many cases, the platforms teams already use form the foundation of digital delivery. What changes is how consistently and deliberately those tools are used across the project.
For civil and transportation projects, this often includes:
- Civil design tools such as OpenRoads Designer, OpenBridge, OpenSite, OpenRail, and MicroStation for producing and coordinating design information
- Engineering information management platforms such as ProjectWise, used as the central environment for managing files, versions, reviews, and approvals
- Design review and coordination workflows supported through Bentley’s digital twin and Infrastructure Cloud capabilities, enabling teams to review models, track issues, and understand design context more clearly
In most cases, the technology itself remains familiar. Digital delivery places greater emphasis on using these tools consistently and to their full capabilities, rather than introducing new systems.
What should project teams be thinking about?
As digital delivery becomes more common, project teams may need to pay closer attention to a few areas:
Information responsibility
There is typically greater clarity around who is responsible for producing, reviewing, and approving specific pieces of information.
Earlier coordination
More coordination effort often happens earlier in the project lifecycle, which can reduce late-stage changes during construction.
Consistency across projects
Standardized approaches to information management tend to replace bespoke, project-specific methods.
These changes are usually introduced gradually and refined over time as expectations become clearer.
What does this mean for subcontractors?
For subcontractors and specialist providers, digital delivery is most often encountered through prime consultant or DOT requirements.
Early impacts may include:
- Requests to submit work in specific digital formats
- Increased coordination with other disciplines earlier in the design process
- Clearer definitions of what information is required and when
While this can feel like a shift at first, many firms in other regions found that clearer expectations reduced rework and uncertainty. Over time, teams spent less effort responding to revisions and more time delivering coordinated work.
Smaller firms were rarely expected to change everything at once. Adoption typically occurred project by project, allowing capabilities to build gradually.
Long-Term Benefits
Across markets that have already moved in this direction, project teams consistently report:
- Fewer coordination-related issues later in delivery
- More predictable review and approval cycles
- Reduced rework caused by conflicting or outdated information
- Stronger collaboration across the full project team
Perhaps most importantly, teams gain confidence that the information they produce is understood, trusted, and usable beyond their immediate scope.
A Gradual Shift, not a Sudden Leap
Digital delivery in the U.S. will continue to evolve through pilot projects, updated guidance, and changing expectations. It is unlikely to arrive as a single mandate or requirement.
For project teams, the most valuable position is awareness. Understanding how work patterns may change makes it easier to adapt as requirements emerge, without disrupting day-to-day delivery.
Digital delivery is best viewed as an evolution in how transportation projects are coordinated and delivered, informed by lessons already learned across the global infrastructure industry.
