FR EA
1025-00008 · Quorum Insurance Holdings · Transaction Documents/MDLA
issues-list-open-points-tracker-v2.xlsx DOCUMENT M&A / Corporate
64 / 76 ← → ✕
Contract analysis Extract to table

[sheet: Cover]

FieldValue
Document TitleIssues List / Open Points Tracker — Master Data License Agreement
MatterQuorum Insurance Holdings Corp. / Meridian Credit intelligence, Inc. — Enterprise Data License
C&H Matter No.1025-00008
Version2.0 — Updated Post-June 30, 2023 Negotiation Session (New York)
DateJuly 2023
Prepared ByWendy Schultz (Lead Associate, IP) / Omar Siddiqui (Working Associate, IP)
Reviewed ByLeonard Cross (Responsible Partner) / Patricia Heng (Senior Counsel, Tech Transactions)
Client ContactGregory Stahl, VP Legal Affairs, Quorum Insurance Holdings Corp.
Counterparty CounselKessler Pruitt & Ashe LLP (Graham Whitley, Nina Chastain, Derek Fontaine)
ConfidentialityPRIVILEGED & CONFIDENTIAL — ATTORNEY WORK PRODUCT — FOR INTERNAL USE ONLY
Prior VersionVersion 1.0 dated January 15, 2023
Transaction DocumentsMaster Data License Agreement (MDLA); Data Security Addendum (DSA); Data Processing Agreement (DPA); Service Level Agreement (SLA); Technical Schedule A; FCRA Permissible Purpose Certification
Governing LawNew York (without regard to conflicts-of-law principles)
Total Deal Value$60,000,000 over 5-year initial term (plus $1,500,000 one-time implementation fee)

[sheet: Summary Dashboard]

CategoryTotal IssuesAgreed / ClosedOpen — Active NegotiationOpen — Critical / RedDeferredNotes
1. Definitions & Interpretation86200Two minor definition refinements remain (Derived Data, Permitted Purpose)
2. Grant of License / Scope54100Scope of license for internal use agreed; sublicense carve-out for affiliates open
3. Data Products & Delivery66000Fully agreed at June 30 session — MCI Consumer Credit File, MCI CommercialView, MCI AltSignal specifications finalized
4. Fees & Payment Terms75110Year 1 fee ($10.8M), Years 2–5 ($12.3M/yr), quarterly installments agreed; MFN pricing clause remains CRITICAL OPEN
5. Most Favored Nation / Pricing Protection30030ALL RED — Full MFN rejected by Meridian (Apr. 21); pricing audit right fallback under development by C&H; Meridian offered SLA-only 'most favored terms' (rejected by Quorum)
6. Service Level Agreement55000Fully agreed — 99.9% uptime, latency standards, service credits resolved at June 30 session
7. Derived Data & IP Ownership (Article VII)80260CRITICAL OPEN — Quorum ownership position, license-back, revenue share (15%), sufficient transformation standard, QuorumScore carve-out, ML model output classification all unresolved
8. Data Security & Privacy65100Substantially agreed; 48-hour breach notification accepted; sub-processor audit scope minor open point
9. FCRA / GLBA Compliance44000Permissible purpose certification schedule agreed; GLBA safeguard provisions agreed
10. CCPA/CPRA & Data Processing43100DPA substantially agreed; de-identification standard for Derived Data commercialization linked to Article VII resolution
11. Representations & Warranties54100Meridian's data-accuracy rep still under discussion
12. Indemnification43100Scope of Meridian's IP indemnity (covering data-accuracy claims) open
13. Limitation of Liability32100Consequential damages carve-outs not yet fully aligned
14. Insurance Requirements33000Agreed — Quorum: $5M CGL, $50M cyber; Meridian: $5M CGL, $25M cyber/tech E&O
15. Term & Renewal330005-year initial term agreed; auto-renewal mechanics agreed
16. Termination & Post-Termination52120Return/destroy raw data within 90 days agreed; Derived Data treatment post-termination CRITICAL OPEN; survival of Derived Data rights CRITICAL OPEN
17. Dispute Resolution30030ALL RED — Quorum: exclusive jurisdiction SDNY or NY Supreme Court Commercial Division; Meridian: binding AAA arbitration, 3-arbitrator panel, New York seat; no movement
18. Confidentiality / Publicity22000Agreed; mutual NDA (NDA-QIH-MCI-2022-001) governs pre-closing; MDLA confidentiality section agreed
19. Corporate / Lender Consents & Conditions Precedent41300Standish National Bank consent under Section 7.12(b) required ($60M exceeds $25M threshold); Quorum board resolution pending; Meridian board authorization pending
20. Miscellaneous / Boilerplate44000Notices, assignment, amendments, counterparts — all agreed
TOTALS92621515067% agreed; 16% active open; 16% critical/red; 0% deferred

[sheet: Detailed Issues Tracker]

Issue #MDLA Section / ScheduleIssue CategoryIssue DescriptionPriorityStatusStatus as of v1.0 (Jan 2023)Change Since v1.0Quorum PositionMeridian / KP&A PositionProposed CompromiseC&H AssignedQuorum Business OwnerLast DiscussedNext Step / Action ItemNotes / Cross-References
1Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Derived Data' — scope of data, models, scores, indices, and analytics outputs created by Quorum using licensed Meridian data as an inputCriticalOpenOpenNo change — remains core dispute linked to Article VIIDerived Data means any data, models (including trained ML model weights/parameters), scores, indices, enriched datasets, or analytics outputs created, developed, or generated by or on behalf of Quorum that use, incorporate, or are based on the Licensed Data as an input, including but not limited to QuorumScore™ outputs, propensity models, and blended risk scoresDerived Data means any data, model, score, index, or output that incorporates, is based on, or is traceable to Licensor's Licensed Data, constituting a derivative work under copyright law and remaining subject to Licensor's underlying IP rightsQuorum to propose tiered definition: (a) 'Direct Derivatives' (outputs containing identifiable Meridian data elements) vs. (b) 'Transformed Outputs' (sufficiently transformed/de-identified outputs where no Meridian raw data can be reverse-engineered) — different rights regime for each tierWendy Schultz / Omar SiddiquiRajesh Anand (CDO)2023-06-30C&H to circulate revised tiered definition to client for approval before transmitting to KP&ACentral to Article VII resolution; linked to Issues #45–52; Meridian insists on 'derivative work' characterization; see C&H memo on ML model outputs (Jan. 2023)
2Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Permitted Purpose' — scope of Quorum's authorized use of Licensed DataHighOpenOpenNarrowed gap at June 30 session; Quorum's internal use largely agreed; third-party commercialization of Derived Data still linked to Article VIIBroad: automated underwriting models, claims-fraud detection algorithms, customer propensity scoring across all Quorum P&C, life, and specialty lines, plus creation and commercialization of Derived DataLimited to Quorum's internal insurance underwriting, claims, and risk management operations; excludes any third-party commercialization or sublicensingInternal use agreed; external commercialization scope to follow Article VII resolutionWendy SchultzDiane Lowell (SVP Underwriting Analytics)2023-06-30Finalize internal-use language; defer external-use scope pending Article VIILinked to Issues #45–52 (Derived Data)
3Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Licensed Data' — enumeration of data products and formats included in the license grantMediumAgreedAgreedNo changeAll MCI Consumer Credit File, MCI CommercialView, and MCI AltSignal data products as specified in Technical Schedule AAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-01-18None — closedFinalized in Technical Schedule A
4Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Affiliate' — scope of entities covered by license grantMediumAgreedAgreedNo changeAny entity controlling, controlled by, or under common control with a party, where control means ownership of >50% voting securitiesAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closedStandard definition accepted by both sides
5Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Confidential Information' — scope and exclusionsLowAgreedAgreedNo changeStandard carve-outs for publicly available information, independently developed information, and information received from third parties without restrictionAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closedAligned with mutual NDA (NDA-QIH-MCI-2022-001)
6Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'intellectual Property Rights' — enumeration of IP categoriesLowAgreedAgreedNo changePatents, copyrights, trademarks, trade secrets, and all other proprietary rights recognized under applicable lawAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closed
7Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Data Security Incident' — triggering events for breach notificationMediumAgreedAgreedNo changeUnauthorized access, acquisition, use, or disclosure of Licensed Data or Derived DataAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-01-18None — closedIncorporated into DSA
8Section 1.1 — DefinitionsDefinitions & InterpretationDefinition of 'Service Level' — uptime and performance metrics baselineMediumAgreedOpenAgreed at June 30 session upon SLA finalizationAs defined in SLA scheduleAgreedN/A — AgreedPatricia HengPriya Nair2023-06-30None — closedLinked to SLA schedule
9Section 2.1 — Grant of LicenseGrant of License / ScopeNon-exclusive license grant for internal use of Licensed Data across all Quorum business units and insurance linesHighAgreedAgreedNo changeNon-exclusive, worldwide license for internal business purposes across all Quorum P&C, life, and specialty insurance linesAgreed to non-exclusive internal-use licenseN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
10Section 3.1 — Licensed Data ProductsData Products & DeliverySpecification of Licensed Data products: MCI Consumer Credit File™ (~310M consumer records, daily batch + real-time API), MCI CommercialView™ (~42M business records, weekly batch), MCI AltSignal™ (~85M consumer alt-data records, daily batch)HighAgreedOpenAgreed at June 30 session; Technical Schedule A finalizedAll three products included; delivery via SFTP batch and REST API as specifiedAgreed to Quorum's specificationsN/A — AgreedOmar SiddiquiPriya Nair (Dir. Data Engineering)2023-06-30None — closedTechnical Schedule A signed off by both Priya Nair and Keith Marlow
11Section 2.2 — SublicensingGrant of License / ScopeRight to sublicense Licensed Data to Quorum affiliates without additional feeHighAgreedAgreedNo changeSublicense to affiliates permitted without Meridian consent or additional feeAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
12Section 2.3 — SublicensingGrant of License / ScopeSublicense carve-out for non-affiliated third parties (e.g., MGAs, reinsurers)HighOpenOpenNo change; linked to Article VII derived-data commercializationQuorum may sublicense Derived Data (but not raw Licensed Data) to non-affiliated third parties for commercial purposesNo sublicensing of any data (raw or derived) to non-affiliated third parties under any circumstancesDefer resolution to Article VII framework; if Transformed Outputs permitted for commercialization, sublicensing followsWendy SchultzGregory Stahl / Diane Lowell2023-06-30Link to Article VII resolutionSublicensing of raw data not sought by Quorum; issue is Derived Data only
13Section 2.4 — TerritoryGrant of License / ScopeTerritorial scope of license — worldwide vs. U.S.-onlyMediumAgreedAgreedNo changeWorldwide — Quorum has international reinsurance operationsAgreed to worldwide scopeN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closed
14Section 3.2 — Data DeliveryData Products & DeliveryData delivery methods: SFTP batch and REST API specificationsHighAgreedOpenAgreed at June 30 sessionSFTP batch (AES-256 encrypted) and REST API (OAuth 2.0 authentication) per Technical Schedule AAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-06-30None — closed
15Section 4.1 — License FeesFees & Payment TermsAnnual license fee structure: Year 1 $10,800,000 ($900K/mo reflecting 6-month ramp); Years 2–5 $12,300,000/yr ($1,025K/mo); total $60,000,000 over 5-year termHighAgreedAgreedNo change$10.8M Year 1 / $12.3M Years 2–5; quarterly in advance ($2.7M Q1 Yr1; $3.075M Yrs 2–5)AgreedN/A — AgreedMarcus WeillThomas Ng (VP Procurement)2023-01-18None — closedYear 1 discount reflects 6-month implementation ramp; reconciliation: $10.8M + ($12.3M × 4) = $60.0M
16Section 4.2 — Implementation FeeFees & Payment TermsOne-time implementation/integration fee of $1,500,000 (outside the $60M license value; billed separately upon execution)MediumAgreedAgreedNo change$1,500,000 payable within 30 days of MDLA executionAgreedN/A — AgreedMarcus WeillThomas Ng2023-01-18None — closedNot included in $60M total deal value
17Section 4.3 — Volume Tiers & OverageFees & Payment TermsBase tier: up to 500 million records/month (consumer + commercial combined); overage rate $0.003 per record above base tierMediumAgreedAgreedNo change500M base tier; $0.003/record overageAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-01-18None — closedCurrent estimated monthly volume ~437M records (87.4% of base tier); well within base tier
18Section 4.4 — Late PaymentFees & Payment TermsLate payment interest rate: 1.5% per month (18% per annum) on overdue amounts, simple interestLowAgreedAgreedNo change1.5%/monthAgreedN/A — AgreedMarcus WeillThomas Ng2023-01-18None — closed
19Section 4.5 — TaxesFees & Payment TermsTax gross-up and withholding provisionsLowAgreedAgreedNo changeStandard tax gross-up; each party responsible for its own income taxes; Quorum responsible for withholding if requiredAgreedN/A — AgreedMarcus WeillThomas Ng2023-01-18None — closed
20Section 4.6 / Proposed RiderMost Favored Nation / Pricing ProtectionMost favored nation pricing clause — Quorum demands automatic price adjustment if Meridian offers any insurance-industry licensee more favorable per-record pricing, volume discounts, or fee termsCriticalCritical-OpenOpenEscalated to CRITICAL: Meridian formally rejected full MFN on April 21, 2023; Meridian board resolution of August 22, 2023 (influenced by Breckenridge Capital Partners and Whitmore Zanthor IPO concerns) resolved against MFN; CEO-to-CEO call (Tierney/Halstead, May 15, 2023) did not resolveFull MFN: if Meridian offers any U.S.-domiciled insurance carrier, MGA, or insurtech firm with annual premiums written ≥ $500M more favorable per-record pricing, volume discounts, or fee terms, Quorum's pricing automatically adjusts to matchCategorically refused. Reasons: (a) confidentiality obligations to other licensees; (b) impracticability of cross-licensee price comparisons given bespoke data packages; (c) Breckenridge/Whitmore Zanthor concern that MFN viewed as margin risk in IPO due diligence; (d) antitrust sensitivities in credit-data marketsQuorum developing fallback: 'Pricing Audit Right' — annual audit by independent third-party auditor (mutually approved) to verify Quorum's effective per-record rate does not exceed 110% of lowest comparable insurance-industry licensee rate. To be formally proposed post-session (target Sept. 2023)Wendy Schultz / Patricia HengThomas Ng / Rajesh Anand2023-06-30C&H to finalize pricing audit right draft language (target: Sept. 2023); consult Pinnacle Ridge Advisory (Franklin Osei) pricing benchmark study (delivered Feb. 14, 2023) for supporting dataKey impasse #1; Meridian board resolution Aug. 22, 2023 is formal backstop; Breckenridge Capital Partners (62.5% owner, Caleb Rourke) and Whitmore Zanthor (Rachel Ng-Castillo) driving resistance; see C&H memo on MFN market practice & enforceability; see C&H antitrust memo
21Section 4.6 / Proposed RiderMost Favored Nation / Pricing ProtectionMeridian's counter-offer: 'Most Favored Terms' clause limited to data-delivery SLAs and uptime commitments only — explicitly excluding pricingCriticalCritical-OpenN/A (new in v2)New counter received; Meridian offered SLA-only most favored terms at June 30 sessionRejected — Quorum views SLA-only most favored terms as commercially meaningless given SLA already agreedOffered as alternative to any pricing-related MFN or audit rightQuorum to reject formally and counter with pricing audit right proposalWendy SchultzThomas Ng2023-06-30Include rejection in next correspondence to KP&A; pivot to pricing audit rightMeridian's formal counter expected Oct. 2023
22Section 4.6 / Proposed RiderMost Favored Nation / Pricing ProtectionMFN comparator class definition — which entities are included in MFN comparisonCriticalCritical-OpenOpenNo progress; linked to resolution of Issues #20–21All U.S.-domiciled insurance carriers, managing general agents, and insurtech firms with annual premiums written ≥ $500 millionN/A — Meridian refuses any MFN; comparator class is moot absent agreement on the principleIf pricing audit right accepted, comparator class would narrow to 'comparable insurance-industry licensee' (to be defined)Wendy SchultzThomas Ng2023-06-30Draft comparator class definition for pricing audit right alternativePinnacle Ridge benchmark study identifies 6 comparable licensees in insurance vertical
23Section 4.7 — Fee EscalationFees & Payment TermsAnnual fee escalation mechanism for renewal periods beyond Year 5MediumOpenOpenPartially discussed; no agreementCPI-based escalation capped at 3% per annum for renewal termsMeridian seeks uncapped escalation tied to CPI plus 2% floorCap at CPI + 1% with 4% ceiling per annumMarcus WeillThomas Ng2023-06-30Draft compromise escalation clause for renewal termsRelevant only for auto-renewal periods beyond initial 5-year term
24Section 3.3 — Data FormatData Products & DeliveryData format specifications: file formats (Parquet, CSV), schema versioning, and backward compatibility commitmentsMediumAgreedOpenAgreed at June 30 sessionParquet preferred; CSV fallback; 12-month backward compatibility for schema changesAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-06-30None — closedIncorporated into Technical Schedule A
25Section 3.4 — Data RefreshData Products & DeliveryData refresh frequency and update Larkspur Services Inc.MediumAgreedOpenAgreed at June 30 sessionConsumer Credit File and AltSignal: daily; CommercialView: weeklyAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-06-30None — closed
26Section 3.5 — Historical DataData Products & DeliveryAccess to historical data archives (backfill) for model training purposesMediumAgreedOpenAgreed at June 30 session; 7-year lookback included7-year historical lookback for Consumer Credit File; 5-year for CommercialView; 3-year for AltSignalAgreed to Quorum's requested lookback periodsN/A — AgreedOmar SiddiquiPriya Nair2023-06-30None — closedHistorical data delivery within 60 days of MDLA execution
27Section 3.6 — Data QualityData Products & DeliveryData quality standards: completeness thresholds, error rate tolerances, and remediation proceduresMediumAgreedOpenAgreed at June 30 session≤2% missing-value rate for core fields; ≤0.5% error rate; remediation within 5 business daysAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-06-30None — closedIncluded in Technical Schedule A
28Section 2.5 — License RestrictionsGrant of License / ScopeRestrictions on reverse engineering, decompilation, or disassembly of Meridian's proprietary algorithms embedded in data feedsMediumAgreedAgreedNo changeStandard reverse-engineering prohibition acceptedAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closed
29Section 5.1 — Audit RightsFees & Payment TermsMeridian's right to audit Quorum's usage of Licensed Data (volume, permitted purpose compliance) — frequency, scope, and cost allocationMediumAgreedAgreedNo changeAnnual audit right upon 30 days' notice; at Meridian's cost unless audit reveals material non-compliance (>5% overage)AgreedN/A — AgreedPatricia HengThomas Ng2023-01-18None — closed
30Section 6.1 — SLAService Level AgreementAPI response time / latency standards for real-time data accessHighAgreedOpenAgreed at June 30 sessionP95 latency ≤200ms for Consumer Credit File API; ≤500ms for CommercialView APIAgreed to Quorum's latency thresholdsN/A — AgreedPatricia Heng / Omar SiddiquiPriya Nair2023-06-30None — closedIncorporated into SLA schedule
31Section 6.2 — SLAService Level AgreementScheduled maintenance windows and exclusions from uptime calculationsMediumAgreedOpenAgreed at June 30 sessionMaintenance window: Sundays 2:00–6:00 AM ET; excluded from uptime calculations; max 4 hours/weekAgreedN/A — AgreedPatricia HengPriya Nair2023-06-30None — closed
32Section 6.3 — SLAService Level AgreementTiered service credit schedule for SLA failuresHighAgreedOpenAgreed at June 30 session99.9–99.5%: 5% monthly fee credit; 99.5–99.0%: 10% credit; <99.0%: 20% credit plus termination right if <99.0% for 3 consecutive monthsAgreed to tiered structureN/A — AgreedPatricia HengThomas Ng / Priya Nair2023-06-30None — closed
33Section 6.4 — SLAService Level AgreementSFTP batch delivery windows and failure escalation proceduresMediumAgreedOpenAgreed at June 30 sessionDaily batch: available by 6:00 AM ET; weekly batch: available by 8:00 AM ET Monday; escalation: L1 notification within 1 hour, L2 within 4 hoursAgreedN/A — AgreedOmar SiddiquiPriya Nair2023-06-30None — closed
34Section 7.1 — Derived DataDerived Data & IP OwnershipScope of Quorum's right to create Derived Data using Licensed Data as an inputCriticalOpenOpenNarrowed at June 30 session; internal creation right largely accepted; commercialization scope disputedUnrestricted right to create Derived Data using any combination of Licensed Data and Quorum's proprietary dataRight to create Derived Data for internal purposes only; any commercialization subject to Meridian approval and revenue shareInternal creation right agreed; commercialization rights follow Article VII frameworkWendy SchultzRajesh Anand / Diane Lowell2023-06-30Incorporate into Article VII compromise frameworkLinked to Issues #45–52
35Section 8.1 — Reps & WarrantiesRepresentations & WarrantiesMutual representations: due organization, authority, enforceabilityLowAgreedAgreedNo changeStandard mutual repsAgreedN/A — AgreedMarcus WeillGregory Stahl2023-01-18None — closed
36Section 8.2 — Reps & WarrantiesRepresentations & WarrantiesMeridian's representation that it has all necessary rights to license the dataHighAgreedAgreedNo changeMeridian represents it has all rights, licenses, and permissions necessary to grant the license hereinAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
37Section 8.3 — Reps & WarrantiesRepresentations & WarrantiesMeridian's non-infringement representationHighAgreedAgreedNo changeMeridian represents that the Licensed Data and its use by Quorum as permitted will not infringe any third-party IP rightsAgreed with knowledge qualifierN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closedKnowledge qualifier accepted: 'to Meridian's knowledge'
38Section 8.4 — Reps & WarrantiesRepresentations & WarrantiesMeridian's compliance with applicable law representation (FCRA, GLBA, state privacy laws)MediumAgreedAgreedNo changeMeridian represents compliance with all applicable federal and state laws governing consumer and commercial credit dataAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-03-09None — closed
39Section 9.1 — IndemnificationIndemnificationMeridian's indemnification of Quorum for third-party IP infringement claimsHighAgreedAgreedNo changeMeridian indemnifies Quorum for any third-party claims alleging that the Licensed Data infringes such third party's IP rightsAgreed; subject to standard notice, cooperation, and control requirementsN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
40Section 9.2 — IndemnificationIndemnificationQuorum's indemnification of Meridian for Quorum's misuse of Licensed DataHighAgreedAgreedNo changeQuorum indemnifies Meridian for claims arising from Quorum's use of Licensed Data outside Permitted Purpose or in violation of MDLAAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
41Section 9.3 — IndemnificationIndemnificationMutual indemnification for breach of data security obligationsHighAgreedAgreedNo changeMutual indemnification for data breaches caused by indemnifying party's failure to comply with DSAAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-03-09None — closed
42Section 9.4 — IndemnificationIndemnificationScope of Meridian's IP indemnity — whether it covers claims based on data inaccuracy (not just infringement)HighOpenOpenNarrowed at June 30 session; Meridian resists extending IP indemnity to data-accuracy claimsMeridian should indemnify Quorum for third-party claims arising from inaccurate Licensed Data (e.g., FCRA claims by consumers, regulatory actions)IP indemnity covers infringement only; data-accuracy claims are excluded and subject to limitation of liabilitySeparate data-accuracy indemnity with aggregate cap of $5M per year; distinct from IP infringement indemnityWendy Schultz / Omar SiddiquiGregory Stahl / Claudia Reeves2023-06-30Draft data-accuracy indemnity clause with annual cap for client reviewLinked to Issue #90 (data-accuracy representation)
43Section 10.1 — Limitation of LiabilityLimitation of LiabilityAggregate liability cap for each partyHighAgreedAgreedNo changeEach party's aggregate liability capped at 2x annual fees paid or payable in the 12-month period preceding the claim ($24.6M based on Yr 2–5 fees)AgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
44Section 10.2 — Limitation of LiabilityLimitation of LiabilityExclusion of consequential, incidental, special, and punitive damages — and carve-outs from such exclusionHighOpenOpenPartially discussed; Quorum seeks broader carve-outs than MeridianStandard mutual exclusion of consequential damages, BUT with carve-outs for: (a) breach of confidentiality, (b) data security breaches, (c) IP indemnification obligations, (d) willful misconduct/gross negligenceStandard mutual exclusion with carve-outs limited to: (a) willful misconduct onlyExpand carve-outs to include data security breaches and IP indemnification in addition to willful misconductWendy SchultzGregory Stahl2023-06-30Draft revised limitation of liability clause with expanded carve-outs
45Article VII — Section 7.1Derived Data & IP OwnershipOwnership of intellectual property in Derived Data — who owns IP in data, models, scores, indices, and analytics outputs created by Quorum using licensed Meridian dataCriticalCritical-OpenOpenEscalated to CRITICAL; Meridian board resolution Aug. 22, 2023 resolved against granting unrestricted derived-data commercialization rightsQuorum owns all IP in Derived Data; unrestricted rights to use, sublicense, and commercialize without additional fees or Meridian consentDerived Data constitutes a 'derivative work' under copyright law; remains subject to Meridian's underlying IP rights; Meridian retains co-ownership or controlling IP interestQuorum to propose tiered framework: (a) Quorum owns all Derived Data; (b) no license-back; (c) commercialization permitted for 'Transformed Outputs' meeting objective de-identification/transformation standard (jointly agreed, not Meridian sole discretion); (d) no revenue share to Meridian; (e) explicit QuorumScore™ carve-outWendy Schultz / Omar SiddiquiRajesh Anand / Diane Lowell2023-06-30C&H to circulate revised Article VII compromise framework (drafted Jun. 2023) to Quorum for final approval before transmitting to KP&AKey impasse #2; linked to Issue #1 (Derived Data definition); see C&H memos: Derived-Data IP Ownership (Jan. 2023), ML Model Outputs (Jan. 2023), Sufficient Transformation Critique (May 2023), QuorumScore IP Protection (Jun. 2023); Derived Data Commercialization Protocol (Jun. 2023 draft appendix)
46Article VII — Section 7.2Derived Data & IP OwnershipMeridian's demand for perpetual, royalty-free license-back on all Derived Data for Meridian's own useCriticalCritical-OpenOpenNo movement; Meridian maintains demandNo license-back of any kind; Quorum's Derived Data is Quorum's proprietary assetPerpetual, royalty-free, irrevocable license-back to Meridian on all Derived Data for Meridian's own internal and commercial useQuorum rejects entirely; license-back would undermine competitive advantage, particularly for QuorumScore™ (projected $40–50M B2B licensing revenue by 2027)Wendy SchultzRajesh Anand2023-06-30Include firm rejection in revised Article VII; cite market survey memo (Omar Siddiqui, Apr. 2023) showing license-back is outside market normsSee license-back market survey memo; Breckenridge views license-back as protecting Meridian's 'data moat' for IPO narrative
47Article VII — Section 7.3Derived Data & IP OwnershipProhibition on third-party commercialization of Derived Data unless 'sufficiently transformed' — with Meridian having sole discretion to determine 'sufficient transformation'CriticalCritical-OpenOpenNo movement; C&H critique memo issued May 2023Quorum may commercialize Derived Data to third parties without restriction; no 'sufficient transformation' gatekeeping by MeridianNo third-party commercialization unless Derived Data is 'sufficiently transformed' such that no Meridian raw data can be reverse-engineered; Meridian has sole discretion on whether standard is metReplace sole discretion with objective, measurable, jointly agreed criteria for transformation/de-identification (per C&H Derived Data Commercialization Protocol draft); independent expert determination in case of disputeWendy SchultzRajesh Anand / Diane Lowell2023-06-30Finalize objective transformation criteria in Commercialization Protocol appendix; propose independent expert dispute mechanismSee C&H memo critiquing 'sufficient transformation' standard (May 2023); Meridian's sole-discretion standard is unworkably subjective
48Article VII — Section 7.4Derived Data & IP OwnershipMeridian's demand for 15% revenue share on net revenues from Quorum's third-party commercialization of approved Derived DataCriticalCritical-OpenOpenNo movement; Meridian reiterated at June 30 sessionNo revenue share of any kind; Quorum bears all costs of creating Derived Data and should retain all revenues15% of net revenues attributable to Derived Data commercialized to third partiesQuorum rejects; would directly undermine QuorumScore™ B2B licensing strategy ($40–50M projected revenue by 2027); C&H to argue Quorum's proprietary first-party data (claims, policy, telematics) is the primary value driver, not Meridian input dataWendy Schultz / Patricia HengRajesh Anand / Diane Lowell / Thomas Ng2023-06-30Maintain firm rejection; prepare economic analysis showing Quorum's first-party data contribution vs. Meridian data input ratioMeridian's Oct. 10, 2023 formal counter expected to include this demand; Breckenridge views revenue share as IPO-friendly recurring revenue line
49Article VII — Section 7.5Derived Data & IP OwnershipClassification of ML model outputs: whether outputs of Quorum's machine-learning models (trained on Meridian data among other inputs) constitute 'Derived Data' vs. independent outputsCriticalCritical-OpenOpenTechnical experts discussed at June 30 session; no agreementOnly trained model weights/parameters are potentially derivative; live predictions using new non-Meridian inputs are NOT Derived Data — they are independent outputs of the trained modelAll outputs of any model trained on Meridian data are Derived Data, regardless of whether live inference inputs come from Meridian or other sourcesPropose distinction between (a) model training artifacts (weights/parameters — subject to negotiated restrictions) and (b) inference outputs on new data (not Derived Data); objective technical criteria to be definedWendy Schultz / Omar SiddiquiRajesh Anand / Priya Nair2023-06-30C&H and Quorum data science team to develop technical framework paper distinguishing model training vs. inference; Priya Nair to provide technical inputSee C&H memo on ML model outputs — copyright & trade secret analysis (Jan. 2023); this is the most technically complex issue in Article VII
50Article VII — Section 7.6Derived Data & IP OwnershipQuorumScore™ specific carve-out — explicit protection for Quorum's proprietary predictive underwriting modelCriticalCritical-OpenOpenRaised at June 30 session; Meridian took under advisementQuorumScore™ (USPTO application Serial No. 97/482,116) and all outputs thereof are expressly excluded from any Meridian rights — no license-back, no revenue share, no 'sufficient transformation' requirement; QuorumScore blends Meridian credit data with Quorum's own first-party claims, policy, and telematics dataNo product-specific carve-outs; all Derived Data treated uniformly under Article VIIIf Article VII compromise achieved, QuorumScore should be explicitly named as a 'Transformed Output' exempt from Meridian restrictionsWendy SchultzRajesh Anand / Diane Lowell2023-06-30Draft explicit QuorumScore carve-out language for inclusion in revised Article VII; coordinate with Angela Firth at Caldwell & Strauss LLP (Quorum's regular IP counsel) on broader IP protection strategySee QuorumScore IP Protection Strategy memo (Jun. 2023)
51Article VII — Section 7.7Derived Data & IP OwnershipBlended risk score outputs — treatment of scores that blend Meridian data with Quorum first-party data and third-party data from other vendorsHighOpenOpenDiscussed at June 30 session; Meridian position unchangedBlended scores are Quorum's proprietary outputs; Meridian data is one of many inputs and does not dominateAny score incorporating Meridian data is Derived Data subject to Article VII restrictionsInclude blended scores in 'Transformed Outputs' tier if objective de-identification criteria are metOmar SiddiquiRajesh Anand2023-06-30Address in Article VII framework paperRelated to Issue #49 (ML model outputs)
52Article VII — Section 7.8Derived Data & IP OwnershipAudit rights for Meridian to verify compliance with Derived Data restrictions and transformation standardsMediumOpenOpenDiscussed briefly at June 30 sessionQuorum accepts reasonable audit right (annual, at Meridian's cost, 30 days' notice) to verify compliance with agreed transformation/de-identification criteriaMeridian demands quarterly audit right at Quorum's cost with unlimited scopeAnnual audit at Meridian's cost; scope limited to Derived Data compliance; qualified independent auditor mutually agreedOmar SiddiquiRajesh Anand2023-06-30Draft audit rights clause for Derived Data compliance
53Section 11.1 — Data SecurityData Security & PrivacyEncryption standards: data at rest (AES-256) and data in transit (TLS 1.2+)HighAgreedAgreedNo changeAES-256 at rest; TLS 1.2 or higher in transitAgreedN/A — AgreedDavid CartwrightClaudia Reeves / Priya Nair2023-01-18None — closedIncorporated into DSA
54Section 11.2 — Data SecurityData Security & PrivacyAccess control: role-based access control (RBAC), multi-factor authentication (MFA), and least-privilege principleHighAgreedAgreedNo changeRBAC with MFA for all access; least-privilege principle; quarterly access reviewsAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-01-18None — closed
55Section 11.3 — Data SecurityData Security & PrivacyData breach notification: 48 hours from discovery by either partyHighAgreedAgreedNo change48 hours from discoveryAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-01-18None — closedSee incident response & breach notification memo (Feb. 2023); aligns with 23 NYCRR 500
56Section 11.4 — Data SecurityData Security & PrivacySecurity certifications required: Meridian — SOC 2 Type II, ISO 27001; Quorum — SOC 2 Type IIHighAgreedAgreedNo changeBoth parties maintain SOC 2 Type II; Meridian additionally ISO 27001AgreedN/A — AgreedDavid Cartwright / Lisa JohannsenClaudia Reeves2023-01-18None — closedCertifications verified; included in DSA
57Section 11.5 — Data SecurityData Security & PrivacySub-processor management: Meridian's obligation to ensure sub-processors comply with DSA standardsHighAgreedAgreedNo changeMeridian responsible for sub-processor compliance; must notify Quorum of new sub-processors 30 days in advance; Quorum has objection rightAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-03-09None — closed
58Section 11.6 — Data SecurityData Security & PrivacySub-processor audit scope — whether Quorum may audit Meridian's sub-processors directlyMediumOpenOpenNarrowed at June 30 session; Meridian prefers SOC 2 reports in lieu of direct auditQuorum may audit sub-processors directly upon reasonable noticeQuorum may review sub-processor SOC 2 Type II reports but may not conduct direct auditsQuorum accepts SOC 2 reports as default; direct audit right triggered only upon material data security incident involving the sub-processorDavid Cartwright / Lisa JohannsenClaudia Reeves2023-06-30Draft conditional audit right clauseMinor open point; near resolution
59Section 12.1 — FCRAFCRA / GLBA ComplianceFCRA permissible purpose certification — Quorum's certification of permissible purpose for each data requestHighAgreedOpenAgreed at March 9 sessionQuorum certifies permissible purpose per FCRA §604(a)(3)(C) (insurance underwriting) for each consumer data requestAgreed; certification schedule attached as exhibitN/A — AgreedDavid CartwrightClaudia Reeves2023-03-09None — closedFCRA Permissible Purpose Certification schedule finalized
60Section 12.2 — FCRAFCRA / GLBA ComplianceFCRA adverse action notice obligations — responsibility allocation between Quorum and MeridianMediumAgreedAgreedNo changeQuorum solely responsible for adverse action notices to consumers; Meridian provides required data source identificationAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-01-18None — closed
61Section 12.3 — GLBAFCRA / GLBA ComplianceGLBA safeguard provisions — both parties' obligations under GLBA Safeguards RuleHighAgreedOpenAgreed at March 9 sessionBoth parties comply with GLBA Safeguards Rule; mutual representations of complianceAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-03-09None — closed
62Section 12.4 — FCRAFCRA / GLBA ComplianceFCRA dispute handling procedures — obligations upon consumer disputesMediumAgreedAgreedNo changeMeridian handles consumer disputes regarding Licensed Data accuracy; Quorum cooperates and provides information as neededAgreedN/A — AgreedDavid CartwrightClaudia Reeves2023-01-18None — closed
63DPA Section 1CCPA/CPRA & Data ProcessingCCPA/CPRA classification of parties: Meridian as 'business' and Quorum as 'business' (not service provider) for consumer dataMediumAgreedAgreedNo changeBoth parties are 'businesses' under CCPA/CPRA; neither is a 'service provider' to the otherAgreedN/A — AgreedDavid Cartwright / Lisa JohannsenClaudia Reeves2023-03-09None — closed
64DPA Section 2CCPA/CPRA & Data ProcessingConsumer opt-out handling: procedures for processing CCPA/CPRA opt-out requests received by either partyMediumAgreedOpenAgreed at March 9 sessionEach party processes opt-out requests it receives; mutual notification within 5 business days; Meridian removes consumer data from feeds within 30 days of verified opt-outAgreedN/A — AgreedLisa JohannsenClaudia Reeves2023-03-09None — closed
65DPA Section 3CCPA/CPRA & Data ProcessingData retention limitations under CCPA/CPRA — retention periods for consumer personal informationMediumAgreedAgreedNo changeRetain consumer PI only as long as necessary for Permitted Purpose; maximum 7-year retention for raw Licensed Data; subject to termination provisionsAgreedN/A — AgreedLisa JohannsenClaudia Reeves2023-03-09None — closed
66DPA Section 4CCPA/CPRA & Data ProcessingDe-identification standard for Derived Data commercialization — CCPA/CPRA de-identification requirements as applied to Derived Data sold or licensed to third partiesHighOpenOpenLinked to Article VII resolution; cannot finalize without Derived Data definitionDe-identification per CCPA §1798.140(m) sufficient for Derived Data commercialization; once de-identified, data is no longer 'personal information' and not subject to CCPA restrictionsAny commercialization of Derived Data incorporating consumer PI must meet CCPA de-identification standard AND Meridian's 'sufficient transformation' standard under Article VIIAlign de-identification standard with objective transformation criteria in Article VII framework; single standard serving both CCPA and contractual purposesLisa Johannsen / Wendy SchultzClaudia Reeves / Rajesh Anand2023-06-30Resolve in conjunction with Article VII frameworkDirectly linked to Issues #45–52
67Section 10.1 — SLAService Level AgreementUptime commitment: 99.9% monthly availability for all data feeds and API access; service credits for failures; measurement methodologyHighAgreedOpenAgreed at June 30 session99.9% monthly uptime; tiered service credits; automatic credits without need for claim submission99.9% uptime accepted; agreed to Quorum's service credit structureN/A — AgreedPatricia Heng / Omar SiddiquiPriya Nair2023-06-30None — closed; incorporate into final SLA scheduleSee SLA Memorandum (Patricia Heng, Mar. 2023)
68Section 13.1 — InsuranceInsurance RequirementsQuorum insurance minimums: $5M CGL per occurrence, $50M cyber liability aggregateMediumAgreedAgreedNo change$5M CGL; $50M cyberAgreedN/A — AgreedMarcus WeillClaudia Reeves2023-01-18None — closed
69Section 13.2 — InsuranceInsurance RequirementsMeridian insurance minimums: $5M CGL per occurrence, $25M cyber/tech E&O aggregateMediumAgreedAgreedNo change$5M CGL; $25M cyber/tech E&OAgreedN/A — AgreedMarcus WeillClaudia Reeves2023-01-18None — closed
70Section 13.3 — InsuranceInsurance RequirementsCertificate of insurance exchange and additional insured requirementsLowAgreedAgreedNo changeAnnual certificate exchange; each party named as additional insured on CGL policyAgreedN/A — AgreedMarcus WeillClaudia Reeves2023-01-18None — closed
71Section 14.1 — TermTerm & RenewalInitial term: 5 years from effective dateHighAgreedAgreedNo change5-year initial term commencing on effective dateAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
72Section 14.2 — RenewalTerm & RenewalAuto-renewal mechanism: automatic 2-year renewal terms unless either party provides 180 days' written notice of non-renewalMediumAgreedAgreedNo changeAuto-renewal for successive 2-year terms; 180-day non-renewal noticeAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
73Section 14.3 — RenewalTerm & RenewalFee adjustment for renewal terms — escalation mechanismMediumAgreedAgreedNo changeRenewal term fees subject to CPI adjustment per Section 4.7 (if agreed) or negotiationAgreed in principle; specific escalation rate linked to Issue #23N/A — Agreed in principleMarcus WeillThomas Ng2023-01-18None — closed in principle; specifics depend on Issue #23Linked to Issue #23 (fee escalation)
74Section 15.1 — TerminationTermination & Post-TerminationTermination for cause: material breach with 60-day cure periodHighAgreedAgreedNo changeEither party may terminate upon material breach if not cured within 60 days of written noticeAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closed
75Section 15.2 — TerminationTermination & Post-TerminationTermination for insolvency/bankruptcyMediumAgreedAgreedNo changeEither party may terminate upon the other party's filing for bankruptcy, insolvency, or similar proceedings; subject to Bankruptcy Code §365 protectionsAgreedN/A — AgreedMarcus Weill / Nathaniel BowerGregory Stahl2023-01-18None — closed
76Section 14 — Dispute ResolutionDispute ResolutionForum for dispute resolution: court jurisdiction vs. binding arbitrationCriticalCritical-OpenOpenNo movement at June 30 session; remains fully openExclusive jurisdiction in the U.S. District Court for the Southern District of New York or the Commercial Division of the New York Supreme Court, New York CountyBinding arbitration under AAA Commercial Rules, seated in New York, NY, with a three-arbitrator panelNo compromise proposed yet; potentially explore hybrid: arbitration for technical/data disputes, court jurisdiction for IP ownership and injunctive reliefLeonard Cross / Wendy SchultzCarolyn Whitford / Gregory Stahl2023-06-30C&H to develop hybrid dispute resolution proposal for client reviewLinked to IP ownership disputes under Article VII; Quorum prefers court for precedential IP rulings
77Section 14 — Dispute ResolutionDispute ResolutionPre-litigation escalation procedure: executive negotiation requirement before formal proceedingsCriticalCritical-OpenOpenDiscussed at June 30 session; concept agreed but specifics unresolved pending forum resolution30-day executive escalation (GC-to-GC, then CEO-to-CEO) before either party may initiate proceedings60-day executive escalation plus mandatory mediation before arbitrationAccept executive escalation concept; duration and mediation details to follow forum agreementWendy SchultzGregory Stahl2023-06-30Draft escalation clause once forum issue is resolvedCannot finalize without agreement on forum
78Section 14 — Dispute ResolutionDispute ResolutionInjunctive relief — right to seek emergency injunctive relief without arbitration/escalation requirementCriticalCritical-OpenOpenDiscussed at June 30 session; concept agreed but procedural specifics unresolvedEither party may seek emergency injunctive relief from any court of competent jurisdiction without exhausting escalation proceduresInjunctive relief available through emergency arbitrator procedure under AAA RulesIf hybrid approach accepted, injunctive relief via court regardless of whether underlying dispute is subject to arbitrationWendy SchultzGregory Stahl2023-06-30Include in hybrid dispute resolution proposalCritical for IP protection scenarios under Article VII
79Section 15.3 — TerminationTermination & Post-TerminationReturn or destruction of raw Meridian data within 90 days of terminationHighAgreedAgreedNo change90-day period for return or destruction of raw Licensed Data; certification of destruction by Quorum officerAgreedN/A — AgreedLisa JohannsenPriya Nair / Claudia Reeves2023-01-18None — closedApplies only to raw Meridian data; Derived Data treatment is separate issue (#81–82)
80Section 15.4 — TerminationTermination & Post-TerminationPost-termination transition assistance: Meridian's obligation to provide reasonable cooperation during data migration off Meridian platformMediumOpenOpenDiscussed at June 30 session; general concept accepted; specifics under reviewMeridian provides 90-day transition assistance at no additional cost; continued data access during transition periodTransition assistance available for 60 days at Meridian's then-current professional services rates90-day transition period; first 60 days at no cost; remaining 30 days at reasonable ratesOmar SiddiquiPriya Nair2023-06-30Draft transition assistance clause
81Section 15.5 — TerminationTermination & Post-TerminationPost-termination treatment of Derived Data — whether Quorum retains, returns, or destroys Derived Data after MDLA expiration/terminationCriticalCritical-OpenOpenEscalated to CRITICAL; directly linked to Article VII resolutionQuorum retains all Derived Data in perpetuity post-termination; Derived Data is Quorum's proprietary assetAll Derived Data must be returned or destroyed within 90 days of termination, same as raw dataQuorum retains Transformed Outputs (per tiered definition) in perpetuity; Direct Derivatives subject to return/destroy within reasonable period; survival of this provision beyond terminationWendy SchultzRajesh Anand2023-06-30Resolution dependent on Article VII; draft post-termination survival provisions consistent with Derived Data compromiseDestroying Derived Data (including trained ML models and QuorumScore) would be commercially devastating to Quorum; critical path issue
82Section 15.6 — TerminationTermination & Post-TerminationSurvival of Derived Data commercialization rights post-terminationCriticalCritical-OpenOpenEscalated to CRITICAL; linked to #81All rights to commercialize Derived Data survive in perpetuityNo commercialization rights survive termination; all Derived Data rights revert or terminateSurvival rights for Transformed Outputs only; subject to ongoing compliance with de-identification standardsWendy SchultzRajesh Anand / Diane Lowell2023-06-30Draft survival clause tied to Article VII frameworkCritical for QuorumScore B2B licensing revenue continuity
83Section 16.1 — ConfidentialityConfidentiality / PublicityMutual confidentiality obligations during and after termMediumAgreedAgreedNo changeStandard mutual confidentiality with 5-year survival post-termination; carve-outs for disclosures required by law, regulation, or court orderAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closedAligns with mutual NDA (NDA-QIH-MCI-2022-001)
84Section 16.2 — PublicityConfidentiality / PublicityPublicity restrictions: no press release or public announcement without mutual written consentLowAgreedAgreedNo changeMutual consent required for any public announcement; each party may disclose relationship in SEC filings as requiredAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closed
85Conditions PrecedentCorporate / Lender ConsentsStandish National Bank lender consent under Section 7.12(b) of Amended and Restated Credit Agreement dated June 15, 2021 — $60M license exceeds $25M IP license threshold by $35M (240% of threshold)HighOpenOpenConsent request letter sent Nov. 2022; follow-up sent Feb. 2023; no response received; Philip Yardley (Standish relationship manager) indicated informal willingness but formal consent process ongoingObtain written consent from Required Lenders via Standish as Administrative AgentN/A — Standish is not a party to the MDLA negotiationN/A — consent/waiver must be obtained unilaterally by Quorum from its lenderMarcus Weill / Nathaniel BowerGregory Stahl / Carolyn Whitford2023-02-28Follow up with Philip Yardley at Standish; prepare updated description of MDLA terms for lender consent package once Article VII resolvedSee covenant analysis memo (Nov. 2022), structuring alternatives memo (Nov. 2022); draft consent request letter and waiver form prepared; $1.2B revolver facility
86Conditions PrecedentCorporate / Lender ConsentsQuorum board resolution authorizing execution of MDLAHighOpenOpenDraft resolution prepared (Harrison Kimble, Board Chair); execution deferred pending resolution of commercial termsBoard resolution to be adopted prior to closingN/AN/AMarcus WeillCarolyn WhitfordN/AFinalize board resolution once MDLA terms are settled; schedule board meetingDraft resolution, officer's certificate, and secretary's certificate templates prepared for future use
87Conditions PrecedentCorporate / Lender ConsentsMeridian board resolution authorizing execution of MDLAHighOpenOpenMeridian indicated board authorization will be sought once terms are finalizedRequire Meridian officer's certificate confirming board authorization at closingBoard authorization will be obtained; timing depends on finalization of Article VII and other open issuesN/AWendy SchultzGregory Stahl2023-06-30Confirm with KP&A that Meridian board authorization is on track
88Conditions PrecedentCorporate / Lender ConsentsRegulatory approvals or notifications — assessment of whether any state insurance regulatory filings are requiredMediumAgreedAgreedNo change; confirmed no regulatory filing requiredNo state insurance regulatory approval required for data license; confirmed by Claudia Reeves with regulatorsAgreed; no regulatory filing requiredN/A — AgreedMarcus WeillClaudia Reeves2023-01-18None — closed
89Section 10.3 — Limitation of LiabilityLimitation of LiabilitySuper-cap for data security breaches and willful misconduct: 3x annual fees ($36.9M)HighAgreedAgreedNo changeSuper-cap of 3x annual fees for data security breaches and willful misconduct; no cap for fraudAgreedN/A — AgreedWendy SchultzGregory Stahl2023-01-18None — closedBased on Yr 2–5 annual fee: $12.3M × 3 = $36.9M
90Section 8.5 — Reps & WarrantiesRepresentations & WarrantiesMeridian's data-accuracy representation — scope and qualification of Meridian's rep that Licensed Data is accurate, complete, and currentHighOpenOpenNarrowed at June 30 session but not closed; Meridian resists unqualified accuracy repMeridian represents that Licensed Data is materially accurate, complete, and current as of the date of delivery, consistent with industry standards for consumer and commercial credit bureausMeridian will represent only that it uses commercially reasonable efforts to maintain data accuracy; no representation as to completeness or currency; all data provided 'as is' except as to specified quality metrics in Technical Schedule ACompromise: Meridian represents data meets defined quality metrics in Technical Schedule A (error rates, freshness thresholds); broader 'as is' for attributes not covered by quality metricsWendy Schultz / Omar SiddiquiPriya Nair / Diane Lowell2023-06-30Finalize data-quality metrics in Technical Schedule A to serve as objective accuracy benchmarkLinked to indemnification scope (Issue #42)
91Section 17.1 — NoticesMiscellaneous / BoilerplateNotice provisions: addresses, methods of delivery, effectivenessLowAgreedAgreedNo changeNotices by email (with read receipt) and overnight courier to designated addresses; effective upon receiptAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closed
92Section 17.2–17.4Miscellaneous / BoilerplateAssignment, amendments/waivers, counterparts, severability, entire agreementLowAgreedAgreedNo changeNo assignment without consent (except to affiliate or successor by merger); amendments in writing only; electronic counterparts accepted; standard severability and entire agreement clausesAgreedN/A — AgreedOmar SiddiquiGregory Stahl2023-01-18None — closed

[sheet: Change Log]

Issue #MDLA SectionIssue Descriptionv1.0 Status (Jan 2023)v2.0 Status (Jul 2023)Change DescriptionDate of ChangeTriggering Event
8Section 1.1 — DefinitionsDefinition of 'Service Level' — uptime and performance metrics baselineOpenAgreedAgreed at June 30 session upon SLA finalization2023-06-30Third negotiation session (New York)
10Section 3.1Licensed Data Products specification (MCI Consumer Credit File, MCI CommercialView, MCI AltSignal)OpenAgreedData product specifications and Technical Schedule A finalized at June 30, 2023 session2023-06-30Third negotiation session (New York)
14Section 3.2Data delivery methods: SFTP batch and REST API specificationsOpenAgreedSFTP and API delivery specifications finalized at June 30 session2023-06-30Third negotiation session (New York)
20Section 4.6 / RiderMost favored nation pricing clauseOpenCritical-OpenEscalated: Meridian formally rejected MFN Apr. 21, 2023; CEO-to-CEO call May 15 inconclusive; Meridian board resolution Aug. 22, 2023 against MFN (influenced by Breckenridge Capital Partners and Whitmore Zanthor IPO strategy); no progress at June 30 session2023-06-30Multiple: Apr. 21 rejection, May 15 CEO call, board resolution anticipated
21Section 4.6 / RiderMeridian counter: most favored terms (SLA-only)N/ACritical-OpenNEW ISSUE: Meridian proposed SLA-only most favored terms as alternative to pricing MFN at June 30 session; Quorum views as commercially meaningless2023-06-30Third negotiation session (New York)
24Section 3.3Data format specifications: Parquet, CSV, schema versioningOpenAgreedData format and schema versioning agreed at June 30 session2023-06-30Third negotiation session (New York)
25Section 3.4Data refresh frequency and update cadenceOpenAgreedRefresh cadence agreed at June 30 session — daily for Consumer Credit File and