TL;DR
TL;DR: One ±5mm capture (80,000–120,000 sq ft/day, occupied is fine) answers dimensional questions for years. Buy hosted access first, floor plans second, models per-project; roll portfolios out phased on one coordinate standard; keep it current by rescanning changed areas and writing scan handover into closeout specs.
Facility managers inherit the documentation problem everyone upstream created: drawings that stopped being true decades ago, knowledge that lives in one veteran's head, and a stream of questions — will it fit, where does it run, how big is that room — each answered with a site walk. Laser-scan documentation fixes this categorically: one capture produces a ±5mm measurable record that answers dimensional questions for years, from a browser. This guide covers what to buy, how to roll it out, and how to keep it alive.
What should a facility scan capture?
Everything a future question might touch — which is more than the pretty floors:
- All occupied and support spaces — including mechanical rooms, risers, and roofs, where the expensive questions live.
- [Above-ceiling conditions](/services/mep-scanning) in areas facing future work — the plenum is where renovation budgets go to die, and tile-lift capture documents it while ceilings are already accessible.
- 360° panoramas — captured automatically alongside geometry every 2–3 meters; for daily FM use, the visual layer gets opened more than the cloud itself.
- The exterior envelope where maintenance and capital planning need it.
Capture is fast — 80,000–120,000 sq ft per field day, fully occupied is fine — so scope by future usefulness, not by this year's project boundary.
Which deliverables does a facility team actually use?
In observed practice, in this order:
- [Browser-hosted access](/services/point-cloud-hosting) — the workhorse. Staff, consultants, and contractors answer their own questions from a link; no CAD seats, no site walks. This single deliverable carries most of the daily value.
- [2D floor plans](/services/floor-plans) — space management, BOMA calculations, life-safety documentation, and the base drawings every small project starts from.
- The archived point cloud (E57/RCP, open formats you own) — the master record every future deliverable is extracted from. Capture once, extract forever.
- [Revit models](/services/scan-to-bim) — where renovation pipelines or FM-system integrations consume them; many teams commission models per-building as projects arise rather than portfolio-wide up front.
- A [digital twin](/services/digital-twin) assembly when the organization is ready to give every stakeholder one navigable reference.
How should a multi-building portfolio roll this out?
Phased, on one coordinate standard. The published template is our 12-building university program: 480,000 sq ft across nine field days, every building registered consistently, clouds and panoramas for everything, models added per building as planning required. The results FM leadership cares about: renovation planning time down 40%, an estimated $85,000 in repeat verification trips eliminated, and 19 non-compliant ADA ramps surfaced by the unified dataset.
Prioritize buildings by question volume: scan first where projects, moves, and compliance activity concentrate. Each capture lands on the shared standard, so the portfolio dataset assembles building by building without rework — and budget cycles can spread the program across years.
How do you keep scan documentation current?
A scan is a snapshot; buildings drift. Three habits keep the record honest:
- Rescan after every significant modification — renovations, tenant fit-outs, MEP changes. Changed areas re-register onto the existing coordinate system; you don't recapture the building.
- Put re-scan handover in project closeout specs — make the contractor's as-built scan a deliverable, and the record updates itself project by project.
- Annual or biennial review for active facilities — compare, rescan drifted zones, archive prior states. Prior snapshots remain valuable: they're the building's history, and occasionally its evidence.
What does this cost, and how is it justified?
Capture runs $0.05–$0.20 per square foot; hosting adds a modest ongoing line; extracted deliverables price by scope. Justification is the site-walk math: every dimensional question answered from a desk instead of a visit returns staff hours, and every project that starts from measured truth instead of folklore returns multiples — the renovation ROI numbers apply to every project the record serves. For education, healthcare, and multi-site operators, the record also outlives the staff turnover that used to take building knowledge with it.
Start with one building — ideally the one generating the most questions — and get the number. The first month of answered-from-a-desk questions usually settles the argument.