Export Site Analysis to AutoCAD and Revit with Less Rework
A practical handover method for reusing site-analysis context in AutoCAD and Revit, with checks for file formats, coordinates, units and geometry.
Quick answer
To reuse site-analysis data in AutoCAD or Revit, agree a supported exchange format, verify the files returned, then check units, coordinates, geometry and source coverage in the receiving application. A usable context drawing can reduce rework, but it does not automatically become a measured survey or a coordinated project model.
This handover sequence is for the architect receiving a site-context package. It focuses on avoiding unnecessary redraw while preserving a trustworthy project reference. Keep the broader export-format checklist available, but assess the delivered drawing in the actual AutoCAD or Revit project before deciding what can be reused.
1. Request the minimum useful package
Tell the sender which design question the file must support and which geometry is required. Request the source boundary, available context, file manifest, units and coordinate note. Ask which elements are measured and which are approximate. Unnecessary detail can obscure the objects that need checking; missing critical geometry should be identified before coordination starts.
2. Quarantine and inspect the received drawing
Keep the original package unchanged and work on a copy. Open the drawing, inspect layer visibility and extents, and look for remote stray objects. Measure a known distance and check elevations where they matter. Record absent layers, duplicate objects and boundary closure rather than silently repairing everything and losing the audit trail.
3. Establish the project relationship
Agree the relationship between the incoming file and the trusted project reference. The reviewed Atlasly context DXF exporter defaults to local metres; this is not proof of British National Grid or existing Revit shared coordinates. Check control points and orientation. If a reference-system conversion is needed, use the appropriate transformation and document it.
4. Choose the receiving-application workflow
In AutoCAD, decide how the context will be referenced and controlled within the project. In Revit, choose import or link, units and placement deliberately; Autodesk documents these as separate decisions. Test with a copy before distributing a coordinated reference. Importing a DXF does not establish native DWG delivery or a complete Revit model.
5. Reuse geometry selectively
Separate acceptable context from information that needs replacement by the measured survey. Keep approximate neighbouring massing clearly identified. Do not use a desktop contour interval as a statement of survey accuracy, and do not infer legal boundaries from drawn features. Rework critical objects when necessary rather than preserving an incorrect drawing for the sake of a no-redraw promise.
6. Issue a handover note and measure rework
Record the received version, placement checks, approved reference, corrections and unresolved issues. Tell the next team member which file should be updated when new evidence arrives. If evaluating time saved, include inspection, conversion and cleanup as well as download time. A file that opens successfully has passed only the first check.
Illustrative example
Illustrative scenario: A team reopens an exported context file in its intended design application and checks units, two known distances, location and layer contents. Missing or altered elements are recorded before the file is used as a design reference.
Frequently asked
Can I avoid all redraw?
That depends on the delivered geometry and intended use. Reuse checked context and replace unsuitable information.
What should I check first?
Units, a known distance, drawing extents and the relationship to a trusted project reference.
Should approximate context overwrite the survey?
No. Keep source status clear and coordinate critical geometry against suitable measured information.
How should a revised export be handled?
Retain the previous version, repeat the relevant checks and communicate changes before updating the shared project reference.
Conclusion
Reuse is worthwhile when the next designer can trust the checked reference and understand its limitations. Keep the broader export checklist with the handover record.
About the author
Shatakshi Patil
Architect writing about pre-construction due diligence, planning context, and site intelligence workflows for design teams using Atlasly.
Sources and references
Authoritative references for the planning policies, regulations, and standards referenced in this article. Always check the publisher for the latest version.
Related articles
Auto-suggested
export site analysis data to AutoCAD and Revit
How to Export Site Analysis Data to AutoCAD and Revit
A guide to choosing and verifying site-analysis exchange files, including units, coordinate references, geometry, source coverage and receiving-application checks.
Read
3D site context for architects
3D Site Context for Architects: Data, Exports and Review Checklist
Build useful 3D site context from terrain and surrounding buildings. Check height assumptions, units, coordinates and export quality before design handover.
Read
site intelligence report
Shareable Site Intelligence Reports: Evidence, Gaps and Handover
How to prepare a traceable site report with source dates, coverage limits, unresolved issues, access checks and reviewed outputs for the next project decision.
Read
Workflow
How to Export Site Context to DXF for AutoCAD Using Atlasly
Export available Atlasly site context to DXF and check layers, units, coordinates and geometry before using it in AutoCAD or another supported CAD workflow.
Read