Document control procedures for UAE construction projects

Document control on a Gulf project carries requirements that international teams frequently underestimate: multiple authorities, bilingual documentation on some contracts, and retention periods that outlast the people who set the system up.

These are the procedures worth getting right in the first fortnight, because retrofitting any of them across ten thousand records is not realistic.

1. Agree the numbering convention before the first document

A convention that survives three years and several changes of personnel is worth more than a clever one only its author understands. Most workable schemes encode project, originator, discipline, document type and a sequence — for example NHM-ALM-265000-DG-00-7A4002-002.

Whatever you choose, write it down, circulate it, and make new starters follow it. The most common failure is not a bad convention; it is three conventions running simultaneously because nobody documented the first.

2. Record distribution, not just issue

Who received a document, and when, is the fact most often disputed and least often captured. A transmittal should be a record with a receipt, not a covering note.

On projects where a delay claim later turns on whether information was issued in time, the transmittal register is consulted more than any other document.

3. Never overwrite a revision

Superseded documents answer the question of what was in force on the date the work was built. Deleting them destroys the only evidence that matters when work built to an earlier revision is questioned.

Mark them superseded, keep them accessible, and make sure the current revision is unambiguous on site as well as in the office. Rework against an obsolete drawing is among the most expensive avoidable errors in construction, and it is almost always a communication failure rather than a competence one.

4. Plan for the authorities from day one

Depending on the emirate and the sector, submissions may run through the municipality, Civil Defence, DEWA or ADDC, Trakhees or a free-zone authority, and each has its own format, sequence and resubmission behaviour.

Two practical points. Build authority submissions into the submittal register rather than tracking them separately, so their status is visible alongside everything else. And record the date of each authority submission and response — those dates support entitlement where approval times exceed what was allowed in the programme.

5. Bring email onto the project record

The most consequential correspondence on most projects is informal, and it lives in personal inboxes until somebody moves to another project. Capturing project email against the project reference — searchable alongside the formal registers — closes the largest single gap in most document control systems.

6. Set retention deliberately

Retention should be driven by the limitation period applicable to your contract and by any decennial liability the project carries, not by whatever the storage plan defaults to. For most Gulf building projects that means the project record needs to remain retrievable for a long time after practical completion, in a form somebody can still search.

7. Build the handover set as you go

O&M manuals, test certificates, warranties and as-builts assembled during the project take a fraction of the effort of assembling them in the final fortnight, and they are far more likely to be complete.

This is largely a tagging discipline: mark documents for the handover set as they are approved, and the set assembles itself.

A test worth running

Ask a new starter to find the current revision of a specific drawing, the transmittal that issued it, and the comments raised against it. Under a minute is achievable. An afternoon and a phone call means the register depends on memory rather than structure.

Our automated document control is built around these procedures, with OCR retrieval, transmittal tracking and an immutable audit log behind every action.