Your team captures the site. Then the real work starts: registering hundreds of scans, cutting them into deliverables, shipping hard drives, and answering the same "can you send me the view from level 3?" email for the tenth time.
Laser scan management software promises to fix that by putting scan data in the cloud. But if you own the scan supply, two questions decide whether a platform is worth it. Will performance hold up on your biggest projects? And does it replace what your team does, or make your team more valuable?
This guide gives you six criteria to answer both, plus a pilot plan you can run in two weeks.
A single terrestrial scan can hold tens of millions of points. Multiply that by a few hundred positions on a refinery unit or a hospital wing, and you're handing clients hundreds of gigabytes they can't open without specialist desktop software and a workstation to match.
So the data gets fragmented. The engineer gets a cropped cloud points, the project manager gets screenshots, and the facility team gets nothing. Each copy drifts from the last one, and nobody is sure which version matches the site. That's how data silos turn into rework, extra site visits and avoidable risk.
The cost lands on your team too. Every request for a new view or a different section becomes a manual export. Your specialists spend hours on file logistics instead of capture, registration and QA, the work clients actually pay you for.
Every platform looks fast with 10 scans. The question is what happens with 500 positions from mixed scanners, opened by 20 people on hotel Wi-Fi and site laptops.
Performance depends mostly on how the platform handles the data, so ask how it's stored and delivered:
What to test:
If a vendor only demos curated sample data, bring your own.
Speed means nothing if the platform quietly decimates your data. Your reputation rests on accuracy, so the cloud version of a scan has to be something you'd sign off on.
Ask three direct questions:
Then check it yourself. Pick a control dimension you've already verified on site, such as a column spacing or a pipe diameter, and measure it in the platform. If the number moves, so does your liability.
Visual clarity matters as much as the coordinates. Point clouds are notoriously hard to read for anyone outside the scan team. A view that looks like the real site lets a plant manager or architect make a call without phoning your surveyor to interpret it.
This is the question most scan owners don't say out loud. If clients can open the data themselves, do they still need you?
Look at what a scan management platform actually takes over. It removes file logistics: exports, cropping, copying, shipping drives, chasing who has the latest version. It doesn't capture the site, register the scans, control accuracy or interpret what the data shows. Those stay with your team, and they become more visible.
| Task | Today | With a cloud scan platform |
| Capture and registration | Your team | Your team |
| Accuracy control and QA | Your team | Your team, with a shareable record |
| Cutting views and sections for each stakeholder | Your team, on request | Stakeholders, self-serve |
| Shipping data and managing versions | Your team, by drive or transfer link | One shared project, one version |
| Scan-vs-BIM checks and issue reporting | Specialists only | Your team leads, others comment |
| Repeat scans and progress tracking | Ad hoc | A recurring service on the same project |
The pattern is clear: the low-value work moves out, and the expert work moves forward. Teams that adopt a platform tend to sell more, not less, because clients start using scan data in meetings, design reviews and maintenance planning, which creates demand for updated captures and progress tracking.
When you evaluate, ask whether the platform lets you stay the owner of the project: who controls uploads, who sets permissions, and whether your branding or company name stays attached to the deliverable. On Cintoo, for example, the provider can own the project and invite clients with tailored roles, or hand the project over to the client's account when ownership needs to move. Custom branding is available as a separate option.
Sharing is the point, but uncontrolled sharing is a risk, especially on industrial, energy or defense sites where scan data is sensitive.
Check for:
A scan platform that becomes another island just moves the silo. Map your inputs and outputs before you shortlist.
Inputs. Confirm the formats you deliver today: E57, FLS, LSPROJ and RCP from registration software, plus BIM models such as IFC, RVT, DWG, JT, STP, STEP, OBJ, RVT, NWD and NWC. Check whether each format loads from disk or only through a cloud connection.
Outputs. Check that data can go back out without losing its coordinate system, for example as RCS for modeling in Revit or as a point cloud region for a specialist.
Connections. Look for live links to the environments your clients work in, such as Autodesk Construction Cloud, Procore or ArcGIS, plus an API or SDK if you build your own workflows. Cintoo lists integrations with Autodesk Construction Cloud, a Revit plugin, Procore, ArcGIS and Power BI, plus Newforma Konekt, an Unreal Engine plugin, a public REST API and a C++ SDK.
Pricing tells you who the platform was built for. Per-seat models suit internal design teams. Capacity-based models, priced on how much scan data you host, suit teams whose job is to supply scans to many people. Cintoo, for example, prices on scan-position capacity, with unlimited users and projects.
Run the numbers on a typical year:
Then weigh it against what you spend today on drives, transfer services, export time and repeat site visits. For many scan teams the strongest return comes from avoided trips: one wasted visit to a remote plant can cost more than a year of hosting [TO VERIFY: replace with a sourced figure or a customer example].
Demos are scripted. A pilot on your own data answers both buyer questions in days. Most vendors offer one; Cintoo has a free 30-day trial.
The last answer is the one that matters. If stakeholders still need you for interpretation, QA and new captures, but not for file handling, the platform is extending your team, not replacing it.
| Criterion | Pass if |
| Performance | Largest project opens and navigates smoothly in a browser on a standard laptop |
| Fidelity |
Control measurements match site values within your tolerance |
| Team role | File requests drop; expert requests stay with your team |
| Access control | You can set roles and permissions per project, a project member can be invited to only a workzone of the project or to another part thanks to the group management workflow. |
| Interoperability | Your input formats load and outputs keep coordinates |
| Commercial model | Cost per project beats today's delivery cost |
Cintoo was built for teams that own the scan data and need everyone else to use it. Its patented TurboMesh technology converts each scan position into a high-fidelity mesh around 10 to 20 times smaller than the source point cloud, while keeping the source data's resolution, color and intensity, so large projects stream in a standard web browser.
Your team keeps the specialist work: capture, registration, QA and analysis. Clients, designers and operators get one hub where they can view scans next to BIM models and 360° imagery, take measurements and raise issues, without asking you for another export. BIM Edition covers scan-to-BIM and scan-vs-BIM workflows, Twin Edition covers plants and facilities in operation, and 360 Edition adds lightweight 360° capture for frequent site updates.
The result: fewer file requests, more projects your data supports, and a team clients see as the source of truth for the site.
See how it works on your own data. Book a demo, or read how other teams share scan data in our customer stories.
It's a platform that stores, organizes and shares laser scan data, usually in the cloud, so stakeholders can view, measure and compare scans without specialist desktop software or local copies of large files.
It depends on how the data is processed. Platforms that convert point clouds into lightweight meshes with levels of detail usually stay responsive on large projects. Test with your largest real project before you commit.
It shouldn't, but verify it. Measure known control dimensions in the platform and confirm you can return to the original point cloud data when needed.
No. A platform removes file handling, not capture, registration, QA or interpretation. Teams usually see more demand for repeat scans once clients use the data day to day.
At minimum E57 and RCP for terrestrial scans, LAS or LAZ for mobile and drone data, and RVT, NWD or IFC for model overlay.