What Civil Engineers Should Know About Sharing DWG Files with Other Firms

You finish a drawing, it looks perfect on your screen, and you email the DWG to the architect or the surveyor you are teaming with. An hour later, the phone rings. “Your xrefs are missing.” But it was all there when you sent it.

A DWG is rarely alone

Start with the thing most people forget. The drawing you see on your screen is usually not one file. It is a main drawing plus a whole supporting cast that loads in behind it.

Those supporting files are called external references, or xrefs. Your drawing might reference the survey base, the architect’s floor plan, an aerial image, and a title block, each one a separate file living somewhere on your network. On top of that, your drawing relies on fonts, plot styles (the rulebook that controls how it prints), and other support files.

So when you “send the drawing,” you are often sending one piece of a set that needs several other pieces to look right. Send just the one piece, and the rest is missing on the other end.

Why it breaks on their end

Here is the actual mechanism, because understanding it makes the fix obvious. Each xref is remembered by its file path, the address that tells AutoCAD where to find it.

The problem is that those paths usually point to your folders. Something like a drive and folder that only exists on your computer or your network. When the other firm opens your drawing on their computer, AutoCAD goes looking for the survey at that exact address, does not find it there, and reports “xref not found.” The reference is not gone. AutoCAD just cannot find it at an address that does not exist on their machine.

For example: your survey base lives at a path on your office server. You send only the main sheet. The other firm opens it, and AutoCAD tries to load the survey from your server path, which their computer cannot reach. So the survey vanishes from the drawing. Nothing is corrupt. The map just points to your house.

Nothing is corrupt. The map just points to your house.

The fix: send it with eTransmit

Here is the tool built to solve exactly this, and every civil engineer should use it for handoffs. AutoCAD and Civil 3D have a command called eTransmit. It packages your drawing and everything it depends on — all the xrefs, images, fonts, and plot styles — into one neat bundle (usually a zip file), and it sorts out the paths so the references work on the other end.

Instead of emailing one DWG and hoping, you run eTransmit, and it gathers the complete set for you. The other firm unzips it, opens the drawing, and everything is there, because everything came along and the links point to files that are actually in the package.

This is the single biggest fix in this whole post. If you take one thing away, it is: do not just attach a DWG, send a transmittal made with eTransmit. It is the difference between “it is all broken” and “it just works.”

Relative paths vs. absolute paths

There is one more setting worth understanding, because it prevents the problem at the source. It is how your xref paths are stored.

An absolute path is the full address to the file. It only works on the machine where that exact route exists. So it breaks when the drawing moves. A relative path describes where the xref sits in relation to the main drawing, like “in the xrefs folder next to me.” That kind of path survives the move. As long as you keep the files in the same arrangement, the relationship holds wherever the folder lands.

The habit to build: set your xrefs to relative paths, and keep your project files organized in a consistent folder structure. Then your references travel well, and eTransmit has an easy job. Absolute paths are the quiet reason so many drawings break when they leave the office.

Civil 3D’s extra wrinkle: data shortcuts

Civil engineers have one more thing to watch, because Civil 3D adds a layer that plain AutoCAD does not. Your surfaces, alignments, and pipe networks are often shared between drawings using data shortcuts. A data shortcut is a reference to a design object that lives in another source drawing.

So a sheet might show a surface that does not actually live in that sheet. It lives in a source drawing and is referenced in. If you send the sheet without the source, the surface reference breaks the same way an xref does. eTransmit helps gather these, but data shortcuts need extra care, because the link is to a design object, not just a file.

The practical move depends on the job. If the other firm needs to work with your live surfaces and alignments, you may need to send the whole project structure, or coordinate your data shortcut setup with them. If they just need to see and reference the result, exporting to a plain DWG that “bakes in” the geometry can be cleaner. Either way, a Civil 3D handoff is worth a second of thought, because the data shortcut links are the part that most often surprises people. This connects to keeping Civil 3D projects healthy in general, which we cover in our post on why Civil 3D projects run slow.

A clean handoff checklist

Pull it together into a routine that makes you the firm everyone likes to share files with.

First, ask the same question we always start with: does the other firm need to view the drawing or edit it? If they just need to see and mark it up, a PDF is the simplest, safest answer, as we cover in our post on sharing large CAD files with clients. If they need the editable files, keep going.

Then, use eTransmit to package the full set, not just the main DWG. Keep your xrefs on relative paths and your folders organized so the references travel cleanly. For Civil 3D, decide how to handle your data shortcut sources, and include what they need. And tell them what is inside: a quick note listing the files, the coordinate system, and anything they should know. That little note saves a long phone call.

Do that, and your drawings show up complete and correct on the other end, every time.

Frequently asked questions

Why do my xrefs disappear when another firm opens my drawing?

Because the xref paths point to folders on your computer that do not exist on theirs. AutoCAD looks for the referenced files at your addresses, cannot find them, and reports them as missing. The references are not gone; they are just pointed at a location the other firm cannot reach.

What is eTransmit and why should I use it?

eTransmit is an AutoCAD and Civil 3D command that packages your drawing plus all of its xrefs, images, fonts, and plot styles into one bundle, with the paths sorted out. It is the right way to send a complete drawing, so everything opens correctly on the other firm’s computer.

What is the difference between a relative and absolute xref path?

An absolute path is the full address to a file and only works on the machine where that route exists, so it breaks when the drawing moves. A relative path describes where the xref sits in relation to the main drawing, so it survives being moved as long as the files keep their arrangement. Use relative paths.

How is sharing a Civil 3D file different from a plain AutoCAD file?

Civil 3D often shares surfaces and alignments through data shortcuts, which reference design objects in other source drawings. Send a sheet without its source and those references break. A Civil 3D handoff needs extra care to include the right source data, or to export geometry to a plain DWG.

We will make your file handoffs painless

Sending and receiving drawings between firms should be smooth, not a source of broken xrefs and embarrassing phone calls. We help small engineering firms around Knoxville set up clean project folder structures, relative-path habits, and handoff routines so your drawings always arrive complete, and the ones you receive open the way they should.

If sharing DWGs with other firms is a recurring headache, give us a call. We will set up your files and workflow so handoffs just work, so your team can focus on the engineering, not on chasing missing references.

Sources: How to transfer DWG with XREFs from different locations in AutoCAD (Autodesk); AutoCAD: Working with Xrefs, Use eTransmit (Arkance); Xref Path Strategy: Relative, Absolute, or No Path (Novedge)