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.
Gpt 4 1'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.
Certainly! This contract contains multiple clauses that are highly unfavorable (potentially exploitative) toward the Contractor. Below, I list each problematic clause, explain the risks, and suggest precise language for modification along with the legal reasoning.
Original:
Client reserves the right to modify the scope at any time without additional compensation.
Risk:
Client can expand the required work without paying more, which is unfair and potentially abusive.
Suggested Modification:
Any modification to the scope of work must be agreed upon in writing by both parties, including adjustments to compensation and timeline as appropriate.
Legal Reasoning:
Fair contracts require mutual agreement for changes; unilateral scope changes can result in unpaid labor or “scope creep.”
Original:
Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion.
Risk:
Client can refuse payment arbitrarily, even if Contractor performed as agreed.
Suggested Modification:
Payment may only be withheld for unsatisfactory deliverables if Contractor is notified in writing of specific deficiencies within 10 business days of delivery, and is given a reasonable opportunity to cure such deficiencies.
Legal Reasoning:
Courts generally require objective standards for withholding payment and an opportunity to cure (fix) any issues.
Original:
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.
Risk:
Client obtains rights to Contractor’s pre-existing IP (e.g., code, libraries) that were not specifically developed for the project.
Suggested Modification:
All work product specifically created for Client under this Agreement shall be the exclusive property of Client. Contractor’s pre-existing intellectual property, and any tools, libraries, or methodologies not developed specifically for Client, shall remain the property of Contractor. Contractor grants Client a non-exclusive, royalty-free license to use Contractor’s pre-existing IP solely as necessary for the deliverables.
Legal Reasoning:
It is standard to distinguish between “work-for-hire” and pre-existing IP; otherwise, the Contractor can lose valuable assets not intended for transfer.
Original:
Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination.
Risk:
Overly broad and lengthy non-compete greatly restricts Contractor’s ability to work, possibly unenforceable in some jurisdictions.
Suggested Modification:
Contractor agrees not to solicit Client's existing customers or use Client's confidential information to compete for a period of 6 months following termination. This non-compete shall be limited to direct competitors identified in advance and shall not restrict Contractor’s ability to provide general software development services.
Legal Reasoning:
Courts often strike down broad non-competes; reasonable duration, scope, and geographic limits are required for enforceability.
Original:
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.
Risk:
Client can terminate instantly without compensation; Contractor is forced to deliver unpaid work.
Suggested Modification:
Either party may terminate this agreement with 14 days written notice. Upon termination, Contractor shall be compensated for all work completed and in progress up to the effective date of termination.
Legal Reasoning:
Fairness and mutuality are required; courts generally require payment for work performed and reasonable notice.
Original:
Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability.
Risk:
Contractor could face unlimited liability, financially devastating even for minor bugs.
Suggested Modification:
Contractor’s liability for defects in delivered software shall be limited to direct damages up to the amount of fees paid under this Agreement. Contractor shall not be liable for consequential, incidental, or punitive damages.
Legal Reasoning:
Commercial contracts almost always include liability caps; unlimited liability is unconscionable and rarely enforceable.
Original:
Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault.
Risk:
Contractor is liable even if Client is at fault or if claims are frivolous.
Suggested Modification:
Contractor shall indemnify Client against claims arising from Contractor’s willful misconduct or gross negligence. The indemnification shall not apply to claims arising from Client’s actions, directions, or modifications to the work.
Legal Reasoning:
Indemnification must be limited to fault or negligence; “regardless of fault” is not commercially reasonable.
Original:
Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination.
Risk:
Overly broad and lengthy restriction; may prevent Contractor from even listing the engagement on a resume.
Suggested Modification:
Contractor shall not disclose Client’s confidential information (as defined herein) for 2 years after termination. Contractor may disclose the existence of the engagement and general nature of services for professional purposes, provided no confidential information is revealed.
Legal Reasoning:
Confidentiality must be reasonable in duration and scope; contractors generally need to reference work experience.
Original:
Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party.
Risk:
Contractor may need to travel to a distant jurisdiction and bear all costs, even for minor disputes.
Suggested Modification:
Any disputes shall be resolved through binding arbitration in a mutually agreed location. Each party shall bear its own costs unless determined otherwise by the arbitrator.
Legal Reasoning:
Location should be fair and mutually agreed. Costs should not automatically fall on the losing party, as this can discourage valid claims.
| Clause | Key Risk | Modification | Legal Reasoning |
|---|---|---|---|
| Scope | Unpaid work | Mutual written agreement for changes | Prevents scope creep |
| Payment | Withholding payment | Specific criteria & cure period | Objective standards required |
| IP | Loss of pre-existing IP | Only work-for-hire; license for pre-existing | Protects Contractor’s assets |
| Non-compete | Can't work for 2 years | Limit scope, duration, geography | Must be reasonable to be enforceable |
| Termination | No notice/pay for unfinished work | Mutual notice, pay for work done | Fairness/mutuality |
| Liability | Unlimited liability | Cap liability, exclude consequential damages | Commercially reasonable |
| Indemnification | Indemnify regardless of fault | Limit to willful misconduct/negligence | Must be tied to fault |
| Confidentiality | Can’t mention engagement | Limited duration/scope | Reasonableness |
| Dispute Resolution | Unfair venue/costs | Mutually agreed location, costs as determined | Fairness |
The contract is extremely one-sided and exposes the Contractor to major risks.
All suggested modifications above are standard in software consulting agreements and would make the contract fair and legally defensible.
Legal Reasoning:
Courts generally favor contracts that are mutual, reasonable, and specific. Overbroad, unlimited, or unilateral clauses are often unenforceable and can be struck down. Contractors should always negotiate these terms before signing.
Recommendation:
Contractor should negotiate all the above points, and never sign the agreement as currently drafted. Consider consulting a lawyer for jurisdiction-specific advice.
Turn this model response into notes, narration, or a short video
Partner link