Mitmar
Construction project controls: schedule, cost, site and payments on one platform
-
At a glance
Sector
Construction
Platforms
Web · iOS · Android
Modules
9
Integrations
8
Screens
4
Total duration
23 weeks
Mitmar ties the schedule and bill of quantities to what is actually happening on site: engineers file daily reports from their phones, and AI estimates progress from photos and flags slippage before it compounds. Earned value is calculated automatically, subcontractor certificates, RFIs, submittals and Balady permits run from one platform, and owners receive a monthly report drafted by AI.

-
Challenge
-
01
Progress is estimated by eye and collected in scattered Excel files, so slippage only shows up in the monthly report, when it is too late.
-
02
Daily reports live on paper or in WhatsApp groups, so evidence for delays and claims is lost when it is needed.
-
03
Subcontractor certificates are checked by hand against the BOQ, so payments run late and retention is calculated inconsistently.
-
04
RFIs and submittals move between email and paper copies, and work is sometimes built from an outdated drawing revision.
Who it is built for
-
Site engineer
A daily report in minutes from the phone, with photos, manpower and equipment
-
Planning & controls engineer
Planned versus actual and earned-value indices without manual consolidation
-
Project manager
Early sight of critical delays and cost by package
-
Quantity surveyor
Certificates matched to the BOQ, with retention and recoveries calculated automatically
-
Owner & consultant
A monthly report backed by photos and clear indices, with electronic approvals
-
Modules
What the system does
Connected modules working on one set of data.
-
01
WBS & schedule
Imports Primavera P6 and MS Project schedules and compares baseline with actual
-
02
Daily site report
Manpower, equipment, weather, photos and delays from the phone, even offline
-
03
Photo progress
Progress per activity estimated from site photos, plus drone flight comparison
-
04
BOQ & earned value
Cost per item and package, with CPI and SPI
-
05
Subcontractor certificates
Executed quantities against the BOQ, with retention, advance recovery and deductions
-
06
Documents, RFIs & submittals
RFIs, submittals and drawings with revisions; the site sees only the current revision
-
07
Safety & permits-to-work
Incidents and observations, plus hot-work, work-at-height and confined-space permits
-
08
Balady permits
Tracks the building permit, renewals and completion certificate, with alerts before expiry
-
09
Owner portal
Progress, cost, certificates and an AI-drafted monthly report
Where the AI works
-
AI · 01
A computer-vision model recognises site elements in photos, such as rebar, formwork, poured concrete, blockwork and finishes, estimates progress per activity, compares it with what the engineer entered and flags the gaps.
-
AI · 02
Drone imagery from two flights is turned into surface models to estimate cut and fill volumes and structural progress.
-
AI · 03
A delay model reads the schedule, the critical path and daily reports, such as labour shortages, idle equipment and weather, and identifies activities likely to slip weeks ahead.
-
AI · 04
A private in-Kingdom language model drafts the monthly owner report in Arabic and English from project data, and summarises open RFIs and their threads.
-
Screens
The system as the client's team and customers use it.



-
Architecture
Independent services, in-Kingdom data, and integrations over documented APIs.
Channels
- Project web app: Controls, BOQ & certificates
- Site app: Flutter · offline-first
- Owner portal: Reports & approvals
- Drone uploads: Survey & 360° imagery
Edge
- API gateway: WAF & rate limits
- Identity: Nafath & project roles
Services
- Schedule service: WBS & baselines
- Field service: Daily reports & safety
- Cost & EVM service: BOQ & earned value
- Certificates service: Certificates & retention
- Document control: Drawings, RFIs & permits
AI
- Progress vision: Progress from photos
- Delay forecasting: Slippage prediction
- Report writer: In-Kingdom LLM
Data
- PostgreSQL: System of record
- Object storage: Photos & drawings, in-Kingdom
- OpenSearch: Document search
Integrations
- Balady: Building permits
- Primavera P6: Schedules & baselines
- ERP: Costs & payments
- Etimad: Government project claims
Connections
- Project web app to API gateway
- Site app to API gateway
- Owner portal to API gateway
- Drone uploads to API gateway: upload
- Owner portal to Identity: Nafath
- API gateway to Schedule service: REST
- API gateway to Field service
- API gateway to Cost & EVM service
- API gateway to Certificates service
- API gateway to Document control
- Field service to Progress vision
- Field service to Delay forecasting
- Schedule service to Delay forecasting
- Schedule service to Report writer
- Schedule service to PostgreSQL
- Cost & EVM service to PostgreSQL
- Certificates service to PostgreSQL
- Field service to Object storage
- Document control to Object storage
- Document control to OpenSearch
- Document control to Balady
- Schedule service to Primavera P6: XER
- Cost & EVM service to ERP
- Certificates service to Etimad
Stack
- Next.js
- NestJS
- Flutter
- PostgreSQL
- Temporal
- Python · PyTorch
- OpenSearch
- Kubernetes
-
Workflow
From site to certificate and monthly report
-
01
Approve the baseline
Planning engineerPrimavera P6 · Schedule service
-
02
Daily site report
Site engineerSite app
-
03
Progress from photos
AutomaticProgress vision
-
04
Update planned vs actual & earned value
Automatic, then plannerCost & EVM service
-
05
Early delay warning
AutomaticDelay forecasting
-
06
Subcontractor submits certificate
SubcontractorCertificates service
-
07
Verify quantities & approve
QS & project managerCertificates · ERP · Nafath
-
08
Monthly owner report
AI, then project managerReport writer · Owner portal
-
Data & API
The core entities and relations, and a live example from the API.
Project
- iduuidPK
- codetextunique
- owner_iduuidFK
- contract_valuenumeric
- start_datedate
- finish_datedate
- balady_permittext
- statusenum
Activity
- iduuidPK
- project_iduuidFK
- wbs_codetext
- nametext
- baseline_startdate
- baseline_finishdate
- planned_pctreal
- actual_pctreal
- is_criticalboolean
DailyReport
- iduuidPK
- project_iduuidFK
- report_datedate
- manpowerjsonb
- equipmentjsonb
- weatherjsonb
- delaysjsonb
- submitted_byuuidFK
SitePhoto
- iduuidPK
- report_iduuidFK
- activity_iduuidFK
- storage_keytext
- sourceenum(phone,
drone, 360) - ai_progressreal
- confidencereal
- taken_attimestamptz
BoqItem
- iduuidPK
- project_iduuidFK
- codetext
- descriptiontext
- unittext
- qtynumeric
- ratenumeric
- packagetext
Certificate
- iduuidPK
- subcontractor_iduuidFK
- numbersmallint
- perioddaterange
- grossnumeric
- retentionnumeric
- advance_recoverynumeric
- netnumeric
- statusenum
CertificateLine
- iduuidPK
- certificate_iduuidFK
- boq_item_iduuidFK
- prev_qtynumeric
- this_qtynumeric
- amountnumeric
- verifiedenum(match,
variance, pending)
Document
- iduuidPK
- project_iduuidFK
- typeenum(drawing,
rfi, submittal, permit) - numbertext
- revisiontext
- statusenum
- superseded_byuuidFK
- Project 1—∞ Activity
- Project 1—∞ DailyReport
- DailyReport 1—∞ SitePhoto
- Activity 1—∞ SitePhoto
- Project 1—∞ BoqItem
- Certificate 1—∞ CertificateLine
- BoqItem 1—∞ CertificateLine
- Project 1—∞ Document
/v1/daily-reports
Submit a daily site report
Request
{
"project": "PRJ-2417",
"date": "2026-11-08",
"zone": "tower-b",
"manpower": { "workers": 186, "engineers": 12 },
"equipment": [
{ "type": "tower_crane", "count": 2, "state": "working" },
{ "type": "concrete_pump", "count": 1, "state": "working" },
{ "type": "excavator", "count": 1, "state": "idle", "reason": "spare_part" }
],
"progress": [{ "activity": "B-STR-L09-SLAB", "reported_pct": 55 }],
"photos": ["ph_3e91", "ph_3e92", "ph_3e93"],
"delays": [{ "cause": "labour_shortage", "trade": "rebar", "impact_days": 2 }]
}
Response
{
"id": "dr_01JE2K7QW4N",
"number": 412,
"status": "submitted",
"weather": { "temp_c": 29, "wind_kmh": 18, "source": "auto" },
"ai_progress": [
{
"activity": "B-STR-L09-SLAB",
"reported_pct": 55,
"estimated_pct": 41,
"confidence": 0.91,
"flag": "variance"
}
],
"critical_path_impact_days": 2
}
Webhook event · activity.slippage_detected
{
"event": "activity.slippage_detected",
"project": "PRJ-2417",
"activity": "B-STR-L09-SLAB",
"planned_pct": 62,
"actual_pct": 41,
"slip_days": 12,
"on_critical_path": true,
"at": "2026-11-08T18:05:00+03:00"
}
-
Integrations
-
Balady
Building permits, renewals and completion certificates
-
Etimad
Payment-certificate data for government projects
-
Nafath
Owner and consultant sign-in and certificate approvals
-
Primavera P6 · MS Project
Schedules, baselines and progress updates
-
ERP (SAP · Oracle)
Purchase orders, actual costs and payments
-
Drone imagery
Aerial survey photos and surface models
-
BIM (IFC)
Links activities to 3D model elements
-
Weather service
Site weather filled into daily reports
-
Security & compliance
- Data, photos, drawings and backups hosted inside the Kingdom.
- National Cybersecurity Authority Essential Cybersecurity Controls (ECC).
- Personal Data Protection Law (PDPL) alignment, with faces blurred in site photos before they are shared with the owner.
- Project- and package-level permissions, so a subcontractor sees only its own items and certificates.
- Certificate approvals signed through Nafath under maker-checker.
- Undeletable revisions for drawings and correspondence, with a full audit trail of every change.
- Encryption in transit and at rest, with a timestamp and geotag on every site photo.
-
Delivery plan
Clear phases with measurable deliverables.
-
01
Discovery & controls mapping
- Workshops with planning, QS, site and the owner
- Review of current report and certificate templates
2 weeks -
02
UX & architecture
- Site app and dashboard prototypes tested with engineers
- Data model and WBS design
3 weeks -
03
MVP build
- Schedule, daily reports and earned value
- Certificates, retention and the owner portal
8 weeks -
04
Integrations
- Primavera P6, ERP, Balady, Etimad and Nafath
- Drone imagery and BIM import
4 weeks -
05
Vision training & pilot
- Train the progress model on photos from the company’s own projects
- Pilot on one project in parallel with the current method
4 weeks -
06
Go-live & hypercare
- Phased rollout project by project
2 weeks
- Total duration
- 23 weeks
- Team
- Project manager, business analyst with project-controls experience, 3 backend and frontend engineers, a mobile engineer, a computer-vision engineer, QA and DevOps.
Performance
- < 10 min A complete daily report from the phone
- ± 5% Photo-based progress versus field measurement
- < 5 days Subcontractor certificate from submission to approval
- 99.9% Availability
