5 productivity traps that are eating your project margins

After running projects in Abu Dhabi for a decade, I've stopped being surprised by the same five mistakes. They show up on residential towers, mosques, warehouses, and roads — same five traps, regardless of project type. None of them are caused by lazy people. They're caused by tools that were never designed for the job.

Here they are, ranked by how much margin they quietly consume.

Trap 1: Excel BOQs without version control

The BOQ moves through 15 revisions before tender close. Three of them are emailed. Two are shared on Google Drive. One lives in a folder named Final that has four files in it. Six months later, when an IPC dispute arises, nobody can defensibly say which revision was current when item 2.3.4 was measured.

The fix: treat the BOQ as a versioned object, not a file. Every revision is a diff: which items changed, by how much, on which date, attributable to which addendum. Excel is fine for exchange with consultants. It is not a system of record.

Trap 2: WhatsApp daily reports nobody owns

The site engineer posts manpower, weather, and progress photos to the project WhatsApp group every evening. The PM sees them, the QS sees them, the office manager sees them. Nobody files them. Three months later, someone asks "how many workers were on site on March 14?" and the answer requires scrolling through 8,000 messages.

The fix: the engineer keeps using WhatsApp — that part is fine. The data behind the message gets captured into a structured record the moment it's sent. You don't ask the engineer to change behavior; you change what happens after he hits send.

Trap 3: Paper IPCs

The interim payment certificate is the only document in a construction project that directly converts to cash. And on too many UAE projects, it still gets compiled in Word, with screenshots of supplier invoices, manual sums in the cover sheet, and the QS calculating retention by hand.

The IPC then takes three weeks to circulate, because every revision requires re-printing, re-signing, and re-scanning.

The fix: the IPC is a computed document. The progress quantities come from approved field reports. The line items come from the BOQ. The supplier invoices come from the AP module. Retention is a formula, not a manual line. When the inputs change, the IPC re-computes. The cycle drops from three weeks to four days because there's no manual assembly step.

Trap 4: Tax filing as a year-end scramble

VAT returns are quarterly, but most contractors treat them like an annual event. By the time the deadline approaches, supplier invoices are missing, line-item splits aren't right, and the FTA portal demands data nobody has assembled.

In 2026, this is going to get worse. Corporate Tax at 9% on profits above AED 375,000 is in effect. E-invoicing is rolling out. The year-end scramble is going to compound.

The fix: capture the tax-relevant fields at the moment of invoice entry, not at quarter-close. Supplier invoice arrives → AI scans it → VAT line is extracted → CT-relevant categorization is applied. By the time the quarter ends, the return is already 90% computed.

Trap 5: Hiring more PMs to "solve" reporting

The most expensive trap. The PM team is drowning in reports. The natural response is to hire another PM, or a project coordinator, or a "reporting analyst."

But the bottleneck isn't headcount. It's that PMs are spending 60% of their time consolidating data that lives in five different places. Adding a sixth person to the consolidation chain doesn't speed it up; it adds a sync meeting.

The fix: consolidate the data, not the people. When the BOQ, daily reports, supplier invoices, and IPCs live in one system, the PM stops being a consolidator and goes back to being a project manager.

The compounding cost

Each of these traps costs maybe two to four hours a week per project. On a 10-project portfolio, that's 200 hours a week. At AED 200 an hour fully-loaded, that's AED 40,000 a week in PM time burned on work that shouldn't exist.

Across a year, that's AED 2 million. For mid-market contractors, that's not a rounding error — that's the difference between a year where you bid more work confidently and a year where you stretch the team thin.

The fix for all five traps is the same: stop using disconnected tools as your operating system. The ERP is not the goal — running the projects is the goal. The ERP is just the tool that gets the PM team out of consolidation hell and back to running the projects.

— Eng. Amr Shoieb