Flexibility
No tool bends to a weird BOQ structure like a spreadsheet does.
The Honest Comparison
ProClaim vs Excel.
Written by people who ran progress claims in Excel for ten years. Excel is not the enemy. It is just not a claims process.
Where Excel is still the right tool.
Familiarity
Every QS in Malaysia grew up in Excel. Zero training.
The universal format
Main contractors and consultants expect Excel files. That will not change soon.
Task By Task
The monthly claim cycle, side by side.
| The task each month | In Excel | In ProClaim |
|---|---|---|
| Starting this month's claim | Copy last month's file, update every previous-quantity cell by hand | Carry-forward is automatic and previous quantities are locked |
| Claimed vs certified | Two documents eyeballed side by side | Discrepancy Detector flags every shortfall line by line |
| The boss checking position | "Can you compile the summary for me?" | Director view, live, without asking anyone |
| Who changed what | No record. Disputes become memory contests | Audit trail on every claim |
| Retention and caps | Calculated by hand in every file | Computed automatically on every claim |
| Site progress from supervisors | Re-keyed from WhatsApp messages and calls | Site reports flow into the claim In rollout |
| Finding answers in your claim data | You dig through the files | Ask Kira, the built-in assistant |
| Sending to the MC | Excel, and that is fine | Still Excel, plus Word and PDF. The output does not change |
The cost nobody counts.
The real damage from spreadsheet claims is not the hours. It is the money you never knew you were owed. Under-certification that nobody spots, claims submitted late because the file was still being rebuilt, retention that quietly exceeds its cap. That cash sits with the main contractor instead of in your bank.
Claim #12 on the demo project: RM 130,531 of shortfalls flagged line by line.
Keep Excel. Add a claims process.
Run ProClaim alongside your spreadsheets. A 30-minute demo on your own BOQ.
WhatsApp 010-453 9315