When a commander disregards the procedural protections that govern a General Officer Memorandum of Reprimand, accountability runs mostly through corrective and remedial channels rather than through punishment of the commander. The service member’s primary remedy is to attack the reprimand itself, getting it transferred, removed, or set aside, while the issuing authority can face professional and administrative consequences for serious or repeated abuses. Understanding this requires separating the due process the system actually guarantees from the popular assumption that a flawed GOMOR automatically punishes the commander who issued it.
What process a GOMOR requires
A GOMOR is an adverse administrative action, not a criminal punishment. In the Army it is governed by Army Regulation 600-37, which sets the rules for placing unfavorable information in a soldier’s Army Military Human Resource Record. Authority to direct that a GOMOR be filed in the permanent record is restricted to general officers and certain school commandants.
The regulation affords two core due process protections before a GOMOR is filed. First, the recipient is entitled to review the documentation that serves as the basis for the proposed filing, and that documentation is to be largely unredacted so the member can meaningfully respond. Second, the member is entitled to a reasonable amount of time to submit a written rebuttal, with active duty soldiers typically given a set number of days to respond. The issuing authority must consider the rebuttal before deciding whether to file the reprimand in the performance portion of the permanent record or to file it locally.
A due process violation in this context usually means the command denied the member the supporting documents, refused or shortened the rebuttal period, filed the GOMOR before the member responded, or failed to genuinely consider the rebuttal.
The member’s primary remedy: attack the GOMOR
The most direct consequence of a due process violation falls on the reprimand, not the commander. A member can use the rebuttal itself to document the procedural defect. If the GOMOR is filed despite the violation, the member can seek transfer of the document out of the permanent record or removal of it through the appropriate appeal channels and, ultimately, the relevant Board for Correction of Military Records or service equivalent.
On appeal the burden generally rests on the member to show by clear and convincing evidence that the GOMOR is untrue or unjust, in whole or in part. A clear procedural violation, such as being denied the chance to rebut, is strong evidence of injustice and is one of the most effective grounds for getting a reprimand transferred or expunged. Because a permanently filed GOMOR is often career-ending, removing or transferring it is the relief that matters most to the member.
How the commander is held accountable
Accountability for the commander operates separately and is more limited. There is no automatic sanction triggered by a procedural error. Instead, several mechanisms can apply depending on the severity and intent of the violation.
A correction board or appeal authority that finds the process was abused can overturn the action, which serves as an institutional check on the commander’s decision and creates a record of the error. Repeated or egregious disregard of regulatory due process can become a matter for the general officer’s own superiors to address through counseling, evaluation comments, or loss of confidence, because issuing reprimands in violation of regulation reflects on the officer’s judgment.
If the violation involved bad faith rather than mere error, the conduct can implicate the officer’s own integrity. Where a commander manipulated the GOMOR process to retaliate against a subordinate for a protected communication, that may trigger the Military Whistleblower Protection Act at 10 U.S.C. 1034 and the retaliation offense under Article 132 of the Uniform Code of Military Justice. Where the misuse of authority rose to abuse of a subordinate, conduct could in theory be examined under Article 93. These are the exceptional cases; ordinary procedural mistakes are corrected, not prosecuted.
The Inspector General system provides another avenue. A member who believes a commander abused the GOMOR process can file an IG complaint, which can lead to a substantiated finding against the officer and referral for appropriate action.
Why accountability is structured this way
The GOMOR system is intentionally administrative and commander-driven. Its purpose is to let senior leaders document and correct conduct quickly, which is why issuing authority is concentrated in general officers and the standard of proof is low. The tradeoff is that the safeguards are procedural, and the principal cure for a procedural breach is to undo the resulting harm to the member rather than to convert the commander’s error into the commander’s punishment. Direct sanction of the commander is reserved for bad faith, retaliation, or abuse.
Bottom line
Commanders are held accountable for due process violations during GOMOR filing mainly through the reversal, transfer, or removal of the defective reprimand on appeal to the correction boards, supported by the member’s rebuttal record and IG complaints. Direct consequences for the commander, ranging from adverse leadership assessments to liability under Article 132, the whistleblower statute, or Article 93, are reserved for violations involving bad faith, retaliation, or abuse rather than ordinary procedural error.
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.