The body-camera production just arrived. Now what?
A ZIP from Axon Evidence.com lands in the inbox. Or a detective hands over a Cellebrite phone extraction on a USB drive. Your client's case may turn on what is in that archive, but before anyone can review the footage or the forensic report, someone has to open the package, figure out what is inside, name it correctly, route it to the right place, and make sure the forensic container is never altered. That intake step is more consequential than it looks, and it happens before any attorney touches the file.
General information for Nevada legal professionals. This is not legal advice. Read the full disclaimer.
Why digital-evidence intake is a chain-of-custody problem
Nevada courts expect counsel to be able to account for what was received, when, in what form, and how it was handled from the moment it arrived at the firm. NRS 51.345 and the common-law authentication requirements for digital evidence both assume that the party offering the evidence can show it was preserved in substantially the same condition as when it was collected. If your intake process involves unzipping an archive, renaming files ad hoc, and dropping clips into folders by hand, you have created a gap between the production you received and the files you can actually point to at trial.
The problem compounds with large productions. An Axon Evidence.com export for a serious felony defense can include dozens of body-camera clips from multiple officers, metadata files, audit logs, and a proprietary container format. A Cellebrite physical extraction adds a .ufdr forensic container, parsed report files, and a directory of extracted artifacts. Opening those files without a plan produces a scattered, unverifiable record. Handling them correctly produces a logged manifest you can authenticate.
This is not a novel problem. What is new is the volume. Productions that once arrived as one or two VHS tapes now arrive as multi-gigabyte archives with hundreds of discrete files. The intake step has scaled; the manual process around it mostly has not.
The two categories that require different treatment
Body-camera and other video
Body-camera footage from an Axon Evidence.com production typically arrives as a ZIP archive containing one or more MP4 or proprietary video files, officer metadata, and in some cases a public safety redaction layer applied by the agency before production. The video is the evidence. The attorney and client review it; the expert may analyze it; the key frame may be a trial exhibit. What it is not is a forensic container. The video file itself can be named, organized, and copied to a matter folder without altering the underlying content, provided you treat the received archive as the source of record and work from copies.
The practical intake task for video is: open the archive, inventory what is inside, rename files to a consistent convention, move clips to the matter's media folder, and queue them for transcription so the attorney can review the audio as text. None of that alters the footage. All of it makes the footage usable.
Forensic containers: Cellebrite, .ufdr, and disk images
A Cellebrite extraction is different. The .ufdr file is a forensic container that a qualified examiner created using a validated forensic process. The parsed report and the extracted artifacts inside it are derived from that container. If you rename, move, or alter the .ufdr itself, or if you open and re-save the parsed report in a way that changes its metadata, you have touched the forensic evidence. That is a chain-of-custody event that the opposing examiner will ask about.
The correct handling is simple: copy the entire extraction to a preserved location and leave it there. Never alter it. Never run it through a conversion tool. Never open it with software that might modify a timestamp. Work from the parsed report and extracted artifacts for review; point the expert back to the original container for analysis.
Disk images and other forensic containers follow the same rule. Preserve, copy, never alter.
What goes wrong with manual intake
The errors that complicate digital-evidence cases are almost always intake errors. They are not malicious. They are the predictable result of a paralegal unzipping a large archive under time pressure with no documented process:
- No manifest. A production of sixty clips with no inventory means that when the opposing party asks what you received and when, the answer is an email chain and a rough count. That is not an authentication foundation.
- Inconsistent naming. Files named by hand under pressure produce conventions like "Officer Doe clip 1," "OfficerDoe-bodycam-final," and "OD_cam_USE THIS ONE." Three months later, no one knows which version was reviewed and which was not.
- The forensic container in the wrong folder. A .ufdr file that gets dropped into the same folder as the parsed report and then sorted by someone who does not know what it is will eventually be moved, renamed, or accidentally opened in an application that modifies it.
- Missing original archive. If the ZIP is deleted after extraction, the production as received no longer exists. The extracted files are what you have. If a file is later questioned, you cannot point back to the original.
How DilloLex handles the intake
When a digital-evidence archive arrives and is dropped into the matter's intake folder on the appliance, DilloLex runs a structured intake sequence on the firm's own hardware. No client content goes to an outside AI. Here is what happens:
- The archive is opened and inventoried. Every file inside the ZIP or folder is catalogued: filename, type, size, and hash. The appliance builds a manifest that records the production as received before anything else happens.
- Files are classified by type. Video files (.mp4, .mov, and common body-camera formats) are identified as media. Forensic containers (.ufdr, disk images, and similar formats) are identified as preserved artifacts. Documents, reports, and metadata files are classified separately.
- Video is renamed and routed. Media files are renamed to the firm's convention (date, matter number, officer identifier where discernible from metadata) and moved to the matter's media folder. The inventory records both the original filename and the new name so the correspondence is permanent.
- Forensic containers are moved to a preserved location and flagged as read-only. The appliance moves .ufdr files and other forensic containers to a designated subfolder, marks them do-not-alter, and records their hash. It does not open, convert, or modify them. They sit exactly where they arrived until your expert accesses them.
- Media is queued for transcription. Body-camera clips are queued for automatic speech-to-text transcription so the attorney can search and review the audio content as text. The transcript is linked to the source clip in the matter file.
- The manifest is saved to the matter. The intake manifest, recording what was received, when, in what form, and how each file was routed, is attached to the matter file. It is the chain-of-custody foundation for the firm's handling from arrival forward.
The attorney or paralegal reviews the manifest and confirms it is complete before the matter moves to the review stage. The system proposes; the staff confirms.
What DilloLex does not do
This matters as much as what it does. DilloLex is intake and organization software. It does not perform forensic analysis. It does not verify whether a video was edited before production. It does not examine the integrity of a .ufdr container against an original device image. It does not vouch for the authenticity of any file or offer an opinion on admissibility. Those determinations belong to a qualified forensic examiner and to the supervising attorney, who must independently evaluate foundation and authentication under Nevada Evidence Rules and applicable case law.
The appliance also does not substitute for a proper litigation hold. Counsel's obligations under NRCP 16.1 and applicable case law governing preservation of digital evidence are independent of what the software does with the files after they arrive. Confirm current Nevada rules and any applicable court orders before relying on this or any other description of discovery obligations. Rules change.
How DilloLex helps
DilloLex is software that assists a firm's staff. It organizes, inventories, and preserves a digital-evidence production on hardware the firm owns. The appliance builds a manifest, routes media to the right folder, queues video for transcription, and locks forensic containers in place without touching them. Each step is logged. The supervising attorney reviews the manifest and approves the intake before the matter proceeds. Nothing is filed, produced, or sent anywhere without attorney sign-off. The attorney handles admissibility, authentication, chain-of-custody at trial, and all substantive legal judgments. The tool handles the intake paperwork so a paralegal does not have to sort sixty body-camera clips by hand at 5pm the day before a motion deadline.
Because all of this runs on the firm's own appliance, no client content goes to an outside AI. The production, the manifest, the transcripts, and the matter file stay on hardware the firm owns and controls. Read more about the firm's security architecture and how the appliance works.
For the Bates numbering and production tools that work alongside this evidence intake pipeline, see the Bates numbering guide. For the pre-filing citation check that applies once the attorney is drafting motions from the transcripts and exhibits, see the Nevada pre-filing citation check.
Common questions
Does receiving a Cellebrite extraction create any obligation to produce it?
Discovery obligations in Nevada criminal matters are governed by NRS Chapter 174, any applicable standing orders of the assigned department, and constitutional disclosure duties. In civil matters, NRCP 16.1 and 26 govern. Whether a received extraction must be disclosed, and in what form, depends on the case, the charges or claims, what the extraction contains, and any protective order or court directive. This note is general information, not legal advice; confirm current Nevada rules and any case-specific orders with the supervising attorney before making any discovery decision.
Can the attorney use the Cellebrite parsed report without the forensic examiner?
An attorney can review the parsed report produced by opposing counsel or law enforcement for purposes of case preparation. Whether the parsed report is admissible at trial without a foundational witness, and what foundation is required to authenticate it, are legal questions that depend on Nevada Evidence Rules 901 and 902 and applicable case law. A qualified forensic examiner is typically needed to authenticate a Cellebrite extraction at trial and to independently evaluate the extraction for completeness and accuracy. Confirm current Nevada evidence rules before relying on any specific description here.
What if the production does not include a chain-of-custody log from the agency?
The absence of a chain-of-custody log from the producing agency is itself a litigation issue that the supervising attorney evaluates. The firm's own intake manifest documents the firm's handling from arrival forward; it does not fill the gap for what happened before the production arrived. If the production is incomplete or the chain of custody appears broken, that is a matter for a discovery motion or challenge to admissibility, not an intake decision.
How are body-camera transcripts used in a Nevada matter?
A speech-to-text transcript of a body-camera clip is a working tool for attorney review, not a trial exhibit by itself. The transcript helps the attorney locate key statements, prepare cross-examination questions, and draft motions that reference specific portions of the video. The video itself, not the transcript, is the evidence. Foundation for the video and any quoted audio at trial still requires proper authentication under Nevada Evidence Rules. The transcript is a convenience; verify any quoted language against the actual footage before citing it in a filing.
Does the appliance handle Axon Evidence.com downloads directly?
The appliance processes archives dropped into the matter's intake folder, including ZIPs downloaded from Axon Evidence.com and similar platforms. It does not connect directly to Evidence.com or any agency portal; the download and transfer to the firm's system is a step the firm's staff performs. Once the archive is on the appliance, the intake pipeline runs automatically. Confirm the current intake workflow with the firm's administrator before relying on any specific process described here.
A note on accuracy
This guide is general information for Nevada legal professionals. It is not legal advice, it does not create an attorney-client relationship, and it is not a substitute for the rules themselves. Nevada discovery rules, evidence authentication requirements, and chain-of-custody standards are governed by NRS, NRCP, Nevada Evidence Rules, applicable case law, and any operative court orders, all of which are amended from time to time. Confirm current requirements before relying on anything described here. Digital forensics is a specialized discipline; a qualified forensic examiner, not this software, is the appropriate resource for analysis, authentication, and expert opinion.
See the intake in your office, on your hardware.
Book a thirty-minute demo and watch DilloLex open a sample archive, build the manifest, route the video, and lock the forensic containers, all on the appliance, with no client content leaving the office.
Book a demo