Infrastructure Contract Drafting

Module 2: Basics and Structure of Contract

06 Sep 2025

Presented by: Contact Info:

Dr. Pradeep Reddy pradeepreddyindia@[Link]
Advocate & Arbitration Professional +91 7702967275
 Disclaimer
 This presentation should NOT be interpreted as legal or technical advice. This
presentation is intended to help a person understand the topic discussed here, merely
as a preliminary educational tool. This presentation does NOT create any professional
or commercial relationship.
 This topic is dynamic and vast. It is difficult, or probably impossible to be up to date
with the Law that applies to every case. Errors and omissions are possible.
 The presenter, the presenter’s firm, or the Institute organizing this event, DOES NOT
accept any responsibility for the content, accuracy or completeness of the information
presented.
 All rights reserved. This presentation shall NOT be used or distributed without the
written authorization of the Presenter.
2
 Notes
 Do not believe anyone. Verify for yourself.
 Traditional beliefs may not be up to date. The law is dynamic.
 Every case is unique.
 Every Rule has an Exception. Every Exception has a Rule.

3
Types of Construction Contracts

4
 By Pricing Structure
 Lump Sum
 Cost Plus
 Unit Price
 Time and Materials

5
 By Project Delivery Method
 Design – Bid – Build
 Design – Build
 Engineering, Procurement, and Construction
 Construction Management at-risk (CMAR): The CMAR provides a guaranteed
maximum price and is contractually liable for cost overruns.
 Construction Management as agent: The CMAS acts as the owner's agent, without a
financial guarantee for the project's cost.

6
Basics

7
 Elements for a Valid Contract
 Offer and acceptance
 Intention to create legal relations
 Consideration
 Capacity to contract
 Free consent (including no misrepresentation or mistake)
 Lawful object
 Certainty of terms

8
 Types of Contract Formation
 Express contracts
 Written
 Oral
 Implied contracts
 Inferred from the actions, conduct, or circumstances of the parties
 Executed contracts
 All parties have fulfilled their obligations
 Executory contracts
 Obligations under the agreement have yet to be completed

9
 Types of Contract Formation
 Valid Contract
 meets all legal requirements
 Void Contract
 legally unenforceable from the start
 Voidable contracts
 Initially valid but can be made void at the option of one party

10
Start Drafting

11
 Drafting
 Offer and acceptance
 Tenders = Notice Inviting Offers or Offer to Perform
 NIT = Notice Inviting Tenders
 Tender / Bid submitted by Contractor = Offer
 LOA / LOI = Letter of Acceptance / Letter of Intent
 Drafting:
 WHEREAS the Owner has issued a Notice Inviting Offers for the Work of …
 WHEREAS the Contractor submitted a Tender dated …
 WHEREAS the Owner has accepted the Contractor's tender subject to the terms and
conditions set forth herein …

12
 Drafting
 Intention to create legal relations
 In commercial contracts, the intention to create legal relations is presumed
 To be extra careful, sometimes expressly incorporated
 Drafting:
 WHEREAS both the Parties now intend to enter into a legal relationship for the
said Work as per the following terms and conditions…

13
 Drafting
 Consideration
 Need not be money
 Quid pro quo (give and take)
 Need not be of equal “value”
 Drafting:
 The Contractor shall complete the said Work as per the said terms & conditions,
and for the said Work the Owner shall pay the Contractor an amount of Rs. One
Lakh in accordance with the payment schedule as stated in Clause 10.

14
 Drafting
 Capacity to contract
 Major and of Sound Mind for individual
 Authorisation for an entity
 Drafting:
 This Agreement is made and entered into this [Date] by and between [Owner's full legal
name] an individual and [Contractor's full legal name] an individual …
 Each party represents and warrants to the other that the individual signing this Agreement
on its behalf is duly authorized to execute this Agreement and to bind the party to its terms

15
 Drafting
 Free consent
 Voluntary; free from undue influence, fraud, or coercion; no misrepresentation or
mistake
 Drafting:
 By signing below both the Parties state that they have signed the contract
voluntarily, and free from any undue influence or fraud or coercion.
 Neither party relied on any verbal statements or representations not explicitly
contained within this written contract

16
 Drafting
 Lawful object
 Can be determined only by reading the Contract
 Drafting:
 The Contractor shall comply with all local, state, & central government laws,
ordinances, building codes, rules, regulations, Acts, Codes, or any other
requirements as applicable to the performance of the Work

17
 Drafting
 Certainty of terms
 Can be determined only by reading the Contract
 Drafting:
 'Work' shall mean all construction, materials, equipment, and services required to
construct the Project in accordance with the Drawings and Specifications

18
 Question to Ponder

If only these 7 elements are sufficient, why do we need such

lengthy / big contracts?

19
 Objectives of a Contract
 Establish a clear record of rights and responsibilities
 Allocate and manage risk
 Provide legal protection and remedies
 Control costs and set a project budget
 Define the project's scope, timeline, and quality
 Establish a mechanism for dispute resolution
 Ensure regulatory compliance
 Facilitate collaboration and good faith

20
Single Document Contract

21
 Single Document Contract
 One consolidated document
 All terms and conditions included in a continuous manner
 More common for smaller and straightforward projects

22
 Single Document Contract
Benefits Drawbacks
 Simplicity and clarity  Lack of flexibility
 Cost certainty  Not suitable for complex projects
 Streamlined administration  Risks on one of the Party’s are more
 No need to track and cross-reference  Requires more customisation for
multiple documents every project
 Expedited process

23
 Single Document Contract
Drafting:
 Plain language: Usually drafters use straightforward language and avoid overly
complex legal jargon that could confuse non-legal professionals
 Limited definitions: Since all terms are within one document, the need for extensive
definitions is minimized. However, any technical or industry-specific terms must still
be clearly defined.
 Detailed clauses: Because there are no additional documents to reference, all key
clauses—covering scope, payment, schedule, insurance, and dispute resolution—must
be fully detailed within the single text.
 No incorporation by reference: There is no need for clauses that incorporate other
documents by reference, as this approach is built on self-sufficiency 24
Multi-Document Contract

25
 Multi-Document Contract
 The Agreement along with a list of other documents that form part of the contract
 General Conditions
 Special Conditions
 Specifications
 Drawings
 Schedules
 Bill of Quantities
 Change Orders and Addenda

26
 Multi-Document Contract
 Incorporation by Reference: When drafting, the main agreement must clearly state that
all other documents are "incorporated by reference" and made a binding part of the
contract.
 Order of Precedence: A critical clause in a multi-document contract is the "Order of
Precedence" or "Priority of Documents." This clause establishes a hierarchy for the
documents in case of a conflict or discrepancy between them.
 Comprehensive Management: All contract documents must be kept current. This
involves tracking revisions, managing approvals, and communicating changes to all
stakeholders to ensure everyone is working with the latest versions.

27
 Multi-Document Contract
Benefits Risks
 Comprehensive Detail  Coordination Challenges
 Flexibility  Hierarchy Disputes
 Clear Risk Allocation  Higher Administrative Costs
 Can be used repeatedly for several
projects with minimal changes

28
 Multi-Document Contract
Drafting:
 Incorporation by reference: The main agreement must contain a clear and explicit
clause that legally binds all referenced external documents as if they were fully
included in the main text.
 Order of precedence: A critical clause must establish a clear hierarchy for resolving
conflicts between documents.
 Consistent terminology: With multiple authors contributing to different documents
(e.g., specifications by an engineer, drawings by an architect), consistent use of
defined terms is crucial to avoid ambiguity.

29
 Multi-Document Contract
Drafting:
 Comprehensive document management: This includes maintaining a master list of all
contract documents, version control, and clearly identifying and labeling changes
 General vs special conditions: Drafters must distinguish between boilerplate general
conditions (covering standard issues) and project-specific special conditions, using the
latter to modify the former as needed.
 Risk allocation: The structure must be intentional about how risk is distributed.

30
 Multi-Document Contract
Experiences:
 Two documents related to the same Work signed on the same date.
 Clause restricting “future changes” in the “first set” of documents. Clause
“overruling” the earlier document provisions in the “current set” of document.
 Arbitration Clause / Jurisdiction Clause incorporation.
 Supplementary Agreement or Novation.

31
Judicial Notice of Contract Framework

32
 Judicial Notice of Contract Framework
 George Mitchell Chesterhall Ltd vs Finney Lock Seeds Ltd
 [1983] QB 284 at 300-301 (CA)
 Lord Denning MR wrote: “I do hope, however, that we shall not often have to
consider the newfound analysis of contractual obligations into “primary obligations”,
“secondary obligations”, “general secondary obligations” and “anticipatory secondary
obligations”. No doubt it is logical enough but it is too esoteric altogether. It is fit
only for the rarified atmosphere of the House of Lords. Not at all for the chambers of
the practitioners. Let alone for the student at the university.”

33
 Judicial Notice of Contract Framework
Framework after Lord Denning’s Opinion:
1. Primary obligation
 A primary obligation is the duty of performance that the parties originally agreed upon
and intended to fulfill. It is the main, substantive promise in the contract.
 Example: A contractor's obligation to build a house to specified plans, or a supplier's
obligation to deliver a certain quantity of goods.

34
 Judicial Notice of Contract Framework
Framework after Lord Denning’s Opinion:
2. Secondary obligation
 A secondary obligation is a remedial duty that arises automatically upon the breach of
a primary obligation. This is not something the parties actively perform but is a legal
consequence of a breach.
 Example: The obligation of a party in breach to pay damages to the innocent party.

35
 Judicial Notice of Contract Framework
Framework after Lord Denning’s Opinion:
3. General secondary obligation
 When a breach is so fundamental that the contract is terminated, the innocent party’s
primary obligations cease, and the breaching party acquires a liability to compensate
for the loss of the contract.
 Example: If a contractor completely abandons a project, the owner's primary
obligation to pay for the work is discharged. A general secondary obligation then
arises for the breaching party to compensate the innocent party for repudiation of the
entire contract.

36
 Judicial Notice of Contract Framework
Framework after Lord Denning’s Opinion:
4. Anticipatory secondary obligation
 This obligation arises when one party informs the other of their intention to not
perform a primary obligation in the future, known as an anticipatory breach. The
innocent party may then be able to terminate the contract and claim damages
immediately, rather than waiting for the actual breach to occur. This gives the innocent
party an option to mitigate their losses early.
 Example: If a supplier notifies a contractor that they will not deliver materials next
month as scheduled, the contractor does not have to wait for the missed delivery. An
anticipatory secondary obligation arises, allowing the contractor to immediately seek a
new supplier and sue the original supplier for damages.
37
 Framework Learnt from Lord Denning
Functional Framework
 Parties and Recitals: Who is involved and why.
 Definitions: Clear interpretations of terms.
 Commercial Terms (The "Operative" Clauses): Scope of Work, Price, Payment,
Schedule.
 Risk Allocation (The "Secondary" Clauses): Indemnification, Limitation of Liability,
Insurance, Force Majeure.
 Operational Clauses: Notices, Intellectual Property, Confidentiality.
 Legal Mechanics (The "Tertiary" Clauses): Entire Agreement, Governing Law,
Dispute Resolution
38
 Framework Learnt from Lord Denning
Risk-Based Framework
 Identify risks early: Use a risk matrix to identify all potential risks associated with the
project, such as financial, operational, and legal risks.
 Allocate risks deliberately: Draft clauses to explicitly allocate risks to the party best
able to manage them. For example, the schedule clause should address the risk of
delay, and the payment clause should mitigate credit risk.
 Provide appropriate remedies: Ensure that for every major risk, a corresponding
remedy or mitigation is provided, such as liquidated damages for delay or a clear
dispute resolution procedure

39
 Framework Learnt from Lord Denning
Plain English Framework
 Clarity over elegance: Avoid archaic and overly formal language where simpler terms
will suffice. The goal is to avoid ambiguity, not to impress with complex vocabulary.
 Active voice: Use the active voice to make clear who is responsible for an action. For
example, "The Contractor shall submit a payment application," not "A payment
application shall be submitted by the Contractor."
 Audience awareness: Draft with the end-users in mind—the project managers, site
supervisors, and financial teams—to ensure the contract is a practical tool, not just a
legal one.
 Visual aids: Utilize headings, tables, and lists to break up dense text and improve
readability, especially for complex technical data 40
 Framework Learnt from Lord Denning
Modular Framework
 Standardized clauses: Create and approve standard versions of common clauses (e.g.,
Force Majeure, Confidentiality, Dispute Resolution).
 Playbooks: For large organizations, use playbooks that define acceptable deviations
from standard clauses and provide guidance on negotiation strategy.
 Automation: Utilize Contract Lifecycle Management (CLM) software to streamline
the process of assembling contracts from the clause library, which helps ensure
consistency and speed.

41
 Judicial Notice of Contract Framework
 Investors Compensation Scheme Ltd v West Bromwich Building Society [1998]
 Lord Hoffmann's judgment in this case is widely regarded as establishing the
modern, contextual approach to contractual interpretation in English law.
 While not a drafting framework itself, the five principles of interpretation he set out
have profound implications for how contracts should be drafted.

42
 Judicial Notice of Contract Framework
Lord Hoffmann's five principles of interpretation
1. Meaning to a reasonable person: Draft with the understanding that a court will give a
document the meaning it would convey to a reasonable person who has all the relevant
background information reasonably available to the parties. This means anticipating how
a third party might read and interpret your language.
2. Context is key: Use the "matrix of fact" (the entire background known to the parties)
to inform the drafting. Avoid relying on literal, "dictionary" meanings of words if they
lead to an uncommercial or absurd result in the context of the deal.

43
 Judicial Notice of Contract Framework
Lord Hoffmann's five principles of interpretation
3. Presumption against mistake: While courts presume parties don't make linguistic
mistakes, a drafter must be careful. If the language clearly contradicts the commercial
reality, a court may find a mistake. Avoid this by drafting clearly and consistently.
4. Exclusion of prior negotiations: Previous negotiations are generally excluded from
interpreting the final contract. This reinforces the importance of the "entire agreement"
clause and ensures that only the written document governs the agreement.
5. Commercial common sense prevails: Draft to reflect the commercial reality and
business common sense of the transaction. If a clause has two possible interpretations, a
court will favor the one that makes more commercial sense.

44
 Judicial Notice of Contract Framework
 Thornton v Shoe Lane Parking Ltd [1971]
 This Court established critical principles regarding the incorporation of terms into a
contract, particularly in situations involving automatic processes and standard-form
agreements.
1. Reasonable notice of onerous terms: If a clause is particularly onerous or unusual, the
party seeking to rely on it must take reasonable steps to bring it to the other party's
attention. A drafter cannot bury a significant liability exclusion in small, inconspicuous
print.

45
 Judicial Notice of Contract Framework
2. Timing of contract formation: A contract's terms must be known before or at the time
of contract formation. This means terms added later—for example, on the back of a
ticket issued after payment—are not part of the contract.
3. Clear communication in automated settings: For automated contracts (e.g., via a
machine), the offer is made clear at the entrance, and acceptance is irreversible once the
customer proceeds. Terms displayed after this point will not be incorporated.

46
 Judicial Notice of Contract Framework
 L'Estrange v F Graucob Ltd [1934] 2 KB 394
 This older but foundational case established the "signature rule," which states that a
person who signs a contractual document is bound by its terms, whether or not they
have read them. However, modern interpretations and subsequent legislation have
limited its application.
1. Signature as acceptance: A signature is strong evidence of assent to a contract's terms.
As a drafter, obtaining a signature provides the most robust form of consent.

47
 Judicial Notice of Contract Framework
2. Beware of misrepresentation: The rule is nullified by fraud or misrepresentation. The
drafter must not misrepresent any aspect of the contract's terms or content to the other
party.
3. Limitations in consumer contexts: While important for commercial contracts, drafters
should be aware of statutory restrictions in business-to-consumer (B2C) contexts.

48
Structure of a Contract

49
 Structure of a Contract
 Preliminary section
 The preliminary section provides a foundational understanding of the contract and the
parties involved.
 Title: Clearly identifies the document, such as "Construction Agreement,"
"Subcontract," or "Contract for Services".
 Parties: States the full legal names, addresses, and contact information of the
parties entering the contract. It also assigns shorthand identifiers, such as "Owner"
and "Contractor," to be used throughout the document.

50
 Structure of a Contract
 Preliminary section
 Recitals (Background): These "WHEREAS" clauses provide the context and
background for the agreement. They explain the project's purpose and the events
that led to the contract, helping to define the intent of the parties.
 Words of Agreement: A formal statement that signifies the parties' mutual consent
to the terms and conditions that follow.
 Defined Terms: A section that defines key terms to ensure clarity and consistency
throughout the document, such as "Work," "Project," or "Effective Date".

51
 Structure of a Contract
 Operative clauses
 The operative clauses contain the core terms and conditions of the agreement,
outlining the rights and obligations of the parties.
 Scope of Work (SOW): This is a detailed description of the work to be performed.
It often incorporates specifications, drawings, and other exhibits by reference.
 Contract Price and Payment Terms: Specifies the total price for the project and
establishes the payment structure, schedule, and procedures (e.g., lump sum,
progress payments).
 Project Timeline and Milestones: Sets clear start and completion dates and
includes a project schedule or a list of key milestones. It may also define
procedures for extensions of time.
52
 Structure of a Contract
 Operative clauses
 Change Orders and Variations: Defines the process for how modifications to the
scope, price, or schedule will be handled.
 Responsibilities of Parties: Details specific duties of each party, such as contractor
providing labor and materials and the owner providing site access or permits.
 Representations and Warranties: These clauses contain factual promises by the
parties. The contractor, for example, typically warrants that the work will be free
from defects.
 Insurance and Indemnification: Requires parties to carry specific insurance (e.g.,
general liability, workers' compensation) and defines who is responsible for
covering losses or damages.
53
 Structure of a Contract
 Standard (boilerplate) clauses
 These administrative and legal clauses are common to most commercial contracts.
 Dispute Resolution: Specifies the method for resolving disputes, such as
negotiation, mediation, or arbitration, to avoid costly litigation.
 Confidentiality: A non-disclosure clause that protects any sensitive information
exchanged during the project.
 Force Majeure: Excuses a party's non-performance for events beyond their control,
such as natural disasters or strikes.
 Termination Clause: Outlines the conditions and procedures for ending the contract
before completion, including for cause or for convenience.

54
 Structure of a Contract
 Standard (boilerplate) clauses
 Governing Law and Jurisdiction: Specifies which laws will govern the contract
and where any legal action must be filed.
 Notices: Sets forth the official method and addresses for delivering legal notices
between the parties.
 Entire Agreement: Confirms that the written contract is the final and complete
agreement between the parties, superseding all prior discussions.
 Severability: Ensures that if one part of the contract is found to be unenforceable,
the rest of the agreement remains in effect.

55
 Structure of a Contract
 Concluding section
 The concluding section executes and finalizes the agreement.
 Signature Block: Provides spaces for the authorized representatives of each party
to sign and date the document, making it legally binding.
 Annexures/Exhibits: This section references and includes all supporting documents
that are formally incorporated into the contract, such as drawings, specifications,
and schedules.

56
 Structure of a Contract
Standard:
This Course:
 Preliminary Section  Primary Clauses
 Operative Clauses  Secondary Clauses
 Standard (boilerplate) clauses  Tertiary Clauses
 Concluding section

“overly simplified” only for the

purpose of clarity

57
FIDIC / JTC / NEC

58
 FIDIC (International Federation of Consulting Engineers)
 Structured and formal, designed for international projects where parties may be from
different legal jurisdictions
 FIDIC contracts are typically modular, consisting of two parts:
 General Conditions (Part I): These contain the standard clauses, which FIDIC
intends to be used without amendment. These clauses are based on international
practice and set out the standard risk allocation.
 Particular Conditions (Part II): These allow for project-specific amendments and
additions to the General Conditions to reflect the governing law, site conditions,
and commercial requirements. FIDIC provides guidance on how to draft these
Particular Conditions to avoid contradicting the fundamental principles of the
contract, often referred to as the "Golden Principles".
59
 FIDIC
 Legal language: The language is formal and legalistic, reflecting a civil law tradition
and aiming for precise and comprehensive coverage of all eventualities. The emphasis
is on contractual certainty and a clear, defined process for claims and dispute
resolution.
 Risk allocation: The risk allocation is based on a deliberate and perceived fair balance.
However, the specific risk balance varies by the "color book" (e.g., Red Book for
Employer-designed, Yellow Book for Contractor-designed), and amendments in the
Particular Conditions can significantly shift this balance.
 Administration: Administration is formal and relies on an independent third party, the
Engineer, who makes impartial determinations. The process is defined by strict notice
periods and formal procedures.
60
 FIDIC – Golden Principles
 GP1: The duties, rights, obligations, roles and responsibilities of all the Contract Participants
must be generally as implied in the General Conditions, and appropriate to the requirements of
the project
 GP2: The Particular Conditions must be drafted clearly and unambiguously.
 GP3: The Particular Conditions must not change the balance of risk/reward allocation
provided for in the GCs.
 GP4: All time periods specified in the Contract for Contract Participants to perform their
obligations must be of reasonable duration.
 GP5: Unless there is a conflict with the governing law of the Contract, all formal disputes
must be referred to a Dispute Avoidance/Adjudication Board (or a Dispute Adjudication
Board, if applicable) for a provisionally binding decision as a condition precedent to
arbitration. 61
 FIDIC – Minor Works (Green Book)
 The Agreement: This initial page serves as the formal agreement, identifying the
parties and summarizing the project.
 Contract Data: A series of project-specific information to be filled in by the parties,
including payment terms, completion time, and dispute resolution details.
 General Conditions: A set of 15 clauses that govern the contract. These are notably
shorter and less detailed than the General Conditions in other FIDIC "colour books"
but cover key areas like:

62
 FIDIC – Minor Works (Green Book)
 The Engineer's role (neutral administration is key).
 The parties' general obligations.
 Claims and payments.
 Variations and adjustments.
 Risk allocation (including clear tables for employer risks).
 Appendix (or Particular Conditions): This allows for project-specific modifications to
the General Conditions, such as the governing law and language.

63
 FIDIC – Major Works
 The Agreement: This short, formal document is signed by all parties and legally binds
all other contract documents.
 Letter of Acceptance: This is the owner's formal acceptance of the contractor's tender,
often marking the contract's formation.
 Letter of Tender: The contractor's formal offer includes the proposed price and
timeline.
 Part II - Particular Conditions: This document provides project-specific modifications
and additions to the standard General Conditions. It tailors the contract to specific site,
governing law, and commercial requirements without altering the fundamental
principles of the FIDIC form.

64
 FIDIC – Major Works
 Part I - General Conditions: The standard, unamended clauses govern the core
contractual relationship, rights, and obligations. FIDIC strongly advises against
changing these principles.
 Employer's Requirements (for Design-Build/Yellow Book) or Specification (for
Construction/Red Book): These detailed technical documents define the project's
scope, standards, and performance criteria.
 Drawings: The works are visually and graphically represented by drawings.
 Schedules: Documents include rates, quantities, and other commercial details.
 Other Documents: All other referenced documents, such as site information and
reports, are part of the contract.
65
 JCT (Joint Contracts Tribunal)
 Structure: JCT contracts are comprehensive, single-document agreements (or a suite of
documents for larger projects) with extensive procedural details built-in. They include
standard clauses but are accompanied by schedules and recitals that are completed for
each specific project. Amendments are often made via a "Schedule of Amendments".
 Legal language: The language is traditional, complex, and legalistic, reflecting the
long history of common law precedent in the UK construction industry. This can
sometimes make them difficult for non-legal professionals to fully understand without
specialized knowledge. (However, modern JCT revisions aim for clearer language)

66
 JCT (Joint Contracts Tribunal)
 Risk allocation: The risk allocation is generally conventional, with more risk placed on
the contractor. However, the specific risk profile depends on the contract type (e.g.,
Design and Build vs. Standard Building Contract).
 Administration: The process is typically prescriptive, with detailed procedural steps
for variations, payment, and managing extensions of time. It relies on a Contract
Administrator (often an architect) who issues certificates

67
 JCT – Minor Works
 Articles of Agreement: A short introductory section that identifies the parties, the
project, and the contract sum. It includes key dates like the date of possession and the
completion date.
 Contract Particulars: A data sheet containing project-specific information, such as
insurance levels, liquidated damages, and names of the parties involved.

68
 JCT – Minor Works
 Conditions: A section containing all the standard clauses. This is much shorter and
simpler than a JCT Standard Building Contract, covering topics like:
 The contractor's obligations.
 Payment and certification procedures.
 Insurance requirements.
 Possession and completion.
 Termination provisions.

69
 JCT – Minor Works
 Schedules: These are typically attached to the contract and contain the work schedules,
drawings, and specifications.
 Guidance Notes: JCT contracts often come with accompanying notes to help users
properly complete and understand the document

70
 JCT – Major Works
 Articles of Agreement: The core document signed by all parties, referencing and
incorporating all other documents.
 Contract Particulars: This document contains project-specific information and
elections that must be completed for each project.
 Conditions: The main body of the contract contains detailed standard clauses. This is a
single, comprehensive document outlining the rights and obligations of the parties.
 Employer's Requirements and Contractor's Proposals (for Design & Build contracts):
In a D&B context, these documents outline the employer's needs and the contractor's
proposed design and build solution.

71
 JCT – Major Works
 Specification: This document details the quality and standards of the materials and
workmanship.
 Drawings: Visual plans for the project.
 Schedules: Documents such as the Pricing Document, containing the Bill of Quantities
or Activity Schedule, are incorporated.
 Schedule of Amendments: Any custom changes to the standard JCT clauses are
typically documented here.

72
 NEC (New Engineering Contract)
 The NEC drafting mechanism is characterized by its modern, collaborative, and plain
language approach, intended to facilitate proactive project management.
 Structure: NEC contracts are modular and written in plain English, with a clear and
logical structure. The contract consists of Core Clauses, which are standard, and a
selection of Option Clauses and Secondary Option Clauses to tailor the contract to the
project. All project-specific information is contained in the "Contract Data".
 Legal language: NEC's use of present tense and clear, concise language is deliberate to
promote collaboration and be easily understood by all project members. It uses initial
capital letters for defined terms to aid clarity.

73
 NEC (New Engineering Contract)
 Risk allocation: NEC promotes a proactive and collaborative approach to risk
management. The "Early Warning" system requires parties to notify each other of
potential risks to collaboratively mitigate them.
 Administration: The contract is actively managed through a process driven by a
Project Manager. The process for assessing and compensating for changes is
standardized, but the focus is on a forward-looking, "no-blame" approach.

74
NEC - Engineering and Construction Short Contract (ECSC)
 Core Clauses: A set of simplified core clauses that cover the fundamentals of project
management and risk allocation. This includes provisions for:
 General obligations of both the client and the contractor.
 Starting, completion, and defects.
 Compensation events (the NEC term for a claim or variation).
 Payment.

75
NEC - Engineering and Construction Short Contract (ECSC)
 Contract Data: This is a crucial section where all project-specific information is
entered. It includes:
 Part 1: Data provided by the Client (e.g., project details, completion date,
insurance).
 Part 2: Data provided by the Contractor (e.g., tendered prices, activity schedule).
 Option Clauses: While the main NEC contracts have many options, the ECSC has a
simpler selection of options that can be chosen to tailor the contract.

76
NEC - Engineering and Construction Short Contract (ECSC)
 Pricing Schedule (or Price List): This document defines how the contractor will be
paid, based on the specific pricing option chosen.
 Scope: The Scope provides a complete description of the works, including drawings
and technical specifications. This is a vital document in the single-document contract
structure.

77
 NEC – Major Works
 The Agreement: This main document legally binds all other documents.
 Contract Data: This critical, two-part document contains all project-specific
information.
 Part One: Completed by the Client contains project details, selected options, and
key dates.
 Part Two: Completed by the Contractor with tender-specific information, such as
activity schedules or pricing.
 Core Clauses: The set of standard clauses forms the foundation of all NEC contracts,
covering general obligations, time, payment, and compensation events.

78
 NEC – Major Works
 Main Option Clauses (e.g., A-F): One of these clauses is selected to define the
project's pricing strategy (e.g., Target Cost, Lump Sum).
 Secondary Option Clauses (e.g., X1-X21): These are chosen to address specific issues,
such as inflation, performance bonds, or termination rights.
 Scope (Works Information in NEC3): This document describes the work to be
performed, including all drawings and specifications.
 Program: The accepted program for the work is a formal, contractual document
defining the project schedule and progress.
 Z-Clauses: Bespoke clauses can be added to the contract to modify the standard terms,
though NEC discourages their overuse to maintain the contract's integrity.
79
The more we learn, the less we know!

THANK YOU

Presented by:
Dr. Pradeep Reddy
Advocate & Arbitration Professional
pradeepreddyindia@[Link]
+91 7702967275
80