You’ve got a building to renovate and drawings you don’t trust. Here’s the repeatable workflow we use to turn a point cloud into a drafting-ready floor plan that your team can dimension, annotate, and build from—without guesswork.
What “accurate” really means for floor plans
For plan production, accuracy is less about the maximum spec on a brochure and more about controlled, predictable error across a whole building. On typical commercial interiors:
- Capture density: 5–10 mm point spacing at 10 m for walls/doors/structure, tighter where needed
- Registered accuracy: ±6–10 mm across a floor when tied to control and looped correctly
- Deliverable scale: 1/8" = 1'-0" plans with linework driven directly by point cloud slices at 4' AFF (and mechanical/equipment areas supplemented with additional slices at 1' and 7' AFF)
We routinely capture 80,000–120,000 sq ft per day with a NavVis VLX3, then augment with static scans (Leica RTC360 or Faro Focus) in large atria or long corridors to pin global accuracy. Final floor plan drafting for a 100,000 sq ft, two-story office typically wraps in 5–7 business days, inclusive of registration and QC. File deliveries for that footprint average 18–30 GB (E57 + RCP) and a 10–25 MB DWG per floor.
“If it doesn’t close, it doesn’t go in the drawing. Every loop is checked, and we verify doors and core dimensions in three independent slices before we commit a line.”
Step-by-step: from point cloud to drafting-ready DWG
The process is simple to describe, but each step has traps that can cost days. This is the field-tested sequence our team follows.
1) Set the scope and tolerances before anyone scans
- Define deliverables: 2D plan only, or include RCPs, reflected ceilings, and elevations? If you need BIM, see our Scan to BIM service and this LOD guide.
- Agree on tolerances: We quote ±6–10 mm registered accuracy for plans tied to site control, documented in the title block.
- Drafting standards: Layers, linetypes, symbols (AIA/office standard). Provide a sample sheet.
- Levels and grids: Existing benchmark elevations and any owner gridlines.
- Output formats: DWG + PDF set, plus E57 and/or RCP. If you’re new to formats, this primer helps: Point Cloud File Formats Explained.
If you need a template to capture all of this, grab our Scope of Work template.
2) Prep the site so the scan tells the truth
- Access: Keys/badges, elevator control, roof access if required.
- Control: Black-and-white targets or spheres; minimum three per floor tied to a common control network (total station or survey control). We like 20–40 m spacing in long corridors.
- Visibility: Prop open fire doors during capture; cover mirrors or log them; mark “do-not-scan” zones.
- Loop planning: Sketch the path and closures for each floor to avoid SLAM drift.
A short owner checklist is here: How to Prepare Your Site for a 3D Laser Scan.
3) Capture: mobile first, static where it counts
- Primary device: NavVis VLX3 (SLAM). We walk at a normal pace, pausing for high-detail areas (mechanical rooms, stairs).
- Hybrid fill: Leica RTC360 or Faro Focus shots at long, straight runs and double-height spaces to anchor global geometry.
- Field notes: Photos of edge conditions, inaccessible rooms, and ceiling plenum observations—these matter later in drafting.
Throughput benchmark: In a typical office in Columbus, one operator covers ~100,000 sq ft per day. In dense industrial interiors, plan on 40,000–60,000 sq ft/day.
4) Registration and QA: make the cloud trustworthy
- Registration: Cloud-to-cloud in NavVis IVION or Autodesk ReCap, snapped to control. We target residuals under 6 mm for loops and under 8 mm across floors.
- QC routines:
- Loop error checks and heat maps
- Spot checks: three tape-verified dimensions per floor (core-to-core, exterior wall grid spacing, a long corridor)
- Control report saved to the deliverable set
- Clean-up: Remove moving people, duplicate passes, and stray returns.
Turnaround: 0.5–2 days depending on building size and the number of floors. Final combined cloud size: 15–40 GB E57 for mid-size jobs; RCP indexing adds another 2–6 GB.
5) Section the cloud for plan geometry
- Slices: 4' AFF for architectural plans; 7' AFF for door headers and soffits; 1' AFF in equipment-heavy rooms. Thickness: 1–2".
- Alignment: Confirm levelness; if the building is out of level, keep the model true and note flatness variances in the sheet.
- Views: Create orthographic floor plan views per level in ReCap or Revit for drafting backgrounds.
6) Draft linework in AutoCAD (or Revit if you prefer)
- Background: Attach RCP/E57 in AutoCAD with units verified. Use UCS by floor to ensure clean northing.
- Walls: Trace centerline or face-of-stud per scope; polylines converted to walls if the client will continue in Revit.
- Doors/windows: Snap to jambs in the slice; verify swings and head heights using vertical sections.
- Stairs/ramps/shafts: Cross-check three sections; draw treads and risers from measured nosing-to-nosing vector in the cloud.
- Annotations: Dimensions, door numbers, and room tags if requested. We follow AIA layering unless your standard overrides.
If you’ll model later, align with our Scan to CAD and Scan to BIM conventions so geometry ports cleanly.
7) QC the drawings against the cloud and control
- Per-sheet checklist:
- Ten dimensions spot-checked and initialed
- Door schedule counts vs. field photo tally
- Core-to-core checks aligned with control distances
- Room area totals within 1–2% of cloud-derived polylines
- Clash sanity: Look for impossible wall thickness, skewed columns, or bending corridors—signs of registration or slicing missteps.
8) Deliver, document, and archive
- Deliverables: DWG + PDF plans, RCP, and the master E57. If needed, we include a small “viewer set” for non-CAD users.
- Documentation: Registration report, control layout, and a one-page summary of capture settings.
- Archive: We retain raw projects for 12 months unless otherwise specified.
For owners who want a complete package, see our As-Built Documentation and 2D/3D Floor Plans services.
Mobile vs. terrestrial vs. hybrid for floor plans
| Approach | Typical Use Case | Speed (per day) | Registered Accuracy | Notes |
|---|---|---|---|---|
| Mobile (VLX3) | Offices, schools, hospitals, housing | 80k–120k sq ft | ±8–12 mm (no control), ±6–10 mm (with control) | Fastest; rely on loop closures and control targets |
| Terrestrial only (RTC360/Focus) | Small footprints, tight tolerances | 10k–25k sq ft | ±3–6 mm | Slower; great in plant rooms or heritage details |
| Hybrid (VLX3 + TLS) | Large/complex buildings, long corridors | 60k–100k sq ft | ±5–8 mm | Our go-to for multi-story and atriums |
If you’re working on heritage or adaptive reuse, mobile scanning supports the process but does not replace measured drawings taken by hand where ornament profiles or deflection mapping is the priority. See our notes on Preservation and Adaptive Reuse.
A quick Ohio field note
We recently supported a downtown Columbus office-to-resi conversion—nine floors, 212,000 sq ft. One day of mobile capture with the VLX3 for each three floors, plus 42 static RTC360 stations across two sky bridges and the lobby. Registration closed at 5–7 mm over the stack. From there, our drafting team produced floor plans, RCPs, and core details. Total timeline: 9 field days, 3 days registration/QC, 8 days drafting. Point cloud delivery: 34 GB E57 + 4.8 GB RCP. The GC logged zero RFIs tied to “unknown dimensions” during demolition—an outcome we’ve also seen on our Downtown Mansfield case study.
Practical settings and habits that save hours
- Control spacing: 20–40 m in corridors; always include at least one control point per stair core per floor.
- Slice thickness: 1" for door checks, 2" for general drafting.
- ReCap indexing: High detail for architecture; medium for shell/exterior. Keep RCS segments per floor; avoid one giant file.
- Door verification: Confirm at head height with a vertical section; slab recesses can trick a 4' AFF slice.
- Naming: Level_01_Plan.dwg and Level_01_E57.e57. Keep file names dumb and consistent.
- QA log: Maintain a running list of oddities (skewed columns, curved walls) with screenshots; include as an appendix.
Common pitfalls (and how to dodge them)
- “We’ll figure out tolerances later.” You won’t. Document them up front, on the sheet, and in the proposal.
- No control on multi-floor jobs. Expect drift. Use targets and loop closures on every floor.
- Over-thinning the cloud. It drafts faster until you hit a detail and can’t see the jamb. Keep density where decisions happen.
- Drafting from orthophotos only. Orthos are helpful, but always check three slices in 3D before finalizing geometry.
- Skipping site prep. Propped doors and a planned path cut hours off registration.
When you should move beyond 2D plans
If you need collision checks, equipment placement, or coordinated MEP routing, shift to a Revit model. We provide LOD 200/300/400 per scope—details here: Scan to BIM (Revit LOD 200/300/400). For strictly architectural plans, 2D DWGs paired with the master RCP remain the most efficient path and keep your team in familiar tools.
What you’ll get from ZEALOT
- Capture with NavVis VLX3, augmented by Leica RTC360/Faro Focus where needed
- Registered point clouds in E57 and RCP, cleaned and aligned to your coordinate system
- Drafted floor plans (DWG + PDF), ready for dimensioning and detailing
- Clear documentation: registration report, control summary, QA checklist
- Typical turnaround: 6–10 business days for 100,000 sq ft, depending on complexity
If remote collaboration is key for your team, we also host secure web viewers so architects can “walk” the building and cut sections on demand—useful when you want to eliminate field visits.
Budgeting and schedule math you can trust
- Capture: 80k–120k sq ft/day (VLX3), 40k–60k sq ft/day hybrid in complex conditions
- Registration/QC: 0.5–2 days per building stack
- Drafting: 0.5–1.5 days per 25,000 sq ft for plan-only; add 30–50% for RCPs and elevations
- Savings: We routinely see $10k–$40k avoided in rework and RFIs on mid-sized renovations when plans are derived from the cloud, not old PDFs
To turn this workflow into a clean set of drawings, we focus on three things: defined scope, stated tolerances, and a schedule that includes registration and QC. Skip any one of those and you’ll spend your savings on do-overs.
Looking for a deeper dive on deliverable language? Start here: How to Write a 3D Scan Deliverable Spec That Protects Your Project.