The problem
A developer of private residential plans in Riyadh supervises dozens of projects at once, each with a different owner, design consultant, supervising consultant, contractor and municipality engineer. Progress arrived as the contractor’s weekly WhatsApp message and a monthly PDF nobody could search. Management could not say which projects were behind, because the only number tracked was one overall percentage that hid the item that had not started. Contract dates were Hijri on paper and Gregorian in Excel, so handover deadlines were routinely miscalculated.
What we built
Every project carries its six parties, its price, type, status, duration, site-handover and final-handover dates, and a map location. Dates are entered and shown in the Umm al-Qura Hijri calendar and stored in Gregorian, which is what ended the deadline arithmetic errors.
The timeline is where the real answer lives. A project breaks into milestones such as consultant selection, design approval, site handover and execution, and each milestone breaks into work steps that carry their own percentage, date and note. Planned versus actual shows per item, not as one comforting average.
Inside the system
- Teams organised by job title for the developer, the contractor and the consultant, assigned per project.
- Periodic PDF reports and project documents stored per project with download tracking.
- Dashboard for total, ongoing, completed and delayed projects, with monthly activity analysis.
- 21 permissions across projects, reports, users, roles and audit, with an exportable audit log.
- A JWT REST API so field teams can feed progress from their phones.
Screens
