Direct
1,240
/ ConTrust Suite · Field Intelligence
Project vitals, drawn from the one record every stakeholder agrees on.
We connect to the project's document management system and run forensic analysis across every daily report — inception to date. Actual staffing by trade, mobilization and demobilization signals, and what's slipping, trended over the life of the project and delivered to your phone each morning. Not a fresh data-entry exercise. The record already on file, finally read as intelligence.
/ Sourced from the project's daily reports
/ Integrates with the project Document Management System
/ Daily brief or deep forensic
LIVE · IN YOUR CHAT APP
Project X
Daily Site Report
THU · 26 JUN 2026
On Site Today
Indirect
310
Total
1,550
Direct Labour Trend
7d avg1,200▲ 40
30d avg1,170▲ 70
Manpower Mobilizing
7d avg30d avg
1Subcontractor 1250▲40210▲80
2Subcontractor 2160▲25140▲45
3Subcontractor 3105▲1590▲30
Manpower Demobilizing
7d avg30d avg
1Subcontractor 4150▼40180▼70
2Subcontractor 5105▼25120▼40
3Subcontractor 688▼1895▼25
Equipment On Site
86units today
7d avg
81 ▲5
30d avg
78 ▲8
/ Who it's for
One project record. Every stakeholder's question, answered.
The daily reports sit in your project Document Management System serving one purpose. ConTrust reads them for the question each stakeholder actually needs answered — the same source, a different lens.
Project Owner
Is my project manned to hit the program?
See real staffing across every trade against plan, and catch a trade demobilizing weeks before it shows up in a monthly report — while there's still time to intervene.
Owner's Representative
Are the contractors resourcing as committed?
Monitor mobilization against the baseline for every subcontractor, flag under-staffed trades before they break the sequence, and hold delivery to the record — without chasing anyone for numbers.
Main Contractor
Where is my exposure building?
Track labour expenditure per trade and per subcontractor, spot the slip forming, and hold the contemporaneous record that defends your position before it becomes a dispute.
Delay Analyst
What does the record actually show?
Trended manpower, cost of labour per entity, and daily site conditions — inception to date, contemporaneous, ready for entitlement analysis instead of reconstructed after the fact.
/ The problem
The warning was always in your data. Just never in time.
Every project already collects what it needs to see trouble coming. The daily report just isn't built to read it as early warning — so slip stays invisible until it's expensive.
T+90
You find out too late
The demobilization that started three weeks ago surfaces in a monthly report — after the trade is gone, the sequence is broken, and the recovery cost is already yours to argue over.
buried
The signal is in the data — unread
Manpower draining off a critical trade, actuals diverging from program, a subcontractor quietly winding down. The warning was in your daily reports all along. Nobody had time to read it that way.
→ claim
By the time it's visible, it's a dispute
Slip that goes unseen doesn't stay a scheduling problem. It becomes a variation, an EOT, a claim — argued months later from records that were never built to warn you.
/ How it works
It plugs into what you run today — and starts watching.
01
We read what you already report
No new system, no rollout, no forms for the site to fill. We connect to the reporting you run today and pull the daily site data straight from it. A wide range of systems is supported, with no customization on your side.
Integrates with your existing stack
02
The engine looks for trouble
Every day it computes work done, tracks manpower against program, measures staffing on site, and watches each trade's mobilization trend — flagging what's demobilizing, what's under-staffed, and which trades are turning risky.
Set your thresholds — it alerts you the moment one is crossed
03
The warning reaches you
One clear read lands on your phone: today's site vitals, the trades ramping up and winding down, and where actuals sit against your schedule. High-level, decision-ready, every morning — no dashboard to open.
Delivered to decision-makers, not buried in a portal
/ What it watches
Every read is an early-warning signal.
Each block answers a question that decides whether today's slip becomes next quarter's claim — coloured by performance against your program, not the direction of the change.
Progress against your program
The engine calculates work done each day and sets it against your planned S-curve. The moment time starts outrunning progress, the bars show it — the earliest, cleanest evidence that the project is drifting.
- →
Divergence you can see forming
Not a month-end surprise. A gap that widens in front of you, day by day, while there's still time to act.
- →
Variance in points, not opinions
−7.6% behind program is a number you can raise in a meeting the same morning — backed by the record.
Schedule Health
Time elapsed56.6%
Planned progress61.0%
Actual progress53.4% · −7.6%
Time is ahead of progress → the schedule is burning faster than it's earning. The gap is visible before it becomes a claim.
Mobilization, demobilization & risky trades
The trades ramping up and the trades winding down, ranked by 7-day-versus-30-day swing — and a flag on any trade whose staffing is turning risky. The movement no monthly report catches until the trade has already left.
- →
Demobilization, caught the first week
A trade quietly draining off site is the earliest symptom of a subcontractor in trouble. You see it while it's still recoverable.
- →
Under-staffing, flagged
A critical trade that isn't manning up to meet the program is a slip in the making. The engine surfaces it before the sequence breaks.
Mobilizing
1Subcontractor 1250▲40210▲80
2Subcontractor 2160▲25140▲45
Demobilizing
1Subcontractor 4150▼40180▼70
2Subcontractor 5105▼25120▼40
The record, built as you go
Every daily read is captured — staffing, progress, movement, and the site conditions around them. Weather and traffic logged as documented datasets, timestamped against the day's work. When a claim does come, the evidence was assembled the whole time.
- →
Weather and traffic, on the record
The conditions that drive delay entitlement, captured daily and tied to the day they affected — not reconstructed afterward.
- →
Contemporaneous by default
The strongest claim record is the one built in real time. This one builds itself.
Site Conditions · Logged Daily
WeatherClear · 41°Clogged
Wind18 km/h NWlogged
Access / trafficGate 3 · 25mflagged
Work done today+0.31%vs 0.42
Each day's conditions timestamped against the day's progress — a contemporaneous record, not a hindsight reconstruction.
/ Delivery
The warning reaches the people who can act on it.
Not a dashboard someone has to remember to open. The daily read arrives on the phone — the owner's, the PMC's, the director's — on a channel they already check before the day starts.
the daily headline
Executive read
For owners and directors. A clean, branded card — the site's vital signs seen in seconds, screenshot-ready for the next status meeting.
- High-level, decision-ready
- Drop straight into a report
- Built for the people who decide
the full detail
Working read
For the PMC and commercial team. Every number copyable, searchable, and instant even on site signal — the record they act from.
- Numbers you can lift out
- Searchable back through the job
- Loads on any connection
one payload, two channels
Both
Most projects run both: the headline to leadership, the detail to the team, from the same daily read — no duplication.
- Separate exec + team channels
- One source, no divergence
- Zero extra data entry
Delivered in the messengers your team already uses
Available now
Telegram
Coming soon
Slack
Teams
& more
1
read a day, on every stakeholder's phone
3 wk
earlier a demobilizing trade shows
< 30s
to answer any question across all reports
100%
of data & AI models hosted in KSA
/ Security & your data
Built for data you can't afford to leak.
Project data is commercially sensitive and, for government work, sovereign. ConTrust is engineered around that from the ground up.
Hosted entirely in KSA
Your data and the models that read it run on ConTrust infrastructure inside the Kingdom — processed in the Kingdom, stored in the Kingdom.
AI that runs inside the Kingdom
The models that read your reports run inside ConTrust's own KSA environment — your data is never sent to external frontier models or beyond the Kingdom's borders.
User access management
You decide who sees what — role-based access down to the project, the section, and the individual stakeholder.
A defensible record
Every figure is drawn from the daily reports on file — timestamped and traceable. An audit trail built for entitlement and dispute.
Aligned with the Kingdom's data-protection and construction-sector requirements.
/ Questions
The questions we get first.
Can the team stay informed without logging in?
Yes. Daily briefs with the core data arrive straight in your chat app, and you can ask the AI assistant anything about any report or period — a trade's trend, this month vs last, what's behind program — right in Telegram, Slack, or Teams. No login needed.
Do we have to change how we report?
No. ConTrust reads the daily reports you already produce, in the system you already use. Nothing changes on site.
Where does our data live?
Inside the Kingdom. It runs on ConTrust's own infrastructure in KSA and never leaves it — the AI models run inside ConTrust's own KSA environment, not on external frontier services.
Who can see what?
You control it. Access is role-based, down to the individual project, section, and stakeholder.
See the slip before it costs you.
Point us at one project's reporting and the daily read starts arriving — nothing for your team to change.