No. A command investigator cannot evade the warning requirement of Article 31 of the Uniform Code of Military Justice (UCMJ), codified at 10 U.S.C. section 831, simply by calling a conversation “non-investigative,” “informal,” or a “welfare check.” Whether Article 31(b) warnings are required turns on the substance of the encounter, not the label the questioner attaches to it. Courts look past the name to the real purpose and circumstances of the questioning. If the substance triggers the duty to warn, an artificial label will not save the resulting statement from suppression.
What actually triggers the warning duty
Article 31(b) bars any person subject to the Code from interrogating, or requesting a statement from, an accused or a person suspected of an offense without first advising that person of the nature of the accusation, the right to remain silent, and that any statement may be used against him at a court-martial. The duty is not defined by a label. It attaches when two things are present: the questioner is acting in an official law-enforcement or disciplinary capacity, and the person being questioned is a suspect or accused at the time of the questioning. A “non-investigative” tag does not change either condition.
The officiality test controls, not the title
Military courts use an officiality analysis to decide whether the warning was required. The leading framing comes from United States v. Cohen, 63 M.J. 45 (C.A.A.F. 2006), which asks whether, considering all the circumstances, the questioner was acting or could reasonably be perceived as acting in an official law-enforcement or disciplinary capacity, and whether a reasonable person in the suspect’s position would have viewed the questioning as official rather than casual or personal. A command investigator gathering facts about a suspected offense is, by definition, acting in a disciplinary or law-enforcement capacity. Announcing that the talk is “just a conversation” does not transform an official inquiry into a personal chat.
Purpose, not packaging, is what courts examine
The genuine line that the law draws is between questioning for a law-enforcement or disciplinary purpose and questioning for some other legitimate reason, such as an operational or administrative need. In United States v. Loukas, 29 M.J. 385 (C.M.A. 1990), the court found no Article 31 violation where a supervisor questioned a service member out of concern for the immediate safety of an aircraft and crew, because the purpose was operational rather than disciplinary. That case shows the distinction is real, but it is grounded in the actual purpose of the questioner. An investigator whose job is to develop a case against a suspect cannot borrow the Loukas exception by relabeling an interrogation as a non-investigative talk; his purpose remains disciplinary.
Why the suspect’s perception matters
The officiality test also asks how a reasonable person in the suspect’s shoes would perceive the encounter. When a known command investigator sits a service member down to ask about a suspected offense, the member reasonably understands the questioning as official, regardless of the investigator’s reassurances. The point of Article 31 is to guard against the subtle pressure that rank and official position exert on a subordinate. Calling the meeting “informal” does not dissipate that pressure; if anything, an attempt to lower the suspect’s guard reinforces why the protection exists.
The consequence of skipping the warning
If a warning was required and the investigator proceeded without one, the statement is subject to suppression. Article 31(d) provides that no statement obtained in violation of the article may be received in evidence against the accused at a court-martial. Military Rule of Evidence 305 implements that command. A military judge ruling on a suppression motion will examine the actual nature and purpose of the conversation, the investigator’s role, and the member’s status as a suspect. A self-serving characterization of the talk as “non-investigative” will carry little weight against evidence that the encounter was, in substance, an interrogation of a suspect.
A genuine non-investigative talk is different
None of this means every conversation requires a warning. A truly personal exchange, a routine administrative inquiry unrelated to suspected misconduct, or operational questioning aimed at safety or mission needs may fall outside Article 31(b). The protection is not triggered when there is no suspect or no law-enforcement or disciplinary purpose. The distinction is sound. What the law forbids is using the form of a benign conversation to disguise the substance of a suspect interrogation, then arguing the label should control.
Bottom line
A command investigator cannot avoid Article 31 advisement merely by labeling a conversation “non-investigative.” The warning requirement depends on whether the questioning is official and disciplinary in purpose and whether the person questioned is a suspect, judged by the totality of the circumstances under the officiality test of United States v. Cohen. If those conditions are met, a misleading label does not excuse the missing warning, and any statement obtained may be suppressed under Article 31(d) and Military Rule of Evidence 305.
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.