Qatar needs a contract suite, not another amended Red Book

I have worked on projects in Qatar where the contract begins as the FIDIC 1999 Red Book and, by the time the Particular Conditions, employer requirements, schedules, tender clarifications, letters and work orders have been added, no one can explain the commercial deal without opening half a dozen documents. The form is still described as “standard” because the cover is standard. Much of what follows is not.

This is common across the Gulf. The 1999 Red Book has become the region’s universal contract adapter. It is used for employer-designed civil works, then amended for design-and-build. It is used for lump-sum work, then amended for remeasurement. It is used for emergency work, then supplemented with cost-plus rules. It is used for maintenance, then surrounded by task orders and service measures. Small jobs are often given almost the same form as major infrastructure schemes, complete with long notice clauses, bonds, retention and dispute provisions which nobody expects to use.

The problem is not FIDIC itself. A well-drafted and properly administered Red Book can work very well, and FIDIC has other forms, including the Yellow, Silver and Green Books. The problem is how the market uses them. In much of the Gulf, the normal answer to a new procurement problem is not to choose a different route. It is to take the 1999 Red Book and add more amendments.

Every previous dispute appears to leave another line in the Particular Conditions. The Engineer’s authority is reduced because an earlier Engineer made a decision the employer disliked. Notice periods are tightened because a contractor once submitted a late claim. Broad wording is added to make the contractor responsible for every permit, interface and unknown condition. Internal approvals remain outside the contract timetable, even where the Engineer is meant to decide within a stated period. The contract gets longer, but the project does not become clearer.

This is, apparently, standardisation.

The Red Book as a universal adapter

The lack of procurement choice causes problems long before a claim reaches a lawyer.

Take a distressed or incomplete project where no one can know the full scope until surveys, testing and opening-up works have been completed. The commercial facts suggest a cost-reimbursable route. The contractor should recover properly recorded cost, subject to clear rules, plus an agreed fee. The employer should have audit rights, a cost cap and firm controls over staff, equipment, procurement and subcontracting. Once enough is known, the remaining work could move to a target or fixed price.

Instead, such work is often forced into a familiar Red Book structure. Unknown scope is hidden inside provisional sums, daywork, new rates, work orders and letters. One bespoke schedule tries to define reimbursable cost, another adds the fee and a later letter introduces a cap. Audit rules are written after the first payment dispute. The parties have created a cost-plus contract, but without starting from a contract designed for cost reimbursement.

The same fault appears on complex design projects. A developer may want contractor input on buildability, logistics and procurement, but still issue a single-stage fixed-price tender before the design is ready. The contractor prices the gaps, qualifies the tender and accepts a date based on assumptions. During construction, the employer treats design development as included while the contractor treats much of it as change. The dispute was not caused by poor drafting alone. It was built into the buying method.

Target cost is even less common. There is no routine Gulf market model under which an employer and contractor agree a target, work on an open-book basis and share savings or overruns within stated bands. Each project must invent its own rules for cost records, disallowed cost, target changes, pain and gain share and audit. The commercial idea may be sound, but the contract starts life as a bespoke experiment.

At the smaller end of the market, the position becomes faintly absurd. A modest fit-out or repair package may be issued under a form written for a major project, with guarantees, retention and a dispute route costing more than the likely dispute. The parties sign a long contract and administer the job through emails, site instructions and WhatsApp. A great deal of paper has been created to make sure the paper is ignored properly.

All of this leads to the same question: what would Qatar’s contracting market look like if the form followed the project, rather than the project being forced to follow the form?

A Qatar contract family

The more interesting answer is not another national set of Particular Conditions for FIDIC. It is a Qatar contract family (coining the term NEC-Q, before anyone steals it), based on NEC4, which could be used by private developers, utilities, industrial firms, consultants, contractors and public bodies.

It would not need to begin as a government form. A group of major developers, utilities, contractors and consultants could adopt the same Qatar clauses and schedules, publish a contract manual and test the system on live projects. Wider use could follow from better results rather than an instruction from above.

Nor would it replace FIDIC. There are projects for which the Red, Yellow or Silver Book remains a sound choice. The change would be to give the market a second established system built around different commercial routes and more active management.

The first decision would be the type of contract. Major works could use the NEC4 Engineering and Construction Contract. Small works could use the Engineering and Construction Short Contract. Consultant appointments could use the Professional Service Contract. Maintenance could use the Term Service Contract or Facilities Management Contract. Major plant could use a supply contract, while repeat projects could sit under a framework.

The second decision would be how the work is priced. Option A provides a priced contract with an activity schedule. Option B keeps a bill of quantities and remeasurement. Option C provides a target cost with an activity schedule. Option D provides a target with a bill of quantities. Option E is cost reimbursable. Option F is a management contract.

That list alone would change many tender discussions in Qatar. An employer would have to decide whether the design is mature enough for fixed price, whether quantities remain uncertain, whether a target would improve behaviour, or whether the scope is too unknown for anything other than cost reimbursement. Today those questions are often answered indirectly, through qualifications and amendments after the preferred form has already been selected.

The Qatar version could then be assembled in clear layers. The standard NEC clauses would manage programme, early warning, change, payment, quality and completion. A short set of Qatar Y clauses would deal with local law and recurring local matters, such as Arabic and English documents, formal notices, ten-year statutory liability, labour duties, Ramadan working, summer heat rules, payment and local dispute routes.

Project information would sit in the right place. The Scope would describe the asset, design duties and handover requirements. Contract Data would state the dates, values, periods and named people. A dated technical register would identify the exact QCS, Ashghal, Kahramaa, municipal or employer documents which apply. A permit and connection matrix would state who prepares, signs, submits, pays for and carries the delay risk for each approval. A completion schedule would separate physical completion, regulatory approval, utility connection, taking over and final handover.

This matters because phrases such as “all latest requirements” or “all permits necessary for completion” appear firm but postpone the real decision. Which revision applies? Which party can sign the application? What information must the employer provide? What response period was allowed in the tender programme? What happens where an authority changes its requirement after the tender date?

Employer amendments, known in NEC as Z clauses, would need tight control. Any extra clause should have to explain why the matter cannot be dealt with through the selected option, the Scope or Contract Data. Without that discipline, a Qatar NEC form could quickly become a familiar Gulf contract: NEC on the cover, 80 pages of amendments behind it and the same habits underneath.

The practical value becomes clearer through examples.

A hotel or residential tower with a mature design could use Option A, with payment against completed activities. The Scope could define contractor design, mock-ups, testing, commissioning and handover, while Key Dates could cover sample-room approval, permanent power, operator access and soft opening. Where the design is not ready, the project could begin with early contractor involvement, allowing the contractor to test buildability, logistics and programme before the main price is agreed. This would be cleaner than tendering half a design and calling the result lump sum.

A road, drainage or utility package could use Option B. The bill of quantities and remeasurement would remain familiar, but the programme would include permits, traffic diversions, trial holes, dewatering, utility approvals and inspections. The permit matrix would show whether the contractor, employer, landowner or designer owns each step. A late and incomplete contractor submission would remain the contractor’s risk. A late employer-owned approval could be treated differently. The contract would stop pretending that every permit is the same.

An urgent rectification project could use Option E. The contractor would recover properly recorded Defined Cost plus a fee, subject to disallowed-cost rules and audit. Staff, labour, equipment, materials and subcontractors would be treated through stated rules from day one. A cost cap could require approval beyond an agreed limit. As surveys reduce uncertainty, the remaining work could move to a target or fixed-price package. This is what many employers already try to achieve through bespoke cost-plus schedules, but it would begin with a tested commercial structure rather than a patch added to the Red Book.

A hospital, data centre, treatment plant or large mixed-use project could use Option C after an early contractor stage. The employer and contractor would agree a target. Actual Defined Cost would be measured against it. Savings would be shared, and overruns would also be shared within agreed bands. The target would change only for stated compensation events. Defective work, poor productivity and unapproved cost would not become employer risks merely because the account is open book.

This would not make the parties friends, nor does it need to. It would simply give both sides a commercial reason to deal with design, utilities, logistics and procurement before they become claims. That may be more useful than asking a contractor to price every unknown risk on tender day and then acting surprised when the risk allowance is either very high or not there at all.

Small works could use the NEC short contract, with a concise Scope, price, programme, payment process, change rule and dispute route. Maintenance could use the Term Service Contract or Facilities Management Contract, with response times, planned tasks, emergency call-outs, task-order pricing and asset records. The same family could extend to consultants and suppliers, so that design stages, authority submissions, manufacture, testing, delivery and warranty all use the same language of programme, early warning, change and records.

The real change would be how projects are run

A new form would be of little value if it were administered like an amended Red Book.

On many Gulf projects, the programme becomes less a management tool than a record prepared for the next extension-of-time submission. Updates arrive late, reviews take too long and instructions are issued without a firm view of time or cost. Variations remain open for months or years. The final account then tries to reconstruct decisions which should have been made while the work was live.

NEC works differently because early warning, the accepted programme and compensation events are tied together. When an event appears, the parties are expected to notify it, consider how to reduce its effect, forecast time and cost, and update the programme. The purpose is to make a decision while there are still choices.

A late utility approval provides a simple example. The contractor’s submission would first be checked against the accepted programme and permit matrix. Was it complete? Was it submitted on time? Were the fee and supporting documents provided? If not, the risk remains with the contractor. If the submission was compliant and the delay sits with an employer-owned approval, the Project Manager would assess the event and consider what can be done about it. The team may resequence work or bring forward another area. The effect would be forecast at the time, not reconstructed two years later from correspondence.

The role of the contract administrator would also change. Under NEC, the Project Manager manages instructions, programme, payment and compensation events, while the Supervisor deals with tests, inspections and defects. The same consultancy could supply both people, but the functions would be clearer than the common arrangement in which the FIDIC Engineer is expected to monitor, certify, instruct, review design, determine claims and remain subject to employer approval at the same time.

The difficult part is authority. A Project Manager cannot make a prompt contractual decision where every meaningful answer must pass through four committees over two months. Private developers can face the same problem as public bodies, particularly where lenders, operators and overseas boards all want to approve change. The contract timetable must match the real approval structure, or the stated response periods become fiction.

Completion would need the same care. Qatar projects often become stuck between physical completion, authority certification, utility connection, beneficial use, taking over and final handover. A Qatar NEC form could state what each stage means and what changes at each point, including delay damages, insurance, maintenance, payment and the defects period. This would be a marked improvement on broad terms such as “beneficial use”, which are often expected to solve a practical problem without anyone defining when they start, what they cover or when they end.

The system should also be digital from the outset. Each early warning, instruction, programme submission, compensation event, permit and payment assessment could be logged against the right clause and response date. A simple dashboard could show overdue decisions, open risks, permit status, forecast change and movement in completion. Standard data fields and a controlled workflow would already be a large step forward from project knowledge being held across letters, PDFs, spreadsheets and inboxes.

There are obvious ways this could fail. Employers could add so many Z clauses that the new form becomes another risk-transfer document. Contractors could turn every early warning into a claim notice. Consultants could keep making decisions as though preparing a later FIDIC determination. Target-cost contracts could be launched without reliable cost records, while cost-reimbursable contracts could be used without enough audit staff. A new label would not cure any of these problems.

A small Qatar contract council could control the standard local clauses, bilingual text and permitted departures. It need not belong to one employer. Developers, utilities, contractors, consultants, lawyers, quantity surveyors and planners could all take part. The first projects should then test different behaviours: a measured civil package, a defined private building, an urgent cost-reimbursable job, a target-cost complex scheme, a small works contract and a term maintenance service.

More choice, fewer fictions

The strongest case for a Qatar-adapted NEC family is not that NEC is newer than FIDIC or better for every project. It is that Qatar’s construction market needs more normal choices.

A mature market should be able to say that a project is fixed price because the design is ready, remeasurement because quantities are uncertain, target cost because difficult risks need joint management, cost reimbursable because the scope cannot yet be known, short form because the job is small, or term service because the work is maintenance.

Qatar often reaches those same commercial positions, but only after the 1999 Red Book has been amended, qualified, supplemented and partly replaced by letters. By then, the price has been tendered and the parties may already hold different views of the deal.

A local NEC family could move that decision to the start. It could give contractors, consultants and employers a common language across construction, professional services, supply, maintenance and small works. It could reduce dependence on bespoke drafting, make tender comparison clearer and allow the supply chain to use terms which match the main contract rather than a rough pass-down of risks.

FIDIC would still have an important place. The aim should not be to replace one default with another. It should be to end the assumption that every project can be made to fit the same amended Red Book.

Qatar’s next major change in contracting should not be a thicker set of Particular Conditions. It should be a family of contracts designed around the way different projects are actually bought, priced and delivered.

The radical step is also the most obvious one: stop pretending that one contract can do every job.