Gideon vs LawDroid: how they compare in 2026

A conversational intake and CRM product with a genuine analytics model inside it, where the workflow rather than the model is what the buyer purchases. The chatbot layer is described as easy to build and driven by firm specified qualification criteria, and independent comparison material characterises the product as a chatbot bundled with an intake workflow tool where form data flows into Gideon's own CRM. That is configured conversational automation plus a CRM, and both function on rules rather than on generative capability. The genuinely model driven component is the predictive analytics engine, stated to learn a firm's preferences for particular case types and predict likely case outcomes, which is a real machine learning claim and is the vendor's oldest differentiator, present in its positioning since 2017. Held at C because removing the models leaves a working intake chatbot, questionnaire builder, scheduler, document generator and CRM, which is most of what a firm buys. Same placement as LawDroid and for the same reason: this category's products are automation platforms with models added rather than models with interfaces.

Two products with genuinely different centrality, and the record grades the composite honestly rather than the stronger half. Builder, the intake and automation product this category is about, is fundamentally a no code workflow and conditional logic engine: independent review states plainly that Builder draws on the workflows, templates, questions, logic and content the firm builds into it, and that it is not positioned as a broad legal research database. Chatbots built on decision trees and document assembly on conditional logic are deterministic automation, and natural language question answering sits on top as an addition. Copilot is the opposite and is genuinely model native, being an AI assistant with no function absent the model. LawDroid predates generative AI by years, having operated since 2016 when chatbot automation was rule based, and Copilot is described in independent review as a new product incorporating large language model generative AI into an existing repertoire. Graded C on the composite: the platform this category buys is an automation builder that now has AI in it, not a model that automation was built around.

Nothing published, and the axis applies in an unusual form on this record. The product generates no legal citations and performs no legal research, so the classic grounding question does not arise. What does arise is the accuracy of the predictive analytics engine, which is stated to predict likely case outcomes so firms can direct resources toward higher value matters, and that is a quantitative prediction about a real world result that is testable in principle and published nowhere. No accuracy figure, no calibration statement, no error rate on qualification, no evaluation and no methodology were located for either the prediction engine or the chatbot's answers to initial enquiries. A prediction engine whose accuracy is unstated is being relied on to decide which prospective clients a firm pursues, and neither the firm nor the consumer can assess it. Checked the home page, the blog material, the Clio directory listing, the CodeX profile and independent comparison material on 29 Aug 2026.

A research capability with no disclosed sources and an explicit third party warning. Copilot is stated to assist with case law research, and independent review states that the specific sources from which it retrieves case law are not explicitly detailed, that outputs should be treated as work product requiring attorney review, and that attorneys should verify results before relying on them. Unsourced case law retrieval is the highest risk configuration in legal AI and it is exactly the shape that produces fabricated citations. Nothing published by the vendor addresses grounding, citation to source, accuracy, hallucination rate, evaluation or benchmark. The Builder side compounds it differently: chatbots answer frequently asked questions using natural language over firm supplied content, and nothing states what happens when a question falls outside that content. Checked the Copilot product page, the home page, the Builder material and independent review on 29 Aug 2026.

Both directions are stated plainly and they sit in tension, which the note records rather than resolves. The vendor states that chatbots qualify leads and route them to the right attorney or staff person automatically, direct from the website, and expressly without any human intervention, which is an unambiguous autonomy claim about a system conversing with the public. It separately states that when a lead is qualified the relevant attorney or staff member is alerted immediately and can jump in to convert the lead in real time over messaging, which is a human takeover mechanism of the same shape credited on LawDroid. So a human can enter the conversation and the qualification and routing decision has already been made without them. Held at C rather than B because the takeover is described as a sales opportunity rather than as an oversight control, no trigger or threshold is published, nothing states what the bot may say unattended before a human arrives, and the decision that carries consequence for the consumer, being whether they are qualified at all, is the one explicitly performed without human intervention.

One published feature that directly answers this axis and is uncommon on the index. The vendor states human agent takeover, describing it as allowing a person to jump in and take over an automated conversation, with the framing that automation is good and automation plus the human touch is better. That is an explicit, named mechanism for a human to interrupt an autonomous process mid execution rather than review it afterward, which is a different and stronger thing than post hoc review, and it is the right control for a chatbot conversing with a member of the public in real time. Independent review reinforces the posture, noting output should be treated as work product needing attorney review. Held at B because nothing is bounded: no statement of what triggers a handoff, whether escalation can be automatic on a detected condition, what the bot does while waiting for a human, or what it may say unattended in the Enterprise tier where LawDroid builds and manages the chatbot on the firm's behalf.

Institutional recognition and funding are checkable, and customer evidence is absent. Verifiable without the vendor: a Stanford Law School CodeX startup profile featuring a named cofounder, Elan Fields, which is an academic legal technology programme rather than a marketing placement; a published integration listing in the Clio app directory, which required a partner relationship with the largest practice management vendor in the market; independent secondary market data reporting $11.5m total funding with a seed round in March 2026; and sustained independent comparison coverage assessing the product against named competitors. Longevity is real, with positioning documented from 2017. Against that: no law firm customer is named anywhere in located material, no case study, no usage figure, and no outcome claim with a figure despite the product being built around measurable conversion metrics, which is a conspicuous omission for an intake platform whose entire value proposition is lead conversion. Held at C on that split.

Independent review coverage is the substance, and customer evidence is thin. The strongest element is sustained assessment by a named legal technology publication that reviewed both products separately, verified pricing and integrations, and recorded specific limitations including that no secondary source library was verified for Builder and that Copilot's case law sources are not detailed. Independent review that documents what could not be verified is better evidence than a testimonial. The vendor operates since 2016, which is unusual longevity in this market, and holds a named affinity partnership with that publication. Against that: one customer quote is attributed to a named individual as CEO and Founder of LexBlog, and no law firm, legal aid organisation, court or government agency customer is named anywhere despite all four being stated buyer types, no usage figure, no case study and no outcome claim with a figure were located, and a major review platform profile shows zero reviews. Held at C on that split.

Nothing located. No confidentiality statement, no encryption reference, no data handling description and no treatment of privilege or prospective client confidences was found in any surface read. The gap is the category's central one and is sharper here than on LawDroid because this product retains the intake data in its own CRM rather than passing it through: consumers describe their legal problems to a chatbot on a firm's website, that account is captured, analysed by a prediction engine and stored in the vendor's system, and nothing published addresses the status of those communications, whether they are treated as confidential, or what happens to them when the firm declines the matter. Checked the home page, the blog material, the Clio directory listing, the CodeX profile and the site navigation on 29 Aug 2026.

Nothing substantive located. The only statements found are that the platform maintains confidentiality and safeguards sensitive information, which is unfalsifiable phrasing naming no mechanism, and an independent review checkbox indicating the product claims to keep data secure. Nothing addresses attorney client privilege or work product. The gap has a specific shape in this category that no prior record has raised: an intake chatbot converses with a prospective client before any engagement exists, and the information collected sits in the uncertain zone before privilege attaches, which is both a professional responsibility question and a conflicts question, since a firm that learns a prospective client's confidences may be conflicted out of representing the other side. Nothing published engages any of it. Checked the Copilot page, the home page, the Builder material and independent review on 29 Aug 2026.

Not located. The chatbot is stated to answer initial enquiries from consumers and to qualify them against case type criteria without human intervention, which places an automated system in the first conversation a person has about their legal problem. Answering an initial enquiry is where the line between legal information and legal advice is thinnest, and telling a consumer they do or do not have a qualifying matter is a determination they will act on. Nothing published states that the chatbot does not give legal advice, addresses what it may and may not say, describes any disclosure to the consumer that they are talking to a machine, or engages any bar guidance on automated client communication. Distinguished from LawDroid, which markets legal guidance to the public as a product; here the exposure arises from qualification and enquiry handling rather than from advice being sold, and it is unaddressed either way. Checked the home page, the blog material, the Clio directory listing and the CodeX profile on 29 Aug 2026.

Not located, and this is the sharpest instance of the question on the index so far. The vendor markets Builder to firms as a way to scale legal expertise and charge for services such as self serve legal documents, issue spotting and legal guidance, delivered while the lawyer sleeps. Issue spotting and legal guidance delivered autonomously to a member of the public, for a fee, without a lawyer present is the unauthorised practice scenario in its most direct form, and the vendor names it as the product's purpose rather than as an edge case. Buyer types include legal aid organisations and courts, where the end user is a self represented member of the public. Nothing published states that output is not legal advice, addresses where the line sits between legal information and legal advice, or engages any bar authority or access to justice guidance on unbundled or automated delivery. Checked the Copilot page, the Builder material, the home page and independent review on 29 Aug 2026.

Nothing published, and this record carries the most concrete untested bias risk in the category. The predictive analytics engine is stated to learn a firm's preferences for case types and predict likely case outcomes so firms can deploy resources to optimum value, which is a model scoring prospective clients on expected value and directing firm attention accordingly. A system trained on which past matters a firm accepted and how they resolved will reproduce whatever patterns are in that history, and the people affected are consumers seeking legal help who are never told a prediction was made about them, cannot see it, and have no route to contest it. The vendor's stated mission is making legal help accessible to everyone, which makes the absence of any fairness evaluation more pointed rather than less. No AI policy, model card, bias testing, evaluation, monitoring, governance body, ISO 42001 or EU AI Act positioning was located.

Nothing published about how the models are governed, evaluated or monitored. No AI policy, no model card, no bias or fairness testing, no evaluation methodology, no accuracy monitoring, no drift statement, no named governance body, no ISO 42001 and no EU AI Act positioning were located. The untested risk is specific to intake rather than generic: an intake chatbot performs triage, deciding which enquiries convert to leads and which are turned away, and any systematic tendency in that triage falls on prospective clients who are never told a machine assessed them and have no route to appeal. In the legal aid and court configurations the vendor names, the people being triaged are self represented and often have no alternative. Checked the home page, the Copilot page, the Builder material and independent review on 29 Aug 2026.

No stewardship position located. Nothing states whether intake conversations, captured matter details, generated documents or outcome data are used to train or improve models, no retention period is published, and no deletion right is described. The architecture makes the question weightier than on peers that pass data straight through: independent comparison material describes the CRM as part of the same product, so consumer intake data is retained by the vendor rather than only transiting, and the prediction engine is stated to learn from case outcomes, which means outcome data from firms feeds model improvement without any published statement about whose data, on what basis, or whether learning is scoped to the individual firm or pooled across customers. That last question is the one a firm should ask and it is unanswered. Checked the home page, the blog, the Clio listing, the CodeX profile and independent material on 29 Aug 2026.

No stewardship position located. Nothing states whether intake conversations, uploaded documents, firm built workflow content or Copilot prompts are used to train or improve models, no retention period is published, and no deletion right is described. The content at stake includes conversations with prospective clients about their legal problems, which is sensitive personal information collected from members of the public who are not the customer and have no relationship with the vendor at all. The only located statements are generic assurances of confidentiality and privacy. Checked the Copilot page, the home page, the Builder material and independent review on 29 Aug 2026.

No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy. Two exposures are specific to this product. A chatbot that wrongly disqualifies a consumer ends the conversation, and unlike a defective document or a bad citation nobody discovers the error, since the consumer simply goes elsewhere or gives up and the firm never learns what it turned away, which makes it the least visible failure mode graded on this index. A missed or mishandled enquiry can also carry limitation period consequences where a matter is time sensitive. Nothing published addresses either, and no service level commitment was located for a system described as an always open front door. Checked the home page, the blog material, the Clio directory listing and the site navigation on 29 Aug 2026.

No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy. Three exposures are distinctive here. An unsourced case law citation from Copilot reaching a filing is the fabricated citation risk in its classic form. A chatbot delivering issue spotting or legal guidance that is wrong reaches a member of the public directly with no lawyer in between, which is the vendor's stated use case rather than a misuse. And in the Enterprise tier LawDroid builds and manages the chatbot on the firm's behalf, so the vendor authored the conversation flow that spoke to the public, and nothing addresses who carries that. Checked the Copilot page, the Builder material, the home page and the site navigation on 29 Aug 2026.

A named practice management integration published on the partner's own directory, plus an architecture that removes the integration problem for part of the workflow. Clio integration is listed in the Clio app directory, which is verification by the counterparty rather than a vendor claim, and Clio is the practice management system this buyer segment most commonly runs. The architectural point is credited because independent comparison material makes it precisely: because the chatbot and the intake CRM are the same product, no middleware is needed to connect them, which the reviewer identifies as a no handoff workflow and a genuine strength. The same material identifies the trade off honestly, noting the CRM half is redundant for a firm already running Lawmatics, Clio Grow or Filevine, and that channel coverage is website focused with limited direct messaging and WhatsApp support. Held at B because only one practice management vendor is named, no API documentation was located, and the vendor's stated reach across directory profiles and social media is not matched by named platform integrations.

Named practice management integration with the distinction between products stated precisely, which is unusually candid. Builder integrates natively with Clio Grow and Clio Manage, which are the intake and practice management systems the target buyer actually runs on, and native integration into the intake product specifically is the correct connection for this category since a captured lead must become a matter. Copilot connects only through Zapier, and independent review states this plainly, noting that any practice management system connecting to Zapier could potentially work with Copilot. Publishing that one product integrates natively and the other does not, rather than claiming integration platform wide, is the kind of precision this index credits. Lead capture into a firm's case management system is stated as a Builder function, and API workspace integrations are referenced. Held at B rather than A because only one practice management vendor is named, no API documentation was located, and the Zapier dependency is a real limitation for Copilot rather than an integration.

Nothing located. No hosting provider is named, no region or data residency commitment is published, and no deployment options are described. The product is a website embedded chatbot with a hosted CRM behind it, so consumer intake data plainly resides with the vendor, and nothing states where. Residency is a live question because the chatbot collects personal information from members of the public who may be in any jurisdiction, and state privacy regimes attach to that collection regardless of where the firm sits. Checked the home page, the blog material, the Clio directory listing, the CodeX profile and the site navigation on 29 Aug 2026.

Nothing located. No hosting provider is named, no region or data residency commitment is published, and no deployment options are described beyond the products being web based and cloud hosted. Residency matters here because the vendor states buyers including courts and government agencies, which routinely carry procurement requirements about where public data is processed, and because intake conversations with members of the public are personal data subject to state and international regimes. Checked the Copilot page, the home page, the Builder material and independent review on 29 Aug 2026.

No certification, attestation, trust centre or security page was located. No SOC 2 of either type, no ISO 27001, no named auditor, no penetration testing partner and no encryption statement were found across any surface read. Under the three tier test the artifact is absent rather than gated. Two records in legal-intake-and-client-development now sit at D on this axis, this one and LawDroid, and both are the small vendors in the category, which is worth watching as the remaining five are built rather than concluding anything from two. The gap is material for a product holding consumer personal information collected through a law firm's website, where the firm carries the obligation and cannot evidence the vendor's controls to anyone. Checked the home page, the blog, the Clio directory listing, the CodeX profile and the site navigation on 29 Aug 2026.

No certification, attestation, trust centre or security page was located. No SOC 2 of either type, no ISO 27001, no named auditor, no penetration testing partner and no encryption statement were found. The only located material is a generic claim that the product keeps data secure, recorded through an independent review checkbox whose own framing notes that most AI products are built in such a way that they are inherently insecure, which is the reviewer's caution rather than a finding about this vendor. Under the three tier test the artifact is absent rather than gated. The gap is material given the stated buyer set includes courts and government agencies, which ordinarily require a named attestation before procurement. Checked the home page, the Copilot page, the Builder material, the site navigation and independent review on 29 Aug 2026.

Nothing located. No foundation model provider, model family or version is named, no distinction is drawn between proprietary and third party models, and no subprocessor list was found. The predictive analytics engine is described as the vendor's own capability, which is an ownership statement rather than a supply chain disclosure, and independent classification of the company references natural language and conversational AI without identifying what powers it. For a platform processing consumer personal information on a law firm's behalf, the identity of any third party processing that data is a question the firm's own obligations require it to answer and it cannot be answered from public material. Checked the home page, the blog, the Clio directory listing, the CodeX profile and independent material on 29 Aug 2026.

Nothing located. No foundation model provider, model family or version is named, no distinction is drawn between proprietary and third party models, and no subprocessor list was found. Independent review describes Copilot as incorporating large language model generative AI, which confirms an external or licensed model layer exists without identifying it, and the absence of any named source is compounded by the separate finding that Copilot's case law retrieval sources are also undisclosed, so neither the model nor the corpus behind the research capability can be identified from public material. Checked the Copilot page, the home page, the Builder material and independent review on 29 Aug 2026.

No pricing published at any level. No price, no range, no tier structure and no unit of charge, and no indication of whether the platform prices per seat, per conversation, per captured lead or per firm, which matters because those scale very differently for an intake product and determine whether cost rises with marketing spend. Independent comparison material positions the product as suited to mid size firms wanting a chatbot and intake CRM in one, without publishing a figure. Notable within this category: LawDroid publishes complete pricing across three products and reaches A on this axis, and this record publishes nothing, so the category is not uniform and the contrast is between vendors rather than inherent to intake products. Checked the home page, the pricing navigation, the Clio directory listing and independent comparison material on 29 Aug 2026.

Complete published pricing across a multi product line, including the awkward combination case most vendors hide. Published and independently verified: Copilot at $25 per user per month, Builder at $99 per user per month, both month to month with no annual contract required, a 7 day free trial on Copilot, and the two products together at $99 per user per month which requires an annual commitment. That last item is the notable one, because publishing that the bundle costs the same as Builder alone but locks the buyer into a year is a real commercial trade off disclosed rather than buried, and a buyer can weigh it without a sales conversation. An Enterprise tier exists for managed delivery and is unpriced, which is the only gap. Third A on this axis in 55 records, after Descrybe and Huski.ai, and the pattern across all three is the same: small vendors selling to solo and small firms publish their prices, and enterprise vendors selling to large firms do not.

Channel coverage is characterised and practice coverage is not. The vendor states reach across the firm website, directory profiles and social media, which is a real channel claim for an intake product since prospective clients arrive from all three, and independent comparison material qualifies it usefully by noting the product is website focused with limited direct messaging and WhatsApp coverage, so the stated reach exceeds the verified reach. Firm size targeting is identified by independent review as mid size firms. What is absent: no practice areas are named, no jurisdictions are stated, and because qualification criteria are configured by the firm the substantive coverage is whatever the customer builds, which the vendor does not say. The predictive analytics engine is stated to learn firm preferences by case type, which implies practice area handling without enumerating any. Held at C on that basis.

Buyer coverage is stated broadly and practice coverage is not stated at all. Named buyer types span law firms, legal aid organisations, courts and government agencies, which is a genuinely wide institutional range and the only record in this pull to name courts and legal aid as direct customers, and firm size targeting is clear from pricing and independent review as solo practitioners and small firms. What is absent is any characterisation of substantive coverage: no practice areas are named, no jurisdictions are stated, and because Builder operates on firm supplied content, its subject matter coverage is whatever the customer builds rather than anything the vendor provides, which the vendor never says. On the Copilot side independent review records that no secondary source library was verified and that case law sources are undetailed, so research coverage cannot be assessed either. Held at C: the buyer set is characterised, the substance is not.

Silent, and the quoted line is why the silence matters rather than a commitment. The vendor states that the platform learns a firm's preferences for particular case types and predicts likely case outcomes, which establishes that customer data trains a model as a core product function, and nothing published states whose data, on what basis, or whether learning is scoped to the individual firm or pooled across customers. That last question is the one a firm should ask before deploying, because a model improved by one firm's outcome data and served to competitors is a materially different product from one that learns only within a tenant. The consumer dimension compounds it: intake conversations come from members of the public who are not the customer, cannot consent and have no relationship with the vendor, and independent comparison material confirms the intake data lands in the vendor's own CRM rather than passing straight through. Recorded as silent, not as a negative commitment. Checked the home page, the blog, the Clio listing, the CodeX profile and independent material on 29 Aug 2026.

Silent. The quoted phrase is the fullest data handling statement located and it is an unfalsifiable assurance naming no mechanism, no scope and no commitment. No statement in either direction was found on whether intake conversations, uploaded documents, firm built workflow content or Copilot prompts are used to train or improve models. The content at stake is distinctive in this category: intake conversations are collected from members of the public describing their legal problems, and those people are not the vendor's customer and have no relationship with it, so they cannot consent, object or ask. The vendor names legal aid organisations and courts among its buyers, which means some of those conversations are with self represented people in difficulty. Recorded as silent, not as a negative commitment. Checked the Copilot page, the home page, the Builder material, the site navigation and independent review on 29 Aug 2026.

Not addressed. No retention period is published for intake conversation transcripts, captured matter details, generated documents or prediction outputs, and no deletion right is described. Retention is structural to this product rather than incidental: the intake CRM is part of the same platform, so conversations are stored by design, and the analytics engine depends on historical intake and outcome data persisting to make predictions. Nothing states how long transcripts from consumers who never became clients are kept, whether a firm can purge them, or what happens on termination. Checked the home page, the blog, the Clio directory listing and independent comparison material on 29 Aug 2026.

Not addressed. No retention period is published for intake conversation transcripts, generated documents, captured lead data or Copilot prompts, and no deletion right is described. Retention is implicit in the product rather than stated: the vendor markets rich analytics giving an in depth understanding of a client's every choice and preference, which requires conversation level data to be retained and analysed, and lead capture writes contacts into a case management system. Nothing states how long the underlying transcripts persist, whether a prospective client who never becomes a client can be purged, or what happens on cancellation of a month to month subscription. Checked the Copilot page, the home page, the Builder material and independent review on 29 Aug 2026.

Not addressed, and this record presents the prospective client conflicts problem in its most acute form on the index. No permission model, access restriction or segregation description was located. The vendor states that chatbots qualify leads and route them automatically to the relevant attorney or staff person without human intervention, and that the alerted person can jump into the conversation immediately. So a prospective client's account of their dispute is captured, assessed and pushed to a named attorney before any human has run a conflicts check, and under professional conduct rules receiving a prospective client's confidences can disqualify a firm from acting against them. Automatic routing is the opposite of quarantine. Nothing published describes screening, holding pending a check, or restricting who inside a firm can see an inbound intake. Checked the home page, the Clio listing, the CodeX profile and the blog on 29 Aug 2026.

Not addressed, and this category raises a conflicts question the prior six did not. No permission model, matter level access restriction or tenant segregation description was located. The specific issue is prospective client conflicts: an intake chatbot collects a prospective client's account of their dispute before any engagement or conflicts check has occurred, and under professional conduct rules receiving a prospective client's confidences can disqualify a firm from acting against them. Nothing published describes whether intake data is screened, quarantined pending a conflicts check, or made visible firm wide on capture, and the vendor's stated lead capture behaviour writes contacts automatically into the case management system, which is the opposite of quarantine. Checked the Builder material, the Copilot page, the home page and independent review on 29 Aug 2026.

Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The vendor holds transcripts of consumers describing legal problems, including matters that may be criminal, family or immigration related where the consumer's account could be adverse to their own interests if produced, and it holds them in its own CRM rather than only in the firm's system, so a request served on the vendor would reach material the firm might otherwise resist producing. Checked the home page, the blog, the Clio directory listing and the site navigation on 29 Aug 2026.

Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The vendor holds intake conversations in which members of the public describe legal problems, which may include admissions or details relevant to matters they are seeking help with, and it names courts and government agencies among its buyers, so it sits close to public institutions while holding material about individuals dealing with them. Nothing published addresses any of it. Checked the home page, the Copilot page, the Builder material and the site navigation on 29 Aug 2026.

Not addressed, and inapplicable in the usual sense with a live residue. The product has no primary law corpus: chatbots run on firm configured questionnaires and criteria, so the substantive content is the customer's. The residue is what the predictive analytics engine is built on. Predicting likely case outcomes requires historical matter and outcome data, and nothing published states whether that corpus is the individual firm's own history, aggregated across the vendor's customers, or drawn from external sources, nor what jurisdictions or case types it covers or how current it is. A prediction about a prospective client's likely outcome is only as good as the population it was fitted on, and that population is entirely undisclosed. Checked the CodeX profile, the home page, the blog and independent material on 29 Aug 2026.

Not addressed, and the absence is documented by an independent reviewer rather than only by this pass. Builder operates on firm supplied workflows, templates, questions, logic and content, so on that product there is no vendor corpus and the customer provides the substance, which independent review states directly along with the finding that no secondary source library was verified for Builder. Copilot is the live gap: it is stated to perform case law research, and independent review records that the specific sources from which it retrieves case law are not explicitly detailed. A research capability whose corpus is unidentified cannot be assessed for jurisdiction, depth, currency or licensing, and a practitioner relying on a returned authority has no way to know what was searched. Checked the Copilot page, the Builder material, the home page and independent review on 29 Aug 2026.

Not addressed, and inapplicable on the facts. Gideon performs intake, qualification, scheduling and document generation from firm supplied templates, and produces no legal research or citation to authority, so there is nothing for a citator to check. Recorded as a scope fact rather than a disclosure failure, consistent with the treatment of this row on Tavrn, DigitalOwl, Legal Tracker and Mitratech, so a reader comparing this record against a research product does not read an empty row as a gap. Distinguished from LawDroid in this same category, where the signal is live because Copilot performs case law research. Checked the home page, the Clio directory listing and the blog on 29 Aug 2026.

Not addressed, and applicable rather than a scope fact. Copilot performs case law research and checks citation formats, and independent review confirms basic case law research capability. Format checking is not treatment checking: confirming that a citation is correctly formatted says nothing about whether the case is still good law. Nothing published names a citator, describes a treatment or currency check, or indicates that an overruled or superseded authority would be flagged. The combination on this record is the concerning one and is recorded here for the next reader: unidentified case law sources, no citator, and a stated citation format checker that could give a practitioner false confidence that citations have been validated when only their formatting has. Checked the Copilot page, the home page and independent review on 29 Aug 2026.

Not addressed, and the omission bears on the consumer rather than on the firm. Nothing published describes what the chatbot does when a consumer's enquiry falls outside the firm's configured criteria, whether it says so plainly, whether an unqualified consumer is told why or simply ends the conversation, or whether an ambiguous case is escalated to a human rather than disqualified. The vendor states qualification and routing happen without human intervention, so the disqualification path is fully automated and undescribed. Nothing states whether the bot flags uncertainty, defers, or answers an initial enquiry it cannot properly address. For a person seeking legal help this is the behaviour that determines whether they get any, and it is unpublished. Checked the home page, the Clio listing, the CodeX profile and the blog on 29 Aug 2026.

Not addressed, with one adjacent mechanism credited elsewhere. Human agent takeover lets a person interrupt an automated conversation, which is graded on the Autonomy axis and is a control over the conversation rather than a described behaviour of the system under uncertainty. Nothing published states whether a chatbot flags that it cannot answer, hands off automatically when a question falls outside the firm's configured content, or attempts an answer anyway using its natural language capability. That last case is the one that matters, because the person on the other side is a member of the public who cannot tell a configured answer from an improvised one. On Copilot, nothing describes behaviour when case law research finds nothing supportable. Checked the Builder material, the Copilot page, the home page and independent review on 29 Aug 2026.

None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction and complaint terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. Recorded as a statement about what this search found, not as a clearance. The exposure shape is not fabricated citations, since no legal authority is generated: the analogous adverse finding would be a bar complaint or a claim arising from an automated intake interaction, such as a consumer disqualified in error or a limitation period missed after an enquiry was mishandled, neither of which appears in the sources a citation focused search would reach. Name collision noted for any later search: callgideon.com is a different company and results must be separated.

None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction and fabricated citation terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. Recorded as a statement about what this search found, not as a clearance. The exposure shape is worth stating precisely: Copilot performs case law research from sources it does not disclose, and independent review advises that attorneys verify results before relying on them, which is the exact configuration that has produced fabricated citation sanctions elsewhere in this market. This is a strong candidate for a proper docket search on a later pass.

Not addressed. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located, despite the vendor publishing a multi part educational series on chatbots in law firm intake aimed directly at practitioners. That series addresses consumer preference, engagement and conversion and does not reach the professional rules governing prospective client communications, conflicts screening or automated advice, which are the rules a firm deploying this product is operating under. Second of two records in this category at this value. Checked the blog series, the home page, the Clio directory listing, the CodeX profile and the site navigation on 29 Aug 2026.

Not addressed, and the omission is more consequential on this record than on any prior one. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located. The product is marketed to deliver issue spotting and legal guidance to the public for a fee without a lawyer present, and to legal aid organisations and courts serving self represented people, which is precisely the territory that bar authorities and access to justice regulators have been actively addressing. A vendor operating in that space with no reference to any authority is a gap of a different order than a drafting tool omitting the same thing. Checked the Copilot page, the Builder material, the home page, the site navigation and independent review on 29 Aug 2026.

Not addressed. No time saving figure, conversion improvement figure or return on investment claim was located in vendor material, which is unusual for an intake product whose value proposition is measurable lead conversion and which means there is not even a savings claim to record. Nothing appears on the consumer's side of the equation either: no position on whether an automated intake interaction is disclosed to the person as machine handled, and no record showing what portion of an initial client interaction was automated, which matters where the resulting engagement is billed. Checked the home page, the blog series, the Clio directory listing and independent comparison material on 29 Aug 2026.

Recorded at savings claims only, and the framing here is unusual enough to note precisely. The vendor does not principally sell time savings; it sells a revenue model, marketing Builder as a way for firms to scale their legal expertise and charge for services such as self serve legal documents, issue spotting and legal guidance while they sleep. That is a claim about creating billable product rather than reducing cost, and independent commentary supplies the cost side, observing that the $25 monthly Copilot plan costs less than a single hour of paralegal work in most markets. Neither carries methodology. Nothing appears on the client's side of the equation: no position on how a firm should present or bill machine delivered legal services to a consumer, no disclosure guidance, and no record showing what portion of a delivered service was automated, which matters most precisely where the buyer is a member of the public paying for a self serve document.

Not addressed. No trust centre, security page, named certification, subprocessor list, named model provider, data processing agreement or documentation request route was located, so a firm has nothing to forward and no destination to point a client toward. The gap has practical bite here because the firm, not the vendor, carries the obligation for consumer personal information collected through its own website, and it cannot evidence a single control of the system doing the collecting. Second of two records in this category at this value. Checked the home page, the blog, the Clio directory listing, the CodeX profile and the site navigation on 29 Aug 2026.

Not addressed. No trust centre, security page, named certification, subprocessor list, named model provider, data processing agreement or documentation request route was located, so a firm has nothing to forward and no destination to point a client toward. The gap is compounded by the stated buyer set: courts and government agencies ordinarily require a named attestation and a documented processing position before procurement, and neither exists in public material. Checked the home page, the Copilot page, the Builder material, the site navigation and independent review on 29 Aug 2026.

Not addressed. Nothing indicates that output records which model produced it, no human verification record is captured, and no export or audit artifact was located. The vendor publishes intake analytics giving firms an understanding of client choices and preferences, which is conversion analysis serving the firm's marketing rather than a defensible record of what an automated system said to a consumer. The relevant forum in this category is a bar complaint, a fee dispute or a malpractice claim rather than a filing, and the disputed record would be the intake transcript and the qualification decision behind it. Conversations are retained in the vendor's CRM by design, so the raw material exists, and nothing describes it as producible as an evidentiary artifact or as recording whether a human or the system made the qualification call. Checked the home page, the Clio listing, the blog series and independent comparison material on 29 Aug 2026.

Not addressed. Nothing indicates that output records which model produced it, no human verification record is captured, and no export or audit artifact was located for either product. The vendor publishes rich analytics on client choices and preferences, which is conversion analysis for the firm rather than a defensible record of what a chatbot told a member of the public, and those are different artifacts serving different purposes. The forum question in this category is also distinctive and is recorded for later readers: the disputed record is more likely to be what an intake bot said to a prospective client, surfacing in a fee dispute, a bar complaint or a malpractice claim, than a filed document, and nothing in the product is described as producing a retainable transcript for that purpose. Checked the Builder material, the Copilot page, the home page and independent review on 29 Aug 2026.