Draftwise vs Sonar Legal: how they compare in 2026
The choice turns on whether a firm is organizing its accumulated deal knowledge or equipping lawyers for daily drafting and document preparation. Draftwise connects precedent repositories to Word, creates playbooks from deal history and uses Ontonomi to connect clients, matters and contractual relationships with a trail back to source material. Deal Table analyzes terms and obligations across the portfolio, while Knowledge Console controls the collections and approved guidance used by the team. Sonar Legal starts with the active Word agreement and adds clause drafting, cited playbook findings, definition navigation and house style formatting. Its Outlook add in handles correspondence, and its web application adds knowledge hubs and tabular review. Draftwise makes institutional precedent a shared foundation for transactional work; Sonar combines legal revision with the practical work of preparing agreements and emails.
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.
Draftwise uses a firm's deal history to draft, review and negotiate agreements in Word. Its agent interprets redlines and comments, follows version history and applies precedent to new drafting tasks. Playbook Studio creates rules from example agreements and representation instructions, while Deal Table extracts terms, risks and obligations across the contract corpus. Ontonomi connects clients, matters, contractual relationships and positions into a structured model whose answers trace back to source material. Knowledge Console controls the collections and guidance available to these workflows. The underlying document management system remains the firm's existing repository; Draftwise supplies the intelligence that turns that material into proposed legal work.
Sonar Legal combines AI drafting and review with everyday Word tools for definitions, error detection and formatting. Partner analyzes the open agreement, drafts clauses, prepares memoranda from attached research and responds to counterparty comments. Playbooks turn precedents or instructions into review rules, and Tables extracts selected fields across contract sets. The drafting workflow can compare a response enriched by a clause knowledge base with one generated without it. Definition navigation and parts of the document interface remain useful independently of generative output. Formatting also uses AI to suggest styles before a user applies them, so automation extends beyond writing new contract language.
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.
Ontonomi resolves questions through a structured map of the firm's legal relationships and shows the exact memo, clause or agreement behind each answer. This supplies an inspectable trail through the material used for the result. The drafting workflow also uses selected precedent from the document management system, and negotiation comparisons can draw on EDGAR filings. Playbook Studio lets a reviewer inspect citations while editing and exporting the marked agreement. Accuracy and repeatability are asserted without a reproducible test set, error rate or account of unsupported questions. Those assertions should be distinguished from the source links, which establish where an answer came from rather than whether it is correct.
Partner answers from the open agreement and attaches citations to its analysis. Playbook results show a pass or fail for each rule, a supporting contract passage and proposed replacement text. Tables links each extracted result to the exact clause or section and lets a reviewer correct it. For clause drafting, Jina embeddings identify relevant knowledge base clauses that accompany the request to the language model. The web application also returns citations for legal research across more than 100 jurisdictions, but the underlying law collections and update schedules are unspecified. There is no reproducible accuracy test covering those research answers or the contract extraction workflow.
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.
Playbook Studio turns uploaded example contracts and representation instructions into proposed rules that the user can refine and save. Running a review produces redlines, with a surface for inspecting citations, making manual edits and exporting the marked agreement. Knowledge Console lets administrators control collections, user access and approved playbooks across the organization. These functions give lawyers and knowledge teams specific ways to influence and inspect the work. The drafting agent also performs work across deal history and whole agreements, but its stop conditions and error escalation route remain unspecified. There is no complete account of which wider agent actions require separate approval.
Users initiate AI requests and decide when to insert or replace text in Word. Suggestions can become tracked changes or ordinary edits, with a chosen author and optional comment. Playbook creation pauses for clarification when instructions are ambiguous, and reviewers can exclude rules before running a check. Results have severity labels and individual revisions. Formatting presents a paragraph by paragraph review table before Apply changes the file. Outlook separates reading a thread from composing a reply, and insertion requires Compose Mode. These are tangible review controls, but the wider agentic task feature lacks a complete account of escalation, failure handling and actions requiring approval.
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.
Orrick, Gunderson Dettmer, Mishcon de Reya, Mayne Wetherell and Sekri Valentin Zerrouk provide named accounts of using Draftwise. Orrick partner Zac Padgett describes extracting a market percentage from comparable deal agreements during final negotiations, while Mayne Wetherell's Cameron Reeves describes quicker access to curated precedent. These examples identify practitioners and the work performed without a dated measurement method. Playbook Studio separately claims first pass creation falls from more than six hours to five minutes and NDA review from an hour to two minutes. Those figures have no named customer, sample or evaluation method attached to the product page.
TWL Law Group managing partner Bob Tseng describes using Sonar Legal for cross border transactions and credits its practical workflow and hands on coaching with improved efficiency. The testimonial identifies both the firm and the legal buyer, but gives no dated before and after measurement. Sonar also reports that 44 percent of users use the product more than five times daily, without a population, observation period or measurement method. Its claimed reduction of up to 80 percent in model token consumption concerns operating efficiency, not a measured improvement in legal outcomes. Other deployment examples in its startup application leave customer identities undisclosed.
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.
Customer data does not train public models, and Ontonomi's customer owned model is not used to train a tool sold to another firm. The data policy also prohibits sharing firm intellectual property, including trained intelligence or aggregates. Live DMS permissions govern access, while private cloud and on premises options can leave encryption keys with the firm's IT team. These commitments support confidentiality but do not explain every model provider's access or retention. A customer subscription agreement is not available alongside the website terms. Privilege and work product protections are not expressly allocated, and private learning within the customer's own environment is distinct from the prohibition on shared training.
The AI processing policy limits submitted text to the requested response and rules out training, fine tuning and future improvement by Sonar or its model providers. Requests are isolated from other users' requests. Hosted knowledge bases have row level security, with customer hosted and dedicated enterprise alternatives. The Marketplace license adds confidentiality duties for customer data and limits disclosures to representatives with a need to know. Stored playbooks, knowledge and usage information sit outside the simple transient request description. Privilege and work product receive no specific treatment, and the permission model does not explain matter walls or how connected repository restrictions carry into retrieval.
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.
The product is aimed at transactional lawyers rather than a consumer seeking personal legal advice. It drafts agreements, applies precedent and analyzes negotiation positions, with lawyers able to inspect citations and revise proposed changes. Its ethical wall guidance discusses client restrictions, access control and material that should never reach AI. An explicit statement separating software assistance from legal advice remains unspecified, as do competence and supervision requirements across the jurisdictions served. The website terms disclaim accuracy in general commercial language. Those terms and the professional audience do not establish a jurisdiction specific framework for responsibility when generated contract language is wrong.
Sonar Legal targets legal professionals, including law firms and corporate counsel, and its interface keeps drafting and revision work inside familiar office applications. Partner interprets clauses, identifies risks, prepares legal memoranda and generates replies to counterparty comments. Those functions support legal judgment, while tracked edits and source links give the practitioner a way to inspect the result. An explicit boundary between software output and legal advice is unspecified in the product policy and linked Marketplace license. The claim of support across more than 100 jurisdictions does not identify limits tied to professional admission, competence duties or supervision of nonlawyer users.
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.
Knowledge Console organizes access to precedent, users, licenses and approved playbooks, while usage analytics show adoption and engagement. The ethical wall guidance adds live permission checks and restrictions on material that may enter an AI workflow. These are controls over a firm's knowledge and access, not a release assurance framework for the vendor's models. A named model risk owner, evaluation procedure before deployment and results across legal practices or populations remain unspecified. Information security policies assign responsibilities to the executive team and require regular review, but do not explain how incorrect legal answers are investigated or how model behavior changes are approved.
Playbook authors can express preferred positions, acceptable fallbacks and unacceptable terms, then revise the proposed rules before sharing them. The guidance explains how vague instructions can cause the model to weaken an already favorable clause. This is useful control over an individual review, rather than an organization wide account of model governance. Sonar describes secure development practices based on Microsoft SDL and OWASP, but those practices concern software security. A person accountable for model behavior, release evaluation procedure, incident review process for incorrect legal answers and results across languages or legal systems are unspecified. The broad jurisdiction and language coverage claims therefore lack corresponding quality comparisons.
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.
Encryption uses AES 256 at rest and TLS 1.2 or 1.3 for transport. CloudWatch collects operational logs with alerting and anomaly detection, retaining them for up to two years. The separate retention policy sets a general maximum of five years, subject to legal requirements, and deletes data when its applicable period ends. Playbook Studio promises to delete trial uploads after the trial finishes. Information security rules restrict employee access by business need and require escalation of unusually sensitive material. A named processor register, exact AI prompt lifecycle and customer breach notification timetable remain unspecified; the general privacy page's retention heading does not supply those missing periods.
AI requests pass through Sonar to selected model providers, with a promise that prompts and responses are discarded when the response is returned. Google Cloud hosts account services in Singapore, and Jina provides knowledge embeddings from Germany. Hosted knowledge bases, playbooks, templates and usage records have different persistence from those transient requests; application backups run hourly. The privacy policy retains information as needed without a fixed deletion schedule. Access protections include role based controls, account lockout, optional two factor authentication and remotely revocable sessions. A signed DPA is available on request. Specific backup erasure timing and a product incident notification timetable remain unspecified.
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 August 2025 website terms address access to the site and connected media rather than setting out a complete enterprise subscription agreement. They disclaim warranties of accuracy and completeness, exclude liability for direct and indirect damages arising from site use, and require the user to indemnify Draftwise for specified claims. They also disclaim responsibility for loss or corruption of transmitted data. No monetary cap appears in those clauses. An AI output warranty, customer indemnity and contractual remedy for a failed legal workflow are unspecified. A cyber insurance certificate is available by request; its cover and exclusions cannot be determined from the resource title.
The License Agreement link on Sonar's Microsoft Marketplace listing leads to Microsoft's standard publisher contract. That contract includes a warranty of substantial conformity with the product instructions and defense against intellectual property and applicable law claims, with exclusions for customer data, other products and unauthorized modifications. Subscription liability is capped at the greater of the preceding 12 months' fees or $500,000; certain customer data breaches have a higher cap, and defense obligations have exceptions to the limits. These are Marketplace acquisition terms, whose applicability to a separately purchased subscription is unclear. A specific warranty for correct legal conclusions or generated contract language is absent.
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.
Word is the drafting surface, and the connected DMS supplies agreements, clauses, tags and version history. Deal Table brings together material from iManage, NetDocuments, Google Drive and SharePoint to analyze terms and obligations. Ontonomi exposes its structured knowledge through MCP and APIs. The access approach checks the DMS using the individual lawyer's identity and live permissions, with access events intended to remain visible in the source system's audit trail. The product pages describe what those connections support, but do not provide an implementer's complete setup guide, synchronization schedule or field mapping. Customer cloud deployment also requires coordination with the firm's IT environment.
Word installation works through Microsoft Marketplace or administrator deployment to selected users and groups. Partner reads the active agreement and writes accepted clauses or replacements back into it, including optional tracked changes and author names. Outlook reads a thread, prepares responses and inserts text into a compose window, with a separate feature for visible revisions. Agentic email tasks require additional tenant administrator consent, which must be revoked separately when the add in is removed. OneDrive and SharePoint supply knowledge material to the web application. Email code authentication cannot enable features requiring Microsoft 365 consent, and older volume licensed Office editions lack the required browser component.
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.
A firm can use a dedicated private cloud on AWS, Azure or Google Cloud, deploy into its existing cloud, or run Draftwise on premises. For the private cloud option, the firm's IT controls encryption keys and auditing, vendor access is limited to support, and network access can be restricted to firm subnets. Existing cloud installation can use containers, virtual machine images or Linux binaries, with administration by Draftwise or the customer. These are concrete hosting and tenancy choices. The default statement that data stays inside the VPC does not separately identify the location of every language model inference service, so storage control is clearer than the complete AI processing geography.
Most Word processing takes place on the user's device, while explicitly initiated AI requests travel through Sonar's backend to model services. Google Cloud in Singapore hosts the manifest and authentication services, and the processor list places Jina embeddings in Germany. Hosted knowledge bases can use Google Cloud with row level security, a dedicated enterprise server or a customer's own environment. Dedicated application hosting is also an enterprise option. The locations used by Azure OpenAI, OpenAI, Anthropic, Vertex AI and optional OpenRouter routing are unspecified. The privacy policy permits transfers to Thailand and other jurisdictions, so local document editing does not mean every AI request remains local.
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.
Draftwise's trust center lists SOC 2 Type I, SOC 2 Type II and ISO 27001:2022, with an ISO certificate, a SOC 2 report and a penetration testing attestation dated January 22, 2026 among its resources. Access to the certificate and report requires a request, so their auditor, scope and coverage period are not visible from the listing alone. The FAQ additionally names Cyber Essentials Plus. These standards concern the company's security rather than the accuracy of generated legal work. The portal also lists a 2026 cyber insurance certificate and disaster recovery testing material, with the underlying terms subject to access.
Sonar describes encrypted transport, secure WebSocket connections, role based access, device management and regular security testing. Its internal access practices include hardware security keys, while customer sessions can use two factor authentication and are revocable. The architecture follows Microsoft SDL and OWASP guidance, which are development practices rather than independent company certifications. The processor page refers to SOC 2 Type II certified infrastructure for Jina embeddings, but does not establish an attestation covering Sonar's own application and operations. A named auditor, certificate or report period for Sonar is unspecified. Technical security explanations and the DPA request route are available without a sales demonstration.
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.
Ontonomi supplies a structured legal knowledge model over the firm's clients, matters, agreements and negotiated positions. It connects those relationships and traces answers back to their source clauses or memoranda, while the drafting system applies precedent and review rules to Word agreements. This describes the knowledge architecture supporting the AI workflows. The language model providers and versions remain unnamed, as does the allocation of individual tasks among models. AWS, Azure and Google Cloud are hosting choices rather than an identification of inference suppliers. The promise against training public models does not establish where each provider processes a request or how substitutions are communicated.
The AI provider list names Microsoft Azure OpenAI, OpenAI, Anthropic and Google Vertex AI. Customers can choose or exclude providers, and optional OpenRouter routing supplies an alternative when the primary provider is unavailable. Sonar says it disables providers that permit training and opts out of OpenRouter prompt and completion logging. Jina creates embeddings for clause retrieval before selected knowledge accompanies the drafting request. The guide describes direct and routed workflows, but does not identify model versions or map each feature to an exact model and processing region. A commitment to notify customers of every model substitution is also unspecified.
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.
Draftwise requires a sales discussion for product pricing. A rate, charging unit, tier structure, deployment fee and enterprise minimum are unspecified across the core product and FAQ. Playbook Studio has a free trial registration route and promises deletion of uploaded material when that trial ends, without stating an ongoing subscription price there. The website terms describe card, wire and ACH payments, recurring billing and cancellation at the end of the paid term. Those payment mechanics do not establish the cost of a firm deployment. Private cloud, existing infrastructure and on premises arrangements also lack a stated implementation charge.
A permanent free plan includes unlimited definitions, ten monthly Error requests, ten Partner requests and five uses of Sonar playbooks. Value costs $61 per user monthly or $49 per month with annual billing, covering 100 Error and Partner requests and 50 playbook and formatting requests monthly. Premium costs $99 monthly or $79 per month with annual billing and adds unlimited Word usage plus Outlook. Those plans restrict playbooks and formatting to Sonar's supplied options. Enterprise uses a quote and adds the web application, custom playbooks, house styles and a prompt library. Implementation charges and a standard cancellation arrangement for direct subscriptions are unspecified.
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.
Large and midsize law firms and corporate legal teams use Draftwise for transactional work. Its in house examples span advertising technology, defense contracting, investment funds, life sciences, real estate and software companies. Ontonomi adds concrete relationship models for funds and side letters, acquisitions, lending arrangements and corporate contract obligations. Named customers include Orrick, Gunderson Dettmer, Mishcon de Reya, Mayne Wetherell and Sekri Valentin Zerrouk, reflecting practice across several legal markets. The depth of precedent available depends on the firm's own connected corpus. Unsupported agreement types, jurisdiction boundaries and the extent of support beyond transactional practice remain unspecified.
The product serves solo practitioners, small and midsize firms and corporate legal departments, with Word and Outlook as the main working environments. Its practice examples include corporate transactions, acquisitions, commercial contracts, financing, litigation and tax. Tables handles bulk agreement review, while knowledge hubs reuse internal precedents and memoranda. Sonar claims legal research across more than 100 jurisdictions and formatting templates for over 150 languages, including bilingual layouts and Asian scripts. Specific legal source coverage and comparative performance by jurisdiction are unspecified. The installation guidance provides concrete Office version limits, and custom knowledge, playbooks and styles belong to the enterprise offering.
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?
Customer material is excluded from training public models, and Ontonomi says the firm's data never trains a tool sold to another firm. The customer owns its ontology and the information within it. The FAQ also prohibits disclosure of firm intellectual property, including trained intelligence and aggregates. These are product policy commitments rather than an express training clause in a customer subscription agreement. They do not prohibit learning confined to the firm's own environment or identify every external model provider's terms.
Sonar's AI policy says submitted text is used only to generate the requested response, with no reuse for training, fine tuning or future improvement by Sonar or its model providers. Optional OpenRouter routing excludes providers that allow training, and prompt logging is disabled. The Marketplace license protects customer confidentiality but does not expressly prohibit model training. The separate privacy policy allows service improvement using account, usage and uploaded template information, without overriding the more specific AI request promise.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
A general retention policy sets a maximum of five years unless legal or regulatory requirements require longer, with the actual duration varying by dataset and purpose. Operational logs can remain for up to two years. Playbook Studio trial uploads are deleted when the trial ends, and the security program includes data deletion when customers leave. The precise period for production prompts, generated drafts and residual backups is unspecified. Customer hosted deployment also puts some storage under the firm's administration.
For AI requests, Sonar promises to discard the input and generated response immediately after returning the result, without keeping a prompt archive or cache. That fixed zero retention statement concerns the processing path. Playbooks, house styles, hosted knowledge bases and usage records can persist separately, with information kept as needed under the privacy policy and hourly application backups. Their deletion periods are unspecified. The general website claim of no metadata retention is broader than the usage logging described in the privacy policy.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Ontonomi enforces identity across connections and mirrors DMS permissions live. Draftwise's ethical wall guidance describes checking access as the individual lawyer at the time of each request, rather than relying on permissions copied at ingestion. It also describes blocking selected client, matter, document or clause material from AI and preserving access events in the source DMS audit trail. Knowledge Console controls collections and users, but the source repository remains the authority for whether a person can see a particular file.
A playbook can remain private or be shared with every member of an organization; only its owner can edit a shared playbook. Standard hosted knowledge bases use row level security, and enterprise customers can have dedicated storage or host knowledge themselves. AI requests are processed separately and are not combined with another user's request. The Microsoft connection requires authorized users and tenant consent, but repository permission inheritance at retrieval time and formal matter conflict walls are unspecified.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
The privacy policy permits disclosure of personal data in response to lawful public authority requests, including national security and law enforcement demands. Where law permits, Draftwise limits the disclosure to what is legally required. It does not commit to telling the customer before responding or describe a request transparency report. Private deployment may affect which material the vendor possesses, but does not itself create a notification obligation. A separate negotiated customer agreement could contain additional terms not available in the website policies.
The publisher contract linked from Sonar's Microsoft Marketplace listing requires notice before legally compelled disclosure, when notice is lawful, so the customer can seek a protective order. The same contract requires prompt notice of unauthorized use or disclosure of confidential information. Its scope is Marketplace orders. Sonar's own privacy policy separately permits disclosure required by law, regulation or court order without a corresponding notice sentence. A general request transparency report and equivalent direct subscription terms are unspecified.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Draftwise draws principally on a firm's agreements, clauses, tags and deal history, with EDGAR filings used for market comparisons. Ontonomi links those materials into a map of relationships and negotiated positions. Neither customer precedent nor filed commercial agreements identifies a collection of primary case law or legislation behind legal research answers. A primary law corpus, licensing basis and update schedule are unspecified. The cited source trail serves contract knowledge and negotiation work rather than a law publisher collection.
The web research service claims coverage of more than 100 jurisdictions in their native languages, but does not identify the underlying court, legislation or publisher collections. Its drafting knowledge base contains more than 50,000 selected clauses, and customers can add their own agreements and memoranda. That clause library is not an identified primary law collection. Source citations help the user inspect an individual answer, while acquisition rights, refresh schedules and jurisdiction by jurisdiction completeness remain unspecified.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
The workflow compares contractual positions and retrieves precedent from earlier matters. EDGAR benchmarking can show how a term appears in filed agreements, and Ontonomi traces a result to the clause or memorandum behind it. Neither function establishes whether a judicial authority remains good law. A citator, subsequent history method or status warning for overruled decisions is unspecified. The product is primarily aimed at transactional drafting and negotiation, so its market comparisons should not be treated as legal authority checks.
Legal research answers include citations, and the litigation offering refers to statutes, precedents and case law. Neither that description nor the research workflow identifies a commercial citator, a subsequent history calculation or an indicator that an opinion has been overruled. Contract passage links in Partner and Tables address a different question: where the answer or extracted field came from. They do not establish the continuing authority of a court decision used in a memorandum.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Ontonomi promises repeatable answers with a trace back to source material, while Playbook Studio lets a lawyer inspect citations and edit proposed redlines. A defined response when the required support is absent is unspecified. There is no stated abstention message, calibrated uncertainty display or escalation rule for a drafting request that the firm's precedent cannot support. A source trail can help a reviewer investigate an answer, but does not by itself describe what the system does when it should not answer.
When building a playbook from instructions or precedents, Sonar pauses and asks clarification questions if the instructions are ambiguous. The rule guidance also explains how an imprecise payment or confidentiality requirement can produce unwanted edits and shows how to preserve acceptable terms. These are concrete uncertainty controls for playbook construction. A comparable no answer path for unsupported legal research questions is unspecified.
High, medium and low labels in review results describe issue severity rather than calibrated confidence in the model's answer.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court incident naming Draftwise was identified in the AI Hallucination Cases database on October 16, 2026. Draftwise's main work concerns contractual precedent, negotiation and deal analysis rather than preparation of litigation filings. Its expanded source trails and editable review results give practitioners material to inspect, but do not establish an absence of errors in generated work. The incident result concerns records that name the tool and is separate from a controlled assessment of citation or drafting accuracy.
No court record naming Sonar Legal or its former AutoDox name was identified in the AI Hallucination Cases database as of October 16, 2026. The product generates contract language and also offers research and memorandum assistance, so citations can enter legal work through several features. This result concerns identified court incidents, not a test of citation accuracy. Contract source links and the ability to inspect research citations do not establish that every answer is correct or current.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Draftwise's ethical wall guidance addresses the firm's responsibility to enforce client restrictions, live access permissions and limits on sending material to AI. It discusses protective orders, client guidelines and the risk of creating a second permission system outside the DMS. The article presents these as standards Draftwise follows, without mapping them to a named bar opinion or a jurisdiction's professional conduct rules.
Competence, billing and client disclosure obligations are not translated into a complete product specific compliance guide.
Sonar is built for legal professionals and provides review controls such as tracked changes, source citations and editable playbook rules. Its compliance materials discuss privacy, security practices and Microsoft deployment requirements. They do not map the workflow to named bar opinions or jurisdiction specific duties concerning competence, supervision, confidentiality or disclosure of AI use. Broad research coverage across many jurisdictions is a product coverage claim and does not establish alignment with each jurisdiction's professional conduct requirements.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
The product emphasizes faster preparation, contract review and access to a firm's negotiated precedent. Named practitioners describe spending less time finding language and extracting deal insights, while Playbook Studio gives time reduction figures for creating and applying playbooks. Knowledge Console tracks adoption and engagement, but does not describe a client billing record that distinguishes AI work from a lawyer's review time. Treatment of saved time, subscription charges and AI assisted tasks on a legal invoice is unspecified.
The law firm offering emphasizes faster drafting, formatting and review, with TWL Law Group describing efficiency in cross border work. Sonar's pricing and token efficiency claims address the software cost rather than how a lawyer charges a client. Usage analytics can count generated clauses, errors and active users, but no client invoice record separates machine effort from lawyer review. Guidance on passing subscription charges through, reducing time entries or describing AI assisted work on a legal bill is unspecified.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The trust center offers security reports, certification, testing and insurance material through an access request, while privacy, information security and retention policies can be read directly. Ethical wall guidance discusses client restrictions and blocking material from AI. Those materials support procurement review, but a client disclosure package naming model providers and their processing locations is unspecified.
A complete named subprocessor register is also absent from the accessible policy pages. The available reports require the firm's own assessment against each client's instructions.
The processor register names Google Cloud in Singapore and Jina in Germany, alongside the available language model providers and optional OpenRouter routing. Technical pages explain local processing, request transmission, authentication and knowledge hosting options. A signed data processing agreement is supplied on request. These materials can inform a firm's vendor assessment, but they do not form a client specific AI disclosure package. Exact model versions, all inference regions and a template for client approval remain unspecified.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Ontonomi ties answers to the source clauses, memoranda and agreements used in its reasoning. Playbook Studio supports citation inspection, manual editing and export of a marked agreement. The access approach also preserves DMS events under the individual user's identity, while CloudWatch logs operational activity separately. These records capture parts of source use and revision work, but do not form a complete court disclosure history identifying model versions, prompts and lawyer approval for every output. A filing template or dedicated certification export is unspecified.
Word users can apply an AI revision as a tracked change with a chosen author and optional comment, or insert it without tracking. Playbook results include the supporting contract passage and the proposed replacement. Tables links extracted values back to their source, and Outlook has a separate feature for visible revisions. These features preserve parts of review work, but do not create an immutable record of prompts, model versions and lawyer approval. A court disclosure export or filing template is unspecified.
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.
- UPL and Professional Responsibility Posture
- AI Governance and Bias Disclosure
- Good Law Verification
Which one fits
Choose Draftwise if
- The firm's negotiating history should inform work across many matters. Ontonomi connects legal entities and relationships, and its answers lead back to the agreements or memoranda behind them.
- Existing ethical walls need to remain authoritative. Draftwise describes live checks under each lawyer's DMS identity and restrictions on material that may be sent to AI.
- The knowledge team needs central control over precedent and guidance. Knowledge Console manages collections, users, playbooks and adoption analytics, while Deal Table compares contractual terms across the portfolio.
Choose Sonar Legal if
- Lawyers spend significant time repairing inherited formatting. Sonar's review table applies a selected stylesheet across the agreement, including support for bilingual templates and localized styles.
- Contract work regularly moves into correspondence. Sonar offers email thread analysis, response drafting and a tracked revision workflow directly in Outlook.
- A practitioner needs a small, defined starting package. Sonar's free tier includes limited Partner and playbook requests; individual paid plans expand usage before enterprise customization becomes necessary.
In summary
Draftwise
Draftwise applies a firm's own precedent to contract drafting and negotiation. Across connected matter knowledge and the individual lawyer's access rights, the AI Legal Index identifies Ontonomi's source trails and live DMS permission checks as distinct product features. Playbook Studio lets lawyers refine rules, inspect citations and export edited agreements. Deal Table spans iManage, NetDocuments, SharePoint and Google Drive.
Sonar Legal
Sonar Legal offers Partner drafting, rule based contract review and paragraph formatting inside Word. Its knowledge can include a supplied clause library or a customer's own material. The Outlook product adds email analysis and drafting, while the web application handles bulk extraction and internal knowledge hubs. A permanent free plan supports limited AI use before a paid individual or enterprise subscription.
Questions buyers ask
Can both products build a playbook from an example agreement?
Yes. Draftwise Playbook Studio creates rules from uploaded contracts and representation instructions, then lets the user refine them. Sonar can start from a precedent, the current agreement, instructions or a blank structure, with clarification questions when the intended rule is ambiguous. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
How do their repository permissions differ?
Draftwise describes checking the source DMS as the individual user with current permissions at request time. Sonar has private and organization shared playbooks, row level security for hosted knowledge and dedicated storage options, but does not explain live inheritance of OneDrive or SharePoint permissions for every retrieval. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does a private deployment keep every Draftwise AI operation in the same region?
Draftwise offers a dedicated private cloud, installation in the customer's cloud and on premises deployment, with customer control over keys in the private cloud option. The exact inference providers and processing regions remain unspecified. Those hosting choices do not establish the location of every AI request. 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 Sonar let a lawyer inspect extracted contract data?
Tables links a result to the exact clause or section from which it came, and a reviewer can correct the value. In its account of this extraction workflow, the AI Legal Index highlights that source jump and editable result. The feature complements Sonar's Word based drafting tools.
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.
Draftwise's website terms are separate from an unavailable enterprise subscription agreement. Sonar's Microsoft listing links a Marketplace publisher contract whose application to direct subscriptions is unclear. Neither vendor reviewed this page.