Customer questions, answered

Scope3D reads your BIM and drawings — IFC, Revit .rvt, DXF, STEP, and PDF drawing sets or plan images. You upload the source and it becomes a live 3D model that you own.

Yes. Drop a drawing set into the PDF builder, the walls are traced off the sheets and corrected in the scene, then authored into a real IFC twin you own.

The floorplan detector reads the plan, segments the rooms, and reconstructs storeys, walls, and openings into a clean twin you can then correct by hand.

Yes. Bring an RVT, or an IFC exported from Revit. Scope3D reads the semantics — types, storeys, and properties — not just the triangles of a mesh.

Yes. Element names in Cyrillic are translated to English for display only, and cached across models, so the original names inside your IFC are never rewritten.

Portfolio-scale models are fine — a few hundred megabytes of federated IFC runs in a browser tab. Very heavy sets are baked once into a Fast view fragment, so a 143 MB model reopens from about 11 MB.

Yes. Modify mode edits walls, slabs, doors, and openings on the real IFC. Every edit is versioned, so you can step back to any earlier point at will.

Materials mode puts real finishes onto live geometry — floors, walls, ceilings — per room or per element, and those finishes export back out to IFC.

Furnish mode places real catalogue furniture and equipment into rooms, so layouts, clearances, and fit-out counts come off the twin instead of a spreadsheet.

Separate IFCs — architectural, structural, plumbing, MEP — merged onto one twin. Toggle any of them off to see what sits behind the one you are looking at.

Yes. Model version history keeps every geometry edit as a restore point, even after saving, so a wrong wall or a bad merge is one click from being undone.

Builder Config turns a twin into a buyer showcase: configure each area, show the upgrade options, and let the buyer see the choice on the real building in 3D, not a brochure. Prices stay out of the view by design.

IFC — one format, and it carries the whole twin: geometry, properties, and the finishes written onto the elements. Revit and the rest read it through their own IFC import.

As data, yes. Each finish is written onto its element as an IfcMaterial plus a property set, so Revit imports the twin with every surface named and schedulable. Appearance is a separate visual tier.

Your twin is owner-held — the geometry, records, and finishes belong to the building's owner, and ownership transfers with the building. IFC export runs on an author seat while the account is live, so take your copy out before you wind it down.

No live sync. You export an IFC and import it into Revit — a clean one-way handoff that keeps Scope3D the owner's record and Revit the design tool.

Analyze gives element takeoff by IFC type, and Scope AI turns a selection into an estimate anchored to the real elements, with the quantities a trade needs to price the work.

Yes. Ownership transfers with the building, so a developer hands a finished twin to the buyer, and an owner hands operations access to whoever runs the property day to day.

Ask about the building in plain language. It reads rooms, assets, and finishes, flies the camera to what you asked about, and drafts a scope you then refine.

Yes. The copilot works off the semantic IFC data in your twin, not a generic guess, so counts, areas, and clearances come from the building you actually uploaded.

Scope AI anchors line items to real elements, so a cost is tied to the door or the wall it belongs to. You set the rates, and every line stays traceable to its element.

In capex mode it forecasts from install date and expected life, then offers to add a selection to a future year's plan, or to raise a ticket for it right now.

It does. Ask about the pool or a blocked room and the twin flies there and focuses the elements in question, so you are always looking at what is being discussed.

Your model and records stay in your account. The copilot reads only the twin you point it at, for the question you asked, and nothing about your building trains a public model.

Only the people you invite. Share mode sets access per person, and stakeholder notes and exports are scoped to what that person is allowed to open.

Yes. Invite people by email and set the role on the way in. A trade comes in on a stakeholder seat — they open the twin and the scope you shared with them, and they cannot edit the model or export it.

Not for the studio. Scope3D runs in the browser — no plugin, no workstation, no licence server. Scope3D Desktop for Revit is the exception: that one is Windows software you install.

Yes. Each organisation's properties, records, and twins sit behind its own access rules, and a twin is only reachable by the org that owns that building.

The receiving owner does. Transfer moves the property and everything on it — geometry, records, finishes, and history — into their account, under their control.

Version history logs every geometry edit as a restore point, records carry install dates and documents, and tickets keep the operational trail, so nothing changes untraced.