Docusign CLM vs eBrevia: how they compare in 2026
Docusign CLM and eBrevia both organize contract information and support review, but the work that drives their workflows differs. Docusign CLM emphasizes agreement generation, conditional routing, collaboration, and movement through the contract lifecycle. It can populate agreements from Salesforce, apply approved clauses, and use a library of preconfigured workflow steps. eBrevia gives particular attention to reading existing contract sets, extracting data, validating source language, and producing structured outputs. DraftPro adds Word revisions, while Command supplies requests, ownership, and status management around the agreement portfolio. Docusign CLM is relevant when a company needs its sales and procurement processes to produce and advance contracts through defined approval paths. eBrevia becomes compelling when the central task is understanding accumulated agreements and reusing their data and language across diligence, drafting, and ongoing administration.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. 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 core of CLM is a workflow and document system. It generates contracts from templates, keeps a clause library, and stores agreements in a repository with reporting. A drag and drop workflow designer offers more than 100 preconfigured steps for generation, review, approval, signature and storage. That system dates from SpringCM, which Docusign agreed to buy in 2018, before generative AI was part of it. AI now drives several core functions. More than 100 pretrained models extract and report on contract data points and legal topics. AI-Assisted Review flags nonstandard clauses and suggests redlines against a playbook. Generative features summarize agreements, draft clauses on request and answer questions about the repository. Docusign brands the engine Iris and describes it as trained on decades of contract data. Workflows can start from analytics, risk scores and contract content, so extracted data drives routing as well as lookups in the repository.
AI drives eBrevia's extraction, contract questions, and suggested revisions. Contract Analyzer applies more than 700 prepared fields and supports optional custom extraction, while Lens answers questions without requiring a new model for each request. DraftPro applies playbooks and draws clauses from previous agreements to assist Word editing. Those capabilities sit alongside a conventional operating layer in Command: a repository, contract requests, assignees, priorities, due dates, and status changes. Removing AI would remove the intelligence and drafting functions, but the surrounding storage and contract work system would still have functions. The suite therefore combines an AI engine with ongoing agreement administration.
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.
Docusign describes Iris as delivering accurate, secure and trusted agreement intelligence. Its AI Trust page says AI outputs have been tested for accuracy, and that diverse datasets and checks correct skewed outputs before release. Docusign publishes no figure, error rate, test set or evaluation method for CLM extraction, AI-Assisted Review or agreement summaries. The numbers it gives for the review product are time savings, such as 72 to 80 percent saved on contract reviews, with no stated baseline. Section 6.2 of the AI Attachment for Docusign Services, version 8 July 2026, warns that the AI may produce incorrect output, given the probabilistic nature of machine learning. The same section places review for accuracy on the customer. CLM works from the customer's own contracts and clause library rather than from law. Docusign does not describe how a summary or an answer links back to the clause it came from.
Contract Analyzer presents extracted information beside the agreement and lets a reviewer jump from a result to the exact source text. Lens uses the same contract material for contextual answers, and DraftPro draws reusable clauses from agreements already in the repository. Users can validate, annotate, or correct results before exporting them. This gives contract findings a traceable basis, rather than treating generated language as an unsupported conclusion. Published review speed and accuracy claims are not accompanied by a reproducible evaluation dataset or a detailed failure analysis. The source links concern agreements, not a verified collection of judicial authority.
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.
AI-Assisted Review suggests edits and flags risky language for a reviewer to accept or reject. CLM workflows send agreements with nonstandard terms to review under conditional rules the customer sets, and they can also be triggered automatically by analytics, risk scores and contract content. Every action sits in an audit trail of who did what and when, with version control across drafts. Section 6.2 of the AI Attachment makes the customer responsible for reviewing and evaluating AI output for accuracy and suitability, including through human review. The AI Trust page says the customer has the final say to approve outputs. Docusign does not set out what an AI step may do without a person, at what confidence an extraction is held for review, or what happens after an AI output is found to be wrong.
DraftPro proposes redlines after applying the legal team's playbook, but the lawyer chooses which revisions enter the Word file. The review explains whether a provision passes or fails the chosen standard and allows navigation to the relevant clause. Contract Analyzer separately supports reviewer assignments, progress states, annotations, and quality assurance workflows. Command tracks ownership and activity as an agreement moves through drafting, review, negotiation, and signature. These are practical review surfaces and responsibilities. The product does not describe a confidence based stopping rule, an automatic route for every uncertain answer, or a recovery procedure after an incorrect result has been accepted.
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.
The CLM page carries four customer stories, each naming the customer, giving figures and quoting a named, titled speaker. T-Mobile Wholesale cut agreement time by 44 percent without adding headcount, with 1.8 times faster cycle time on high value agreements, says Janet Sutherland, Senior Manager of Sales Enablement. Keith McCarraher, Special Projects Manager at the automotive parts distributor, describes more than ten use cases across five departments. Vestwell reports agreement packages built in 5 minutes instead of 75 and 70 percent fewer drop offs, quoted by its COO, Jon Mark. At iCIMS, 78 percent of the company's agreements need no legal involvement, according to Courtney Dutter, Deputy General Counsel. The page also states a 449 percent return on investment, an 85 percent reduction in errors and 2,200 enterprise CLM customers, without naming the study or the customers behind those figures. No story gives a deployment date or a measurement method.
Named users describe concrete work with eBrevia. McDermott, Will & Emery attributes its ability to meet difficult review deadlines to the product. MUFG describes using custom trainable AI across different review needs, while Morris, Manning & Martin connects it with reducing data handling so lawyers can focus on analysis. Baker McKenzie discusses international deals, and Best World Group describes visibility across regional contracts. The product also advertises review time reductions of 30 to 90 percent. These accounts establish deployed legal and business uses, but the cited figures are not tied to a dated study with a reproducible measurement method.
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.
The Docusign Master Services Agreement, version 14 November 2022, keeps Customer Data owned by the customer (3.1). Confidential information may be used only for the purpose given and must be protected with at least reasonable care (11.1). Liability for a breach of confidentiality sits outside the twelve month fee cap (10.2). The AI Attachment treats AI output as Customer Confidential Information. Section 4.1 of the AI Attachment grants Docusign a perpetual license to use CLM customer data and AI output, once anonymized and aggregated, to train models. Section 4.2 lets the customer switch that off going forward with a toggle in the product. Section 4.3 of the MSA separately lets Docusign use deidentified usage data, including for training. Within a customer account, CLM folder security limits who sees which contracts. The agreements and the product pages do not address privilege or work product.
The service agreement treats uploaded Licensee Data as confidential and restricts disclosure to authorized recipients who need the information and carry matching confidentiality duties. It permits injunctive relief for a breach and requires steps to recover improperly disclosed material. Live customer data is deleted at termination or written request, with encrypted backups and legal retention exceptions. Public marketing promises no training on client data, while the incorporated Privacy Notice permits service personal data to support product improvement. The contract does not expressly exclude model training from that permission. Attorney client privilege, matter barriers, and downstream model provider retention receive no specific public treatment.
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. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Section 6.2 of the AI Attachment, the contract that governs CLM's AI features, states that neither Docusign, the AI Services nor AI output provide the customer with legal advice. The same section leaves suitability for any purpose to the customer's sole discretion and has the customer review output for accuracy, including through human review. CLM is sold to sales, procurement, human resources and customer experience teams as well as legal. AI-Assisted Review proposes redlines and drafts clauses for any of those users. Docusign does not say who in a customer reviews an AI redline before it reaches a counterparty, how the product supports a lawyer's competence and supervision duties, or whether any limit applies by jurisdiction.
eBrevia's service agreement defines its role as a tool for reviewing, summarizing, and managing legal material, expressly excluding replacement of legal advice. The customer remains responsible for decisions based on generated information. Authorized users include employees, attorneys, paralegals, and professional staff performing legal or related services. A licensee may share analysis with its clients, but direct client access requires a separate license. DraftPro reinforces lawyer control over proposed changes. These boundaries identify the product's professional role without setting out jurisdiction specific eligibility rules or a detailed account of how a firm should satisfy competence, supervision, and client consent duties.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
Docusign publishes AI Trust and AI Innovation Principles pages for Iris, the engine behind CLM's AI features. The AI Trust page lists encryption in transit and at rest, consent based training on aggregated and anonymized data, and content filtering for harmful outputs. It also describes diverse datasets and checks that correct skewed outputs before deployment, and adoption of frameworks such as the NIST AI framework. Section 6.1 of the AI Attachment warrants that, to Docusign's knowledge, it holds sufficient permissions for the data used to train its own models. That data is defined as customer data authorized for that use, publicly available data and licensed data. Docusign names no person, committee or team as accountable for model behavior and lists no ISO/IEC 42001 certification. It publishes no test results, including on whether output differs across contract types, languages or regions. The AI Trust page says broader AI Trust capabilities are available through sales.
eBrevia offers Legal Advisory services covering AI use case selection, secure architecture, governance mapping, pilot evaluation, and adoption. Those services describe work for a customer's rollout, rather than a published policy governing eBrevia's own model development. Its leadership materials identify technical responsibility for the AI platforms, and its security program concerns protection of information. No public framework describes model release approval, bias evaluation, or results across languages and agreement types. Customer playbooks specify review positions, but they do not reveal how the vendor evaluates errors or uneven performance before introducing changes to its underlying AI.
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.
Under section 3.1 of the Service Schedule for Docusign CLM, version 15 September 2025, documents are stored for the subscription term or until the customer deletes them. An account administrator can set a different retention and deletion schedule. Retrieval is free during the term and available for 90 days after it through professional services, after which Docusign may delete the account and its documents (3.2). The Data Protection Attachment, version 4 September 2024, commits to notice of a data breach without undue delay, giving its nature, likely consequences and the measures taken. It also commits to deletion of personal data on request. Docusign's subprocessor list, last updated 18 September 2026, has its own CLM section naming each hosting and AI supplier with locations. Updates go out through an RSS feed, and objections go by email. Agreement contents are encrypted at rest, and folder security controls access inside an account. Section 4.1 of the AI Attachment lets Docusign keep training data derived from customer content after termination, with no duty to delete it. Docusign does not state what Microsoft or Google keep from prompts.
The customer agreement provides deletion of live Licensee Data at termination or on written request, while allowing encrypted backup copies for six months and retention required by law. The Privacy Notice supplies a similar rule for service personal data. Contract Analyzer describes encryption in transit and storage, and the wider platform offers access controls for enterprise use. Public materials also describe monitoring and independent security audits. They do not name a complete current subprocessor chain or establish a specific incident notification deadline. The service terms exclude protected health information, payment card data, and certain financial personal information from authorized uploads.
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.
The Master Services Agreement, version 14 November 2022, warrants that the services perform substantially as documented (8.1). The remedy is repair, replacement, or termination and a prorated refund. Docusign indemnifies the customer against third party claims arising from its breach of confidentiality and from intellectual property infringement (9.1). Liability is capped at fees paid for the service in the twelve months before the first event (10.2). The cap does not apply to indemnity obligations, confidentiality breaches, gross negligence or willful misconduct. The AI Attachment narrows these terms for AI. Section 6.2 disclaims all warranties on AI output and says Docusign is not liable for output to the extent it includes customer data. It also removes the indemnity where a claim arises from the customer's data, its own modifications or output it knew to infringe. The agreements do not cover loss from a wrong extraction or redline, and Docusign publishes nothing on insurance.
The service agreement provides an intellectual property indemnity for claims that eBrevia's technology infringes third party rights, subject to a customer modification exclusion. That indemnity is expressly outside the general liability limit. Ordinary direct damages are capped at fees paid during the preceding 12 months, with consequential losses excluded and a one year limit for bringing an action. Separate exceptions cover specified personal injury, misconduct, and fraud claims. The functionality commitment uses commercially reasonable efforts, while accuracy and completeness are disclaimed. These terms provide defined recourse for technology infringement, but no specific indemnity or correctness warranty for generated legal output.
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.
Docusign's Salesforce integration for CLM generates documents and runs workflows across Salesforce Customer 360. With SAP Ariba, users create supplier agreements, ingest third party paper and track workflow tasks from Ariba. The Coupa integration lets contracts be created or updated in either system. Slack carries review notifications and actions, and comments sync between Microsoft Word, Google Docs and CLM. AI-Assisted Review runs inside Word, and Docusign eSignature is built in. The CLM API in the Docusign Developer Center offers object, task and content APIs for Salesforce and custom applications. Docusign Monitor, sold as an extra on top of CLM, reports CLM event activity, including through Splunk. Docusign University runs courses on building custom CLM integrations. The named integrations include no document management system used by law firms, such as iManage or NetDocuments. The product pages do not say which fields move in which direction for each connector.
DraftPro works inside Word and obtains clause language from the licensed eBrevia repository; users inspect suggestions and apply selected redlines to the draft. Connect handles incoming agreements and pushes extracted data into downstream systems. Its listed connections include iManage, NetDocuments, HighQ, Relativity, Salesforce, SharePoint, Microsoft applications, and reporting tools. Described operations include tagging files, assigning employees, validating data across systems, and generating reports. This establishes movement into and out of the contract platform. The public descriptions do not provide connector specific field mappings, permission synchronization rules, or installation procedures showing what each firm must configure.
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.
Docusign's subprocessor list names CLM's hosting suppliers and places each by where the service is provisioned. The hosts are Equinix in the Netherlands, the United Kingdom and the United States, Switch in the United States, and Microsoft Azure in the United States, Australia, Canada, the European Union and Japan. AI processing is listed separately. Azure AI services for review, summaries and extraction run in the United States, Canada, the European Union, Australia and Japan. Google processing for the CLM Analyzer service runs in Belgium, Canada, Germany, Switzerland, the United Kingdom and the United States. Government editions are separate deployments. The CLM Service Schedule keeps government customer data inside Docusign's FedRAMP Moderate boundary unless a connector exports it (5.2). The DoD Impact Level 4 edition requires a connection to NIPRnet through a boundary cloud access point (5.3). Docusign does not describe the tenancy model for commercial customers and offers no on premises option.
eBrevia operates as a hosted contract platform with a Word add in connected to the licensed environment. Its Privacy Notice says hosting defaults to the United States unless the customer instructs otherwise, while also identifying facilities across several continents. The same notice explains that business processes cross borders and processing cannot always be confined to the individual's country. No public tier matrix identifies the alternative regions available for every product, and no separate location is supplied for each generative model task. A hosting instruction therefore provides some regional control without a complete account of storage, processing, and provider locations.
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.
The certifications page Docusign publishes lists ISO/IEC 27001:2022 certification enterprise wide, ISO/IEC 27017:2015 and 27018:2019, and PCI DSS 4.0. Annual SOC 1 Type II and SOC 2 Type II audits cover all production operations, including data centers. FedRAMP agency authorization, GovRAMP authorization and a Defense Information Systems Agency Impact Level 4 provisional authorization each name CLM directly. Reports and certificates are available in the Docusign Trust Portal, and the annual CSA STAR CAIQ is public on the CSA registry. Docusign also completes the Shared Assessments SIG, S&P Global KY3P and ProcessUnity assessments each year. USDM assesses its 21 CFR Part 11 module annually. C5 Type II covers the eSignature product only and does not extend to CLM.
eBrevia states that it is independently certified for SOC 1 and SOC 2, and Contract Analyzer specifically names SOC 2 Type II infrastructure. The security description refers to continuing audits and monitoring, encryption, and controls for authorized access. It also claims GDPR and HIPAA compliance, which are separate from a disclosed audit report. No accessible report supplies the audit period, exceptions, or precise service scope. The public customer agreement additionally restricts protected health information, so the HIPAA marketing statement does not override that upload restriction or establish that a customer has an applicable business associate agreement.
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 October 2026 subprocessor list assigns AI suppliers to specific CLM features. Azure OpenAI Service handles current AI Assisted Review and agreement summaries, while Azure AI Document Intelligence handles extraction. Google processes CLM Analyzer, and Docusign's DocuSmart subsidiary, trading as Lexion, handles legacy AI Assisted Review for selected United States customers. Countries are specified by service provisioning, and customers can subscribe to updates and object on data protection grounds. Model families and versions are not identified for these CLM services. Gemini naming in the separate Agreement Manager section does not establish that CLM uses the same model or configuration.
The suite distinguishes structured extraction from Lens, its generative layer for questions across contract material. Contract Analyzer has prepared fields and optional custom models, while DraftPro combines AI classification, playbook review, and clause reuse. eBrevia describes its own long development history in machine learning and natural language processing, but does not identify the foundation model providers serving current Lens or DraftPro requests. No version inventory, provider retention arrangement, or notification commitment for model changes is published in the product and contract materials. Named business integrations identify connected applications, not the model services that may process a customer's agreement.
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.
A CLM subscription is prepaid and measured by a seat allowance, a document count or both, depending on the edition (4). The Service Schedule for Docusign CLM publishes that charging structure, but Docusign publishes no CLM price. Every call to action on the CLM page, Get Started included, goes to Contact Sales. The site's plans and pricing links lead to eSignature and IAM plans, none of which includes CLM. Under section 4.3, extra seats are charged pro rata at list price for the rest of the term. Documents over the count are charged per document at list price and invoiced monthly in arrears. Seats can be reassigned between people without penalty, and documents exported and then deleted during the term still count. Retrieval after the term ends is a paid professional services engagement. Editions named across Docusign's documents include CLM Essentials, CLM, CLM+ and the AI Extension for CLM, alongside government and DoD Impact Level 4 editions.
eBrevia quotes review projects according to contract volume, review scope, and required capabilities. Its service agreement sets fees and access in a proposal and defines a processed Document as no more than 300 pages. The default contract period is one year with annual renewal unless the proposal changes it, and nonrenewal requires 30 days' notice. Contract Analyzer, DraftPro, and Connect can form part of the licensed services. No numeric subscription rate or implementation charge is supplied publicly. Training and support appear within the service definition, but their inclusion and any additional cost depend on the negotiated proposal.
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.
CLM is sold to legal, sales, procurement, human resources and customer experience teams. Its named customer stories come from wholesale telecom, auto parts distribution, retirement plan administration and recruiting software. Government use runs through CLM Government Products, authorized under FedRAMP and GovRAMP, and a DoD Impact Level 4 edition. Docusign says 2,200 enterprises use CLM for contract management. Its integrations with SAP Ariba and Coupa point at procurement as well as sales contracting. Docusign frames coverage by department and industry rather than by contract type or area of law. It names no minimum customer size, no law firm use, and no contract types the AI handles poorly. The IAM plans page states AI extraction in English, French and German, and the CLM pages give no language list.
The product addresses law firms, corporate legal departments, financial institutions, and audit or consulting teams. Law firm workflows include mergers and acquisitions diligence, bankruptcy and financing review, and compliance reporting. Contract Analyzer also supports leases, repapering, and migration of agreement data. DraftPro covers repeat commercial, employment, privacy, technology, finance, real estate, and corporate agreements, with sample playbooks for selected types and custom positions for others. Command extends contract information to procurement, sales, finance, and related business teams. Coverage is described through these tasks and examples, without a complete list of supported jurisdictions or performance boundaries for each language.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
Section 4.1 of the AI Attachment for Docusign Services, version 8 July 2026, grants Docusign a perpetual license to use customer data and AI output to train models and improve its services generally. The data and output are anonymized and aggregated first. The attachment's applicability table says customers on a Master Services Agreement consent to that training for Docusign CLM. Section 4.2 lets the customer opt out at any time with a toggle in the product, on a going forward basis.
Docusign keeps the training data created before the opt out, with no duty to delete it. The AI Trust page describes the same program as consent based. Customers whose subscription began before 8 July 2026 are pointed to earlier versions of the terms.
The service agreement incorporates the Privacy Notice for uploaded material and service personal data. That notice permits personal information to support developing and improving products and services, without expressly excluding model training from that permission. The scope is personal data covered by the notice, not an assertion that every uploaded agreement is used for training. Public event material separately promises no training on client data, but a matching prohibition does not appear in the customer contract.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Section 3.1 of the Service Schedule for Docusign CLM, version 15 September 2025, keeps each stored document, including the customer data in it, for the subscription term or until the customer deletes it. The account administrator can set a different retention and deletion schedule. After the term, documents can be retrieved for 90 days through professional services, and Docusign may then delete them (3.2). The schedule covers stored documents rather than prompts as such.
AI output is Customer Confidential Information under the AI Attachment. The same attachment lets Docusign keep anonymized training data derived from content, with no duty to delete it. Docusign does not state what the Azure and Google model services keep from a prompt.
The customer can instruct eBrevia in writing to delete live Licensee Data, and termination also triggers that deletion duty. The Privacy Notice similarly permits removal of personal data from live services on request. Encrypted backups may remain for six months, and legal retention requirements create an exception. This is control through a contractual instruction, rather than a published retention slider. No mode promises that prompts and generated answers are never retained during processing.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
CLM has its own permission model built on folders. A Docusign employee's guide on the Docusign Community sets out six levels. They run from No Access, the default for all content, through View, View and Create, View and Edit, and View, Edit and Delete, to full control with Set Access. Security can be set for a user, a permission profile or a user group. Folders inherit their parent's security unless it is set explicitly.
CLM administrators can see all content whatever the folder settings. The CLM page adds granular permissions controls and an audit trail of who did what and when. Docusign does not say how AI review, summaries or repository lookups apply folder permissions when they run.
DraftPro ties user access to the licensed eBrevia environment and can filter clause material by project, matter, contract type, or jurisdiction. Contract Analyzer supports assignments and enterprise access controls. Those features do not establish that retrieval enforces a firm's ethical walls or inherits the permissions of an upstream document repository. A matter filter organizes material for review; it is not, by itself, a documented security boundary preventing access to another client's information.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Section 11.2 of the Master Services Agreement, version 14 November 2022, requires prompt written notice before a compelled disclosure of confidential information, unless legal process forbids it. It also requires cooperation in seeking a protective order. The Data Protection Attachment adds prompt notice of any government request about personal data. Docusign's law enforcement page says the company notifies customers when their data is subject to disclosure and withholds notice only under a signed nondisclosure order or a statute that bars it.
The page adds that Docusign cannot decrypt agreement contents at rest. Docusign prepares an annual transparency report on requests and makes it available to data protection authorities on request. The report is not published. Section 2(d) of the CLM Service Schedule says Docusign is not responsible for producing customer documents to any third party.
The Privacy Notice allows disclosure in response to an information request when eBrevia determines that law, regulation, or legal process permits or requires it. It also covers disclosures to protect rights and defend legal claims. Neither that provision nor the service agreement commits to informing the customer before producing material, and no transparency report is supplied. The confidentiality clause limits ordinary sharing but does not add a separate notice procedure for compulsory demands.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
CLM works from the customer's own contracts, templates and clause library, and does not retrieve case law or legislation. Docusign describes Iris, the engine behind it, as trained on decades of contract data. Section 6.1 of the AI Attachment lists the training data for Docusign's own models as customer data authorized for training, publicly available data and data licensed from third parties. Docusign warrants that to its knowledge it holds sufficient permissions for them.
The section names no specific source or license, and it excludes the data third party providers used for their own models.
eBrevia's contract answers and clause library derive from agreements supplied to its repository. Lens asks questions of that material, while DraftPro reuses provisions from earlier contracts with filters for the current context. The service terms require the customer to hold the rights needed for uploaded material. No separate primary law collection, publisher license, or legal update schedule is described. Contract source traceability therefore establishes where an agreement answer came from, rather than the provenance of external legal authority.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
Docusign CLM manages a customer's own agreements and does not cite case law or legislation, so a citator is not part of the product. The CLM page, the AI-Assisted Review page and the AI Trust page do not address checking authority for later history. Docusign does not describe how CLM detects when an amendment or a policy change leaves extracted terms or clause library positions out of date.
A reviewer can follow an extracted provision back to the contract and assess it against a playbook. Neither that process nor a Lens answer checks whether a judicial authority has later been reversed or limited. The products focus on contract language, obligations, and company positions, with no named citator or subsequent treatment mechanism. A governing law field identifies a contract term; it does not establish that the law applied to the agreement remains current.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Section 6.2 of the AI Attachment warns that AI output may be incorrect or otherwise undesirable and makes the customer responsible for reviewing it. The AI Trust page describes content filtering for harmful outputs. Neither document says what AI-Assisted Review or the question and answer feature does when a playbook or the repository does not cover what is asked. Nor do they say how a doubtful extraction is marked before it feeds a report, a renewal alert or a workflow rule.
Docusign documents no path for CLM's AI features to decline an answer and publishes no confidence or grounding scores for extraction, review or summaries.
Lens is described as producing contextual answers linked to contract material, but no public example specifies what it returns when the agreement cannot support an answer. DraftPro's pass or fail result concerns compliance with a chosen playbook, not uncertainty in the model's interpretation. Users can correct extraction, add missing clauses, and reject revisions. Those review controls leave room for human judgment without defining an automatic refusal or abstention path for unsupported output.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database maintained by Damien Charlotin tracks court decisions worldwide that address hallucinated AI content and records the tool involved where known. It has no entry naming Docusign, Docusign CLM, Iris, SpringCM or Lexion, in the tool field or anywhere in the case text. CLM manages commercial agreements rather than producing court filings, so its output does not ordinarily reach a brief.
The AI Hallucination Cases database maintained by Damien Charlotin has no entry naming eBrevia or e Brevia. The database records court decisions involving hallucinated AI material and identifies tools when the proceedings do so. eBrevia mainly analyzes agreements and proposes contract language, rather than preparing briefs from judicial authorities. That focus does not make its output infallible, and the absence of a named court case is not a test of extraction accuracy or drafting quality.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Section 6.2 of the AI Attachment for Docusign Services, which governs CLM's AI features, states that neither Docusign, the AI Services nor AI output provide the customer with legal advice. It makes the customer responsible for reviewing output for accuracy and suitability, including through human review. The CLM page, the AI-Assisted Review page, the AI Trust page and the agreements name no bar opinion, ethics rule or professional conduct guidance.
Docusign's compliance work covers data, security and sector regimes, including ISO, SOC, PCI DSS, FedRAMP, GovRAMP, DoD Impact Level 4, HIPAA and 21 CFR Part 11. Those regimes bind Docusign as a provider rather than a lawyer using the product.
The service agreement separates software assistance from legal advice and places responsibility for decisions with the customer. DraftPro also keeps proposed changes subject to lawyer approval. These provisions establish a supervised product role, but no named bar opinion or jurisdiction specific ethics mapping accompanies them. The public materials do not connect use of Lens, shared client material, or automated contract revisions with particular duties of competence, confidentiality, disclosure, or supervision under a professional rule.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Enterprise legal, sales, procurement, and HR teams use CLM for their employer's agreements. Customer examples include T-Mobile Wholesale, Vestwell, and iCIMS, whose outcomes concern internal contracting speed and administrative effort. Vestwell reduced agreement package creation from 75 minutes to 5 minutes, while iCIMS attributes reduced legal intervention to its workflow. These are corporate operating costs rather than outside counsel invoices, and CLM does not specify a client fee adjustment for AI assisted work.
eBrevia markets reduced review time and cost to law firms as well as corporate buyers. Its law firm use cases include diligence, financing review, and compliance reports, and the customer license expressly permits sharing resulting analysis with clients. These uses place the product inside legal service delivery where efficiency can affect a bill. The public product and contract materials do not explain how lawyers should record saved time, adjust billed hours, or disclose an AI related charge.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
Docusign's subprocessor list, last updated 18 September 2026, is published as a web page and a download, with a separate section for CLM. It names each hosting supplier and each AI supplier against the feature it powers, with countries and a contact address. Changes go to an RSS feed, with an email route for objections. The Data Protection Attachment, the AI Attachment, the Master Services Agreement and the CLM Service Schedule are all published without a login.
The certifications page and the public CSA STAR CAIQ cover security. Together these documents name every model provider that touches CLM content, and a customer can forward them when its own clients ask about AI vendors.
The service agreement, Privacy Notice, and security statements provide general information about confidentiality, retention, and permitted data. They do not include a current named model provider chain, a complete subprocessor register, or a client disclosure package for outside counsel use. Lists of supported applications describe integrations rather than organizations processing data on eBrevia's behalf. A firm can use the public contract material in diligence, but it does not resolve a client's AI specific notification requirements.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
CLM keeps an audit trail of who did what and when, and detailed version control across drafts, so the history of a contract can be reconstructed. Docusign does not say whether an AI-Assisted Review suggestion, an AI drafted clause or an AI extraction is marked as machine generated in that history. Nor does it say whether the audit trail records which model produced it. It publishes no export built for disclosing AI involvement and no disclosure template.
CLM output is a contract, a report or an obligation record rather than a court filing. A record of AI involvement would most likely go to a counterparty, an auditor or a regulator.
Contract Analyzer retains extracted terms beside source language and supports review status, annotations, and exported reports. DraftPro leaves selected revisions visible as Word redlines, while Command records contract activity and status changes. Those elements can help reconstruct what was reviewed. No public export combines the generating model, the full set of material used for an answer, and a named person's verification in one certificate. Contract analysis records therefore cover only part of a filing disclosure.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- Good Law Verification
- Refusal and Uncertainty Behavior
Which one fits
Choose Docusign CLM if
- Agreement generation should use Salesforce data and approved clause language.
- Internal and external review must follow conditional routing through a defined contract process.
- Procurement needs shared contract data and updates with Coupa.
Choose eBrevia if
- A review project starts with many existing agreements requiring extraction and validation.
- The team needs assignments, completion states, annotations, and structured diligence outputs.
- Word drafting should reuse language held in the existing agreement repository.
In summary
Docusign CLM
Docusign CLM supports agreement creation with business system data, approved clause libraries, conditional review, and collaborative negotiation. The AI Legal Index highlights its catalog of more than 100 preconfigured workflow steps as a concrete means of assembling contract processes. Reviewers can receive tasks through email and Slack, while version history supports collaboration. Connections with Salesforce and Coupa place the agreement within sales or procurement work, alongside the platform's repository and lifecycle functions.
eBrevia
eBrevia Contract Analyzer lets teams assign review work, maintain progress states, and validate extracted information against its original language. The AI Legal Index identifies those reviewer and quality assurance controls as part of its large contract set workflow. Lens adds contextual questions, DraftPro supplies playbook based Word redlines, and Command manages contract requests and activity. Connect can carry structured results to other systems after the review is complete.
Questions buyers ask
How does Docusign CLM use Salesforce information?
It can populate new agreements with Salesforce data and connect document generation, workflow, and a central agreement repository with the Salesforce environment. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
What can move between Docusign CLM and Coupa?
The described integration shares data between the systems and can create or update contracts in Coupa or Docusign CLM. That connects contracting with procurement activity. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
How does eBrevia organize a team review of a contract set?
Contract Analyzer assigns agreements to reviewers, tracks whether work is unreviewed, in progress, or complete, and supports quality assurance. Findings remain linked to source language for validation. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Is Docusign CLM simply the electronic signature product?
No. CLM also covers generation, negotiation, approvals, repository functions, and ongoing contract processes. Electronic signature is one part of Docusign's wider agreement offering. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
Docusign CLM is distinct from Docusign eSignature and Agreement Manager. eBrevia Command likewise adds contract administration to its analysis and drafting tools; the suite is not limited to extraction alone.