How to Coordinate with a Structural Engineer in Revit Without Wrecking Your Model

A single unsynced shared coordinate can shift an entire structural link metres off-position with no visible warning in your view. You'll be sat there, plan looking perfect, elevations lining up, everyone nodding in the coordination meeting — and three weeks later someone discovers the transfer slab is sitting 1.2 metres away from where the columns actually land in reality. The Revit structural coordination workflow that prevents this isn't complicated. It's just rarely agreed properly before people start modelling.

This article gives you that workflow: one shared coordinate system, managed links instead of copy/monitor chaos, and clash detection that happens on a schedule rather than in a panic the week before issue.

Why Structural Coordination Breaks Most Revit Models

The most common cause of Revit model corruption in multi-disciplinary projects is unsynced shared coordinates between linked models — architects and engineers each working from their own version of "true north" without realising it. Once that drift starts, every linked view, every clash report, every dimension check becomes fiction.

By the end of this workflow, your architectural and structural models will share one coordinate system, update through properly managed links rather than an ever-expanding pile of copy/monitored elements, and clash-check without anyone manually eyeballing sections against each other. That's the outcome. Getting there needs three things in place before anyone opens Revit: both teams on compatible Revit versions (or an agreed IFC exchange if not), a shared coordinate strategy locked in at kickoff, and one named person — architect, BIM manager, whoever — responsible for coordination as an actual job, not an afterthought.

Here's the real cost of skipping this: a structural link can drift geometrically without a single error message. Revit won't flag it. Your view will look correct because you're used to seeing it that way. The drift only surfaces when someone dimensions off it, or worse, when it's on site and a steel fabricator is asking why the grid doesn't match the drawing.

This is worth saying plainly: coordination failures are almost never a Revit problem. They're an agreement problem that Revit then faithfully reproduces. Fix the agreement, and the software behaves. Skip the agreement, and no amount of BIM execution plan boilerplate will save you.

Agree the Rules Before You Open Revit

The architect should own the project's shared coordinate system and issue a coordination model to the structural engineer at project start — never the other way round on a building project. This single decision, made early and made explicit, prevents the vast majority of link drift problems that surface later.

Shared coordinates: who owns the origin

Revit gives you two commands that matter here: Acquire Coordinates and Publish Coordinates. The architect models the site, sets up a sensible project base point and survey point relative to real-world coordinates (Ordnance Survey grid references if you've got them), and publishes that as the shared coordinate system. The structural engineer then links the architectural model and uses Acquire Coordinates to pull that system into their own file. Do this once, early, correctly — and 90% of the drift issues that plague projects later simply don't happen.

The gotcha, and it's the single most common cause of coordination failure I see: never let the structural engineer acquire coordinates from their own internal survey point after the architect has already issued shared coordinates. It happens constantly, usually because the engineer's template has its own default origin and nobody thought to override it. The moment that happens, you've got two coordinate systems politely pretending to agree with each other, and they won't — not for long.

File naming and link management conventions

Agree a naming convention before the first model gets shared. Something specific and boring works best: discipline_projectnumber_building_revision — so STR_2601_MAIN_R03 for revision 3 of the structural model on project 2601. Boring is good here. You want anyone on the team to know exactly what they're linking without opening the file.

Worksharing vs. simple linking for smaller projects

Don't over-engineer this. For projects under roughly 500m² or jobs with a single consultant engineer, full worksharing with a central model and Revit Cloud Worksharing is often more process than the project needs. Simple linked files, reloaded manually on a sensible schedule, do the job perfectly well. Save the heavier infrastructure for projects where multiple people are genuinely working in the same model simultaneously.

If your team's still shaky on the fundamentals of linking and worksharing, ArchAdemia's Revit BIM Collaboration course covers this properly — worth doing before you're troubleshooting it live on a project with a client watching.

The Link, Copy/Monitor, and Clash Workflow That Actually Works

The correct Revit structural coordination workflow links the structural model using Origin to Origin positioning, copy/monitors only grids and levels, and runs clash detection at agreed milestones rather than continuously. That's the whole thing. Everything else is detail in service of that principle.

Step 1: Link the structural model correctly

Once shared coordinates are established, link the structural model using Origin to Origin positioning — not "Auto - Center to Center" and definitely not "Auto - By Shared Coordinates" unless you've already confirmed both files agree on what those coordinates are. Origin to Origin is predictable. It does exactly what it says, which is more than you can claim for some of the automatic options when two files have slightly different histories.

Step 2: Copy/Monitor grids and levels — not everything

This is where most juniors get it wrong, and it's an easy mistake to make because Revit doesn't stop you doing it. Copy/monitor grids and levels only. That's it. Don't copy/monitor columns, don't copy/monitor walls, don't copy/monitor floors because it "feels more thorough." Every additional monitored category creates a relationship Revit now has to track, report on, and eventually confuse you about when something changes upstream. Set up a shared parameter to track monitoring status if you want visibility on what's being watched — but keep the scope tight.

Step 3: Run clash detection at defined milestones, not constantly

Clash-checking every day generates noise, not insight, because live models are supposed to be inconsistent mid-design. Run interference checks at defined milestones — typically RIBA Stage 3, Stage 4, and pre-tender — when there's actually something stable enough to check. Revit's native Interference Check can handle combined model sizes up to roughly 300MB before performance starts to degrade noticeably; past that point, you're better off exporting to Navisworks.

Step 4: Reload links on a schedule, not ad hoc

Set a cadence and stick to it: weekly reloads during design development, a reload before every issue date without exception, and an immediate reload after any structural scheme change big enough to matter. Ad hoc reloading — "I'll grab it when I remember" — is how people end up coordinating against a structural model that's three revisions out of date without realising it.

Best Tools for Structural Clash Detection at Every Project Scale

Revit's built-in Interference Check is the best clash detection tool for two-consultant projects under 300MB combined file size, because it needs no additional software licence and runs directly inside the model you're already working in. Beyond that scale, or beyond two consultants, you need something purpose-built.

Navisworks Manage is the best tool for coordination on projects with 3+ consultants, handling federated models well over 1GB and letting you group clashes by discipline pair — architecture versus structure, structure versus MEP, and so on — instead of drowning in a single undifferentiated list. Autodesk Construction Cloud Model Coordination is the best option for phased or multi-office projects that need cloud-based clash tracking without every team member holding a local Navisworks licence.

Worth stating plainly: a lot of mid-size UK practices skip Navisworks entirely and run coordination through ACC purely because of licence cost. That's a sensible call for practices without a dedicated BIM manager, though it comes with a lighter feature set than full Navisworks Manage.

Role-based note: if you're a BIM Manager coordinating a hospital or education project with M&E, structure, facade, and landscape all in play, Navisworks or ACC isn't optional — it's the only sane way to manage that many discipline pairs. If you're a sole practitioner working with one structural engineer on a house extension, Revit's Interference Check will do everything you need for free.

If clash detection at scale is new territory for you, ArchAdemia's Navisworks course walks through federated model setup and clash grouping from scratch.

The Mistakes That Wreck a Coordinated Model

The fastest way to break Revit coordination silently is deleting and recreating a structural grid instead of moving the existing monitored one — this severs the copy/monitor relationship without throwing any warning at all. The grid still looks right on screen. Revit has simply stopped tracking it.

Overriding monitored elements without flagging

Coordination Review is Revit's mechanism for flagging when a monitored element has moved in the linked file. It's genuinely useful — and routinely ignored, because it shows up as a slightly annoying dialog box that people click through during a busy week rather than actually resolving. The habit of "accept and move on" is how small discrepancies accumulate into large ones.

Deleting and recreating grids instead of moving them

This is the one that catches people out hardest. An engineer revises a scheme, deletes grid line 4, redraws it two metres over. Visually, identical result. Structurally, Revit no longer has any idea that "new grid 4" has any relationship to what your architectural model was monitoring. Nothing breaks immediately. It breaks three weeks later when levels shift and nobody can work out why the coordination review isn't catching it.

Ignoring 'Coordination Review' warnings

Treat every Coordination Review notification as something to resolve within the day, not something to batch up and deal with at the end of the week. It's a small discipline that saves enormous pain later.

Ballooning file size from unmanaged copy/monitor

Unmanaged copy/monitoring of full structural elements — not just grids and levels, but columns, beams, floors — can add 50-150MB to an architectural model with genuinely zero design value. It's dead weight that slows down every save, sync, and open for the rest of the project.

Run a monthly model health check. It sounds like overkill until the month you skip it is the month something quietly goes wrong. Check file size trends, audit what's actually being copy/monitored, and clear out anything that's accumulated without purpose.

When to Walk Away From Revit-to-Revit and Use IFC Instead

IFC exchange is the better choice over native Revit links when the structural engineer works in a different BIM authoring tool — Tekla, an ETABS-linked model, or anything outside the Autodesk ecosystem — because native Revit linking only works reliably between Revit files. The moment the engineer isn't in Revit, you're in IFC territory whether you like it or not.

The trade-off is real and worth naming honestly: IFC loses parametric intelligence and copy/monitor functionality entirely. You're exchanging a static coordination snapshot, not a live, tracked relationship. Treat it as a coordination checkpoint format — a clash-check-and-verify moment — rather than something you rely on the way you'd rely on a native link.

The practical tip that saves genuine grief: agree IFC export settings — coordination view versus structural analytical view — with the engineer before the first exchange, not after a failed clash report leaves you wondering why half the model didn't come through. Structural analytical models often export as centreline representations rather than solid geometry, which looks like an error but is actually just a settings mismatch.

Coordination Is a Discipline, Not a Feature

None of this requires exotic software or an enormous BIM execution plan nobody reads past page two. It requires one shared coordinate system set up correctly on day one, restraint in what you copy/monitor, a clash-checking cadence you actually stick to, and someone whose job it is to notice when Coordination Review starts flagging problems instead of clicking past them.

Get those four things right and Revit does exactly what it's supposed to do — quietly, reliably, without drama. Get them wrong and you'll find out the expensive way, usually on site, usually with a fabricator on the phone. If you want to walk through this workflow properly, step by step, inside a live project file, ArchAdemia's coordination course covers exactly this — shared coordinates, copy/monitor discipline, and clash detection done the way it should have been taught the first time.

FAQ