Platform · Data integration
Tektome reads your package as it is.
Submit the native models, drawings, schedules and scanned specifications you already have, and Tektome indexes them in place. Conversion, exports and model cleanup all stay off your critical path.
What it reads
Formats, as they arrive.
Geometry, sheets, schedules and prose are indexed together, so a requirement written in a document can be answered against an element in the model without anyone rebuilding either one.
| Category | Formats | What Tektome reads from it |
|---|---|---|
| BIM models | .ifcRevit plugin | Geometry, element properties, type and instance parameters, spatial structure and schedules held in the model. |
| CAD drawings | .dxf | Layers, blocks, dimensions and annotation, linked back to the sheet each one sits on. |
| Drawing sets | Vector and scan-quality sheets alike. Title blocks, revision clouds, dimensions and drawing notes are read from scans as well as native exports. | |
| Images | .png.jpg.tif | Photographs, marked-up screenshots and image-only sheets, indexed with the text they contain. |
| Schedules | .xlsx.csv | Room and door schedules, requirement registers, equipment lists, read as structured data, not as a flat table of text. |
| Documents | .docx.pdf.txt | Specifications, client briefs, standards, meeting minutes and correspondence, indexed alongside the model they govern. |
Working in a format not listed here? It is usually a question of scope rather than capability. Tell us what you hold and we will confirm.
How data gets in
Four routes in, none of them disruptive.
Start with a drag-and-drop and add the connected routes later. Nothing about the first upload has to be undone to move to a deeper integration.
Direct upload
Drop files or a whole folder into the browser. Nothing is installed, and the first review can run on the package you already have open.
Revit plugin
Submit straight from the model you are working in, so the package under review is the one on your screen rather than an export of it.
Public API
Push packages from your own pipelines and pull findings back into the tools your teams already use.
CDE and folder connections
Watch a folder in your common data environment so each new revision is picked up as it is issued, without anyone re-uploading it. Box and SharePoint land first, with further environments to follow.
What we do not require
The preparation you can skip.
Most model-review tools ask for the work to be tidied before it can be read. Every item below is something Tektome does not ask you to do first.
Model cleanup
No purging, no re-modelling, no fixing warnings before submission. The package is read in whatever state it is in.
Naming conventions
You do not have to adopt a parameter schema or rename anything. Your firm's conventions are learned, not imposed.
Rule authoring
No rule sets to write before the first review. Ask in plain language and refine from the results.
Format conversion
No exporting to an intermediate format. The file you submitted stays the file of record.
A migration project
Nothing has to move off your existing systems. Tektome reads a package where it already lives.
Specialist licences
Reviewing a model does not require a seat of the software it was authored in. Anyone accountable for the work can open it.
The reason is straightforward: preparation work is the reason most review tools are never adopted. Removing it is the integration.
Connected systems
Alongside your stack, not instead of it.
Tektome does not ask you to replace an authoring tool, a viewer or a common data environment. It reads what those systems produce and hands findings back to the people using them.
Revit
LiveA plugin submits the open model directly, so review runs against the file you are authoring.
IFC
LiveThe open BIM standard, read vendor-neutrally, so models authored in any major tool are covered.
AutoCAD
LiveDrawings are indexed sheet by sheet from a DXF export, alongside the models they document.
SharePoint
PlannedPoint Tektome at the libraries where your standards and past projects already sit.
Box
PlannedConnect project folders so issued packages are picked up without a re-upload.
Notion
PlannedRead the internal guidance your teams write down, so it counts as part of the record.
Common data environments
PlannedFolder connections to the environment your project issues through, so revisions arrive on their own.
Your own tools
LiveThe public API puts review, research and requirements inside the internal apps your teams already open.
Where your data lives
Plainly stated, before you upload anything.
Hosting
Your packages are held in a managed cloud environment, encrypted in transit and at rest. Regional hosting is available where a project or client requires it.
Tenancy
Each organisation has its own instance. Your models, documents and the record built from them are not pooled with another firm's, and are never used to train shared models.
Retention
You decide how long packages are kept and can delete them at any point. Deleting a package removes the source files; the determinations you chose to keep stay in your record.
The full detail (certifications, access control, audit and sub-processors) is set out on Trust and security.
Schedule a Demo
See Tektome run a full review.
Book a 30-minute walkthrough. Bring a package in whatever state it is in, and we will read it as it is and show you what comes back.
- Tailored to your workflow and disciplines
- Live Q&A with our engineering team
- No commitment, no setup required
Book a 30-minute demo
Step 3 of 3
Pick a time with Henry
Thirty minutes, and you will get a calendar invite straight away.
Your meeting is booked.
A calendar invite is on its way to your inbox.
Henry will bring a prepared sample project, so there is nothing for you to set up.
Need to change it? Reply to the invite and we will sort it out.