Picture a specialist subcontractor arriving on a large construction site. A rope access qualified tiler is brought in for a bespoke facade installation that some ambitious architect specified. They’re on site for a few days, possibly a week. They are doing physically demanding, high-risk work. And they almost certainly have less access to project intelligence than anyone else on site.
This is one of the more persistent structural problems in construction safety, and it rarely gets the attention it deserves. The workers who are most exposed to risk on a construction project are often the least connected to the information that could help them understand and manage that risk.
Who has the data versus who needs it
On most construction projects, the client or the tier one contractor holds the data. They run the scheduling platform, the document management system, the BIM environment, and the safety management software. Their project managers and engineers have access to weather forecasts, programme updates, coordination schedules, and whatever risk intelligence the project generates. Their safety team can see incident trends, hazard registers and inspection results.
The subcontractor hanging off a rope on the side of the building typically doesn’t have access to any of that. They are working from a loose scope of works, a paper-based SWMS, and whatever their supervisor told them at the start of the shift. If the schedule changed overnight, if another trade is now working directly below them, if the wind forecast has shifted since the morning briefing, they may not find out until well after the dynamic risk presents itself.
This is not a technology problem in the traditional sense. The data exists. The platforms exist. The intelligence could, in theory, be made available. The issue is mostly structural. Construction operates on a layered subcontracting model where the people who fund and control the technology ecosystem are not the same people who are most exposed to the consequences of poor information flow.
The technology access problem runs deeper than software
It is tempting to frame this as a simple procurement issue. Give the subbies access to the platform. But anyone who has worked on a construction site knows it is more complicated than that.
Let’s start with devices. Most subcontractors are bringing their own phones to site. They are not enrolled in the head contractor’s mobile device management platform. On some projects, particularly in defence or critical infrastructure, personal devices are restricted or prohibited entirely for cybersecurity reasons. On others, mobile phones are banned outright on the grounds that they are a distraction. We are simultaneously trying to deliver safety intelligence through a device that some sites will not let workers use, not to mention internet connectivity – which is often not thought about.
Then there is the interface itself. Even where access is technically possible, the systems were designed for project managers and engineers, not for a tradesperson trying to get oriented at 6:30 in the morning. The user experience gap is significant. A worker who moves between projects every few weeks encounters a different platform, a different login, a different way of finding what they need to know. On one site, everything is clear. On the next, they are lost.
And beneath all of this sits the reality of the margins that every layer of the construction ecosystem is dealing with. Construction is a low-margin industry. Investing in the user experience and technology access for workers who are not on your payroll, who are employed by a subcontractor three tiers down the contractual chain, is a hard business case to make. So, it doesn’t get made. The workers who literally need the information the most are the last line item in anyone’s technology spend.
What good practice probably looks like (for now)
Some sites are finding ways around this. The most effective approaches tend to be low-tech in presentation, even if the underlying data aggregation is sophisticated.
Visual planning boards in common areas, where workers can walk past and see the day’s programme, coordination clashes, weather updates, and active hazard zones. Morning briefings that go beyond reading a pre-written script and genuinely surface the dynamic risks for the day. Physical dashboards are placed where people congregate, showing aggregated project intelligence in a format that does not require a login or a company email address.
The common thread is designing the feedback loop around the people who need it, not around the platform that generates it. The question is not “how do we get workers onto our system?” but “how do we get the right intelligence to workers in a format they can actually use, in the places they need it most?”
That is a fundamentally different design problem. And it requires safety teams, IT teams, and project teams to think jointly about how operational technology is delivered to a workforce that is largely transient, multi-employer, and not enrolled in your corporate systems.
A question of design intent
This conversation came up recently during an interview with Cam Stevens from PKG and Owen Drury, Co-Founder of Bricks and Bytes, a UK-based media company focused on technology in construction. They are putting together a report on the state of safety technology in the sector, and one of the threads we explored was this gap between who generates safety-relevant data and who needs it at the point of work.
At PKG Safety Innovation, we describe this as a work design problem. If safety is an outcome of well-designed work, then the information architecture of a construction project is part of that design. How intelligence flows from a scheduling platform to a rope access crew is as much a safety consideration as the anchor points they are clipping into.
Corporate IT teams in construction companies typically design technology ecosystems for their own employees. That makes sense from an enterprise architecture perspective. But from a work design perspective, it leaves a gap where the risk is highest. The subcontractor workforce is not an edge case. On most large projects, subcontractors make up the majority of the people on site. Designing information systems that structurally exclude the majority of the workforce is a design failure, even if it is an understandable one.
Better Work, By Design™ means asking who does the work, what they need to know, and how we get that information to them; in the right format at the right time. If the answer to this question is “we can’t, because they’re not in our system,” then the system needs redesigning.
PKG Safety Innovation helps organisations rethink how safety data, technology, and intelligence flow to the people who need it. Most engagements start with a discovery conversation. Get in touch at pocketknifegroup.com/contact
