BOQ automation and site control for a contractor
A control panel for a contracting business that reads bills of quantities out of documents, tracks site progress and material movement, and chases the follow-ups that fall between them.
A contractor's real operating system is a bill of quantities in a document, a progress figure in someone's head, and a material shortage that surfaces the morning it stops work. The BOQ gets re-keyed into a spreadsheet, the spreadsheet drifts from the site, and the follow-ups that hold it all together live in email and WhatsApp where nothing can be counted.
This puts the three in one place. A new BOQ is opened under a client or project from whatever the source happens to be, a PDF, an Excel file, or an email carrying drawings, and the line items are extracted from it rather than re-typed. Quantities are then mapped against the vendor master for cost and selling price, the assembled set is validated before anything is committed, and the result is filled into a template to generate the BOQ. Around it, project and site progress and material movement sit in the same view, with slippage, shortages and overdue follow-ups surfaced rather than waited for.
A new BOQ opens under a client or project from a PDF, an Excel file or an email with drawings
Line items extracted from the source documents instead of re-typed
Quantities mapped to cost and selling price against the vendor master database
A validation step before commit: the assembled set is checked, then the template is filled
Project and site progress and material movement in one view across active jobs
Exception surfacing: slippage, shortages and overdue follow-ups raised rather than hunted for
- PDF / Excel / email
- Line extraction
- Vendor master pricing
- Validation
- Template fill
- BOQ
Followed one bill of quantities from the document it arrives in to the spreadsheet it ends up in, and counted the places it gets re-typed.
A command centre bringing the BOQ, site progress, material movement and open follow-ups into a single panel.
Built so rollout is configuration: a new project or site reuses the same extraction, pricing and validation path rather than a new build.
Re-typing the same BOQ into a third spreadsheet?
Bring the workflow and the number it affects. A reply within one business day.