What Is HBIM?
HBIM (Historic Building Information Modeling) is a BIM-based way to document a historic, heritage, or otherwise existing building from measured reality instead of design intent. In practice it ties measured geometry, usually a registered laser-scan point cloud, to a scoped 3D model plus the drawings, photos, and element information a preservation or design team will actually use. It is not a magic model that captures every cornice and crack. It is a documentation workflow, and its whole value depends on how the deliverable is scoped.
That last point is where most HBIM requests go wrong. “We need an HBIM model” can mean a clean architectural shell for design backgrounds, or it can mean every molding, baluster, and phase of repair modeled as a parametric Revit family. Those are wildly different efforts. Before anything gets modeled, the project has to decide what belongs in the model and what is better left as point cloud, CAD elevation, or photo record.
Why HBIM is different from new-building BIM
New-building BIM starts from a design and adds reality later. HBIM starts from reality and has to interpret it. Historic structures are rarely square: walls lean, floors slope, rooms are out of plumb, additions are undocumented, old repairs hide original construction, and the only drawings on file may show the architect’s intent from a century ago rather than what stands today. Record drawings are not the same as a measured as-built. (See the FAQ below on record drawings versus as-builts.)
Because of that, an HBIM workflow cannot just “model the building.” It has to decide how much of the irregularity is worth modeling and how much should stay as measured evidence. A leaning rubble wall can be a single Revit wall on its true centerline, or a faithful warped surface; one is a background, the other a research artifact, and they cost very different amounts.
The scan is the measured foundation
For existing conditions, laser scanning is almost always the measurement base, and it is the part WeAre Capture does in the field. We capture with a Trimble X7, register the scans into a single coordinated point cloud, and deliver that cloud in the formats the modeling team needs: E57 for an open exchange, RCP/RCS for Revit and AutoCAD, and the original station data where it helps. A scan day on site runs up to roughly twelve hours depending on access, height, and how much of a tower, roof, or facade has to be reached from limited setups. The HBIM model itself, the Revit/IFC authoring, is downstream modeling work that we coordinate through modeling partners; the scan and the registered cloud are what we own.
That distinction matters, because the point cloud is useful on its own. It is the measured source of truth: a modeler interprets it into geometry, but the cloud stays as evidence behind every element, and reviewers can go back to it to check a dimension the model simplified. Registration realities apply too. Tight projects use survey control or targets for an absolute coordinate system; many heritage jobs use cloud-to-cloud registration on a local origin. Either way, the coordinate basis should be written into the handoff so the model and the cloud line up later.
Decide what to model, and what to leave as something else
The single most useful decision in an HBIM scope is not “what LOD,” it is “what output does each element deserve.” Not everything should become a modeled object. The table below is how we think about the trade-off for irregular historic elements.
| Element | Best output | Why |
|---|---|---|
| Walls, floors, levels, openings, roof forms | Modeled in Revit (LOD 200-300) | Spatial coordination, design backgrounds, quantities |
| Facade with profiles and string courses | 2D CAD elevation from the cloud, or scoped modeling | Restoration drawings need accurate line work, not heavy families |
| Ornament, carving, plaster detail | Point cloud view or photo record | Modeling it parametrically is slow and rarely changes a decision |
| Warped or settled surfaces | Left in the registered point cloud | The cloud already records the true shape better than a clean model |
| Material, condition, phase notes | Information attached to model elements | Useful only if the receiving team will actually read those fields |
For a lot of projects the practical answer is a modeled shell plus the full point cloud, not an attempt to model every surface. That combination is cheaper, faster, and often more honest about what is known.
LOD and LOA are not the same thing
Two standards-based ideas get blurred constantly, and separating them is the clearest way to scope HBIM. LOD (Level of Development, from BIM specifications) is about how much of an element is modeled: a generic wall versus a wall with finishes, openings, and material. LOA (Level of Accuracy, defined by the US Institute of Building Documentation, USIBD) is about how well the geometry is measured against reality, expressed as a tolerance. A model can be richly detailed (high LOD) but loosely located (low LOA), or sparse but tightly measured. Heritage work usually needs both stated, because a facade restoration drawing is worthless if it looks complete but is off by an inch where new stone has to fit. These are industry standards for scope and tolerance, not price benchmarks; there is no neutral conversion from either into a dollar figure.
Write a scope someone can price
A request that can be priced reads something like this:
“Provide a scan-backed Revit model for historic building documentation. Include exterior walls, interior partitions, floors, levels, roof forms, major openings, stairs, and visible primary structure at LOD 200-300. Deliver the registered point cloud (E57 and RCP) and CAD facade elevations. State the coordinate basis. Exclude structural analysis, material testing, repair recommendations, and detailed ornament modeling unless separately marked.”
Compare that to “we need an HBIM model,” which forces the modeling team to either guess high and look expensive or guess low and miss what you wanted. The clearer request also makes the handoff cleaner: a good HBIM package names the RVT version, includes the registered cloud, the CAD sheets and PDFs, an assumptions list, the excluded areas and known blind spots (anything access or line-of-sight prevented from scanning), and the coordinate notes.
What HBIM does not do on its own
An HBIM model supports specialist work; it does not replace it. It will not perform structural analysis, recommend conservation treatments, test materials, interpret the building’s history, review code, or produce fabrication drawings. Those need the relevant specialists. The model and the point cloud give them better measured information to work from, but the judgment stays with the engineer, conservator, or architect.
If your team only needs PDF floor plans, a quick visual archive, or there is no one who will maintain a Revit model, HBIM is probably more than the project needs. A registered point cloud plus CAD drawings and photo documentation is often the better first package, and it can always feed a model later.
To start, the most useful thing you can give us is the building’s use case: restoration, adaptive reuse, owner records, or facade repair. From there we can scope the field capture and a sensible model boundary. Request a quote and tell us what the model has to do, not just that you want HBIM.
FAQ
What is scan to BIM?
Scan-to-BIM turns a laser-scan point cloud of an existing building into a BIM model, usually in Revit. HBIM is scan-to-BIM applied to historic or heritage buildings, where geometry is irregular and scope decisions matter more. See our scan-to-BIM services and the scan-to-BIM LOD guide.
What are as-built drawings?
As-built drawings document a building as it actually exists, including changes made during construction or later renovations. In HBIM work they are typically CAD plans, sections, and facade elevations produced from the measured point cloud rather than from old design records.
As-built vs record drawings: what is the difference?
Record drawings show the design as intended or last documented. As-builts, and an HBIM model built from a fresh scan, show current measured reality. For a historic building those can differ by a lot, which is why a measured scan is the safer foundation. See as-built documentation.
How much does scan to BIM cost?
There is no single dollar-per-square-foot rate, because cost tracks element density and modeling detail far more than floor area. Scanning is typically billed by the day or hour and modeling by area or hour, with HBIM running higher than plain commercial work because of the irregular geometry. Our scan-to-BIM cost factors page walks through what moves the number.
How does 3D laser scanning work for a historic building?
A scanner like the Trimble X7 sits at multiple stations and measures up to 500,000 points per second by timing reflected laser pulses. Those scans are registered into one coordinated point cloud that becomes the measured base for CAD drawings and the HBIM model. Learn more about 3D laser scanning.
Last reviewed: May 2026.