Does prior strained relationship between the accused and the superior impact the charge?

Insubordination and disrespect charges often grow out of relationships that were already tense. A service member who has clashed with a supervisor for weeks, then has a heated exchange, may find that exchange charged as disrespect or insubordinate conduct. A natural question follows: does the history between the two people change the legal picture? The history does not change the elements the government must prove, but it can matter a great deal to how those elements are evaluated, to the credibility of the accuser, and to defenses the accused may raise. Understanding where the prior relationship is relevant and where it is not is essential to handling these cases well.

The charges at issue

Disrespect and insubordination offenses arise under several articles of the Uniform Code of Military Justice (UCMJ). Article 89 prohibits disrespect toward a superior commissioned officer. Article 90 covers willful disobedience of a superior commissioned officer. Article 91 prohibits insubordinate conduct, including disrespect and disobedience, toward a warrant officer, noncommissioned officer (NCO), or petty officer. Each requires the government to prove specific elements, and the existence of a prior strained relationship does not erase any of them.

For a disrespect specification, for example, the government must show that the accused used certain language or behavior, that it was directed toward and within sight or hearing of the superior, that the accused knew the person’s status, that the person was in the execution of office, and that the conduct was disrespectful under the circumstances. A bad relationship does not supply or excuse any of these. The prosecution still has to prove each element beyond a reasonable doubt.

Where the prior relationship becomes relevant

Although the relationship does not alter the elements, it bears on the case in several concrete ways.

First, intent. Disrespect and insubordination require more than a misunderstanding; the prosecution must establish that the conduct was actually disrespectful or that the disobedience was willful. A long, mutually combative relationship can cut in either direction. The government may argue the history shows a settled contemptuous attitude. The defense may argue that what looks like disrespect was the product of frustration, miscommunication, or an emotional moment, not an intent to be contemptuous, and that the words must be read against the backdrop of an ongoing personal dispute rather than as a deliberate affront.

Second, credibility and motive of the accuser. If the superior had a prior conflict with the accused, the defense is entitled to explore whether that history gives the superior a motive to exaggerate, misremember, or fabricate. Bias and motive to misrepresent are classic, permissible subjects of cross-examination. A strained relationship can therefore become a central theme in attacking the reliability of the government’s key witness.

Third, the “execution of office” requirement and divestiture. Articles 89 and 91 generally require that the superior be acting in an official capacity. Military law recognizes that a superior whose own misconduct toward a subordinate is a substantial departure from required standards can be divested of the protected status the article provides. If the strained relationship involved the superior abusing authority, behaving abusively, or acting outside official duties at the moment of the incident, the defense may argue that the superior was not in the execution of office or had been divested of protected status, which can defeat the charge.

Unlawful command influence and improper motive

A prior strained relationship can also raise the question of why the charge was brought at all. If the accusing superior is also the person driving the prosecution, the defense may scrutinize whether the charge reflects a personal grudge dressed up as discipline, or whether unlawful command influence tainted the decision to prosecute. Where the evidence suggests the command singled out the accused because of personal animus rather than even-handed enforcement, that can support a motion challenging the proceeding. These arguments are fact-intensive and require careful development of how the conduct was treated across the unit, not just against the one accused.

What the prior relationship cannot do

It is equally important to be clear about the limits. A poor relationship is not, by itself, a defense. The fact that two people did not get along does not give a subordinate license to be openly contemptuous toward a superior in the execution of office. If the elements are proven and no recognized defense applies, the history of friction will not defeat the charge; at most it becomes mitigation at sentencing, where the context of an ongoing difficult relationship may be offered to explain the conduct and argue for leniency.

Practical takeaways

A prior strained relationship between the accused and the superior does not change the elements of a disrespect or insubordination charge, but it is far from irrelevant. It informs the intent analysis, supplies a basis to attack the accuser’s credibility and motive, can support an argument that the superior was not in the execution of office or was divested of protected status, and may raise concerns about improper motive or unlawful command influence behind the prosecution. The strained relationship is best understood as context that shapes how the elements and defenses play out, and as potential mitigation, rather than as an automatic shield. Counsel should investigate the relationship thoroughly, because its details often determine whether the conduct reads as criminal insubordination or as a regrettable moment in a dysfunctional working relationship.

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.

Leave a Reply

Your email address will not be published. Required fields are marked *