A controlled way to decide where AI belongs in criminal-defense work, what evidence a vendor must provide, and which failures should stop a pilot.
A criminal-defense AI pilot can fail before anyone types a prompt. The firm may have chosen a tool category without defining the matter, jurisdiction, evidence source, court restriction, reviewer, or failure that ends the test.
That gap matters during arrest-to-first-appearance work, when urgency is high and a wrong route can consume the little time available. It also matters in large discovery sets, where a fluent summary can hide an omitted recording or an untraceable source version.
This guide gives firm owners, attorneys, technology leads, and operations leads an operating card, an input gate, seven unranked workflow classes, vendor evidence requirements, and explicit pilot stops. Demand, cost, adoption, savings, accuracy, and outcome metrics are unavailable.
Scope: This is marketing and operations information for law firms, not legal advice. Confirm every decision with qualified counsel, your state bar, controlling ethics opinions, applicable court rules and orders, and the facts of the matter. Past results do not guarantee future outcomes.
Start with a criminal-defense operating card, not a tool list
Document the firm's real practice boundaries before reviewing software: admitted jurisdictions, accepted matters and stages, urgent coverage, evidence systems, court constraints, staffing, capacity, and firm-defined economics. The card prevents a product demo from quietly deciding which clients, deadlines, or protected materials the firm can responsibly handle.
| Operating-card field | Firm-supplied entry | Owner and evidence | Exclusion or unavailable rule |
|---|---|---|---|
| Jurisdictions/admissions | State, district, court, status, reviewer | Attorney; current records | Exclude unconfirmed or expired status |
| Matter/stage fit | Accepted and excluded matters from arrest through post-conviction | Practice owner; acceptance policy | Unsupported pair is ineligible |
| Urgent coverage | Staffed hours, on-call lawyer, custody route, escalation | Operations; current rota | Never infer 24/7 coverage |
| Evidence | Video, calls, affidavits, transcripts, images, native exports | Matter attorney; discovery index | Exclude unpreservable formats |
| Court/data constraints | Seal, order, access, retention, export, deletion, location | Counsel; order and contract | Unresolved means hold |
| People/capacity | Attorney, paralegal, intake, technology, incident owners | Firm owner; staffing record | Unavailable reviewer stops use |
| Economics/seasonality | Fee arrangement/bands, capacity, first-party pattern | Finance/practice; dated evidence | Portable benchmarks unavailable |
| Competitive density | Query, geography, device, date, observed firms, method | Marketing; saved record | No ranking/enquiry forecast |
“Criminal defense” cannot be one eligibility row. A custody call in an admitted county and a sealed post-conviction record have different clocks and controls. Mark unknown fees, caseload, seasonality, and capacity unavailable. For broader adoption questions, use the AI for law firms guide.
Use an input eligibility gate before the seven workflow classes
Classify the proposed input before selecting a tool or environment. Public or hypothetical material may carry lower confidentiality risk, but no class is universally permitted. Prospective-client, matter, discovery, sealed, protected, and court-restricted material requires controlling-source, contract, access, retention, and reviewer checks before any test.
| Data class and example | Source owner | Confidentiality / order issue | Vendor-contract control | Permitted test environment | Approver and log | Reject or escalate when |
|---|---|---|---|---|---|---|
| Public/hypothetical | Research | Public, non-identifying | Use, retention, training, export | Source-approved environment | Workflow owner; URL/date/version | Real-matter resemblance or unclear status |
| Internal non-matter | Policy | Access/trade-secret check | Storage, deletion, subcontractors | Approved firm environment | Policy/security; version log | Credentials or matter facts appear |
| Prospective-client | Intake | Duties, consent, conflicts, minimization | Flow, retention, access, incident terms | None before qualified approval | Intake counsel; consent record | Missing authority, conflict, or urgent route |
| Client confidential / privilege / work product | Matter attorney | Rule, waiver, obligations | Confidentiality, deletion, breach process | Specifically approved environment | Attorney; matter authorization | Any control or purpose unresolved |
| Discovery/evidence | Matter team | Order, chain, completeness, access | Upload, processing, retention, export | Approved evidence environment | Attorney; manifest/version log | Missing original, authority, or traceability |
| Sealed/protected/restricted | Court/custodian | Order and permitted persons | Contract cannot override order | Only if authority permits | Counsel; order/decision record | Permission implied or undocumented |
“Redacted” is not an eligibility class. Metadata, voices, locations, and rare facts may remain identifying. Record the method, reviewer, removal scope, and permitting authority. Stop if that chain cannot be reproduced.
Evaluate public-content AI without mixing it with client or matter systems. See how theStacc fits a law firm's reviewed marketing lane while licensed counsel retains every legal and publication decision.
Map all seven workflow classes before approving one
Treat the seven classes as separate evaluation lanes, not a ranking. Each lane needs a matter-stage fit, urgency rule, authorized test input, source of truth, administrative output, named reviewer, verification step, failure cost, stop condition, and system of record. Approval in one lane never transfers automatically to another.
| Workflow | Matter/stage and urgency | Allowed test input | Source and output | Reviewer and verification | Failure cost and stop | Record |
|---|---|---|---|---|---|---|
| Evidence navigation | Approved set/deadline | Authorized files | Manifest; inventory/transcript | Attorney; compare originals | Omission/provenance loss; stop | Evidence/test log |
| Research | Issue/jurisdiction/date | Public authority | Official source; candidate list | Attorney; verify propositions | False/stale authority; stop | Research log |
| Drafting | Approved transformation | Authorized version | Original; internal draft | Attorney; line/citation check | Fact/source drift; stop | Document system |
| Urgent intake | Administrative route; arrest/court clock | Synthetic contacts | Coverage rules; route | Intake counsel; handoff test | Missed urgency/advice; stop | Intake system |
| Client administration | Schedule/status route | Approved message | Template; delivery record | Matter team; verify | Ambiguity/failure; escalate | Communication system |
| Operations/knowledge | Policy/capacity query | Approved non-matter set | Policy; linked answer | Owner; freshness check | Stale/leaked answer; stop | Audit log |
| Marketing | Public education | Public/firm facts | Approved sources; draft | Attorney; claim review | Claim/disclosure failure; hold | CMS approval log |
Workflow class 1: discovery inventory and evidence navigation
Evaluate this class only for an approved evidence set whose originals, manifest, permissions, and deadline are known. The administrative target may be an inventory, draft transcript, or navigation aid. It must never decide admissibility, credibility, guilt, innocence, evidentiary weight, litigation strategy, or likely case outcome.
Berkeley Law's inventory maps tool categories; JusticeText describes work with police footage, jail calls, and affidavits. Neither establishes accuracy, security, admissibility, or firm fit.
Test an authorized packet with known file count, duration, order, speakers, and hard segments. Preserve originals and compare the output to the manifest. Require proof for formats, upload, access, retention, deletion, export, audit, and failure behavior. Stop on any missing file, timestamp mismatch, untraceable excerpt, unauthorized access, or failed export/deletion.
Workflow class 2: research and source retrieval
Use AI research only as a candidate-source retrieval step under attorney control. Set the jurisdiction, court, issue, source cutoff, and negative-result procedure before the query. Every citation and proposition must be opened, checked against authoritative text, dated, status-verified, and logged before it informs any filing or client communication.
Thomson Reuters describes CoCounsel Legal for criminal-law research, analysis, and drafting. That is a vendor statement. ABA Formal Opinion 512 calls for understanding tool risks and reviewing court-bound citations and analysis; it is model guidance.
Test public authority with superseded law, an ambiguous quotation, a negative result, and a jurisdiction mismatch. Require links, parameters, query history, returned and rejected sources, status checks, and sign-off. Stop when authority is irreproducible, a proposition outruns its source, controlling material is absent, or jurisdiction/date is obscured.
Workflow class 3: drafting and document transformation
Separate four tasks before testing: summarizing an approved source, transforming firm-approved text, producing an internal first draft, and preparing material that could become a filing or client communication. Each has a different reviewer and failure cost. Generated text is never presumed filing-ready, legally correct, complete, or properly cited.
Start with a versioned source set and narrow instruction. Record authority, input/output versions, permitted changes, reviewer, and destination. Compare for omitted qualifications, altered names or dates, invented facts, quotation drift, and citation mismatch.
A filing or client path also needs controlling rules, matter facts, attorney review, and any required AI disclosure. Never let a summary become the next document's source. Stop when provenance is lost, comparison is incomplete, citations fail, unauthorized facts appear, or the attorney cannot account for a material statement.
Workflow class 4: urgent intake and conflict-safe routing
Limit this class to administrative routing after the firm defines staffed coverage, jurisdiction and matter eligibility, data minimization, no-advice language, conflicts handoff, urgent human escalation, unreachable-contact treatment, consent, and record ownership. An AI route must not explain rights, deadlines, charges, strategy, or whether representation exists.
Test synthetic arrest, custody, first-appearance, bail, wrong-jurisdiction, adverse-party, existing-client, and unreachable-caller scenarios. Assign routes and firm-set escalation thresholds. Test after-hours claims against the rota; “immediate” is false when no admitted attorney is staffed.
Keep click, connection, message, reachability, qualification, consultation, engagement, and opened matter separate. Stop on missed urgency, advice, conflict bypass, unsupported acceptance, message loss, duplicates, unclear consent, or unavailable coverage. Preserve contact and routing events separately in the intake system.
Workflow class 5: client communication and matter administration
Keep this class to scheduling, status routing, approved templates, translation or accessibility review, delivery verification, and human escalation. Automation must not explain charges, rights, plea options, evidence, strategy, deadlines, or likely outcomes. The matter attorney defines which messages qualify and who approves each template and exception.
Test invented names and matter IDs across ambiguity, failed delivery, language and accessibility needs, missed appointments, urgent custody updates, and off-template replies. Expected output is an administrative route or approved message.
Require identity and permissions, message history, delivery proof, template versions, retention, export, and escalation evidence. The approved communication system is authoritative. Stop on uncertain identity, failed delivery, unavailable translation/accessibility review, ambiguity, legal questions, or unavailable human ownership.
Workflow class 6: practice operations and knowledge retrieval
Use internal AI retrieval only against a controlled, permissioned, and dated source set. Suitable tests include approved policies, playbooks, staffing coverage, capacity views, and administrative summaries. Keep confidential matter records separate unless a matter-specific process has independently passed every authorization, contract, access, and court-order gate.
Test current and superseded versions of the rota, accepted-matter policy, evidence playbook, and incident procedure. Answers need source links, review dates, permissions, and a correction owner; conflicting documents must escalate.
Require proof for indexing boundaries, access, deletion, refresh, audit, export, and cache correction. Policy remains authoritative. Stop on stale content, missing links, permission leakage, unlogged change, unresolved conflict, or a withdrawn document that remains retrievable.
Workflow class 7: marketing and educational content
Keep public education, practice-area pages, local content, Google Business Profile work, reviews, and social distribution outside legal research, evidence, conflicts, intake qualification, and case management. Use public sources and approved firm facts, then require jurisdiction, attorney-advertising, no-advice, claims, disclaimer, and intake-boundary review before publication.
See theStacc for lawyers, the law firm SEO guide, and the lawyer SEO tool comparison. Content SEO handles keyword/SERP research, drafting, scoring, and queued CMS publishing. Local SEO covers GBP posts, review replies, citations, and rank tracking.
Compliance Profiles can inject configured bar-number, responsible-firm, and not-legal-advice disclosures at planning time, steer drafts away from prohibited claims, and assign a human verdict of None, Hold, or Block. Automated and agent-key callers cannot override that verdict. The licensed professional remains responsible, and the control does not certify compliance.
Use the approved claim record, never a case file. Stop on promised results, fabricated testimonials, unsupported superlatives or expertise, missing disclaimers, wrong jurisdiction, unverified law, or implied representation. Confirm specialist language against certification and controlling rules.
Compare vendors through evidence, then run a bounded pilot
Shortlist a vendor only when its current official documentation matches one eligible workflow. Then document the data path, contract, retention, deletion, permissions, auditability, source traceability, integration, export, support, cost owner, reviewer, and failed test. Unresolved evidence stays unresolved; a sales statement cannot fill the cell.
| Vendor / category and inclusion | Official page and check date | Self-described capability | Excluded inference | Data, retention, access evidence | Traceability, integration, export | Test owner, failed test, unresolved question |
|---|---|---|---|---|---|---|
| JusticeText; evidence navigation; criminal-evidence category fit | Official site; 2026-07-13 | Vendor describes police footage, jail calls, and affidavits in an AI-assisted workflow | No accuracy, completeness, security, admissibility, outcome, or private-firm fit finding | Upload path, retention/deletion, access roles, contract controls: unresolved until reviewed documentation is obtained | Audit, source mapping, integrations, export/exit: unresolved | Matter attorney and security owner; fail on omitted/untraceable file; obtain complete technical and contract packet |
| CoCounsel Legal; research/drafting; current criminal-law page | Official page; 2026-07-13 | Vendor describes research, analysis, and drafting for criminal-law work | No independent accuracy, security, outcome, or firm/matter fit finding | Input path, retention/deletion, role access, applicable contract: unresolved until the candidate packet is reviewed | Citation traceability, integrations, export/exit: verify in the selected product and plan documentation | Research attorney and technology owner; fail on false or missing authority; resolve plan-specific controls |
Berkeley Law's inventory is useful for discovering categories, and NACDL's AI Task Force frames implications for criminal-defense practice. Neither is a product endorsement or vendor diligence packet. Do not score or rank candidates until the firm publishes a repeatable evidence method and completes comparable cells.
Put governed marketing content in its own evaluated lane. theStacc supports public content and local-search operations with planning-time Compliance Profiles and a human review gate; it does not enter the legal-work lanes above.
Use a pilot card with measurable stop authority
Run one workflow for one declared window under one fixed protocol version. The pilot card must name the hypothesis, excluded legal decisions, dataset authorization, test cases, required sources, reviewers, success and failure rules, privacy and ethics gate, cost owner, incident path, stop authority, and final keep, change, or stop decision.
| Pilot-card field | Required entry |
|---|---|
| Workflow hypothesis | One administrative output tied to one eligible workflow; no efficiency, accuracy, or outcome promise |
| Excluded decisions | Admissibility, credibility, guilt, innocence, strategy, legal conclusion, conflict clearance, engagement, or case outcome |
| Dataset and window | Synthetic or specifically approved inputs; protocol version; start/end dates; source manifest |
| Tests and sources | Normal, edge, failure, access, outage, export, deletion, and reviewer-unavailable cases; authoritative comparison records |
| Review and gates | Workflow reviewer, attorney sign-off, security/privacy owner, ethics review, contract approval |
| Incident and stop | Named incident route, containment action, evidence preservation, stop authority, restart approval |
| Decision | Keep, change, or stop with unresolved questions, restrictions, owner, and next review date |
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| AI pilot exception rate | Unique test cases triggering a documented factual, source, access, confidentiality, jurisdiction, workflow, or review exception | All unique test cases executed under the same fixed pilot protocol | One declared pilot window with protocol version held constant | Test log, source comparison record, and incident register | Pilot owner with attorney/ethics sign-off | Duplicate reruns unless separately labeled, tests outside protocol, vendor demos, unlogged ad hoc use, and missing evidence |
Do not set a borrowed pass percentage. Define which exceptions force an immediate stop, then compare results only within the fixed protocol. A low exception rate cannot cure one unauthorized disclosure, missing evidence file, fabricated authority, access leak, or court-order breach.
Keep the marketing-to-matter funnel as separate evidence stages
Define every acquisition and matter stage with its own rule, timestamp, source, owner, attribution, consent state, and exclusions. This prevents a marketing interaction from becoming an invented enquiry, engagement, or result. The dictionary is firm-specific; qualified counsel and operations must approve it before automation writes any downstream status.
| Stage | Business rule and timestamp | Source and owner | Attribution and consent | Exclusions |
|---|---|---|---|---|
| Impression | Platform-reported display under one definition; platform event time | Search/social/ad platform; marketing analytics | Declared cohort and platform model; consent state recorded where applicable | Paid or organic kept separate, bots/scanners per written rule, missing records |
| Click | Unique approved-link click; analytics event time | Platform plus approved link/UTM log; analytics owner | Documented source/medium/campaign rule; consent state | Staff/tests, bots/scanners, duplicates, unapproved links |
| Call click | Phone-control activation only; event time | Website/app analytics; analytics owner | Landing/referrer rule; consent state | No connection inference, tests, duplicates |
| Form | Backend-confirmed receipt; server timestamp | Form system; web/intake owner | UTM/referrer rule; form consent version | Starts, failures, spam, tests, duplicates |
| Chat/message | Message received in approved channel; channel timestamp | Chat/message system; intake owner | Declared channel/campaign rule; notice and consent state | Bot greetings, staff tests, spam, duplicates |
| Reachable enquiry | Two-way contact with authorized intake; connection timestamp | Call/form/chat records; intake owner | First/last-touch rule declared; contact consent state | Clicks, voicemails without connection, wrong numbers, spam |
| Qualified enquiry | Meets written jurisdiction, matter, conflict, capacity, and contactability rule; decision timestamp | Intake/CRM; intake owner with attorney-approved rule | Acquisition rule retained; intake consent state | Unsupported jurisdiction/matter, conflict, spam, duplicate, unreachable |
| Booked consultation | Confirmed consultation under the firm's calendar rule; confirmation timestamp | Calendar plus intake; intake/practice owner | Original cohort retained; scheduling consent | Tentative holds, cancellations, no-shows, duplicates |
| Executed engagement | Firm's declared accepted-engagement evidence completed; acceptance timestamp | Engagement record; responsible attorney/practice owner | Original cohort retained; engagement consent/terms record | Consultations, unsigned or unaccepted records, conflicts, declines |
| Completed consultation | Consultation reached declared administrative endpoint; completion timestamp | Calendar/intake; practice owner | Original cohort retained; communication consent state | No-shows, cancelled, rescheduled, incomplete records; no outcome inference |
| Retained/opened matter | Firm's separate opened-matter status met; open timestamp | Case-management system; responsible attorney | Original cohort retained; engagement terms govern | Engagements not opened, duplicates, transferred records |
| Active matter | Current active status under matter policy; status timestamp | Case-management system; matter attorney | Original cohort retained; matter permissions apply | Paused, transferred, closed, withdrawn, duplicate |
| Closed or reopened matter | Declared administrative close or reopen rule met; event timestamp | Case-management system; matter attorney/operations | Original cohort retained; matter permissions apply | Active, incomplete, duplicate; no favorable-result inference |
A “booked job” in a cross-industry report must be labeled as a booked consultation or executed engagement here. A “completed job” must be labeled as a completed consultation or closed matter. Neither says anything about a verdict, dismissal, plea, sentence, or client outcome.
Stop the pilot when a criminal-defense failure appears
A stop rule is useful only when the event, owner, containment action, evidence record, and restart authority are written before testing. Some failures stop one test; others suspend the environment. Do not let deadline pressure, a persuasive vendor demo, or reviewer absence turn an unresolved exception into permission.
Eligibility and authority failures
- Unsupported jurisdiction, matter type, or stage
- Missed arrest, custody, first-appearance, bail, or court urgency
- Conflict not cleared through the approved human process
- Hallucinated, stale, missing, or irreproducible authority or citation
Evidence and data failures
- Wrong source version, incomplete evidence set, or lost original-file traceability
- Protected, sealed, unauthorized, or court-restricted material enters the wrong environment
- Permission leakage or an unapproved person, role, subcontractor, or system gains access
Communication and operations failures
- Untranslated, inaccessible, ambiguous, undelivered, or unverified client message
- Duplicate contact, advice-like intake response, or failed urgent human escalation
- Vendor outage, reviewer unavailable, failed export, or failed deletion
Contain first: suspend the affected route, preserve logs and source files, restrict further access, and notify the named incident owner. Qualified counsel and the responsible technical or security reviewer decide whether contractual, client, court, insurer, or regulatory notice is required. Restart only against documented corrective evidence and a new approval.
Frequently asked questions
These answers address the decision points that appear after a firm has separated workflow categories. They do not decide whether a specific tool, input, disclosure, or use is permitted. Apply the controlling jurisdiction, court and protective orders, vendor contract, matter facts, and qualified-reviewer decision to every proposed use.
How are criminal defense lawyers using AI?
Criminal defense lawyers are evaluating AI across evidence navigation, source retrieval, document transformation, administrative intake routing, approved client messages, internal knowledge retrieval, and public marketing. Each use needs its own input class, authoritative source, reviewer, system of record, and stop rule. A tool accepted for public marketing content is not thereby accepted for client or discovery data.
What kinds of AI tools are built for criminal-defense work?
Current category maps and vendor pages describe tools for evidence transcription or navigation, legal research, analysis, and drafting. Other products serve general firm operations or marketing. A category label does not establish matter fit, accuracy, confidentiality, admissibility, or ethics compliance. Evaluate the exact workflow and current official documentation instead of adopting a broad criminal-defense label.
Can a criminal defense lawyer put client or discovery data into an AI tool?
There is no universal permission to do so. Before any such input, qualified reviewers must check the controlling jurisdiction, applicable ethics opinions, court and protective orders, matter facts, client obligations, and the vendor contract and data path. Redaction alone does not establish authorization. If authority or a required control remains unresolved, reject or escalate the input.
Can AI review body-camera footage, jail calls, or affidavits?
Vendors describe AI-assisted workflows for police footage, jail calls, affidavits, and related formats, but that description is not proof of completeness, accuracy, security, admissibility, or matter fit. Preserve original files and source identity, test only with authorized data, compare outputs to originals, restrict access, and stop when material cannot be traced or verified.
Can a lawyer rely on AI-generated legal research or citations?
A lawyer should not rely on an AI-generated proposition or citation without independent verification. Open the authoritative source, confirm jurisdiction, date, status, quotation, and proposition, search for contrary or controlling authority, and preserve the research log. ABA Formal Opinion 512 is model guidance; the firm must also apply controlling rules, opinions, and court requirements.
How should a criminal-defense firm test an AI tool before using it on matters?
Run a bounded pilot for one workflow with synthetic or specifically approved data. Predefine test cases, required sources, reviewers, permissions, failure events, incident handling, export and deletion checks, and stop authority. Record every exception under one protocol version. Broader use requires a documented keep, change, or stop decision plus fresh privacy, security, ethics, and contract approval.
Does AI replace attorney review or responsibility?
No. AI output does not replace the lawyer's duties of competence, confidentiality, communication, candor, supervision, or reasonable billing under the applicable rules. A qualified attorney must own legal verification and the final decision. The firm should also define what happens when the assigned reviewer is unavailable, because silence cannot become automated approval.
Is criminal-defense AI software the same as law-firm marketing or SEO software?
No. Criminal-defense legal tools may describe research, drafting, or evidence workflows, while marketing software works on public content and local-search operations. theStacc supports keyword and SERP research, content drafting and scoring, queued CMS publishing, GBP posts, review replies, citations, and rank tracking. It does not perform legal research, evidence review, conflicts, intake qualification, case management, or legal approval.
Choose one bounded workflow and earn the next decision
Start with the operating card, reject ineligible inputs, and choose one workflow whose source, reviewer, system of record, vendor evidence, failure cost, and stop authority are explicit. A successful pilot supports only that recorded use under that protocol. It does not approve a vendor for every criminal-defense task.
Start with a 60-minute mapping session. Bring the practice owner, one matter attorney, operations, intake, and the technology or security owner. Complete the unavailable fields honestly. Pick a synthetic test packet, name the person who can stop it, and schedule the evidence review before the pilot starts.
For public marketing only, theStacc can research live search results, draft and score content, queue or publish to a connected CMS, and support GBP work. Compliance Profiles add configured disclosures during planning and keep the human verdict in control. Licensed counsel remains responsible for every public claim, disclaimer, ethics decision, and release.
Build the marketing lane around verified firm facts and a human release gate. Review theStacc against your firm's jurisdictions, attorney-advertising rules, public-content workflow, and approved publishing controls.
Sources & references
Blog SEO, Local SEO, and Social Media — one dashboard, no headaches.