Commercial Contracting: CIPS Level 4 Diploma Study Notes

Commercial Contracting Study Guide.

Chapter 1: Understand the Legal Issues that Relate to the Formation of Contracts

This chapter covers:

• 1.1 Analyze the documentation that can comprise a commercial agreement for the supply of goods or services.

  • 1.1.1 Invitation to tender or request for quotation

  • 1.1.2 Specifications

  • 1.1.3 Key performance indicators (KPIs)

  • 1.1.4 Contract documentation

  • 1.1.5 Pricing and other schedules (e.g., health and safety records, supplier staff details, use of sub-contractors, non-disclosure/confidentiality agreements)

• 1.2 Analyze the legal issues that relate to the creation of commercial agreements with customers or suppliers.

  • 1.2.1 Invitation to negotiate, also known as invitation to treat in English law

  • 1.2.2 Principles relating to offer and acceptance, consideration, intention to create legal relations, and capacity to contract

  • 1.2.3 Principles relating to the battle of the forms and precedence of contract terms

  • 1.2.4 Risks presented by contracting on supplier's terms

  • 1.2.5 Risks presented by contracting oral contracts

  • 1.2.6 The Vienna Convention provisions for the International Sale of Goods and the impact on the formation of a contract

  • 1.2.7 Misrepresentations made at pre-contract award stages

• 1.3 Compare types of contractual agreements made between customers and suppliers.

  • 1.3.1 One-off purchases

  • 1.3.2 Framework arrangements and agreements

  • 1.3.3 The use of mini-competitions

  • 1.3.4 Call offs

  • 1.3.5 Services contracts

  • 1.3.6 Contracts for the hire and leasing of assets

Introduction to Contract Formation

The procurement and supply function heavily relies on the contracting process. Successful contracts demand clear definitions, key terms and conditions, and adherence to legal frameworks, while maintaining a degree of flexibility for business realities. This module is for those involved in developing and using legally binding contracts with suppliers and is also useful for contract management.

1.1 Analyze the Documentation that Can Comprise a Commercial Agreement for the Supply of Goods or Services

This section delves into the components of contract documents. These can be separate, 'linked' documents (a core document with annexes, appendices, and schedules) or a single combined document. 'The contract' refers to the entire agreement between parties, as evidenced by these documents.

Traditionally, schedules, annexes, and appendices had distinct purposes:

• Schedule: A time-oriented attachment, structured for periodic updates (e.g., annual price lists, project delivery plans, maintenance programs).

• Annex: An attachment directly relevant to the contract but not frequently updated (e.g., corporate delivery addresses, organizational policies, organigrams).

• Appendix: An attachment for reference or background, independent of the contract (e.g., historical information not directly affecting future contract performance).

Modern commercial contracts are designed to accommodate change. Therefore, mechanisms must be in place to ensure the current, up-to-date agreed version of 'the contract' is easily accessible.

1.1.1 Invitation to Tender or Request for Quotation

Difference Between Estimate, Quotation, and Tender

Legally, in contractual processes, there is no difference between a quotation and a tender. The legal basis (offer and acceptance) is covered in section 1.2.

• Estimate: Has no legal standing; it's a supplier's best guess of cost and should be avoided in commercial contracts.

• Tender/Quotation: Both are firm offers to perform something for a stated price or rates. Tenders are typically more comprehensive.

In procurement, a distinction is often artificially made:

• Quotation (Quote): Normally used when price is the only variable. The process is often simpler, possibly informal, with the buyer precisely describing needs and the supplier offering a price. Terms and conditions are (in poor practice) often unspecified, leading to the 'battle of the forms' (see section 1.2). Quotations are suitable for:

  • Low-value, low-risk purchases.

  • Fixed specification and delivery terms.

  • Pre-qualified suppliers.

  • Framework or dynamic purchasing systems where contract terms are fixed, and price is the only variable.

• Tender: Normally used when there is potentially more than one variable, though it can be used for price-only situations. The process is formal, requiring sealed bids, purchaser-dictated response formats, and specified contract terms for acceptance. Tenders are suitable for:

  • Complex projects.

  • High-value or high-risk purchases.

  • Projects requiring assessment of both quality and price.

  • Accessing unknown suppliers and pre-qualifying them (two-stage process) or assessing suitability (single-stage open tender).

Remember: An estimate is not a firm offer. Quotations and tenders are firm offers, with tenders being more detailed and including quality aspects.

Request for Quotation (RFQ)

RFQs are often misused (e.g., asking for price without adequate contract terms/specifications). However, they are valuable when properly controlled, especially under framework agreements with fixed contract terms.

Main Features of RFQs:

• Degree of Formality:

  • Advantages: Reduces administration costs for clear specifications (e.g., by make/model or product code), frees professional resources, suitable for small, known supplier pools.

  • Risks: Without strict internal rules, may devolve to simple phone calls; potential lack of audit trail; possible lack of transparency (collusion/bribery risk); limited market engagement.

  • Controls: Set maximum value limits, minimum formality (e.g., sealed quotes to central point, e-tendering), issue standard T&Cs, monitor usage, train staff on risks.

• Speed:

  • Advantages: Short turnaround if price is the only variable, quick implementation when necessary.

  • Risks: May be used inappropriately where price isn't the only variable; temptation for quick quotes instead of considered aggregated spend; nominal compliance without understanding broader procurement; no thought to contract terms or supplier vetting.

  • Controls: Use category management for aggregated spend, establish framework agreements to fix terms, permit quotes only from pre-qualified suppliers.

• Relationship to Contract Documents:

  • Risks: No cross-reference to contract on order can lead to lack of clarity; quotes often issued on supplier's terms.

  • Controls: Include terms and conditions in requests and reiterate at order placement, cross-reference request information with the order.

Invitation to Tender (ITT)

ITTs (sometimes RFTs) are more formal than RFQs, involving more thought in supplier selection and contract drafting. The tender process is well-developed, with regulated sectors (public, utilities) having legally set procedures and specific codes of practice (e.g., UK construction industry 'Practice Note'). Tender submissions are more detailed, including method statements, timescales, quality aspects, and often supplier vetting information in open tenders.

Main Features of ITTs:

• Formality:

  • Advantages: Full audit trail (especially with electronic platform), transparency reduces bribery/corruption risks, potential for wider market engagement.

  • Risks: Requires specific documentation, process-driven tenders risk lack of project-specific thought, unnecessary administrative burdens, may be regulated (risk of challenge if rules not followed).

  • Controls: Clear processes (options appraisals, reporting, accountability), compliance with legal requirements, random audit samples, staff training.

• Lack of Speed:

  • Risks: Perceived urgency can drive poor practice, lack of understanding of appropriate ITT use, poor documentation leading to prolonged clarification/poor results.

  • Controls: Robust forward planning, clear authorization for urgency (e.g., tender waiver process).

• Relationship to Contract Documents:

  • Advantages: Clear response schedules easily inserted into formal contracts if designed properly.

  • Risks: Inserting full tender response into contract can create inconsistencies (especially after clarifications).

  • Controls: Standardize documentation, train staff for efficiency, design tender/contract documents for ease/clarity.

Real-World Comparison of Quotations and Tenders

• Process Administration Costs: Sourcing (getting bids) and bidding (submitting bids) are resource-intensive. Costs should be proportionate to contract value/risk. Low-value contracts can be high-risk if failure brings business to a standstill. Upfront costs for clear, concise contracts are repaid during performance. Simplicity reduces bidding costs for suppliers.

• Audit Trails: Written or electronic records of 'what, when, by whom.' Important for:

  • Reducing bribery, corruption, collusion, extortion by increasing detection likelihood.

  • Providing evidence for unlawful activities.

  • Improving accountability and care among staff.

  • Tracing errors for personnel development and system improvement.

  • Providing evidence for disputes (specifications, offers).
    RFQs often have weaker audit trails, but e-tendering reduces this risk. Tenders are more formal and built-in auditability, further enhanced by electronic systems.

• Transparency of Process: Controlled Opening of Offers: Trust in the process is crucial for suppliers to invest time and effort. If bids are opened on receipt without safeguards, early offers could be shared, allowing later bidders to adjust prices strategically. E-tendering ensures fixed deadlines and prevent bids submission once the vault has opened.

• Urgency and Speed: Good category management and market awareness should minimize urgent situations. For unavoidable urgent needs, replacement supplier selection must remain controlled. Organizations' rules must include a tender waiver process requiring high-level authority and full business justification, along with a requirement to document lessons learned and operational improvements.

Remember: Tender processes must be transparent. Waiving normal processes requires full documentation and high-level approval.

1.1.2 Specifications

The specification is central to commercial contracts. Ambiguity, misunderstanding, stakeholder exclusion, or confusion lead to:

• Poor (over/underpriced) bids.

• Claims for time extensions or additional payments.

• Delays in approvals.

• Administration costs from contract clarifications.

• Delivery of goods/services not meeting purpose, wrong place/time/quantity.

• Delivery of substandard or legally non-compliant goods/services, risking purchasers, end-users, or the public.

The specification details requirements for procured goods, services, or works, usually included as an annex or schedule. Defining needs is difficult, with risks at both extremes:

• Excessive detail can prevent innovation.

• Products should avoid specific manufacturer/part number references.

• A 'wish list' might be unmeetable or unenforceable.

The goal is to find a middle ground.

Types of Specification

• Performance Specifications: Focus on outputs (the 'what,' not the 'how'). Sets results to be achieved, offering suppliers flexibility and shifting risk to them.

• Conformance Specifications (Prescriptive/Technical): Focus on inputs (the 'how' as well as the 'what'). Gives specific methods, processes, and materials, tying the supplier to details and retaining risk with the buyer.

• Outcome-Based Schedules: A looser, more flexible approach encouraging innovative solutions, often used in 'payment by results' (PBR) schemes (e.g., UK government public services). Note: 'output' and 'outcome' are often confused. PBR is a mechanism where payment depends on achieving commissioner-specified outcomes; providers choose interventions to secure these.

Most often, a hybrid specification is used, combining elements of both performance and conformance. It's possible for a hybrid to appear conformance-based but fail to deliver the intended outcome (e.g., w/cm ratios in concrete not ensuring durability despite compliance). Procurement professionals must engage technical stakeholders but also challenge 'what we know' or 'how we've always done it,' returning to first principles.

Remember: Procurement professionals must challenge specifications. Naive questions can expose technical errors.

Designing a Specification

1. Purpose: What are you trying to achieve (current/future needs, make/buy)?

2. Perspective: What do different stakeholders need (buyers, suppliers), and what's their influence?

3. Type: Conformance or performance (considering technical interfaces, compatibility, interoperability, lock-in risks)?

4. Relevance: Include only what's needed (minimum/maximum standards, cost-benefit of higher investment)?

5. Scope: What's included/excluded (geographical, business unit, value limits; contract changes; test/implementation/training needs; internal input)?

6. Performance: Define quality standards (KPIs, targets, complaint/remedy processes, warranty periods)?

7. Improvement and Innovation: Never reuse old specifications. What's changed, and what might change during the contract?

8. Clarity: Clear, unambiguous language (plain/technical where appropriate)? Easy to assess costs/prices? Contract manager can check delivery?

9. Regulatory Compliance and Quality: What standards must be met (laws, CoPs, ISO, H&S, environment, equality, data protection)?

10. Service Conditions: Impact of delivery point (operating/storage conditions, resource availability, safety, cultural issues)?

11. Budget: Impact on quality, design, and performance?

12. Waste and Emissions: Management of waste, environmental impact, applicable legislation?

The Specification as a Contract Document

The specification is only a contract document if explicitly stated. Changes during tender or negotiation, or supplier qualifications, can lead to disputes about the contractual version. Effective configuration control is vital. The simplest method is to reproduce and append the final, agreed specification as a schedule, clearly referenced in the contract terms. Throughout delivery, clear, unambiguous contractual measures must identify compliance and performance.

Potential Problems if Not Incorporated:

• Total agreement clauses invalidate anything not in contract documents, including tender information.

• Clarifications/amendments during tender may be omitted, undermining the contract and creating scope for dispute.

• Failure to use the most up-to-date specification.

Remember: Construct contract documents as a single package with working cross-references and referenced schedules.

1.1.3 Key Performance Indicators (KPIs)

A specification defines what is to be delivered; a mechanism is needed to compare actual delivery against it. Commercial life is complicated, and unforeseen issues can arise. A performance management framework sets standards, targets, measurement methods, and actions based on results, aiming to control controllable aspects and optimize outcomes.

Key Components of a Performance Management Framework:

• Key Performance Indicators (KPIs): What is being measured.

• Targets: The performance level to be achieved.

• Consequences: What happens if measures are not achieved or are exceeded.

(KPI design is detailed in section 2.2; here, the focus is on documentation status.)

Are KPIs Necessary?

Surprisingly, contracts without KPIs are common. While good suppliers and relationships might seem sufficient, investing in KPIs is worthwhile for:

• Ensuring minimum standards are consistently met, requiring measurement.

• Not relying on luck.

• Using commonly recognized and defined measures (ee.g., meters, seconds, liters) and avoiding contentious or uncertain ones (e.g., ton/tonne, gallon (European vs. American), furlong).

• Protecting against changes in supplier's operating environment, significance of purchaser's business, or personnel changes that erode relationships.

• Monitoring performance (stable, improving, deteriorating) to provoke appropriate responses:

  • Stable: Analyze for missed improvement opportunities.

  • Improving: Understand successes for transferability.

  • Deteriorating: Analyze root causes, take action, and learn for future contracts.

Do KPIs Need to Be Contractual?

Managing KPIs outside the contract is poor practice, as it negates leverage. KPIs should be intrinsic to the specification. Without contractual integration and consequences, even measurement may be difficult to enforce, as data often comes from the reluctant supplier. Non-contractual KPIs make it hard to enforce measurement and often lead to reluctant engagement from suppliers due to the associated costs.

Targets

A KPI is merely an indicator (e.g., customer satisfaction at $85\%$). A target (the 'pass mark') is needed for context. If $85\%$ is low against a sector average of $90\%$+, it's a concern; if average is $80\%$+, it's less so. KPIs must be linked to targets within the contract. Both indicators and targets should be developed in contract design:

• Negotiated Contracts: Can be revisited during negotiation.

• Tendered Contracts: Must be part of the original tender invitation.

KPI targets affect potential suppliers':

• Ability to perform (e.g., resource next-day delivery).

• Interest in the contract (cost-effectiveness, profitability).

• Willingness to bid.

• Price for performance.

• Performance expectations for future negotiations.

Consequences

The contract must define consequences for meeting or missing KPI targets. Without direct consequences, incentives/disincentives might be embedded (e.g., transparency enabling lessons learned). An enlightened supplier uses KPI info for internal improvement, but contractual remedies (penalties for failing, bonuses for exceeding) ensure purchaser's problems are immediately addressed. Without explicit clauses, the purchaser has no grounds for redress unless failure constitutes a fundamental breach (e.g., non-compliance with specification, fitness for purpose).

Remember: KPIs and the performance management framework are only contract documents if explicitly stated. Appending them as a referenced schedule to the core contract is the simplest method.

1.1.4 Contract Documentation

This section examines specific aspects of contract documents, building on specifications and KPIs. Essential supplier tender submission aspects for product/service delivery must be included:

• Purchase price factors: agreed price, inflation rates.

• Time scales: production, delivery, completion.

• Logistical aspects: location, delivery method, packaging, transfer of ownership.

• KPI aspects: delivery performance (on-time, in-full), quality performance (defects), response times.

• Specification factors: material requirements (grade of metal), standards (ISO $9001$, ISO $14001$).

These are documented via contractual terms or schedules.

Contractual Terms

These terms, also called 'terms and conditions,' form the main body (core contract) of the contract document. Often, they are the smallest part of the contract and require schedules and supporting documents for full understanding. Key terms are detailed in section 3.2. Here, the focus is on their nature and purpose and how they are established.

Formal Contracts

A formal contract is any agreement evidenced in writing and intended to be legally binding. Conditions for a formal contract:

• Terms are detailed.

• Parties agree to terms and desire enforceability.

• Terms are written, and the document is signed (or signed and sealed).

These are conditions for formality, not legal binding (see section 1.2 for legal binding conditions). A contract can exist without being written. 'Contract' may also be called an agreement, commission, letter of appointment, or service level agreement (SLA – context matters).

Remember: The contract is the total agreement, possibly labeled differently (e.g., 'agreement,' 'commission,' 'appointment') and comprising multiple documents.

The Use of Templates or Standard Terms

Few contracts are written 'from scratch.' Most commercial contracts use industry standard forms or templates developed by the organization, legal advisors, or other bodies (CIPS, government). Advantages of templates:

• Key risk areas are covered.

• Standard clauses prompt relevance checks.

• Legal meaning of terms is considered, reducing misinterpretation.

• Standard schedule lists prompt inclusion.

• Often cheaper to produce.

• Drives consistency.

Disadvantages of templates:

• Risk of using inappropriate templates (e.g., goods form for services).

• Complacency (only checking known amendment clauses, ignoring specific procurement needs).

• Failure to cross-check references, creating nonsensical requirements.

• Outdated legislation/standard references.

• Schedules appended without firm reference, causing improper incorporation.

• Definitions in schedules differing from standard contract, creating ambiguity.

Bespoke contract forms advantages:

• Focuses on precise procurement needs.

• Avoids standard form risks.

Bespoke contract forms disadvantages:

• Language may be inconsistent with legal interpretation.

• Potential to omit non-obvious risk areas.

• Identifying risk/remedy without considering wider consequences (e.g., termination).

The Importance of Selecting the Correct Template

While templates offer advantages, using the wrong one is a risk. Commercial organizations have limits to contract standardization. Building, works, consultancy, catering, and software contracts have very different considerations. If organizations use a bank of standard forms, a decision tree or flow-chart may be needed to guide personnel. Simplifying lists might lead suppliers to reject overly generic forms.

Key Sections of the Contractual Terms Document

Many contracts follow an established format:

1. The ARTICLES: Basic agreement summary. States Party A (purchaser) contracts with Party B (supplier) for goods/services, with Party A paying. Identifies legal names/registration, and defines short terms for each party (e.g., 'the Purchaser'). Clarifies purpose and parties, simplifies drafting.

2. The RECITALS: Provides context (e.g., purchaser wants X, supplier agrees to provide it). Often starts with 'whereas.' If inaccurate, can undermine the entire contract.

3. CONTRACT PARTICULARS: (Some forms, especially industry standards). Sets specific parameters (e.g., completion date, insurance requirements). Mechanism for filling in common variables, referring back to detailed terms. May include critical success factors (CSF), warranties, and innominate terms.

   • Conditions: Critical elements, breach allows termination.

   • Warranties: Lesser terms, breach results in damages, not termination.

   • Innominate terms: Can be conditions or warranties depending on dispute resolution judgments.

4. The full TERMS AND CONDITIONS: The detail. Covers ifs, buts, maybes. Normally standard wording with DEFINITIONS AND INTERPRETATION clauses. Cross-refers to contract particulars and schedules.

5. The SCHEDULES: Project-specific detail (e.g., KPIs by purchaser, pricing by supplier).

How Contract Terms Are Established

The process for formal contracts:

1. Commercial team (procurement, stakeholders, legal) designs contract and CSFs.

2. Draft contract discussed with potential suppliers during pre-market engagement, refined.

3. Draft contract issued with RFQ, ITT, or negotiation invitation.

4. Quotes/tenders received (subject to clarifications) or terms amended during negotiation.

5. Offer accepted (including agreed terms).

6. Formal contract documents produced and signed (or signed and sealed).

Good practice is for the purchaser to lead in establishing terms, with T&Cs part of the RFQ/ITT, requiring bidder acceptance. Enforceability depends on:

• Procurement team professionalism.

• Process robustness.

• Purchaser's buying power in target market.

• Market competitiveness.

• Sourcing process.

Considerations:

• Market leverage: Lower leverage means easier supplier negotiation (tender or post-signing), creating opportunities/threats.

• Regulated procurement: Changes to terms after advertising are difficult but not impossible if all potential suppliers are informed and deadlines extended.

Procurement personnel must fully understand contract forms and term purposes (protect supplier, protect purchaser, balance protection). Any clause change shifts this balance. Understanding this shift and its practical impact is part of a procurement professional's role.

Remember: Contracts protect both parties, reflecting relative bargaining positions and influence.

Informal Contracts

Legal rules determine contract existence without formal documents. If a quote is requested, provided, and an order issued, intention to create a legal relationship exists. The difficulty is establishing terms. Disputes may refer to previous agreements or normal sector expectations, if no counter-evidence. This is unsatisfactory, exposing both parties to unconsidered risks which can outweigh the cost of a simple formal contract.

1.1.5 Pricing and Other Schedules

Examples of schedules include pricing, health and safety records, supplier staff details, use of subcontractors, and non-disclosure/confidentiality agreements. A schedule is an attachment to the body of the contract form, simplifying incorporation of project-specific information without amending core clauses, allowing standardization of terms.

Benefits of this approach:

• Drafting is simpler, quicker, cost-effective.

• Consistency across similar internal contracts.

• Contract managers become familiar, easily finding info.

• Procurement documents designed for direct supplier offer incorporation, reducing misinterpretation.

Pricing Schedules

Contracts not involving a single fixed-fee payment will have a pricing schedule, detailing how price is calculated for each invoice. Complexity varies with contract nature. Pricing schedules and arrangements are detailed in section 3.3.

Other Schedules

There's no limit to schedule numbers. Template forms often include a standard list, acting as a reminder during drafting. Not all are applicable.

Remember: A schedule has no force unless referenced within the terms and conditions. Schedules explain, amplify, or limit areas covered by T&Cs.

Most Common Types of Schedules:

• Specification: Most important. Exactly what is to be delivered (conformance/technical or performance). Must be clear, unambiguous. Enables supplier costing, purchaser checklist. Ensures compatibility/interface.

• Preliminaries (or contractual/operational matters): (Often construction industry 'prelims'). Explains contract context. Overarching for other schedules. Often in tender documents, for single pricing schedule line covering overheads/risks.

• Performance Management Framework: Full framework (KPIs, targets, assessment, incentives/disincentives, bonuses/penalties). Unless linked to contract clauses enabling consequences, of little positive purpose. For term contracts, should include mechanism for adjusting targets/indicators.

• Delegated Authority and Contractual Management: Factors for amendment, signatories, vested power, management of performance.

• Site lists, maps and plans: Factual lists/maps for delivery clarity. Critical for precise delivery (e.g., GIS mapping). Relevant for facilities management or partial building jurisdiction.

• Health and Safety: May include pre-construction info (e.g., UK CDM regulations) or risk assessment for known hazards (asbestos, chemicals, noise). Live documents requiring updates.

• Method Statements: Describes how results are achieved. Important for performance specifications. Can be separate or in specification. Contract must clarify if statement is 'approved' or 'accepted'; approval shifts some liability to purchaser.

• Sub-contractors/Supply Chain: Can list subcontractors/approved manufacturers, or set process for agreeing/approving supply chain. Used to leverage buying power, control ethical issues (materials, labor rights), or manage reputation. Requires sanctions/remedies if minimums unmet; supplier development may be better.

• Alliancing Agreements: Contractual mechanism for requiring subcontractors/co-contractors to work with main contractor/purchaser on joint supply chains. More common in framework agreements. Useful if combined buying power is greater. Risks undermining existing arrangements. Only for very high-value contracts.

• Core List or Exclusions List: For schedules of rates/catalogue prices (e.g., percentage discount). Specifies which items it applies to (core list/items) versus which it does not (non-core/excluded items). Pricing schedule should cross-refer or combine, and indicate pricing for non-core items.

• Supplier's Staff: For service dependent on individual skills, may require key personnel whose sustained participation is material to contract (termination if not present or replaced with proportional skill/experience). For work with children/vulnerable adults or defense/security, specific staff-vetting processes and clearance evidence needed.

• Codes of Conduct: If not in preliminaries, sets behavior norms for supplier staff on client premises (respect, cultural sensitivity). Should be a contract schedule for enforceability.

• Data Management: May need NDA requirements (IP, commercial confidentiality), cyber-security standards, rules for personal data processing (e.g., GDPR), IPR terms, data disposal post-termination.

Contract Variations

Contracts are not fixed; they must allow for change due to unforeseen circumstances (regulations), foreseeable needs (price adjustments), or requests benefiting both parties. If a contract lacks a change mechanism, it risks stagnation, ineffective delivery, or early termination.

The change process should be in the contract, including:

• Who can request/authorize/accept a change.

• Mechanism for price adjustments (referencing existing framework).

• Implications if variation order rejected.

• Details of variance management and configuration control.

• Responsibilities for notification to affected parties.

Ideally, a variation order format (see Figure 1.3) should be a schedule or appendix. It must include price impact, timescales, and reference clauses/schedules being changed. Copies should be with original contract documents. Variation orders don't need signing/sealing; authority is delegated. Changes may need to be reflected in contract registers.

Remember: Contracts can be amended. Those lasting more than a very short period should include a variation mechanism, outlining authorization and limits.

1.2 Analyze the Legal Issues that Relate to the Creation of Commercial Agreements with Customers or Suppliers

This section covers contract law, primarily from the UK legal system, but principles are generally accepted. Many cases are old; relevant law evolves through trials or statutory changes. Civil law countries (e.g., Austria, Poland) rely on statutes. Mixed systems exist (e.g., South Africa). French law conflicts with EU directives require careful attention.

The Basic Rules of Contract Formation

Six conditions for a contract to come into being:

• Offer

• Acceptance

• Consideration

• Intention to create legal relations (or intention to be legally bound)

• Capacity to contract

• Be legally binding

1.2.1 Invitation to Negotiate, Also Known as Invitation to Treat in English Law

Procurement professionals must distinguish between an offer and an invitation to negotiate (ITN) or invitation to treat. No offer means no acceptance, thus no contract. Buyers sending RFQs or ITTs are making ITNs, not offers to purchase; they are requests for supplier bids. Similarly, a seller's ITN/invitation to treat showcases a product/service, inviting buyer offers or negotiations. The buyer's response is the offer.

Common examples of ITNs/Invitations to Treat:

• Advertisement of goods/services: Owner reserves right to choose buyer, multiple interested parties can offer. Carlill v. Carbolic Smoke Ball Company (1892): A £100 reward advertisement for flu prevention after using smoke balls was held to be an offer because a reasonable person would take the promise seriously due to £1000 deposit.

• Displaying goods for sale: Customer makes the offer at point of sale. Fisher v. Bell (1961): Flick-knife display was an invitation to treat, not an offer for sale. Pharmaceutical Society of Great Britain v. Boots Cash Chemists (1953): Product display was invitation to treat, offer made at cash desk where pharmacist was present.

• Auctions/e-auctions: Advertisement is ITN; bids are offers. Winning bid's announcement is acceptance, creating contract. Harris v. Nickerson (1872): Auction advertisement was not an offer, so cancelled auction did not entitle plaintiff to expenses.

• Online catalogues/websites: Invitation to treat for purchasers. Order placement is an offer, requiring supplier acceptance (exception: specific negotiated contracts).

1.2.2 Principles Relating to Offer and Acceptance, Consideration, Intention to Create Legal Relations, and Capacity to Contract

Offer

An offer is a full statement of what the offeror is willing to provide and its terms. If something isn't an offer, it can't be accepted, so no contract is created. Definitions of non-offers evolved through case law, primarily English, but similar principles apply elsewhere. Buyers should check applicable jurisdiction.

Actions that are NOT Offers:

• Invitation to negotiate/treat: Person willing to discuss a deal, but not bound by mentioned terms. Catalogues, displayed goods, and ITTs are examples. Harvey v. Facey (1893): Lowest price quote was information, not an offer to sell.

• Declaration of intention: An aim or plan, not definite.

• A 'mere puff' (boast): Not meant to be taken literally, unless a reasonable person would take it seriously (e.g., Carlill v. Carbolic Smoke Ball Company).

• Provision of information: Simply answering a request for information.

Remember: ITN/treat, declaration of intention, 'mere puff,' and information provision are not offers.

Communication of an Offer

An offer only exists if communicated to the other party, allowing them to accept or decline. Taylor v. Laird (1856): Sea captain's offer to assist on return voyage was not communicated to employers, so they weren't obliged to pay.

Duration of an Offer

Six ways an offer ends (ceases to be capable of acceptance):

1. Withdrawal (revocation): Offeror can withdraw at any time before acceptance, even if promised to keep open, unless compensated for keeping it open (e.g., an option). Withdrawal must be communicated, but not necessarily directly (e.g., selling to someone else, communicated by reliable source: Routledge v. Grant (1828), Dickinson v. Dodds (1876)).

2. Lapse: If a time limit for acceptance is set and not met. If no express limit, lapses after a 'reasonable time' (circumstance-dependent: Ramsgate Victoria Hotel v. Montefiore (1866)). In practice, purchaser may seek extension or accept anyway (switching offer direction).

3. Death: Death of either party before acceptance terminates the offer (likely applies to company winding-up).

4. Rejection: Once rejected, cannot be accepted later. A counter offer is a rejection (Hyde v. Wrench (1840)). Acceptance subject to conditions other than original is also a rejection/disguised counter offer (Neale v. Merrett (1930)). Rejection must be communicated. Without prejudice phrase can protect an offer during negotiation.

5. Failure of conditionality: If an offer is subject to conditions (express or implied) that are not fulfilled (Financings Ltd v. Stimson (1962)).

6. Acceptance: Once accepted, the offer ends. If offer is for a single item to a group, one acceptance makes it unavailable to others.

Remember: Withdrawal, lapse, death, rejection (including counter offer), failure of conditions, and acceptance are the six ways an offer ceases to exist.

Acceptance

Acceptance is subject to:

• Offer still being open.

• Being absolute and unconditional.

• Being intentional.

• Not being made by someone with diminished capacity.

This raises questions about subject to contract headings (e.g., letters of intent), which typically indicate no contract yet. Acceptance creates the contract, so place of acceptance can determine jurisdiction (less clear with electronic contracts; contract terms should explicitly state legal/judicial system). Acceptance can be implied by actions (acceptance by performance), but silence on unwanted deliveries does not imply acceptance (Felthouse v. Bindley (1862)).

Remember: An offer can only be accepted if still open. Acceptance must be unconditional.

Exceptions to Acceptance Rules Regarding Communication

Two exceptions override the need for acceptance communication:

• Offeror dispenses with formal acceptance: Common in call-off contracts where seller fulfills order as acceptance (similar to acceptance by performance).

• Mailbox rule: Letter accepting an offer, once properly posted, is effective from posting date, even if never arrives. Applies only to acceptance, not offers or withdrawals. Requires both parties to anticipate postal acceptance and evidence of posting. Byrne & Co v. Leon Van Tien Hoven & Co (1880): Acceptance valid when sent, before withdrawal received. This rule doesn't apply to near-instantaneous communication (telephone, telex: Entores v. Miles Far East Corporation (1955)). Email status under mailbox rule is debated, with Neocleous v. Rees (2019) recognizing electronic signatures. However, instant communication reduces the practical impact of cross-postings, and contracts now routinely specify jurisdiction.

Mailbox Rule in Civil Law Jurisdictions

Civil law countries generally don't apply the mailbox rule; acceptance is effective when communicated. Some (Germany, Netherlands) soften this if lack of communication is not the fault of the offeror.

The Vienna Convention on the Mailbox Rule

The United Nations Convention on Contracts for the International Sale of Goods (CISG) generally excludes the postal rule for contract conclusion, but retains that an offer cannot be withdrawn after acceptance is sent.

Ability to Agree Rules Between the Parties

Parties can explicitly define acceptance communication protocols (e.g., email copy of signed letter effective on receipt, deemed received within one hour unless non-delivery message, hard copy confirmation).

Remember: Offer/acceptance rules are complex and jurisdiction-dependent. Be explicit about jurisdiction and tender receipt/acceptance terms.

Consideration

In legal terms, contracts are bargains; consideration is 'one thing given in exchange for another.' In commercial contracts, usually financial payment, but payment in kind (barter) can also be consideration. Consideration must have value but doesn't need to be adequate. No consideration means no contract.

Definitions of non-consideration evolved through case law:

• Past consideration: Something already done or given cannot be consideration (Eastwood v. Kenyon (1840), Roscorla v. Thomas (1842)).

• Implied consideration: If a promise to pay is made after goods/services, but an implied promise of payment was present from the outset, it may be valid consideration (Stewart v. Casey (1892)).

• Promise to perform an existing obligation: If the obligation is legal, it must be performed regardless, so it's not consideration (D&C Builders v. Rees (1966)).

• Promise to perform over and above an existing obligation: This IS consideration (Glasbrook Bros v. Glamorgan County Council (1925)).

• Promise given to a third party: Not normally consideration, due to privity of contract (contract is private arrangement between parties; non-parties generally cannot sue: Tweddle v. Atkinson (1861)).

Adequacy and Sufficiency of Consideration

• Sufficient consideration: Capable of monetary value, not past, not existing obligation (unless over and above), from one contract party to another, more than vague promise. Does not need to be 'adequate'.

• Adequate consideration: Relates to fairness/reasonableness of payment. Law generally doesn't intervene if power balance is reasonable. Governments may intervene in consumer contracts (e.g., price caps).

Remember: Consideration must be direct, present/future, new obligation, from one party to another, specific, and have value. It doesn't need to be 'good value.'

Rights of Third Parties

Concern about beneficiaries' inability to enforce contracts has led to legislation like the UK Contract (Rights of Third Parties) Act 1999, allowing third parties to enforce if the contract explicitly grants this right or intends to confer a benefit. Similar legislation exists in New Zealand. Other countries haven't followed, and many UK contracts explicitly state no third-party rights. Donoghue v. Stevenson (1932) established negligence as a basis for claim by an injured party not subject to a contract.

A collateral warranty is a subcontractor's agreement to guarantee obligations to a third party. It's legally binding only if executed as a deed.

Where Consideration is Not Required

The exception is when a promise is made by deed. Traditionally, a deed needed to be sealed; now, it generally requires explicit declaration as a deed, and signing by parties and witnesses. Commercial organizations with company seals must attach them. Collateral warranties are often deeds because they lack consideration. Deeds carry $12$ years' liability, compared to $6$ years for most contracts.

Remember: Consideration is not required when a promise is made by 'deed'; a document is a 'deed' if it explicitly says so.

Intention to Create Legal Relations

Contracts require mutually agreed intention to be enforceable (legally binding and legally enforceable). Commercial arrangements are generally presumed enforceable. Domestic agreements are generally not (Balfour v. Balfour (1919) where husband's allowance promise wasn't a contract). However, some agreements between non-family members can be contracts (Simpkins v. Pays (1955) where shared winnings from a competition were enforceable).

In commercial settings, intention to be bound is assumed unless there's strong evidence against it (Rose and Frank v. JR Crompton and Bros Ltd (1925) where explicit wording 'not a formal or legal agreement' prevented enforcement; Appleson v. H Littlewood Ltd (1939) where 'binding in honour only' precluded legal obligation).

Capacity to Contract

Capacity to contract (legal capacity/competency) means no legal reason prevents entry into a contract. Those typically lacking capacity:

• Infants/minors (under age of maturity, varies by legal system/context, e.g., age of $13$ for social media, $16$ for marriage, $17$ for vehicle responsibility, $18$ for alcohol/tattoos in English/Welsh law).

• People with mental health issues.

• People under the influence of alcohol or drugs.

Contracts with individuals lacking capacity are not legally binding on them (rules protect them), but may be binding on the other party. Exceptions exist for essentials (housing, food) if the person understood the contract. These rules apply to natural persons, not companies or public authorities, which are deemed to have capacity.

Ultra Vires

Public sector bodies face ultra vires rules (beyond powers), limiting their legal ability to contract for certain things. Acts of parliament define their duties/obligations. Contracts beyond these limits are unenforceable against the organization (Credit Suisse v. Allerdale Borough Council (1997) where council's guarantee of a loan for a swimming pool company was unlawful). This rule has been largely eradicated in the UK to avoid unfairness to the other party.

Remember: Lack of capacity to contract applies to individuals. Ultra vires applies to companies/public bodies acting beyond legal limits.

1.2.3 Principles Relating to the Battle of the Forms and Precedence of Contract Terms

The Battle of the Forms

A counter offer rejects the original offer (covered in duration of offer). Companies often unknowingly engage in battle of the forms when using standard terms (e.g., on RFQs, quotes, order forms, delivery notes, invoices). Purchaser's and supplier's terms differ, each trying to override the other. Each issue of terms is a counter offer. The battle is won by the person who 'fires the last shot' (Butler Machine Tool Co Ltd v. Ex-Cell-O Corporation (1979)).

Remember: In the battle of the forms, the most recently issued T&Cs typically take precedence.

Precedence of Contract Terms

Commercial agreements are complex, with numerous documents/sections drafted by different specialists, potentially leading to inconsistencies. The law generally holds that anything explicit in a contract overrides anything implicit or previously agreed, unless an implied term is statutory or legally regulated.

• Matters not reflected in the contract: Most contracts have a full agreement clause stating that prior discussions are ignored. Courts uphold this unless the written contract is unclear, then pre-contract context may be used to establish intent.

• Standard forms and attached schedules: If direct amendment overrides standard format, courts first check for actual inconsistency. If an interpretation makes all clauses valid, that will be assumed. If not, specific clauses override general ones.

• Hierarchy of clauses or order of precedence clauses: Many contracts explicitly state which terms take precedence (e.g., contract clauses over drawings/schedules). Courts generally try to reconcile all clauses before using these (e.g., RWE Npower Renewables Ltd v. J N Bentley Ltd (2014)), only using them for blatant discrepancies (CLP Holding v. Singh and Kaur (2014)).

Remember: Specific contract terms generally override standard terms. Express terms override implied terms (unless statutory). Fairness of upholding written contract is considered. Courts review all documents to determine intent, but precise express terms are hard to override.

1.2.4 Risks Presented by Contracting on Supplier's Terms

A fairly drafted contract protects both parties. Equal bargaining power leads to equal protection. Stronger parties dictate terms. Accepting supplier's terms means accepting a contract drafted entirely in their favor, potentially leading to:

• No warranty of quality or fitness for purpose.

• Specification reflecting supplier's desires, not purchaser's needs.

• All transit damage risks with purchaser.

• Payment terms causing cash flow issues for purchaser.

• Exclusion of liability (to extent permitted by law) for damage/injury caused by goods/services.

• Lack of protection against time/budget overruns.

• Inability to change specification without disproportionate extra costs.

• Lack of protection for purchaser's intellectual property.

• Inability to control shared data, risking legal penalties (especially under GDPR).

1.2.5 Risks Presented by Contracting Oral Contracts

Oral contracts are enforceable, but proving terms is difficult without written records. Transactions (e.g., phone calls outlining needs, asking for price, placing order) are often short and limited. Purchaser and supplier may believe they contract on their own terms regarding warranty, specification, timescales, cost, liabilities. This often leads to formal documentation creeping in (confirmation order, delivery note), initiating a battle of the forms. Procurement professionals should avoid oral contracts.

1.2.6 The Vienna Convention Provisions for the International Sale of Goods and the Impact on the Formation of a Contract

The Vienna Convention on Contracts for the International Sale of Goods (CISG) is a voluntary treaty under UNCITRAL, aiming to harmonize international transaction rules. Contracting States (currently 164 WTO members) are countries that have signed it. Some countries (North Korea, Monaco) have not. Applies only in specific situations:

• Goods only (not services or works), including goods manufactured to buyer specifications.

• Private commercial (B2B) transactions (not public sector or consumer sales).

• Parties have places of business in different Contracting States.

States can exclude parts of it for specific goods or territories (e.g., China excludes Hong Kong). Parties can exclude/alter provisions case-by-case. A contract clause stating the contract is subject to the legal systems and courts of a particular country overrides CISG rules. If only one (or neither) business is in a Contracting State, CISG applies only if local rules permit choice of legal system AND contract explicitly states CISG application. CISG interpretation evolves through case law (UNCITRAL reports on ~$4500$ cases).

Remember: CISG applies to B2B goods contracts between different Contracting States, unless excluded by states or superseded by explicit contract terms.

What Type of Goods Fall Under CISG Rules?

CISG generally does NOT apply to:

• Distribution agreements (about organization/transport, not ownership transfer).

• Goods bartered for other goods/services (payment not money).

• Framework agreements (not actual contracts).

• Franchise agreements.

• Sale of ships or aircraft.

• Sale of electricity (gas position unfinalized).

• Anything sold at auction (traditional, not clear for reverse e-aulections).

• Software position is less clear; some courts say only standard, others say bespoke. All other types of goods are covered.

Impact on the Formation of a Contract

CISG covers contract formation: offer, acceptance, consideration.

• Offer: Must be addressed to person, definitively describe goods/quantity/price, and indicate intention to be bound. Revocable if withdrawal received before acceptance sent.

• Acceptance: Must be explicit (silence not acceptance). Any changes to terms are a counter-offer/rejection.

CISG does NOT cover validity or enforceability of contracts (or parts), so national laws determine:

• Capacity, illegality, mistake, duress, fraud.

• Damages, penalty clauses, assignments, settlements, retentions, deposits.

• Liability for death or personal injury caused by goods.

This means contracts still need to specify which country's laws apply to non-CISG matters, wording carefully to avoid accidental exclusion of CISG rules. There's a general requirement to act in good faith, which is a reason for the UK's (now former EU member) reluctance to sign. CISG doesn't require contracts or amendments to be in writing; procurement professionals should explicitly exclude this and mandate written variations.

Remember: CISG does not require contracts or amendments to be in writing. It's wise to state all variations must be in writing as an exclusion to CISG rules.

Rules Relating to the Sale of Goods

• Seller's duty: Deliver goods, provide related documents, transfer ownership.

• Goods quality/quantity/specification: Must conform to contract, be suitably packaged, fit for purpose, free of third-party claims (e.g., IPR infringement).

• Buyer's duty: Take reasonable steps to take delivery, examine promptly, advise non-conformity within reasonable time, make payment.

• Risk transfer: CISG has provisions, but Incoterms® are generally preferred.

• Remedies for breach: Damages, specific performance, price adjustment, depending on facts/breach nature. Liability avoided if failure due to unforeseen/unpreventable circumstances (equivalent to force majeure).

• Refunds: If seller refunds, must include interest from original payment date (interest rate source unclear).

• Returns: If buyer returns goods, must pay for value/benefit gained while in possession (calculation unclear).

• Caveat emptor (buyer beware) applies.

1.2.7 Misrepresentations Made at Pre-Contract Award Stages

Misrepresentation is a false statement of fact made by one party before or at contract entry, which induced the other party to contract.

Necessary Conditions for Misrepresentation:

• Statement must be made: Can be explicit or implied by conduct. Silence is usually not misrepresentation, unless:

  • Contracts of utmost good faith (e.g., insurance).

  • Silence deliberately creates a misleading impression (Nottingham Patent Brick & Tile Co v. Butler (1886)) where solicitor failed to reveal restrictive covenants.

  • If a true statement becomes false due to changed circumstances, there's a duty to update (With v. O'Flanagan (1936)) where a medical practice's earnings declined before sale.

• Statement must relate to fact: Not a statement of law or an honestly held opinion. Stating a false intention is misrepresentation (Edgington v. Fitzmaurice (1885)) when funds were raised for business improvement but intended for debt repayment.

• Statement must be false: Untrue, became untrue, or misleading in context.

• Statement must be made by the contracting party: Or their agent. Doesn't need to be direct.

• Statement must induce the contract: Must directly influence willingness to contract. Cannot be made after contract entry. Innocent party cannot avoid if they knew about the falsehood, didn't know about the statement, or didn't rely on it (carried out own investigations). Misrepresentation doesn't have to be the only inducement.

Types of Misrepresentation

• Fraudulent misrepresentation: Statement made knowing it's false, or recklessly without verifying truthfulness.

• Negligent misrepresentation: Person making statement has a duty of care and fails to take reasonable care of accuracy (applies to experts). UK Misrepresentation Act 1967 places burden of proof on defendant to show non-negligence.

• Innocent misrepresentation: Misleading statement is genuinely and reasonably believed to be true.

Remedies for Misrepresentation

• Rescission of contract (placing parties in pre-contractual position).

• Damages.

For fraudulent/negligent misrepresentation, courts may award both. For innocent, only one. Rescission is not always possible if:

• Innocent party affirmed the contract.

• Claim not brought within reasonable time.

• Restitution impossible (goods consumed/deteriorated).

• Intervention of innocent third-party rights (goods sold on).

In these cases, damages may still be awarded.

1.3 Compare Types of Contractual Agreements Made Between Customers and Suppliers

This section compares contract types by their structure, not the procurement procedures leading to them. Most can be reached by negotiation or competitive tender.

1.3.1 One-Off Purchases

One-off purchase contracts are for a single purchase, not necessarily a single item. Can be for goods (a computer, a fleet of vehicles), services (a training course, a land valuation), or works (a single building, a housing estate). More complicated items are less likely to use one-off contracts.

Simple One-Off Purchases

May lack a formal contract (e.g., marketing team ordering leaflets by phone). Goods delivered, invoice paid. This approach carries problems (see sections 1.1, 1.2). A formal purchasing system with standard T&Cs helps, but battle of the forms risk remains.

Complex One-Off Purchases

Distinct from spot-purchases. Commissioning major projects (housing estate, aircraft carrier) can be one-off, even if strategy/funds allow for more efficient, multi-year procurement (e.g., framework agreements). Political and financial realities often prioritize immediate capital investment over procurement efficiency. Public/utility regulations may apply. Sourcing is competitive (formal tenders, parallel negotiation). Contracts are carefully considered, with detailed specifications and well-documented change procedures due to project complexity.

Remember: A one-off contract can be simple or complex, tendered or not.

Reasons for Using One-Off Purchase Contracts

• Simple items/services: Low-value, urgent need, lack of planning. Immediate use, or to exploit special offers (bankruptcy sales). Often untendered, spot-purchase approach.

• Complex purchases: Lack of developed strategy for spend area, inability to predict future funding (often linked). Public sector faces political/international impacts, private sector internal budget competition.

Nature of the Contract

Complexity reflects purchase complexity. Simple, low-value purchases may only need standard T&Cs. Complex one-off contracts still need to cover:

• Warranties and guarantees (if long lifespan, business-critical).

• Insurance requirements (professional indemnity, public/products liability, employer's liability, specific risks).

• Licensing and updates for software (amendments, drivers, versions, operating guidelines).

• Specification requirements (quality, timing, delivery).

• Minimum quality standards for business operations (e.g., hygiene for catering).

• Built-in change process for any but the simplest goods/services (works contracts always have variations).

• Minimal/no scope extension, limited duration extension for time overruns (subject to damages/penalties or overhead costs).

• Data security protocols for shared personal data.

Remember: One-off contract complexity must reflect product/service/works complexity.

Benefits of One-Off Contracts

• For Purchaser: Speedy delivery (simple, low-value from known suppliers), capitalize on falling market prices/special offers, focused terms for single deliverable (complex projects) simplifying contract to specific risks.

• For Supplier: No competition (spot-purchase), allowing own pricing; significant total spend from regular one-off contracts.

Risks of One-Off Contracts

Benefits for one party are risks for the other. Additional risks:

• For Purchaser: No market investigation/competition means no value-for-money demonstration (sourcing process issue, not contract nature). No contract extension may lead to supplier embeddedness, increasing leverage over price/terms. Limited relationship development, missing joint working/innovation opportunities. In regulated procurement, avoiding regulations by keeping values below thresholds is non-compliant, risking legal challenges/penalties.

• For Supplier: Low-value ad-hoc purchases make planning difficult. Failure on one contract could lose client permanently, with no opportunity for demonstrated performance improvement.

1.3.2 Framework Arrangements and Agreements

Distinction between a framework arrangement (informal) and agreement (formal).

Informal Framework Arrangements

A loose setup without legal standing. Organization internally limits suppliers (approved list, approved contractor list, approved panel). No commonly agreed terms. Due diligence done on viability/suitability. Purchasers usually restricted to approved suppliers. Contractually, no legal standing; no guaranteed work or terms. Still offers advantages.

Advantages/Disadvantages of Informal Arrangements:

• Quick access to reliable, vetted suppliers for direct purchasing/limited tendering:

  • Purchaser good: Reduces tender process costs, speeds supply. Purchaser bad: Limits providers, might miss best one.

  • Supplier good: Better tender chance with fewer bidders. Supplier bad: No access if not on list.

• Familiarity (known client/supplier):

  • Purchaser good: Builds trust through regular work.

  • Supplier good: Builds trust through regular work.

• Keeping list updated (financial standing, H&S, data protocols, insurance, ESG, structure changes, accreditations):

  • Purchaser bad: Resource intensive to check documentation.

  • Supplier bad: Resource intensive to provide documentation for many databases.

• Open access for suppliers to apply anytime (unlike formal framework):

  • Purchaser good: Can include newly discovered providers. Purchaser bad: Resource for vetting, list can become unmanageable.

  • Supplier good: Can target potential customers without tender constraints. Supplier bad: Lists can become large, reducing win likelihood.

Remember: Informal framework arrangements are non-legally binding 'approved lists,' offering quick access to pre-qualified suppliers but resource-intensive management and risk of missing good suppliers.

Formal Framework Agreements

Differs from informal by having some legal standing. Not a contract (no consideration), but an overarching/umbrella agreement for creating contracts. Intended to be legally binding when a contract under the framework is created. Doesn't commit parties to contract, but sets T&Cs if one is created. Usually has unspecified terms needing inclusion in subsequent contracts. Should include price mechanism (less definitive than schedule of rates), allow for order size/location variations. Setup like a contract (tender/negotiation to select suppliers). Agreement defines:

• How call-offs are made (mini-competition or direct).

• Price calculation.

• Specification (options for different needs).

• Agreement duration.

• Who can access (a closed system).

• Limitations (e.g., contract running past framework end).

• Main terms or standard contract form.

Purchaser issues a call-off order or contract using framework terms (direct or mini-competition).

Types of Framework Agreements

Can be one-to-one, one-to-many, many-to-one, or many-to-many. For one supplier, contract placed directly. For multiple suppliers, framework defines call-off method and selection.

Direct Call Off

If multiple-supplier framework permits direct call-off, it must specify selection. In regulated procurement, strictly the highest-ranked supplier from original evaluations. In practice, suppliers often used in rotation or preferred for specific projects, maintaining some competition. If top-ranked gets most work, others may be reluctant to tender. Frameworks aren't meant to tie purchaser to single supplier (use term contract for that). Call-off may also refer to drawing down products/services from a contract.

Remember: Direct call-off under formal framework only if permitted, and framework defines supplier selection.

1.3.3 The Use of Mini-Competitions

A mini-competition is a tender process run under a framework agreement. The framework sets the process; only framework suppliers are invited (not obliged). Tender typically includes price and limited quality aspects, often price-only. Purposes:

• Calculate price for precise requirements.

• Refine contract-specific terms.

• Maintain competition among framework suppliers.

Advantages: Quicker and fewer resources than full tenders; due diligence done at framework level, not repeated. Risk: if framework poorly managed, due diligence checks become outdated.

Contracts Created Under Framework Agreements

Limitations on contract nature depend on the framework. Can be any standard/bespoke form, single purchase, or term contract.

Remember: Mini-competition is a tender under a framework, just for framework suppliers, used to clarify terms and foster price competition.

1.3.4 Call Offs

A call off (or term contract) exists for a fixed period, not a specific purchase. Used for regular needs of similar nature from a single supplier (e.g., equipment servicing, laundry, stationery supply). Unlike single-supplier framework, all terms (including price) are agreed at outset. Price may be annual/quarterly fee or schedule of rates (may differ by volume). A call off is the actual order under the contract, stating only item, quantity, delivery place. Supplier is committed to all orders. Benefits/risks are summarized in table 1.12. Disadvantages can be avoided with well-written, shorter-duration contracts and mechanisms for change/early termination.

Benefits for Purchaser: Guaranteed delivery, agreed prices (fixed or indexed), simple order mechanisms, schedule of rates pricing (for e-procure-to-pay), justified costs (market engagement, tender/negotiation), opportunities for joint efficiencies.

Risks for Purchaser: Locked into higher rates if prices fall, tied specification preventing innovation (rapid tech change).

Benefits for Supplier: Demand certainty (planning, cash flow), simple order/payment (reduced admin), reduced short-order costs (standardized products/stock holding), joint efficiencies.

Risks for Supplier: Loss if raw material costs rise and price fixed, hampered move to newer models if serving older specifications.

Remember: Refer to contracts for fixed periods as term contracts to avoid confusion with framework call-offs.

1.3.5 Services Contracts

Contracts can be classified by subject matter: goods, services, or works.

• Goods: Products, tangible items, materials (raw, components, finished).

• Services: Intangible, something done or provided by people.

• Works: Special services contracts for construction, buildings, civil engineering, and sometimes repair/maintenance. Complex area varying by legislation/regulation; procurement professionals must check case-by-case, aware of discrepancies even within a single legal jurisdiction.

Implications of the Difference Between Goods, Services and Works

Often, the contract type (goods, services, works) doesn't matter; general principles (offer, acceptance, consideration, misrepresentation) and drafting methodologies are similar. All can be one-off or term, informal or formal frameworks. Differences exist:

• Regulated procurement (public procurement): Financial threshold for full procedures is usually same for services/goods, but much lower for works. Affects tender procedure.

• International trade: WTO has similar but not identical requirements for services (GATS) as goods (GATT). GATS signatories can select which services apply, unlike GATT which applies to all goods. Vienna Convention relates only to goods; services contracts need explicit jurisdiction clauses.

• Key personnel: More critical in services contracts (consultancy, legal, training), especially if selection based on individual skills. Contracts need terms allowing termination if replacements don't meet quality.

• Local knowledge: Regulated procurement typically prohibits selection purely on location (national vs. international), with exceptions in developing/transitional/command economies. In market economies, wider view of location benefit/otherwise. Service provision may require specific local knowledge (laws, customs, politics, planning); specifications can require familiarity with relevant legislation.

• Data sharing: More likely in services, requiring robust data sharing protocols (e.g., GDPR in Europe).

• Insurance: Specific thought for professional indemnity insurance for services. Some insurances are mandatory.

• Conflicts of interest: More likely in professional services; robust clauses and administration needed.

• Codes of conduct: Many services involve supplier staff interacting directly with purchaser staff/customers, reflecting purchaser values. Codes of conduct (e.g., for respect, cultural sensitivity) should be contract schedules for enforceability.

Remember: Difference between goods, services, and works is important if procurement is regulated or subject to trade agreements, as different rules or financial thresholds may apply.

1.3.6 Contracts for the Hire and Leasing of Assets

Acquiring asset use can be done by hiring (short-term) or leasing (longer-term), rather than purchasing. Contract of bailment is the same. Ownership is not transferred, so no 'sale'; regulations for sale of goods (e.g., UK Sale of Goods Act, Vienna Convention) do not apply. Contract formation process is the same as for sale (offer, acceptance, consideration, intention, capacity). Many service contract terms apply (payment, H&S, insurance). Specific areas for hire/lease contracts:

• Why hire/lease rather than buy? Cost-effectiveness for intermittent use, preferable budget perspective for regular payments (but higher total cost).

• Hire the asset or buy the service? Consider if hiring equipment or contracting for the complete service (equipment + operator).

• Transfer of risk: Some ownership risks transfer to hirer (e.g., hirer insuring asset). Contract must clarify. NEC4 contract example: Client's liabilities include loss/damage to Plant and Materials after inclusion, Contractor's liabilities before inclusion. Ownership and risk may transfer at different times.

• Maintenance: Hire contract may include servicing (e.g., company vehicles) or be separate. Important to compare offers' inclusions.

• Period of hire and arrangements at end: State hire period and asset's fate (return to owner, at whose cost; hirer keeping). Financial implications for buy, lease, hire differ for finance, tax, liabilities.

• Extending scope: If more machines needed, contract must define options:

  1. New machines hired only for remaining original contract period.

  2. New machines hired for new period, old contract expires.

  3. New five-year period for all machines. Option 3 creates rolling contracts. Option 1 may be unviable for supplier. Option 2 is a compromise. Choice must be conscious and explicit.

• Reducing scope: ContractProvision for early return/disposal if fewer assets needed.

Remember: Key areas for hire contracts: reason for approach, transferred/retained risks, maintenance responsibility, end-of-period arrangements, and implications for hire period if scope changes.

Hire Purchase Agreements

Less common, but still exist. Asset is hired for a period, intending ownership transfer at period end (automatic on final installment, or option exercise by further payment). Legally, contract is for hire until final payment/option payment; only then does it become a purchase contract.

Chapter 2: Understand the Fundamentals of Specifications and Key Performance Indicators that are Included in Contractual Arrangements Made with Suppliers

This chapter details specifications and KPIs, building on their introduction in section 1.1. It covers their content and how procurement professionals design/negotiate it, emphasizing considering both purchaser and supplier perspectives. In some cases, purchasers design freely; in others, it's a negotiation; sometimes, suppliers dictate.

2.1 Analyze the Content of Specifications for Procurement Activities

Section 1.1 highlighted the specification's importance. Ambiguity or confusion leads to failures against the Five Rights of Procurement:

1. Quantity

2. Quality

3. Time

4. Place

5. Price

This section details how to draft specifications as binding legal documents, covering these 'Rights.' The Five Rights offer a basic, transactional approach; modern professional procurement also considers operational risk management, stakeholder engagement, supplier relationship management, and regulatory compliance, which also influence specification drafting.

2.1.1 Benefits and Risks of Market Dialogue with Suppliers

Specifications can be developed via sample versions (discussed later) or through communication with suppliers. Procurement officers must open and maintain dialogue with suppliers in relevant markets, often as a category specialism. Generalists also need market understanding. Market dialogue should be an ongoing exchange, not limited to specific procurements. Both parties gain insight into industry/sector developments, product roadmaps, supply opportunities/risks, and client roadmaps.

How to Develop Dialogue

Before initiating contact, be clear on:

• Objectives of the conversation.

• What information you are willing to divulge.

• Conflicts of interest and protection against them.

• Intellectual property issues and protection.

• Whether it's a procurement-led or technical/operations-led conversation.

Ideally, meetings should involve both procurement and technical/operational personnel. Wider stakeholders can add insight but complicate arrangements and increase commercial confidentiality breach risks. Approaches to engaging suppliers:

• General networking (events, social media): Establishes personal connection, basis for deeper talks. Disadvantages: Unlikely to deliver specific info, risk of perceived 'too close' relationship/conflicts of interest.

• One-to-one meetings: Most likely to deliver supplier-specific product development, insider view on supply chain risks, direct input into specification. Disadvantages: Supplier bias, may understate competitor advantages, risk of information not being shared across departments.

• Group visits (supplier to buyer, or buyer to supplier): Allows different teams to meet counterparts and understand challenges. Useful for supplier understanding of purchaser requirements. Disadvantages: Personnel may be unaccustomed to managing info flow, often too late to influence specification.

• Meet-the-buyer events (group events for future programs/contracts): Informs supply market on product/service development. Disadvantages: Often too late for specification, traditionally process-focused.

• Formal negotiations or competitive dialogues (contract-specific): Useful for refining draft specification into agreed contract spec. Disadvantages: Time-consuming, resource-intensive, limited number of participants.

What Kind of Dialogue?

Objectives must be clear (e.g., supplier ability for needs vs. general sector developments, near-future contract vs. knowledge upkeep). Clarity ensures professionalism and avoids souring relationships (e.g., supplier thinking contract offered when market capacity assessed).

How Do You Manage Market Dialogue?

• Clarity of objectives guides approach.

• All meetings should be documented (attendees, discussion, insights, follow-up). Market dialogue informs specifications, contract terms, supplier interactions, and future planning.

• Respect commercial confidentiality. Insights from one conversation inform questions in another, but avoid breaching confidentiality. Memorandum of understanding/non-disclosure agreement (NDA) formally binds parties not to undermine commercial interests (usually mutual).

Market Dialogue in Regulated Procurement

Previously, market dialogue was falsely believed prohibited in regulated areas (e.g., EU). Restrictions are generally on equity and transparency, and dialogue must halt once a specific procurement process begins (unless that process itself is formal dialogue). Public sector/regulated environment professionals should engage in ongoing market dialogue, especially since they cannot once an opportunity is advertised.

Remember: Market dialogue is ongoing, helps specification development. Beware supplier bias. Treat all info confidentially.

2.1.2 Drafting of Specifications to Form a Binding Legal Document

Section 1.1 discussed $10$ key things for specification design. A well-run procurement should follow project management lines, reflecting business as usual (BAU) processes. Scoping stage (managed by procurement professional) defines objectives, limits/constraints (budget, legal), processes, and team roles/responsibilities. Scoping questions on specification:

1. Who produces first draft? (Procurement, commissioning, contract manager, external expert). Influenced by organizational structure, skill/knowledge levels, re-procurement vs. new, workloads, timescales. All stakeholders should input; owning department approves.

2. Existing specification?

3. How well does it meet needs?

4. Identified shortcomings?

5. If none, what are broad objectives?

6. Defined minimum quality standard?

7. Quality aspirations above standard?

8. Technical constraints? (Physical, interoperability, input factors).

9. Environmental/social requirements/aspirations?

10. Stakeholders to consult? (Views on 1-9, draft spec; bring in early).

Remember: Good procurement is project-managed, starting with scoping. Scoping questions cover draft producer, existing basis, fundamental objectives, and relevant stakeholders.

Writing the First Draft of a Specification

Specifications rarely start from scratch. Most goods/services exist in the market, thus specifications exist. Start by assembling comparable specifications and stakeholder needs from various sources (internal, other companies in same/different sectors).

Obtaining sample specifications varies by sector/category. Competitive sectors are less likely to share. Public/third-sector organizations are more likely, but may not be at forefront of development. Suppliers are willing to help, but may bias towards their products. Non-disclosure agreements (NDAs) are common when sharing. Any acquired specification is a starting point only, subject to robust analysis and challenge by stakeholders (an iterative process). The $10$ key aspects of design guide this review:

• Purpose, conformance/performance preference, varying perspectives, relevance, scope, performance, improvement, clarity, regulatory compliance, operating environment.

Remember, starting specifications were designed for different situations. Understand those differences. Challenging the sample specification against your business scenario is critical. Don't simply change what doesn't fit; understand why features were included, as they may apply to your organization. Consider whole-life cost and end-of-contract/product life. A lot of information isn't directly available; procurement needs to challenge sample specs, don't just blindly change.

Remember: Previously used specifications must be robustly challenged to fit proposed circumstances. Analyze seemingly unmatched aspects to understand original intent and whether changes are appropriate.

Advantages and Disadvantages of Starting from a Pre-Written Specification

Advantages:

• Easier to critique than create; blank page is hard start.

• Covers necessary elements, prompts inclusion/omission decisions.

• Multiple samples provide ideas/options.

• Good for understanding quality variations (quality-price trade-off).

• Price brackets for quality levels enable intelligent business conversation.

• Cross-references to legislation/standards prompt compliance checks.

• Suggests innovation promotion/capture.

• Aligns with standard contract forms, ensuring consistency.

Disadvantages:

• Time wasted discussing irrelevant aspects.

• Relevant elements may be missed if solely relying on sample.

• Combining aspects from different samples creates inconsistency/ambiguity (e.g., terminology).

• Sample may require higher/lower quality than needed/affordable.

• Difficult to understand original operating environment for sample. References may be outdated.

• Different contract length/format can lead to including unnecessary things or missing value-adding opportunities (requiring contract approach review).

• Changing specification to align with different contract form creates inconsistencies.

Specification must not be drafted in isolation; it must mesh with other contract documents. Discussions may necessitate changing proposed contractual approach.

Shortcuts to the Specification

• Brand names: Generally prohibited in regulated procurement unless an alternative equivalent is permitted or product already compliant.

• Recognized standards: Company-specific, national (BSI), international (ISO), or trade body (see ISO 9001, 27001, 50001, 14001, 90-1, 3630-1, 18890:2018, 5790:1979 examples).

• Samples: Rare in large contracts, useful for new products/suppliers in short pilot programs (e.g., textiles, agriculture) to prove sustainability. Requires multiple copies for competitive procurement.

Drafting Legally Binding Specifications

For specifications incorporated into contracts, accuracy and sufficiency are essential for contractual disputes. Good procurement makes specifications only as definitive as truly needed; variant means increase competition/innovation. Risk: reduced standardization, increased operating costs. Table 2.4 details key sections (derived from BS 7373/ISO 14084):

• Title: Precise, succinct, reflects what's specified and context (tender, wider use, common vs. different operating conditions). Purchaser vs. supplier perspective.

• Version control/issue reference: Ensure consistent version (version number + date of issue minimum). Project management systems use detailed version control tables.

• List of contents: Ease of finding sections. No repetition; if unavoidable, cross-reference.

• Foreword (background): Context for specification. Explanation helps supplier/purchaser understand assumptions, removes misunderstandings early.

• Scope: Limits requirements. Detailed scope helps suppliers draw on past successes/failures. Avoids wasted time/money.

• Definitions: Define terms (words/phrases, abbreviations, units of measurement, time) to avoid disputes.

• Consultation requirements: Explicitly state if supplier/purchaser is responsible for ensuring compliance with national/local legal requirements. Failure implies provider of specification checked.

• References to other documents, standards or CoPs: Clearly reference full title, date, and obtainment info. Clarify if compliance is mandatory/desirable. Define hierarchy or procedure for discrepancies.

• Substantive requirements (bulk): Exactly what is required/offered:

  • Characteristics: design, dimensions, interface, materials, labelling.

  • Timescales: delivery/time-from-order.

  • Response times: failures, defects, repairs.

  • Performance/reliability: KPIs, operating conditions, testing, inspection regimes, tolerance, reporting.

  • Lifespan/durability: required/offered useful life, 'normal use' definition.

  • Packaging: protection, waste removal, environmental consequences.

  • Recycling criteria: regulations, best practice.

  • Social criteria: align with social factors.

  • Information requirements: user manuals, instructions, support availability.

  • Implementation: staff training, system integration, method statements.

  • Guarantees and warranties: availability, restrictions.

Remember: Key specification elements: product/service characteristics, delivery/response timescales, KPIs, lifespan, documentation, implementation requirements.

A specification incorporated into a contract becomes legally binding, typically as a schedule. Contract must explicitly refer to the schedule.

Using Standards in Specifications to Create Binding Legal Documents

Drafting legally binding specifications (technical/legal expertise, costly) can be eased by incorporating national and international standards. Benefits:

• Shorter specifications (no need to repeat details).

• Suppliers understand quickly (know if offer meets standard).

• International standards remove trade barriers for cross-border suppliers.

• Allows different approaches that meet desired outcome.

• Up-to-date international standards ensures recent influences considered.

Risks:

• In-house staff unfamiliar with applicable standards.

• Staff misunderstanding standards, creating conflicts (e.g., precise requirements disagree with standard, no precedence clause).

• Staff misusing standards in inappropriate situations, adding cost without value.

• Insufficient thought to standard updates.

• SMEs less familiar with international standards, disincentivizing responses.

Standardization of Requirements versus Increasing the Range of Products

Standardization reduces the range of products, but in some cases, increasing the range is better. Standardization isn't always wholly good, can lead to lack of innovation, generic solutions.

Advantages of Standardization:

• Clarity of specification: Both parties clear on requirements.

• Compatibility: Current/future products/services compatible.

• Economies of scale: Automation, rapid production, efficiency, cost reduction.

• Reliability: Flaw elimination, more reliable products.

• Service enhancement: Personnel become familiar, more adept.

• Time-saving in procurement: Less time to write/understand/respond to specifications.

• Accuracy of quotations: Fewer errors, reduces pricing for risk.

• Wider supply market: More suppliers, increased competition, less reliance on specialists.

• Narrower supply base: Fewer suppliers used, improved bargaining, reduced supplier management costs (accreditations, insurance, finance, ethics).

• Inventory savings: Less warehousing space (goods, spare parts).

• Reduced risk: Easier to switch to alternative if supplier fails.

Advantages of Increasing the Range of Products:

• Breadth: Appeals to more market segments, generates more revenue.

• Innovation: Creation of new products (e.g., Apple).

• Product differentiation: Increasing market share by differentiating products (often via branding/marketing, not just product itself).

• Cultural differences: Access different markets, influence product/packaging (e.g., Heinz mayonnaise variations, Red Bull colors).

• Economic factors: Cheaper versions for less affluent, complex for wealthier.

• Flexibility: Company better responds to market changes (legislation, economics, supplier innovation).

When drafting legally binding specifications, balance standardization benefits/drawbacks with increased product range to meet long-term organizational objectives. Quick/easy standardization may have wider costs.

2.2 Appraise Examples of Key Performance Indicators (KPIs) in Contractual Agreements

Building on section 1.1's discussion of KPIs in contracts, this section details examples for defining and implementing useful KPIs.

2.2.1 Defining Contractual Performance Measures or Key Performance Indicators (KPIs)

The Purpose of KPIs

Specifications define what a purchaser expects (characteristics, timeliness, pricing, delivery—the Five Rights). 'Right' varies by context (e.g., luxury vs. budget quality). KPIs measure how well the contract is performing in delivering these elements. Performance is a function of the contract, not just the supplier (influenced by purchaser actions, contract structure).

Consider purchaser KPIs (not procurement team KPIs, but contract-specific): e.g., payments made within terms (late payment is common complaint), timeliness/accuracy of orders. Performance management not only controls poor performance but highlights/rewards excellent performance.

How Many KPIs Do You Need?

Avoid measuring just because possible; limit KPIs to what really matters (IPA rule from Laura Tyson):

• Important: Don't measure insignificant things; monitoring/responding is costly.

• Potential Improvement/Problem: Should relate to solvable issues; if unchanging/uninfluenceable, monitoring is wasted.

• Authority/Ability to Influence: Must be within parties' control to influence results.

If a measure isn't important, isn't linked to improvement/problem, or can't be influenced, don't use it. You generally don't need more than five or six KPIs. Costs of capturing/analyzing KPI data must never exceed potential benefits.

Remember: KPIs are for improvement, must be important, address potential problems/improvements, and be influenceable. Costs must not outweigh benefits.

Types of KPIs

1. Binary measures: Only one of two options (yes/no, pass/fail). E.g., project delivered on time or not.

2. Numerical measures: Most common, a range of solutions. Definite number (e.g., incomplete orders) or percentage (e.g., inaccurate orders as % of total). Both approaches have arguments (e.g., $2\%$ over budget on $25$ million contract is significant $500,000$, but can also be presented as small percentage (e.g., $0.2\%$ if the contract was $250$ million), requires contextualization).

3. Qualitative or subjective assessments: Opinions on performance, often converted to numerical (e.g., rating 0-4). Surveys often include free fields for context, which can inform management despite not being direct KPI values.

Remember: KPI data may provide useful context even if not directly usable as a measure, especially qualitative assessments.

Sources of Data and Who Controls Them

KPIs depend on data availability. Much common KPI data already exists in systems:

• Cost data: Purchaser/supplier ordering and finance systems.

• Delivery data: Ordering and receipting records.

• Health and safety records: Often legally required.

• Help-desk/complaints records.

Information is acquired by purchaser or supplier. Some linked systems (procure-to-pay), some bespoke. Records can be electronic or paper-based (inefficient). Using existing systems reduces collection costs but risks designing KPIs around available data, rather than 'measures what matters.'

Key Considerations for KPI Data Collection/Storage:

• What data do you need? (Already collected, by whom, additional detail needed, ease of collection).

• Where is the data held? (Accuracy, transparency, direct access for both, duplication avoidance).

• Are there costs associated with collecting the data? (Benefits vs. costs, cost-effectiveness).

Contractual remedies for KPIs require reasonable certainty of performance. Each party having a right to audit the other's information helps, but grants access to commercially sensitive areas.

Remember: KPI data must be easily accessible and trusted by both parties.

Converting a Measure into a Score and Setting Targets

A metric alone isn't meaningful (e.g., $87\%$ accurate/on-time deliveries). Converting to a score involves defining 'what good looks like.' Common $0-4$ scale:

• $0$ = unacceptable (breach).

• $1$ = poor/below standard (cannot continue).

• $2$ = meets requirement (complies).

• $3$ = good/very good (exceeds without added cost/waste).

• $4$ = excellent (significant improvement without added cost).

Binary measures usually score $0$ or $2$. Numerical measures require determining ranges for $0, 1, 2, 3, 4$ scores, a value judgment based on:

• Severity of inadequate performance.

• Tolerance against specification.

• Targets for improvements.

KPIs can undermine specifications if not carefully designed (e.g., specification mandating $100\%$ compliance, KPI targetting $95\%$). This creates conflict. Specification must differentiate mandatory vs. tolerance/option.

Targets drive performance and are crucial for incentives. Targets should be SMART:

• Specific: Clear number (e.g., missed delivery dates, % on time, average time from order to receipt).

• Measurable: Quantifiable, even for user perception. Define measure and determination method.

• Achievable: Not too easy (no purpose), not too difficult (demotivating).

• Realistic: Motivating and achievable.

• Time bound: Period or deadline for achievement.

Other target considerations:

• Value of improvement: Can it be converted to cash (savings, cost avoidance, increased sales)?

• Cost of improvement: Who bears cost (capital investment, labor, altering ordering processes)?

• Unintended consequences: Diverting resources to one aspect harms another (e.g., faster delivery of non-urgent items increases cost, pressure on pricing).

Five Steps to Defining KPIs

1. Decide what matters: IPA rule (important, improvement/problem related, influenceable). Risks? Opportunities?

2. How to measure? Data source (existing/new)? Measure type (pass/fail, numerical, percentage)? Subjective input capture/analysis?

3. Who measures? Parties agree/discuss. Logically, party with easiest data access. Weigh data collection costs vs. trust. Shared data source ideal (e.g., procure-to-pay system).

4. How often? (Measure frequency, scoring frequency). Does one excellent quarter offset a poor one?

5. Convert to score? 'What good looks like.' What specification requires? Tolerance/penalty levels? Reward/bonus levels?

Remember: KPIs measure outputs of activity.

2.2.2 The Use of Service Level Agreements (SLAs)

KPIs, by linking to 'what good looks like,' can be converted into scores indicating compliance. Targets drive performance (with/without bonuses). Penalty clauses/service credits compensate for missed targets. Details of KPI monitoring and consequences must be documented and agreed, either embedded in specification/contract body, or in a Service Level Agreement (SLA).

What is a Service Level Agreement (SLA)?

SLA has different meanings:

• Non-contractual agreement between internal divisions.

• Single document within a contract suite.

• Incorrectly used to mean entire contract.

• Side-agreement, separate but legally binding.

Context is crucial. An SLA is always an agreement between a service provider and recipient, defining quality standards (e.g., robustness, timeliness, support responsiveness, availability), actions for non-achievement, consequences for unresolved issues, and (sometimes) for exceeding standards.

Remember: SLA can be non-contractual, a schedule, the whole contract, or a side agreement. Its nature/status must be clear. Function: define standards, detail consequences for not meeting/exceeding.

Supplier-Defined SLAs

SLAs are often purchaser-specified. However, suppliers may have standard SLAs (common in IT for software/hosted services) that purchasers must accept. Purchasers should avoid accepting supplier-drafted SLAs if possible.

Designing an SLA

Often confused with specifications. No definitive answer for where elements belong. Core SLA elements (table 2.8):

• Service definition: Exact supplier provision. Cross-reference specification if duplicate info exists.

• Quality definition: Mandatory minimums, unacceptable, poor, acceptable, good/excellent standards. Cross-reference specification.

• KPI details: What, how, who, how often measured. How measures convert to scores, targets. Usually separate from specification (SLA or performance management framework schedule).

• KPI management response: Actions/consequences for not meeting/exceeding targets. In SLA or core contract; cross-reference.

• Operational performance: Day-to-day issues (non-KPI) and management. Foreseeable failures, significance, resolution speed (e.g., ICT contract severity, goods delivery delays, liquidated damages). In SLA or core contract; cross-reference.

• Operational performance management response: Actions/consequences for each failure. First response, escalation, threshold for breach of contract issues (mediation, arbitration, courts). In SLA or core contract; cross-reference.

• Constraints or mitigating factors: Circumstances for waived/eased service levels (e.g., force majeure, purchaser actions hindering supplier). Cross-refer main contract clauses.

Ensuring the SLA is Contractually Binding

Wording of management responses/consequences is critical. Must be legally binding.

• Between departments/divisions in a single company: Internal SLAs are not normally contractual (company can't sue itself).

• Constituting the whole agreement: If SLA is the only document, it is the contract. Poor approach (other risks ignored). Must clearly state KPIs, scores, standards, minimums, acceptable ranges, mitigating factors, remedy times, remedies (damages, penalties, termination), process for remedies, handling inconsistencies. Must follow normal contract formation rules (offer, acceptance, capacity, consideration, intent).

• If only agreement, lacking consideration, must be executed as a deed to be legally binding.

• Part of a set of contract documents: More usual. May be called performance management framework or schedule/appendix. Identified as contract document. Items 1-7 (from 'Constituting…') must be clear. Cross-reference separate specification. Remedies in contract body, cross-referenced in SLA. Hierarchy of clauses may be needed.

• Stand-alone agreement for a separate contract: Uncommon. For urgency before full KPIs, or single SLA for multiple contracts. Clear cross-reference to relevant contract(s). Items 1-6 (from 'Constituting…') must be clear. Cross-reference separate specification. Remedies in SLA or main contract. Hierarchy of clauses may be needed. If created after main contract, needs additional consideration or deed execution.

Reviewing KPIs and Service Levels

KPIs and SLAs should be regularly reviewed. Frequency depends on contract/KPI nature (e.g., monthly for deliveries, quarterly for innovation). Review program in original request and contract. Initial targets based on past performance may be inappropriate for new contract (different supplier/conditions). Technology improvements can change cost-effectiveness. If KPI targets consistently exceeded, strengthen or replace them.

2.2.3 Typical KPI Measures to Assess Quality Performance, Timeliness, Cost Management, Resource Efficiency and Delivery

This section illustrates common KPI measures, highlighting potential issues (costs, risks, unintended consequences). Focus: contract KPIs, not procurement team KPIs.

Delivery Performance & Timeliness (Table 2.9)

• Delivery on time in full (OTIF):

  • KPI: Delivery compliance (quantity, all lines supplied).

  • Measured: Inaccurate deliveries as % of total.

  • Cost/Risk: Detailed checking time, order delays if part-orders rejected. Unintended consequence: Reduces overall project length, but may also increase purchaser's stock-holding if early deliveries.

• Delivery on time:

  • KPI: Delivery within agreed time.

  • Measured: Missed deliveries as % of total.

  • Cost/Risk: None (basic requirement).

• Average lead time:

  • KPI: Improvement of lead time compared to previous period.

  • Measured: % improvement over previous period.

  • Cost/Risk: Improvements by efficient processes or increased upfront resources (risk of later shortfall). May not reduce overall project length; purchaser may increase stock. Unintended consequence: Good emergency order performance encourages inefficient ordering by purchasers.

• Consignment stock availability:

  • KPI: Supplier holds adequate stock for reliable service.

  • Measured: Number of stockouts as % of requests.

  • Cost/Risk: None (basic requirement for normal order levels).

Product/Service Quality (Table 2.10)

• Product/service compliance:

  • KPI: Meets agreed standards, fit for purpose (whole-life cycle).

  • Measured: Acceptable items as % ordered.

  • Cost/Risk: Additional quality control costs may exceed gains. Stringent checking delays delivery.

• Reliability/durability:

  • KPI: Product reliable/durable.

  • Measured: Non-routine service call-outs per period.

  • Cost/Risk: Over-specifying routine servicing to pre-empt non-materialized faults.

• Usability/user satisfaction:

  • KPI: User-friendly product.

  • Measured: Periodic user survey ($0-4$ scoring).

  • Cost/Risk: Survey costs. Representative sample? Statistically significant response? Reasons for scores captured (else, wasted resource addressing wrong root cause).

• Technical support:

  • KPI: Acceptable quality of technical info/support.

  • Measured: Periodic survey ($0-4$ scoring) (as above).

• Supplier response time:

  • KPI: Timely on-site attendance for fault report.

  • Measured: Agreed response times missed as % calls logged.

  • Cost/Risk: Rush-to-site mentality reduces first-attendance resolution. Doesn't account for individual incident severity.

• Repair lead time:

  • KPI: Compliance with agreed lead times for repair/service restoration.

  • Measured: Agreed 'fixed or resolution' times missed as % repairs.

Health and Safety (Table 2.11)

• Endangering health and safety:

  • KPI: Zero reports of product/service endangering staff/public.

  • Measured: Count number of reports.

  • Cost/Risk: Focus on reportable accidents may miss near-misses.

Administration (Table 2.12)

• Number of credit notes per month:

  • KPI: Supplier issues no more than X credit notes.

  • Measured: Count credit notes.

  • Cost/Risk: May delay credit note issue to keep figures low, rather than ensuring accurate original invoices.

• Invoice preparation:

  • KPI: Invoice contains all info for prompt payment.

  • Measured: Invoices needing more detail as % issued.

  • Cost/Risk: None (basic requirement).

• Provision of quotations:

  • KPI: Quotation requests turned around within X days.

  • Measured: Total late & not-submitted quotes as % requested.

  • Cost/Risk: Most likely used on framework agreement, could result in 'cover prices' or quotes for unmanageable workloads.

• Documentation:

  • KPI: Full supporting documentation received for installations/updates within X days.

  • Measured: Count late documentation instances, average days late.

  • Cost/Risk: None (basic requirement).

• Management information:

  • KPI: Management info reports provided on schedule.

  • Measured: Count late documentation instances, average days late.

  • Cost/Risk: Info provided on time but rushed/inaccurate.

Best Practice & Continuous Improvement (Table 2.13)

• Supplier innovation:

  • KPI: Supplier proactive in suggesting innovative, workable solutions.

  • Measured: Number of innovations implemented.

  • Cost/Risk: Resource diverted to innovation instead of core contract.

• List of targeted value-added activities:

  • KPI: Targeted value-added activities identified in advance.

  • Measured: Number identified.

  • Cost/Risk: (As above).

• Value-added activities:

  • KPI: High success rate.

  • Measured: % of targets achieved.

  • Cost/Risk: None if 'success' adequately defined and core delivery maintained.

• Proactivity:

  • KPI: Supplier proactive in relationship management.

  • Measured: Periodic survey ($0-4$ scoring).

  • Cost/Risk: Relies on agreed definition of 'proactivity', could result in wasteful contacts/meetings.

• Responsiveness:

  • KPI: Responds rapidly without chasing.

  • Measured: Times requests chased as % requests.

  • Cost/Risk: None (basic requirement).

• Change/flexibility:

  • KPI: Flexible in response to changing requirements.

  • Measured: Periodic survey ($0-4$ scoring).

  • Cost/Risk: If supplier overly accommodating, purchaser may seek low-value changes, reducing contract efficiency.

• Openness and cooperation:

  • KPI: Open/cooperative in relationship (e.g., joint problem solving).

  • Measured: Periodic survey ($0-4$ scoring).

  • Cost/Risk: 'Perception' evaluation, can rely too much on personalities.

• Understanding of accountabilities and responsibilities:

  • KPI: Clear understanding under contract.

  • Measured: Number of rework requests and disputes.

  • Cost/Risk: Basic requirement, but poor performance may result from poorly drafted documents.

Contact Centre/Call Centre Service Measures (Table 2.14)

• Abandonment rate:

  • KPI: % calls abandoned by caller while waiting.

  • Measured: Calls abandoned as % total calls.

  • Cost/Risk: Resource dedicated to quick pickup at expense of response quality/resolution.

• Average speed to answer:

  • KPI: Average time to answer calls (seconds).

  • Measured: Time taken for each call averaged.

  • Cost/Risk: (As above).

• Time service factor:

  • KPI: % calls answered within given timeframe (e.g., $90\%$ within $30$ seconds).

  • Measured: Calls within timeframe as % total calls.

  • Cost/Risk: (As above).

• First time resolution (or first time fix):

  • KPI: Number of problems resolved at first contact.

  • Measured: % incoming calls not requiring repeat contact.

  • Cost/Risk: Better service but at expense of quick call pickup.

Cost Management (Table 2.15)

• Savings (unit price reduction):

  • KPI: Reduction in unit price.

  • Measured: % reduction over previous rate.

  • Cost/Risk: May not feed to budget savings if due to higher volumes. Only true saving if quality/scope maintained.

• Savings (total cost reduction):

  • KPI: Total cost reduction.

  • Measured: Final account sum as % of original contract sum.

• Cost avoidance:

  • KPI: Value of spend avoided by pre-emptive action (e.g., forward orders).

  • Measured: Estimate of likely spend without action less actual spend.

  • Cost/Risk: 'What if' measure, cannot be accurately verified. Subject to debate. Opportunity cost of funds unknowable.

• Transaction cost reduction:

  • KPI: Reduction in number of invoices.

  • Measured: Invoices in previous period less current period.

  • Cost/Risk: Only valid if order volumes constant/increase. Risk to supplier if consolidation interrupts cash flow. Invoice queries more complex/difficult, poorer relationship.

Chapter 3: Understand the Key Clauses that are Included in Formal Contracts

This chapter deeply analyzes common terms in commercial contracts, including express/implied terms, standard T&Cs, and model forms. Section 3.2 details typical clauses (liabilities, indemnities, subcontracting, insurance, guarantees, liquidated damages, labor standards, ESG). Section 3.3 covers pricing arrangements. When analyzing, consider both purchaser and supplier perspectives; balance is key.

Before approaching the market, purchasers must clarify the envisaged pricing model and willingness to explore alternatives. Transparency in pricing is a primary objective, breaking down elements for costing variations, applying adjustments, and allocating costs. Cost is total sum paid by supplier to produce goods/services. Price is amount paid by purchaser to supplier.

3.1 Analyse Sources and Purpose of Contractual Terms for Contracts that are Created with External Organisations

This section contrasts express and implied terms, and examines standard terms of business and model forms of contract.

3.1.1 Express and Implied Terms: Understand the Role or Use of Different Types of Contract Terms

A contract term is any provision creating a legal obligation (do/refrain/do in specific way). Breach has specific consequences. 'Contract term' also refers to contract duration; here, it's the legal sense.

Understanding the Contrast between Express Terms and Implied Terms

• Express terms: Specifically and clearly stated in words (oral or written); definitive agreement.

• Implied terms: Assumed part of contract even if not stated. Ways terms are implied:

  • Custom and practice: Normal in locality/industry/between parties. Applies if contract silent; overridden by express terms or specific side contract.

  • Statute: Governments mandate certain measures for contract types. Law states if express terms can override (e.g., UK Contract (Rights of Third Parties) Act 1999 allows overriding, EU Public Procurement Directive 2014 does not for termination right under Regulation 73).

  • International agreements (e.g., Vienna Convention).

Remember: Express terms are explicit and generally override implied terms, unless implied by statute and the law dictates otherwise.

Why Do You Need Express Terms in a Contract?

Express terms clarify the agreement, setting out:

• Obligations of purchaser/supplier.

• Rights of purchaser/supplier if other defaults.

• Handling circumstances beyond control.

• Confirming or overriding potentially implied terms (e.g., Regulation 73).

Express Terms and Contract Schedules

Contractual clauses often refer to schedules for technical/operational detail; schedules are easily updated. Contract clause is precise wording in main document; contract term is totality (clause + referenced schedule). Anything in a schedule is an express term.

Establishing What the Express Terms of a Contract Are

In well-drafted contracts, express terms are clear. But poorly drafted contracts pose issues:

• No written contract (oral negotiations): What was said? Was it all contractual intent? Courts decide based on facts (Oscar Chess Ltd v. Williams (1957) - car age statement wasn't express term).

• Written contract based on oral negotiations: How much of negotiation is part of contract? Written word usually supersedes prior statements, but now possible to argue contract is partly written/oral, or two contracts exist (J Evans and Son (Portsmouth) v. Andrea Mezario (1976) - verbal assurance overrode written T&Cs).

• Written contract where purchaser may not know conditions: Surprisingly, purchaser can agree to unknown conditions (Thornton v. Shoe Lane Parking (1970) - car park ticket terms not enforceable for unusual exclusion of injury; Interfoto Picture Library v. Stiletto Visual Programmes Ltd (1989) - high late fee was unusual term). Unusual/onerous terms require specific attention.

Remember: Oral contracts include express terms. Pre-contract negotiations might be implied into written contracts unless explicitly precluded.

3.1.2 The Use of Standard Terms of Business by Both Purchasers and Suppliers

Most organizations have standard terms and conditions for all transactions not subject to specific overriding contracts. They typically have two sets: one for purchasing, one for supplying, each protecting relevant interests (e.g., purchaser wants longer payment terms, supplier wants shorter).

Remember: An organization's standard terms differ when acting as purchaser vs. supplier.

What Are Standard Terms?

Short contractual agreements (1-2 pages), covering all eventualities for normal goods/services. Generic, offering basic protection, better than none. Often printed on standard documents (order forms, delivery notes), but text size can be small (small print). Electronic ordering systems use T&Cs on website, with links; unusual/onerous terms must be highlighted (Allen Fabrications v. ASD Ltd (2012) reinforces earlier case law).

Non-Negotiable

Standard terms are unilaterally imposed, often required for transaction to proceed, without negotiation.

When Should Standard Terms Be Used and When Are They Best Avoided?

Used for repetitive, low-value, low-risk, 'standard' transactions. Provide basic legal protection. Avoid for purchases with full tender, precise specification, and potential for negotiated variations (specific contract needed). Risk of becoming outdated (regulations, technology). Can create conflicts if attached to purchase orders used for call-offs under term contracts; must explicitly state non-overriding of formal contracts, or formal contracts state explicit overriding of standard terms.

Advantages:

• Time saved negotiating individually.

• Reduced administration costs.

• Consistency of approach (staff understand risks, both parties understand 'deal').

Disadvantages:

• Risk of ineffective incorporation (legal uncertainty, potential 'battle of the forms').

• Don't allow for contract-specific risks.

• Can become outdated.

• Create conflicts with call-off contracts.

What Happens if Any of the Standard Terms Are Ineffective?

An ineffective contract term cannot be enforced (e.g., exclusion of liability for negligence, unusual/unexpected conditions not highlighted, exclusion of liability for death, no warranty of fitness for purpose). In civil law countries, statutory rules may replace. In common law, statutory provisions may imply terms. Otherwise, courts consider 'balance of interests' for a 'just' outcome.

What Should be Included in Standard Terms?

Precise wording reflects business nature (goods/services) and role (purchasing/supplying). Key areas for purchasing perspective (Table 3.5):

• Definitions: Precise meaning for key phrases (narrow sense, different from dictionary).

• Express term to override other standard terms: Avoids 'battle of the forms' (e.g., 'These terms shall apply irrespective of any terms printed on the supplier's standard operating documentation…').

• Express term for framework/term contracts: Clarifies precedence (e.g., formal contracts override standard terms on purchase orders).

• Formation of the contract: Defines contract documents (order form, standard terms, implied by law), optionally 'but nothing else' (risks if order cancelled/amended).

• Order of precedence: Explicitly states conflict resolution (e.g., 'express written agreement…; (2) our order; (3) these Terms').

• Price: Stated price, tax treatment, inclusions/exclusions, currency, discounts.

• Invoicing and payment: Invoice requirements (PO number, send-to, cut-off), payment period (calendar/working days), entitlement to set off debts.

• Specification: Cross-reference, intended purpose. Facility to change specification/cancel order and price implications.

• Obligation to comply with the law: Supplier must comply with all laws (including changes), deemed included in price.

• Delivery and risk: Delivery place/time, 'time is of the essence' clause, ownership/risk transfer point, right to reject, defect management.

• Warranties and liability: Warranties (quantity, quality, description, fitness for purpose, qualified staff), appropriate insurance cover.

• Intellectual property and similar rights: Ensure all relevant rights provided.

• Termination: Circumstances for termination, fate of delivered-but-unpaid goods.

• Confidentiality and use of data: General data protection/management rules, compliance with relevant laws.

• Ethics and environmental, social and governance: Requirements regarding ethical considerations (at least international law), specific details depending on business/priorities.

• Law and jurisdiction: Which country's legal framework/courts apply for disputes.

Remember: Standard T&Cs must cover all key areas, even if a short document.

3.1.3 The Use of Model Form Contracts

This section covers model form contracts, their use, and safe implementation.

Why Are Contract Documents So Complicated?

Drafting contracts is complex, requiring category knowledge (trading norms, tolerances, compliance targets) and legal knowledge. Obscure language (legalese) in common law jurisdictions stems from legal precedent (ratio decidendi, obiter dicta) where court judgments give specific meaning to phrases. This ensures legal certainty – knowing what law means, how courts decide disputes – which saves time/money by avoiding litigation. Procurement professionals need a minimum legal knowledge and strong relationships with legal teams.

Remember: Contracts are complex for a reason. Simplifying language/punctuation without legal advice may remove protection.

Why Model Forms of Contract Exist

Standard terms are for low-value, low-risk, repetitive purchases, not for bespoke specifications/tenders. When standard terms are insufficient, model forms of contract are a good alternative to bespoke contracts. Disputes generally hinge on price, delivery, quality, contract management, data/property rights, warranties/guarantees. Within a sector, consensus on problems/protections leads to model forms – templates with core wording for normal scenarios. Suppliers/purchasers familiar with model forms welcome them.

Examples of Model Forms:

• NEC (New Engineering Contract): Construction (UK).

• JCT (Joint Contracts Tribunal): Construction (UK).

• AS (Australian Standards): Various purchase types.

• FIDIC (International Federation of Consulting Engineers): Widely used internationally for construction.

• IMechE/IET (Mechanical Engineers/Engineering and Technology): Electrical, electronics, mechanical plant (including software).

• CIPS (Chartered Institute of Procurement and Supply): IT functions.

• ITC (International Trade Centre): Small companies doing international business.

Construction sector has a bias due to long-standing professional institutions, litigation scope, and common formula. Model forms are expanding; organizations create internal 'model forms' adapted from others, checked by legal teams. These reflect typical contracts (contract-specific details, standard common clauses, schedules).

Remember: Model forms contain standard core clauses but are templates requiring project-specific supporting documentation.

How Model Forms of Contract Are Developed

Traditionally developed by professional institutions protecting members (often supply-side). More recently, standards organizations, governments, and independent third parties develop more balanced models. Original professional bodies widened stakeholder representation. This aligns with a shift from adversarial to collaborative procurement. Working groups regularly review forms based on changes in law, legal disputes highlighting ambiguity, and technological change. Involvement in these groups offers professional development and influence for procurement professionals.

How to Use a Model Form of Contract

Using a model form isn't 'done.' Care is needed to ensure it protects interests, avoids ambiguity, and accurately reflects the agreement. Every clause must be reviewed for applicability. Procurement professionals need adequate training and legal advisors for complex transactions. Most models have guidance notes highlighting:

• Blank spaces to fill in.

• Optional clauses to delete.

• Options with default positions (e.g., defects periods).

• Schedules to complete/attach.

Organizations may have standard amendments to industry models. These can be separate amendment schedules, properly referenced. Risk: specific project may not need all standard amendments, or non-standard ones are needed (requiring project-by-project review by trained personnel). Viewpoints on amending models:

• Strict view: Never amend key clauses beyond options; if unsuitable, use project-specific contract. Risks breaking internal logic, confusing precedence, altering contract balance.

• Opposing view: Amend models as parties are familiar, understanding embedded mechanisms. Avoids reviewing familiar clauses. 'Knowns' allow focus on changes. Easier for tender/contract stages. Requires continuous review of case law and model changes.

Remember: When amending standard forms, ensure all cross-references are appropriately amended.

Key Steps in Using Model Forms:

1. Identify/develop appropriate models for common purchases.

2. Identify/develop appropriate guidance, including standard amendments.

3. Review model and intended use with legal advisers.

4. Review guidance, confirm appropriateness (seek alternative if not).

5. Select appropriate model for specific procurement.

6. Train procurement staff.

7. Complete blanks, options, schedules.

8. Embed draft contract in tender/negotiation process; agree terms.

9. Manage contract normally.

10. Continuously review case law impacting interpretation & template changes for future use.

Advantages and Disadvantages of Model Forms of Contract

Advantages:

• Saves time/resource drafting bespoke contracts.

• Suppliers/purchasers familiar with main terms.

• Specific to sector/purchase type.

• Measure of legal certainty.

• Consistent structure.

• Lower costs to produce/approve.

• Easier to resolve disputes.

Disadvantages:

• Poorly trained staff may use incorrectly/choose inappropriate model.

• Amendments create ambiguity.

• May become outdated.

• May be biased (supplier/purchaser).

3.2 Recognise Examples of Contractual Terms Typically Incorporated into Contracts that are Created with External Organisations

This section examines key terms: liabilities, indemnities, subcontracting, insurances, guarantees, liquidated damages, labor standards, and ESG issues. These are typically in standard clauses of model forms. Analysis considers both purchaser and supplier perspectives for effective balance.

3.2.1 Key Terms in Contracts for Indemnities and Liabilities, Sub-Contracting, Insurances, Guarantees and Liquidated Damages

Indemnities and Liabilities

Most contracts include liability (legal responsibility for injury/loss/damage compensation) and indemnity (security/protection against loss, usually financial). Some liabilities depend on failure (negligence); others are strict liability (absolute, no fault needed). One party indemnifying another means offering this protection. Parties often seek to exclude or limit liability (scope or value).

Key Aspects of Liability & Indemnity Clauses (Table 3.7):

• Liquidated damages: Circumstances and rates for late delivery (e.g., $300 per week).

• Exclusion of liability (force majeure): Some liabilities cannot be excluded (strict liability, criminal offence); contract generally confirms non-exclusion.

• Negligence of the other party: One party shouldn't be responsible for consequences caused by other's negligence. If client contributes, contractor's liability is reduced, not removed.

• Indemnity: Clauses may be complex, especially in common law countries; civil law definitions are often in codes.

• Financial limit of indemnity: Businesses need to plan for liabilities. Liability should be capped (e.g., value of fees), but potential loss may exceed fees. Indirect/consequential losses are nearly impossible to calculate and generally excluded.

• Limiting scope of liability: (covered above)

• Transfer of liability (transfer of risk): Point at which liability for damage to goods/materials transfers (e.g., from supplier to purchaser after fitting, as in NEC4). Can be in 'liabilities' or 'ownership and risk' (ownership and risk may not transfer simultaneously).

Remember: Liability is legal responsibility; indemnity is promise to meet costs. Contract terms limit liability by capping indemnity levels.

Insurance

Insurance transfers financial risk from the legally liable party to an insurer. It's a pooling of risk: insurer takes fee (premium), covers costs up to agreed limit for risk events, relies on few occurrences. Insurance is referenced in contracts because liabilities can be significant, potentially catastrophic for smaller firms, disrupting cash flow or causing collapse. Contracts typically require suppliers to insure and set out type/level of cover.

Types of Insurance Cover (Table 3.8):

• Employer's liability: Statutory legal requirement for employers; covers injury to staff during employment. Shows responsible business, compliance, manages cash flow risk. Minimum values set by law.

• Public/products liability (third-party cover): Injury/loss/damage caused by products, on premises, or by personnel actions. Public liability for services, products liability for goods. May need both (catering company) or one (management consultant needs public, not products).

• Professional indemnity insurance (PII/PI cover): Losses from poor/negligent professional advice (legal, accountancy, engineering). Important to understand, not always obvious cover is needed (e.g., building company design).

• Goods in transit cover: For goods lost/damaged during delivery. Clause states who arranges/pays, not necessarily owner.

• Works/buildings: Insurance of partially completed works is complex. Model forms offer options for insuring building/works, joint names client/contractor policies.

• Level of cover required: Influences premium. Contracts stipulate minimum. No definitive calculation rule; organizations have standard requirements, reviewed periodically. Cost-benefit analysis is crucial: higher cover means higher contract price.

• Aggregate or 'each and every': Aggregate cover = total claims cannot exceed limit (later claims may not be met). Each and every claim = limit applies per individual claim (better, higher cost).

• Scope of cover: Difficult to detail; uses phrases like 'all customary risks.' Procurement professionals must know these risks and check supplier policies (e.g., restrictions on working at height, other jurisdictions, transport methods).

• Auditability of insurance: Purchaser should have right to access evidence of cover. Ideally, contract allows purchaser to arrange insurance and reclaim costs if supplier fails to meet requirements.

Remember: Insurance ensures offending party can meet financial costs. Contract terms require subcontracting also appropriately insured.

Subcontracting

Commercial contracts are often layered (tiers): main contractor/supplier appoints others (subcontracts). Subcontracts sit below, are directly related to, and partially governed by a higher contract. (e.g., plumbers for a school). Tier 1 is direct; Tier 2 is direct supplier's contractor, etc. (Figure 3.5). Builder's supplier of bricks not usually a subcontract, but a standalone supply contract. Subcontractor generally used regardless of supply nature.

Why is Subcontracting Referenced in Contracts?

Purchaser wants to control supplier's subcontracting for:

• Supply chain: Vetting effort is wasted if subcontractor isn't vetted to same degree. Need to control choice.

• Contract terms: Ensure main contract terms are reflected in subcontracts (e.g., ethical payment terms, as highlighted by European Commission's Public Procurement Directive 2014 requirement for $30$ day payment terms throughout public contract supply chains).

• Liability: Main contractor must remain legally liable (assignment or novation arrangements transfer responsibility/benefits to third-party).

Things to Consider for Subcontracting Clauses (Table 3.9):

• Permit subcontracting? Valid reasons not to (security, confidential info). Generally accepted as beneficial (allows smaller firms, increases competition, spreads risk). EU Public Procurement Directive 2014 requires permitting, but reasonable rules on how.

• Control over selection? Generic need for approval (not unreasonably withheld) is common. Clarify what 'unreasonably' means (e.g., license/qualification). Be explicit for sensitive requirements (secrecy).

• Influence over subcontract terms? (e.g., prompt payment, data protection, insurance). Sample wording provided for payment control (Crown Commercial Service) and insurance.

• Main contractor retains liability: Wording needed (e.g., 'The Contractor shall be responsible for the acts and omissions of its Subcontractors as though they are its own.').

• Beware of price impact: Restrictions on choice may increase price due to less competition or higher admin costs.

Remember: Contract terms control subcontracting, including permission and specific terms (payment, insurance).

Guarantees

A guarantee is a formal written assurance of quality conditions and a specific remedy for failure (repair/replacement if product fails within period). Applies more to goods, outlives the contract (e.g., hotel mini-fridges). More complex products/longer desired guarantees increase likelihood. Guarantees have a cost for suppliers, but value to purchaser often exceeds cost.

Things to Consider for Guarantees (Table 3.10):

• Need for guarantee? Consider likelihood/impact of failure. Essential if failures are costly to rectify. More units purchased, higher chance of faulty one.

• Duration? Manufacturers offer standard periods (2-10 years). Extended guarantees may cost extra, often not worth it as failures tend to be early/very late.

• Inclusions? Depends on product. Simple replacement vs. repair (if component, ensure 'parts and labour' cover). Define covered faults/failures (not accidental/wilful damage). Consider response times (like servicing contracts). Complex guarantees as separate schedule or in specification.

Liquidated Damages

Damages are financial payments for loss. Liquidated damages (or 'liquidated and ascertained damages') are predetermined sums payable for a specific breach, usually late delivery. They are compensation, not a penalty, a genuine pre-estimate of loss. Figures are set by purchaser or agreed in negotiations; keep record of estimate calculation. Romalpa clause states how damages claimed (specific notice to supplier). Can be paid or deducted from payments (must be clear it's a debt, may enable interest/right of set-off).

Things to Consider for Liquidated Damages (Table 3.11):

• Which breaches? Only when no other suitable remedy. Most often for late delivery (cannot be 'unmade'). Quality issues need rectification.

• Estimating the sum: Genuine estimate of financial loss due to lateness (e.g., lost rental income, extra loan interest, staff salaries for late building). Losses accrue over time, so expressed as sum per period (e.g., $3000$ per week).

• Tying figure to degree of lateness: (covered above)

• Process for claiming: Romalpa clause requires specific notice. Contract may state whether paid or deducted from payments due. If deducted, clear it's a debt for audit trail.

Labour Standards and Ethical Sourcing

Contractual terms for labor standards/ethical sourcing are one tool; joint working and education are more impactful. Terms provide ultimate leverage if supplier management fails. ESG issues (environmental, social, governance) are discussed in next section.

Remember: Contract terms are one tool for ethical sourcing, supported by right of audit.

3.2.2 Terms that Apply to Labour Standards and Environmental, Social and Governance Issues

Ethical behaviours and adherence to labour standards and ESG issues are prominent. Critical reputation aspects: investors' and consumers' perceptions. Tarnished reputation ($labor$ standards, ethical sourcing failures) leads to diminished investment/sales, share price fall, potentially business collapse. Businesses recover, but incur significant cost in dealing with association. Motivation: 'right thing to do' but also 'business beneficial thing'. Procurement professionals need to understand motivators to phrase messages effectively. CIPS promotes ethical sourcing/contracting (ethics test for members).

Labour Standards

Labour standards are employment terms and conditions, particularly for lowest-paid, most vulnerable workers. Procurement professional's obligation: (a) comply with relevant national and other state laws (including subcontracts, upstream supply chains), and (b) encourage higher standards commercially. Commercial contracts must mandate legal compliance, but commercial leverage can achieve more by linking economic rationale to public good. Child labor is complex: definition of 'child' varies, and stopping child labor may harm poorest families if it's their only income. Procurement professionals must recognize this broader context.

Rather than complex clauses referencing treaties, set requirements in terms of local laws and practical application (e.g., specific working hours). Clauses must permit unannounced local site audits. Ultimate sanction: contract termination, but practical response is understanding reasons and improving situation.

Remember: ILO sets minimum labor standards; many countries enhance them. Contracts must comply with international/national standards as minimums. Commercial pressure can enhance terms. Improvement efforts always precede remedies.

Environmental, Social and Governance (ESG) Issues

ESG refers to the ethical and sustainable impact of procurement activities. Broad concept: supply/service origin, logistical impact, responsible end-of-life. Incorporate ESG provisions into contracts/schedules. Moral responsibility, plus reputational, legal, financial consequences for non-compliance. Ethical sourcing ensures products obtained responsibly/sustainably, workers safe/fairly treated, and environmental/social impacts considered. Impact on workers covered under labor standards.

Embedding ESG requires a multi-strand approach:

• Direct supplier actions: Own labor force, environmental policies.

• Subcontract arrangements: Ensure rules flow downstream.

• Indirect inputs (upstream supply chain): Supplier's suppliers' actions (materials, components).

No quick, easy clauses. Starts with selecting right supplier (demonstrated ESG commitment). Within contract, various ways to encourage/mandate ESG:

• Labour standards: Enforce international/national/local laws. Go beyond minimums? Formal commitment to eradicating modern slavery, requiring supplier/supply chain support. Sample UK Modern Slavery Act wording provided.

• Environmental impacts: Contract's impact on water/energy use, process pollution, waste disposal. Embedded energy and whole-life impacts. Clean production vs. safe disposal. Deal via clauses requiring legal standards, quality/design requirements (eco-labels), KPIs for impact scores.

• Social impacts: Health/wellbeing of service users (safeguarding), accessibility of product/service. Deal via clauses requiring legal standards, quality/design requirements, KPIs.

• Fraud, bribery and corruption: Explicitly state unacceptable behavior; ultimate sanction: termination and barring from future contracts. Sample wording referencing US, EU, UK, Singapore anti-bribery/money laundering laws.

• Subcontracting: Conditions on direct contractor must flow to subcontracts (shown by Modern Slavery Act example).

• Upstream impacts: Source of energy, timber, conflict minerals. Avoid association with rainforest decimation/conflict minerals; encourage fair trading with contractual clauses and traceability certifications. Methodology varies.

ESG is measurable (CIPS definition). KPIs needed for ESG requirements to track progress/gaps (refer section 2.2).

Including Environmental, Social and Governance Criteria in Specifications

ESG criteria are increasingly specified. Procurement professionals must understand why, its business value, appropriate criteria, and how to include.

Driving Forces for Increased ESG Criteria (Table 3.13):

• Ethics: Labour conditions (modern slavery, child labour), bribery/corruption. Criteria: Compliance with international labor standards, support for education, adult worker rights awareness.

• Customer-led: Changing demands, willingness to pay premiums, brand reputation, boycotts/protests. Criteria: Organic production, ethical trading (Fair Trade), environmental labelling (Forest Stewardship Council, Marine Stewardship Council, GHS labelling), avoidance of certain inputs, traceability (conflict minerals).

• Stakeholder pressures: International agreements, government policies, proposed regulations, internal policies/marketing, funding agreements. Criteria: Waste separation/recycling, energy use/carbon footprint, water conservation, community initiatives, training/employment initiatives, use of local/SME firms.

• Economic incentives: Cash savings, process efficiencies, skills shortages/talent management, waste reduction. Criteria: Waste/energy/water reduction, training/apprenticeships.

Remember: ESG criteria are important due to regulation, consumer/stakeholder pressure, informed stakeholders, and cost savings from waste reduction.

When to Define Environmental, Social and Governance Criteria

Detail evolves with specification refinement but not ad-hoc. Organization needs overarching strategy/policy for ESG objectives in procurement/supply chain. Consider supplier selection/monitoring processes and contract scope. Strategy favoring smaller suppliers may conflict with environmental approach needing capital investment. Short-term contracts don't support apprenticeships. All internal stakeholders must understand how aspirations/policies impact procurement decisions. Ongoing study of supply market and pre-market engagement for high-value/risk contracts should analyze feasible, effective, and efficient ESG gains.

ESG and Social Value

Public sector often views ESG/social value as an add-on. This is naive; every specification item has a cost. Cost of reusing/recycling waste might be less than disposal + virgin materials. Other criteria may add costs (for all or some suppliers). If disproportionately affecting some suppliers, consider if it matters (market efficiency vs. levelling playing field for national security, supply security, risk spreading). Price premiums for certain providers are generally not permitted in most public-sector procurement regimes (except some developing countries).

The Impact of ESG Criteria on Price

If ESG adds cost, supplier covers it by:

• Increasing overheads element of price.

• Increasing price of goods/services.

• Absorbing cost, reducing profit margin.

No definitive 'best' option. Depends on general production methods, contract-specific costs, market competitiveness. Procurement needs to understand this cost element to assess value of criteria and explore more cost-effective ways.

Monitoring ESG Criteria in Practice

Purchasers need assurance that what's paid for is delivered. ESG elements may not be visible in surface performance or goods/services. Monitoring requires audits and site inspections of supplier's operations. Complex and costly, especially in global supply chains. If not done, no certainty of compliance.

Remember: ESG criteria may add cost (not always). Purchasers seek cost disclosure to ensure proportionality. Monitor suppliers closely, likely needing on-site audits.

Incorporating the Criteria into the Specification

ESG criteria should be written into specification like any other requirement:

• Use international standards.

• Avoid conflicts with other aspects.

• If different aspects use standards, ensure standards don't conflict.

• Include order of precedence for standards if conflicts arise or are updated.

• Clearly state minimum, mandatory, aspiration, or target level (impacts breach of contract determination).

ESG Criteria in Public Sector Contracts

Increasingly encouraged (e.g., UK Public Services (Social Value) Act 2012, Australia's Social Procurement Guide, South Africa's Preferential Procurement Policy Framework Act, USA Socioeconomic Programs for Small Businesses). Aims: use public money for public good via procurement. Social benefit must directly relate to contract. Transparency still applies; social criteria cannot undermine equitable treatment unless set-aside or preferential programs are intentional. Implementation requires tender process design and supplier evaluation, plus direct criteria. Encouraging certain firms to tender is wasted if specification prevents delivery.

3.3 Recognise Types of Pricing Arrangements in Commercial Agreements

This section covers pricing arrangements (schedules, fixed, cost-plus, indexation, incentivized contracts, payment terms). Focus: contractual incorporation and use. Procurement process must clarify envisaged pricing model and willingness to consider alternatives. Pricing transparency is key: breakdown elements for costing variations, applying adjustments, allocating costs.

Cost and Price

• Price: Amount (currency units) paid by purchaser to supplier.

• Cost: Total sum paid by supplier to produce goods/services.

Price must exceed cost for profit. Competitiveness, business strategy, bargaining power determine degree. Supplier may accept short-term loss (new market entry, skilled employee retention), meaning price < cost.

Remember: Price is purchaser's payment; cost is supplier's inputs.

3.3.1 The Use of Pricing Schedules

Pricing is critical for both parties. Simplest contracts may not need schedules if price is fixed, unchanging, and needs no breakdown. Most commercial contracts are more complex:

• Call-off contracts: No predetermined total price.

• Total fee known: Payment in stages (milestones, e.g., construction).

• Price breakdown needed: For accurate costing changes (e.g., staff day rates) or accounting (allocating costs across localities/cost centers).

• Variation orders: Changes to scope/duration require accurate cost impact assessment; guaranteed maximum price (GMP) protects against excessive increases.

Purchasers must consult stakeholders (contract managers, finance, strategic planners) before market approach to understand how financial information will be used, designing price schedule to accommodate this. Overly complicated schedules are less easy to use or compare offers.

Remember: Design price schedules considering how price info will be used beyond invoicing/payment; consult other stakeholders.

Terminology: 'Price Schedules' and 'Schedule of Rates'

• Price schedule (or 'fee schedule'): Attachment stating prices. May include how/when charged (or separate section if complex).

• Schedule of rates: Itemized list of component parts in lump-sum contract, or unit prices for individual products. Rates may differ for different order volumes.

Calculating and Expressing Price

• Unit price: Price in dollars per unit (single item, batch, e.g., box of 10 reams of paper). Linear pricing (same unit price regardless of quantity) vs. non-linear pricing (unit price changes with volume, e.g., cheaper for larger orders). Most common for goods.

• Hourly rates/day rates: For services where labor is primary cost (consultants, lawyers). Specific unit pricing. Schedule may show different rates by seniority/expertise, minimum charges (e.g., on-site work).

• Combination rates: For mixed goods/services (parts + labor). Schedules combine; common in repairs/maintenance. Can use linear or non-linear terms.

Remember: 'Units' on price schedules can be batches or other measures (e.g., square meters).

The Use of Standard Schedules

Available for certain supply types (professional bodies for members, commercial, stakeholder groups). Give reasonable price estimate for goods/services. Negotiations/tenders reference these. Example: UK housing sector used NHF schedule for maintenance contracts (variation percentage): simple pricing, direct comparison. But broad, doesn't account for specific housing stock needs. Shifted to specific schedules or 'price-per-property' approach.

Incorporating the Prices into the Contract Terms

Pricing schedule completion is fundamental to tender/negotiation. Final version must be properly incorporated into contract (e.g., contract term states goods/services charged at schedule rates, schedule appended). If standard schedule referenced, contract must specify edition (reference number/date) and whether it updates. Disputes arise if unclear (e.g., 8th vs. 9th edition rates). Options:

1. No change to contract rates.

2. Rates tied to original edition; adjustment by changing percentage.

3. Fixed percentage applied to new editions.

Option 1: price certainty, no gain/loss from average rate changes. Option 2: free negotiation for changes. Option 3: retains discrepancy from benchmark, risky for both as neither party controls standard schedule rates.

Remember: Standard schedules are starting points, not always compulsory. Tenders/negotiations use them as reference, avoid designing new schedules.

3.3.2 The Use of Fixed-Pricing Arrangements

Fixed-fee pricing (or fixed-pricing arrangements) is an alternative. For goods, purchaser quotes fee for one order (simplest use of firm prices). For services/works, two circumstances:

• Small-to-medium scope projects: Short timelines, adequately specified, limited likelihood of specification/scope/cost changes. Price calculation is simple arithmetic.

• Repeated services with slight variations: Fixed-fee works if overall costs even out based on average cost. Requires assumptions (annual service frequency, minimum specification scope).

Fixed-fee example: legal services for housing association (table 3.18). Specific services (injunctions, debt recovery) are commonplace, lawyers know typical processes, but cannot predict court appearances. Costs average out over caseload.

Benefit and Risk in Using Fixed-Pricing Arrangements

Some argue fixed-price places all risk on supplier (no extra payment for work/cost changes). But purchaser can't claim rebate if input factors change favorably, or less work required. Cost risk is shared, not necessarily equally. Depends on:

• Specification accuracy.

• Supplier resistance to post-contract changes.

• Original price estimation accuracy (supplier risks loss, purchaser risks inadequate budget/poor value for money). Relies on accurate data and understanding volume influences.

Main advantage: planning advantage. Purchaser has budget certainty, supplier has income certainty. Fixed at outset.

Fixed-fee pricing may not cover whole contract; can combine fixed pricing with schedule of rates (e.g., legal services example).

Fixed-pricing disadvantages often outweigh advantages (Table 3.19). Inflexibility makes it suitable only for quickly/firmly established requirements and short contracts.

Advantages: Budget/income certainty. Impact of supplier's cost base changes not passed to purchaser (supplier gains if costs diminish, purchaser gains if costs rise).

Disadvantages: Time for full specification. Impact of supplier's cost base changes not passed through (supplier gains if costs diminish, purchaser gains if costs rise). Assumptions on cost balance may lead to disputes. Potential quality issues if fixed price too low ('supplier will deliver down to price').

Remember: Fixed pricing and schedule of rates can be combined in a contract.

3.3.3 Cost-Plus and Cost-Reimbursable Pricing Arrangements

Cost-plus and cost-reimbursable are interchangeable. Price moves with costs. Cost is biggest influence on price.

Understanding Cost Impacts on Price

Supplier price setting tied to cost-base: fixed costs (don't change with production volume) + variable costs (fluctuate with production). (Figure 3.6). Sustainable contract needs supplier to at least break even (cover costs); worthwhile contract needs profit. Prices set to ensure profit. Break-even point met, fixed costs covered. Beyond break-even, supplier only needs to charge for variable costs; fixed cost contribution becomes additional profit (