LinkSquares vs Workday Contract Lifecycle Management: how they compare in 2026

A platform that chose to rebuild rather than bolt on, which is the distinction this axis exists to catch. LinkAI launched 5 May 2026 as an AI native agentic architecture replacing the prior approach, and independent review material credits that specifically as rebuilding on an AI native architecture rather than attaching a chat sidebar to the existing product, noting most incumbent CLM vendors took the bolt on path. Extraction has been the core of the product since the beginning: identifying and pulling payment deadlines, governing law, liability, renewal and commercial obligation terms out of executed agreements is a model task, and the analytics layer that made the company's name is built on that extracted output, so the models generate the data the rest of the product reasons over. Held at B rather than A because the repository, workflow, approval routing and reporting infrastructure still stands without the model layer, and because the rebuild is four months old at the date of this record, so the AI native claim describes a recent architectural decision rather than a long established one. Revisit on the next pull.

The models are the engine of a core capability layered on a product that would function without them as a workflow and repository system. The vendor describes the platform as AI native and the underlying Evisort product genuinely was, but what is sold here is a full contract lifecycle platform: intake, no code workflow configuration, approval routing, signature integration, clause library, templates, dashboards and a contract repository, all of which stand without generative AI. What the models drive is substantial rather than peripheral, which is why this is not a C: OCR plus AI ingestion, extraction across roughly 30 standard terms, custom model creation, AI redlining against a playbook, and an Ask AI conversational layer. Fourth B on this axis, consistent with Ironclad and Icertis, and the note records that the AI native heritage does not change what the product is today.

The vendor tells buyers to demand the exact measurement it does not publish, which is the sharpest instance of that pattern in the pull. Its own published buyer guidance on evaluating AI contract management states that buyers should demand precision and recall benchmarks on their own documents and maintain review workflows for exceptions. That is correct advice and it is the right metric for extraction work. LinkSquares publishes no precision or recall figure of its own, for any clause type, on any corpus. Extraction accuracy is claimed as a differentiator in comparison content and quantified nowhere. Also absent: no error rate by clause type, no statement of behaviour on non standard or ambiguous language, no confidence indication on extracted values, and no evaluation methodology. The gap is consequential because extraction failures in this product are silent: a missed renewal date or auto renewal clause does not announce itself, it simply never appears in the report the legal team relies on. Checked the LinkAI page, the security page, the comparison and buyer guide material and the home page on 29 Aug 2026.

Grounding is real and documented with the architecture described in more detail than most, short of published measurement. The retrieval and generation path is stated concretely: a multifaceted engine orchestrating traditional, generative and agentic AI, including a proprietary large language model fine tuned for contracts and an orchestration layer that applies multiple models per task to maximise accuracy, with the vendor stating it enhances prompt language for custom models so users need no prompt engineering skill. Output grounds to sources a reader can open: Ask AI answers include links to source documents so users can act with confidence, and extraction ties each term to the contract it came from. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026 and located no accuracy figure, no hallucination rate, no test set, no evaluation methodology and no independent benchmark participation. The claim that multiple models are applied to maximise accuracy is an architectural assertion with no measurement attached.

The product is marketed as agentic and the oversight model is not described. LinkSquares positions itself as agentic CLM and states that the platform handles the bulk of standard contracts automatically, which is an autonomy claim with commercial substance behind it. Its own buyer guidance recommends maintaining review workflows for exceptions, so the vendor knows where the human belongs. What is not published for its own product: which contract types or value thresholds can complete without human review, what makes a contract standard enough to be handled automatically, whether an agent can send or approve a contract unattended, what confidence threshold routes an exception to a person, and what the audit record shows when an agent rather than a lawyer made the call. Marketing an agent and describing its limits are different acts and only the first has happened. Checked the home page, the LinkAI page, the comparison material and the buyer guide material on 29 Aug 2026.

Autonomy is present and the control structure around it is administrative rather than described. Real elements exist: AI redlining is described as suggesting surgical edits rather than applying them, which implies a human accepts or rejects, and advanced administration allows customised user roles and access controls. But those govern who may use the product rather than what it decides alone. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026 and located no statement of what the agentic components run unaided, no threshold at which a workflow stops or escalates to a person, no described review surface a lawyer must clear, and no statement of what the vendor commits to when an output is wrong. Notable given the platform explicitly includes agentic AI and automates routing and approval.

Customers are named, a case study carries figures, and one of those figures does not survive arithmetic. Named customers: DraftKings, TIME, ProPharma and Asurion, with more than 1,200 customers stated. Independent placement is dated and repeated: G2 Leader in contract lifecycle management for five consecutive years including the Winter 2026 Grid Report, with a stated 98 percent of users reporting the product moving in the right direction. A named case study, Softonic, reports outside counsel costs reduced by 40 percent, which is a coherent and checkable claim from a named company. Held at B rather than A on the quality of the other figures. The same case study reports NDA processing time cut by nearly 400 percent, and a reduction of more than 100 percent is not a possible quantity, so the claim is either a throughput multiple described as a reduction or an error, and either way it cannot be read as stated. A separately published 360 percent ROI over three years carries no methodology, sample or baseline. A vendor that names its customers and publishes an impossible percentage is being open and imprecise at the same time, and the record should say both.

Claims are published with the evidence base disclosed but the substance withheld. The vendor makes quantified results claims and footnotes them honestly, stating they are based on select customer stories and on average results from Workday Contract Intelligence, which is more disclosure of method than most vendors offer and is worth crediting. An attributed third party endorsement is published from a named practitioner at Harbor Global. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026 and located no named customer paired with figures and a date on these product pages, and no case study a reader could assess. The predecessor's customer names, including Microsoft, McKesson, BNY Mellon and NetApp, appear in pre acquisition material rather than in current Workday product material and were not carried across as evidence for this record.

Confidentiality is well evidenced at platform level and privilege is not addressed. Published: SOC 2 Type II, ISO 27001 and GDPR compliance on a dedicated security page, encryption of all contracts and data, and a stated commitment that customer data stays private within the platform. Independent review material describes data residency and retention controls as mature enough that a public company legal operations lead does not need to negotiate addenda, which is a practitioner assessment rather than vendor material and is treated as supporting. What is absent: any treatment of legal professional privilege or attorney work product, and any statement about the confidentiality of proprietary negotiation playbooks and clause libraries, which are the closest thing in this product to work product and which the vendor elsewhere states are isolated. The platform is used by legal, sales, procurement, finance and HR in the same instance, so the boundary between legal's own analysis and the wider business is a live question and is not described. Checked the security page, the LinkAI page, the data privacy solution page and the home page on 29 Aug 2026.

Confidentiality rests on certification claims and administrative controls without the specific commitments this axis tests. Published: responsible AI safeguards backed by ISO 42001, 27001 and 27701 certifications, the last of which is a privacy information management standard and is the nearest thing to a published privacy position, plus enterprise grade administration with customisable user roles and access controls. Searched the datasheet, the product overview pages in three regional editions and the Workday newsroom on 29 Aug 2026 and located no statement on whether customer content may be used to train models, no retention or deletion terms, no segregation model between customers or matters, and no treatment of attorney client privilege or work product. For a platform whose repository is designed to hold every executed agreement across legal, HR, finance and M and A, the training and retention questions are central and neither is answered on the surfaces reached.

Not located. The product drafts, reviews and approves contracts and is explicitly sold for use by sales, procurement, HR, marketing and finance alongside legal, so non lawyers act on machine generated contract analysis by design and the vendor describes that as a feature. Nothing published addresses the professional dimension: no statement that output is not legal advice, no guidance on when a contract should reach a lawyer, no positioning on the in house counsel's supervisory role over self service authoring by business users, and no engagement with any bar guidance. Checked the home page, the LinkAI page, the solution pages and the buyer guide material on 29 Aug 2026.

The audience is broad by design and no position on the advice line was located. The datasheet states explicitly that contract data should be accessible across legal, procurement, finance, HR, revenue operations, compliance, M and A, information security and other teams, and Ask AI is described as letting users across the enterprise ask questions and act with confidence on the answers. That is non lawyers acting on AI generated contract analysis, described as a feature. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026 and located no statement on advice versus tooling, no treatment of competence or supervision duties, and no jurisdiction limits. Consistent with the pattern across every enterprise CLM on this index.

The vendor publishes governance guidance for its customers and nothing about its own models. Its buyer guide recommends implementing quarterly AI governance reviews to monitor bias, validate accuracy and enforce compliance, and lists model governance covering audit trails, PII handling and zero retention options as things a buyer should expect from a vendor. Every one of those is advice pointed outward. For LinkAI itself the located material amounts to a claim that it is designed with enterprise grade data security and governance built in. No AI policy, no model card, no bias or fairness testing, no evaluation methodology or result, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001 despite holding ISO 27001. Same shape as FinregE, which analyses regulatory obligations for customers in structured detail and turns none of that rigour on itself, and graded the same way for consistency. Checked the LinkAI page, the security page, the buyer guide material and the comparison content on 29 Aug 2026.

UPDATED 29 Aug 2026 during the trust portal sweep; grade unchanged at A, evidence strengthened. The record already rested on accredited ISO/IEC 42001 certification, achieved as Evisort in October 2024 when it was the first contract AI provider globally to obtain one, carried forward under Workday ownership, with the certifying body identifiable as Schellman and the certification route documented through the compliance platform partner. Located during the sweep and added here: the owner publishes a NIST AI Risk Management Framework attestation, accessible from its compliance page, described as a voluntary framework for incorporating trustworthiness considerations into the design, development, use and evaluation of AI products, services and systems. That is a second, independent AI governance instrument alongside the ISO certification, and it addresses the design and evaluation lifecycle rather than the management system alone. The TRUSTe Enterprise Privacy and Data Privacy Governance Practices Certification separately names this product in scope and is benchmarked against the OECD Privacy Guidelines, GDPR, HIPAA, the APEC Privacy Framework and ISO 27001. Two certifications specific to AI, one of them accredited and one a recognised risk management framework attestation, is a stronger position than any other A on this axis except Harvey. Still not located and recorded rather than waived: published pre release testing results, a named accountable owner for model governance, and any disclosure of uneven output across matter types, parties or populations.

A real and repeated training commitment, with a carve out that has to be read carefully. The vendor states that contract data is never shared with or used to train any third party LLM providers, that contract data and proprietary playbooks are completely isolated and never used to train public AI models, and that data stays completely private within the LinkSquares platform. That answers the dominant risk for a CLM, which is customer contract text reaching an external model provider, and it answers it in plain words rather than by implication. Held at B rather than A because of what the wording leaves open. Both formulations are scoped to third party and public models. Neither states that LinkSquares does not use customer contract data to train or tune its own models inside its own platform, and stays completely private within the LinkSquares platform is consistent with internal training rather than exclusive of it. No retention position for AI processed content is published either, and the vendor's own buyer guide lists zero retention options as something a buyer should demand without stating whether this product offers one. A well drafted sentence that stops precisely where the harder commitment would begin.

CORRECTED 29 Aug 2026 during the trust portal sweep. Previously graded C because certification breadth stood in for published operational detail, with retention, subprocessors and incident practice all unlocated. The owner's trust estate, not reached in the original pass, supplies most of that. Published: rigorous screening of subprocessors, stated as a standing practice; encryption of database and transaction log backups; TLS securing network traffic against passive eavesdropping and active tampering; ISO 27017 for cloud specific security controls and ISO 27018 for processing of personal data in the cloud, both with accessible certificates; SOC 2 scoped to cover any system containing customer data and audited annually by an independent third party, with the report available to customers and prospects; SOC 1 covering production systems and financial reporting controls; and an EU Cloud Code of Conduct adherence report. Backup retention is acknowledged with the vendor stating the period varies by system, which is disclosure without a figure. Not located as of 29 Aug 2026, and why this is B rather than A: a named subprocessor list as distinct from a screening commitment, a stated retention period or deletion control for contracts, prompts and Ask AI outputs, and an incident or breach notification practice.

No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy where an extraction is wrong, a clause is missed, or an agentic action progresses a contract that should have been escalated. The exposure is concrete: the platform is stated to handle the bulk of standard contracts automatically, and a missed auto renewal or liability cap in an executed agreement is a loss the customer discovers later with no published vendor position on it. Checked the home page, the LinkAI page, the security page and the site navigation on 29 Aug 2026. Enterprise agreements govern this and are not public, and no public terms page was located in this pass.

Searched the datasheet, the product overview pages in three regional editions and the Workday newsroom on 29 Aug 2026. No published indemnity, liability cap, carve out, warranty on output or insurance position was located, and no customer agreement was located on the product surfaces reached. Recorded as a pure absence on those surfaces. Rebuttable, and more likely to be so here than for most records: an enterprise vendor of this size will have published master agreement terms somewhere, and this record was built from product marketing material rather than from a contracts or legal centre.

Integrations are named, numerous and aimed at where contract work actually happens. Named: Microsoft Word, Google Docs, Microsoft 365, Salesforce, Slack, DocuSign and HubSpot, with the vendor stating that clause libraries and playbooks are accessible from inside the drafting environment so users do not switch tabs or upload files. Word and Google Docs native drafting is the integration that matters most for this product class and it is present, and the CRM and e-signature connections cover the pre signature path end to end. Held at B rather than A on a gap identified in independent review material and not contradicted by anything located: no generally available developer facing API, which limits a customer's ability to move contract data into systems the vendor has not built a connector for. No document management system such as iManage or NetDocuments is named either. Checked the LinkAI page, the comparison material, the home page and independent review material on 29 Aug 2026.

Real integrations exist, are named individually, and span the systems a contract actually moves through. Named: Docusign and Adobe Sign for signature, Salesforce for revenue systems, Box and SharePoint plus shared drives for storage, and Microsoft Word 365 for drafting. The vendor states a robust API and productised integrations facilitate system connections, alongside self service configuration and enterprise grade administration controls. Syncing across existing repositories rather than requiring migration into a new one is stated as a design goal and is a real integration position. Not located as of 29 Aug 2026: legal specific document management connectors such as iManage or NetDocuments, an integrations index page, and per integration documentation of what moves in which direction and what an administrator configures.

Residency is described in third party assessment and not in vendor material located here. Independent review material states that data residency and retention controls are mature enough that a public company legal operations lead does not have to negotiate addenda, which is a specific practitioner claim about the existence and quality of residency controls. No vendor page located in this pass names a hosting provider, enumerates regions, states a residency commitment, or describes single tenant or private deployment options. Source basis recorded as Third Party Estimated on that footing rather than credited as vendor disclosure. Correction candidate: the dedicated security page carries certification statements and may carry residency detail below the summary content read here.

CORRECTED 29 Aug 2026 during the trust portal sweep. Previously graded D on the finding that nothing at all was located on the deployment model, including no tenancy statement. That was wrong: the owner's security documentation states plainly that the platform is a multi tenant SaaS application and describes multi tenancy as a key feature enabling multiple customers to share one physical instance of the service. So the tenancy model is published, and it is published honestly rather than obscured, which several records on this index do not manage. Recovery point objectives and encrypted backups are also described. What remains unlocated, and why this is C rather than higher: no named regions, no customer selectable data residency for this product, no statement of where processing happens as distinct from where data is stored, and no confirmation of which regional infrastructure serves the contract products specifically. Regional site editions and an EU Cloud Code of Conduct adherence report indicate European operations without stating a residency option. Rebuttable further by any published region list.

Two named certifications on a dedicated security page, published openly rather than gated. SOC 2 Type II and ISO 27001 are both stated, alongside GDPR compliance and encryption of all contracts and data, on a page whose purpose is security rather than as a line in marketing copy. Both certifications are corroborated across independent review material, which describes them as the two certifications that clear most enterprise procurement gates. Publishing the status openly with no login is better than the request flow tier and is the reason this sits at the top of B. Held below A on three absences: no auditing firm is named for either certification, no certificate date, examination period or expiry is published so currency cannot be established, and no trust centre or documentation request route was located, so a reviewer wanting the report itself has no stated path. Consistent with Regology and Onspring at B, and below Lexis+ AI and Exterro at A, which add currency, scope detail and a verifiable route.

CORRECTED 29 Aug 2026 during the trust portal sweep. Previously graded B because no coverage period, report request route or trust portal was located from the product marketing surfaces. The owner operates a full trust estate that was not reached, and it names this product explicitly. Published and product scoped: a SOC 3 report for Workday Contract Intelligence and Contract Lifecycle Management, powered by Evisort AI, accessible directly. A SOC 3 is a public summary report rather than a gated attestation, so a buyer can read an auditor's conclusion about this specific product without an agreement or an access request, which almost nothing else on this index offers. The TRUSTe Enterprise Privacy and Data Privacy Governance Practices Certification names Workday Contract Lifecycle Management, powered by Evisort AI, in its stated scope, with TRUSTe acting as third party verification agent under the Data Privacy Framework. At owner level: consolidated ISO 27001 and ISO 27017 certificates with accessible certificates, ISO 27018, SOC 1 and SOC 2 reports with the SOC 2 scope stated as covering any Workday system containing customer data and audited annually by an independent third party, and EU Cloud Code of Conduct adherence with a published adherence report. Alongside the accredited ISO 42001 recorded on the governance row, that is a named, scoped, dated and partly public certification estate. Short of nothing material; the auditing firm for the SOC reports was not located.

The category is acknowledged and no party is named, and the acknowledgement is inadvertent. By committing that contract data is never shared with third party LLM providers, the vendor confirms that such providers exist in the architecture, since a commitment not to share with them is only meaningful if they are there. Nothing names any of them: no provider, model family or version, no subprocessor list, and no statement of what runs where between the vendor's own infrastructure and any external model. For a product now rebuilt on an agentic architecture, the identity of the underlying models is a question an enterprise security review asks directly. Compare Onspring at B, the only record on this index naming its provider outright. Checked the LinkAI page, the security page, the comparison material and the home page on 29 Aug 2026.

The architecture is described with real specificity and the third party components are not named. Published: a proprietary large language model fine tuned for contracts, described in predecessor material as the first large language model built specifically for contracts, plus an orchestration layer that applies multiple large language models to maximise accuracy for particular tasks, and a stated combination of traditional, generative and agentic techniques. A buyer therefore knows the vendor owns a model layer and that other models are also invoked. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026 and located no identification of which external models or providers sit in that orchestration layer, no statement of where they run, no subprocessor list, and no commitment to notify customers when the supply chain changes. Disclosing that multiple third party models are used without naming any of them leaves the customer's exposure undefined.

No pricing published at any level. No price, no range, no tier structure and no unit of charge, and the vendor's own buyer guidance tells readers to compare user based, usage based and record based pricing models without disclosing which of those it uses itself. Third party reconstruction places the median around $31,000 per year with a starter tier near $10,000 and enterprise above $75,000, which is independent estimation rather than disclosure and is recorded as context rather than credited. That estimated range is material to a buyer because it places the product outside the reach of small teams, which is exactly the kind of fit judgement published pricing would let a reader make for themselves. Checked the home page, the LinkAI page, the pricing navigation and independent review material on 29 Aug 2026.

Checked the datasheet, the product overview pages in three regional editions and the Workday newsroom on 29 Aug 2026. No pricing page was located, no rate is published, no unit of charge is stated and no tier structure appears. Every commercial path located terminates in a contact or demo request. Third party analysis states pricing is quote based under Workday's enterprise model, driven by contract volume, users, modules, integrations and whether the customer bundles with other Workday products, with no public price list and no free trial, which confirms the absence rather than filling it. Also recorded from third party analysis: the product is now negotiated as part of the broader Workday platform rather than as an independent purchase, so a buyer cannot price it standalone.

Coverage is stated in the terms that matter for contract work, which is clause and lifecycle scope rather than jurisdictions. Named clause and term coverage: payment deadlines, governing law provisions, liability clauses, renewal language and commercial obligations, with batch analysis across large legacy portfolios for M&A due diligence and repository audit. Lifecycle coverage runs pre signature through post signature in one platform, and the user set extends beyond legal to sales, procurement, finance, HR and marketing, which is honest about who actually touches contracts. More than 1,200 customers across the in house market. Held at B rather than A because coverage is not characterised where it would matter to a buyer: no statement of which contract types or languages are supported, no jurisdictional scope for governing law extraction despite that being a named capability, and no indication of extraction depth by agreement type. Independent review also identifies the scope boundary honestly, noting no primary law research capability, which is correct and is a category fact rather than a gap.

Segment coverage is described with substance and enumerated by function rather than claimed broadly. Nine business functions are named as intended users: legal, procurement, finance, HR, revenue operations, compliance, M and A, information security and others. Practice scope is contract lifecycle end to end from intake through storage, with the extraction schema published in full, roughly 30 named standard terms from assignment and change of control through liability cap, non compete, renewal type and termination for convenience, plus custom model creation for any other term. Publishing the actual extraction schema is rare on this index and tells a buyer precisely what the product knows how to find. Not located as of 29 Aug 2026: any statement of organisation size the platform is not built for, industry segmentation, and any jurisdictional or language coverage statement beyond noting that the ingestion layer recognises contract languages.

Policy never, and the scope of the never is the finding. READ THE QUALIFIER: the quoted commitment is to public AI models, and the parallel statement on the LinkAI page is that contract data is never shared with or used to train any third party LLM providers. Both are scoped to models outside the vendor. Neither states that LinkSquares does not use customer contract data to train or tune its own models, and the accompanying phrase that data stays completely private within the LinkSquares platform is consistent with internal training rather than exclusive of it. Recorded at policy never because a real and repeated commitment exists and covers the dominant risk for a CLM, which is contract text reaching an external provider, and erasing it as silent would misdescribe the record. Recorded as policy rather than contractual because it appears on product and comparison pages rather than in terms or a data processing agreement. A carefully drafted sentence that stops precisely where the harder commitment would begin. Checked the LinkAI page, the security page, the comparison material and the home page on 29 Aug 2026.

Searched the product datasheet, the contract management overview pages in three regional editions and the Workday newsroom on 29 Aug 2026. No located material states whether customer content may be used to train models, either way. Recorded as silent under the rule that a value is never inferred from the absence of a contradiction, and specifically not inferred from the ISO 42001 certification, which evidences that an AI management system exists rather than what its training position is. The question has weight here because the vendor states it operates a proprietary large language model fine tuned for contracts and an orchestration layer applying multiple models, so a customer would want to know what the fine tuning draws on. Rebuttable against a corporate trust or privacy centre this record did not reach.

Not addressed, and the vendor's own buyer guidance shows it knows the question. That guidance lists zero retention options among the things a buyer should expect from an AI contract management vendor, alongside audit trails and PII handling. No statement was located as to whether LinkSquares itself offers a zero retention option, what its default retention period is for AI processed contract content or extracted output, or whether any of it is customer configurable. Advising buyers to demand a control without stating whether you provide it is the pattern this record repeats across three axes. Checked the buyer guide material, the LinkAI page, the security page and the data privacy solution page on 29 Aug 2026.

Searched the product datasheet, the contract management overview pages in three regional editions and the Workday newsroom on 29 Aug 2026. No public material on these surfaces states how long contracts, prompts, Ask AI conversations or generated outputs are retained, whether a customer controls the window, or whether deletion is available. The platform is a system of record designed to hold every executed agreement and to sync continuously with existing repositories, so retention is central to what is being bought rather than incidental to it. Rebuttable against a corporate trust centre this record did not reach.

Not addressed for this product. The vendor's buyer guidance names MFA and SSO among the controls a buyer should expect, and independent material notes role based access controls as standard across enterprise CLM platforms generally, but neither is a statement about what LinkSquares implements. The structural question is live: the platform is sold for use by legal, sales, procurement, finance, HR and marketing in a single instance holding the whole contract estate, and nothing published describes what separates legal's own analysis, playbooks and risk annotations from the business users working in the same system. No document management system integration exists to inherit permissions from. Checked the security page, the LinkAI page, the solution pages and the home page on 29 Aug 2026.

Segregation is asserted through an administration feature with no published detail on how it is enforced. The datasheet states advanced administration allows customisation of user roles and access controls for enterprise grade provisioning and security. That is an access model claimed at feature level: no roles are described, no scoping rules are given, and nothing states whether the Ask AI layer and search respect those controls per user at query time, which matters because the product's stated value is making contract data accessible across nine business functions. No document management integration was located whose permissions could be inherited. Noted for context: the buyer is a corporate function rather than a firm carrying conflicts obligations, so matter level walls in the professional sense are less directly applicable than for a firm facing product.

Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The dedicated security page states SOC 2 Type II, ISO 27001, GDPR compliance and encryption and does not reach third party requests. Checked the security page, the data privacy solution page, the home page and the site navigation on 29 Aug 2026.

Searched the product datasheet, the contract management overview pages in three regional editions and the Workday newsroom on 29 Aug 2026, and no published customer agreement or data processing agreement was reached on these surfaces. No clause committing to notify a customer of a government or law enforcement request for their data was located, and no transparency report was located from the product pages. Rebuttable against a corporate trust or legal centre this record did not reach.

Not addressed, and inapplicable in the usual sense. The product operates on the customer's own executed and draft agreements rather than on published law, so there is no external legal corpus to name, license or date. Recorded rather than omitted because the underlying question has a live form here that is unanswered: what the extraction models were trained on. Extraction of governing law, liability and renewal terms across contract types implies a substantial training corpus of agreements, and nothing published states whether that corpus was licensed, synthetic, publicly sourced, or built from customer contracts. The commitment not to train third party models on customer data speaks to future flow and not to what already built the extraction capability. Checked the LinkAI page, the security page and the comparison material on 29 Aug 2026.

No primary law corpus is identified because the product does not hold one. Retrieval runs against the customer's own contracts, synced from shared drives, cloud repositories such as Box and SharePoint, and enterprise systems such as Salesforce, so the corpus is the customer's own agreements and its provenance is theirs. Predecessor material described the proprietary contract model as trained on a corpus of public contracts and legal documents, which would be the nearest thing to a vendor corpus, but that appears in pre acquisition third party material rather than in current vendor material and no scale figure, source or licence basis was located for it. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026. Same architectural shape as Ironclad, Icertis and Definely, where the absence describes the product design rather than a disclosure failure.

Not addressed, and inapplicable on the facts. LinkSquares analyses contracts rather than researching law and produces no citation to legal authority, so a citator would have nothing to check. Independent review material identifies the same scope boundary directly, noting the absence of primary law research on case law, statutes and regulations, which is a category fact rather than a defect. Recorded as a scope fact so a reader does not mistake an inapplicable row for a disclosure failure, consistent with the treatment of this row on Legal Tracker, Mitratech, TrialView and Exterro. Checked the LinkAI page and the comparison material on 29 Aug 2026.

Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026. No material was located addressing whether authority carries a treatment signal or whether subsequent history is checked, and no commercial citator licence was located. Noted for context: this is a contract lifecycle platform grounded in the customer's own agreements with no case law research surface, so a citator is outside its design entirely. The extraction schema does include governing law as a captured term, which identifies which law applies to a contract rather than whether any authority remains good law, and the two were not conflated.

Not addressed. Nothing published describes an explicit no answer path, abstention behaviour or confidence signal for extraction, review or the agentic layer. The vendor's own buyer guidance recommends maintaining review workflows for exceptions, which implies exceptions are identifiable, and nothing states how LinkAI identifies one: whether a low confidence extraction is flagged, left blank, or filled with a best guess that reads identically to a confident one. For a product whose output is a structured field in a report, an unflagged wrong value and an unflagged missing value are both invisible to the person relying on it. Checked the LinkAI page, the buyer guide material, the comparison content and the home page on 29 Aug 2026.

Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026. No published material describes what the product does when it cannot ground an answer, and no explicit no answer path or confidence signal exposed to the user was located. The vendor states Ask AI returns clear, reasoned answers with links to sources, which describes what a successful answer looks like rather than what happens when the contracts do not support one. The datasheet also publishes a text quality field among extracted terms, which flags poor source scans rather than low confidence in an answer, and the two were not conflated.

None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction, contract dispute and extraction error terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. The product generates no citations to legal authority, so the classic fabricated case failure mode does not arise, and the analogous risk would be a missed or misextracted contract term surfacing in a commercial dispute. Recorded as a statement about what this search found, not as a clearance.

No court order, opinion or disciplinary record naming this product or its Evisort predecessor has been located as of 29 Aug 2026. Instrument searched: the AI Hallucination Cases database maintained by Damien Charlotin, which tracks court decisions worldwide involving AI generated hallucinated content and records the AI tool implicated where it is known. Also checked published 2026 sanctions summaries and secondary sanctions trackers. The entries located name filers, and in some rows other products, rather than this one. This is a statement about the public record on the date shown and not a clearance. Note that this is a contract lifecycle platform with no case law research surface, so its output is very unlikely to reach a court filing as cited authority.

Not addressed. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located, despite the vendor publishing a substantial library of in house counsel guidance covering AI adoption, governance reviews, procurement and change management. The omission is notable given that library's scope: it advises legal departments on how to govern AI adoption without engaging the professional rules those departments' lawyers work under. Checked the buyer guide material, the in house insights library, the LinkAI page and the home page on 29 Aug 2026.

Searched the datasheet, the product overview pages in three regional editions and the Workday newsroom on 29 Aug 2026. No engagement with any named ethics opinion or bar guidance was located, including ABA Formal Opinion 512 and state bar guidance. The vendor publishes substantial material on responsible AI framed around its ISO 42001 certification, which addresses how its own AI management system is governed rather than the professional responsibility obligations that bind the lawyers among its nine stated user functions.

Savings claims only, including one that cannot be read as stated. Published: a named customer, Softonic, reducing outside counsel costs by 40 percent, which is coherent and attributable, alongside a stated 360 percent ROI over three years and contract review times reduced by up to 400 percent. A reduction of more than 100 percent is not a possible quantity, so the last figure is either a throughput multiple presented as a reduction or an error, and it is recorded here as unreadable rather than credited. Nothing appears on the client side of the equation: no position on billing for AI assisted contract work, and no record a department could produce showing what portion of a review was machine performed. Checked the LinkAI page, the comparison material and the case study content on 29 Aug 2026.

Savings are claimed with the evidence base disclosed and nothing published on the client's side of the equation. Published claims cover dramatically faster contract turnaround at lower cost and quantified results footnoted as based on select customer stories and on average results from Workday Contract Intelligence, which is more honest about the basis than most savings claims on this index. Searched the datasheet, the product overview pages and the Workday newsroom on 29 Aug 2026 and located no per matter record of AI assisted work intended for fee purposes, and no guidance on billing, fee or client disclosure treatment. Noted for context: the buyer is an in house or business function that does not bill a client by the hour, so this signal reads as enterprise cost rather than billable time for this segment.

Not addressed, with one genuine open element. The dedicated security page publishes SOC 2 Type II, ISO 27001 and GDPR compliance without a login, so a department has something citable immediately, and open publication is better than a gated summary. Everything else a forwardable pack needs is missing: no subprocessor list, no named model provider, no data processing agreement, no trust centre and no documentation request route were located, so there is no path to the underlying reports and no way to answer a client's question about which third parties process its contract data. Recorded as not addressed because a certification summary is not a disclosure pack and no request route exists. Checked the security page, the data privacy solution page, the LinkAI page and the site navigation on 29 Aug 2026.

Searched the datasheet, the product overview pages in three regional editions and the Workday newsroom on 29 Aug 2026. Named certifications are published and are genuinely useful diligence material, ISO 42001, 27001 and 27701, with the AI certification accredited and its certifying body identifiable. But the artifacts this signal specifically turns on were not located on these surfaces: no subprocessor list, no statement naming which model providers see customer content, which matters here because the vendor discloses that an orchestration layer applies multiple large language models without naming any, no published data processing agreement, and no client facing consent or notification pack. Rebuttable against a corporate trust centre this record did not reach.

Not addressed, and close to inapplicable in the form this signal usually takes. LinkSquares produces contract analysis and executed agreement data rather than work product filed with a court, so the model used, sources retrieved and human verification export a judicial standing order asks for has no natural object. Recorded as a scope fact rather than omitted. Worth noting the adjacent gap that does apply: nothing indicates the platform records which contract fields were AI extracted as opposed to human entered, or whether a person confirmed an extracted value, so a party relying on repository data in a dispute could not evidence how any given term got into the record. Checked the LinkAI page, the comparison material and the home page on 29 Aug 2026.

Some elements of a record are available as a by product of the product's design. Ask AI answers carry links to the source documents they rest on, extraction ties each captured term back to the contract it came from, and workflow automation records routing and approvals per contract, so what was relied on is traceable. Two elements are missing: no per document export covering model used, sources retrieved and human verification together was located, and the model used could not be stated in any case since the orchestration layer applies multiple unnamed models per task. Noted for context: this is a contracting platform rather than a litigation product, so a judicial AI disclosure order is unlikely to reach its output.