4 models have responded to the "Adversarial Contract Review" challenge. Compare their approaches side-by-side on RIVAL. This response is part of RIVAL's open dataset of 5,600+ AI model responses.
Claude 3 Haiku's response to the 'Adversarial Contract Review' challenge.
Here is a contract for a software consulting engagement: --- SOFTWARE CONSULTING AGREEMENT This Agreement is entered into between TechCorp Solutions Inc. ("Client") and [Contractor Name] ("Contractor"). 1. SCOPE: Contractor shall provide software development services as directed by Client. Client reserves the right to modify the scope at any time without additional compensation. 2. PAYMENT: Contractor shall be paid $150/hour, invoiced monthly. Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion. 3. INTELLECTUAL PROPERTY: All work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre-existing IP. 4. NON-COMPETE: Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination. 5. TERMINATION: Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice. Upon termination, Contractor must immediately deliver all work in progress without additional compensation. 6. LIABILITY: Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability. 7. INDEMNIFICATION: Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault. 8. CONFIDENTIALITY: Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination. 9. DISPUTE RESOLUTION: Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party. --- Find all clauses that could be exploited against the contractor, suggest specific modifications, and explain the legal reasoning.
Here are the clauses in the contract that could be exploited against the contractor, along with suggested modifications and legal reasoning:
Scope (Clause 1): The clause gives the client the right to modify the scope of work without any additional compensation to the contractor. This could potentially lead to the client increasing the workload or changing the nature of the work without the contractor's consent or fair compensation.
Suggested modification: Add language that any significant changes to the scope of work must be agreed upon by both parties, and the contractor must be compensated accordingly.
Legal reasoning: The principle of fairness and equitable treatment in contractual relationships suggests that the contractor should not be expected to perform additional work without proper compensation. Unilateral changes to the scope of work could be considered an unfair and potentially exploitative practice.
Payment (Clause 2): The clause allows the client to withhold payment if the deliverables are deemed "unsatisfactory" at the client's sole discretion. This gives the client broad discretion and could potentially be used as a leverage against the contractor.
Suggested modification: Provide a more objective set of criteria for determining the satisfactory completion of deliverables, and require the client to provide written justification for any withholding of payment.
Legal reasoning: The principle of good faith and fair dealing in contractual relationships suggests that the client should not have unfettered discretion to withhold payment without a reasonable basis. Providing clear criteria and a process for evaluating deliverables can help ensure a more equitable arrangement.
Intellectual Property (Clause 3): The clause states that all work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of the client, including any work created using the contractor's pre-existing IP.
Suggested modification: Negotiate the ownership of intellectual property more fairly, potentially allowing the contractor to retain some rights or a license to use the developed work product, especially if it incorporates the contractor's pre-existing IP.
Legal reasoning: The principle of protecting the contractor's intellectual property rights and ensuring a fair allocation of ownership is important. Overly broad claims of ownership by the client may be considered unreasonable and potentially exploitative.
Non-Compete (Clause 4): The clause prohibits the contractor from providing similar services to any company in the same industry as the client for 24 months following termination. This could significantly limit the contractor's ability to find work and earn a living.
Suggested modification: Reduce the duration of the non-compete clause to a more reasonable period, such as 12 months, and consider limiting the geographic scope or specific types of services covered by the non-compete.
Legal reasoning: Non-compete clauses are generally enforceable, but courts often scrutinize their reasonableness in terms of duration, geographic scope, and the scope of prohibited activities. Overly broad non-compete clauses may be considered unenforceable or against public policy.
Liability (Clause 6): The clause places all liability for any bugs, security vulnerabilities, or system failures in the delivered software, including consequential damages, on the contractor, with no cap on liability.
Suggested modification: Negotiate a more reasonable allocation of liability, potentially including a cap on the contractor's liability and excluding certain types of consequential damages that may be outside the contractor's control.
Legal reasoning: The principle of proportionality and fairness in the allocation of risk and liability suggests that the contractor should not be expected to assume unlimited liability for issues that may be beyond their control or reasonably foreseeable. Capping liability can help ensure a more equitable arrangement.
Indemnification (Clause 7): The clause requires the contractor to indemnify the client against all claims arising from the contractor's work, including claims by third parties, regardless of fault.
Suggested modification: Limit the indemnification to claims directly related to the contractor's negligence or intentional misconduct, and exclude claims that are outside the contractor's reasonable control or responsibility.
Legal reasoning: The principle of proportionality and fairness in the allocation of risk and liability suggests that the contractor should not be expected to indemnify the client for claims that are not directly related to the contractor's actions or within their control.
By addressing these clauses and suggesting more balanced and reasonable modifications, the contract can be made more equitable for the contractor, while still protecting the legitimate interests of the client.
Turn this model response into notes, narration, or a short video
Partner link