Sending a CAD drawing successfully means delivering the files it depends on, not only the main drawing. Start with an agreed deliverable, gather its references, and test the package before using FileFlap to send it to the client.
Agree on the format and intended use
Ask which application and version the recipient uses. Establish whether they need an editable model, a drawing for review, or a PDF for approval. An interchange export can be useful, but it may not preserve every application-specific feature. Keep the native project and check the exported result separately.
Include units, coordinate assumptions, revision, and any relevant view or sheet names in a short delivery note. For a review-only handoff, a PDF alongside the editable files gives the recipient a reference for the intended appearance.
Collect the drawing dependencies
External references, linked images, plot styles, and other supporting resources can affect how a drawing opens or prints. In AutoCAD, eTransmit packages drawings and supporting files. Inspect the resulting file list and resolve missing references before delivery; a package tool cannot recover a source file that is unavailable.
Only include resources you are allowed to distribute. If a font or other asset cannot be shared, document the dependency and agree on a suitable replacement or a review format. Avoid including unrelated client projects from a shared working folder.
Test the package outside its working folder
- Create a clean delivery folder with a specific revision name.
- Collect the drawing, permitted dependencies, and README.
- Extract or copy the package into a separate location.
- Open that copy and inspect references, layouts, and representative views.
- Check that it does not silently depend on your original local paths.
A test on another workstation is useful when available. If the recipient uses different software, ask them to confirm that the agreed export opens before treating the delivery as complete.
Provide a useful handoff message
Share the download link with the project identifier, revision, total size, and the filename to open first. State whether the package replaces an earlier delivery. Request confirmation of both receipt and successful opening; downloading an archive does not prove that its drawing dependencies are intact.
Should I send each reference separately?
A single organized package usually reduces missing-file mistakes. If a replacement reference must be sent separately, identify exactly where it belongs and which previous file it replaces.
Choosing a service for your next delivery? Our WeTransfer alternatives guide starts with FileFlap and explains the delivery features to compare.
← All articles