BlackBoiler vs ContractKen: how they compare in 2026
BlackBoiler is the closer fit when the main objective is to reproduce an organization's established negotiation behavior across recurring agreements. Its executable playbooks derive from prior edits and approved guidance, with each proposed change returned to Word for review. ContractKen offers a wider starting set for lawyers who also draft from source material or want a comprehensive check beyond their firm's existing playbook. It adds configurable local masking before model processing, while BlackBoiler has a stated SOC 2 Type II certification and defined upload allowances on its smaller plans. Neither standard agreement supplies a blanket ban on every improvement use of client content. The operational choice is therefore between repeatable organizational editing and a broader drafting and review toolkit, followed by the particular data terms governing that deployment.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
The product is an automated contract editing engine. It converts an organization's prior redlines, approved language and written guidance into executable playbook rules, applies them to a new agreement, and returns tracked changes and comments in Microsoft Word. There is no repository, workflow or signature product underneath that would work without the models. The June 2026 Veris release adds a generative, conversational layer for building playbooks and questioning clauses on top of the patented rules based editing engine, and both parts make up the product. The company says eleven United States patents cover document revision, playbook driven markup and clause handling.
Models classify clauses, compare negotiation positions, explain deviations and generate contract drafts or proposed edits. The current pipeline combines language inference, entity recognition, retrieval from approved material and generative models selected for the task. These functions are central to the review and drafting work. The Word application also retains useful nonmodel components: a shared clause library, playbook administration, formatting checks and reference validation. Users can organize approved language and maintain negotiation standards alongside the AI analysis. ContractKen thus joins model driven legal work to an established editing and knowledge workflow, rather than treating every formatting or storage operation as artificial intelligence.
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.
The vendor describes a four stage chain: evidence (the customer's prior redlines, approved language and guidance), logic (how those become executable rules), checking (a judge validator that assesses whether a proposed change fits the intended outcome, plus statistical similarity checks), and output (tracked edits and comments for lawyer review). The earlier ContextAI feature shows, for each redline, the playbook rule that prompted it and earlier examples of the same edit in the organization, a trail a reviewer can open for every proposed change. The vendor names failure modes: playbook coverage may be incomplete, contract language may depart from earlier examples, and unusual provisions may need a lawyer's fresh decision. The product cites no legal authority and has no citator; its output rests on the customer's own approved language, which is shown to the reviewer. No measured accuracy figure or test set is published.
Review findings connect to the relevant contract passage, and generated explanations draw on the customer's playbooks, clause library and prior agreements. Retrieval preserves section structure, definitions and cross references instead of splitting text without that context. Drafted clauses identify whether they came from a precedent, approved library language or a playbook requirement. Low confidence suggestions are flagged for review. The models undergo internal classification tests before deployment, but current numerical results, a reproducible test set and error rates for generated legal conclusions are not specified. A research result about similar legal models is separate from ContractKen's production accuracy.
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.
The system runs the first pass markup alone, producing tracked changes and comments. It is constrained by the customer's approved playbook positions, which the customer reviews and approves before use. The review surface is Microsoft Word track changes in the document the reviewer already has open. The reviewer decides what to accept, change, reject, escalate or negotiate, and the vendor says new risks, exceptions and negotiation decisions are left to the right reviewer. Nothing is applied to the agreement unless the reviewer accepts it, because the output is a proposal in tracked changes. Clause 3(b) of the Access Services Agreement says the same in contract terms: use of the Services is not a substitute for, and shall not replace, review and analysis by a lawyer. No marketing claims the system handles review on its own.
Playbook Driven Review checks preferred, fallback and walkaway positions; Comprehensive Review provides an alternative when no organizational playbook exists. Risk sensitivity can be adjusted, and the playbook framework distinguishes deviations that require escalation to a partner. Reviewers navigate to the exact clause, inspect an explanation and approve, modify or reject a proposed change. No edit enters the agreement without explicit human approval. Drafts receive a playbook compliance report before use, and administrators control who can change the playbook itself. These controls separate automatic analysis from the lawyer's decision about the final language and the route for an unacceptable negotiating position.
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.
Four testimonials are published, each attributed only to a first name and surname initial or to a verified user, in the style of review site content, and none gives an organization or a figure. The customer base is described in categories (AmLaw 25 law firms, Fortune 1000 organizations and several construction customers), but no customer is named anywhere and no case study, deployment figure or before and after measure is published. A 2021 AI Breakthrough award, a National Science Foundation SBIR award and Virginia Innovation Partnership Corporation portfolio status are recognition and funding rather than production use. Clause 12(c) of the Access Services Agreement bars either party from any public statement mentioning the other without written approval, so naming customers would need a waiver from each.
Named practitioners describe using ContractKen in contract work. Aseet Patel, a lawyer and legal technology founder, uses it for agreements and term sheets before sending work to outside counsel for final review. Sharon Zachariah, an innovation lawyer and former partner, describes using it after drafting or reviewing client contracts. These accounts identify people and actual tasks, but give no dated baseline or measurement method. Separate drafting illustrations promise substantial reductions in time to a first draft, and the review calculator estimates savings from assumed workloads. Those illustrations do not establish measured outcomes for either named practitioner or the current AI pipeline.
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.
Under clause 7(b) the customer owns all contract data, training of third party foundation models is barred without customer authorization, and use of customer data is limited to configuring, improving, supporting and operating that customer's own use of the service. The vendor also says customer data is not used to train models shared with other customers. Data is isolated per customer, with dedicated instances available for enterprise deployments, access is limited to authorized staff with controls and logging, and data is encrypted in transit and at rest. Mutual confidentiality runs five years, with trade secret protection lasting indefinitely. Privilege and work product are not addressed anywhere. No model provider is named, so whose model touches contract text, and what that provider keeps, is not stated.
The security commitments treat content as confidential work product, restrict staff access to necessary support under confidentiality obligations and separate customer tenants with individual encryption keys. The Moderation Layer masks sensitive text locally, offers a preview and validates the sanitized version before external model processing. Public or shared model training is excluded in the security FAQ, while the architecture also describes controlled feedback learning and private customization. The general terms reserve content review for service improvement. Retention and purge controls exist, but internal matter walls and a consistent contractual training restriction are not established across these different surfaces.
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.
Clause 3(b) of the Access Services Agreement, headed Review of Outputs and No Legal Advice, says use of the Services is not a substitute for, and shall not replace, review and analysis by a lawyer. Supervision and competence are addressed. The vendor sells to contract managers and procurement staff who are not lawyers, and says directly that a lawyer reviews the redline before anything moves forward and handles exceptions, new risks and negotiation decisions. The marketing never describes the product as giving advice; it consistently describes a first pass returned to a lawyer. Jurisdiction limits are not named anywhere. The only geographic limit is a website terms clause limiting site use to United States residents, which covers the website, not the service.
The terms distinguish ContractKen from a law firm or attorney and state that its information is not legal advice. They direct people needing advice to a licensed lawyer and do not create a professional relationship with the vendor. The product reinforces supervision through source inspection, playbook controls and required approval of generated changes. Its confidentiality explanation also engages with lawyers' duties under ABA Formal Opinion 512. Standard clauses include common law jurisdiction notes, but that coverage does not define a complete set of professional practice limits. The trial audience includes people who are not lawyers as well as legal teams.
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.
No AI governance position is published. Nobody is named as accountable for AI governance, no testing before release is described, no evaluation results are disclosed, and nothing addresses uneven output across contract types, counterparties or drafting styles. There is no responsible AI page, principles statement, model card, AI policy, ISO 42001 certification or outside governance assessment. The vendor does describe validation tools: a judge validator that checks alignment with the intended outcome, and statistical similarity checks. Those check individual outputs; nothing describes how the vendor builds, tests and answers for its models.
ContractKen describes a controlled model update process using feedback from accepted, modified and rejected suggestions. Those signals are aggregated and reviewed before supervised retraining, rather than changing the model instantly after each user action. Updated models face held out tests using precision, recall and F1 measures; performance must remain stable or improve before release. Administrators can also restrict sensitive information through redaction rules. This is a concrete development and release framework. A named person accountable for AI governance, current test results and findings about uneven performance across jurisdictions, contract types or groups are not specified.
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.
Customer data is kept for the length of the customer relationship unless agreed otherwise, and can be deleted at contract end or earlier on request. Access control is described in two documents. Access is limited to authorized staff who need it, with access controls and logging, and infrastructure access is secured by VPN, secure tokens and IP allowlists issued only to approved employees. Encryption is AES256 at rest and TLS in transit, backups are encrypted, and clause 7(b) confirms the customer owns its data and the vendor will not sell it. No subprocessor list is published, with only Amazon Web Services for hosting and Stripe for payments named, and no incident or breach notification practice appears anywhere. The vendor also discloses that individual client files may sometimes be downloaded temporarily onto an employee's encrypted hard drive for testing. No retention period is stated.
Administrators can request an immediate purge of contracts, prompts, logs and backups. Operational logs normally remain for 30 days, with a contractual option to set that period to zero. Enterprise controls include single sign on, administrator multifactor authentication and permissions for playbook uploads, draft review and data export. Staff access is restricted and logged. The security FAQ states continuous monitoring and material incident notification within 72 hours or a faster legal deadline. A complete current subprocessor register and the DPA require a request, and the default retention period for application prompts and generated output is not separately stated.
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.
Clause 9(a) of the Access Services Agreement covers third party claims that the Services infringe or misappropriate United States intellectual property, with the vendor controlling the defense and able to modify, replace or terminate. Clause 9(a)(iii) carves out unauthorized combinations, customer changes, Customer Data and Third Party Products. Clause 10 caps total liability at amounts paid or payable in the twelve months before the claim, with exceptions for breach of confidentiality, IP infringement, customer payment obligations and breach of the use restrictions. The agreement is explicit that output errors are the customer's risk. The IP indemnity does not reach output quality, clause 8 disclaims all warranties, and clause 3(b) defines the risk of relying on any edit, redline, comment, summary, suggestion or analysis as Customer's Assumed Risks. Clause 9(b)(ii) requires the customer to indemnify the vendor against third party claims arising from those risks. No insurance is mentioned.
The public terms disclaim accuracy, completeness and noninfringement warranties and cap aggregate liability at the greater of $100 or fees paid in the preceding 12 months. Exceptions concern death, property damage or injury from gross negligence, and fraud or fraudulent misrepresentation. Customers indemnify ContractKen for specified claims. The security FAQ offers a stronger position, including an IP indemnity, performance warranty, cyber and professional insurance and different liability exceptions. Paid customers may instead have an Enterprise Services Agreement, whose text is not available here. Those stronger commitments therefore do not clearly replace the default terms for every subscriber.
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.
The Microsoft Word add-in is the delivery surface. Review runs inside Word without moving to a separate tool, the playbook is chosen in the document, and output comes back as native tracked changes and comments for the reviewer to accept, change or reject. Single sign on and API access are listed as enterprise features, with nothing on what the API exposes or what a firm must configure. No document management, contract lifecycle or electronic signature platform is named as an integration partner. The vendor positions itself as sitting alongside a CLM where the CLM leaves a gap, and as handing back to the customer's existing process, but names no connection.
The Word add in reads the active agreement chosen by the user, rather than scanning other files or email. Review findings navigate to the underlying clause. Approved suggestions return through Office.js as ordinary tracked changes with explanatory comments, and the privacy mapping restores original names and values. Users supply their playbooks, precedents and clause language, then review output within the same document. Standard setup requires Microsoft Word and includes onboarding support. Integrations with systems such as iManage belong to the separately quoted custom workflow offer; they are distinct from the detailed, standard Word editing connection.
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.
The vendor says it uses isolation measures specific to each customer to keep customer data separate, that enterprise deployments may include dedicated customer instances and data separation controls, and that data is held in a silo open only to the client and necessary vendor staff. The service runs on Amazon Web Services, with production, staging and development all in AWS. No region is named, no choice of region is offered, no European or other non United States option is described, and processing location is not distinguished from storage. The vendor says expressly that it does not publish detailed architecture or infrastructure information.
The standard service combines a Word add in with a hosted analysis pipeline. Sensitive entities can be replaced locally before sanitized text reaches ContractKen's servers and external AI providers. Primary hosting is on AWS, with European Union or United States residency available on request. Regulated teams can obtain private inference in their own Azure tenant or virtual private cloud, and enterprise customers can supply an endpoint. These options distinguish local preparation from remote analysis. Exact cloud regions, the location of every provider's processing and the configuration or price differences between residency choices are not specified.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
The vendor says on two pages that it is SOC 2 Type II certified. No auditor, audit period, report date or scope is published, and no other certification is claimed: no ISO 27001, HIPAA attestation or public penetration test summary. The report is available to prospective customers on request through the sales or security review process. Further security materials and completed questionnaires are kept for enterprise evaluations, while team and individual subscribers are pointed to the public page. That public Security and Trust page has a seventeen question FAQ covering hosting, encryption, isolation, access, retention, deletion, backups and authentication, and carries no reports, dates or covered standards.
ContractKen describes SOC 2 Type II certification as in progress and its controls as aligned with ISO 27001 and ISO 27701. The security FAQ also mentions a report under a nondisclosure agreement, without identifying a completed audit period or service scope. Encryption, tenant isolation, administrator authentication, annual independent penetration testing and customer audit access are separate operating controls. Penetration test summaries and a security paper are available on request. Its own certification remains unfinished, without a dated independent audit, a named auditor or a defined assurance scope covering the ContractKen service.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
The vendor refers to generative AI throughout, and no model, provider or architecture is described beyond the four stage evidence, logic, checking and output framing. Clause 7(b) of the agreement allows Customer Data to be processed using third party infrastructure, technology and AI services, and separately bars training third party foundation models without customer authorization. So third party models are in the supply chain under the contract, and nothing identifies them. The Third Party Products definition gives only a generic example. Amazon Web Services is named, but as infrastructure, which says where a model runs, not whose it is. Stripe is a payment processor that never touches contract content and is routed outside the Word add-in and the conversational interface. No commitment to notify customers of a model change is published.
The architecture identifies DeBERTa for clause classification and natural language inference, plus spaCy and custom entity types for recognition. Generative models handle explanations and edits after retrieval from approved material. The security FAQ names OpenAI and Google as example API providers, while enterprise customers can bring their own endpoint. Routing selects models by task and can change as performance improves. Exact generative model families, versions and processing regions are not specified. The 30 day notice commitment concerns material changes to data handling or service levels, rather than every substitution of a model in the pipeline.
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.
BlackBoiler charges $125 per user per month for Starter or $1,250 per user per year with annual billing. Starter includes two playbooks and 25 monthly contract uploads. Pro costs $300 per user per month or $3,000 per year and adds five playbooks per user, 100 monthly uploads, analytics, administration and multifactor authentication. Enterprise has custom pricing for unlimited contract volume, single sign on, API access, playbook help, onboarding and negotiated service terms. A seven day trial requires a payment card and converts to the chosen subscription unless canceled. Setup charges for the larger deployment remain part of the enterprise quote.
The standard Word subscription costs $149 per user per month on monthly billing or $119 with annual billing. It has no minimum seat requirement and includes unlimited review and redlining, a clause library, playbooks, formatting, onboarding and training. A guided trial lasts 14 days, and cancellations or seat reductions can receive a prorated refund. Custom AI and workflow projects use a quoted proof of concept lasting eight to 12 weeks, including usage and customization. Standard installation is included; custom implementation support is also described as included, but the project fee and enterprise deployment price are not stated.
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.
Three buyer segments each have their own stated position: in house legal teams reviewing the same agreement types at volume, law firms applying set positions across client matters, and contract managers applying standards the legal team has already set. One industry has a dedicated page, construction and AEC contracting, supported by a claim of several construction customers. NDAs, service agreements and subcontracts are the recurring types the product is built for, with more complex contracts in scope subject to playbook coverage. The vendor states the product's limit: how useful it is depends on playbook coverage, the language and context of the agreement, and lawyer review. Practice areas are not addressed, since coverage is by agreement type and industry, and government use is not described; a United States Government Rights clause in the agreement concerns license rights, not coverage.
Law firms and internal legal teams can review commercial agreements, draft from prior transactions and maintain shared negotiation language. Examples include nondisclosure, service, software, employment, supply, lease and acquisition agreements. Prebuilt clauses cover common law jurisdictions including the United States, United Kingdom and Australia, with jurisdiction notes and tags for custom language. Separate playbooks can serve different teams, contract types or jurisdictions. Multilingual review is described broadly, but a tested language matrix and unsupported practice boundaries are not specified. The product centers on transactional drafting and negotiation; its clause guidance does not establish a general legal research or litigation service.
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?
The Access Services Agreement permits customer content to configure, improve, support and operate that customer's own use of BlackBoiler. Training third party foundation models requires separate authorization, and the security position excludes models shared with other customers. The own customer improvement permission is broader than that foundation model restriction. It does not require a separate opt in for every improvement use, and should not be read as a blanket prohibition on learning from contract content.
Section 8 permits review or editing of content for "operating and improving the Service" without a model training exclusion. The security FAQ excludes training public or shared models, while the architecture describes aggregated lawyer feedback used in controlled retraining and private customization. Another statement says no customer data trains models. The Enterprise Services Agreement may supersede the general terms, but its training clause is not available in the public agreement.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
The security page says data is kept for the length of the customer relationship unless agreed otherwise, with no period stated, and may be deleted at contract end or earlier on request. Deletion requests are handled subject to legal, security, backup and operational requirements. Clause 7(b) of the agreement also lets the vendor use and keep customer data to configure, improve, support and operate that customer's own use of the service, again with no period.
Deletion is a request the vendor processes under its own practices, not a setting the customer controls. The legal, security, backup and operational conditions on deletion have no stated limit, and nothing says how long backup copies last after a deletion request. Termination duties run one way: clause 11(c) requires the customer to delete or destroy the vendor's property and certify it in writing, with no matching duty on the vendor to delete customer data.
Administrators may request immediate deletion of contracts, prompts, logs and backups. The security FAQ gives operational logs a 30 day default and allows that period to be set contractually to zero. It does not separately define a default window for application prompts or generated answers. The privacy policy's period after account termination concerns personal information and does not establish how long AI interactions remain during active use.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
BlackBoiler separates customer data and offers dedicated instances and additional separation controls in enterprise deployments. Necessary vendor staff may access a customer's environment under authorization and logging controls. These protections distinguish one customer from another. They do not describe ethical walls among client matters within the same law firm or a retrieval connection that inherits a document management system's individual user permissions.
Customer tenants are logically separated and use individual encryption keys. Enterprise roles control who uploads playbooks, reviews drafts or exports information, and shared precedents are available to authorized team members. These controls separate organizations and administrative activities. A permission model that divides opposing matters within one firm, or carries a connected document system's ethical walls into retrieval at query time, is not specified in the standard Word workflow.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Section 6 of the Access Services Agreement allows disclosure of confidential information only as far as needed to comply with a court or government order or applicable law. It conditions that on the disclosing party first giving written notice and the chance to obtain a protective order. The commitment is mutual and is a condition on the right to disclose, not a statement of practice. No transparency report or count of requests is published, and no separate data processing addendum is published.
The commitment covers confidential information as defined in section 6, and the agreement does not separately address requests aimed at customer data, though customer data submitted under the agreement would normally fall within that definition.
The terms allow ContractKen to preserve or share information when reasonably necessary for legal process, law enforcement and protection of rights or safety. The privacy policy also permits disclosures in response to legal requirements. Neither sets out advance customer notice for a subpoena, a process for challenging a request or a transparency report. The separate security incident notice commitment concerns breaches and does not supply a legal demand notification policy.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
The editing engine uses the customer's earlier redlines, approved language and written guidance to build executable playbooks. ContextAI links a proposed edit to its playbook rule and examples from the organization's prior work. These are identified sources for a contract review rather than a licensed case law collection. The service does not give a separate inventory of foundational training corpora or the license terms of any underlying model provider.
Review and drafting use the customer's playbooks, clause library and prior agreements. ContractKen also supplies a library of commercial clauses and describes bundled language as authored internally, licensed or drawn from public domain material. Individual external sources and their rights are not listed, nor is an update schedule for a primary law corpus. Jurisdiction notes and refreshed sample language support drafting without establishing a comprehensive collection of legal authority.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
The product cites no authority. It proposes contract language against the customer's own approved positions and returns tracked changes in Microsoft Word; it does not retrieve cases or statutes, show citations or include a citator. What the product does check is different: the vendor describes a judge validator that assesses whether a proposed edit fits the intended outcome, plus statistical similarity checks against the customer's earlier examples, before the edit reaches the lawyer. That checks a proposed edit against the customer's standards, not legal authority against later history.
ContractKen can flag a precedent that no longer matches the team's current playbook and replace language from the approved clause library. It also traces generated clauses to their inputs. These checks concern contract standards and provenance, rather than the subsequent treatment of a judicial decision. A commercial citator connection, a method for checking whether authority has been overruled or an inline legal status warning is not specified.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
BlackBoiler warns that incomplete playbooks, unfamiliar language and unusual provisions can require a lawyer's fresh decision. Its first pass produces proposed Word changes and comments that a reviewer can accept, change, reject or escalate. Those review choices do not establish an automatic refusal when support is insufficient. A defined no answer response or a confidence threshold that forces escalation is not specified for the editing engine.
The interface flags low confidence suggestions and gives reviewers supporting sources, explanations and control over proposed edits. Playbook thresholds identify unacceptable negotiating positions and can send those issues to a partner. That escalation is about contract risk rather than unsupported answers. An explicit refusal response when retrieval cannot support a generated conclusion, or a published demonstration of the system declining such a question, is not described.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database contains no tool entry naming BlackBoiler or Veris as of October 15, 2026. BlackBoiler's output is a proposed contract redline supported by customer playbooks and prior edits, rather than a brief prepared for filing. That narrower workflow does not establish an error rate. The database result concerns named court matters and does not certify the correctness of proposed edits.
The AI Hallucination Cases database has no entry naming ContractKen as the tool behind fabricated legal citations as of October 15, 2026. Its stated work centers on contract drafting, clause review and proposed Word edits, with the lawyer approving changes. This court record concerns one specific kind of incident; it does not establish an error rate for those tasks or validate the accuracy of the current models.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Clause 3(b) of the customer agreement says use of the service is not a substitute for, and shall not replace, review and analysis by a lawyer. The public FAQ addresses competence and supervision directly. It says nonlawyers can apply standards the organization has set, but a lawyer reviews the redline before anything moves forward and handles exceptions, new risks and negotiation decisions. No named authority is engaged.
No bar ethics opinion is cited, no bar guidance is discussed, no regulator is named, and nothing maps the product to the conduct rules its buyers follow.
The Moderation Layer explanation addresses ABA Formal Opinion 512 and connects its confidentiality duties to local masking, user previews and logs of external AI requests. It discusses informed consent and also references several state bars, the SRA and the CCBE. It does not map the product to named opinions in multiple jurisdictions. These statements explain ContractKen's approach; they do not guarantee privilege or establish that every deployment satisfies a lawyer's duties.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
The vendor invites a buyer to weigh its subscription against how review is done today, citing internal reviewer time, repeated manual markup, outside counsel spend and available capacity. Its wider material says the software takes on the repeatable first pass to save time. That is a claim about the buyer's own costs. There is no record of AI assisted work by matter, nothing a firm could show a client, and no guidance on fee or disclosure treatment where AI has compressed billable time.
The buyer may be an in house team, a law firm or a contract manager. For an in house team the saving stays with the organization rather than passing through an invoice. For a law firm applying set positions across client matters, fee treatment is not addressed.
The privacy workflow logs who triggered AI analysis, what information went to which provider and when. Enterprise administrators can export document activity and enable prompt history exports, while Word preserves accepted edits and comments. These records identify parts of the assisted work performed on an agreement. ContractKen also markets shorter drafting and review times, but gives no corresponding guidance on recording billable hours, charging clients or disclosing the effect of those savings.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
No subprocessor list is published, and nothing says which model providers see client content. Clause 7(b) of the vendor's own agreement allows customer data to be processed using third party AI services and separately restricts training of third party foundation models, so third parties are in the chain and none is named. The named AWS hosting arrangement does not identify the language model suppliers handling a client's content.
Stripe is a payment processor that never touches contract content. No data processing addendum, AI disclosure pack, consent or notice template, or commitment to notify customers of subprocessor changes is published, and nothing says a subprocessor list or model provider statement is available on request. The security review process offers security materials and questionnaire answers.
ContractKen offers a DPA, current subprocessor register, security paper, data flow diagram and insurance certificates on request. Some assurance materials require a nondisclosure agreement. Its public security FAQ explains tenant separation, model provider restrictions and purge options, but is not a complete provider list or a client consent package. A firm can begin its assessment from those commitments, while the detailed materials for a client's AI requirements require direct contact.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Nothing published addresses court disclosure or verification certification. Nothing discusses court standing orders on AI use, no disclosure template or guidance is published, and no export gives the kind of record such an order would require. The product is transactional: it applies negotiation standards to commercial agreements before signature, and its output is a contract redline, not a court filing, so the question does not normally arise.
One element of such a record does exist. The vendor says each proposed edit can be traced to the playbook rule that produced it and to earlier examples of the same edit in the organization. That trail is a review aid inside the document, not an exportable record of model, sources and human verification, and nothing published presents it for disclosure.
Anonymized versions and interaction logs preserve the information sent to AI providers, while drafting identifies source clauses and Word retains accepted edits. Administrators can export activity logs and prompt history. These provide pieces of an explanation of how an agreement was produced. A single export tying each generated passage to the exact model version, retrieved sources and a named human verification step for a court certification is not specified.
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.
- Ethical Walls and Matter Segregation
- Good Law Verification
Which one fits
Choose BlackBoiler if
- Your legal team already has a substantial body of approved redlines and wants those recurring choices turned into executable rules.
- Reviewers want proposed Word changes tied to a consistent organizational playbook, with exceptions returned for judgment.
- A vendor stating completed SOC 2 Type II certification is necessary for the evaluation, subject to reviewing its actual scope.
Choose ContractKen if
- The same lawyer needs drafting from source material as well as review of incoming paper.
- A comprehensive clause review is useful when no sufficiently detailed firm playbook exists for the agreement.
- Your process benefits from masking sensitive terms locally before a model request and restoring them in the returned work.
In summary
BlackBoiler
BlackBoiler turns earlier redlines, approved clauses and written guidance into executable playbooks, then applies them to new agreements as tracked changes in Word. Veris adds a conversational way to create and refine those playbooks. A reviewer accepts, changes, rejects or escalates the proposed edits. The AI Legal Index identifies BlackBoiler's reusable editing rules and visible Word markup as the core of its recurring contract workflow. Starter costs $125 per user per month and includes two playbooks and 25 monthly uploads. The security position states SOC 2 Type II certification. Its agreement permits improving the customer's own service while requiring authorization for third party foundation model training.
ContractKen
ContractKen offers two review approaches inside Word: a firm's own playbook and a broader review against a library of more than 700 clauses. Its drafting tools can also assemble work from precedents and term sheets, while Surgical Redlines aim to change only the necessary language. The AI Legal Index identifies the choice between playbook review and comprehensive clause analysis as a distinction from a workflow built primarily around previously approved edits. ContractKen's standard review subscription includes unlimited review and redlining. Its Moderation Layer supports local pseudonymization, while enterprise arrangements can use private inference. SOC 2 Type II work is still in progress, and broader service improvement rights remain in the standard terms.
Questions buyers ask
How does BlackBoiler build a playbook?
It uses prior redlines, approved language and written guidance to form executable review rules. Veris provides a conversational way to build or revise those instructions. The resulting edits still return to a reviewer as Word changes and comments. From the AI Legal Index, based on each vendor's own published materials as of October 15, 2026. No vendor pays for placement.
What is the difference in review allowances?
BlackBoiler Starter includes 25 uploads a month, with higher allowances on Pro and custom enterprise terms. ContractKen's standard Review plan offers unlimited review and redlining. An allowance comparison still depends on the number of users and the agreements each team expects to process. From the AI Legal Index, based on each vendor's own published materials as of October 15, 2026. No vendor pays for placement.
Can either tool send a negotiated contract without lawyer review?
Both describe proposed changes that the reviewer checks. BlackBoiler expressly leaves acceptance, revision, escalation and negotiation to the reviewer. ContractKen uses playbook thresholds and escalation for issues outside the approved position. Neither comparison assumes that a generated redline is a completed legal decision. From the AI Legal Index, based on each vendor's own published materials as of October 15, 2026. No vendor pays for placement.
Are customer contracts excluded from all model improvement?
BlackBoiler permits improvement of that customer's own service while limiting third party foundation model training. ContractKen permits operating and improving its service and describes controlled private learning. Both positions are narrower than unrestricted sharing, but broader than an unconditional prohibition on all improvement uses. From the AI Legal Index, based on each vendor's own published materials as of October 15, 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.
BlackBoiler and ContractKen are independent offerings. Neither vendor reviewed this page. BlackBoiler's stated certification and ContractKen's certification work in progress describe different assurance states.