Why UAE subcontractors lose money on paperwork, not the work

We recently sat down with a senior project manager who has spent decades running UAE roads and infrastructure projects. We asked him ten questions about where subcontractors actually lose money on a job. He answered one of them with a number, on the spot, before we had even finished asking.

"The percentage of loss due to poor documentation and correspondence, around 50%," he said, in English, without pausing to think about it. He then asked us where the question came from, because in his words, nobody had asked him that before.

How much of a subcontractor's loss is really paperwork?

We want to be precise about what that number is and is not. It is one senior operator's off the cuff estimate from years of watching claims win and lose. It is not a study, not a survey, not a data set anyone measured. He put it around half, and we are reporting it exactly as that: his read, not research.

What makes it worth repeating is not the precision of the number. It is that a person who has spent his career on the technical and commercial side of roads and infrastructure work looked at the whole category of money subcontractors lose and split it roughly down the middle between bad work and bad records.

Ask him what a losing claim was actually missing and the answer was not scope, price, or workmanship. It was documentation: more recording of the work and the materials brought in, and understanding how the reviewing side thinks before you submit anything to them. The claim died on records, not on merit.

What does one extra instruction on site actually turn into?

If a subcontractor gets one verbal instruction to do something extra on site, that instruction has a name: a variation order. And a variation order is not one document. It is a chain.

Seven documents, generated from a single sentence someone said on site. The subcontractor has to survey the site, rule on whether the work was already covered in the bill of quantities, write up what they will do and how, price it, reschedule around it, work out what it does to the overall program, and land on how many extra days it is worth.

Here is the part that should worry anyone running a subcontracting business: the project manager we spoke with told us that firms this size, 20 to 60 people, typically run that entire chain with basically no tools. No system tracking which variation is at which stage, no shared record of what was submitted when, nothing that survives a staff change or a missed email. Just whoever remembers to chase it.

What happens when the wrong person handles the record?

The project manager gave us one concrete example, and it is the clearest illustration of what a documentation failure actually costs on the ground.

A pipeline was fully specified in the project drawings: start and end points given as coordinates, northing and easting, elevation, everything a surveyor needs. The surveyor on site used local coordinates instead of the project's official datum. The line got set out in the wrong place.

The problem: site offices had already been built over the route the pipeline was actually supposed to follow. Once the error surfaced, the offices could not stay. The consultant had to rent temporary space, build new offices, move everyone in, and demolish the original structures, before the correct line could even go in the ground.

He told us the same kind of thing happened again on a separate roads and bridges project. His read on why: an engineer costs a firm roughly 15,000 AED a month, a foreman closer to 10,000 plus a car and accommodation, and it is cheaper to hire the unqualified tier. One cheap hire, one datum error, and the consequence was not a paperwork correction. It was a demolition.

Why does retention money get held so long?

Retention is supposed to come back to the subcontractor at handover. In practice, according to the project manager we spoke with, final handover drags and retention gets held, in his words, "as long as possible."

The documents he named as the actual holdup: ongoing project planning records, continuous verification of the work, inspection and testing reports, and as built and survey inputs. Not the quality of the work itself. Whether the paper proving the work happened, and happened correctly, is complete and accepted.

That is the same pattern from the variation order chain, playing out at the end of the project instead of the middle. The work can be finished. The money still does not move until the record of the work catches up.

Is this only a construction problem?

No, and that is the point of writing this up. This is not a pitch for construction management software, and we have not delivered a project in this industry. We are not claiming otherwise.

What we recognized in this conversation is a pattern we see constantly in operations heavy UAE businesses that have nothing to do with roads or pipelines. The work happens. The record of the work is what actually gets paid, approved, or trusted. And the record usually lives in the same three places: WhatsApp threads, someone's memory, and paper that gets filed after the fact, if it gets filed at all.

A subcontractor's variation order chain is an extreme, formalized version of something almost every SME we work with has an informal version of: a job gets done, and the proof it was done correctly, on time, and to spec exists only in someone's head or a chat thread that scrolls away. We have written before about what that looks like when a spreadsheet quietly becomes the thing an entire company runs on in the signs your spreadsheet became a system, and about what happens when none of your tools are actually talking to each other in tools that don't talk to each other.

The fix, in every case we have built, is not a bigger system. It is making the record happen automatically, at the moment the work happens, instead of relying on someone to remember to write it down later. That is what we build: the layer that captures the work as it happens, so nobody is waiting on a memory, a WhatsApp scroll, or a missing report before they get paid, approved, or trusted.