The Essential Guide To Setting Up A DISPUTE CONTROL Management Unit For The Avoidance, Prevention And Resolution Of Construction Disputes.
most significant commercial challenge you faced?
Author’s Foreword
Construction disputes are becoming the modern malaise that consume time, money, and management attention out of all proportion to their original causes — eroding project value, straining relationships, and often derailing delivery long after the root issue should have been resolved.
In most cases, disputes do not arise because parties intend to act unfairly. They arise because risks are misunderstood, issues are left unattended, and execution discipline weakens under pressure.
This book was written to address that reality. It is not a legal textbook, and it is not a claims manual. It is a practical guide drawn from real project experience across jurisdictions, contract forms, and delivery models. Its purpose is to help project teams recognise dispute risks early and manage them intelligently, before positions harden and options narrow.
The concepts in this book are deliberately simple. They focus on behaviour, documentation, and decision-making during execution — the areas where disputes are most often created or prevented.
If this book helps teams pause earlier, document better, and address issues more clearly, it has served its purpose. ……………………………………
AUTHOR BIOGRAPHY Steven Chin is an international construction contracts and dispute-prevention specialist with extensive experience in contract administration, execution risk control, and dispute avoidance across Common Law, Civil Law, and Sharia-based jurisdictions.
His work focuses on helping contractors, project teams, and commercial leaders understand how contracts actually operate during execution, and how disciplined practices in documentation, authority, and decision-making can prevent disputes before they escalate. He has advised and trained teams on complex construction projects involving heavily amended standard forms, multi-party interfaces, and high commercial exposure. ………………………………………………
INDEX Chapter 1 Why This Book Exists Chapter 2 Disputes Do Not Appear Overnight Chapter 3 The Four Warning Signs That Always Appear Chapter 4 The White Horse — Contract Risk at Award Stage Chapter 5 The Red Horse — Obstruction and Interference During Execution Chapter 6 The Black Horse — When Payment Becomes Uncertain Chapter 7 The Pale Horse — When Blame Escalates and Discipline Breaks Down Chapter 8 Phase 1 — Contract Induction as Risk Control Chapter 9 Document Control as Dispute Insurance Chapter 10 Phase 2 — Execution Discipline and Dispute Containment Chapter 11 Putting It All Together
Appendix A — CETRIS™ Doctrine (Dispute Control — APR [Avoidance, Prevention & Resolution] Lifecycle) Appendix B — EUREKA Phase 1 SOP Manual Appendix C — HERCULES Phase 2 SOP Manual Appendix D — 1 Page Operational Summary (Dispute Control Management ) ……………………………………………….
SUBJECT INDEX Authority and Delegation → Chapters 4, 8, 9 Behavioural Risk → Chapters 2, 6, 7, 10 Black Horse (Payment Risk) → Chapters 3, 6 Claims and Entitlement → Chapters 2, 6, 9, 10 Contract Amendments → Chapters 3, 4, 8 Contract Induction (Phase 1) → Chapter 8 Dispute Containment → Chapters 7, 10, 11 Dispute Prevention → Chapters 1, 2, 3, 11 Document Control → Chapters 8, 9 Execution Discipline → Chapters 5, 8, 10 Four Horsemen of Construction Disputes → Chapter 3 Japanese Contractor Best Practice → Chapters 9, 11 Notices and Conditions Precedent → Chapters 4, 8, 9 Obstruction and Interference → Chapters 3, 5 Pale Horse (Escalation and Blame) → Chapters 3, 7 Payment and Certification → Chapter 6 Page | 4Phase 2 (Execution Review) → Chapter 10 Privity of Contract → Chapter 7 Programme and Delay → Chapters 5, 6 Red Horse (Obstruction) → Chapters 3, 5 Risk Allocation → Chapters 4, 8 Variations and Valuation → Chapters 5, 6 White Horse (Contract Risk) → Chapters 3, 4
…………………………………….. CHAPTER 1 WHY THIS BOOK EXISTS Construction disputes rarely begin with bad intentions. Most projects start with optimism, confidence, and good working relationships. Teams are motivated, schedules are agreed, and everyone expects the job to run more or less as planned. Yet despite this, disputes remain one of the most common and costly outcomes in construction projects around the world.
This book exists because that outcome is not inevitable. Disputes Are Not a Normal Part of Construction There is a long-standing belief in the industry that disputes are simply “part of the job”. This belief is dangerous.
While construction is complex, technically demanding, and commercially pressured, disputes are not a natural by-product of complexity. They are usually the result of unmanaged risk, weak execution discipline, and delayed decision-making, among other causes. Most disputes do not arise because parties deliberately act unfairly. They arise because: • Risks are accepted without full understanding • Assumptions are carried forward from past projects • Issues are allowed to drift unresolved • Documentation does not reflect what actually happened • Decisions are made under pressure without considering contractual consequences These are execution problems, not legal ones.
Why Legal Solutions Arrive Too Late When lawyers become involved, the project has usually already failed from a dispute-management perspective. By that stage: • Positions have hardened • Evidence is incomplete • Relationships are damaged • Commercial leverage has been lost Legal processes deal with the symptoms, not the causes. This book is not written to teach litigation or arbitration strategy. It is written to help project teams avoid reaching that point in the first place, inter alia.
The Real Origins of Disputes Construction disputes do not suddenly appear. They develop gradually, through small decisions that seem harmless at the time. For example: • An instruction is given informally “just to keep things moving” • A notice is delayed because no one wants to upset the other party • A variation is carried out without agreement “for now” • A drawing is issued without clear status • A meeting decision is assumed to be binding without confirmation Individually, these events feel manageable. Collectively, they become the foundation of disputes.
This book focuses on those moments — the ones that happen before disputes become visible.
Who This Book Is For This book is written for people who actually run construction projects, including but not limited to: • Project directors and project managers • Contract administrators and commercial managers • Engineers, quantity surveyors, and site managers • Senior management responsible for governance and risk It is not written for lawyers alone. It is written for people who must make decisions while work is ongoing, often with incomplete information and competing pressures.
The language used is intentionally practical. Legal concepts are explained only to the extent necessary to guide better execution behaviour. A Practical, Not Academic, Guide
This is not a textbook. It does not attempt to explain every clause, every case, or every jurisdictional nuance. Instead, it focuses on patterns that repeat across projects, regardless of contract form or legal system. Whether a project is governed by Common Law, Civil Law, or Sharia-based principles, the same execution failures tend to produce the same disputes. The objective of this book is to help readers recognise those patterns early and respond intelligently.
The Central Idea of This Book The central idea is simple: Most construction disputes can be prevented if risks are recognised early and managed deliberately during execution.
This requires: • Awareness of how contracts actually operate • Discipline in documentation and communication • Willingness to address issues early, even when uncomfortable These are skills that can be learned and applied in-house by experienced and well- trained teams.
What This Book Will Help You Do By the end of this book, readers should be able to: • Recognise early warning signs of disputes • Understand why certain site practices are dangerous • Appreciate the importance of document control and authority • See how small issues escalate into major claims • Implement simple disciplines that prevent disputes from forming
The chapters that follow will introduce the concept of the Four Horsemen of Construction Disputes — a practical framework for understanding how disputes develop and how they can be stopped. The aim is not to eliminate risk entirely. That is impossible. The aim is to control risk intelligently, so that disputes do not become the defining outcome of the project.
CHAPTER 2 DISPUTES DO NOT APPEAR OVERNIGHT Most construction disputes feel sudden. One day, work is progressing. The next, payment is withheld, a claim is rejected, or a formal notice of dispute is issued. To those involved on site, the escalation often feels abrupt and unfair.
In reality, disputes rarely arise suddenly. They develop quietly, over time, through a series of small events that are either ignored, misunderstood, or intentionally set aside for later, inter alia.
The Myth of the “Sudden Dispute” When disputes reach arbitration, adjudication, or court, they are often described as if they arose from a single defining incident. This is rarely true.
What is more common is a gradual build-up of unresolved issues, such as: • Instructions given without proper confirmation • Delays accepted informally without recording impact • Variations carried out without valuation clarity • Notices sent late or not sent at all • Correspondence that avoids clarity to preserve relationships
Each of these decisions is usually made with good intentions. Teams want to maintain progress, avoid conflict, and keep relationships workable. Ironically, it is this desire to “keep things smooth” that often creates the conditions for disputes later.
Small Decisions That Carry Large Consequences Construction projects are made up of thousands of decisions. Most of them are routine. Some, however, carry contractual consequences that are not immediately visible. For example: • Proceeding with additional work without instruction may protect progress today but undermine entitlement later. • Accepting delayed information without recording impact may seem cooperative but removes evidence of obstruction. • Delaying notices to avoid friction may preserve relationships in the short term but destroy rights in the long term. At the time, these decisions feel minor. Months later, they become decisive.
This is why disputes are better understood as a process, not an event.
How Issues Drift Into Disputes Disputes often grow through a predictable pattern: 1. An issue arises on site 2. The issue is addressed informally 3. Documentation is incomplete or unclear 4. The issue repeats or worsens 5. Commercial impact becomes visible 6. Positions harden 7. Formal dispute follows The critical point is usually Step 2 or Step 3, not Step 7.
Once parties reach formal dispute, recovery options are limited. The opportunity to manage the issue intelligently has already passed.
The Danger of Normalising Problems One of the most dangerous habits in construction is the normalisation of problems. Teams become accustomed to: • Late drawings • Slow approvals • Informal instructions • Partial certifications • Shifting responsibilities
When these conditions persist, they stop being treated as issues and start being treated as “how the project works”. This normalisation masks risk. By the time someone finally asks, “Is this acceptable under the contract?”, the damage has often already been done.
Why Memory Is Not Enough Another reason disputes do not appear overnight is that their early stages rely heavily on memory. People remember conversations differently. Meetings are recalled selectively. Agreements are assumed rather than confirmed. As time passes: • Personnel change • Site conditions evolve • Context is lost When disputes finally arise, memory becomes unreliable. Documents then take over as the primary source of truth. If those documents were never properly created, the dispute becomes difficult to resolve fairly.
Early Awareness Changes Outcomes Projects that avoid disputes tend to share one common feature: early awareness. Issues are: • Identified early • Discussed openly • Documented properly • Managed deliberately This does not mean every issue is escalated or turned into a claim. It means issues are not allowed to drift unexamined.
Early awareness allows teams to: • Adjust behaviour • Correct misunderstandings • Preserve entitlement • Maintain commercial balance These actions are far easier to take early than later.
What This Chapter Sets Up This chapter establishes an important foundation for the rest of the book: Disputes are the end result of unmanaged issues, not isolated failures. The chapters that follow will introduce a practical framework for recognising the warning signs that appear repeatedly on projects before disputes form. Understanding that disputes develop over time is the first step toward preventing them.
CHAPTER 3 THE FOUR WARNING SIGNS THAT ALWAYS APPEAR
Best depicted by the 4 Horsemen
Construction disputes may look different on the surface, but they are rarely unique. Across projects, jurisdictions, contract forms, and delivery models, the same warning signs appear again and again. They may be described using different language, but the underlying patterns remain consistent. This chapter introduces those patterns in a simple, practical way.
Why Patterns Matter More Than Clauses Many professionals approach disputes by focusing on individual clauses. While contract wording is important, disputes are rarely caused by a single clause alone. They are caused by how contracts are applied during execution.
Projects that end in disputes usually exhibit recognisable patterns long before formal claims are made. These patterns cut across: • Standard and amended contracts • Public and private projects • Local and international works * Common Law, Civil Law, and Sharia-based systems, inter alia Recognising these patterns early allows teams to intervene before disputes harden.
Introducing the Four Horsemen To make these patterns easy to recognise and remember, this book describes them as the Four Horsemen of Construction Disputes.
Each Horseman represents a category of risk that, if left unmanaged, drives disputes toward escalation. They are: 1. The White Horse — Contract risk at award stage 2. The Red Horse — Obstruction and interference during execution 3. The Black Horse — Payment imbalance and financial strain 4. The Pale Horse — Uncontrolled escalation and misdirected blame These are not sequential stages. They often appear together, overlap, or reinforce one another.
What matters is not the label, but the warning sign it represents.
The White Horse — Contract Unprepardness and ContractualBlindness at the Beginning The first warning sign appears before work even starts. Projects often proceed on the assumption that the contract is understood because it is based on a familiar form. In reality, amendments quietly change risk allocation, procedures, and entitlement. When teams do not fully understand those changes, they unknowingly operate outside the contract. This creates risk that only becomes visible later, when claims are rejected or rights are challenged.The White Horse represents unseen contract risk embedded at award stage.
The Red Horse — Obstruction During Execution The second warning sign appears during execution. Work is delayed, restricted, or disrupted. Drawings arrive late. Approvals take longer than expected. Access is constrained. Instructions are unclear or informal. On their own, these issues are manageable. They become dangerous when: • Their impact is not recorded • Their consequences are not addressed • Their repetition is normalised The Red Horse represents unacknowledged interference that undermines performance and entitlement.
The Black Horse — When Payment Becomes Uncertain The third warning sign relates to money. Construction is cash-intensive. When payment becomes uncertain, tension rises quickly. This warning sign appears when: • Variations accumulate without agreement • Certification is consistently reduced • Valuations lag behind work performed • Cashflow pressure becomes accepted as normal Financial imbalance changes behaviour. Teams become defensive, documentation becomes selective, and cooperation erodes. The Black Horse represents financial strain that fuels disputes. The Pale Horse — When Blame Escalates The final warning sign marks the breakdown of discipline. Issues are no longer managed between the contracting parties. Blame spreads to consultants, subcontractors, and third parties. Correspondence becomes defensive. Claims become broad. Positions harden.
At this stage, resolution becomes difficult because: • Focus shifts from problem-solving to positioning • Strong issues are diluted by weak ones • Credibility is undermined
The Pale Horse represents uncontrolled escalation. Why These Warning Signs Matter Each of these warning signs can exist on its own. What makes disputes inevitable is when they are allowed to coexist without intervention. For example: • Contract misunderstandings combined with obstruction • Obstruction combined with payment strain • Payment strain combined with blame escalation
When these conditions reinforce one another, disputes become almost unavoidable. Using the Four Horsemen as an Early Warning System
The Four Horsemen are not meant to diagnose disputes after they occur. They are meant to act as an early warning system during execution. When teams can identify which Horsemen are present on a project, they can: • Adjust behaviour • Improve documentation • Escalate issues intelligently • Contain problems before they mature The chapters that follow examine each Horseman in detail and explain how disciplined execution can prevent them from driving disputes.
……………………………. CHAPTER 4 THE WHITE HORSE — CONTRACT UNPREPAREDNESS & CONTRACTUAL BLINDNESS AT AWARD STAGE The first and most underestimated source of construction disputes appears before work begins. This is the stage where contracts are signed, teams are mobilised, and projects move quickly from tender to execution. It is also the stage where many disputes are quietly embedded into the project. This warning sign is represented by the White Horse.
Why Contract Risk Is Often Invisible At award stage, optimism is high. Projects have been won. Commercial pressure has eased. Teams are eager to start. In this environment, contracts are often treated as formalities rather than risk instruments. Common assumptions include: • “It’s a standard form.” • “We’ve worked under similar contracts before.” • “The legal team has reviewed it.” • “We’ll deal with issues when they arise.” These assumptions are rarely malicious. They are practical responses to time pressure. However, they are also dangerous.
The Reality of Amended Contracts Very few projects today proceed under unamended standard forms. Employers routinely amend contracts to shift risk, tighten procedures, and reduce entitlement. These amendments are often subtle and dispersed across the document. Examples include: • Shortened notice periods • Additional conditions precedent • Expanded discretion for certification • Restrictions on claims or extensions of time • Increased documentation requirements Individually, these amendments may appear manageable. Collectively, they change how the contract behaves. When execution teams are unaware of these changes, they unknowingly act outside the contract.
How the White Horse Manifests on Site The White Horse does not announce itself. It appears through everyday behaviour, such as: • Continuing past practices that are no longer contractually safe • Missing notices that were previously optional • Accepting informal instructions that no longer carry entitlement • Assuming cooperation will override strict procedures At the time, nothing seems wrong.
The consequences only become visible later, when: • Claims are rejected • Entitlement is challenged • Rights are deemed waived By then, it is too late to undo early decisions.
Contract Understanding Versus Contract Behaviour One of the most common misconceptions is that contract risk is solved through awareness alone. Reading the contract is not enough. What matters is how people behave under the contract during execution.
A contract can be understood intellectually but violated operationally. This gap between knowledge and behaviour is where disputes begin. The White Horse represents this gap. Why Early Correction Matters Contract risk is easiest to manage at the beginning of the project. At this stage: • Teams are flexible • Habits can be reset • Processes can be aligned • Document control can be structured Once work is underway and pressure builds, changing behaviour becomes far more difficult. This is why early intervention is critical.
The Role of Structured Contract Induction Effective management of the White Horse requires a structured approach to contract induction. This is not about explaining every clause.
It is about identifying: • What has changed • What behaviour must change • Where risk now sits A proper induction focuses on difference, not familiarity. It highlights where teams must stop doing what they are used to doing and start doing what the contract requires.
White Horse Warning Signs to Watch For Projects affected by the White Horse often show early indicators, including but not limited to: • Frequent references to “how we usually do it” • Uncertainty about notice requirements • Informal reliance on past relationships • Lack of clarity on authority and instruction limits • Weak document control from day one These are signals, not inconveniences.
Controlling the White Horse The White Horse does not require complex solutions. It requires: • Early awareness • Behavioural alignment • Clear execution rules • Disciplined documentation When contract risk is addressed early, many later disputes never arise.
………………………………………… This chapter examines how risk continues to develop during execution when obstruction and interference are not managed.
CHAPTER 5 THE RED HORSE — OBSTRUCTION AND INTERFERENCE DURING EXECUTION If the White Horse represents risk embedded at the start of a project, the Red Horse represents risk that develops while work is ongoing. This is the stage where most projects experience pressure. Programmes tighten. Interfaces multiply. Decisions are delayed. Information flows become strained. It is also the stage where cooperation is often tested.
The Red Horse appears when performance is hindered or obstructed, and the consequences of that hindrance are not properly recognised or managed.
Obstruction Is More Than Delay Many people associate obstruction with delay. This is only part of the picture. Obstruction can take many forms, including but not limited to: • Late issuance of drawings or information • Delayed approvals or responses • Restricted or partial access to work areas • Excessive review cycles • Conflicting or unclear instructions • Changes introduced without coordination Individually, these issues may appear minor. Collectively, they disrupt planned sequences, increase costs, and reduce productivity. What turns obstruction into a dispute driver is not the obstruction itself, but how it is treated.
Why Obstruction Is Often Tolerated On many projects, obstruction is tolerated in the name of progress. Common responses include: • “Let’s not make an issue of it.” • “We’ll recover later.” • “Everyone is under pressure.” • “We don’t want to escalate.” These responses are understandable. Projects are collaborative environments, and few teams want to be seen as difficult. However, tolerating obstruction without recording or addressing its impact creates hidden risk.
The Danger of Informal Workarounds When obstruction occurs, teams often work around it. They resequence activities. They accelerate elsewhere. They absorb inefficiencies quietly. While this may maintain progress, it also: • Masks the true impact of obstruction • Removes evidence of disruption • Weakens future entitlement
Later, when claims are made, the response is often: • “You managed to proceed.” • “There was no real impact.” • “The delay was mitigated.” The Red Horse thrives on this gap between reality and record.
Obstruction and Behavioural Drift As obstruction continues, behaviour begins to change. Teams become reactive rather than planned. Decisions are made tactically rather than strategically. Documentation becomes selective. This behavioural drift is dangerous because: • It normalises disruption • It weakens contractual discipline • It erodes entitlement incrementally By the time the impact is fully felt, the opportunity to manage it properly has passed.
Common Red Horse Warning Signs Projects affected by the Red Horse often show early indicators, including among others: • Repeated late information without formal response • Instructions issued verbally or informally • Regular resequencing without programme updates • Acceptance of partial access as normal • Lack of clear records linking cause and effect These signs indicate risk accumulation, not cooperation.
Why Recording Matters More Than Complaining Managing the Red Horse does not mean escalating every issue. It means recording reality accurately. Good practice involves: • Clearly identifying obstructive events • Recording when information was required versus received • Linking disruption to specific activities • Preserving evidence without aggressive tone This approach protects entitlement while maintaining working relationships.
Obstruction as a Dispute Multiplier Unmanaged obstruction rarely stays isolated. It often triggers: • Programme compression • Cost overruns • Increased variation claims • Payment disputes In this way, the Red Horse often feeds the Black Horse, creating financial strain.
Controlling the Red Horse The Red Horse can be controlled through disciplined execution, including but not limited to: • Early identification of obstruction • Accurate, contemporaneous records • Clear communication of impact • Structured review of recurring issues Ignoring obstruction does not make it disappear. It allows it to grow unchecked. The next chapter examines how financial imbalance and payment uncertainty amplify disputes once obstruction has taken hold.
……………………………………. CHAPTER 6
THE BLACK HORSE — WHEN PAYMENT BECOMES UNCERTAIN If the Red Horse introduces disruption during execution, the Black Horse introduces financial strain. This is the stage where disputes begin to feel unavoidable.
Construction is a cash-intensive business. Labour, materials, plant, preliminaries, financing costs, and overheads continue regardless of certification cycles. When payment becomes uncertain or unbalanced, pressure rises quickly across the project. The Black Horse represents financial imbalance and the behavioural changes that follow.
Why Payment Issues Escalate So Quickly Most construction teams can tolerate inconvenience and disruption. They cannot tolerate prolonged uncertainty over payment. Payment issues affect: • Cashflow • Supplier and subcontractor relationships • Site morale • Management confidence Once financial strain sets in, cooperation becomes harder to sustain. This is why payment-related disputes escalate faster than most other issues.
How the Black Horse Appears on Projects The Black Horse rarely appears suddenly. It develops through patterns such as: • Variations carried out without agreement on valuation • Provisional sums remaining unresolved • Repeated reductions in interim certifications • Valuations consistently below actual work performed • Delays between work execution and payment At first, teams may accept these issues as temporary. Over time, they become structural.
Variation Accumulation and Valuation Drift One of the most common triggers of the Black Horse is variation accumulation. Additional work is instructed or implied. The work is carried out to maintain progress. Valuation is deferred. Common justifications include: • “We’ll agree the value later.” • “It will be sorted in the final account.” • “Let’s keep things moving.” This approach weakens commercial leverage.
As time passes: • The volume of variations increases • Records become less precise • Positions harden • Valuation becomes more contentious By the time formal valuation discussions begin, trust has already eroded.
Certification Practices and Perceived Fairness Payment disputes are not driven solely by numbers. They are driven by perceived fairness. When certification is consistently reduced without clear explanation: • Confidence is lost • Suspicion grows • Defensive behaviour emerges Even where contracts allow discretion, how that discretion is exercised matters.
A pattern of under-certification creates the impression that the commercial balance of the contract has shifted unfairly. This perception fuels disputes regardless of legal entitlement.
The Behavioural Impact of Financial Pressure Once the Black Horse takes hold, behaviour changes. Teams may: • Become reluctant to cooperate • Escalate correspondence unnecessarily • Focus on claim preparation rather than execution • Withhold information as leverage These behaviours further damage relationships and reduce the likelihood of early resolution. Financial pressure rarely stays contained. It spreads across the project.
Why Final Accounts Rarely Fix the Problem There is a common belief that unresolved payment issues will be addressed in the final account. In practice, this rarely works. By final account stage: • Evidence is fragmented • Personnel may have changed • Commercial positions are entrenched • Emotions have accumulated Final account negotiations then become battlegrounds rather than reconciliation exercises. The Black Horse ensures that by this stage, trust has already been lost.
Black Horse Warning Signs to Watch For Projects affected by the Black Horse often display early indicators, including but not limited to: • Growing gaps between work done and work paid • Increasing reliance on future adjustments • Informal assurances replacing written agreement • Escalating commercial correspondence • Cashflow discussions dominating project meetings These are warning signs, not routine issues.
Controlling the Black Horse The Black Horse cannot be controlled through legal argument alone. It requires: • Timely valuation of work • Clear linkage between instruction and payment • Transparent certification practices • Early discussion of commercial imbalance When payment remains aligned with work performed, disputes are far less likely to escalate.
CHAPTER 7 This chapter examines what happens when disputes move beyond commercial imbalance and blame begins to spread uncontrollably. THE PALE HORSE — WHEN BLAME ESCALATES AND DISCIPLINE BREAKS DOWN The Pale Horse marks the most dangerous stage in the life of a construction dispute. By the time this warning sign appears, the project is no longer dealing with isolated issues. Instead, problems have spread across multiple parties, and the original causes are often obscured by emotion, defensiveness, and positioning. This is the stage where discipline breaks down and recovery becomes difficult. How the Pale Horse Emerges The Pale Horse does not appear suddenly. It usually emerges after the White, Red, and Black Horses have been allowed to operate without control. Typical conditions include: • Long-standing contract misunderstandings • Unresolved obstruction and disruption • Prolonged payment imbalance As pressure builds, parties begin to look outward for responsibility. Blame starts to spread. From Contractual Issues to Blame Culture At this stage, the focus shifts away from solving problems and toward protecting positions. Common signs include: • Broad claims naming multiple parties • Consultants drawn into employer–contractor disputes • Defensive correspondence copied widely • Attempts to assign responsibility beyond contractual boundaries What was once a manageable contractual issue becomes a multi-party conflict. This shift is rarely helpful. ……………………………………
The Illusion of Strength in Broad Claims When disputes escalate, there is often a temptation to issue broad, aggressive claims. These claims may: • Cite multiple causes • Target several parties • Assert overlapping entitlements At first glance, this approach can feel powerful.
In practice, it is usually counterproductive. Broad claims tend to: • Dilute strong arguments with weak ones • Reduce credibility • Make resolution harder Decision-makers are forced to sift through excessive material, increasing scepticism rather than sympathy.
Privity of Contract and Misplaced Expectations One of the most common legal misunderstandings during this stage relates to privity of contract. Teams may assume that because a consultant, subcontractor, or third party contributed to a problem, they can be held contractually responsible.
In reality: • Contractual rights and obligations exist only between contracting parties • Responsibility cannot be imposed simply because someone was involved • Many grievances fall outside contractual remedies This misunderstanding fuels frustration and escalates disputes unnecessarily.
Behavioural Breakdown and Its Consequences As blame spreads, behaviour deteriorates. Teams may: • Stop cooperating • Withhold information • Escalate correspondence unnecessarily • Adopt adversarial language This behaviour further entrenches positions and reduces the possibility of early settlement.
At this point, even reasonable proposals are viewed with suspicion. Pale Horse Warning Signs to Watch For Projects affected by the Pale Horse often display indicators such as: • Increasingly aggressive correspondence • Copying senior management excessively • Claims that lack focus or clear structure • Repeated references to “who is at fault” rather than “what happened” These are signs that discipline has been lost.
Why the Pale Horse Is So Difficult to Control Unlike earlier warning signs, the Pale Horse is difficult to reverse once established. This is because: • Trust has eroded • Positions are entrenched • Evidence is being assembled selectively At this stage, formal dispute processes often become unavoidable.
Preventing the Pale Horse The most effective way to deal with the Pale Horse is to prevent it from appearing. This requires: • Early control of contract risk • Proper management of obstruction • Fair and timely payment practices • Disciplined documentation and communication Once blame spreads, options narrow significantly.
The Lesson of the Pale Horse The Pale Horse serves as a warning. When disputes move beyond facts and into blame, control is lost. The chapters that follow shift focus away from warning signs and toward practical implementation — how disciplined teams can prevent disputes from reaching this stage in the first place. ……………………………………
CHAPTER 8 This is a TOTAL Dispute Control Programme that I developed and refined over the years. I have found it worked very well in Dispute Avoidance, Prevention and Resolution. It is a two Phase programme and must be executed in sequence for maximum impact and to the entire Contract and Project execution teams assigned to the Project.
Best part is the Cetris System is human centric and as such can be implemented In- House by any Contractor with by an experienced Contracts Professional with the relevant essential knowledge.
It is meant to replace the current high priced retainer advisory system from big names claims consultancies thanks to its low implementation cost by being In-House capable.
PHASE 1 — CONTRACT INDUCTION AS RISK CONTROL If the earlier chapters explain why disputes arise, this chapter explains where they can be stopped. Phase 1 represents the most effective and least disruptive opportunity to prevent disputes. It takes place before execution pressure distorts behaviour and before poor habits become entrenched. Phase 1 is not training for training’s sake. It is risk control.
Why Contract Induction Is Commonly Misunderstood On many projects, contract induction is treated as a formality. A short briefing is conducted. The contract is described as “standard”. Teams are told to proceed. This approach creates a false sense of security. Contracts do not cause disputes by being complicated. They cause disputes when teams assume familiarity where none exists.
Phase 1 exists to remove that assumption. Phase 1 Is About Behaviour, Not Clauses A common mistake is to treat contract induction as an exercise in clause explanation. That is rarely effective. What matters is not whether teams can quote clauses, but whether they behave differently under the amended contract. Phase 1 therefore focuses on identifying: • What has changed from the standard form • Where risk has shifted • Which familiar practices are no longer safe • Which actions now require strict discipline The objective is to answer one practical question: “What must we stop doing, start doing, or do differently on this project?”
What Phase 1 Covers in Practice A proper Phase 1 contract induction addresses execution reality, including but not limited to: • Amended clauses that affect entitlement • Notice timing and conditions precedent • Authority limits and instruction validity • Certification and valuation mechanisms • Risk allocation that differs from past projects This is not an academic review. It is a focused discussion on how the contract behaves during execution.
Document Control as a Mandatory Phase 1 Component Contract understanding alone does not protect entitlement. Many disputes are lost because the documents issued on site do not support the position later taken. For this reason, Phase 1 must include a document control review and revamp. This typically examines: • Who is authorised to issue contractual correspondence • How instructions must be issued and titled • How notices are identified, tracked, and preserved • How drawings and IFCs are formally released • How responses and reservations of rights are recorded The aim is simple: If a document cannot withstand later scrutiny, it should not be relied upon now.
Common Document Control Failures Phase 1 Prevents Phase 1 addresses frequent failures such as: • Informal instructions relied upon as contractual • Drawings issued “for information” treated as IFC • Notices sent late or without clear reference • Silence assumed to mean agreement • Authority exceeded without consequence These failures are rarely deliberate. They are habits formed under pressure. Phase 1 resets those habits. Phase 1 Deliverables That Matter
A proper Phase 1 does not end with a presentation. It produces practical execution tools, including among others: 1. Contract Amendment Summary — plain language explanation of what has changed 2. Clause Deviation Heatmap — highlighting where discipline is required 3. Authority & Instruction Matrix — clarifying who can bind the contract 4. Contract-Focused Document Control SOP — aligned to the actual contract 5. Early Warning & Notice Checklist — simple site-level guidance 6. Project-Specific Risk Notes — highlighting common traps These deliverables guide daily behaviour long after the induction session ends.
Why Phase 1 Works Phase 1 works because it intervenes early. At this stage: • Teams are receptive • Processes are flexible • Behaviour can be aligned • Discipline can be established Once execution pressure builds, these corrections become far harder to implement. Phase 1 as the Foundation of Dispute Prevention Phase 1 does not eliminate risk. It controls risk intelligently. Projects that implement Phase 1 properly: • Miss fewer notices • Issue clearer correspondence • Manage instructions more carefully • Preserve entitlement more effectively Many later disputes never arise because the foundations were set correctly. The next chapter examines how disciplined teams maintain this control during execution, before issues have a chance to escalate.
………………………………… CHAPTER 9 DOCUMENT CONTROL (Essential as Dispute “Insurance”) *** The Insurance Analogy Explained Insurance works by paying premiums before loss occurs. Document control works the same way. Every properly issued instruction, notice, response, and reservation of rights is a premium paid toward future protection. Projects that neglect document control may appear to save time in the short term. In reality, they are uninsured.
Having done that we proceed the journey by reiterating Document control is one of the most misunderstood functions in construction. It is often viewed as administrative support — a back-office activity concerned with filing, numbering, and distribution. When projects are under pressure, document control is one of the first disciplines to be relaxed. This is a serious mistake. In reality, document control is dispute insurance.
Why Documents Decide Disputes Construction disputes are rarely decided by memory. They are decided months or years after events occur, by people who were not present on site. By that time: • Personnel may have changed • Site conditions have evolved • Recollections differ • Context has been lost What remains are documents. Emails. Letters. Notices. Drawings. Records of meetings. If these documents are weak, unclear, or inconsistent, entitlement becomes difficult to prove regardless of what actually happened.
The Difference Between Activity and Evidence Many projects generate a large volume of documents. Quantity, however, is not quality. A project can be busy with correspondence and still lack usable evidence. Evidence must: • Be issued by the correct authority • Clearly state its purpose • Be timely • Be traceable to contractual provisions • Preserve rights without unnecessary aggression Document control ensures that documents meet these requirements.
Common Misconceptions About Document Control A common misconception is that document control is about compliance with systems. In reality, it is about protecting contractual position. Another misconception is that document control becomes important only when disputes arise. By then, it is too late. Document control must operate from day one.
How Entitlement Is Quietly Lost Through Documents Many disputes are lost not because entitlement did not exist, but because it was not preserved properly. Common document-related failures include, among others: • Instructions issued informally and later denied • Notices issued late or without proper reference • Responses that acknowledge issues without reserving rights • Silence interpreted as acceptance • Drawings issued with unclear status Each of these failures weakens entitlement incrementally. By the time disputes arise, the position is already compromised.
Writing for the Future Reader One of the most important principles of document control is understanding who the future reader will be. That reader may be: • Senior management • An auditor • An adjudicator • An arbitrator • An insurer Documents should therefore be written clearly, factually, and calmly, without assuming shared understanding. Good documents explain: • What happened • When it happened • Why it matters • What the contractual implications are They do not rely on inference. Tone Matters More Than Many Realise The tone of correspondence often has a greater impact than the content. Aggressive language may feel strong in the moment, but it often undermines credibility later. Equally, overly accommodating language can be read as acceptance or waiver. Effective document control balances firmness with professionalism. It records facts, preserves rights, and avoids unnecessary escalation.
Document Control and Authority Another critical aspect of document control is authority. Documents issued by individuals without contractual authority may have no legal effect, regardless of intent. Document control must therefore ensure that: • Instructions come from authorised persons • Responses are issued by appropriate representatives • Authority limits are respected and enforced Failure to control authority creates ambiguity that later fuels disputes.
Practical Indicators of Strong Document Control Projects with strong document control typically demonstrate: • Clear document titles and references • Consistent use of contractual terminology • Timely issuance of notices • Traceable correspondence chains • Calm, factual tone These projects are not dispute-free, but they are dispute-resilient.
The Cost of Weak Document Control Weak document control does not fail dramatically. It fails quietly. Entitlement erodes one document at a time until, eventually, there is little left to rely on. By then, the damage cannot be undone.
The Role of Phase 1 and Phase 2 Document control is established during Phase 1 and maintained through Phase 2. Phase 1 sets the rules. Phase 2 enforces discipline. Together, they ensure that documentation supports execution reality rather than contradicting it. The Central Lesson of This Chapter If there is one lesson to take from this chapter, it is this: If a document cannot confidently stand up later, it should not be relied upon now. This mindset alone prevents many disputes, among others. The next chapter examines how disciplined teams maintain this control during execution through structured discussion and early containment.