Your engineer says “Villa 101 mein 40 square feet plaster ho gaya” — in Hindi, Gujarati or English, standing in the dust with one hand free. Rozo resolves the villa, the activity and the quantity, and files a structured progress entry before they've put the phone down.
Between the last slab poured and the report that reaches the office, the detail leaks out — into WhatsApp photos, a diary page, a spreadsheet rebuilt every month. By the time anyone asks what happened at Villa 101 on the 14th, the only honest answer is “roughly this”.
No dropdowns, no form fields, no picking a villa from a list of four hundred. The engineer talks the way they'd talk to a colleague — and Rozo does the resolving, matching aliases and local names against the project's real hierarchy.
“Safai”, “विला 101”, “V-101”, “mistri” — aliases you define once are matched alongside the formal name, so nobody has to learn the system's wording.
If “Grouting Work” matches three floors, Rozo asks which one rather than picking. Low-confidence matches wait for a tap to confirm before anything is written.
The entry lands in the active reporting period with its activity's own unit — and an audit row naming who logged it.
Name your levels — Villa, Floor, Room — then list what exists at each. Three villas and two floors becomes six floors wired to the right parents, not six rows typed by hand. Or bring an existing project in from the Excel you already keep.
Up to six levels deep. Define the shape once; elements below inherit it automatically.
Assign each activity's total scope to the room it belongs to, so completion is measured against something real.
Bring hierarchy, elements, activities and BOQ in from Excel — validated row by row before anything is created.
Every element and activity carries aliases, so “V-101” and “विला 101” both resolve without retraining anyone.
Progress files against the open reporting month, and the month rolls forward on its own when the calendar turns.
Project-scoped permissions decide who can restructure a project and who can only add to the day's record.
Managers open one table and see where the project actually is — per villa, per activity, against scope. Cells stay editable, and every correction keeps its history.
| Element | Activity | Scope | Achieved | Completion | Status |
|---|---|---|---|---|---|
| Villa 101 · Floor 2 | Plaster | 1,240 sq ft | 1,108 sq ft | On track | |
| Villa 101 · Ground | Excavation | 380 cu ft | 380 cu ft | Complete | |
| Villa 102 · Floor 1 | Grouting Work | 640 rft | 214 rft | Behind | |
| Villa 103 · Ground | Tiling | 520 sq ft | 305 sq ft | In progress |
Most dashboards quietly sum every quantity into one number. Ours refuses to — each activity is measured in its own unit, and progress is reported as a ratio against that activity's own scope.
1,108 of 1,240 sq ft — measured in area, compared only against area.
380 of 380 cu ft — volume, kept separate from every other activity.
214 of 640 running feet — length, never folded into a single site total.
Every progress and labour entry carries its author, its timestamp and the way it arrived. Managers can ask in plain language whether a number was corrected after the fact — and see the trail, not a summary.
Bring one project's Excel. We'll set up the hierarchy, activities and BOQ with you, and let your engineers log a real day.