Renovation and retrofit projects rarely begin with a complete, reliable set of drawings. Partitions may have moved, building services may have been added, and important dimensions may be missing from the record. When design and construction decisions depend on that information, a small gap in the field data can become a modelling revision, a coordination delay, or another site visit.
Compared with a workflow based on isolated tape measurements, sketches, and photographs, Scan to BIM gives the team a shared spatial record. LiDAR captures visible building geometry as a point cloud that can be reviewed, discussed, and used as a measured reference for CAD and BIM work. It does not automatically create a finished BIM model, but it gives the people creating that model a clearer view of the building before decisions become difficult to change.
AnAutodesk and FMI study of more than 3,900 construction professionals estimated that bad data accounted for 14% of global construction rework in 2020. This is an industry benchmark, not a performance claim for Scan to BIM or FJD Trion. It helps explain why teams are paying closer attention to how existing conditions are captured, checked, and shared.
Who Can Benefit from a Scan to BIM Workflow?
Scan to BIM is relevant to more than large construction organisations. The business case can be particularly clear for people working with limited staff, tight deadlines, or outsourced measurement services.
An independent BIM consultant or small design practice may not have a dedicated survey team. Instead of waiting for a third-party survey and then discovering that a key dimension is missing, the team can capture the required space and review the data as part of its own workflow.
A small architecture, engineering, or construction company may have only three to five people sharing site, coordination, and modelling responsibilities. For these teams, every avoidable return visit and every hour spent reconciling separate field records takes time away from project delivery.
A BIM or VDC team may regularly receive point clouds or measurements from external providers. If the coverage, dimensions, or coordinate information are unclear, modelling can start from an unreliable basis. Reviewing the captured data before modelling begins gives the BIM team an opportunity to raise questions while they can still be resolved efficiently.
Project managers, contractors, and building owners may not work with the point cloud every day, but they need confidence that design, procurement, and construction decisions reflect the building that exists. A shared review process helps them confirm the scope and limitations of the information before the next project decision.
Where Scan to BIM ROI Comes From
The value of Scan to BIM does not come from a headline saving percentage. It comes from measurable changes to a project’s actual workflow.
Fewer return visits caused by missing measurements
A traditional survey may capture exactly what the team knows to request on the day. The problem appears later when a designer needs another ceiling height, opening dimension, or relationship between two spaces. If the required geometry is present in a reviewed point cloud, the team may be able to answer the question without arranging another visit.For ROI purposes, measure the travel, access coordination, field labour, and schedule disruption associated with return visits that the captured data genuinely replaces.
Less time spent consolidating field records
Manual workflows often require someone to connect measurements, sketches, photographs, and notes before the design team can use them. A point cloud does not remove processing or modelling work, but it gives the office team a spatial reference in which those observations can be understood together.Compare the actual field-to-office labour hours rather than assuming an automatic percentage saving.
Earlier clarification of existing conditions
An information gap becomes more expensive when it is discovered after design, procurement, or site work has moved forward. A shared point cloud gives architects, BIM teams, contractors, and owners a common reference for discussing visible conditions earlier.It cannot prevent rework caused by design changes, workmanship, procurement, or concealed conditions. Its more specific value is reducing uncertainty and potential rework linked to incomplete or unclear existing-condition measurements.
One dataset supporting several approved deliverables
Depending on the agreed scope, a validated point cloud may support an existing-condition model, floor plans, sections, coordination reviews, as-built documentation, or a pre-construction record. Count this reuse only when the same dataset replaces a separately commissioned survey, modelling task, or documentation effort. Possible outputs are not the same as verified economic value.
Calculate ROI with project data, not a headline percentage
Compare two complete workflows. Estimate the traditional workflow cost, including field labour, travel, office consolidation, potentially avoidable return visits, and measurement-related clarification or rework. Then estimate the total Scan to BIM cost, including planning, capture, processing, modelling, software, training, quality review, and handover.Use the following formulas: Net benefit = estimated traditional workflow value avoided + downstream cost avoided + verified reuse value − total Scan to BIM workflow costProject ROI (%) = net benefit ÷ total Scan to BIM workflow cost × 100
Illustrative ROI example: a 25,000 m² existing-building renovation
Consider a 25,000 m², six-storey commercial building undergoing renovation and partial adaptive reuse. The existing drawings are incomplete, several building services have been modified, and the team needs floor plans, an existing-condition model, coordination references, and pre-construction documentation.The figures below are illustrative assumptions. Replace them with the customer’s actual labour rates, travel costs, modelling scope, rework exposure, and approved deliverables.
| Cost or value item | Illustrative assumption | Estimated value |
|---|---|---|
| Avoidable field-survey cost | 4 surveyors × 12 days × $700/day | $33,600 |
| Avoidable office-consolidation cost | 2 technicians × 15 days × $550/day | $16,500 |
| Avoidable travel and access costs | Project estimate | $8,000 |
| Potentially avoidable return visits | 2 visits × $7,000/visit | $14,000 |
| Estimated traditional workflow value avoided | $72,100 | |
| Total Scan to BIM workflow cost | Capture, processing, modelling, quality review, and handover | $80,000 |
| Verified deliverable reuse value | Additional approved deliverable supported by the same validated dataset | $18,000 |
Because downstream savings are uncertain, model low, expected, and high scenarios:
| Scenario | Downstream cost avoided | Net benefit | Project ROI |
|---|---|---|---|
| Low | $20,000 | $30,100 | 37.6% |
| Expected | $45,000 | $55,100 | 68.9% |
| High | $80,000 | $90,100 | 112.6% |
For the expected scenario:
Net benefit = $72,100 + $45,000 + $18,000 − $80,000 = $55,100Project ROI = $55,100 ÷ $80,000 × 100 = 68.9%
This example does not suggest that every 25,000 m² project will achieve the same result. It shows how a customer or dealer can build a project-specific business case using transparent assumptions. Reuse value should be included only when the same validated dataset replaces a separately commissioned task, so that benefits are not counted twice.For a reliable baseline, review similar completed projects and track field and office hours, return visits, travel costs, information requests, measurement-related rework, and data reuse.
Why Existing-Building Projects Need a Reliable View of Reality
Across a complex property, one missed dimension can mean another site visit. An unclear ceiling condition can delay coordination. A drawing based on incomplete information can create changes that are difficult to resolve once work is under way.Reality capture gives the team a shared spatial record rather than a collection of disconnected observations. Architects, surveyors, and BIM specialists still need to interpret the site, but they can discuss the same visible condition using the same measured reference.
Step 1: Define What the Workflow Must Deliver
Start with the decision the project needs to support, not with the scanner. A facilities team may need an updated floor plan. An architect may need a reference for a renovation design. A BIM team may need point-cloud data for modelling and coordination. A contractor may need a pre-construction condition record.
Before anyone arrives on site, agree on the required outputs, included and excluded areas, coordinate approach, and model scope. If the data will support an as-built BIM model, define what must be modelled and to what level of detail. If the goal is a CAD drawing or floor plan, state the drawing requirements instead of assuming that every visible object must become model geometry.
A short written scope gives the capture team and the receiving team a shared definition of complete.
Step 2: Plan How to Scan an Existing Building for BIM
Divide the site into manageable zones, note access restrictions, and flag areas with changing light, reflective surfaces, moving people, or heavy traffic. Plan how stairwells, plant rooms, corridors, facades, and other complex spaces will be covered.
For renovation work, focus early on structural features, service routes, floor changes, openings, and visible differences from the existing drawings. A short walk-through can prevent a longer explanation after the dataset reaches the office.
For interior surveys, a portable system such as theFJD Trion P2 LiDAR Scanner or FJD Trion V4e LiDARcan help the operator capture rooms, corridors, and other building spaces without repeatedly stopping to take individual measurements. Instead of recording isolated dimensions with a tape measure, the operator can follow a planned route and capture the surrounding spatial context as they move.
This can make the field process more continuous and give the BIM team a broader reference for reviewing existing conditions. Depending on the building layout, required coverage, and capture method, a team may be able to document an entire floor in a relatively short site visit. Any specific time claim, such as completing a floor in 10 minutes, should be supported by a verified test condition before publication.
The person collecting field data is not always the person creating the BIM model. If missing dimensions or inconsistent measurements are discovered only after modelling has started, the model may require substantial revision and the project schedule may be affected. A point cloud does not remove the need for professional review, but it can provide a more complete spatial record than disconnected measurements, sketches, and photographs.
The field plan should still include a consistent route, sufficient overlap between spaces, and a simple way to record areas that are locked, occupied, obscured, or temporarily unsafe to enter.
Step 3: Capture Existing Conditions and Check Coverage On Site
During capture, ask whether the project team will be able to understand the space later without returning to site. Cover the agreed areas first, then pay close attention to room transitions, vertical circulation, concealed corners, changes in level, and elements likely to be altered.
The right LiDAR setup depends on the size, layout, and complexity of the building. For a larger or more demanding survey, teams may also evaluate the FJD Trion S2 Series LiDAR Scanner as part of the capture setup. The equipment choice should follow the required coverage, deliverables, and site conditions.
On-site review is the first opportunity to prevent an avoidable return visit. Check that important rooms, surfaces, and connections are present while access to the building is still available. Record any inaccessible or uncertain areas before the data is handed to the modelling team.
Step 4: Review the Point Cloud Before BIM Modelling
A point cloud is a measured representation of a space, not a finished BIM model. Before moving from point cloud to BIM, confirm that the dataset covers the agreed scope, follows the project reference system, and is suitable for the intended modelling or documentation task.
Review registration or alignment, identify gaps, and confirm that important building features can be interpreted with confidence. Record what the data does not show, including inaccessible areas, obscured surfaces, and conditions that could not be verified.
Step 5: Align Stakeholders Before BIM Modelling Begins
The scanner operator and the BIM modeller are only two participants in the workflow. The same point cloud may need to answer different questions for several stakeholders:
- The client or building owner needs to confirm that the captured areas reflect the building and support the next design decision.
- The architect or designer needs to review dimensions, openings, room layouts, and visible conditions before developing the renovation or retrofit design.
- The BIM or VDC team needs a consistent spatial reference for modelling and coordination.
- The contractor or site team needs to verify existing conditions before procurement, installation, or construction.
- The facilities team needs information that remains understandable after the design team has left.
Without a shared review stage, each person may work from a different interpretation of the building. A missing measurement or unclear area can then become a design question, a coordination delay, or a modelling revision.
With FJD Trion Model Web, the team can share a point cloud through a browser link before BIM modelling begins. Clients, designers, contractors, and site personnel can review the same spatial data without installing specialist desktop software or relying on high-performance computers.
The team can use this review stage to confirm coverage, key dimensions, visible building features, inaccessible areas, and the agreed modelling scope. The BIM modeller can review the data remotely with the customer and on-site personnel, record limitations, and agree on the next modelling step before significant time is invested in the model.
The value of Scan to BIM is not only the point cloud. It is the connection between field capture, shared review, stakeholder approval, and the final project deliverable. To see how reality-capture workflows are applied in practice, explore FJD Trion customer case studies across different products, industries, and countries.
Step 6: Create a Handover the Project Team Can Use
The final handover should reflect the scope defined at the beginning. It may include a point cloud, a project viewer, CAD-ready information, a BIM reference, or a combination of these.
Use a clear folder structure and include a short note covering file contents, coverage, coordinate assumptions, known limitations, and intended use. This context helps the next person understand what has been delivered and how it can be used.
Common Scan to BIM Mistakes to Avoid
Do not scan before defining the final deliverable. A large dataset is not automatically a useful dataset.
Do not treat the point cloud as a finished BIM model. Moving from point cloud to BIM requires modelling decisions, project standards, and professional interpretation.
Do not leave the first meaningful quality check until everyone is back in the office. A short field review can address missing coverage while access is still available.
Build a More Dependable Scan to BIM Workflow
A successful Scan to BIM project is not defined by the amount of data collected. It is defined by whether the right people can use that data to make better-informed decisions.
Start with the deliverable, plan capture around the building, review the point cloud before modelling, and share the data with enough context for the next team. For existing-building projects, this connected process creates a more reliable starting point for design, coordination, and construction planning.
See how FJD Trion’s Scan to BIM workflow can connect existing-condition capture, point-cloud review, stakeholder alignment, and model-ready project information.
Frequently asked questions
Learn how a Scan to BIM workflow uses LiDAR, point clouds, BIM modelling, and browser-based collaboration to document existing buildings, review project data, and support renovation, retrofit, and adaptive reuse projects.
A Scan to BIM workflow uses reality-capture data, commonly represented as a point cloud, as a measured reference for creating or updating BIM information. It includes project scoping, field capture, data review, modelling, quality checks, and handover.
LiDAR captures visible building geometry and creates a point cloud that can be reviewed and used as a measured reference for CAD, BIM modelling, and existing-condition documentation. It helps project teams understand the building before design or modelling decisions are made.
A typical workflow includes defining the required deliverable, planning the capture route, scanning the agreed areas, checking coverage, reviewing the point cloud, aligning stakeholders, and creating the final BIM or CAD output. The exact process depends on the building layout, project scope, and required level of detail.
No. A point cloud represents measured visible surfaces. A BIM model contains interpreted and organised building elements. The point cloud supports modelling, but the final BIM deliverable depends on the agreed scope, standards, and professional decisions.
Depending on the agreed scope, the workflow may support point-cloud data, floor plans, sections, elevations, existing-condition models, coordination references, as-built documentation, and pre-construction records. Not every project requires all of these outputs, so the deliverable should be defined before capture begins.
Not necessarily. A browser-based workflow such as FJD Trion Model Web can allow authorised project participants to review shared point-cloud data through a web link, subject to access settings and supported formats. This can help clients, designers, contractors, and site teams align before BIM modelling begins.
The approach is particularly relevant to renovation, retrofit, adaptive reuse, building documentation, and projects where existing drawings are incomplete or no longer reflect current conditions. Its value is strongest when the team has a clear plan for turning captured data into a defined project deliverable.
Yes. Scan to BIM can be useful for small teams that do not have a dedicated survey department or that regularly rely on third-party measurement services. A defined workflow can help them capture, review, and share existing-condition data without separating field information from the modelling process.
