Two Scan-to-BIM proposals can describe the same building area and price different work. One may cover modeling from a supplied registered cloud. Another may also include site capture, registration checks, drawing production and a particular acceptance report. Compare those activities before comparing the totals.
Scan-to-BIM cost is a scope question as much as a pricing question. A useful budget states who supplies the data, what information the model must contain and how the delivery will be checked. The worksheet in this guide helps you make those assumptions visible without treating another project's rates as a reliable price for yours.
Separate capture from modeling
Start by identifying the party responsible for field capture and the condition of the information supplied to the modeler. A scanner hire, a registered point cloud and a reviewed existing-conditions model are different deliverables. Your request should say which of them you already have.
If capture is outside the modeling scope, ask what intake review the modeler will perform and what happens when the data is incomplete or unsuitable. A model-only appointment should not quietly acquire responsibility for missing rooms, inaccessible ceilings or an unexplained coordinate transformation.
If capture is included in the wider project, identify its provider, access arrangements and required outputs separately. This guide does not assume that Arcengine performs site capture. Its point-cloud-to-BIM service is the relevant place to discuss modeling scope and the information that will be supplied.
Describe the model by intended use and elements
Building area helps describe a project, but it does not tell the modeler what to represent. An architectural shell model and a coordinated services model of the same area require different work. Dense plant areas, repeated spaces, unusual geometry and occluded surfaces also change what needs to be interpreted and checked.
Specify the uses that matter: renovation layout, coordination, drawing extraction or another defined task. Then identify the elements, information and exclusions needed for those uses. State whether particular interfaces must be represented and which uncertain conditions should be flagged instead of inferred.
Use an element matrix alongside any LOD request. The BIMForum LOD specification addresses model content and reliability. A particular LOD label does not by itself establish the positional accuracy of the supplied scan or the model's fitness for every future use.
Compare the scope in separate rows
This table is a hypothetical comparison structure. It contains no Arcengine prices, market averages or promises about savings.
| Scope question | Proposal A | Proposal B | Question to resolve |
|---|---|---|---|
| Field capture | Supplied by buyer | Included through named provider | Are access and inaccessible areas defined? |
| Point-cloud intake | File readability check | Defined registration and coverage review | Are the review methods equivalent? |
| Modeling | Architecture only | Architecture and selected services | Which elements are required? |
| Drawings | Excluded | Listed plans and sections | Do both totals cover the same outputs? |
| Acceptance evidence | General model review | Agreed report and exception register | What will the buyer inspect? |
Download the scope comparison worksheet and replace the example entries with the actual proposals. Keep unknowns open until the providers clarify them. A blank allowance is not evidence that an activity is included.
Define the checking work you are buying
Ask how the provider will review model geometry against the available evidence, how coverage limitations will be reported and which parts of the model will be sampled or checked. State the acceptance method and agreed thresholds in the appointment. Do not invent a blanket millimeter tolerance because it appears in another provider's article.
The USIBD Level of Accuracy resource offers a professional framework for discussing accuracy requirements. Applying a framework still requires the project team to define the intended use and the required evidence. It does not establish that a particular provider or project is certified.
Checking can also include object scope, naming, file versions and the usability of extracted drawings. Keep those checks distinct. A model can be geometrically plausible and still omit an agreed element, while a complete object list does not prove that every surface meets an agreed accuracy requirement.
Record how changes and gaps affect the fee
Separate a correction to an agreed deliverable from a change in the brief. Adding another floor, requesting a new discipline or changing the required outputs after modeling starts can create additional work. A quotation should explain how that work will be assessed and authorized.
Data gaps need a similar arrangement. If a ceiling zone was not captured, decide whether it will remain unmodeled, be represented under a documented assumption or require additional information. Identify who can make that decision. A neat model should not hide uncertainty simply to preserve the original price.
Agree how many review cycles or what defined review scope is included, which submissions trigger those reviews and how consolidated feedback should be supplied. The important detail is the working arrangement, not the wording of a broad “revisions included” line.
Compare delivery dates against the same dependencies
A proposed completion date means little without its start conditions. Record when the usable dataset, approved scope and necessary answers will be available. Ask whether the date includes buyer review and corrections or ends at first submission.
Your internal review capacity belongs in the budget too. A delivery that arrives before your team can examine it may not advance the project as expected. Identify a reviewer and a realistic acceptance window before committing downstream work to the model.
Keep the package sequence visible if a project needs phased deliveries. A first-floor architectural model may be useful before a complete building package, but only if its issue purpose and dependencies are explicit. Partial delivery should not create an impression that the whole model has been accepted.
Questions about Scan-to-BIM pricing
Can we compare proposals by cost per square foot?
You can record that unit if the providers use it, but compare the element scope, input condition, deliverables and checking basis first. The same area can contain very different modeling obligations. A unit rate alone will not reveal those differences.
Is a higher LOD always more expensive?
Additional agreed information or interfaces can add work, but a blanket label is an incomplete pricing basis. Ask providers to describe what changes in the actual element scope and review requirements. The LOD scope guide provides a matrix for that conversation.
What should we send for a useful quotation?
Supply representative data, an area and discipline breakdown, intended model uses, target file versions, required drawings and known limitations. The Scan-to-BIM process guide includes an input register. Complete that register and the cost worksheet before requesting a scoped proposal.
A working record for this guide
