Solutions

Stratumly for construction

Real-time site asset register, drone takeoff, and design-intent twin, in one platform sized for a single site rather than an enterprise programme.

What you get

Site asset registers, daily progress, H&S near-miss logs, delivery tracking, weekly site progress drone surveys with volumetric takeoff, and design-vs-built twins on a 4D schedule.

Pain we’re replacing

Enterprise CDE platforms over-priced for a single site
Volumetric takeoff disconnected from H&S and progress
No twin connecting plan to actual

How the three pillars apply

Stratumly is one platform with three layers. Here is what each layer does and why it matters for construction.

Pillar 0

Spatial Data Platform

Site asset register, daily progress and H&S near-miss logs, delivery tracking and live status on a single site map.

The horizontal foundation for every operator who needs to know where their assets are and what's happening to them.

Explore Spatial Data Platform

Pillar 1

Inspection & Intelligence

Weekly site progress drones with volumetric takeoff, automatically reconciled against the schedule and bill of quantities.

Turn periodic drone and LiDAR surveys into continuously-updated intelligence about your asset base.

Explore Inspection & Intelligence

Pillar 2

Digital Twin Studio

Design-versus-built twins on a 4D schedule, surfacing schedule slip and clash before they hit the critical path.

A premium tier for the most critical assets that justify a deep, sensor-bound 3D model.

Explore Digital Twin Studio

One platform for your whole estate

The same map, register, and audit trail that operators in construction use to see every asset, defect, and work order in one place.

Stratumly 2D map and asset register, showing layers, a selected feature, defects, and a linked work order — Illustrative product views. Sample data shown.

Who uses Stratumly day-to-day

One tenant, multiple roles. Each role has the surfaces they need without the licence overhead of a separate product per persona.

Site / project manager: Walks the site dashboard at 07:00, signs off the daily progress log, dispatches against the look-ahead, runs the morning stand-up off the live map.
H&S / SHEQ lead: Reviews near-miss submissions, runs RIDDOR-reportable incidents through the audit log, publishes a public-share H&S map for principal-contractor handover.
Site engineer / setting-out: Imports the design model and the as-built point cloud, runs design-vs-built deviation against tolerance bands, flags clashes before they hit the critical path.
Quantity surveyor: Runs weekly volumetric takeoff against the bill of quantities, reconciles drone-derived earthworks against contractor application, exports for cost-value reconciliation.
Logistics coordinator: Tracks deliveries via the delivery form (GPS + photo + linked PO), updates the delivery layer; the gate-in / gate-out audit trail is automatic.

Concrete workflows

Real scenarios, end-to-end, off the same map and audit log. Not slideware: each step maps to a documented surface.

Weekly progress drone + takeoff

Friday afternoon drone flight; by Monday stand-up the QS has the volumetric diff and the PM has the schedule-slip view.

Surveyor uploads the photogrammetry / LiDAR via the survey upload flow; the processing pipeline produces a tileset.
Change-detection (DTM differencing) returns the moved-material polygon and volume against the previous flight.
A spatial-join against the schedule's work-package polygons attributes the volume to packages; the QS dashboard widget updates.
Design-vs-built deviation runs against the IFC model in the twin (where uploaded); deviations beyond tolerance render as defect annotations on the map.
Monday stand-up opens the project dashboard: schedule, volumes, H&S submissions, open defects on one canvas.

Near-miss to RIDDOR audit trail

A near-miss is logged on tablet; if it escalates, the audit log already has every piece of evidence for the investigation.

Operative fills the near-miss form on tablet (geometry required, photo, severity, witness names); offline-capable, idempotent on resubmit.
Submission auto-creates a feature in the H&S incidents layer and lands in the SHEQ inbox.
If escalated to RIDDOR-reportable, the linked feature, submission, attached media and edit history are exported as a single evidence pack.
The audit log carries a defensible record of who saw what when, including any later property edits.

Delivery tracking with gate-in / gate-out

Materials land at gate; the logistics coordinator wants a clean record without writing on a clipboard.

Driver fills a delivery form at the gate (PO, supplier, photo of load, GPS); submission auto-creates a delivery feature.
Site banksman tags the load against its lay-down area on the map (drawing tool or QR scan from the form).
Gate-out captured by the same form; geometry trail is preserved, incident-investigation queries are spatial.
Logistics dashboard widget shows on-site material against PO commitments by trade.

Public-share progress view for the client

The client's PM wants a weekly snapshot but doesn't want a login.

PM builds a client-progress dashboard: schedule, volumes, photo gallery, this-week's milestones.
Generates a public-share link (token-based) with a 7-day expiry that auto-rotates.
Client embeds the iframe in the project portal; no login, no data egress out of the platform.

Asset register templates we ship

Starter feature classes with sensible attribute schemas. Edit the schema, add fields, or replace it; templates are starting points, not lock-in.

Layer	Geometry	Starter attributes
Site boundaries / phases	`POLYGON`	`phase_namestart_atfinish_atprincipal_contractorpermit_status`
Work packages	`POLYGON`	`package_reftradescheduled_startscheduled_finishactual_startactual_finishvalue_gbp`
Plant & equipment	`POINT`	`plant_typeasset_tagoperatorlast_inspected_atservice_due_at`
Lay-down / material storage	`POLYGON`	`materialsupplierpo_numberdelivered_atconsumed_at`
H&S incidents / near misses	`POINT`	`incident_typeseverityriddor_reportablereported_atinvestigation_status`
Deliveries	`POINT`	`po_numbersupplierdriver_namegate_in_atgate_out_atvehicle_reg`
Design-vs-built defects	`POINT`	`element_typedeviation_mmtolerance_mmlinked_ifc_guidstatus`

Integrations & data sources

IFC / Revit BIM import
Twin Studio imports IFC, browses element tree, tracks versions across uploads.
Available
Drone vendors via passive ingest (DJI, Skydio, AgEagle, Microdrones)
Post-flight upload of .las / .laz / mesh / orthoimagery; vendors own the live-flight surface.
Available
Flight-plan import (KML / KMZ / Shapefile)
Planned route renders alongside actual capture for coverage reconciliation.
Planned
Cost-value reconciliation export to QS systems
Volumetric + work-package value exports for CVR / IPA workflows.
Planned
Webhook / API into ACC, Procore, Aconex
Two-way ticket and document sync for shops that already run a CDE.
Planned

Regulatory & compliance fit

CDM 2015 (Construction Design and Management)HSE: Principal-contractor evidence (site induction records, permits, incident reports) lives in the audit log against the right work package.
RIDDOR (Reporting of Injuries, Diseases and Dangerous Occurrences)HSE: Near-miss / incident form output bundles the linked feature, attached media, and edit history into a single export.
ISO 19650 BIM information managementISO / BSI: Twin Studio carries IFC version history; design-intent and as-built are reconciled with a defensible audit trail.
NEC4 / JCT contractual reportingNEC / JCT: Weekly progress, volumes, EWNs and CEs export off the live map and dashboard, no slide deck rebuild.

Sample dashboard KPIs

What a Monday-morning view looks like. Every KPI binds to live data in the same tenant; no copy-paste, no overnight ETL.

Volume moved this week (m³)
Schedule slip vs. baseline (days)
Open near-misses > 7 days
Design-vs-built deviations beyond tolerance
Plant utilisation by package
Deliveries received vs. PO committed

Procurement & deployment

Stratumly is contractable per project (single-site licence) or per portfolio (multi-site, multi-tenant). Sovereign deployment in your tenancy is supported on ENTERPRISE tier; principal-contractor data does not leave the customer's environment.

Book a demo for construction See all industries