The Article 32 preliminary hearing sits between the preferral of charges and the decision to send a case to a general court-martial, and its timing has real consequences for an accused who may be under pretrial restraint. Scheduling conflicts, the everyday reality of coordinating a hearing officer, two sets of counsel, witnesses, and the accused, can stretch that timeline. Understanding how those conflicts interact with the speedy trial rules is essential to knowing whether a delay is harmless housekeeping or a problem worth challenging.
What the Article 32 hearing is, and where it falls in the clock
Under Article 32 of the UCMJ, a preliminary hearing is required before charges may be referred to a general court-martial. The hearing officer determines whether the charges allege an offense, whether there is probable cause to believe the accused committed it, whether the convening authority has jurisdiction, and what disposition the officer recommends. The hearing is a step on the road to trial, so the time it consumes is part of the larger pretrial timeline that the speedy trial rules govern.
The principal speedy trial protection is Rule for Courts-Martial (RCM) 707, which generally requires that the accused be brought to trial within 120 days after the earlier of preferral of charges or the imposition of pretrial restraint. The Article 32 hearing happens inside that window, so delays in scheduling the hearing eat into the same clock that ultimately governs trial.
How a scheduling conflict becomes excludable delay
A scheduling conflict by itself does not violate the speedy trial rule, because RCM 707 allows certain periods of delay to be excluded from the 120-day count. Before referral, requests for pretrial delay are submitted to the convening authority for resolution; after referral, they go to the military judge. Importantly, the convening authority may delegate to the preliminary hearing officer the authority to approve delays connected with the hearing, and when that delegation has been made, delays the hearing officer approves can be excluded from the speedy trial calculation.
The practical effect is that whether a scheduling conflict harms the accused depends on whether the resulting delay is properly approved and documented as excludable. A delay that is requested, justified, and approved on the record is excluded from the clock. A delay that simply happens, without a request and without approval, is not automatically excluded and may count against the government.
What the hearing officer must weigh
When a continuance is requested because of a conflict, the preliminary hearing officer is expected to act as a neutral decision-maker rather than rubber-stamp the request. The officer balances the need for prompt disposition of the charges against a party’s legitimate need for additional preparation time. Relevant factors include who is asking for the delay, the length of the delay requested, the reasonableness of the request, and the reason behind it. The officer is also reminded of a shared responsibility to ensure that an accused is not held in pretrial confinement any longer than necessary, which adds urgency when the accused is confined.
This balancing matters because common scheduling conflicts arise from legitimate sources: a key witness is deployed or unavailable, defense counsel needs time to review voluminous discovery, the accused has requested a particular witness who cannot appear immediately, or the hearing officer has competing duties. A reasonable, well-supported request will usually be approved and excluded; an open-ended or poorly justified request should not be.
Who requested the delay changes the analysis
A central theme in speedy trial litigation is attribution. Delay caused by the defense, such as a defense continuance to prepare or to secure a requested witness, generally does not count against the government and is ordinarily excluded. Delay caused by the government for its own convenience is treated with more skepticism. When scheduling conflicts pile up, the record of who asked for what, and why, becomes the decisive question if the defense later moves to dismiss for lack of a speedy trial. This is why careful documentation at the Article 32 stage protects both sides: the government preserves its excludable time, and the defense preserves its ability to challenge unexcused government delay.
The constitutional and statutory layers beyond RCM 707
RCM 707 is not the only speedy trial protection. The Sixth Amendment right to a speedy trial and Article 10 of the UCMJ, which requires reasonably diligent prosecution when the accused is in pretrial arrest or confinement, provide additional protection. Scheduling conflicts that drag a confined accused’s case out can implicate Article 10 even where the 120-day count is technically managed through exclusions. The defense evaluates not only the raw day count but whether the government proceeded with reasonable diligence given the conflicts that arose.
Practical takeaways
Scheduling conflicts affect the Article 32 timeline in predictable ways. They can lawfully extend it when the resulting delay is requested, justified by a reasonable cause, and approved by the convening authority or, where delegated, the preliminary hearing officer, in which case the time is excluded from the speedy trial clock. They become a problem when delay accumulates without proper approval, when it is attributable to government convenience, or when it leaves a confined accused waiting without diligent prosecution. The accused’s protection lies in insisting that every continuance be supported and documented, and in tracking who caused each period of delay so that the speedy trial record is clear if the issue is later litigated.
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.