From the field
to the مستخلص.
A walkthrough of Mutamad for project managers — how the management view of every villa, every claim, every signature comes together without typing.
One project, five gates.
Before any document can flow, the project is configured once: Config · Inventory · Team · Workflow · Breakdown. The setup wizard walks the owner through each gate. Once all five turn green, the project flips from INCOMPLETE_SETUP to ACTIVE.
- 1Config — project code, contract value, dates, currency.
- 2Inventory — buildings & villas, the units progress is measured against.
- 3Team — invite the three firms, name the project PMs, lock the discipline leads.
- 4Workflow — pick which document types are enabled and who signs each stage.
- 5Breakdown — bill of quantities (بنود) per contractor, with weights that drive every claim.
Field to desk in 30 seconds.
A Work Inspection Request — the contractor's engineer raises one when work is ready to be checked. The villa, the discipline, the activities, the photos — all in a single form. On submit, the chain freezes and the inspector's desk lights up.
- 1Villa picker the unit being inspected — drives the heatmap cell that will eventually darken.
- 2Discipline-filtered بنود only the activities under your discipline appear. Multi-select for a single inspection covering several items.
- 3Photos with GPS EXIF metadata carries lat/long and timestamp. The evidence travels with the document — it is the document.
- 4Submit freezes the chain signers, SLAs, and routing snapshot at submit time. Nobody can rewrite history downstream.
Every signature lives on the document.
Once filed, the WIR moves through its chain — contractor → consultant engineer → discipline lead → consultant PM. Each step picks one of four response codes. The chain stays visible to everyone: who has it, what they said, how long they took.
- 1Chain stepper shows where the doc is, who held it, and how long.
- 2Evidence gallery — every photo, every revision, attached to the chain.
- 3SLA timer ticks per stage. Amber = nearing breach, red = breached.
One truth per discipline.
The Progress Update is how cumulative %-complete moves. The PM-side reviewer compares the previous figure, the evidence (approved WIRs since), and the new claim — line by line, villa by villa. One open PRU per contractor × discipline at a time, by design.
- 1Prev → New two columns side-by-side. The PRU explains the delta.
- 2Evidence column approved WIRs since the last PRU. Click through to the WIR. The audit chain is one tap deep.
- 3Warn-but-allow if a claim outruns its WIR evidence, the line warns — but the PM can still approve with a reason. Friction, not blocking.
- 4One open PRU rule ≤ 1 open PRU per contractor × discipline. No two streams of truth.
The heatmap is the project.
Every approved PRU darkens a cell. Every villa is a column, every activity a row. One artifact reads the whole project — overall %-complete, where work is concentrated, where it's stalled. Every cell is a link into the per-villa report.
- 15-step green ramp 0–20 / 21–40 / 41–60 / 61–80 / 81–100. Read the ramp, read the project.
- 2Click any cell → per-villa report activity-by-activity drill, with the WIRs and PRUs that built each number.
- 3No reports to run the heatmap is the report. It's already up to date because PRUs materialize on approval.
The مستخلص writes itself.
The headline moment. The cover sheet — the document the client signs to release money — is computed from approved PRUs and frozen at certification. Numbers are evidence, not typed.
- 1Auto-computed lines per villa, per discipline. No spreadsheet, no re-typing.
- 2Freeze on signature when the PM certifies, the figures lock. Future PRUs don't retroactively change a signed claim.
- 3Org-scoped at three surfaces contractor sees their lines, consultant certifies, client signs. Same document, three views.
Auto-computed work lines. Auditable material lines.
The PC builder is two tables. Work lines roll up from approved PRU progress — one line per villa. Material lines are backed by Material Tests (MT) — and if an MT is missing, the line warns before the PM can certify.
- 1WORK lines computed per villa from PRU progress. You read them; you don't type them.
- 2MATERIALS lines backed by approved Material Tests. Click through to the MT — the audit chain is one tap.
- 3Warn-but-allow a material with no MT shows a warn chip. The contractor PM can still submit with a justification; the consultant PM sees it before certifying.
- 4Certifying flips the PC to AWAITING_CLIENT_SIGN. The client representative is the final approval.
Your desk is the work.
No more "what's stuck on my plate." Every document waiting on you, every document returned to you, and every document about to land — across every project you're on, sorted by SLA.
- 1Pool items light up for everyone eligible until claimed. First responsive engineer takes it.
- 2Cross-project — your desk pulls from every project you're a member of. One inbox.
- 3SLA chips tell you the truth at a glance. ● on track. ● nearing. ● breached.
Live numbers. No reports to run.
The financials page is the dashboard. Headline figures at the top, the S-curve in the middle, the claims register and the heatmap below — all reading from the same materialized progress. Role-gated: the contractor sees their slice, the consultant sees the project total, the client sees what's settled.
- 1StatBar contract value, certified to date, in-flight, paid. Headline numbers, role-scoped.
- 2S-curve planned vs earned. The gap is the conversation with the client.
- 3Claims register every مستخلص, draft to paid. One-click into any claim.
- 4Heatmap villa × activity matrix. Cells link into the per-villa report.
You ran the site.
Now run the project.
Mutamad gives engineer-PMs the management view of the work they already know — without typing it twice.