Contract Drafting, Negotiation and Legal Risk Analytics

Introduction and Context

Cross-border contracts are instruments of governance, not merely records of commercial agreement. They allocate economic value, define operational responsibilities, manage uncertainty, create evidence for enforcement, and establish procedures for responding to failure. In international business, these functions are complicated by differences in legal systems, languages, currencies, regulatory regimes, business cultures, dispute-resolution mechanisms, and political conditions.

A professionally drafted international contract must therefore do more than state price and delivery. It should answer five questions:

1. What has each party promised to do?
2. What facts may the other party rely upon?
3. What happens when performance is delayed, defective, unlawful, or impossible?
4. How are losses allocated and limited?
5. How will the relationship be monitored, changed, terminated, and disputed?

Contract drafting is consequently an exercise in translating commercial objectives into legally enforceable rules. Negotiation is the process through which those rules are shaped. Legal risk analytics provides a disciplined method for identifying, evaluating, prioritizing, and monitoring the risks created by the agreement.

This chapter focuses on representations, warranties, covenants, indemnities, limitations of liability, audit rights, compliance clauses, boilerplate, due diligence, risk matrices, scenario analysis, and contract-lifecycle metrics. It assumes familiarity with the basic elements of contract formation and with the broad distinction between common-law and civil-law approaches.

Learning Objectives

By the end of this chapter, a student should be able to:

• translate a commercial transaction into a coherent contractual architecture;
• distinguish representations, warranties, covenants, conditions, indemnities, and remedies;
• draft provisions that are precise, internally consistent, and operationally workable;
• negotiate risk allocation using interests, alternatives, evidence, and objective thresholds;
• construct a cross-border legal-risk matrix and perform basic scenario analysis;
• design liability caps, exclusions, indemnities, audit rights, and compliance controls;
• evaluate boilerplate clauses in relation to governing law, forum, language, assignment, force majeure, and change control;
• use contract-lifecycle metrics to improve governance without treating metrics as substitutes for legal judgment; and
• recognize ethical, regulatory, technological, and enforcement limitations.

1. From Commercial Deal to Contract Architecture

A contract should be designed from the transaction outward. The drafter first identifies the commercial model, then the parties, assets, obligations, dependencies, risks, evidence, remedies, and exit routes. A useful architecture commonly contains:

The contract should use defined terms consistently. A defined term should have one meaning unless the context clearly requires otherwise. Capitalization, cross-references, schedules, and precedence rules should be checked systematically. A statement of work should not contradict the master agreement; if conflict is possible, the agreement should state which document prevails and for which subject matter.

Precision in drafting

Precision is not the same as excessive length. A precise clause identifies the actor, action, timing, standard, evidence, exception, and consequence. Compare:

• Weak: “The supplier will provide prompt support.”
• Stronger: “The Supplier shall acknowledge a Severity 1 incident within one hour after receipt of the Customer’s notice and shall provide continuous remediation updates at intervals not exceeding four hours until service restoration.”

The second clause is more operational because it identifies an obligation, trigger, deadline, classification, and reporting requirement. It may still require a definition of “Severity 1,” a communication channel, and a remedy for non-compliance.

Interpretation across legal systems

Common-law drafting often distinguishes representations, warranties, conditions, covenants, and indemnities with considerable remedial significance. Civil-law systems may treat good faith, contractual conformity, mandatory remedies, and statutory concepts differently. A clause valid in one jurisdiction may be ineffective, recharacterized, or subject to mandatory law in another. The drafter must therefore ask:

• Is the chosen governing law validly connected to the transaction?
• Are mandatory local laws applicable despite the choice of law?
• Will the selected forum recognize and enforce the judgment or award?
• Are liquidated damages, exclusion clauses, indemnities, or limitation periods restricted?
• Does the language of execution create interpretive uncertainty?

A choice-of-law clause is not a universal exemption from mandatory public law.

2. Core Assurance and Performance Provisions

Representations

A representation is a statement of existing or past fact made to induce the other party to contract. Examples include statements that a company is duly incorporated, owns specified intellectual property, has authority to sign, or is not subject to undisclosed insolvency proceedings. A false representation may support rescission, damages, or other remedies depending on applicable law and the contract’s wording.

Representations should be limited to matters material to the transaction and supported by due diligence. Overly broad representations create disputes about immaterial inaccuracies and may encourage opportunistic claims. A representation schedule can identify exceptions, but the schedule should be specific enough to provide meaningful disclosure.

Warranties

A warranty is a contractual assurance about a fact, condition, quality, or performance standard. Examples include conformity to specifications, absence of malicious code, compliance with documentation, and authority to grant a licence. Warranties are usually connected to contractual remedies, such as repair, replacement, re-performance, refund, or damages.

A warranty should specify its temporal scope. “The Services shall comply with the specifications” may apply only at acceptance, throughout performance, or during a stated warranty period. The contract should also address notice, inspection, cure, exclusions caused by misuse, and the relationship between warranty remedies and other remedies.

Covenants

A covenant is a promise to do or refrain from doing something. Positive covenants include maintaining insurance, preserving licences, meeting security standards, or providing reports. Negative covenants include not assigning without consent, not using confidential information outside the permitted purpose, and not subcontracting critical functions without approval.

Covenants are particularly important in continuing relationships because they regulate conduct after signing. They should be linked to realistic monitoring mechanisms. A covenant requiring compliance with “all applicable laws” is common but should be supplemented, where material, by specific obligations concerning anti-corruption, sanctions, export controls, labour, environmental protection, tax, competition, cybersecurity, and data protection.

Conditions and acceptance

A condition may make performance, payment, or a right to terminate dependent on the occurrence of a specified event. Acceptance clauses should define objective tests, inspection periods, deemed acceptance rules, rejection notices, and the effect of partial acceptance. Ambiguous acceptance provisions can create disputes over whether payment is due and whether a defect is material.

3. Indemnities and Liability Limits

Indemnities

An indemnity is a contractual allocation of responsibility for specified loss, often triggered by a defined event. Typical indemnities cover third-party intellectual-property claims, bodily injury, property damage, breach of confidentiality, regulatory fines where legally recoverable, tax liabilities, and data-security incidents.

A well-designed indemnity answers:

• What event triggers it?
• Which losses are covered?
• Are direct losses, third-party claims, defence costs, settlements, and investigation expenses included?
• Is there a duty to mitigate?
• Who controls the defence?
• Can the indemnifying party settle without consent?
• What cooperation and notice are required?
• Do exclusions or liability caps apply?

The distinction between first-party and third-party claims is important. A third-party defence procedure may require prompt notice, control of counsel, participation rights, and consent to settlement. These procedures should not allow a party to settle in a manner that admits liability, imposes non-monetary obligations, or prejudices the indemnified party without consent.

Liability caps and exclusions

A liability clause generally combines a monetary cap with exclusions of particular categories of loss. The cap may be expressed as a fixed amount, a multiple of fees, fees paid during a look-back period, or a negotiated percentage of contract value. The chosen measure should reflect the economic exposure and the availability of insurance.

Common exclusions include indirect, consequential, special, exemplary, or punitive damages and loss of profit, revenue, or goodwill. Such terms are not uniformly interpreted across jurisdictions. A party may recover a type of loss described as “indirect” if it is legally classified as direct in the relevant circumstances. Drafting should therefore identify the intended exclusions by category and, where appropriate, use a separate schedule of excluded heads of loss.

Caps often contain carve-outs for fraud, wilful misconduct, death or personal injury caused by negligence, confidentiality, intellectual-property infringement, data incidents, payment obligations, or indemnities. Carve-outs should be deliberate. If every significant obligation is uncapped, the cap may have little practical value.

A useful negotiation structure is a tiered cap:

• a general cap for ordinary contractual liability;
• a higher super-cap for specified serious risks; and
• uncapped liability only where required by law or justified by exceptional misconduct.

The clause must also state whether aggregate liability includes indemnity payments, service credits, costs of cure, and amounts paid by insurers.

4. Due Diligence and Contractual Evidence

Due diligence is the process of testing the facts, capabilities, legal status, compliance record, financial condition, ownership, and operational resilience relevant to the transaction. It is not merely a pre-signing checklist. Its results should influence drafting, pricing, conditions precedent, representations, covenants, escrow, security, and termination rights.

A cross-border diligence program may examine:

• corporate authority, ownership, and beneficial ownership;
• licences, registrations, permits, and sector approvals;
• sanctions, anti-bribery, export-control, and anti-money-laundering exposure;
• litigation, investigations, insolvency indicators, and regulatory history;
• intellectual-property ownership and third-party licences;
• cybersecurity controls, data flows, and incident history;
• supply-chain concentration and subcontracting;
• employment, environmental, tax, and human-rights risks; and
• financial statements, insurance, creditworthiness, and payment controls.

The evidential quality of diligence matters. A self-certification is not equivalent to an independently verified document. The contract can distinguish between information disclosed, information verified, and information that must be continuously monitored.

5. Negotiating the Agreement

Effective negotiation begins with preparation rather than positional exchange. The negotiating team should identify interests, must-have outcomes, acceptable alternatives, authority limits, and matters requiring technical or regulatory input. A risk allocation that appears legally attractive may be commercially unworkable if the counterparty cannot insure or operationalize it.

Interest-based negotiation

Positions are stated demands, such as “unlimited liability.” Interests explain why the demand exists, such as concern about catastrophic data loss, inability to quantify exposure, or internal governance requirements. Interests permit alternative solutions: a higher cap, insurance, escrow, security controls, audit rights, rapid notification, or a specific indemnity.

The parties should distinguish:

• must-have terms, essential to law, policy, or risk tolerance;
• tradeable terms, where concessions can be exchanged;
• information requests, needed to reduce uncertainty; and
• fallback mechanisms, used if a preferred solution is rejected.

Negotiation should also consider BATNA—the best alternative to a negotiated agreement. A party with no practical alternative may accept contractual risk that its policy would otherwise reject. That decision should be documented and approved, not hidden within drafting compromises.

Clause-level negotiation example

Suppose a technology supplier requests a cap equal to fees paid in the previous three months. The customer considers that inadequate because a security incident could affect regulated data. A structured response might combine:

1. a general cap equal to annual fees;
2. a super-cap equal to three times annual fees for security and confidentiality breaches;
3. specified security controls and independent testing;
4. mandatory incident notification within a defined period;
5. cyber insurance; and
6. a third-party claims indemnity for specified infringement risks.

This solution does not eliminate risk. It aligns the cap with exposure, prevention, detection, and financial recovery mechanisms.

6. Legal Risk Analytics

Legal risk analytics supports judgment by making assumptions visible. It should not convert uncertain legal questions into false precision. A practical risk matrix records the risk, cause, event, consequence, existing controls, owner, likelihood, impact, response, and review date.

Risk scoring

A simple qualitative-to-quantitative model is:

Here, R_i is the score for risk i, L_i is its likelihood score, and I_i is its impact score. The model assumes that both dimensions are placed on a defined ordinal scale, such as 1 to 5. Because ordinal scores are not necessarily cardinal measurements, the product is a prioritization aid, not a probability-based estimate of loss.

A more financially oriented expected-loss model is:

where EL is expected loss, p_j is the estimated probability of scenario j, and C_j is the monetary consequence of that scenario. The model assumes that scenarios are defined consistently and that probabilities and consequences are not double-counted. It is useful for comparing controls, insurance, reserves, or contract prices, but it can be misleading when probabilities are highly uncertain or consequences are non-monetary.

Scenario analysis

Scenario analysis examines plausible states rather than relying on a single forecast. For a cross-border supply agreement, scenarios might include ordinary performance, a two-month delay, sanctions affecting a subcontractor, a data breach, currency controls, insolvency, and a force-majeure event. Each scenario should specify:

• trigger;
• contractual rights and duties;
• operational consequence;
• financial consequence;
• regulatory consequence;
• available evidence;
• decision owner; and
• recovery or exit path.

The analysis should test interactions. A sanctions event may trigger suspension, termination, payment restrictions, reporting duties, and reputational harm simultaneously. A force-majeure clause may excuse delay but not necessarily payment, confidentiality, data protection, or mitigation obligations.

Contract-lifecycle metrics

Metrics help organizations identify where contracts create delay, leakage, or unmanaged exposure. Examples include:

• cycle time from request to signature;
• percentage of contracts using approved templates;
• deviation rate from standard clauses;
• time from breach notice to response;
• percentage of obligations with an assigned owner;
• renewal or termination dates captured in a system;
• audit findings closed within the required period;
• claims frequency and average resolution time; and
• realized revenue or savings compared with contractual entitlement.

A metric must have a clear definition, data source, owner, frequency, and decision use. For example, “template adoption” should state whether it measures contracts initiated from a template or contracts signed without material deviation. High speed is not success if it results from inadequate review. Metrics should therefore be balanced across efficiency, quality, compliance, and outcomes.

7. Audit, Compliance, and Governance Clauses

Audit rights

Audit rights provide evidence that contractual obligations are being met. A clause should specify scope, notice, frequency, auditor qualifications, business-hour restrictions, confidentiality, cost allocation, access to systems and records, remediation deadlines, and treatment of privileged material and third-party confidential information.

Unlimited audits may be commercially disruptive and legally problematic. A proportionate approach may permit routine audits on reasonable notice, additional audits after a credible incident, and immediate access where delay would materially increase risk. The contract should distinguish documentary review, technical testing, site inspection, and certification by an independent assessor.

Compliance clauses

A general compliance representation is rarely sufficient for high-risk transactions. Effective clauses combine:

• compliance with applicable laws;
• prohibition of bribery, facilitation payments, and improper benefits;
• sanctions and export-control screening;
• books-and-records obligations;
• flow-down requirements for subcontractors;
• training and reporting;
• investigation and cooperation duties;
• suspension or termination rights; and
• audit and remediation procedures.

The phrase “applicable law” should be considered carefully. A party should not be required to comply with every law in the world, but the agreement should cover laws that apply to the parties, transaction, goods, services, personnel, data, territory, and payment flows.

Data, cybersecurity, and artificial intelligence

Where personal data or sensitive business information is processed, the contract should allocate roles, purposes, security measures, international transfers, breach notification, retention, deletion, subprocessing, assistance with data-subject rights, and audit. Cybersecurity obligations should be measurable where possible, but technical standards must be kept current through change-control procedures.

Artificial-intelligence tools can assist with clause comparison, obligation extraction, anomaly detection, and renewal monitoring. They may also reproduce errors, overlook jurisdiction-specific meaning, expose confidential information, or generate unsupported legal conclusions. Human review, access controls, audit logs, approved tools, and validation against authoritative sources remain necessary. An AI-generated contract is a draft requiring professional judgment, not a legal opinion.

8. Boilerplate with Substantive Consequences

Boilerplate is often treated as secondary, yet it can determine whether the agreement works in practice.

• Entire agreement limits reliance on prior statements, subject to fraud and mandatory law.
• Amendment clauses should require authorized written changes and address electronic signatures.
• Assignment clauses should distinguish corporate reorganizations, changes of control, and transfers to affiliates.
• Subcontracting clauses should preserve responsibility and impose flow-down duties.
• Confidentiality clauses should address permitted disclosures, compelled disclosure, duration, and return or destruction.
• Force majeure clauses should define covered events, causation, notice, mitigation, duration, and termination. Economic hardship is not automatically force majeure.
• Change in law clauses should allocate compliance costs and permit renegotiation or termination where appropriate.
• Notices clauses should identify addresses, electronic methods, receipt rules, and authorized recipients.
• Severability clauses should support replacement of invalid provisions without rewriting the commercial bargain.
• Waiver clauses should prevent a single failure to enforce from unintentionally changing rights.
• Counterparts and electronic execution clauses should reflect applicable signature and evidence rules.
• Dispute resolution clauses should coordinate negotiation, mediation, arbitration or litigation, emergency relief, seat, institution, language, number of arbitrators, and enforcement.
• Survival clauses should identify obligations that continue after expiry or termination.

The dispute clause deserves particular attention. The seat of arbitration determines the procedural law and court supervision; the hearing location may be different. Governing law and dispute forum are related but distinct choices.

9. Illustrative Case: Meridian Components and NordTek Systems

The following is a fictional illustrative case.

Background

Meridian Components, a manufacturer based in Canada, agrees to supply precision components to NordTek Systems, a Swedish industrial-equipment producer. Components will be manufactured in Canada, tested by a subcontractor in Poland, and delivered to facilities in Germany and Mexico. The contract includes forecasts, firm purchase orders, technical specifications, confidentiality obligations, and a three-year term.

Problem

NordTek wants an unlimited supplier indemnity for product defects, late delivery, intellectual-property claims, sanctions violations, and data incidents. Meridian proposes a cap equal to fees paid in the preceding six months and a force-majeure clause covering supply shortages and transport disruption. NordTek also requests audit rights over Meridian and its subcontractors. The parties must address German and Mexican delivery sites, European data requirements, export controls, and the risk that the Polish tester uses an unapproved subcontractor.

Analysis

The parties first map the risk by controllability and severity. Product conformity is largely controllable by Meridian and can be addressed through specifications, testing, acceptance, warranty, and recall procedures. Transport disruption is partly external and may justify a carefully drafted excuse mechanism. Intellectual-property infringement may require an indemnity, but the customer’s modifications and combinations should be excluded. Sanctions exposure requires continuous screening rather than a one-time representation. Data risk is material if production or employee information is transferred through the supplier’s systems.

The proposed six-month cap is poorly aligned with a three-year relationship and could leave the customer under-protected after a major incident. Unlimited liability for every breach, however, may be uninsurable and commercially disproportionate.

Approach and solution

The negotiated structure contains:

1. a general cap equal to fees paid or payable in the previous twelve months;
2. a super-cap equal to three times that amount for confidentiality, cybersecurity, and specified IP indemnities;
3. uncapped liability only for fraud, wilful misconduct, death or personal injury where legally applicable, and amounts that cannot lawfully be limited;
4. product conformity warranties tied to measurable specifications and a twelve-month warranty period;
5. a recall and replacement procedure, with cost allocation based on causation;
6. an IP indemnity excluding claims caused by NordTek specifications, modifications, or combinations not supplied by Meridian;
7. sanctions screening, books-and-records duties, subcontractor flow-down, and immediate notification of an investigation;
8. audit rights once annually, plus event-driven audits after credible evidence of material non-compliance;
9. a force-majeure clause covering specified external events but requiring notice, mitigation, allocation of scarce capacity, and termination after a defined prolonged period; and
10. arbitration seated in a mutually acceptable neutral jurisdiction, with governing law separately stated and mandatory local law preserved.

The parties also add a contract-management schedule identifying owners, reporting dates, test evidence, insurance certificates, renewal alerts, and remediation deadlines.

Outcome

The final agreement does not remove uncertainty, but it makes uncertainty governable. Meridian receives a predictable general exposure and can price insurance and controls. NordTek receives enhanced protection for high-severity risks, evidence rights, operational remedies, and a credible exit path. The arrangement also reduces the danger that a subcontractor’s conduct will fall outside the contract’s compliance framework.

Learning points

The case demonstrates that effective drafting connects legal language to operational controls. A liability cap should be negotiated with insurance, prevention, detection, and remedy. Compliance duties should flow through the supply chain. Audit rights should be proportionate and linked to evidence. Finally, a contract is only as effective as the organization’s ability to monitor and enforce it.

10. Limitations, Ethics, and Best Practices

Risk matrices can conceal disagreement behind numbers. Expected-loss calculations may understate low-probability catastrophic events, while qualitative scoring may give a false appearance of objectivity. Legal teams should record assumptions, confidence levels, unknowns, and dissenting views.

Ethical practice requires truthful disclosure, respect for confidentiality and privilege, avoidance of coercive or discriminatory terms, and attention to affected third parties. International contracting may implicate modern-slavery prevention, environmental responsibility, indigenous rights, labour standards, and human-rights due diligence. A clause should not be used to transfer all responsibility to a weaker counterparty while the economically stronger party controls the relevant conduct.

Best practice includes:

• begin with a transaction map and risk allocation plan;
• use plain, consistent language and controlled definitions;
• align representations with verified facts;
• distinguish prevention, detection, remedy, and compensation;
• make obligations measurable and assign internal owners;
• negotiate caps and indemnities with insurance and operational capability in mind;
• test the contract against adverse scenarios before signature;
• integrate subcontractors and affiliated entities appropriately;
• preserve evidence through records, notices, approvals, and audit trails;
• review mandatory local law and enforceability in relevant jurisdictions; and
• monitor the contract throughout its lifecycle rather than treating signature as completion.

Chapter Summary

Cross-border contract drafting is a form of legal and commercial risk design. A sound agreement begins with the transaction’s scope, dependencies, evidence, and failure modes. Representations address relied-upon facts; warranties establish contractual standards; covenants govern continuing conduct; conditions control rights and obligations through specified events; indemnities allocate defined losses; and liability provisions establish the financial boundaries of responsibility.

Negotiation is strongest when parties explore interests, alternatives, evidence, insurance, and operational controls rather than exchanging unsupported positions. Due diligence should inform representations, covenants, conditions, security, pricing, and termination. Legal risk analytics can organize uncertainty through risk matrices, scenario analysis, expected-loss models, and lifecycle metrics, but quantitative outputs remain dependent on assumptions and cannot replace legal judgment.

Audit, compliance, data, cybersecurity, subcontracting, and boilerplate provisions often determine whether the agreement functions after signature. Effective governance assigns owners, monitors obligations, preserves evidence, and responds to changing law and technology. The central professional task is to create a contract that is clear enough to operate, flexible enough to survive change, and disciplined enough to allocate severe risks fairly and enforceably.

Key Terms

Representation: A statement of existing or past fact made to induce contracting.

Warranty: A contractual assurance concerning fact, quality, condition, or performance.

Covenant: A promise to do or refrain from doing something.

Condition: An event on which a contractual right or obligation depends.

Indemnity: A contractual allocation of specified losses or claims.

Liability cap: A maximum monetary amount recoverable under defined circumstances.

Carve-out: An exception from a limitation, exclusion, or general rule.

Force majeure: A contractual mechanism addressing specified extraordinary events affecting performance.

Due diligence: Investigation of facts, risks, capabilities, and compliance before or during a transaction.

Audit right: A contractual right to inspect records, systems, sites, or controls.

Compliance clause: A provision requiring adherence to specified laws, standards, and procedures.

Boilerplate: Standard contractual language with potentially substantive legal consequences.

Governing law: The legal system selected to interpret the contract.

Seat of arbitration: The jurisdiction whose procedural law governs an arbitration.

Scenario analysis: Evaluation of contractual consequences under defined possible events.

Risk matrix: A structured tool for recording and prioritizing risks by likelihood and impact.

Expected loss: Probability-weighted estimate of monetary consequences across scenarios.

Super-cap: A higher liability limit applying to specified serious risks.

Contract lifecycle management: Governance of a contract from request and drafting through performance, renewal, and termination.

Flow-down obligation: A duty requiring subcontractors or lower-tier parties to comply with specified contract requirements.

Review Questions

5 Short Answer Questions

1. What is the principal difference between a representation and a covenant?
2. Identify three matters that should be addressed in an indemnity procedure.
3. Why may a general exclusion of consequential loss be insufficient by itself?
4. What variables are used in the basic risk-score model R_i = L_i × I_i?
5. Why should audit rights be proportionate to the risk and purpose of the contract?

5 Long Answer Questions

1. Explain how representations, warranties, covenants, conditions, and indemnities perform different functions in a cross-border agreement.
2. Discuss how a liability cap should be designed with insurance, operational controls, indemnities, and serious-misconduct carve-outs.
3. Analyze the legal and commercial significance of governing law, arbitration seat, forum, language, and enforcement considerations.
4. Explain how due-diligence findings should affect contract drafting, negotiation, pricing, and post-signature monitoring.
5. Evaluate the benefits and limitations of contract-lifecycle metrics in a multinational organization.

3 Analytical / Application Questions

1. A supplier requests a cap equal to three months of fees in a five-year agreement involving sensitive personal data. Construct a negotiation proposal using a general cap, possible super-cap, compliance controls, audit rights, insurance, and incident remedies. Justify each element.
2. Build a risk matrix for a cross-border supply contract containing risks of delay, sanctions exposure, defective goods, IP infringement, insolvency, and data breach. For each risk, identify likelihood, impact, controls, owner, and contractual response.
3. A force-majeure event delays delivery for four months, while a subcontractor is under sanctions investigation. Analyze the parties’ likely contractual issues, including notice, mitigation, suspension, payment, audit, termination, and compliance obligations.

Multiple Choice Questions with Answers

Question 1

Which provision primarily governs continuing conduct after a contract is signed?

A. Covenant

B. Representation

C. Entire-agreement clause

D. Definition clause

Correct Answer: A. Covenant

Question 2

What is the principal function of an indemnity?

A. To define the governing law

B. To allocate specified losses or claims

C. To establish the contract price

D. To appoint an arbitrator

Correct Answer: B. To allocate specified losses or claims

Question 3

Under the chapter’s basic risk-score model, a likelihood score of 4 and impact score of 5 produce what score?

A. 9

B. 15

C. 20

D. 25

Correct Answer: C. 20

Question 4

Which item is most directly associated with a third-party indemnity procedure?

A. Control of the defence

B. Choice of currency only

C. Automatic renewal

D. Definition of affiliates only

Correct Answer: A. Control of the defence

Question 5

Why is a liability super-cap used?

A. To eliminate all contractual remedies

B. To impose a higher limit for specified serious risks

C. To replace governing law

D. To prevent any audit

Correct Answer: B. To impose a higher limit for specified serious risks

Question 6

What does the seat of arbitration primarily determine?

A. The contract price

B. The procedural law and court supervision of the arbitration

C. The supplier’s insurance premium

D. The technical specification

Correct Answer: B. The procedural law and court supervision of the arbitration

Question 7

Which metric best concerns contract standardization?

A. Deviation rate from approved clauses

B. Number of office locations

C. Average employee age

D. Annual electricity consumption

Correct Answer: A. Deviation rate from approved clauses

Question 8

What is a key limitation of a risk matrix using ordinal scores?

A. It always produces a legally enforceable remedy

B. Ordinal numbers may not represent precise monetary probabilities

C. It cannot record risk owners

D. It automatically proves causation

Correct Answer: B. Ordinal numbers may not represent precise monetary probabilities

Question 9

Which approach best addresses sanctions risk in a continuing relationship?

A. A one-time pre-signature statement only

B. Continuous screening, reporting, and flow-down duties

C. Removal of all audit rights

D. An automatic waiver of compliance

Correct Answer: B. Continuous screening, reporting, and flow-down duties

Question 10

Which clause typically addresses events that excuse specified performance failures?

A. Force-majeure clause

B. Entire-agreement clause

C. Counterparts clause

D. Notices clause

Correct Answer: A. Force-majeure clause