Does This Clause Pass Meridian's Playbook?
Every sophisticated client has contracting standards that deviate from market norms in specific, deliberate ways. Meridian requires 36-month data retention (market is 12), caps consequential damages at 3x fees (market is 1x), and mandates SOC 2 Type II for any vendor touching PII — even Tier 3 vendors under $50K. No general-purpose AI knows this.
Sample from the record
5 of 1,847 examples
Input
Limitation of Liability clause: "In no event shall either party's aggregate liability exceed the total fees paid or payable under this Agreement during the twelve (12) month period preceding the claim." Vendor: CloudSync Analytics (Tier 2, $180K ARR, processes employee PII).
Trained output
FAILS PLAYBOOK — Section 8.2(b). Meridian Playbook requires consequential damages cap of 3x annual fees for Tier 2 vendors processing PII (Playbook Section 8.2(b), revised Q3 2023). This clause caps aggregate liability at 1x trailing twelve months — below Meridian's minimum. Additionally, the clause uses 'fees paid or payable' which Meridian's playbook flags as ambiguous when payment terms are net-60 (Section 8.2, Note 3). REQUIRED CHANGES: (1) Increase aggregate cap to 3x annual fees ($540K minimum). (2) Add carve-outs for data breach, IP indemnity, and confidentiality breach per Section 8.3. (3) Replace 'fees paid or payable' with 'total annual fees under all active SOWs.' FALLBACK: If vendor resists 3x, Meridian has accepted 2x with enhanced cyber insurance requirement ($5M policy) — see Playbook Section 8.2(b), Alternative Position B.
What you're looking at
1,847 clause-level annotations from Meridian Technologies' vendor contracts (2019-2025), tagged against playbook sections, vendor tiers, and negotiation outcomes. Includes 312 negotiation histories showing which fallback positions were accepted.
Think of it as a clerkship compressed into 3 minutes.
Record size
1,847 examples
Base model
Qwen 2.5 7B
Training time
~35 minutes
Takes about 90 seconds on demo data