ISO 19650-6 is pushing the industry to treat health and safety information as structured project data rather than scattered notes and PDFs. It takes the BIM principles many teams already know and applies them to hazards, controls and residual risks across the lifecycle. The pay-off is better decision-making on design changes, clearer RAMS, and safer interfaces between trades under programme pressure. For UK sites with multiple subcontractors and shifting logistics, the discipline of ISO 19650-6 is less about fancy model views and more about consistent, queryable safety data in the CDE.
What ISO 19650-6 actually asks for on safety information
At its core, ISO 19650-6 expects teams to define what safety information is needed, when, and in what format, then manage that information consistently through the CDE. That means placing structured hazard, risk and control properties on the same modelled elements that drive coordination and quantities, so you can interrogate the data, not just read a note. Residual risks identified by designers, foreseeable risks during construction, and maintenance risks for ops teams all need to be clearly separated, timestamped and attributable. The standard is agnostic about software; the emphasis is on agreed properties, naming and status, with a governance workflow that shows who authored, who reviewed and what changed. Done well, you can filter, group and visualise risks by trade, area or sequence, then tie them to RAMS, permits and temporary works designs.
Turning models into usable safety data in the CDE
Start by expressing safety requirements in your Exchange Information Requirements and appointments. State which model objects must carry risk properties, which codes or classification sets apply, and how residual risks will be flagged through design. In authoring tools, set up templates with property sets for hazard type, consequence, likelihood, control measures, responsible party and status at minimum. Use the CDE to hold model containers, the H&S risk register, RAMS links and 4D sequences, with named states for work-in-progress, shared and published. Give site supervisory staff a viewer they can actually use on a tablet, with saved views that highlight high-risk activities, exclusion zones and live services. As design evolves and temp works change, revision the safety-related properties just as you would geometry, and maintain a clean audit trail back to the author. Finally, integrate the model views into weekly coordination and daily briefings so safety data is live, not an afterthought.
A city-centre crane lift scenario using ISO 19650-6
A main contractor is delivering a CAT A refurbishment in Manchester, replacing roof plant on a twelve-storey office. Programme is tight, neighbours are close, and weekend road closures are limited. The logistics manager builds a 4D sequence for the crane set-up, lift path and demobilisation, linking it to the MEP model where fragile rooflights and parapets are tagged as hazards with residual risk notes from design. The safety manager maps exclusion zones in the site model and tags temporary edge protection as a control that must be in place before the lift status can move to “approved”. The steel subcontractor uploads RAMS to the CDE and links them to the modelled lifting points; the Principal Contractor’s reviewer switches the safety data on in the viewer to check consistency. On the Friday before the lift, a change to the rooftop duct route is pushed to shared; the viewer instantly shows a clash with the crane slew radius and flags the risk property as “uncontrolled”. The team repositions the crane pad by one bay, updates the sequence and republishes; the Saturday lift proceeds without a stop-work order. Post-lift, residual risks are reclassified to “maintained” and handed to the FM team with the rooftop model.
Practical controls that link BIM and site safety
– Name and agree the safety property set at project start, including hazard type, control, status, responsible party and review date.
– Save model views for high-risk trades and sequences, and make them accessible to supervisors and foremen offline.
– Tie RAMS and permits to specific model elements or zones via links in the CDE, not as standalone uploads.
– Use 4D to connect temporary works, plant movements and public interface constraints to risk status.
– Establish a simple coding for residual risks versus construction-phase risks so they are not conflated in reports.
– Include safety data checks in design review and weekly coordination, with a named approver and issue log.
– Keep a modelled logistics layer for hoardings, access, exclusion zones and emergency routes to avoid rework.
Common mistakes with ISO 19650-6 safety data
# Treating hazards as free-text without structure
/> Unstructured notes cannot be queried, sorted by area or filtered by trade, and they break as soon as the geometry changes.
# Keeping safety registers outside the CDE
/> When the risk register lives in a separate spreadsheet with its own versioning, links to model elements go stale and auditability evaporates.
# Blurring residual design risks with construction risks
/> Designers’ residual risks should inform, not overwrite, the Principal Contractor’s construction risk assessment; keep fields distinct with clear ownership.
# Ignoring sequence and temporary works
/> Static risk tags miss the point: 4D sequencing and temp works models are essential to control dynamic hazards like crane operations and façade access.
How it works on real sites: roles and interfaces
The Principal Designer needs a clear path to capture residual risks within the design coordination model, using agreed tags and status codes. The Principal Contractor then layers in construction-phase risks, temporary works, plant and access routes, maintaining author responsibility and dates so accountability is visible. Subcontractors should contribute RAMS mapped to model elements or zones they control, and the CDE should prevent publishing until mandatory fields are complete. Site management uses the viewer in daily briefings, switching on the “safety” layer alongside clashes to show crews exactly what is live that day. When a change request hits geometry or sequence, the safety data rides along through the same workflow, so nobody is relying on stale PDFs in a folder.
Minimum data to capture per risk item
– Hazard category and source (e.g., live services, fragile surface, working at height)
– Affected model element or zone with unique ID and location reference
– Control measure required and verification evidence needed
– Responsible role and current status (proposed, accepted, implemented, verified)
– Linked RAMS or permit ID, with revision and approval date
– Planned sequence step or milestone dependency
– Residual risk outcome for handover to operations
One-week rollout checklist for ISO 19650-6 safety data
# Nominate a single high-risk operation to pilot structured safety properties on the model this week.
/> Choose something visible and time-bound, such as a mobile crane pick or a basement excavation phase.
# Configure and test the safety property set on 10–20 representative elements.
/> Include hazard, control, status, responsible party and a link to a live RAMS in the CDE.
# Build one 4D view that ties the operation to temporary works and exclusion zones.
/> Use it in a coordination meeting and capture feedback from supervisors on clarity.
# Publish a viewer playlist with three saved safety views for the pilot area.
/> Distribute to site leads and run a toolbox talk using only the viewer, not drawings.
# Close the loop with a short retrospective and adjust naming, fields and workflow.
/> Record what changed, who approves, and how updates move from work-in-progress to shared.
What to watch next in the UK market
UK clients and insurers are starting to push for demonstrable digital control over high-risk activities, not just better PDFs. As Building Safety regime expectations ripple into procurement, expect appointments to reference ISO 19650-6 deliverables such as queryable hazard registers, 4D-linked RAMS and clean handover data. Look for public sector clients to start asking for ISO 19650-6-aligned hazard registers and 4D method statements as standard deliverables. The contractors who can evidence clean, queryable safety data across design and delivery will set the benchmark when tender scoring shifts towards digital risk control.
