Case study · ConstructIQ Technologies
A Victorian builder's OHS obligations — inductions, SWMS, incidents, site diary, toolbox talks — moved out of folders and glovebox paper into one live system.
A builder's safety obligations live in folders, spreadsheets and the glovebox. When WorkSafe asks, the evidence is scattered across four people's habits. Small builders can't afford enterprise safety platforms, and don't use them when they try, because those platforms weren't designed at a site gate on one bar of signal.
The product is built through ConstructIQ Technologies Pty Ltd. I am the sole developer — architecture, code, database, security, deployment and production operations. My partner in the product, David Caruana of Arlington Homes (registered building practitioner CDB-U 50292, 30+ years building in Melbourne), is the construction-industry expert: he directs requirements from his live sites and reviews every screen against how a real job actually runs. His feedback lands in the commit log and ships within days.
Digital worker inductions with a safety quiz, an A–Z Safe Work Method Statement library covering 75+ trades, incident and near-miss reporting with automatic LTIFR calculation, a daily site diary that feeds safety statistics, toolbox meetings with attendance sign-off, QR site check-in, and a mobile portal where every tradie signs their own inductions and SWMS, with no paperwork chasing.
Truthful compliance. Most safety software shows green ticks that mean nothing. Here, no compliance status is displayed unless a database-verifiable artifact sits behind it — "submitted" and "verified" are different states, and nothing defaults to 100%.
The site gate. Users are tradies on a phone with one bar of signal, so the app is an offline-capable PWA — and branded PDF generation happens entirely client-side, with the heavy PDF libraries lazy-loaded so a tradie opening an induction never downloads them.
Security that survives a hostile look. Role-based access control is enforced in the database itself, not in the JavaScript — tenancy hardening, database-enforced roles, evidence-backed status and audit separation are each their own reviewed migration.
Live, in pilot on Arlington Homes' active Melbourne sites. The iteration loop is real and recent: partner feedback from late August — truthful compliance states, toolbox lifecycle, diary voice notes, policy PDFs, incident notifications — was shipped within days, and a recorded production cleanup purged empty organisations so platform numbers reflect real tenants only.
I can take a regulated, liability-sensitive domain, sit with a non-technical industry expert, and turn how his business actually runs into secure, audited, multi-tenant production software — solo, end to end.