The site moves only when the paperwork does.
Margin in construction rarely disappears in one place. It leaks through work performed before it is priced, quotes compared by eye, a DURC di congruità computed the week it is due, and a progress statement assembled from photos and memory. Every one of those is a queue that a site manager, an estimator or the office absorbs in the evenings. The queue is where an agent belongs, with the person who knows the site keeping the decision.
- Built on top of the estimating and accounting software you already run
- A named person signs before anything reaches a client, a supplier or an authority
- Most of the six queues below need code and a rule, not a model
Put an agent on the queue, not on the org chart.
Each role owns one recurring queue. It drafts, it shows its evidence, and a named person signs before anything consequential moves. The last column is the sector’s AI Boundary Map: whether the step is mostly a rule, mostly a model, or stays with a person.
| Role | What it drafts | Who signs | What it reads | Mostly |
|---|---|---|---|---|
| Estimating desk | A bill of quantities from the drawings, priced against the regional price list, with every item that had no match flagged. | The estimator, item by item, before the quote goes out. | Drawings, the regional prezzario, your own historical quotes. | a model |
| DURC di congruità check | The labour-cost congruity calculation per site against the CNCE thresholds, updated every time payroll or the contract value changes, with the gap to the threshold shown in days of labour. | The office, before submission. | Payroll, the contract, the Cassa Edile denuncia. | code and rules |
| Progress statement (SAL) clerk | The progress statement from site measurements and delivery notes, with each quantity traced to the document that supports it. | The site manager and the works director. | Site measurements, DDTs, the computo. | code and rules |
| Supplier quote comparison | Three or five supplier quotes normalised to one line list, with missing items, unit mismatches and non-standard conditions flagged. | The buyer. | Supplier PDFs and emails, your RdO. | a model |
| Cassa Edile monthly filing | The monthly denuncia from recorded hours per worker per site, with anomalies against the previous month listed. | The payroll consultant. | Timesheets, payroll, the previous filing. | code and rules |
| Subcontractor compliance | The document set per subcontractor per site, with expiries thirty days out and the contract drafted from the accepted quote. | The office, and the site manager for site access. | PEC, the document store, the DURC portal. | code and rules |
How much of this is actually AI.
Four of these six queues are rules and lookups: the congruity threshold is a published table, the SAL is arithmetic over documents, the denuncia is a transformation of hours, the compliance set is a checklist with dates. Only the two that read unstructured documents, drawings and supplier PDFs, need a model, and even there the model extracts and a rule prices. That is the shape the AI Boundary Map usually takes in this sector, and it is why the running cost stays low and every number can be shown to a works director as a rule rather than argued for as a sample.
4 / 6 queues mostly rules · 2 / 6 with a model
No client names. Real patterns.
Every engagement produces the same five documents, whatever the sector. What we can show is anonymised: the pattern, the number, and where it applies.
Across the workflows SUPALABS has mapped, the step that needs a model is the minority: in one European manufacturer’s order handling, three of eleven. Construction estimating follows the same shape, with extraction in the model and pricing in a rule (SUPALABS engagement data, 2024–2026).
Related case studies
Three tiers, set per task type, and you set the thresholds.
Every automated task runs at one of three levels of authority. The tier is set per task type rather than per system, so the same workflow can draft one step, wait for approval on another, and act alone on a third. A task moves up only when the evaluation suite shows the pass rate you defined as the threshold, and it moves back down the moment the monthly report shows a regression.
Nothing is promoted on our say-so. The thresholds are yours, the report that tests them is a named line item, and the decision log shows every action that was taken at every tier.
The full method: five artifacts, three tiers, four rungs →Four rungs. You can stop after any of them.
The problems, one at a time.
Frequently asked questions
The same method, other queues.
Thirty minutes to find out whether there is anything worth mapping.
The call is free, and we will tell you if the answer is no. Bring one queue that costs someone an evening a week.