Article 96 of the Uniform Code of Military Justice (UCMJ), codified at 10 U.S.C. section 896, punishes a person subject to the Code who, without proper authority, releases any prisoner committed to that person’s charge, or who through neglect or design allows such a prisoner to escape. The same article also reaches unlawfully drinking alcohol with a prisoner. In a modern confinement facility or brig, the question of who released a prisoner and when is frequently answered by electronic systems rather than a handwritten logbook. Door-access controllers, badge readers, custody-management databases, and release logs all generate digital records. Whether those records can be used at a court-martial turns on the ordinary rules of evidence, and the short answer is that they are admissible when properly authenticated and when a hearsay exception applies.
Why these records matter in an Article 96 case
To convict under the release theory, the government must prove that the accused released a named prisoner without proper authority. To convict under the escape-through-neglect-or-design theory, it must prove that a prisoner committed to the accused’s charge escaped and that the accused either intended the escape or was derelict in preventing it. In either case, the digital records are often the most direct evidence of the operative facts: which custodian opened a door, which credential was used, what time a cell was unsecured, and when a prisoner’s status changed in the custody database. Far from being a peripheral matter, the admissibility of these records can determine whether the government can prove its case at all.
Authentication: showing the record is what it claims to be
Before any document or data set is admitted, the proponent must authenticate it, meaning produce evidence sufficient to support a finding that the item is what the proponent says it is. Under Military Rule of Evidence (MRE) 901, this can be done through the testimony of a witness with knowledge, such as the facility’s records custodian or the administrator of the access-control system, who can explain how the system works, how entries are created, and that the printout or export accurately reflects what the system recorded.
The Military Rules of Evidence also recognize self-authentication for certain electronic material. MRE 902 includes provisions that parallel the federal rules permitting self-authentication of records generated by an electronic process or system, and of data copied from an electronic device or storage medium, through a written certification by a qualified person rather than live testimony. These provisions streamline authentication of machine-generated logs, but they reach only authentication. A certification that establishes a record is genuine does not by itself satisfy any hearsay objection, which must be addressed separately.
For systems that produce machine-generated output without human input, such as automated timestamps and badge-reader entries, authentication focuses on the reliability of the process. The proponent shows that the system was functioning properly, that it records events accurately, and that the data was not altered after the fact. Chain-of-custody for the digital export and metadata such as creation dates can support that showing.
Hearsay and the business-records exception
The second hurdle is hearsay. A release log offered to prove that a release actually occurred is an out-of-court statement offered for its truth, so it must fit a hearsay exception or be shown not to be hearsay at all.
The most common path is the records-of-a-regularly-conducted-activity exception, MRE 803(6), commonly called the business-records exception. A custody log or access record qualifies when it was made at or near the time of the event by, or from information transmitted by, someone with knowledge; kept in the course of a regularly conducted activity; and made as a regular practice of that activity, all shown by a custodian or other qualified witness or by an appropriate certification. Confinement facilities maintain these records precisely as part of their routine operations, which is exactly the reliability rationale the exception is built on. The opposing party may still defeat the exception by showing that the source of the information or the circumstances of preparation indicate a lack of trustworthiness.
A distinct and often overlooked point is that purely machine-generated data may not be hearsay in the first place. Hearsay is a statement made by a person. A timestamp automatically recorded by a door controller, or an entry logged by a card reader when a badge is swiped, is the output of a machine rather than the assertion of a human declarant. Courts frequently treat such automated records as outside the definition of hearsay, in which case the analysis collapses into authentication and reliability of the system. Where a human entered information into the system, by contrast, the human-supplied portion is a statement and the business-records exception governs.
The confrontation question
Because a court-martial is a criminal proceeding, the Sixth Amendment right to confront witnesses applies. The relevant distinction is between testimonial and nontestimonial statements. Routine custody and access logs created in the ordinary course of running a facility, not for the purpose of proving a fact at a later trial, are generally treated as nontestimonial business records and do not trigger a confrontation problem merely because they are introduced through a custodian or certification. If a particular record was instead generated specifically to establish guilt in anticipation of litigation, a confrontation issue can arise and the accused may be entitled to cross-examine the person who created it. Counsel should examine why and how each record came into existence, not just whether it fits a hearsay exception.
Relevance, completeness, and reliability challenges
Even an authenticated, non-hearsay record must be relevant and survive the balancing test of MRE 403, which allows exclusion when the danger of unfair prejudice, confusion, or waste of time substantially outweighs probative value. The defense may also attack the weight of digital records rather than their admissibility, by questioning clock synchronization, the possibility that credentials were shared or cloned, gaps or errors in the logs, or whether a badge swipe proves who physically performed an act as opposed to whose credential was used. These are powerful arguments to a panel, but they generally go to how much the evidence is worth rather than whether it comes in.
Bottom line
Digital release logs and access-system data are admissible in a court-martial for an Article 96 prosecution when the government clears two gates: authentication, often through a custodian or a self-authenticating certification under the electronic-records provisions of MRE 902, and the hearsay rule, usually satisfied by the business-records exception of MRE 803(6) or by the recognition that purely machine-generated data is not hearsay. Confrontation concerns are typically minimal for routine custodial records, and most defense efforts focus on the reliability and meaning of the data rather than on keeping it out. Properly handled, these records are often the strongest proof of who released a prisoner and when, which is precisely the question Article 96 asks.
Disclaimer
This article is provided strictly for general educational and informational purposes. It is intended to explain how the Uniform Code of Military Justice (UCMJ), the Rules for Courts-Martial, the Military Rules of Evidence, and related military administrative processes work as a matter of public legal education. It does not constitute legal advice, a legal opinion, or a recommendation about any particular case, and it is not a substitute for advice from a qualified military defense attorney who can evaluate the specific facts and command, service, and jurisdictional circumstances involved.
Reading this article, or contacting any website on which it appears, does not create an attorney-client relationship between the reader and any law firm, attorney, or author. Every court-martial, nonjudicial punishment action, administrative separation, and security-clearance matter turns on its own facts, the charged articles, the convening authority, the service branch, and the evidence, and outcomes vary widely from one case to another.
Military law also changes over time. The Military Justice Act of 2016 (effective January 1, 2019) and subsequent National Defense Authorization Acts renumbered and rewrote many punitive articles, revised the Article 32 preliminary hearing, and altered sentencing, clemency, and appellate procedures. Statutes, regulations, executive orders, the Manual for Courts-Martial, and decisions of the service Courts of Criminal Appeals and the Court of Appeals for the Armed Forces may have been amended, superseded, or reinterpreted after this article was written, and article numbers or procedures cited here may have changed.
For these reasons, no reader should act or decline to act based on this content without first consulting a licensed attorney experienced in military justice about their own situation. The author and publisher make no warranty, express or implied, as to the accuracy, completeness, timeliness, or current applicability of the information provided, and disclaim any liability for any action taken or not taken in reliance on it. If you are facing investigation, charges, or an adverse administrative action, time limits may apply, and you should seek qualified counsel promptly.