CASE STUDY / REAL ESTATE & INFRASTRUCTURE CONSTRUCTION

Unsafe condition reporting becamereal-time across multi-project sites

A large construction organisation replaced supervisor-dependent reporting and manual CAPA tracking with mobile-first capture, contractor qualification workflows, and escalation-backed action closure, so risks surfaced earlier and leadership finally had cross-project visibility.

Download PDF case study

Client highlights

  • 01
    Modules

    Safety Reporting, Contractor Safety, CAPA / Action Tracker, Dashboards

  • 02
    Use case

    Cross-project risk visibility and contractor governance

  • 03
    Outcome

    Higher reporting volume, faster reporting, fewer overdue actions

Site engineer reporting an unsafe condition from a project site
Overdue actions−44%
Unsafe condition reports+63%
6 min read
Multi-projectHigh subcontractor intensity

Measured outcomes

The shift from supervisor-dependent reporting to connected, cross-project risk visibility.

63%

More reporting

Increase in unsafe condition reporting.

What enabled itLow-friction mobile capture and guided templates

48%

Faster reporting

Reduction in incident reporting delay.

What enabled itOn-site submission and instant routing

44%

Fewer overdue actions

Reduction in overdue corrective actions.

What enabled itDue dates, escalations and owner tracking

37%

Contractor governance

Improvement in contractor safety compliance scores.

What enabled itPre-qualification scoring and performance tracking

WORKFLOW AT A GLANCE

From a site report to a closed action, on every project.

01

Trigger

Worker or supervisor reports an unsafe condition on mobile with location and evidence.

Explore this solution
05

Visibility

Dashboards show project-wise risk hotspots, overdue actions, repeats and contractor performance.

Explore this solution

The challenge

What leadership could not see across a portfolio of active projects.

01

Visibility gaps

Leadership couldn’t see risk patterns across projects in real time.

02

Underreporting

Unsafe conditions depended on supervisor reporting, so issues stayed invisible.

03

Contractor friction

Qualification checks were slow and inconsistent across sites.

04

Closure discipline

Actions slipped because tracking lived in manual registers and spreadsheets.

What we implemented

Deploying a standardised, integrated safety environment across all active operational sites.

Unsafe condition capture view with evidence and routing

Field Safety Reporting

Configured for real-time capture by workers and supervisors across sites.

Key workflow controls

  • Guided unsafe condition templates covering category, location or zone, and severity
  • Photo and voice evidence capture at source
  • Auto-routing to the responsible owner: area, contractor or trade

Audit proof captured

  • Time-stamped record history
  • Evidence attached inside the record
Explore
Cross-project dashboard showing overdues, repeats and contractor scorecards

Contractors + CAPA Engine

Configured for predictable closure and contractor governance across projects.

Key workflow controls

  • Contractor pre-qualification scoring and document checks
  • Performance tracking by contractor and project
  • Action tracker with due dates and reminders

Audit proof captured

  • Clear ownership, due dates and an escalation trail
  • Export-ready action packs in PDF and Excel
Explore

Governance and proof, inside the record

Less chasing. More traceability.

Role-based access control

Fine-grained permissions by site, role or module.

Immutable audit trail

Full history of all data changes and access.

PDF and Excel exports

One-click audit pack exports for regulators.

Offline field capture

Capture keeps working in basements and low-signal zones, then syncs when the device reconnects.

See how the evidence adds up

Executive summary

What the safety team started with, what changed, and what improved.

The problem
  • Unsafe condition reporting relied on supervisors
  • Contractor qualification was document-heavy
  • Central leadership lacked cross-project risk visibility
What changed
  • Mobile-first reporting for workers and supervisors
  • Digitised contractor pre-qualification and tracking
  • Executive dashboards for project-wise performance
What improved
  • 63% increase in unsafe condition reporting
  • 48% reduction in incident reporting delay
  • 37% improvement in contractor safety compliance scores

Context & constraints

Number of sites
Multiple active projects
Contractor intensity
High
SOP alignment
Strict requirement
Offline mode
Enabled for basements

Ready to standardise your safety workflows?

Get the one-pager summary, or request a security brief for your IT review.

PDF case study

Before you ask IT or procurement…

Most teams ask these questions before rolling out OQSHA.

Typically 2–6 weeks, depending on the number of sites, the modules you enable (Permit to Work, Inspections, Safety Alerts, HIRA, Visitor Management), and how much historical data you're bringing over. Most customers start with a pilot site, then roll out site by site.

Nothing special. Field teams use the OQSHA mobile app on Android or iOS phones and tablets; admins and managers use the web portal in any modern browser.

Yes. OQSHA is built for sites where connectivity is patchy: basements, towers under construction, plant floors. Field users can raise permits, safety alerts and inspections with no signal, including photos and attachments. Everything syncs automatically once the device reconnects.

Data is encrypted in transit and at rest, hosted on AWS in your chosen region. For organizations that need full control, OQSHA can also be deployed on-premise within your own infrastructure.

No. OQO runs as a captive AI. It works on your safety data within the OQSHA environment and never sends it to a public model or the open internet.

Yes. We support Single Sign-On and integration with common HRIS, ERP, and directory systems. Custom integrations are scoped with our implementation team during onboarding.

Yes. Historical permits, inspections, and incident records can be imported during onboarding, usually alongside the pilot, so your analytics and audit history are complete from day one.

Yes. Each organization runs in its own isolated tenant. Your templates, records, users, and dashboards are never visible to or shared with any other customer.

Built-in dashboards across permits, incidents, and inspections, filterable by site, zone, and time period. They're scoped automatically to what each user is allowed to see.

A named implementation contact through rollout, then standard support with response-time SLAs based on your plan. App updates are delivered over the air, so field users always have the latest version without reinstalling.

SAFER OPERATIONS START WITH A CONVERSATION

See what connected safety looks like.

Your workflows. Your sites. A tailored OQSHA walkthrough.

OQO welcomes you to explore OQSHA