Subcontractor compliance
Insurances, licences and SWMS tracked, with reminders sent before anything expires.
For builders and construction companies
We pull safety, quality, program, cost and contract data out of the tools your sites already use, and turn it into one live view. Green, amber or red, with the reason behind every colour.
Portfolio health
Five live projects, six pillars| Project | Safety | Quality | Time | Cost | Risk | Contracts | Overall | Why |
|---|---|---|---|---|---|---|---|---|
| Harbourside ResidencesMixed use · 64 units | ✓ | ✓ | 1 | ✓ | ✓ | ✓ | Watch | Level 6 pour 3 days behind program |
| Eastgate Logistics HubIndustrial · 18,000 m² | 2 | ✓ | ✓ | 1 | ✓ | ✓ | Watch | 2 permits overdue; steel up 5% on budget |
| St Clare College, Stage 3Education · refurbishment | ✓ | 3 | 2 | ✓ | ✓ | 1 | Act now | 17 defects past due; 4 variations unsigned |
| Parkview Medical CentreHealth · fit-out | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | On track | All measures inside your thresholds |
| Bayline TownhousesResidential · 12 dwellings | 2 | ✓ | ✓ | 1 | 1 | ✓ | Act now | Incident logged; 3 insurances expire in 14 days |
A tick means every measure in that pillar is inside your thresholds. A number shows how many need attention, coloured by the worst of them.
What's about to go wrong
What already happened
Project drill-down
Every pillar breaks down into the measures behind it, each checked against your thresholds. The red isn't a feeling, it's 17 defects past their due date.
St Clare College, Stage 3
Act now: 1 pillar red, 2 on watch600
All inspections on schedule
312
17 defects past due date
420
Stage 3 handover 6 days at risk
600
Cost to complete within 2%
300
No new high risks this week
210
4 variations awaiting sign-off
Trend analysis · construction
Lead and lag
Lagging indicators like open defects tell you what has already happened. Leading indicators like overdue inspections tell you what's about to. Tracked week by week, the trend shows whether a project is recovering before the next client meeting.
Every number links back to the record in the system it came from, so the conversation is about fixing it, not arguing about it.
Where it comes from
Your supervisors keep using the tools they use now. We read from those systems overnight and through the day, and the colours update on their own. Nobody fills in a report to feed it.
Then the admin behind it
Insurances, licences and SWMS tracked, with reminders sent before anything expires.
Invoices read from the inbox, matched to the PO and job, and entered. Only the odd ones reach a person.
Claims drafted from the numbers already in your systems. Variations logged and chased until approved.
Progress, photos and next steps for each client, written from the site diary and sent on schedule.
Proof on your own data
We connect to the systems on one of your current jobs and build its health view for real. You see your own project in green, amber and red before you decide anything else.
No. The view reads from the systems they already fill in. If a number is wrong on the dashboard, it's wrong at the source, and the dashboard shows you where.
You do. We start with sensible defaults for each measure and tune them with your project managers during the proof.
Only if you want them to. Most builders keep the full view internal and send clients a weekly summary built from it.
That's exactly what the proof finds out. Most do. Where one doesn't, we use scheduled exports or a simple form, and we tell you before you commit.
A 30-minute walkthrough of the project health view, then a straight answer on whether it fits your systems.