Skip to content

BlogPricing

Point Cloud to Revit: Pricing Models and What Drives Cost

Point Cloud to Revit: Pricing Models and What Drives Cost

Point cloud to Revit is the work of building a Revit model against a registered point cloud: the modeler links the scan into Revit and draws walls, floors, openings and other elements on top of it, so the model matches the building as it stands. Quotes for this work are written in several different ways, and two quotes that look alike can cover very different scope. This guide explains how the process runs, the pricing models a buyer meets, what moves the price, and how to get quotes that can be compared.

What does point cloud to Revit mean

A point cloud is a set of measured points, usually from a terrestrial laser scanner, that records the surfaces of a building. When several scans are aligned into one coordinate system, the result is a registered point cloud. Point cloud to Revit is the step after that: a modeler uses the registered cloud as a reference inside Revit and builds native Revit elements (walls, floors, doors, ducts, beams) that follow it. The cloud itself is not the model. The model is a set of editable objects, and the cloud is the evidence they were drawn from.

Autodesk’s Revit help describes the link step: a point cloud is brought in through the Insert tab, Link panel, Point Cloud command, as an indexed .rcp or .rcs file, and positioned by one of several automatic options (center to center, origin to origin, by shared coordinates, or origin to last placed). Raw scan data is typically indexed in ReCap first, before Revit can use it. The how-to for that step is in how to import a point cloud into Revit. The service that covers the whole chain, from scan to finished model, is scan-to-BIM.

How the process runs

The order of work matters for pricing, because each step is a place where a quote can include or exclude something.

  1. Scan. The building is scanned and the scans are registered into one cloud. A buyer who already has a cloud skips this step.
  2. Index and link. The cloud is indexed to .rcp or .rcs and linked into a Revit project with the right origin and levels.
  3. Model. The modeler draws the elements named in the scope, to the agreed level of development.
  4. Check. The model is compared against the cloud, for example with section cuts through the cloud, and corrected.
  5. Deliver. The Revit file is delivered in the agreed version, with the agreed template, and the scope states what was and was not modeled.

The registration step has its own effect on cost and quality, covered in registered vs unregistered point clouds.

What pricing models does point cloud to Revit work use

Quotes are commonly written in one of four ways. Each is a way of deciding who carries the uncertainty in the scope, and each rewards one behavior and risks another. Which firms use which model, and at what rates, is not stated here, because that varies by firm and changes over time.

Model How it is written What it rewards What it risks
Per project (fixed quote) One price for a written scope A clear, complete scope; the buyer knows the total before work starts Scope that is vague; changes after signing become change orders
Per square foot A rate multiplied by the modeled area Easy first comparison between quotes Hides what is inside the rate (level of development, MEP, deadline); a large plain area and a small dense one price the same
Per sheet or per element category A price for each drawing sheet, or for each category such as architecture, structure, MEP Buying only the categories needed The number of sheets or categories can grow during the job; categories need clear boundaries
Hourly Time spent, at an hourly rate Flexibility when the scope cannot be known in advance The buyer carries the risk of slow work; the total is unknown until the end

Per project pricing puts the estimating work on the firm before the job starts, which is why it asks for a clear scope. Per square foot is a shorthand that only holds when the quotes being compared have identical scope behind the rate. Hourly work suits exploratory jobs, such as a small trial area, better than a full building.

We price per project and quote within one business day.

What drives the price

The same building can be quoted at very different totals depending on the scope. These are the factors that move it.

Price driver What changes Why it moves the price
Area Floor area and number of floors to model More surface to trace and more elements to place
Level of development Basic massing and openings, or detailed elements with accurate sizes More detail means more drawing and more checking against the cloud. See LOD 200 vs LOD 300
Element categories Architecture only, or with structure, MEP, site Each category is a separate body of modeling
MEP Ducts, pipes, cable trays, equipment Many small runs, often partly hidden above ceilings; dense in mechanical rooms
Cloud quality and registration Density, coverage, gaps, alignment between scans Gaps force assumptions or a rescan; poor alignment slows every step
Revit version and template The version delivered, and the client’s template, families and naming A custom template means extra setup and mapping
Deadline Delivery date requested A short deadline can raise the price.
Condition of the building Clutter, finishes, occluded areas Hidden surfaces cannot be measured and are marked as assumed

A scanner sees only the surfaces it can reach. Framing inside walls and buried pipes do not appear in a cloud, so the scope should say how those are handled. Accuracy is another line worth writing down. The U.S. Institute of Building Documentation publishes the USIBD Level of Accuracy (LOA) Specification, version 3.1, which gives building documentation accuracy a shared vocabulary, including guidance on specifying tolerances by standard deviation. Naming the level in the scope removes one cause of dispute.

What a published price range looks like

For reference, these are our published ranges. A registered point cloud starts from about $1,200 for a house or a floor. With drawings or a model, a house or an apartment runs $2,000 to $4,500, a house with its facades and the site $2,500 to $5,000, and an office or a commercial floor $3,000 to $9,000. Large buildings start from $12,000. Small jobs (a room, a basement, one small floor) start from about $1,000. A model of a commercial floor usually takes two to four weeks, and a whole building, dense systems or a high LOD four to six.

Modeling from a client’s own point cloud is quoted on the cloud: the area, the density and coverage, and the element categories. A cloud the client already owns can lower the total, because the scan is not repeated, but a cloud with gaps or poor registration can add work. The fuller cost picture, with examples, is in scan-to-BIM cost.

How to get quotes you can compare

Comparison fails when each firm prices a different job. Send the same package to every firm and ask each to answer against it:

  • Address, building type, gross area and number of floors, with the areas to be modeled marked on a plan.
  • Whether you have a point cloud (and its format and coordinate system) or need a scan.
  • Element categories wanted: architecture, structure, MEP, site.
  • Level of development for each category, and any accuracy requirement.
  • Revit version, template and any naming standard.
  • Deliverables beyond the model: sheets, schedules, a point cloud export.
  • The delivery date and any phasing.
  • How hidden or unreachable areas should be handled.

Ask each firm to state what is excluded. A quote that lists exclusions is easier to compare than a lower one that does not. The scan-to-BIM quote checklist expands this list item by item.

FAQ

How much does point cloud to Revit cost?

Our published prices run from about $1,000 for small jobs and $2,000 to $4,500 for a house or an apartment with drawings or a model, through $3,000 to $9,000 for an office or a commercial floor, to $12,000 and up for large buildings; a model from your own cloud is quoted on the cloud. It depends on area, level of development, element categories and the quality of the cloud.

What is the difference between point cloud to Revit and scan to BIM?

The two terms describe the same output, a Revit model built from scan data. Scan to BIM is the broader term: it may include the scan, and the model can be Revit, ArchiCAD or IFC. Point cloud to Revit usually means a Revit model from a cloud that already exists.

Is point cloud to Revit priced per square foot?

It can be quoted that way, and we price per project. A per square foot rate only compares fairly when the scope behind each rate is identical.

Can I send my own point cloud for modeling?

Yes. The cloud is checked for coverage, density and registration, and the price is quoted on that cloud and the element categories requested.

How long does a point cloud to Revit model take?

A model of a commercial floor usually takes two to four weeks, and a whole building, dense systems or a high LOD four to six. Deadline, area and level of development change that.

What file format does Revit accept for a point cloud?

Revit links indexed .rcp and .rcs files. Raw scan data is typically indexed in ReCap first.

Sources

Ready when your site is.