01
Revit / native authoring
The authoring model owns geometry and actual element state. Connector tools can extract rooms, materials and parameters; model changes require explicit review in the authoring environment.
Revit & files
A model is one starting point.
Not the only one.
Begin with the information your project already has. Geometry and structured data have different sources and different responsibilities.
02
IFC / model exchange
An IFC supplied by a project participant can contain geometry and properties without an active Revit session. Its identities, units and version still need validation.
03
Files / project information
Spreadsheets, PDFs and structured files can supply requirements, specifications and drawing references. These records are useful before any 3D model exists.
Where does the geometry come from?
| Source | What it contributes | What to preserve |
|---|---|---|
| Revit model | Native geometry, elements and current model parameters | Model identity, element identity, units and snapshot |
| IFC model | Exchanged geometry and BIM properties from an authoring tool | Source file, IFC GUID mapping, coordinate system and version |
| GLB / glTF | A lightweight visual representation for the web | Links back to source objects; a mesh alone is not a BIM record |
| PDF / drawings | Drawing sheets, references and documented design intent | Original document, revision and page reference; no assumed 3D geometry |
| XLSX / CSV / JSON | Room data, schedules, requirements and structured exchanges | Stable record IDs, schema, units and import provenance |
| Manual entry | Requirements and records before a model exists | Author, time, rationale and later model mapping |
Integration principle
Review the change before it returns to the model.
The intended default is a versioned import from a model or file into project information. A proposed write-back is a separate, reviewed action in Revit. A board edit should never silently change geometry.
What this website demonstrates.
The example uses synthetic records stored in the website. It does not upload files, parse IFC, connect to Revit or write to a model. Those capabilities require separate connector and platform services.
Try the sample workflow