Why Construction Projects Drown in Documents — and How to Fix It

How Many Documents Does One Project Generate?

A medium-sized GCC construction project — SAR 100M–300M — typically produces:

• 3,000–8,000 drawings across multiple disciplines (civil, structural, MEP, architectural), each going through 4–8 revision cycles
• 500–2,000 RFIs with question-response-close cycles
• 200–500 transmittals tracking document distribution
• 10,000–30,000 daily reports, inspection records, and test certificates
• 1,500–5,000 subcontract documents — scope, work orders, confirmations, variations, certifications
• 300–800 formal correspondence items — letters, instructions, FIDIC notices

That is before you count timesheets, delivery notes, safety observations, and progress photos. A SAR 200M residential tower in Riyadh generates somewhere between 80,000 and 150,000 documents by handover. Most GCC contractors are managing that volume with email threads, shared drives, and a part-time document controller who is permanently underwater.

The Real Issue: Organization, Not Volume

Construction projects do not drown in documents because there are too many of them. They drown because of three structural failures:

No single point of truth. Drawings live in the design consultant's FTP, the contractor's shared drive, and the PM's desktop — often in different revision states. Field supervisors download revision C, work from it for six weeks, then discover revision F was issued three weeks ago.

Email is the distribution mechanism. A transmittal goes out to 14 addressees. Half open it, half do not. There is no forced acknowledgement, no read-receipt that holds contractual weight, no way to confirm the right revision reached every stakeholder.

The audit trail is incomplete. When a claim arises under FIDIC — say, an EOT request citing late drawing issue — the evidence needed is a timestamped record of when each revision was issued, to whom, and when acknowledged. Pulling that from email threads takes weeks.

Five Document Types That Each Need Their Own Workflow

Not all construction documents are the same. A system that treats them identically will fail at all of them.

1. Drawings and Technical Submittals

These need revision control with automatic supersession. When revision G is issued, every reference to revision F should show as superseded — in the register, in every drawing package, on every mobile device. Submittals need a formal review cycle: submission to review period (typically 14–21 days under FIDIC) to comment to resubmission or approval.

2. RFIs

RFIs need routing rules that prevent them stalling. Who answers each type? What is the response SLA? What happens when the deadline passes? An RFI register is meaningless without automated reminders and escalation paths. A delayed RFI is a potential EOT event — that needs to be captured and linked to the schedule.

3. Transmittals

Transmittals need forced acknowledgement. Not "did the email land?" but "did the specific person confirm receipt of a specific revision?" Under FIDIC Clause 1.3, proper notice delivery matters for claims. A transmittal that cannot prove it was received is only half a document.

4. Site Records and Inspection Certificates

Daily reports, QC inspection records, test certificates, and as-built records are generated in the field — often on paper — and frequently never get scanned and registered. These prove what was built, when, and to what standard. Losing them does not just create compliance risk; it makes it impossible to defend payment claims.

5. Formal Correspondence and FIDIC Notices

Letters, engineer's instructions, and FIDIC notices require tracked issue dates, response deadlines, and follow-up alerts. Under FIDIC Clause 20.1, a contractor who misses notice deadlines loses entitlement regardless of merit. A document control system that does not flag correspondence response deadlines is leaving money on the table.

What Document Failures Actually Cost

Document failures translate directly to financial exposure.

Rework from wrong-revision drawings. A structural crew on a SAR 50M office project in Jeddah built 120m of blockwork to revision D when revision F had moved a partition wall. Demolition and rebuild: SAR 280,000. The revision F transmittal had been sent — but never formally acknowledged by the site team.

Lost claims from poor document trails. A GC submitted an SAR 1.8M EOT claim based on late drawing issue. The engineer rejected it because the contractor could not prove issue dates — transmittals were in email threads across four inboxes. The claim settled for SAR 400,000. A SAR 1.4M shortfall from a document control failure, not a substantive one.

Rework from approval gaps. On a Riyadh MEP package, materials were installed before client submittal approval was confirmed. When comments came back requiring revisions, SAR 380,000 of installed materials had to be replaced.

Audit preparation cost. A GCC contractor preparing for a ZATCA audit on a completed project spent 12 man-weeks reconstructing the document register from email archives. A structured system makes that a 4-hour export.

What a Proper Document Control System Actually Looks Like

The goal is not to digitize the chaos. It is to enforce discipline at the point where documents enter and leave the project.

Single document register. Every document — drawing, submittal, RFI, correspondence, test certificate — has one master record with issue date, revision, status, and recipients. No exceptions.

Structured naming conventions. Documents follow a defined naming schema: project code, discipline, document type, sequence, revision. A code like RYD-STR-DRG-0042-F is immediately understood by anyone on the team. This makes documents findable without relying on memory.

Role-based access and distribution lists. Subcontractors should see their scope documents, not main contract correspondence. Automatic distribution lists by discipline or package reduce manual routing errors and prevent information leakage.

Forced acknowledgement on critical documents. Transmittals carrying drawings or instructions should require the recipient to click-confirm receipt. The timestamp goes into the register automatically — no chasing, no ambiguity.

Mobile access to current drawings only. Field teams should only ever see the current revision on their mobile device. Superseded drawings are viewable but clearly marked — and inaccessible for the active drawing view that site supervisors use daily.

Integration with the claims record. Every transmittal delay, every unanswered RFI, every late instruction should automatically populate the contemporaneous record that supports delay and disruption claims under FIDIC Clause 20.

GCC Context: What Clients and Contracts Require

Saudi Aramco, NEOM, and ROSHN each have defined document management requirements embedded in their contract packages. Aramco requires documents to follow SAEP naming conventions submitted through a defined portal. NEOM projects mandate BIM-integrated document workflows. ROSHN requires structured submittals with defined review periods and tracked responses.

Under FIDIC, document control is a contractual obligation — not just an administrative one. Clause 1.3 defines valid notice. Clause 13.3.1 defines the variation proposal process. Clause 20.2 sets the claim notice window. None of these work without a verifiable document trail.

Saudi Vision 2030 projects are increasingly requiring contractors to demonstrate document management capability at prequalification — not just during execution. A structured system is a competitive requirement, not just an operational one.

Five Practical Starting Steps

If your project runs on email and shared drives, you do not need to rebuild everything at once. Start here:

1. Audit your current drawing register. List every active drawing by discipline, current revision, and last recipient. This single exercise surfaces most version control gaps and shows you exactly where the risk sits.
2. Define document types and workflows before picking software. Map what document types you have and what each needs — creation, review, approval, distribution, acknowledgement, close-out. Software should fit the workflow, not impose one.
3. Set up forced acknowledgement on drawings and instructions. This is the highest-value quick win. Any document that matters for execution or claims should have a timestamped confirmation step.
4. Create a correspondence register this week. Every formal letter and instruction gets a register entry with issue date, expected response date, and action owner. This takes two hours to set up — do it now, migrate to a system later.
5. Scan and register site-generated documents weekly. Daily reports, inspection records, and test certificates piling up in site offices without registration become unrecoverable. A weekly register catch-up is the minimum viable process until a mobile capture workflow is in place.