Contract Law and Regulatory EnvironmentIntroduction and ContextProject procurement converts organizational requirements into legally enforceable relationships with suppliers, consultants, contractors, technology providers, and logistics partners. A procurement contract is therefore more than a commercial document: it allocates risk, defines authority, establishes performance standards, creates evidence for payment and acceptance, and provides mechanisms for managing failure. Contract law is primarily national and jurisdictional. The governing rules may arise from legislation, judicial precedent, commercial codes, administrative regulations, treaty obligations, and sector-specific rules. Consequently, this chapter presents transferable principles rather than legal advice for a particular country. A project manager should identify the governing law, obtain qualified legal advice where required, and never assume that a clause is enforceable merely because it appears in a signed document. The regulatory environment is equally important. Competition law, public procurement rules, sanctions, export controls, anti-bribery requirements, privacy legislation, tax rules, and dispute-resolution provisions may affect a transaction before, during, and after contract award. Learning ObjectivesBy the end of this chapter, the learner should be able to: - explain formation, authority, consideration, representations, warranties, privity, and enforceability;
- distinguish contractual conditions, warranties, covenants, and representations;
- analyze breach, damages, specific performance, suspension, and termination;
- design procurement controls that address competition, integrity, sanctions, trade, and privacy;
- evaluate jurisdiction, governing law, dispute-resolution, and cross-border risks; and
- apply these principles to a complex project procurement scenario.
1. The Contract as a Project Governance InstrumentA contract is an agreement recognized and enforced by law. In project management, it is also a governance system. It defines who must do what, by when, to what standard, for what price, and with what consequences if assumptions fail. Effective contracts align four elements: - Scope: deliverables, exclusions, interfaces, specifications, and acceptance criteria.
- Commercial allocation: price, payment, currency, taxes, incentives, escalation, and financial security.
- Risk allocation: responsibility for design, site conditions, delay, change, intellectual property, data, and third-party claims.
- Control and remedy: reporting, audit, approvals, change control, dispute escalation, suspension, termination, and post-termination obligations.
A contract should be read as an integrated system. A broad indemnity may be undermined by a liability cap; a milestone payment may be difficult to enforce if acceptance criteria are vague; and a termination right may be commercially useless if transition assistance and access to work product are absent. Important terminology- Contracting party: a person or organization legally bound by the agreement.
- Offer: a sufficiently definite proposal intended to become binding upon acceptance.
- Acceptance: assent to the offer, in the manner authorized or reasonably indicated.
- Consideration: the legally recognized exchange supporting a promise in many common-law systems.
- Condition: a term whose failure may justify termination or substantial contractual remedies.
- Warranty: a contractual promise whose breach generally gives rise to damages, subject to applicable law.
- Covenant: a promise to perform or refrain from performing an act.
- Representation: a statement of existing or past fact that induces entry into a contract.
- Warranty statement: a contractual assurance about a fact or future performance.
- Privity: the principle that contractual rights and duties generally attach to the parties, subject to exceptions.
- Material breach: a breach sufficiently serious to justify significant remedies, often including termination.
- Force majeure: an agreed event or category of events that may excuse or suspend performance when specified conditions are met.
2. Formation and Enforceability2.1 Offer, acceptance, and agreementFormation normally requires an agreement, intention to create legal relations, consideration or another basis for enforceability, capacity, legality, and sufficient certainty. Civil-law systems may formulate these requirements differently, and some transactions are governed by special statutory formalities. An invitation to tender is not always an offer. It may be an invitation for suppliers to submit offers, which the buyer may accept or reject. The procurement documents should state whether a bid becomes binding upon submission, how long it remains open, whether the buyer may negotiate, and when a contract comes into existence. Acceptance must correspond to the offer. A purported acceptance that materially changes price, scope, liability, or delivery may be a counteroffer rather than acceptance. Battle-of-forms disputes arise when purchase orders, quotations, framework terms, and acknowledgements contain conflicting standard conditions. A robust procurement process specifies the order of precedence and rejects conflicting terms expressly. Electronic contracting is generally enforceable where applicable law recognizes electronic records and signatures. However, the organization must preserve evidence of identity, authority, version control, consent, timestamps, and integrity of the signed record. 2.2 Intention, capacity, and authorityOrganizations act through people. A project manager may administer a contract without possessing authority to amend price, waive a claim, or bind the organization to a new scope. Authority can be: - Actual, expressly or impliedly granted by the organization;
- Apparent, arising where the organization represents that an individual has authority and a counterparty reasonably relies on that representation; or
- Ratified, where the organization later adopts an unauthorized act.
Authority matrices should define who may approve requisitions, issue purchase orders, sign contracts, approve changes, settle disputes, and authorize termination. Segregation of duties reduces fraud and error: the person who specifies a requirement should not alone select the supplier, approve receipt, and authorize payment. A contract may be challenged where a signatory lacked capacity or the organization exceeded a statutory mandate. Public bodies often have additional approval, budget, transparency, and delegation requirements. Internal approval may not cure a legal defect, but failure to follow internal controls can create disciplinary, audit, or governance consequences. 2.3 Consideration and exchangeIn common-law systems, consideration is generally something of legal value exchanged for a promise. Payment for deliverables is consideration for the supplier's performance; the supplier's undertaking to deliver is consideration for the buyer's payment promise. A promise to perform an existing duty may create difficulty unless the contract, commercial benefit, or applicable law recognizes the variation. Contract variations should therefore identify the new obligation, price adjustment, schedule effect, and approval. A change order that merely records an already existing duty may not support a new payment claim, depending on governing law. Civil-law systems may instead emphasize consent, cause, good faith, or statutory requirements. 2.4 Certainty, legality, and formalitiesThe contract should be sufficiently certain to determine obligations. Essential uncertainty may concern scope, price, duration, acceptance, or the method for resolving future decisions. Mechanisms such as objectively measurable indices, expert determination, agreed rates, and documented assumptions can preserve certainty while allowing flexibility. The purpose must be lawful. Contracts involving bribery, money laundering, unlawful restraint of competition, prohibited exports, or sanctioned parties may be unenforceable and may expose individuals and organizations to criminal, civil, administrative, or reputational consequences. Some contracts must be written, witnessed, notarized, registered, or executed in a prescribed form. The project team should identify these requirements before award rather than treating them as administrative details. 3. Representations, Warranties, Conditions, and RelianceThese concepts allocate different kinds of risk and remedies. | Concept | Typical meaning | Typical consequence of breach |
|---|
| Representation | Statement of existing or past fact inducing the contract | Damages or rescission, depending on law and seriousness | | Warranty | Contractual assurance about fact or performance | Damages, often subject to contractual limits | | Condition | Fundamental term or event affecting the contract | Termination and/or damages if the legal test is met | | Covenant | Promise to act or refrain from acting | Damages, injunction, or other agreed remedy | | Condition precedent | Event that must occur before a duty arises | Duty may not mature until the event occurs |
Labels are not conclusive. Courts examine wording, context, commercial purpose, and applicable law. A statement in a tender about production capacity may be a representation before award and a warranty after incorporation into the contract. The contract should identify which information has been verified, which assumptions are accepted, and which statements survive signing. Project managers should distinguish performance specifications from results warranties. A performance specification requires a method or process; a results warranty promises an outcome. Results warranties can improve accountability but may transfer risks that the supplier cannot control. Acceptance tests should define test conditions, tolerances, retesting, correction periods, and the consequences of failure. Reliance is central to misrepresentation analysis. A buyer that relies on an inaccurate statement may claim remedies, but deliberate concealment, negligent verification, contractual disclaimers, and statutory consumer or procurement protections can affect the outcome. A non-reliance clause should not be assumed to protect fraudulent or legally prohibited conduct. 4. Privity, Third Parties, and Contract ArchitectureThe privity principle generally means that a person who is not a party cannot enforce a contract and is not ordinarily liable under it. Projects nevertheless involve beneficiaries, lenders, end users, subcontractors, designers, operators, and affiliates. The contract can address this through: - express third-party beneficiary rights;
- assignment and novation;
- collateral warranties or direct agreements;
- step-in rights for lenders or owners;
- flow-down obligations to subcontractors; and
- agency, trust, insurance, or statutory mechanisms where recognized.
Flow-down clauses should be specific. Requiring a subcontractor to comply with “all obligations” may create uncertainty if the prime contract contains obligations irrelevant to the subcontracted work. The prime contractor should remain responsible for subcontractor performance unless the contract clearly and lawfully provides otherwise. Assignment transfers rights; novation generally substitutes a new party and transfers rights and obligations. Neither should be inferred casually. Consent requirements, creditworthiness, data protection, sanctions screening, and continuing liabilities should be reviewed before approval. 5. Interpreting and Administering Contract TermsInterpretation seeks the parties' objective contractual meaning, using the text, context, commercial purpose, course of dealing, and applicable interpretive rules. The project team should maintain a controlled contract baseline containing the signed agreement, schedules, clarifications, addenda, change orders, notices, and approved correspondence. Useful drafting and administration controls include: - a clear order-of-precedence clause;
- defined terms used consistently;
- measurable acceptance criteria;
- a responsibility assignment matrix;
- notice addresses and permitted communication channels;
- deadlines expressed with time zones and business-day definitions;
- a documented change-control procedure; and
- a contract register for notices, claims, securities, insurance, milestones, and expiry dates.
A notice clause may require specified content, method, and timing. Failure to comply can affect entitlement, although some jurisdictions limit the enforceability of harsh notice bars. Contract administrators should issue notices promptly, preserve evidence, and avoid informal statements that unintentionally waive rights or vary the contract. 6. Breach and RemediesA breach occurs when a party fails to perform a contractual obligation, performs defectively, or repudiates a future obligation. The legal response depends on the term breached, causation, foreseeability, mitigation, proof of loss, and agreed limitations. 6.1 DamagesCompensatory damages generally aim to place the innocent party in the position it would have occupied had the contract been properly performed, subject to legal limits. Common categories include expectation loss, reliance loss, and, in limited circumstances, restitutionary recovery. Damages are usually constrained by causation, remoteness or foreseeability, mitigation, and proof. A simple direct-loss model is: Recoverable loss = Proven loss caused by breach − Avoided loss − Loss that reasonable mitigation would have avoided This is a conceptual model, not a universal legal formula. The variables are monetary amounts measured in the contract currency. It assumes the governing law recognizes the relevant loss, the claimant proves causation and amount, and no valid exclusion, cap, liquidated-damages clause, or contributory-fault rule changes the result. For delay, a contract may provide liquidated damages. A valid clause normally represents a reasonable pre-estimate or commercially justifiable allocation of anticipated loss, while a penalty may be restricted or unenforceable in some jurisdictions. The clause should define the triggering event, daily or periodic rate, cap, relationship to extensions of time, and whether it is the exclusive remedy. 6.2 Equitable and contractual remedies- Specific performance requires performance rather than money and is more likely where damages are inadequate and supervision is practical.
- Injunction restrains or requires conduct, subject to legal tests and equitable discretion.
- Rescission unwinds a contract in circumstances such as serious misrepresentation, subject to bars and restitution issues.
- Repair, replacement, re-performance, or price reduction are common commercial remedies.
- Set-off permits one amount to be deducted from another only where contract or law permits it.
- Indemnity allocates responsibility for specified losses, often including third-party claims, subject to wording and controls.
An exclusion or limitation-of-liability clause should be read with carve-outs for fraud, wilful misconduct, confidentiality, intellectual property infringement, personal injury, data breaches, or unpaid amounts where appropriate. Enforceability depends on law, bargaining power, clarity, mandatory statutes, and public policy. 6.3 Mitigation and evidenceThe injured party must generally take reasonable steps to reduce loss. Mitigation does not require accepting unreasonable alternatives or compromising legitimate rights. Evidence includes baseline schedules, approved drawings, inspection records, correspondence, cost ledgers, test results, photographs, meeting minutes, and contemporaneous notices. Good contract administration is therefore a legal-risk control, not merely clerical work. 7. Suspension, Force Majeure, and TerminationSuspension temporarily stops some or all performance. The contract should state who may suspend, required notice, protection of work, payment for demobilization and remobilization, security obligations, and the maximum suspension period. Force majeure is not a universal automatic excuse. It operates only according to its wording and applicable law. A well-designed clause addresses qualifying events, causation, foreseeability, control, notice, mitigation, alternative performance, payment, partial performance, and termination after prolonged impact. It should distinguish force majeure from ordinary price increases, poor planning, supplier insolvency, and foreseeable shortages unless the parties deliberately allocate those risks. Termination may be: - For cause, following material breach, insolvency, corruption, persistent delay, or failure to remedy;
- For convenience, where permitted, usually with payment for completed work, committed costs, and agreed termination charges; or
- By mutual agreement, through a documented settlement or termination agreement.
A termination procedure should specify notice, cure period, takeover, access to premises and data, transfer of materials, treatment of intellectual property, final account, employee and subcontractor issues, confidentiality, records retention, and survival of relevant clauses. Wrongful termination can itself be a repudiatory breach, exposing the terminating party to damages. 8. Competition, Public Procurement, and IntegrityCompetition rules seek to prevent agreements or conduct that distort markets. Procurement risks include bid-rigging, market allocation, price-fixing, abuse of dominance, collusion through information exchange, and discriminatory specifications. Warning signs include identical unusual errors in bids, rotating winners, unexplained subcontracting between competitors, suspiciously predictable pricing, and suppliers dividing customers or territories. Controls include market research, proportionate specifications, transparent evaluation criteria, independent bid review, conflict-of-interest declarations, secure tender handling, records of clarifications, and escalation of suspected collusion. A project manager should not share one bidder's confidential pricing or technical solution with another bidder. Public procurement adds obligations such as equal treatment, transparency, proportionality, non-discrimination, value for money, auditability, budget authority, and remedies for disappointed bidders. Procurement thresholds may determine whether open competition, framework procedures, or formal publication is required. Emergency procurement may be permitted but normally requires documented justification, duration limits, and post-award review. Anti-bribery rules may apply to conduct outside the organization's home country. Due diligence should cover ownership, beneficial owners, agents, intermediaries, politically exposed persons where relevant, gifts and hospitality, commissions, charitable contributions, and unusual payment instructions. “Commercial urgency” is not a justification for bypassing integrity controls. 9. Sanctions, Trade, Tax, and Cross-Border TransactionsSanctions may prohibit transactions with designated persons, entities, sectors, territories, vessels, banks, or technologies. Export controls may regulate military items, dual-use goods, software, technical data, and services. Screening should occur at onboarding, tender, award, payment, shipment, subcontracting, and material change. Screening is not enough: ownership, control, end use, destination, routing, and beneficial parties may also matter. Contracts should address compliance representations, licensing responsibility, information duties, suspension, termination, audit, and allocation of blocked funds. A broad “comply with all laws” clause is not a substitute for an operational compliance plan. Cross-border contracts also raise tax, customs, currency, withholding, import documentation, local-content, employment, and foreign-exchange issues. The contract should identify the importer of record, tariff responsibility, tax gross-up rules, delivery terms, currency risks, and the consequences of regulatory delay. 10. Privacy, Cybersecurity, and Intellectual PropertyProject procurement often involves personal data in employee records, access badges, customer information, video systems, health and safety records, and supplier due diligence. Privacy law may impose requirements for lawful processing, purpose limitation, data minimization, retention, security, individual rights, cross-border transfers, breach notification, and processor oversight. A data-processing schedule should define the data, purposes, roles, security measures, approved subprocessors, access controls, incident notification, audit rights, deletion or return, and assistance with data-subject requests. The parties should avoid collecting personal data merely because technology makes it possible. Cybersecurity clauses should be proportionate to the risk. They may require vulnerability management, encryption, multifactor authentication, secure development, penetration testing, business continuity, incident response, and evidence of compliance. Audit rights must be practical and protect the supplier's confidential information. Intellectual-property provisions should distinguish pre-existing materials, project-created deliverables, open-source components, licences, moral rights where relevant, escrow, and rights needed for operation, maintenance, modification, and future procurement. Ownership alone may not provide the operational rights a project needs. 11. Governing Law, Jurisdiction, and Dispute ResolutionGoverning law identifies the legal system used to interpret the contract. Jurisdiction identifies the courts or tribunal authorized to hear disputes. These are related but not identical. A contract may choose one governing law and a different forum, although enforceability and convenience must be considered. A dispute clause may require negotiation, senior-executive escalation, mediation, adjudication, arbitration, or litigation. Arbitration can provide confidentiality, specialist decision-makers, and cross-border enforcement advantages, but it involves fees and limited appeal. Court litigation may provide stronger procedural powers or joinder of necessary parties. Multi-tier clauses should state whether preconditions are mandatory, how deadlines operate, and what urgent relief remains available. The project team should assess: - enforceability of the chosen law and forum;
- recognition and enforcement of judgments or awards;
- language, seat, governing procedural rules, and number of decision-makers;
- interim relief and security for costs;
- sovereign or governmental immunity;
- insolvency and third-party participation; and
- limitation periods and survival of claims.
12. Technology and AI in Contract AdministrationContract-lifecycle-management systems can automate obligation registers, approval routing, expiry alerts, version control, and clause comparison. AI tools can identify inconsistent definitions, missing dates, unusual liability terms, or deviations from playbooks. They should support—not replace—legal judgment and accountable approval. Controls are essential: use approved systems, restrict confidential data, verify extracted obligations against the source, record human review, test for hallucinated or omitted terms, and preserve an audit trail. AI-generated advice may be inaccurate, may expose confidential information, or may reproduce bias. Responsibility remains with the organization and authorized decision-makers. Applied Case: Illustrative Cross-Border Renewable-Energy ProcurementBackgroundA public energy agency awards a contract to design, supply, and commission a battery-storage facility. The supplier is incorporated abroad and proposes to use two subcontractors. The contract includes milestone payments, a performance guarantee, liquidated damages for delay, a sanctions clause, a data-processing schedule, and arbitration in a neutral seat. ProblemDuring construction, an export-control restriction delays critical battery modules. The supplier requests a six-month extension and additional payment. At the same time, the agency discovers that the supplier's regional sales director signed a change order increasing the contract price, although the agency's delegation policy reserved such approval for the procurement board. The supplier also stored employee identification data in an unapproved cloud service. AnalysisThe project team should first identify the governing law and the contractual force-majeure and export-control provisions. The export restriction may qualify only if it is beyond the supplier's control, could not reasonably have been avoided, and caused the delay. The supplier must comply with notice and mitigation duties and demonstrate alternative sourcing efforts. Additional payment is not automatic; entitlement depends on the risk allocation and wording of the contract. The change order raises authority and apparent-authority issues. The agency should examine the signatory's communications, prior practice, approval matrix, and whether the supplier reasonably relied on an apparent representation. Internally, the unauthorized act may breach governance rules even if the agency is externally bound or later ratifies it. No payment should be made until legal and commercial review resolves the issue. The cloud-storage incident requires investigation under the data-processing schedule and applicable privacy law. The agency should preserve evidence, restrict access, assess notification duties, require remediation, and determine whether subcontractor and supplier controls were adequate. Approach and outcomeThe agency forms a cross-functional team comprising procurement, legal, engineering, cybersecurity, privacy, finance, and sanctions specialists. It issues a reservation-of-rights notice, verifies the export restriction, reviews the supplier's mitigation evidence, and commissions an independent schedule assessment. It rejects the price increase pending authority review, but negotiates a documented extension for the portion of delay demonstrably caused by the restriction. The supplier moves personal data to an approved environment, completes an incident assessment, and provides enhanced security evidence. The parties amend the contract through the authorized change process, preserving the agency's rights for unrelated delay. Learning pointsThe case demonstrates that contract administration is integrated governance. Force majeure, authority, data protection, trade compliance, schedule analysis, and change control cannot be managed in isolated departmental channels. Timely notices, reliable records, delegated authority, and specialist escalation protect both enforceability and project outcomes. Challenges, Limitations, and Best PracticesLegal outcomes are uncertain because jurisdictions differ, facts are contested, statutes change, and courts may interpret broad clauses narrowly. Standard templates can reduce drafting time but may embed unsuitable risk allocations. Excessive legal complexity can impede supplier participation and obscure operational duties. Conversely, vague “partnership” language may create expectations without enforceable mechanisms. Best practice is risk-proportionate contracting: - classify the procurement's legal, technical, financial, data, and geopolitical risks;
- select a contract model consistent with scope maturity and risk-bearing capacity;
- verify authority, supplier identity, beneficial ownership, insurance, licences, and conflicts;
- define deliverables, interfaces, acceptance, change, payment, and records;
- align remedies, liability caps, indemnities, securities, and insurance;
- screen sanctions, trade, privacy, and integrity risks throughout the lifecycle;
- maintain a live obligation, notice, and claims register;
- escalate deviations before commitment; and
- close out with final acceptance, releases where appropriate, records retention, data deletion or return, and lessons learned.
Chapter SummaryContract law supplies the principles by which procurement promises become enforceable obligations. Formation requires legally sufficient agreement, authority, capacity, legality, and applicable formalities. Consideration, representations, warranties, conditions, covenants, and privity affect the rights created and remedies available. Clear scope, acceptance criteria, change procedures, notices, and evidence are essential to administration. Breach analysis requires attention to causation, foreseeability, mitigation, agreed remedies, liability limits, and the distinction between damages, specific performance, injunction, indemnity, suspension, and termination. Force-majeure and termination rights operate according to their wording and governing law. Competition, public procurement, anti-bribery, sanctions, export controls, tax, privacy, cybersecurity, intellectual property, and cross-border enforcement create additional regulatory duties. Effective project managers combine legal literacy with disciplined governance, specialist advice, ethical judgment, and reliable records. Key TermsContract: Legally recognized agreement creating enforceable obligations. Offer: Definite proposal intended to become binding upon acceptance. Acceptance: Assent to an offer in an authorized or reasonable manner. Consideration: Legally recognized exchange supporting a promise in many common-law systems. Authority: Legal power of a person to bind an organization. Representation: Statement of existing or past fact inducing contracting. Warranty: Contractual assurance about a fact or performance. Condition: Fundamental term whose breach may justify termination. Covenant: Contractual promise to act or refrain from acting. Privity: General limitation of contractual rights and duties to the parties. Material breach: Serious failure that may justify substantial remedies. Force majeure: Contractually defined event potentially excusing or suspending performance. Liquidated damages: Agreed sum or method for loss arising from a specified breach. Indemnity: Promise to compensate specified losses, often including third-party claims. Novation: Substitution of a contracting party with transfer of obligations. Sanctions: Legal restrictions imposed on specified persons, activities, goods, or territories. Governing law: Legal system selected to interpret the contract. Jurisdiction: Court or tribunal authority to determine a dispute. Data processor: Party processing personal data on behalf of another party under applicable law. Review QuestionsShort Answer Questions- What are the principal elements normally considered in contract formation?
- Distinguish a representation from a warranty.
- Why should project organizations maintain an authority matrix?
- What is the purpose of an order-of-precedence clause?
- Identify three controls relevant to sanctions and export compliance.
Long Answer Questions- Explain how scope definition, acceptance criteria, change control, and evidence interact to reduce contractual disputes.
- Compare damages, specific performance, injunctions, indemnities, and liquidated damages as contractual remedies.
- Discuss the legal and managerial implications of privity in a project with several subcontractors and a lender.
- Analyze the main drafting and administration issues in a force-majeure and termination regime.
- Evaluate how public procurement principles and competition law shape supplier selection and contract award.
Analytical / Application Questions- A supplier misses a milestone, claims force majeure, and requests additional payment without giving the contractually required notice. Develop a structured analysis for the project manager, identifying evidence, legal questions, and possible responses.
- A project manager signs a price increase outside delegated authority, while the supplier claims it reasonably relied on prior informal approvals. Analyze actual authority, apparent authority, ratification, and governance consequences.
- A cross-border technology supplier transfers project data to an unapproved subcontractor in a sanctioned jurisdiction. Design an immediate response and a longer-term contract-administration plan addressing privacy, sanctions, cybersecurity, termination, and dispute resolution.
Multiple Choice Questions with AnswersQuestion 1Which statement best describes apparent authority? A. Authority expressly written in a delegation document B. Authority created only by a court judgment C. Authority reasonably inferred by a third party from the organization's representation or conduct D. Authority that automatically exists for every project manager Correct Answer: C. Authority reasonably inferred by a third party from the organization's representation or conduct Question 2A statement about an existing production facility that induces a buyer to contract is most likely a: A. Representation B. Condition precedent C. Liquidated-damages clause D. Novation Correct Answer: A. Representation Question 3What is the primary purpose of an order-of-precedence clause? A. To eliminate the need for acceptance criteria B. To determine which document controls if contract documents conflict C. To transfer all risk to the buyer D. To replace the governing-law clause Correct Answer: B. To determine which document controls if contract documents conflict Question 4Which remedy principally seeks to require actual performance rather than payment of damages? A. Specific performance B. Rescission C. Set-off D. Liquidated damages Correct Answer: A. Specific performance Question 5Which fact is most relevant when assessing whether liquidated damages may be unenforceable as a penalty? A. Whether the contract has a title page B. Whether the agreed amount is disproportionate to the anticipated or legitimate interest protected C. Whether the supplier used subcontractors D. Whether the buyer paid in the correct currency Correct Answer: B. Whether the agreed amount is disproportionate to the anticipated or legitimate interest protected Question 6Which procurement practice most directly supports competition and equal treatment? A. Sharing one bidder's price with another bidder B. Changing evaluation criteria after bids are opened C. Using transparent criteria disclosed before evaluation D. Selecting the incumbent without documenting justification Correct Answer: C. Using transparent criteria disclosed before evaluation Question 7What does privity generally mean? A. Only contracting parties generally obtain contractual rights and duties B. Every project stakeholder automatically becomes a contracting party C. A contract cannot contain third-party benefits D. Subcontractors are always immune from liability Correct Answer: A. Only contracting parties generally obtain contractual rights and duties Question 8Which item is most appropriate in a data-processing schedule? A. A guaranteed exchange rate B. Approved subprocessors and incident-notification duties C. A construction productivity formula D. A supplier's marketing strategy Correct Answer: B. Approved subprocessors and incident-notification duties Question 9What is a key distinction between governing law and jurisdiction? A. They always mean exactly the same thing B. Governing law identifies the applicable legal system, while jurisdiction identifies the forum hearing the dispute C. Jurisdiction determines the contract price, while governing law determines delivery D. Governing law applies only to public contracts Correct Answer: B. Governing law identifies the applicable legal system, while jurisdiction identifies the forum hearing the dispute Question 10Which action is most consistent with sound contract administration after discovering an unauthorized change order? A. Pay immediately because any signed paper is automatically binding B. Destroy informal communications to avoid confusion C. Review authority, reliance, ratification, and applicable contract procedures before deciding entitlement D. Terminate every supplier contract automatically Correct Answer: C. Review authority, reliance, ratification, and applicable contract procedures before deciding entitlement
|