How the AEC Collection Integrates Revit, Civil 3D, and AutoCAD into One Workflow

One of the most persistent frustrations in building and infrastructure design is the handoff problem: the architect works in Revit, the civil engineer works in Civil 3D, the structural engineer works in a mix of tools, and everyone exchanges drawings and models in a patchwork of exports, imports, and manual coordination. Data gets lost, models become out of sync, and the same information gets entered and re-entered in different systems. The Autodesk AEC Collection addresses this directly by providing a suite of tools specifically designed to exchange data with each other cleanly, enabling workflows that span disciplines without losing fidelity at each boundary.

This article explains how Revit, Civil 3D, and AutoCAD interact in a typical AEC project, where the integration points are, and what practical benefits this connected workflow delivers for real project teams.

The Three Pillars of the AEC Collection Workflow

AutoCAD: The Universal Exchange Format and Legacy Platform

AutoCAD’s DWG file format is the closest thing the construction industry has to a universal language. Virtually every other design and engineering application can read and write DWG files, which means AutoCAD sits at the centre of the data exchange web even in workflows that have largely moved on to BIM tools. Within the AEC Collection workflow, AutoCAD serves several specific functions:

• Production of 2D detail drawings, schedules, and notes that are more efficiently created in 2D than extracted from a 3D BIM model
• Exchange format for sharing with contractors, specialists, and clients who may not have Revit or Civil 3D
• Working environment for disciplines that have not yet adopted BIM (some specialist contractors, some overseas teams)
• Platform for AutoCAD vertical products (AutoCAD Architecture, AutoCAD MEP, AutoCAD Map 3D) which add discipline-specific functionality to the base AutoCAD environment

In a modern AEC workflow, AutoCAD is often the last step in a publication chain — models from Revit and Civil 3D are published as DWG drawings for contractor use — rather than the primary design environment. But its role as the interchange format means it remains important even when nobody is designing in it directly.

Revit: The BIM Core

Revit is the central modelling environment for building design. Its fundamental difference from AutoCAD is that instead of drawing lines and symbols, you model actual building elements — walls, floors, roofs, columns, beams, doors, windows, MEP ductwork and pipework — as intelligent parametric objects that know what they are and how they relate to each other.

This intelligence drives the integration. A wall in Revit is not just a pair of lines — it has a thickness, material composition, fire rating, thermal properties, and a relationship to the floor it sits on and the roof above it. When you change the wall type, all the associated properties update automatically throughout the model and in all the drawings and schedules that reference it. A floor plan, a section, an elevation, a 3D view, and a quantity schedule are all different views of the same underlying model — change the model and all the views update.

Revit supports multiple disciplines within its environment:

• Revit Architecture — architectural design, space planning, room data sheets, material takeoffs
• Revit Structure — structural framing, foundation design, structural analysis model export
• Revit MEP — mechanical systems, HVAC design, electrical distribution, plumbing and drainage

All three disciplines can work in the same Revit file (a central model on BIM 360 or a network server) simultaneously using Revit’s worksharing feature, with each team member working in their own local copy and synchronising changes back to the central file periodically. This enables genuinely collaborative multi-discipline design within a single BIM environment.

Civil 3D: Site and Infrastructure

Revit’s strength is buildings; Civil 3D’s strength is everything below and around them. Civil 3D handles terrain modelling, road design, drainage design, utility networks, grading, and site development. On a typical building project, Civil 3D is used to:

• Process survey data (levels, boundaries, topographical features) into a usable terrain model
• Design the site levels and earthworks (cut and fill to achieve target ground levels)
• Design access roads, car parks, and footpaths
• Design surface water drainage — gutters, drains, detention basins, and outfalls
• Design foul drainage — sewer connections, adoption details, inspection chamber layouts
• Produce infrastructure drawings (road sections, drainage longitudinal sections) for adoption by local authorities and utilities

Civil 3D works primarily in the DWG environment, extended with a set of civil engineering objects — alignments, profiles, corridors, pipe networks, surfaces — that sit on top of the standard AutoCAD drawing environment. This means Civil 3D output can be shared as DWG with any AutoCAD user, with the civil objects visible as graphics even if the recipient does not have Civil 3D.

Key Integration Points Between the Three Tools

Civil 3D Survey and Levels into Revit

The starting point for most building design projects is survey data: OS mapping, levels survey, measured building survey, and property boundaries. Civil 3D processes this data into a digital terrain model (DTM) — a 3D surface representing the existing ground levels across the site.

This DTM can be exported from Civil 3D in formats that Revit can consume. The most common workflow is to export the survey data as a point cloud (using Autodesk ReCap, also part of the AEC Collection, to process LiDAR or photogrammetry data) or as a DWG with level information that the Revit team can use to set up their project levels and site topography.

Revit’s Toposurface tool can import terrain data directly, allowing the architectural team to see the ground levels and design their building’s relationship to the site with accurate level information. This eliminates a common source of errors — architects assuming approximate ground levels that differ significantly from reality.

Revit Building Footprints into Civil 3D

Once the building position and footprint are established in Revit, the civil engineer needs this information to design the site levels and drainage. The building outline, finished floor level, and any hard-standing areas can be exported from Revit as a DWG and referenced into Civil 3D as a background drawing.

Using Autodesk’s BIM 360 (now called Autodesk Docs) platform, this exchange can be more automated: Civil 3D can reference a federated model that includes the Revit building model, allowing the civil engineer to see the current building geometry in context while working on the site design. When the building footprint changes in Revit, the civil engineer sees the updated footprint in their Civil 3D model and can adjust the site works accordingly.

Navisworks Coordination

Navisworks Manage, included in the AEC Collection, aggregates models from multiple sources — Revit models from the architectural and MEP teams, Civil 3D drawings from the civil engineer, structural models from the structural engineer — into a single federated coordination model. Navisworks then runs clash detection: it identifies every location where objects from different models physically overlap.

In a complex building, there will typically be hundreds or thousands of clashes in the first coordination review — beams running through ductwork, columns in the wrong location, drainage pipes conflicting with structural elements. Navisworks provides a workflow for systematically reviewing, assigning, and resolving these clashes before construction begins, when changes are cheap. Resolving the same clashes on site, after steel has been fabricated and ductwork installed, costs orders of magnitude more.

AutoCAD as the Publication Layer

Most construction contract documentation is still issued as DWG or PDF drawings, even when the design was produced in Revit and Civil 3D. Both Revit and Civil 3D can produce high-quality DWG outputs — Revit through its sheet publishing tools and Civil 3D through standard AutoCAD plot functionality. These published drawings form the contract set that is issued to the main contractor for tendering and construction.

The advantage of producing drawings this way, rather than drawing them in AutoCAD directly, is that they are automatically coordinated with the underlying models. Floor areas in the room schedule match the room areas in the BIM model. Road cross-sections in Civil 3D are genuinely cut through the corridor model. There is no opportunity for the discrepancy that arises when drawings are created manually and then edited independently of the model.

Setting Up a Shared Project Environment

Making this integrated workflow function in practice requires some upfront setup, particularly around coordinate systems and shared levels.

Project Coordinates

The single most important technical requirement for multi-tool coordination is a shared coordinate origin. If Revit uses one coordinate system and Civil 3D uses another, the models will not overlay correctly in Navisworks and the exchange of geometry between tools will produce errors. The standard practice is to establish a shared site coordinate system (typically National Grid coordinates, or a local grid based on a site benchmark) and set all tools to use it from the project outset.

In Revit, this is configured through Project Base Point and Survey Point settings. In Civil 3D, the drawing units and coordinate system must be set to match. Getting this right at project start saves significant coordination effort later.

Accessing the AEC Collection

The Autodesk AEC Collection is available from GetRenewedTech for €174.99, covering Revit, AutoCAD, Civil 3D, Navisworks Manage, InfraWorks, and the supporting tools in the collection. For any AEC practice that regularly uses two or more of these applications, the collection represents a highly cost-effective way to ensure every team member has access to the full suite of tools they need.

Conclusion

The integration between Revit, Civil 3D, and AutoCAD in the AEC Collection is not theoretical — it is a practical workflow that project teams use on complex building and infrastructure projects every day. The shared coordinate system enables geometry exchange, Navisworks closes the coordination loop between disciplines, and AutoCAD provides the publication layer for contract documentation. Setting up this workflow properly at project start requires care, but the payoff — a coordinated, consistent project information model that spans all disciplines — is one of the fundamental efficiencies that modern BIM practice delivers.

Common Integration Challenges and How to Solve Them

While the integration between AEC Collection tools is powerful, it does not always work perfectly without careful setup. These are the most common integration problems and their solutions:

Coordinate Mismatch

If Revit and Civil 3D are using different coordinate systems or origins, models will not overlay correctly in Navisworks, and geometry exchanged between the two will be in the wrong location. The solution is to establish the shared coordinate system at the start of the project and verify it before any significant modelling work begins. Create a test exchange — a simple shape from Civil 3D appearing in the correct position in Revit, and vice versa — before starting the real work.

Large File Sizes Slowing Coordination

Very large Revit models and Civil 3D drawings can make Navisworks coordination review sessions slow and unwieldy. Mitigations include:

• Export lightweight NWC (Navisworks Cache) files from each model for coordination, rather than working directly with the native formats
• Use Revit’s model subdivision features to export only the relevant portions of a large model for specific coordination reviews
• Schedule coordination reviews with updated NWC exports prepared in advance, rather than live-linking to full models during the review meeting

Version Compatibility

Different team members or consultants working on different versions of the same application can cause file compatibility issues — a Revit 2025 file cannot be opened in Revit 2024 without being upgraded. In collaborative projects, agree on a single application version across the team at project outset, and upgrade all team members simultaneously rather than allowing version drift.

The Business Case for the AEC Collection

For any architecture, engineering, or construction practice that regularly uses two or more of the applications in the AEC Collection, the collection pricing represents a substantial practical benefit. The alternative — purchasing individual licences for Revit, AutoCAD, Civil 3D, and Navisworks separately — would cost considerably more at full retail prices.

Beyond the direct cost saving, the integration benefits described throughout this article have real productivity value. Less time spent on manual data transfer between tools, fewer coordination errors, automatic consistency between model and drawings — these are real time savings that accumulate significantly over a project lifetime.

The Autodesk AEC Collection is available from GetRenewedTech for €174.99. For any professional AEC team working on buildings or infrastructure, this represents exceptional value for access to the industry-standard tools that define modern UK design practice.