Bexar County Criminal Defense
Evidence ingestion automation
An Axon share notice lands in the inbox, and the evidence pulls itself down, files itself under the right matter, and arrives read-ready, with nothing downloaded twice and every step on the record.
The thumb drive that used to be the bottleneck
The State produces its digital evidence through Axon, and the way you learn it exists is an Axon Justice share notice in your inbox, sitting there like any other email. The old way to get from that notice to a working file was all manual: log in, find the share, download nine hours of body-cam MP4s and a 911 call and an interrogation recording and forty scene photos, then drag every file into the right folder and hope you put it under the right cause number. For an appointed defender on a full docket, that is hours of clerical work standing between the lawyer and the evidence.
The evidence ingestion automation takes that whole stretch off your desk. An hourly sweep watches for Axon share notices across your active cases and recent Justice shares. When one lands, it refreshes the Axon registry, pulls the originals, and places them in the matter’s Drive folder, under the case the appointment-email chain already opened. Then it writes an evidence note back to the matter so the record knows what arrived and when.
Filed under the matter the Case Board already built
The reason the evidence knows where to go is that the matter built the container first. The appointment-email chain laid down the Drive folder tree, client folder to matter folder to the evidence subfolder, before any discovery arrived. So ingestion is not guessing at a destination. It drops the body-cam clips, the dash-cam video, the 911 and interrogation audio, and the scene photographs into the exact folder that already belongs to that cause number.
The matter is the container and the source is just metadata. Different share notices on one case never spawn separate top-level folders, because the case is the drawer and the shares are labels inside it. A client with three matters gets three clean folders, not one pile, and the file you can defend the handling of is the file you have by default.
Nothing downloads twice
Evidence is heavy, and downloading the same nine-hour body-cam pass a second time is both a waste and a way to end up with two slightly different copies of the truth. So every file is checked against what is already there before it lands, by evidence ID, file hash, Drive file ID, and matter number. If the system has already pulled it, it does not pull it again. If a notice points at evidence already on the matter, it reconciles rather than duplicates.
This is the same instinct that runs through the rest of the Machine: a job already in line is reused rather than run a second time, so the automations do not fight over the same Axon account or storm it with logins. The system reuses one shared session and stops safely when a cap is reached or fresh sign-in is required, rather than bypassing any login challenge. A human seeds the access once. The automation works within it.
Read-ready, then read in one controlled run
Ingestion ends where evidence review begins. When a new file settles into a governed matter folder, the review lane runs Google’s Gemini multimodal review across it, writes the investigative findings the motion will later cite, and sends a review-ready notification so a human knows the file is in. Every AI action is logged to an audit table, and review runs under a cost cap that writes a hold row rather than run unbounded, so the reading never quietly overspends.
The discipline that matters most is the single run. Every file in a matter is read with the same models and the same prompts on the same day, so the record reads as one coherent document and not a pile stitched together over three weeks. A stitched-together dataset looks exactly as unreliable as it is. Reading the whole matter in one pass is part of what makes the result something a court can check.
What the automation does, and what it leaves to you
The ingestion automation downloads, files, deduplicates, reads, and notifies. It does not decide what the evidence means. The silence at 0:41:12 where no Miranda warning was given is captured, captioned, and timestamped, but what that silence is worth to the defense is a lawyer’s call, not the machine’s. A legacy backfill lane handles the older matters whose evidence still lives in scattered links, normalizing them into the same clean folder tree, so the discipline reaches backward as well as forward.
Every night a branded review emails the firm a full account of what the automations did in the last twenty-four hours, evidence downloaded and synced included, and a weekly report rolls it up. Those are the receipts, the system showing its work each day, which is the only honest way to ask a defender to trust it with the case. Gideon promised the person on the bench a real lawyer with real tools. For the appointed defender, real tools means the same eyes on the tape that a fully resourced office would have, filed and ready by the time you sit down, with your hand still the one that reads it and decides.
The whole machine
Ten logins down to two
One subscription stands in for the stack a defense firm usually stitches together, so the practice runs on two things it already trusts: Google Workspace, where the files and matters live, and The IMC Machine, where the matter runs. LawPay and QuickBooks, the money rail, stay where they are, fed by the Machine. Casework, evidence, motions, vouchers, marketing, and events, in one place.
San Antonio and Bexar County. The Machine is built for here first. For another city, county, or region, the build-out is custom and carries its own setup fee.
