Military Lawyers

Article 31 of the Uniform Code of Military Justice gives service members a protection against compelled self-incrimination that is broader in some respects than the civilian Miranda rule. It requires that a person be advised of the nature of the accusation, the right to remain silent, and that any statement may be used against them. A recurring question is whether this protection reaches everyday, informal exchanges, such as a supervisor’s casual remark or a conversation between friends in the barracks. The short answer is that Article 31 does not attach to every conversation. It applies only when specific conditions are met, and a genuinely casual exchange that does not involve an official inquiry usually falls outside its reach. Understanding where the line sits is essential, because the difference determines whether a statement can later be used at a court-martial.

The two conditions that trigger a warning

A warning is required only when both of two conditions are present. First, the person being questioned must be a suspect at the time. Second, the person doing the questioning must be acting in an official law enforcement or disciplinary capacity, conducting an inquiry rather than simply talking. If either condition is absent, Article 31 generally does not apply, and the absence of a warning will not bar the resulting statement.

This framework explains why ordinary conversation is not swept in. A friend asking what happened over the weekend, or a service member venting to a peer, is not conducting an official inquiry. Even if the speaker is technically subject to the code, the questioner is not acting in a disciplinary or investigative role, so no warning is owed.

How courts decide whether questioning was “official”

The Court of Appeals for the Armed Forces evaluates these conditions using an objective standard rather than relying on what the people involved privately felt. Whether someone is a suspect is judged by considering all the facts and circumstances at the time to determine whether the questioner believed, or reasonably should have believed, that the service member committed an offense. Likewise, whether the questioner was acting in an official capacity is assessed objectively, by asking whether the questioner was, or could reasonably be considered to be, acting in a law enforcement or disciplinary role.

This objective approach reflects a deliberate move away from an older test that asked, in part, about the subjective perceptions of the person being …

A defense contractor whose security clearance has been revoked faces a different process than an active duty service member. The contractor does not have a military chain of command in the traditional sense. Instead, the people who occupy the equivalent supporting role are the contractor’s employer, the company’s security office, and the government and supervisory personnel who work alongside the contractor. Understanding who can help, and what their help can and cannot do, is essential to a realistic appeal strategy for reinstatement.

The framework that governs a contractor’s appeal

Industrial security clearance decisions for contractors are handled through the Defense Office of Hearings and Appeals, commonly called DOHA, under the Department of Defense personnel security program. When a clearance is in question, the contractor receives a Statement of Reasons setting out the security concerns. The contractor can respond in writing, and can request a hearing before an administrative judge where evidence, documents, and witnesses can be presented. If the decision is unfavorable, there is an appeal to the DOHA Appeal Board, which reviews the record.

Throughout this process, adjudicators apply the national adjudicative guidelines, frequently referenced through Security Executive Agent Directive 4. Those guidelines use a whole person approach, meaning the decision maker weighs the entire picture of the individual, both the concerns and the favorable information, rather than disqualifying the person over a single isolated issue. This whole person framework is exactly where support from the contractor’s professional circle becomes valuable.

What “chain of command” means for a contractor

For a contractor, the functional chain of command is the company structure and the government customer. Several actors play distinct parts. The Facility Security Officer, or FSO, is the company official responsible for the contractor’s clearance administration and is often the central point of contact with the security system. Company management decides whether to continue sponsoring and employing the individual, which can be a practical prerequisite to retaining a clearance, since industrial clearances generally require a continuing need tied to the job. Government supervisors, program managers, and military or civilian officials who oversee the contractor’s work can speak to the person’s reliability and trustworthiness on the job.

These individuals are not decision makers in the clearance case. The administrative judge and the Appeal Board decide it. But the support of these people can meaningfully shape the evidentiary record the judge evaluates.

How support strengthens the whole person analysis

Because the …

Before a serious charge can be referred to a general court-martial, the accused is entitled to an Article 32 preliminary hearing. The accused can waive that hearing, and at first glance waiving may seem like a way to avoid a stressful and exposing proceeding. Yet experienced defense counsel often advise against waiver. Even though the modern Article 32 hearing is narrower than the investigation it replaced, it still offers the defense valuable opportunities that disappear the moment the right is given up.

What an Article 32 Hearing Is Today

Under the version of Article 32 reshaped by the Military Justice Act of 2016, the preliminary hearing serves four limited purposes: to determine whether each specification alleges an offense under the UCMJ, to assess whether there is probable cause to believe the accused committed the offense, to determine whether the court-martial would have jurisdiction, and to recommend to the convening authority whether the charges should be referred for trial, dismissed, or otherwise resolved.

This is a significant change from the old system. The 2016 reforms shifted the proceeding from a comprehensive pretrial investigation, which had allowed extensive discovery and evidence gathering, to a narrower hearing modeled on federal civilian preliminary hearings. The preliminary hearing officer, usually a judge advocate, conducts a limited-scope review and issues a recommendation that is not binding on the convening authority. Even with these limits, the hearing remains a rare pretrial window into the government’s case, and that is precisely why counsel hesitates to surrender it.

Reason One: A Preview of the Government’s Case

The hearing allows the defense to examine the government’s evidence, to question witnesses, and to challenge the legal and factual basis for the allegations. Although Congress narrowed the discovery role of the hearing, the proceeding can still serve as a useful pretrial discovery tool. The defense may gain insight into the government’s theory, learn what evidence the prosecution intends to rely on, and in some instances gain access to investigative materials and the chance to question government witnesses.

That preview is hard to replicate. Watching how a witness testifies under questioning, observing inconsistencies, and locking in early accounts can shape the entire defense strategy for trial. A witness who testifies one way at the hearing and differently at trial has handed the defense a tool for impeachment. Waiving the hearing forfeits that opportunity.

Reason Two: A Chance to Defeat or Reduce the Charges

…

United States v. Ravenel is a decision of the Court of Military Appeals, the predecessor to today’s Court of Appeals for the Armed Forces, reported at 26 M.J. 344 and decided in 1988. It is cited in military self-incrimination law for its recognition that the conditions of military life make the protection in Article 31(b) of the Uniform Code of Military Justice broader in important respects than the warning requirement the Supreme Court created for civilians in Miranda v. Arizona. To understand why that recognition matters, it helps to start with what Article 31 actually says.

The statutory backdrop

Article 31, codified at 10 U.S.C. 831, has several parts. Subsection (a) bars compelling any person subject to the code to incriminate himself. Subsection (b) prohibits interrogating, or requesting any statement from, an accused or a person suspected of an offense without first informing him of the nature of the accusation, advising him that he does not have to make any statement regarding the offense, and warning that any statement may be used as evidence against him in a trial by court-martial. Subsection (d) makes statements obtained in violation of the article inadmissible.

The crucial feature of Article 31(b) is that, unlike the civilian Miranda warning, it is not triggered only by custody. Congress wrote a warning requirement into the military code itself, and military courts have long held that the warning can be required even when a service member is not in custody at all.

What Ravenel recognized

Ravenel is frequently cited for the proposition that the privilege against self-incrimination is even more carefully guarded in the military setting than in the civilian setting because of the uniquely coercive factors present in a military environment. The decision reflects a theme that runs through military self-incrimination law: a service member faces pressures that a civilian suspect does not. Rank, the duty to obey lawful orders, and the deference owed to superiors mean that a question from a person in authority can carry an implicit compulsion to answer that has no clean civilian analogue.

From that premise, military courts have treated Article 31(b) as serving a purpose distinct from Miranda. Miranda responds to the inherently coercive atmosphere of custodial police interrogation. Article 31(b) responds to a different danger, the pressure that flows from the military hierarchy itself, and so the warning attaches in situations where the civilian rule would not apply. Ravenel …

Service members often turn to a chaplain during the hardest moments of a career, sometimes including the period when they are under investigation. A natural worry follows: if I confide in a chaplain, can the government later use what I said against me at a court-martial? The short answer is that statements to a chaplain are usually protected, but the protection comes from a confidentiality rule rather than from Article 31 itself. Understanding why matters, because the two doctrines work very differently and reach different statements.

Two separate protections, often confused

Article 31(b) of the Uniform Code of Military Justice requires that a person subject to the Code who is suspected of an offense be advised of the nature of the accusation, of the right to remain silent, and that any statement may be used as evidence, before that suspect is interrogated or asked to make a statement. Article 31 is a warning-and-suppression rule aimed at official questioning. If a required warning is omitted, the statement can be suppressed under Article 31 and Military Rule of Evidence 305.

The clergy privilege is found in Military Rule of Evidence 503. It is a confidentiality privilege that lets a person refuse to disclose, and prevent others from disclosing, a confidential communication made to a clergyman or to a clergyman’s assistant when the communication is made either as a formal act of religion or as a matter of conscience. These are different tools. Article 31 asks whether a warning was owed and skipped. Rule 503 asks whether the conversation was a protected confidence in the first place.

Why Article 31 usually does not apply to a chaplain conversation

Article 31 is triggered by questioning conducted for a law enforcement or disciplinary purpose by someone acting in an official investigative capacity. A chaplain counseling a troubled service member as a spiritual advisor is not gathering evidence for the command and is not acting as an investigator. When a chaplain hears a confession or counsels a penitent in a confidential and clerical capacity, the conversation falls outside the kind of official interrogation that Article 31 governs. For that reason, courts have treated the Article 31(b) and Tempia advisement requirements as simply not applicable to a genuine pastoral conversation. The statement is shielded not because a warning was skipped, but because the communication is privileged and confidential to begin with.

This distinction explains why the question …

When a soldier is accused of a sexual offense under Article 120 of the Uniform Code of Military Justice but is never charged at a court-martial, the matter does not always end there. The command can still pursue involuntary administrative separation. This is a different track from the criminal system, with a different standard, different procedures, and different stakes. Understanding how separation processing works in this specific situation, where there was an accusation but no criminal charge, helps explain why a soldier can face career ending consequences without ever standing trial.

Administrative separation is not punishment for a crime

The first point is foundational. Administrative separation is not a criminal proceeding and is not technically punishment. It is the Army’s mechanism for deciding whether a soldier should remain in service. Because it is administrative rather than criminal, it does not require a conviction, a referral of charges, or even a completed criminal investigation that leads anywhere. An allegation that the command believes warrants separation can serve as the basis, even if prosecutors declined to charge or a court-martial never occurred.

This is precisely why a soldier accused under Article 120 but never charged can still be processed. The absence of a criminal charge removes the soldier from the court-martial system, but it does not remove the command’s authority to seek separation on the underlying conduct.

The standard of proof is much lower

The most consequential difference is the burden of proof. A court-martial requires proof beyond a reasonable doubt. An administrative separation board, by contrast, applies a preponderance of the evidence standard, meaning it decides whether the alleged misconduct more likely than not occurred. That is a far easier threshold for the government to meet.

The practical effect is significant. Evidence that would be insufficient to convict, or that prosecutors concluded could not prove guilt beyond a reasonable doubt, may still be enough to support separation under the lower standard. This is the central reason a never charged accusation can lead to discharge: the question shifts from whether guilt can be proven to a criminal certainty, to whether the conduct is more likely than not to have happened.

Relaxed evidentiary rules

Administrative boards do not apply the Military Rules of Evidence the way a court-martial does. Hearsay can be considered, written statements can be received without the author testifying, and investigative materials can be presented. This relaxed approach again favors …

The “functional equivalent of interrogation” is the idea that questioning is not limited to literal questions. Words or conduct designed or reasonably likely to draw out an incriminating statement count as interrogation too. This concept matters for Article 31 of the Uniform Code of Military Justice (UCMJ), codified at 10 U.S.C. section 831, because Article 31(b) requires a rights advisement before a suspect is interrogated or asked for a statement. If the protection applied only to sentences ending in a question mark, an official could sidestep it by making suggestive remarks instead of asking direct questions. The functional-equivalent concept closes that gap.

Where the concept comes from

The phrase entered American law through the civilian Miranda context in Rhode Island v. Innis, 446 U.S. 291 (1980). There the Supreme Court held that “interrogation” includes not only express questioning but also its functional equivalent, meaning any words or actions by police that they should know are reasonably likely to elicit an incriminating response. The focus is on the perceptions and likely effect on the suspect, not solely on the officer’s stated intent. This objective, effects-based definition has shaped how interrogation is understood across both civilian and military self-incrimination law.

How Article 31 is worded

Article 31(b) speaks of any person subject to the Code who chooses to “interrogate, or request any statement from” a suspect or accused. The statute already reaches beyond pure question-and-answer by including a request for a statement. The functional-equivalent concept fits naturally into this language: an official who makes comments calculated to prompt a suspect to talk is, in substance, requesting a statement, even if no formal question is posed. The Military Rules of Evidence, which implement Article 31, define interrogation in terms consistent with this understanding, treating questioning that is intended to or reasonably likely to elicit an incriminating response as interrogation requiring a warning.

Why this matters more in the military

Article 31 is broader than civilian Miranda in an important way. Miranda warnings are required only during custodial interrogation by law enforcement, while Article 31(b) applies whenever an official questioner seeks a statement from a suspect, even outside custody and even when the questioner is a supervisor rather than a police officer. Because so many ordinary interactions in a command setting can amount to questioning, the functional-equivalent concept has real force. A noncommissioned officer or commander who does not ask a direct question but …

When a commissioned officer is processed for involuntary administrative separation, a Board of Inquiry can become the decisive event in the case. Officers and their families often ask a practical question: if the command wants the officer out, but the Board of Inquiry recommends retention, who wins? The answer turns on understanding what a Board of Inquiry is, what authority its recommendation carries, and where the final decision actually rests.

What a Board of Inquiry is

A Board of Inquiry, commonly called a BOI, is a formal administrative hearing used to decide whether a commissioned officer should be retained or separated. It is governed by Department of Defense policy on commissioned officer administrative separations and by the implementing regulations of each service. The board is convened after the officer has been notified of the contemplated separation and the reasons for it, and it gives the officer an opportunity to respond to and rebut the basis for separation.

The board hears evidence in open proceedings and decides retention or separation based on that evidence. Its findings must be supported by a preponderance of the evidence, must be stated in clear and concise language, and must be signed by the concurring members. In substance, the BOI functions as a fact-finding and recommending body that evaluates whether the alleged basis for separation is supported and whether the officer should remain in service.

The command’s recommendation in context

A command recommendation for discharge is the front end of the process. It reflects the chain of command’s view that the officer should be separated, and it is typically what sets the separation action in motion. But a command recommendation is not a decision. It is one input. The very purpose of convening a Board of Inquiry is to provide an independent hearing at which the officer can contest that recommendation before any separation is finalized.

This is the key structural point. The command recommendation and the BOI recommendation are not equal competitors where the more senior voice automatically prevails. They occupy different roles. The command recommendation proposes separation; the BOI independently evaluates whether separation is warranted and makes its own recommendation after a hearing.

Where the final authority lies

Neither the command nor the board has the final word in the formal sense. For commissioned officer separations of this kind, the action of the Secretary of the Military Department concerned is final. The BOI makes …

Losing a security clearance can be devastating for a service member or defense contractor whose career depends on access to classified information. A common and understandable concern is whether a clearance can be restored when it was revoked based on misconduct findings that are now years old. The encouraging answer is that reinstatement is possible. Security clearance decisions are forward-looking judgments about current trustworthiness, and the passage of time, combined with evidence of changed circumstances, can be among the most powerful tools for regaining eligibility. Reinstatement is not automatic, however, and it requires a deliberate effort to show that the concerns that led to the revocation no longer apply.

Clearance Decisions Look at Present Trustworthiness

The framework for granting, denying, and revoking clearances is built around the National Security Adjudicative Guidelines, which all executive branch adjudication authorities apply using the same standards. These guidelines assess whether an individual can be relied upon to safeguard classified information. Crucially, they ask about present and future reliability, not whether a person made mistakes at some point in the past. That orientation is precisely why older misconduct can lose much of its force over time. A finding that supported revocation years ago may no longer reflect who the individual is today.

This is also why simply having a clearance revoked is not necessarily permanent. The question on reconsideration is not whether the original decision was correct when made, but whether the individual is now eligible based on current circumstances.

The Role of Time and Mitigation

Two related concepts dominate the analysis of stale misconduct: mitigation and the passage of time. Mitigation refers to facts and actions that reduce or counterbalance a security concern. The guidelines recognize that conduct can be mitigated when it happened long ago, was an isolated event rather than a pattern, occurred under circumstances unlikely to recur, or has been followed by evidence of rehabilitation and responsible behavior.

The more time that passes without a recurrence of the problematic conduct, the easier it generally becomes to demonstrate rehabilitation. Outdated misconduct findings, by their nature, are often well suited to mitigation. If the conduct was a single episode that occurred years earlier, was promptly corrected, and has not been repeated, an applicant has a strong foundation for arguing that the original concern is no longer disqualifying. Demonstrating an unblemished record in the intervening period is often persuasive evidence that the past conduct …

Article 97 of the Uniform Code of Military Justice, codified in the punitive articles at 10 U.S.C. 897, addresses unlawful detention. It is one of the less frequently charged offenses, but it carries real weight because it polices the very people the military trusts with the power to restrain others. Understanding exactly what the government must establish at a court-martial helps a service member and counsel see where a charge is strong and where it can fall apart.

The Statutory Foundation

The text of Article 97 is short. Any person subject to the code who, except as provided by law, apprehends, arrests, or confines any person shall be punished as a court-martial may direct. The brevity is deliberate. Article 97 is not a general kidnapping or false imprisonment statute. It targets the misuse of the specific authority that the military grants to commanders, military police, masters-at-arms, and others who may lawfully restrain a member.

Because the offense turns on the abuse of an official power, it does not reach purely private conduct. A service member who grabs another in a barroom fight has not committed unlawful detention under Article 97, although other articles may apply. The article is concerned with the wrongful exercise of the authority to apprehend, arrest, or confine.

The Two Core Elements

The Manual for Courts-Martial sets out two elements the government must prove beyond a reasonable doubt.

First, that the accused apprehended, arrested, or confined a certain person. These three terms are distinct. Apprehension is the taking of a person into custody. Arrest is the moral restraint of a person by an order directing the limits of movement. Confinement is physical restraint, such as placing a person in a cell or holding area. The prosecution must show that one of these forms of restraint actually occurred and identify the person restrained.

Second, that the accused unlawfully exercised the authority to do so. This is the heart of the offense. The restraint must have been without legal justification. If a noncommissioned officer or military police member acted within the bounds of lawful authority, with proper grounds and following applicable regulations, there is no offense. The government must prove the restraint exceeded or lacked that lawful basis.

Proving the Restraint Was Against the Person’s Will

The restraint must have been imposed against the will of the person detained. This does not mean the government must prove a struggle …