The three things every builder wants tracked - and why they sit in different systems
Construction execution comes down to three recurring questions. Is the project actually moving the way the tracker says it is? Is the realised cost staying within the BoQ? Is contractor performance worth the relationship? The data exists to answer all three. It just lives in different systems that update on different cadences.
THREE QUESTIONS, FIVE DATA SOURCES
- Progress (planned vs actual). Construction tracker (MS Project, Asana, ClickUp, custom) holds the milestone plan. Site supervisor WhatsApp photos and notes hold the physical reality. The gap between the two is the slippage nobody surfaced.
- Cost (BoQ vs realised). BoQ in Excel holds the baseline. RA bill submissions hold the realised cost per activity per contractor. Tally per SPV books it after invoice processing. None alone shows the trend; together they do.
- Contractor performance. Per-project notes about which contractor is consistently late, over-billing, or producing rework. Almost never aggregated across projects to surface patterns.
How AI joins the five sources to answer each question
THE READ + JOIN MODEL
- Progress tracking: tracker + WhatsApp photos + RA bills. AI joins the tracker-reported progress with the actual progress derived from supervisor photo metadata (date, location, activity tagged in the message) and the RA bill claims. The variance between tracker-reported and actual-reported progress surfaces per project per week.
- Cost tracking: BoQ + RA bills + Tally. AI matches each RA bill line back to the BoQ line item, computes the realised-cost-per-unit, and compares against the BoQ rate. Any line where realised cost has drifted more than the threshold surfaces with the cumulative value impact.
- Contractor performance: tracker + RA bills + supervisor escalations. AI aggregates per-activity slip rates per contractor across every active project, plus the supervisor escalation language from WhatsApp threads. Patterns that no single project view would expose - contractor X is late on plastering across three projects, contractor Y is over-billing on civil work everywhere.
5 sources
Joined per project
BoQ + tracker + RA bills + Tally per SPV + WhatsApp
Daily digest
Per-project view
Per project: progress, cost, billing, escalations
Read-only
By default
Auto-replies to contractors / customers opt-in per rule
What an AI construction-tracking digest actually shows
Concrete shape - what the daily 8:30 pm digest looks like for a builder with 4 active projects, 18 active contractors, and 320 units across the portfolio.
A REAL BUILDER DIGEST
- Progress: 4 projects today, 2 on plan, 2 slipping. Tower A at 51% actual (tracker says 62%). Tower B on plan. Tower C on plan. Tower D at 38% actual (tracker says 47%). The 11-point and 9-point gaps surface with the activities driving each.
- Cost: 3 BoQ lines drifted above budget this week. Civil work at Tower A running 7.7% above BoQ (steel-rate change). MEP at Tower D running 5.2% above (vendor surcharge). Plumbing at Tower C running 4.1% above (rework). Total value impact ₹18.4 lakh this week.
- Billing: 2 customer milestones at risk in next 60 days. Tower A milestone #5 (structural completion certificate, ₹3.2 crore trigger) at risk - structural work 18 days behind. Tower D milestone #3 (slab completion, ₹1.8 crore trigger) at risk - 11 days behind.
- Contractors: 3 contractors flagged on slip pattern. Contractor X slip rate 28% on plastering across Tower A and Tower C. Contractor Y over-billing pattern flagged (5 RA bills above BoQ rate this quarter). Contractor Z site supervisor escalations spiking - 4 mentions of quality issues this week.
Manual tracking vs AI tracking - side by side
| Tracking task | Manual today | AI-tracked (KolossusAI) |
|---|---|---|
| Tracker vs actual progress gap | Discovered at monthly review | Surfaced daily with activity-level breakdown |
| BoQ vs realised cost variance | Quarterly reconciliation, often at project close | Per-line variance flagged within the week the RA bill processes |
| Customer billing milestone risk | Found when customer asks why invoice is late | Flagged 30-60 days ahead of slip |
| Contractor slip-rate per activity | Per-project anecdote | Cross-project pattern detection |
| Contractor over-billing pattern | Caught manually during RA bill review | Flagged across all active projects automatically |
| Site escalations reaching leadership | Buried in WhatsApp scroll | Categorised, surfaced in daily digest |
| Multi-project view for owner | Per-project review per week, no joined view | One owner digest covers every project, every contractor |
What this does NOT do (honest limits)
OUT OF SCOPE
- Not a construction management replacement. MS Project, Asana, ClickUp, your custom tracker, and your RA bill workflow stay. We read them in place.
- Cannot validate physical quality of work. Site visits are still the only way to confirm execution quality. The AI flags slips, cost drift, and patterns; the inspection stays human.
- Not a contractor replacement engine. AI surfaces the slip-rate pattern with data. The decision to renegotiate, replace, or coach the contractor stays with the project head.
- Auto-messages to contractors are opt-in. By default, KolossusAI is read-only on WhatsApp. Reminders or escalation messages to contractors are workflow rules you turn on with the trigger logic you approve.
How KolossusAI fits without replacing your tracker or Tally
KolossusAI is the AI analytics layer for real estate and construction. AI Analytics for Real Estate Developers is the deployment shape - it reads each source in place and surfaces the cross-system view daily.
WHAT KOLOSSUSAI READS FOR CONSTRUCTION TRACKING
- BoQ baseline. Excel (most common) or vendor BoQ tools - picked up from a shared folder. Used as the cost reference for variance detection.
- Construction tracker. MS Project, Primavera, Asana, ClickUp, Notion, custom tracker - via DB or API. Milestone plan, activity sequence, assigned contractors.
- RA bill workflow. Email submissions, shared-drive uploads, or vendor-portal records. Parsed for line items, quantities, rates, contractor reference. Matched against the BoQ baseline.
- Tally per SPV. Native connector. Booked costs, vendor payments, customer collections, multi-company consolidation by default.
- Site supervisor WhatsApp. Via Business API, read-only by default. Photos parsed for date and location; text parsed for activity status, escalations, weather impact.
The honest summary
Yes - AI can track construction progress, costs, and contractor performance by joining the five systems your project data actually lives across. The team keeps using each tool as they do today; the AI layer reads them and surfaces the cross-system view in one daily digest - per project, per contractor, per customer milestone. AI Analytics for Real Estate Developers - free 14-day POC on your real stack. The first BoQ overrun or contractor slip pattern usually surfaces on the kickoff call.