When the military needs to prove where a service member was, or was not, at a particular moment, it often turns to the ordinary records a base generates as part of its daily operation. Gate check-in logs are a prime example. These are the entry and exit records kept at installation access control points, capturing identity, time, and sometimes vehicle and destination information as people pass through the gate. In prosecutions for unauthorized absence under Article 86 of the Uniform Code of Military Justice (10 U.S.C. section 886) and missing movement under Article 87 (10 U.S.C. section 887), these logs can become important documentary evidence of accountability. Understanding their role means understanding both what they tend to show and the legal hurdles to using them.
What gate logs actually record
A gate log is a record of access control activity. Depending on the installation and the system in use, it may consist of electronic card or common access card scans, automated license plate reads, visitor registration entries, or handwritten guard logs. The common thread is that each entry ties an identity or a credential to a time and a location, the gate. That combination is exactly what accountability questions turn on. If a member is required to be present at a unit by a certain time and the question is whether the member was on the installation, a gate record showing the member entered or did not enter during the relevant window speaks directly to the issue.
The connection to Article 86 and Article 87
Unauthorized absence under Article 86 turns on whether a member was absent from a place of duty without authority. The government must establish the member’s absence for the charged period, and gate logs help fix the start and end of an absence by showing when the member last left and when the member returned to the installation. For failure to go to or remain at an appointed place of duty, the same records can corroborate that the member never arrived.
Missing movement under Article 87 turns on whether a member, through design or neglect, missed the movement of a ship, aircraft, or unit with which the member was required to move. Here gate logs can be probative in two directions. They can show the member did not enter the installation or staging area in time to make the movement, supporting the government’s case. They can also support a defense, for example by showing the member did arrive on the installation but was delayed by something beyond the gate, which can bear on whether the miss was through neglect rather than mere bad luck. Because Article 87 requires proof that the member knew of the prospective movement and that there was a causal connection between the member’s conduct and the miss, the timing data a gate log supplies can be the difference between a provable case and a gap in the evidence.
Corroboration, not conclusion
It is important to see gate logs as one piece of a larger accountability picture rather than as a self contained proof of guilt. A gate record can show that a particular credential was scanned at a particular time, but it does not by itself prove who was holding the credential, why the person was entering or leaving, or whether the absence was authorized. Leave and pass records, unit accountability rosters, muster reports, duty rosters, and witness testimony from supervisors typically work together with gate data to build or rebut a case. A prudent prosecutor uses the gate log to corroborate the human accounts, and a prudent defense counsel scrutinizes whether the log actually supports the inference the government draws from it.
Getting a gate log admitted: the business records question
For a gate log to be considered by a court-martial, it must be admissible. The usual vehicle is the business records exception to the hearsay rule found in Military Rule of Evidence 803(6). That exception allows a record of an act or event to come in if it was made at or near the time by someone with knowledge, kept in the course of a regularly conducted activity, and made as a regular practice of that activity, with these foundational facts shown by a qualified witness or by an appropriate certification. Access control logs generated routinely at the gate fit this framework well, because recording who comes and goes is precisely a regularly conducted installation activity.
The record must also be authenticated under Military Rule of Evidence 901, meaning the proponent must offer evidence sufficient to support a finding that the log is what it is claimed to be. For an electronic system, that often involves testimony or certification describing the system, how entries are created, and that the system was functioning properly and producing accurate results. Defense challenges commonly focus on these foundations, questioning whether the system was reliable, whether the data was altered, or whether the entry truly reflects the member’s own passage rather than someone else using the credential.
Reliability and the limits of the data
Gate logs are powerful precisely because they are generated mechanically and contemporaneously, which makes them harder to dismiss as fabricated or as the product of faulty memory. But they have limits that bear directly on accountability findings. A handwritten guard log can contain transcription errors. An automated system can suffer clock drift, leaving its time stamps slightly off. A scan can register a credential without confirming the bearer’s identity. A member might enter through a gate that is not logged, or on foot rather than by vehicle, escaping a license plate reader. None of these limitations destroys the value of gate logs, but each is a legitimate subject of cross examination and argument, and each is a reason the records are best treated as corroborating evidence rather than as the last word.
The bottom line
Gate check-in logs play a meaningful supporting role in movement accountability. They supply objective, time stamped data about presence on and absence from an installation that bears directly on the elements of unauthorized absence under Article 86 and missing movement under Article 87. To carry weight at a court-martial they must clear the foundational requirements for business records and authentication, and even then they are most persuasive when combined with the unit’s accountability records and witness testimony. Their strength is contemporaneity and their weakness is that they record a credential and a moment rather than a complete account of where a person was and why, which is why both prosecution and defense should treat them as one carefully scrutinized component of the accountability record.
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.