Ironclad
Enterprise contract lifecycle management platform covering intake, contract creation, no code workflow automation, approvals, negotiation, signature, repository and analytics, sold to in house legal, legal operations, procurement, sales and IT. AI is embedded across the platform rather than sold separately: AI Playbooks drive precise redlining with each play tied to a clause, and Jurist is an agentic AI contract partner running a family of named agents including Manager, Drafting, Editing, Review, Research, Intake and Redlining, alongside Conversational Search over the contract repository. The vendor states Jurist uses proprietary legal AI models with legal engineered prompts. Positions itself as the leading AI CLM and publishes deep integrations including Salesforce and Coupa.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
The models are the engine of a core capability, layered on a product that would function without them as a workflow system. Ironclad is a contract lifecycle management platform: intake, no code Workflow Designer, approvals, routing, signature, repository, analytics and integrations all predate and stand without generative AI, and the vendor sells that workflow layer as its foundation. What the models drive is real and central rather than peripheral, which is why this is not a C: AI Playbooks with each play tied to a clause do the redlining, and Jurist runs a named family of agents for drafting, editing, review, research, intake and redlining under a Manager Agent, with Conversational Search over the repository. Second B on this axis after Definely, and for the same structural reason: an established product with a substantial AI layer rather than an AI native one.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
Accuracy is asserted and the grounding behind it is not documented. Vendor material claims precision redlining, advanced AI and proprietary legal AI models trained on legal terminology with legal engineered prompts. Real structure exists in the AI Playbooks mechanism, where each play is tied to a clause and the system proposes varying degrees of revision to match preferred terms with minimal language change, so output is anchored to a customer authored standard a reviewer can check. What is missing is everything this axis measures: searched the site, the Ironclad AI and Jurist product pages, the security page and the support documentation via search on 29 Aug 2026 and located no accuracy figure, no hallucination rate, no test set, no evaluation, and no description of the retrieval method or how output grounds to a source a reader can open.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
A written commitment that the models work alongside a supervising human, with real and specific review surfaces, short of published thresholds. The vendor states human in the loop governance ensures every agent works transparently, is auditable and controllable, and says plainly that the customer is in charge, with governed and auditable AI review frameworks the customer can review, override and continuously govern across teams and contract types. The control surface is administrative as well as rhetorical: playbook permissions let administrators configure which users and groups may view, create and edit playbooks, and a Manager Agent routes tasks across the agent family so orchestration is visible. Vendor material states the agents automate repetitive lower risk work while strategic negotiation and nuanced risk assessment stay with the lawyer, which is a stated allocation. Not located as of 29 Aug 2026: the threshold at which an agent stops or escalates, and what the vendor commits to when an output is wrong.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Real deployment evidence with substance, short of dated attribution and method. A named customer carries a figure: NEXT Insurance is published as giving legal operations 50 percent of its time back with Jurist. Attributed customer quotes carry before and after numbers, including a first pass redline moving from 30 minutes to a couple of hours down to a solid first draft in minutes, and an MNDA review or custom order form clause drafting moving from an hour to a day down to minutes or seconds. A customer stories section is published. Not located as of 29 Aug 2026: a dated case study with a stated method a reader could assess, and the identity of the speakers behind several of the quoted figures.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
Substantive published commitments, and unusually the vendor addresses its own training use directly rather than only its providers. Published: strict do not train and zero data retention policies enforced with external LLM providers; any customer data used to train Ironclad's own models is anonymised and aggregated before use; output generated for other customers by models trained on a customer's data will never include that customer's data; and training data protection is stated as covered by the same security standards as the rest of the platform. Certification covers the privacy trust category under SOC 2 and includes ISO 27701 for privacy information management. Two gaps hold this off an A. Attorney client privilege and work product handling is not addressed directly in located material. Segregation between customers, users or matters is not documented on the pages checked.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point.
The intended audience is broad by design and no position on the advice line was located. Dedicated pages address legal operations and general counsel alongside procurement and IT, and vendor material describes the platform as serving business teams that touch contracts, with the AI proposing redlines and drafting negotiation ready revisions for those users. Searched the site, the product and persona pages, the security page and the support documentation via search on 29 Aug 2026 and located no statement on advice versus tooling, no treatment of competence or supervision duties, and no jurisdiction limits. The human in the loop governance language is a control statement rather than a professional responsibility position, and the two are not the same thing.
AI Governance and Bias Disclosure
Published governance over model behaviour: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
A published governance framework with real substance, short of testing results, a named owner and any bias disclosure. What exists is a described mechanism rather than a principles page: governed and auditable AI review frameworks, human in the loop governance stated as ensuring every agent is transparent, auditable and controllable, customer ability to review, override and continuously govern agent behaviour across teams and contract types, and administrator configurable permissions determining who may view, create and edit the playbooks that drive AI behaviour. A chief technology officer is named publicly as owning the AI roadmap. Not located as of 29 Aug 2026: an AI management certification such as ISO 42001, published pre release testing results, a named accountable owner for model governance as distinct from the technology function, and anything on uneven output across matter types, parties or populations.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
Substantive published policy covering most of the ground. Certification breadth is the strongest element and is stated precisely: routine audits producing third party SOC 1 and SOC 2 Type II reports certified against multiple trust categories named as security, availability, confidentiality and privacy, plus ISO 27001, 27701, 27017 and 27018, a dedicated GDPR programme, and Cloud Security Alliance membership with Trusted Cloud Provider status. Data centre operations run on public cloud providers the vendor states are themselves certified under SOC 2, ISO 27001 and PCI DSS, across multiple regions. Zero data retention is enforced at the external model layer. Not located as of 29 Aug 2026: a stated retention period or deletion control for customer contracts and prompts in Ironclad's own systems, a named subprocessor list, and an incident or breach notification practice.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
Searched the site navigation, the security page, the Ironclad AI and Jurist product pages, the support documentation and the article library via search on 29 Aug 2026. No published indemnity, liability cap, carve out, warranty on output or insurance position was located, and no customer agreement or master services agreement was located as published on the property. Recorded as a pure absence on the surfaces checked. Rebuttable with a single link to a published agreement, which for an enterprise platform of this size may well exist somewhere not surfaced by the searches run.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
Real integrations exist and are documented, and the vendor treats them as a primary differentiator. Named specifically: Salesforce, described by the vendor as the number one Salesforce integration in the market, and Coupa, with a dedicated integrations page and a stated claim of the deepest integrations in the market. The workflow layer is itself integration: teams create, manage and collaborate on contracts from inside the systems they already use rather than switching into the CLM. Orientation is toward enterprise commercial systems rather than legal document management, which fits a CLM buyer. Not located as of 29 Aug 2026: legal specific document management connectors such as iManage or NetDocuments, and per integration documentation describing what moves in which direction and what an administrator configures.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Residency is offered without the processing location being addressed, which is the B band. The vendor states it leverages multiple data centre regions from its cloud providers specifically to meet data residency requirements, which is a real published residency position rather than a geography footnote. What is missing: the cloud providers are described only as public cloud vendors and are not named, no available regions are listed, no customer selectable region is stated, no tenancy model is given, and no statement separates where processing happens from where data is stored. Checked the security page and the platform pages via search on 29 Aug 2026.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
Certification is real and stated with correct scope language, short of accessible evidence. The vendor names SOC 1 and SOC 2 Type II from routine third party audits and, unusually, names the trust categories certified against: security, availability, confidentiality and privacy. ISO 27001, 27701, 27017 and 27018 are all named, which is a broader ISO set than most of this index carries, and Cloud Security Alliance membership with Trusted Cloud Provider status is stated. Supply chain assurance is addressed by stating that the underlying cloud vendors are themselves SOC 2, ISO 27001 and PCI DSS certified. What was not located as of 29 Aug 2026 is the evidence route: no audit coverage period, no report date, no named auditing firm, and no trust portal or published request flow for obtaining the reports.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
The vendor refers to models without identifying what sits underneath. Two layers are acknowledged and the distinction between them is drawn clearly, which is more than most manage: proprietary legal AI models built by Ironclad with legal engineered prompts, and external LLM providers bound by do not train and zero data retention terms. That tells a buyer the shape of the chain and the commercial terms binding it. What it does not tell them is who is in it. Searched the site, the Ironclad AI and Jurist pages, the security page and the article library via search on 29 Aug 2026 and located no named external model provider, no statement of where models run, no subprocessor list, and no commitment to notify customers when the supply chain changes.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
Checked the site navigation, the platform and product pages, the persona pages and the security page via search on 29 Aug 2026. No pricing page was located on the property, no rate is published, no unit of charge is stated and no tier structure appears. Every commercial path located terminates in a demo request. No free trial or self serve entry point was located. Consistent with third party coverage describing implementation cost as dependent on the scope of the CLM deployment rather than on a published rate.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Segment coverage is described with substance, short of the boundaries. Four buyer personas carry their own published positioning: legal operations, general counsel, procurement and IT, and the vendor addresses business teams beyond legal that touch contracts. Enterprise class and global business teams are stated as the target, and at least one industry, manufacturing, carries dedicated positioning around leakage and contract performance. Practice scope is clear and consistent throughout: contracting end to end from intake to post signature, with no claim to litigation or research capability. Not located as of 29 Aug 2026: a statement of which organisation sizes or contract types the platform is not built for, and an enumerated industry or practice area list comparable to the strongest records on this index.
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
Training occurs only where the customer has affirmatively enabled it.
The clearest opt in on this signal in the index, and the vendor argues for it openly rather than burying it. Published: customers may opt into allowing Ironclad to train its own models on their contracting data; any customer data so used is anonymised and aggregated before use; output generated for other customers by models trained on that data will never include the contributing customer's data; and the customer stays in control with data kept confidential. Separately and distinctly, strict do not train and zero data retention policies are enforced with external LLM providers, so the third party layer is prohibited while the vendor's own layer is permitted with consent. Recorded at opt in because training occurs only where the customer has affirmatively enabled it. What was not located as of 29 Aug 2026 is where the opt in is exercised, whether it sits in the agreement or a product setting, and whether it can be withdrawn.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Retention is acknowledged in public materials with no stated period.
Retention is answered at the external model layer and unaddressed for the platform itself. The vendor states it enforces zero data retention with external LLM providers, so prompts and completions are not persisted by those providers. Searched the security page, the platform pages, the article library and the support documentation via search on 29 Aug 2026 and located no retention period for contracts, prompts or outputs held in Ironclad's own repository, no customer control over that window, and no deletion commitment. That gap is material here because the product is a system of record designed to hold every executed agreement indefinitely, so the retention question is the core of what the customer is buying.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
The product maintains its own permission model, documented, requiring the firm to keep it aligned.
The product maintains its own documented permission model rather than inheriting one from a document management system. Published support documentation states that administrators can configure Ironclad users and groups to permit or restrict which users may view, create and edit AI Playbooks, so the standards driving AI behaviour are themselves access controlled, and the workflow layer routes and assigns contracts across named reviewers. That is a documented internal permission model. What was not located as of 29 Aug 2026 is segregation of the contract repository itself between users or matters, any ethical wall concept, and any legal document management integration whose permissions retrieval could inherit at query time. Noted for context: the buyer here is an in house or business team rather than a firm carrying conflicts obligations, so the question reads differently than it would for a firm facing product.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No located term or policy addresses third party requests for customer data.
Searched the security page, the site navigation, the article library and the support documentation via search on 29 Aug 2026. 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. No published customer agreement or data processing agreement was located on the property either, so the search covered the public pages rather than the contract documents.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
No primary law corpus is identified because the product does not hold one. Retrieval runs against the customer's own contract repository and their own AI Playbooks, and the vendor's proprietary models are described as trained on legal terminology and contract management architecture with legal engineered prompts, plus, where customers opt in, anonymised and aggregated customer contracting data. That last element is the closest thing to a vendor corpus and its provenance is disclosed in principle, being customer contributed under consent, though no scale figure, licence basis or update cadence is published for it. Searched the site, the Ironclad AI page and the article library on 29 Aug 2026.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
Searched the site, the product pages and the support documentation via search 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 playbooks and repository, with no case law research surface, so a citator is outside its design entirely.
Refusal and Uncertainty Behaviour
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
Searched the site, the Ironclad AI and Jurist pages, the agent launch material and the support documentation via search 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 Review Agent is documented as identifying missing clauses and compliance gaps, which is flagging what is absent from a contract rather than the system declining to answer, and the two were not conflated.
Fabricated Citation Record
Does a public court record exist involving output from this product?
No court order, opinion or disciplinary record naming this product has been located as of the date shown. This is a statement about the public record, not a finding about the product.
No court order, opinion or disciplinary record naming this product 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 product with no case law research surface, so its output is very unlikely to reach a court filing as cited authority.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
Searched the site, the article library, the persona pages and the community and resources sections via search 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 AI governance, auditability and human in the loop control, which addresses how its own system is controlled rather than the professional responsibility obligations its legal buyers are bound by.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure.
Savings are claimed and quantified with nothing published on the client's side of the equation. Published figures include a named customer recovering 50 percent of legal operations time, first pass redlines moving from up to a couple of hours down to minutes, and MNDA review moving from up to a day down to minutes or seconds, alongside framing about scaling review without adding headcount. Searched the site, the product pages, the article library and the support documentation via search 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 team that does not bill a client by the hour, so this signal reads differently for this segment.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
No located public material supports a client side disclosure obligation.
Substantial certification material is published openly, including SOC 1 and SOC 2 Type II with the trust categories named, ISO 27001, 27701, 27017 and 27018, a GDPR programme and Cloud Security Alliance Trusted Cloud Provider status, all reachable without a sales conversation. But the artifacts this signal turns on were not located as of 29 Aug 2026: no subprocessor list, no statement naming which model providers see customer content, no published data processing agreement, and no client facing consent or notification pack. The vendor states its external LLM providers are bound by do not train and zero data retention terms without naming them, which is a statement about the terms rather than a disclosure of the chain. Recorded as not addressed because no list exists to point to.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Some elements of the record are available, short of a document level export.
Some elements of a record are available and the auditability language is more specific than most. The vendor publishes governed and auditable AI review frameworks with human in the loop review, stating customers get transparent auditable AI behaviour they can review, override and continuously govern across teams and contract types, and the workflow layer records routing, assignment and approvals per contract. Two elements are missing: no per document export covering model used, sources retrieved and human verification together was located, and no model is named anywhere in published material so the model used could not be stated. 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.