Avvoka vs Clarilis: how they compare in 2026
Avvoka and Clarilis are both UK document automation platforms for transactional lawyers, turning questionnaires into first drafts from approved language. Avvoka's lead is what happens after the first draft. Negotiation runs in one live document with clauses the firm has locked, drafts can start from Harvey, and negotiation heatmaps show how each clause is marked up across a portfolio. Its disclaimer also states plainly that it is not a solicitor and that information given to it is not privileged. Clarilis's counterweight is how it handles its AI. Every clause its AI Draft writes is highlighted in the delivered Word document under a notice that it needs review, and firms can switch the AI off. It names OpenAI in Azure as its preferred model, runs zero retention endpoints in region, and states that neither inputs nor outputs train the model.
Which one fits
Choose Avvoka if
- You negotiate with counterparties and want one controlled draft. Avvoka runs negotiation in a single live document, lets the firm lock clauses in advance and mark others open, turns comments into assigned tasks, saves every version, and signs in platform or through Docusign and Adobe Sign.
- You want to see how your clauses are actually negotiated. Avvoka records how each structured clause is marked up across a portfolio, producing heatmaps of what changes and where, reports on pushback against standard positions, and comparisons of individual negotiators.
- Your lawyers already draft in Harvey. Avvoka's published partnership lets a lawyer working in Harvey draft from the firm's own Avvoka templates and clause library and carry the document through negotiation, and its data sits in the UK, Europe, the US or Australia on AWS, OVH or Azure.
Choose Clarilis if
- You need to see which parts of a draft a machine wrote. Clarilis highlights every AI Draft clause in the delivered Word document under a notice that AI content requires review, lists what its AI gets wrong, such as unmatched cross references and undefined terms, and lets firms switch it off.
- You want whole deal suites built and maintained for you. Clarilis's own professional support lawyers build and maintain the automations, with over seventy real estate templates for England and Wales, more than fifty Scottish PSG documents and nearly two hundred corporate documents.
- Your procurement team wants a certificate it can check and a named model. Clarilis states ISO 27001:2022 certification by BSI across the company with certificate number IS 677941, names OpenAI hosted in Azure as its preferred model, and has signed the Litig AI Transparency Charter.
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.
Avvoka combines AI assisted template creation with a document assembly and negotiation system. Curate compares clauses across uploaded agreements and proposes a reusable precedent, while the lawyer chooses the language to retain. MassDraft uses AI to identify inconsistent input data before generating many agreements. Beneath these functions, questionnaires, conditional clauses, approved libraries, version history, negotiation controls, and signatures remain usable without a model. The assistant connections bring that governed drafting engine into other tools. Removing AI would remove comparison and preparation capabilities, but the structured document workflow would continue to operate. The product therefore has an AI engine within a broader drafting platform.
Clarilis describes deterministic, template based automation as the gold standard for legal drafting and positions AI Draft as adding to it rather than replacing it. It gives the split: automation takes a draft roughly ninety percent of the way and AI Draft helps with the remaining ten. AI Draft creates new content without changing the content the rules generate, and its FAQ says firms that do not permit generative AI can disable AI Draft in an automation, leaving the rest of the platform unaffected. What remains with it switched off is the whole product: questionnaire driven assembly of complete document suites, hundreds of maintained templates across four practice areas and five jurisdictions, house style formatting, and the managed service behind it.
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.
Curate works from files supplied by the customer, compares versions of each clause side by side, and lets the lawyer select, combine, or rewrite the wording before it enters a precedent. Subsequent document assembly follows approved template rules. The drafting process is therefore source based, though deterministic assembly cannot show that an AI synthesis or the underlying legal language is correct. Avvoka advertises millions of drafted documents without hallucinations without publishing a reproducible evaluation or failure analysis. The product does not supply a legal authority citator. Its source controls concern the firm's own contract language and require professional review.
There is no accuracy figure, evaluation, test set or error rate on the site. The ninety percent figure that recurs is a time saving claim about the automation, not an accuracy measure. AI Draft writes new contract language and has no authority to cite. The vendor lists what its own AI gets wrong. Users must check AI content for cross references, because the AI does not yet match references to other clauses automatically; for definitions used but not defined elsewhere; and for legal and commercial effectiveness. The guidance ends by telling users to always treat AI generated content as a first cut. Grounding is described as matter context and codified practice area knowledge from in house lawyers, and how that grounding works is not described.
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.
Curate separates model assistance from adoption into the firm's precedent. It compares uploaded clauses and can combine wording, but no clause enters the template until the lawyer approves it. After approval, document generation follows the template's rules. Negotiation controls can lock clauses and route work to named people, with comments assigned as tasks and versions preserved. MassDraft adds validation of input data before bulk generation and lets users compare amendments before execution. These controls define both automated actions and review surfaces. Approval of a clause is an explicit boundary for Curate, although the vendor does not publish numerical stopping conditions across all AI functions.
AI Draft writes new content only where a user invokes a named task, and it cannot change the drafting the automation produced. Review is built into the document itself. Every AI generated clause is highlighted in the delivered Word document, and any document containing AI content carries a notice at the top saying that content needs review. The vendor says AI content is new and, unlike automated content, has not been reviewed in advance, and lists what to check: cross references, use of definitions, and legal and commercial effectiveness. It calls AI generated content a first cut that still needs expert review. A firm that does not permit generative AI can turn the layer off and keep the automation. Because the marking sits inside the document, it survives export, which a review state inside the platform does not.
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.
Named users describe Avvoka in production. Maddocks identifies its replacement of a legacy platform and reports improved stability and easier adaptation as document requirements change. Ropes & Gray describes adoption and workflow improvements, while Fried Frank's knowledge leadership discusses turning past deal language into approved standards through Curate. The homepage also advertises drafting eight times faster and adoption by a quarter of the AmLaw 100. Those aggregate figures are not accompanied by a defined measurement period or method. The attributed accounts establish actual use and customer context, but do not isolate an independently measured benefit from the AI functions.
Two customers are quoted with organizations attached. Miri Stickland, Head of Knowledge at Forsters, speaks to the risk management benefit of updates being made quickly and consistently behind the scenes. A Head of Knowledge Management at TLT, named by role only, says the solution exceeded expectations on delivery. Both link to individual customer pages, and CMS is named in a vendor blog post about faster drafting for its Scottish real estate team. Separately, the platform material says the system cuts the time to produce document suites by around ninety percent, and that firms draft suites ninety percent faster, with no firm, date or method attached to either figure. So the named customers carry no measurement and the measurement carries no named customer. A customers section and a case studies section sit in the navigation.
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.
Documents are encrypted at rest, connections use HTTPS, and administrators can require a second authentication factor or single sign on. Curate and the assistant drafting offering promise that customer documents will not train a shared model. That wording does not expressly prohibit all forms of private model adaptation. The legal advice disclaimer also states that information supplied to Avvoka does not attract legal advice privilege through a relationship with the software provider. The assistant offering claims that permissions and ethical walls carry over, but does not explain enforcement. No readable customer agreement provides a complete confidentiality, retention, and model provider commitment.
On AI, neither user inputs nor AI responses are used to train the models, processing runs through zero data retention endpoints, and data is processed in region. On the platform, encryption covers data at rest and in transit, and protected links expire and use 256 bit AES. All requests are logged and verified, including IP addresses, and user level checks restrict access to particular document suites and drafts. SAML 2.0 single sign on and optional IP lockdown are offered, and development, testing and production environments are separate. All staff pass criminal record and eligibility checks, access follows least privilege and is recorded and auditable, and system development is not outsourced. No privilege or work product treatment appears anywhere, on a platform holding transactional drafting for named clients. No customer agreement, master services agreement or data processing addendum is published, so every commitment above sits on a product page rather than in a contract.
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.
A full advice line statement is published on a dedicated page, with no engagement with the professional rules. The disclaimer says Avvoka is not a firm of solicitors, does not practice law and does not give legal advice. It is not the user's solicitor or a substitute for a solicitor's advice, and has no solicitor client relationship with the user. A user who enters into a document created on the platform does so at their own risk and represents themselves. It also lists what the product does not do: it does not review information for legal accuracy or sufficiency, draw legal conclusions or give opinions on the documents a user creates, or apply the law to the user's circumstances. It says information provided is not covered by legal advice privilege. No Solicitors Regulation Authority guidance, bar rule or ethics opinion is named, and nothing addresses a firm's supervision or competence duties when generated drafting reaches a client. The page opens as terms for use of the website, though its substance plainly covers documents created on the platform.
The vendor says AI Draft does not replace professional legal judgment, that AI generated content should always be treated as a first cut that still needs expert review, and that automated content is carefully reviewed in advance while AI content is new and has not been. Nothing says Clarilis is not a law firm or that its output is not legal advice. No jurisdiction limit is drawn, although automated content spans England and Wales, Scotland, Ireland, the United States, Canada and Asia Pacific, and nothing addresses a firm's supervision or competence duties. There is no terms of service on the site where such a statement could sit, so the position rests entirely on a product FAQ and a blog post.
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.
Information security controls and an information security management policy are set out, with no corresponding AI governance framework. The materials do not identify a model risk owner, release approval process, evaluation regime, or testing of differences across languages, legal contexts, and document types. Customer approval in Curate gives a lawyer control over the content of a template. It does not explain the vendor's testing of the models that propose that content. ISO 27001 certification concerns information security and is not a statement that model fairness, legal reliability, or bias has been independently assessed. No AI management certification is identified.
Clarilis says it has signed the Litig AI Transparency Charter, links to it, and describes it as setting out commitments for organizations developing and providing legal AI, promoting responsible innovation while safeguarding ethical and professional standards. The security page adds a responsible AI section with four commitments: clear indicators separating AI from rules based drafting, processing in region through zero data retention endpoints, no use of data for model training, and respect for third party intellectual property rights. No management system such as ISO 42001 or independent audit of AI governance is published. No accountable owner or function is named, no evaluation regime before release or results are described, and nothing covers uneven output across practice areas or jurisdictions. The ISO 27001 certification concerns information security, not AI governance.
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.
Security controls include AES 256 encryption at rest with a separate initialization vector per document and a rotating master key; HTTPS for all connections, including the API; BCrypt password hashing, with passwords kept out of logs and rotation rules available; enforceable two factor authentication; SSO only mode with automatic removal of leavers; real time replication of production databases with hot standby failover; and encrypted backups. Annual black box penetration testing uses only CREST approved providers, with the latest scorecard available to clients on request. There is a published vulnerability reporting process with a PGP key, and the build pipeline is continuously tested for CSRF, XSS and SQL injection. A breach procedure commits to identifying compromised information and notifying affected individuals and the bodies the law requires. No retention period is stated; the GDPR policy says only that data is kept when necessary and deleted on a data subject's request. No subprocessor list goes beyond the named infrastructure providers.
Published controls cover encryption at rest and in transit, protected links that expire and use 256 bit AES, servers behind a firewall with all access encrypted, and separate development, testing and production environments. Data sits on encrypted file systems backed up at least daily, with horizontal scaling and resource monitoring. All requests are logged and verified, including IP addresses, and user level checks limit access to particular document suites and drafts. SAML 2.0 single sign on comes with optional IP lockdown and configurable lockout. All staff pass criminal record and eligibility checks before hiring, access follows least privilege and is recorded and auditable, and development is not outsourced. Hosting is named as AWS and Azure, and the AI layer uses zero data retention endpoints in region. Regular penetration testing is stated. No retention period is given: the only statement is that the customer has complete control over storage and deletion of data, with no period or process described. No incident notification commitment appears, and there is no agreement for one to sit in.
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.
Nothing published says who bears the loss when the product is wrong. The published legal set is a GDPR policy, a privacy policy, a legal advice disclaimer, a signing disclaimer and a security page. There is no terms of service, customer agreement, subscription agreement or service level agreement, so there is no indemnity, liability cap, warranty, warranty disclaimer or insurance statement to read. The legal advice disclaimer says a user who enters into a document does so at their own risk, but that concerns advice, not loss. It does not cover a defective template, a clause assembled wrongly, a negotiation lock that failed, or a generated draft that departed from the firm's standards. No standard limitation clause is published either.
Nothing published addresses who bears the loss when the product is wrong. The site footer carries two entries, a privacy policy and a sitemap. There is no terms of service, master services agreement, customer agreement or data processing addendum anywhere on the site, so no indemnity, liability cap, warranty position, warranty disclaimer, service level commitment or insurance statement is published. The product produces complete suites of transactional documents through a managed service, and nothing says who carries a defect in a maintained template. No limitation clause of any kind is published.
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.
Assistant connections expose templates, approved clauses, amendments, and document export through other working environments. Claude and Microsoft 365 Copilot are listed as live, Harvey as early access, and Legora as a planned beta in the fourth quarter of 2026. Curate names an iManage integration, while API and MCP access support connections to business systems. MassDraft describes Docusign envelope preparation, signature status tracking, and combining signed counterparts for download. These sources explain actions beyond a partner logo. They do not publish complete field mappings, configuration steps, or permission synchronization behavior across every connector, so implementation still needs discussion with the vendor.
No integration into the systems a firm runs is published. The platform is web based and delivers finished drafts in Word in the firm's house style, which is a format and a delivery convention rather than a connection. Two named third parties appear and both are identity rather than practice systems: SAML 2.0 single sign on for authentication, and Certivox M-PIN offered as an optional additional security element. No document management system is named anywhere, so nothing addresses iManage or NetDocuments, and no matter management, ebilling, CRM or electronic signature counterparty appears. No API, developer documentation or integrations page exists in the navigation, which carries platform, AI Draft, security, managed service, partners and working globally.
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.
Avvoka is delivered as a hosted platform. Its general security materials name infrastructure in the United Kingdom, Europe, the United States, and Australia through AWS, OVH, and Azure. Curate and the assistant drafting offering separately specify European Union residency. The GDPR policy describes an older arrangement with a United Kingdom application server and French backup, so that policy alone does not explain the full current regional offering. The materials do not map every model operation to a processing location or define single tenant deployment options. A customer needs the selected product and contractual region to establish the boundary for its own content.
The AI Draft page says data is hosted in the customer's region via Azure, and the security page says the same for the AI layer: data is processed in region using zero data retention endpoints. The platform serves firms across England and Wales, Scotland, Ireland, the United States, Canada and Asia Pacific, and as a whole is hosted on Amazon Web Services and Microsoft Azure. Nothing says whether the platform is single tenant or multitenant, no dedicated or isolated instance is described at any tier, and no on premises or self hosted option is mentioned. The nearest thing to a separation statement is a permission control: user level checks restrict access to particular document suites and drafts. That governs users within a customer, not the boundary between customers.
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.
A named standard is backed by a stated history and a published document, without the certifier or scope. Avvoka says it has been ISO 27001 certified continuously since October 2017, with annual external audits, and it publishes its signed ISMS policy as a PDF anyone can download. A period, an audit cycle and a readable governing document go well beyond a badge. Penetration testing is annual, black box and done only by CREST approved providers, with the latest scorecard available to clients on request. Avvoka gives no certification body, certificate number, scope or statement of applicability, so a buyer cannot tell which systems and locations the certificate covers. There is no trust portal.
The security page says Clarilis is ISO/IEC 27001:2022 certified by BSI across the entire company and gives the certificate number, IS 677941. That covers the standard, the current revision, the certifying body and a company wide scope, plus an identifier that can be checked against the certifier's register. Regular penetration testing is stated separately on the AI Draft page. No certification date, expiry or surveillance cycle is published. No report, statement of applicability or summary is published, and there is no trust portal. No other certification is claimed.
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.
AI comparison, synthesis, and validation functions are described without the model versions or providers that run them. Claude, Copilot, Harvey, and Legora are named as assistant connections, not a complete account of Avvoka's internal model stack. Naming the infrastructure providers AWS, OVH, and Azure likewise leaves open which models receive document content. Curate limits its input to uploaded files and promises no training of a shared model, but no public register connects each AI feature to its processor and retention terms. A commitment to notify customers of changes to that underlying supply chain is also not published.
In the AI Draft FAQ, the vendor says it prefers OpenAI's model, hosted in Azure. The AI Draft page adds that data is hosted in the customer's region via Azure and processed through zero data retention endpoints. The vendor also says it uses a range of models depending on the drafting task and configures them with practice area knowledge from its in house lawyers, so the supply chain is plural. Its FAQ says OpenAI's model without naming which model or version, and adds that Clarilis is always exploring the latest models to ensure the best outputs. That says the set will change, and no commitment to notify customers when it does is published. No subprocessor register is published, though AWS and Azure are named as platform infrastructure on the security page.
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.
No pricing information is published at any level, including the unit of charge. The navigation has features, solutions, resources and company sections only, and the footer has no pricing entry. Every commercial route on the site is a demo booking, and there is no self service signup. Nothing says whether the platform is licensed per user, template, document, matter or firm. No tier names, minimum commitment or term, or implementation or template building cost are given, although building automated templates from precedents is a delivery project. No customer agreement is published either, so no payment terms show the charging structure.
No pricing information is published at any level, including the unit of charge. There is no pricing page in the navigation (what we do, solutions, customers, about us and resources) or in the footer, which carries only a privacy policy and a sitemap. Every commercial route leads to the same call to action, book a demo. Nothing says whether the platform is licensed per user, template, document suite, matter or firm. Nothing addresses how the managed service is charged; the vendor's own professional support lawyers build and maintain the automation, so implementation is a service engagement rather than a setup task. No tier names, minimum commitment or term length appears. No terms of service or master agreement is published, so no payment provisions are published either.
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.
Avvoka serves law firms and corporate legal teams, with distinct workflows for template authors, document users, and managers. Current examples include mergers and acquisitions, real estate, commercial agreements, and procurement. A share purchase agreement can be generated alongside disclosure letters and related papers from the same transaction facts, while MassDraft addresses large repapering exercises. Curate helps legal teams turn prior deals into approved precedents without beginning from an empty library. The product does not publish a complete jurisdiction or language matrix, or define which practices require unsupported content. Customers remain responsible for the legal suitability of the clauses and rules they approve.
Four practice areas have their own product lines with counts and named content. Real estate has over seventy automated templates for commercial investment and letting in England and Wales, plus more than fifty Property Standardization Group documents for Scotland. Corporate has nearly two hundred documents covering share purchase agreements, early stage investments, share reorganizations and business purchase agreements. Banking and finance covers leveraged and real estate finance facilities, simplified lending, security documents, legal opinions and APLMA based agreements for Asia Pacific. Private client covers wills and estate planning. Engagement letters and in house legal are addressed separately. Jurisdictional reach is stated product by product, with automated suites for Ireland, the United States and Canada, the Canadian content based on CVCA model forms. Nothing says which practice areas or jurisdictions are not served, no firm size range is given, and no document type is named as one the platform handles poorly.
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?
Curate and Avvoka's assistant drafting offering promise that customer documents are never used to train a shared model. This is a public product promise, with no matching readable customer agreement. Its scope is shared models; it does not expressly rule out adaptation confined to the customer's own service. Curate also states that it acts on uploaded files rather than indexing the customer's entire document system. A firm needs the contract to establish broader training restrictions.
The AI Draft FAQ says neither user inputs nor AI responses are used to train the AI, and the same page repeats it as a headline security property: no AI models are trained using customer data. The security page states it a third time under responsible AI and pairs it with two supporting facts: processing runs through zero data retention endpoints, and it happens in region. The site footer carries no terms of service, master services agreement or data processing addendum, so no improvement right is granted or withheld, and no contract carries the commitment.
No opt out is needed because the position is absolute, and firms that do not permit generative AI can disable AI Draft entirely at the automation level.
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 published material with no period stated. The GDPR policy addresses it under its own heading and says only that Avvoka ensures data is retained when necessary, with deletion following a request by a data subject. No period appears, no configuration option is offered, and nothing separately addresses how long drafts, template content, clause libraries, negotiation history or the prompts behind generated drafting are held, either during a subscription or after it ends.
The platform's own design points the other way and is recorded because it bears on the question: every version of a document is automatically saved and negotiation data is retained across a portfolio to build the analytics the product is sold on, so material plainly persists by design. The deletion route published is a data subject request to a data protection mailbox, which is a personal data right rather than a customer's contractual entitlement to return or destruction of its documents.
For AI processing, the security page describes the mechanism: data is processed in region using zero data retention endpoints, a specific configuration at the model provider rather than a general assurance. For the platform, the AI Draft page says the customer has complete control over platform storage and deletion of data. That control is asserted without any period, process or interface being described. Nothing on the AI Draft page, the security page or in the footer says what happens to stored drafts on termination, and no agreement on the site carries a return or destruction duty.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Avvoka's assistant drafting offering states that permissions and ethical walls carry over while documents remain in Avvoka. Curate separately acts only on uploaded files and names an iManage integration. The materials do not explain how permissions are evaluated for each request, how changed source rights propagate, or how a conflict between matters is enforced. Single sign on and access revocation protect account access, but do not supply that missing enforcement detail.
The security page says user level checks restrict access to particular document suites and drafts, that all requests are logged and verified including IP addresses, and that any change in access level requires authentication by key stakeholders. Optional IP lockdown and SAML 2.0 single sign on sit alongside it. Nothing says whether the platform is single tenant or multitenant or how one customer's drafts are kept apart from another's, and no permission model or administrator documentation is published.
A firm's precedents and live transaction drafts sit together on the platform, and the vendor's own professional support lawyers build and maintain the automations; the staff security section addresses vendor side access only as least privilege.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No commitment covers notifying a customer when a subpoena, court order, or government demand seeks its data. The GDPR policy addresses security incidents and notification of affected people and required authorities, which is a different event from compelled disclosure. No readable customer agreement supplies a notice period, an exception for legally prohibited notice, or a process allowing the firm to contest a demand before information is produced.
No published term or policy addresses third party requests for customer data. This is usually found in the confidentiality section of a master agreement, and no agreement of any kind is published. The site footer carries a privacy policy and a sitemap and nothing else. Nothing on the security page or the AI Draft page says what happens when a subpoena, court order or regulatory demand reaches drafts or precedents held in the platform.
No commitment to notify, reservation of discretion over notice, or transparency report is published. The platform holds a firm's own precedent library and its live transaction drafting for named clients.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
The customer's own agreements, precedents, and approved clause library are the principal material. Curate compares uploaded examples and lets a lawyer choose the wording that will become a reusable standard. The product does not identify a licensed legal authority collection or a publisher supplying case law behind its drafting output. A firm's rights to use its source material and the currency of that language remain separate from the platform's ability to assemble documents.
The vendor names the sources of its automated suites: the Property Standardization Group for the Scottish real estate suite, the MCL drafting committee and curated content from Gowling WLG for commercial real estate, the CVCA model form documents for the Canadian venture capital suite, and APLMA for Asia Pacific facilities agreements. The Canadian automation is said to be fully maintained in line with changes to those model forms.
No licensing or permission position is published. Nothing says on what basis that third party content is reproduced and automated; the only related statement is a general security page commitment to compliant processing and respect for third party intellectual property rights. AI Draft is separate: it generates new content using the vendor's own knowledge lawyers' expertise rather than retrieving from these sources.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
Avvoka does not describe a citator or automated analysis of subsequent treatment of legal authority. Its primary outputs are assembled agreements, negotiated drafts, and comparisons of contract language. Updating a clause centrally can improve consistency across future drafts, but that is a content maintenance process rather than a determination that cited law remains valid. Lawyers must establish the legal currency of the provisions they approve and any authority incorporated into them.
The product neither retrieves nor cites primary law, and nothing on the AI Draft page, the security page or in the platform material addresses checking authority for later history. Its outputs are assembled and generated transaction documents, and AI Draft writes new contract language rather than authority a user would need to verify. One related practice bears on currency. The automations are maintained by the vendor's professional support lawyers, and the Canadian suite is said to be fully maintained in line with changes to the CVCA model form documents.
That is a named team keeping templates current against a named outside source, which is maintenance of drafting content rather than a check on legal authority.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
No abstention response is specified for when a model lacks enough support for a synthesis or proposed template. Curate requires a lawyer to approve each clause, and MassDraft identifies input inconsistencies before bulk generation. Those controls expose work for review without describing a confidence threshold or an automatic route for every unsupported result. Clause locks constrain permitted document changes; they do not show that a model can recognize when its proposed wording is unreliable.
Nothing on the AI Draft page, its FAQ, the security page or the AI Draft blog post describes what the system does when it cannot produce a reliable output. Its FAQ lists what AI Draft gets wrong. Users must check cross references, because the AI does not yet match references to other clauses automatically, check definitions used but not defined elsewhere, and verify legal and commercial effectiveness. That is a published account of known failure modes, not a description of uncertainty behavior.
Nothing says whether the system signals low confidence, declines a task it cannot complete, or behaves differently when the matter context is thin, and no confidence indicator or abstention path is described. The one hard constraint published is a design limit rather than a probability: AI Draft cannot change the content the rules generate.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No reported citation fabrication incident naming Avvoka or Avvoka Limited appears in the AI Hallucination Cases database reviewed on October 16, 2026. The product primarily assembles approved contract language, but AI assistance with synthesis and template creation still requires verification. The absence of a named reported incident says nothing about whether every generated clause is accurate or suitable, and it does not replace professional review of legal authority used in an agreement.
The AI Hallucination Cases database maintained by Damien Charlotin records no case naming Clarilis, AI Draft or Clarilis Limited, and no court order, opinion or disciplinary record naming the product or the company is on the public record. This is a statement about the public record rather than a finding about the product. The database records hallucinated authority in court filings, and this product generates transactional drafting rather than citations to authority.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Professional responsibility is engaged in general terms, and no authority is named. The legal advice disclaimer uses the vocabulary of the professional rules. Avvoka is not a firm of solicitors, does not practice law and does not give legal advice; there is no solicitor client relationship; it is no substitute for a solicitor's advice; and information provided to it does not attract legal advice privilege. Naming privilege and the solicitor client relationship goes beyond a bare disclaimer.
No Solicitors Regulation Authority guidance, code of conduct, bar rule or ethics opinion is cited anywhere, and no jurisdiction is named, although the company operates from London and Singapore. Nothing sets out what a firm must do to meet its own supervision and competence duties when generated drafting reaches a client.
Clarilis says it has signed the Litig AI Transparency Charter, links to it, and describes it as reaffirming a commitment to the safe, ethical and transparent adoption of AI in the legal sector. It also describes the charter as setting out commitments for organizations developing and providing legal AI while safeguarding ethical and professional standards. Litig is a legal technology innovation group, and the charter binds vendors, not practitioners: it is not a bar, law society or regulator instrument, and it does not set out what a solicitor must do.
No Solicitors Regulation Authority guidance, Law Society material, code of conduct or ethics opinion is named, and no jurisdiction is identified although the product serves six.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Time savings are the central promise, and nothing addresses the billing consequence. The site offers templates in hours and days rather than weeks and months, contracts created in minutes, less manual work, lawyers freed from repetitive work to focus on strategy and clients, and MassDraft for large repapering projects. None of it says what happens to the bill when a day of drafting takes an hour. No record of AI assisted work by matter is described, no fee or disclosure guidance is published, and nothing addresses what a client is told when the platform assembled and drafted a document.
The analytics layer comes nearest: it tracks document activity, negotiation patterns and individual negotiator performance across a portfolio, so the data on who did what exists. It is presented as a tool for better drafting and client value, not as a billing or disclosure record.
The vendor says the platform cuts the time to produce document suites by around ninety percent, and states the commercial effect plainly: customers improve margin, increase capacity, provide superior client service, aid recruitment and retention, and mitigate risk. The law firm page adds that Clarilis improves cost effectiveness and helps firms gain competitive advantage. No per matter record of AI assisted work is described, no guidance on fee or disclosure treatment is published, and nothing addresses whether a client should be told that parts of their transaction documents were generated rather than drafted.
The product does mark AI content inside the delivered document, which could support such a disclosure, but the marking is meant for the drafter's review rather than the client's information.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
Avvoka publishes an information security policy and offers penetration test results to customers, but does not publish a complete model provider register or a client consent pack. Curate's promise against training a shared model provides one useful statement for client discussions. Infrastructure names and assistant integrations do not identify every processor receiving content. A firm would still need contractual and configuration details to answer a client's requirements for AI use, subprocessors, and disclosure.
The AI Draft FAQ says Clarilis uses a range of models depending on the drafting task and currently prefers OpenAI's model hosted in Azure. The same page commits that neither user inputs nor AI responses train the models, that processing uses zero data retention endpoints, and that data is hosted in the customer's region. The security page names AWS and Azure as the platform's infrastructure and gives the ISO 27001 certificate number.
Those public pages name who processes content and on what terms. No subprocessor register, data processing addendum or client notification material is published, and no agreement of any kind is on the site.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Nothing addresses producing a record of AI assisted work. The platform keeps a thorough drafting history: it saves every version, records how each clause is marked up, tracks every decision as a deal progresses, and reports negotiation patterns across a portfolio. None of it separates machine generated text from human drafting. Nothing identifies which model produced a clause, nothing marks generated language once it is in the document, and no export attributes authorship for disclosure to a client, counterparty or tribunal.
What is captured is document change, not model authorship. No disclosure template or guidance is published, and with no customer agreement there is no contract term on it either.
Where a document contains AI content, a notice at the top says the AI content needs review, and every inserted AI clause is highlighted. Unlike an audit trail inside the platform, that marking survives export into Word and reaches anyone the draft is sent to, so a firm can show which passages were machine generated without reconstructing anything. The security page frames the same feature as a responsible AI commitment: clear content indicators that separate AI and rules based drafting.
No model or version is identified against the marked content, nothing records that the required review was done or by whom, and no export or report is described for giving an account of AI use to a client, counterparty or tribunal. The marking is also plainly meant for the reviewing lawyer and would usually be removed before the document is sent.
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.
- AI Liability and Recourse
- Commercial Transparency
- Third Party Request and Subpoena Notice
- Good Law Verification
- Refusal and Uncertainty Behavior
Product updates
The latest logged changes from each vendor, newest first, each linked to its source.
Avvoka
-
Integration / interoperability
Avvoka launched headless Massdraft, which lets lawyers run its bulk document generation and signing workflow from Harvey, Legora, Claude or Copilot.
Source -
Product / capability
Avvoka opened early access to headless templating, which lets an AI assistant connected to Avvoka build document templates as well as draft from them.
Source -
Product / capability
Avvoka launched Curate, a standalone product that reads a firm's historical transaction documents, extracts the clause variations that performed best, and generates templates from them.
Source
In summary
Avvoka
Avvoka, based in London with an office in Singapore, turns a firm's precedents into automated templates and carries each document through negotiation to signature. Users build questionnaire driven drafts without coding and negotiate with counterparties in one live document with locked clauses. They sign in platform or through Docusign and Adobe Sign, while negotiation analytics show how clauses are marked up across a portfolio. According to the AI Legal Index, Avvoka holds ISO 27001 since 2017, hosts in the UK, Europe, the US or Australia, and has a published partnership with Harvey.
Clarilis
Clarilis, from Birmingham, England, automates whole suites of transactional documents. A lawyer answers one questionnaire and receives a complete first draft and its ancillary documents in Word, in house style. Clarilis's own professional support lawyers build and maintain the automations across real estate, corporate, banking and private client work. Its AI Draft layer writes the remaining deal specific content, highlights it in the document for review, and can be switched off. According to the AI Legal Index, Clarilis states ISO 27001:2022 certification by BSI and names OpenAI hosted in Azure.
Questions buyers ask
Avvoka vs Clarilis: which is better for transactional document automation?
They do different jobs once the questionnaire is answered. Avvoka carries a document through negotiation and signature and measures how clauses are negotiated. Clarilis builds and maintains whole deal suites for the firm and marks every AI written clause in the delivered document. Firms without their own automation team will find more that fits in Clarilis. From the AI Legal Index, based on each vendor's own published materials as of September 25, 2026. No vendor pays for placement.
Does Clarilis train AI on client documents?
No. Clarilis's AI Draft page states that neither user inputs nor AI responses are used to train the AI, and its security page adds that processing runs in region through zero data retention endpoints. The commitment sits on product pages. From the AI Legal Index, based on each vendor's own published materials as of September 25, 2026. No vendor pays for placement.
How does Avvoka's negotiation analytics work?
Because Avvoka stores clauses as structured data rather than free text, it records how each clause is marked up across a firm's portfolio. It produces heatmaps of what changes, how often and where, reports on pushback against standard positions, and comparisons of how individual negotiators perform, so a firm can revise its precedents against what happens in negotiation. From the AI Legal Index, based on each vendor's own published materials as of September 25, 2026. No vendor pays for placement.
How does Clarilis mark AI written content?
Every clause AI Draft inserts is highlighted in the delivered Word document, and any document containing AI content carries a notice at the top that the AI content requires review. Clarilis tells users to check cross references, undefined terms and legal effect, and firms that do not permit generative AI can switch AI Draft off. From the AI Legal Index, based on each vendor's own published materials as of September 25, 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.
Three points to weigh. Neither vendor publishes a terms of service, customer agreement or data processing addendum, so neither page can state a liability position. The commitments quoted here sit on product and security pages. Avvoka's GDPR policy describes older hosting, in the UK and France with OVH, than its security page does. Clarilis's own figure of drafting about 90 percent faster carries no named firm or method. Neither vendor reviewed this page.