Scan-to-BIM Company vs Freelancer vs Offshore Team

A scan-to-BIM model can be bought from a company that scans and models, from a freelance Revit modeler, or from an offshore modeling team, and all three can produce a Revit file. Choosing between a scan-to-BIM company vs a freelancer vs offshore outsourcing comes down to who owns the three things that decide whether the model is usable: the registration of the point cloud, the check of the model against the scan, and the handoff. This guide explains where each option fits, what each one expects from you, and what to ask any of them before the work starts.

What decides whether a model is usable

Every scan-to-BIM model is traced from a point cloud, and a cloud is trustworthy only once its registration has been checked. A registered cloud comes with a report that lists the average error of each station and the overlap between scans; a cloud without one cannot be checked, and a model built on it inherits whatever drift it carries. Before delivery, a model has to be checked against the cloud it was built from, element by element, to the Level of Accuracy the scope names, which the U.S. Institute of Building Documentation’s specification states as a standard deviation at the 95 percent confidence level, LOA30 being a deviation between 15 mm and 5 mm. And the handoff has to say what the model contains, what it excludes, where the scanner could not see and what was taken from older documents. Whoever you hire, those three things need an owner, and the question to ask of any provider is who that owner is.

A scan-to-BIM company

A company that scans and models is the fit when the building still has to be scanned, when it is complex, or when the project needs one contact from the first station to the delivered file. A company of this kind should plan the stations, register the scans in the field check the registration before leaving the site, index the cloud for Revit and build the model to the level of development the scope names, in the BIMForum Level of Development Specification’s terms, then check it against the cloud before delivery. The delivery is the Revit model, the registered cloud in E57 (the ASTM exchange format) and RCP/RCS with its registration report, and the notes that make the file usable. The scan-to-BIM page describes that scope and the scan-to-Revit workflow guide walks through the sequence.

The premium buys one owner for all three. From us, the price follows the area, the LOD and how much of the building is in scope; our typical ranges from recent projects are $2,000 to $4,500 for a house or an apartment scanned and modeled, $2,500 to $5,000 for interiors with the facades and the site, $3,000 to $9,000 for an office or a commercial floor, and from $12,000 for large buildings, quoted on their own.

A freelance modeler

A freelancer fits a narrow, well-defined modeling task: a registered point cloud you already own, an architecture-only model of walls, floors, doors, windows and stairs, a known Revit version and a LOD per category written down. With clean data and a tight scope, a good modeler is fast and economical.

The risk is the lack of backup. There is no second reviewer to catch a level set wrong or an opening missed, no one to re-register a cloud that turns out to drift, and no capacity if the scope grows into the systems or the modeler is unavailable mid-project. Keep the scope small enough that a single point of failure is acceptable, supply the registration report with the cloud, and write the exclusions down so a gap does not surface as a surprise.

An offshore modeling team

An offshore team is built for production: when the scope is large, the categories are defined and your Revit standards are documented, a team moves through square footage quickly and at a lower price. Such teams are usually modeling-only and expect a clean, registered cloud delivered to them.

Two things decide whether it works. The standards have to be written down, because a remote team models to the specification it is given, and a gap in the specification becomes a gap in the model. And someone on your side has to own the review and answer questions, or a time-zone gap adds days to every open question. The main risk is split ownership: if one party scans, another models and a third reviews, somebody still has to decide whether the final package matches the scope, and if nobody was named, that somebody is you.

What to ask any provider

The same questions cut through every label. What is included and what is excluded, by category? Who reviews the point cloud before modeling starts, and does it come with a registration report? Which Revit version, and which LOD per category? What accuracy is the model stated to, and how is it checked against the cloud? How many review rounds are included, and how is a correction told from added scope? What happens if the scan data turns out to be incomplete? And the one that matters most: who owns the final handoff, and what is in the package? The guide to comparing scan-to-BIM companies turns those questions into a side-by-side comparison, and the guide to laser scanning deliverables describes what a complete package contains.

On price, a low number is reasonable when the scope is simple and risky when it is vague. The cost climbs the moment the LOD is undefined, the systems scope is fuzzy, the registration quality is unknown or the check against the cloud is not actually included; the guide to scan-to-BIM price vs value covers how that plays out.

Sources

• USIBD Document C120, Level of Accuracy Specification Guide, version 2.0 (2016): the LOA levels as standard deviations at the 95 percent confidence level.
• BIMForum, Level of Development Specification 2023, Part I: the level of development definitions.
• Trimble X7 3D laser scanning system datasheet: the registration report contents.
• ASTM E2807, Standard Specification for 3D Imaging Data Exchange: the E57 file format.