The Control Layer Between the Contract and the Decision

The layer underneath capital and ambition

Complex programmes across the GCC combine national ambitions, funding commitments and demanding delivery schedules. Their operating conditions deserve as much attention as their technical plans.

The region has solved for capital. It has solved for ambition. It has largely solved for the technology stack, because every serious contractor and client in the Gulf now runs some combination of contract lifecycle platform, project controls suite and executive dashboard.

What remains unsolved is the layer underneath all of it. Not what the contract says, and not what the system records. What people actually do at the moment a decision has to be made under pressure.

That layer is ungoverned, and it is where the money goes.

When projects are reprioritised, descoped or delayed, organisations need reliable records and clear authority. The practical task is to understand the consequences of a change before making commitments that the delivery team cannot support.

What leakage looks like on a Gulf programme

A programme director on a live package knows this sequence without needing it explained.

Site access slips by five weeks and nobody serves notice, because the client is a sovereign entity or a group that will award the next three packages. A design change is agreed verbally in a progress meeting and priced nine months later, from memory. A commercial manager who held the entire history of a claim finishes his contract and flies home, and the file he carried in his head leaves with him. A subcontractor commitment does not match the prime contract, and the mismatch surfaces at handover. An executive gives a reassurance in a client meeting that the delivery team was never consulted on. A frustrated email is sent at eleven at night and becomes the strongest document the other side owns.

None of that is a breach. Every step of it is reasonable, human and locally rational. And by the time it is called a dispute, the value has already left the building.

Contracts in this region rarely fail in the document. They fail in the behaviour of capable people operating under real pressure.

The structural reasons this happens here

Four conditions make the Gulf a higher amplitude environment for this failure than most markets. None of them is a criticism of the region. All of them are consequences of the speed and scale at which it has chosen to build.

Counterparty asymmetry. A large proportion of regional work is performed for sovereign clients, national champions and major family groups, against whom a contractor holds a real entitlement and a limited practical appetite to enforce it. Notice provisions exist and go unused. The relationship is protected and the margin is not. That is a commercial structure, not a cultural failing, and it produces measurable leakage.

Compressed programmes. When a national deadline is fixed and public, sequence gets traded for pace. Decisions move to the site and to the individual, ahead of the documentation that is supposed to protect them.

Deep and multinational supply chains. Delivery runs through layers of subcontractors and specialist vendors, and through teams drawn from a dozen national engineering traditions. A term interpreted one way in a design office in one country is interpreted differently on site in another. The contract is centralised and its interpretation is not.

Mobile workforces and thin project memory. The Gulf's talent model is international and rotational by design — expatriates constitute roughly four fifths of the Saudi employed workforce, a share that has barely moved despite a decade of localisation policy, because giga-project construction keeps pulling capability in. It brings extraordinary expertise into the region, and it means institutional memory frequently sits in individuals rather than in the organization. When they move, the history moves with them, and the same mistake is priced again on the next job.

These four conditions were offered, in the first version of this article, as practitioner observation. The dispute data now lets us measure their amplitude.

Payment timing, changes in scope and approval delays can interact across a supply chain. Their importance should be established from the actual programme records, rather than inferred from a regional stereotype or an unrelated dispute sample.

The four conditions are observation. The amplitude they produce is measurement.

Measure the exposure in your own organisation

Start with the record of decisions: missed notices, unauthorised changes, delayed approvals, unresolved handovers and payment disputes. Separate observed events from estimates of what they may have cost.

External research can help frame questions, but different samples and definitions cannot be combined into a regional loss estimate. A survey of contract managers and a dataset of disputed construction projects answer different questions.

The useful comparison is between an agreed baseline and subsequent behaviour in a defined setting. Commercial outcomes may emerge later. Do not treat a change in activity as proof of a financial saving.

The control point the market does not serve

Contract prevention is not the claim that disputes can be eliminated. It is the disciplined reduction of the conditions that make value hard to protect. A mature model operates across five control points.

1. Structure. Is the commercial position clear before performance begins? 2. Recognition. Can the organization see risk before it becomes an event? 3. Behaviour. Will people act in a way that preserves the position? 4. Evidence. Can the organization prove what happened and when? 5. Learning. Does the organization get better after each project?

Contract platforms, claims specialists, programme offices and controls teams can support structure, recognition, evidence and learning. Their roles remain necessary.

The behavioural control point can fall between those roles. A risk may be identified without being acted on, or an obligation tracked without being understood. Examine who owns the step from information to decision in this organisation.

The practical question is whether commercial expertise remains available when operational commitments are made. Obligation tracking is more useful when the decision-maker can interpret the obligation in context and reach an appropriate reviewer.

Every organization runs two operating systems

Only one of them is written down.

The System OS is the visible layer. Platforms, workflows, data, dashboards, documents, controls. It is what the transformation budget buys.

The Human OS is the behavioural layer. How people interpret risk, decide with incomplete information, communicate under pressure, preserve leverage and evidence, escalate to the right authority, and convert experience into rules the organization keeps.

System OS stores the contract; Human OS interprets what it means in context. System OS tracks the obligation; Human OS decides whether it is understood and acted on. System OS flags the risk; Human OS determines whether the warning changes behaviour. System OS records the communication; Human OS shapes the communication before it is sent. System OS reports performance; Human OS explains the behaviour that produced it.

System OS creates capability. Human OS decides whether capability becomes performance. An organization that installs better tools on top of an ungoverned behavioural layer has purchased a clearer view of its own leakage.

Human OS is a working metaphor for how judgement, relationships and behaviour influence execution. Independent assessment, clear decision boundaries and appropriate checks can help a team examine decisions before acting on them. Their usefulness needs to be tested in the actual workflow.

That is exactly what the unserved notice, the verbal variation and the eleven o'clock email are. Not personality defects. Predictable, patterned, structurally reducible judgment failures — occurring in the one layer of the delivery stack that has no owner and no instrumentation.

Build the capability in its local context

The instinct in the region has often been to bring in mature market practice and adapt it. On this question that instinct is wrong, for a straightforward reason.

The Gulf brings together complex programmes, multicultural teams and relationships that cross organisational boundaries. These conditions offer a practical setting for learning how commercial decisions are made and where support is missing.

Early planning is an opportunity to agree decision rights, evidence requirements and escalation routes. Waiting until a programme is distressed can make the same work harder. The appropriate controls still depend on the contract and context.

There is also a localisation argument that in country value programmes across the region already recognise. Delivery capability is national capability. A region that can prevent value loss in execution retains margin inside its own economy, builds a class of commercially disciplined local contractors, and reduces the volume of regional dispute value that flows to advisers outside it.

Delivery capability also matters beyond a single contract. Local organisations can retain knowledge by making decision records, commercial responsibilities and lessons from delivery part of their everyday practice.

What a serious organization does next

Resist buying a solution before establishing a baseline. The discipline runs in this order, and the order is the discipline.

Establish the baseline. Review missed notices, late escalations, unauthorised concessions, evidence gaps and decision rework. Agree the definitions before comparing results. This makes later claims easier to examine.

Run a controlled proof of concept — and design it to be believed. One live project or business unit, 30 to 60 days, behavioural guardrails at selected decision and communication points, with a defined decision gate at the end to scale, refine, reposition or stop. The evaluation design should be fixed before the pilot starts, not negotiated after it ends: the leading indicators chosen in advance, the comparison logic stated, the causal caveats written down. A sceptical CFO will not be persuaded by a success story. They may be persuaded by a pre-registered test that was allowed to fail.

Measure leading indicators before lagging ones. Interventions accepted or overridden, contract context retrieved before a decision, escalations routed to the correct authority. Commercial outcomes follow later, and a credible evaluation links the two without pretending causality is immediate. The honest claim after sixty days is not "we saved X million." It is "the decisions that historically produced X million of exposure now happen differently, and here is the instrumented record."

Build governance into the return. Data minimisation, access and retention control, human override, explainable rationale, audit logs and clear boundaries for sensitive communications. In a region where relationship trust is the operating currency, a capability that protects margin and erodes trust has not created value.

Scope reductions and suspensions test these disciplines directly. Review notices, verbal agreements and evidence gaps when a change arises, rather than discovering the missing record during a dispute.

The question worth putting to your board

Most organizations in this region can answer whether they have a contract platform, a claims adviser and a project dashboard. Very few can answer the question underneath all three.

Can our operating system stop a pressured human decision from becoming an expensive commercial fact?

The question deserves evidence from the organisation itself: which decisions create avoidable exposure, what support reaches the decision-maker, and what changes when that support improves?

The connection between a contract and the decisions made under it deserves a named owner.

Clarity before scale. Structure before performance. Human OS before System OS.

Basis and limits of the argument

This essay presents a practitioner perspective on decision-making and commercial execution. It does not estimate GCC contract losses or promise a recovery rate.

Any external benchmark used in a proposal should be linked to its original publication, date, sample and definition. A client-specific claim requires evidence from that client and a clear account of other factors that may have affected the outcome.

About the author

Zeeshan Sabri is a Clarifier and founder of ClarityOS. His writing explores the human conditions beneath decisions, governance and change. To discuss a situation or programme, use the contact page.