Effect on Sentencing: Consecutive vs. Concurrent After Severance

The Default: Concurrent Sentences in a Single Criminal Action

When multiple offenses from one criminal episode are tried together, Texas law starts with a thumb on the scale for the defendant at sentencing. The sentences presumptively run at the same time, not one after another. That default is the reason a joint trial, for all its prejudice risk, can be the safer sentencing posture.

Section 3.03(a) provides that when an accused is found guilty of more than one offense arising out of the same criminal episode prosecuted in a single criminal action, the sentences “shall run concurrently,” except as the statute otherwise provides. This is a real limit on the court’s general power to stack. In LaPorte v. State, the Court of Criminal Appeals held that the trial court’s authority under Code of Criminal Procedure article 42.08 to order consecutive sentences is “statutorily limited by Section 3.03 whenever a single criminal action arising out of the same criminal episode occurs.”

The trigger is the “single criminal action,” and LaPorte defined it broadly: a defendant is prosecuted in a single criminal action “whenever allegations and evidence of more than one offense arising out of the same criminal episode — as that term is defined in Chapter 3 — are presented in a single trial or plea proceeding, whether pursuant to one charging instrument or several.” So it is the single proceeding, not the number of cause numbers, that matters. Try the offenses together, and the concurrency rule applies; and because it is a single action, the offenses were never severed — which is exactly what changes the analysis once severance enters the picture.

Why does the default cut in the defendant’s favor? Concurrent sentences are served at the same time, so the effective time turns on the longest single sentence rather than the sum of all of them. In a multi-count case that difference can be large — the distance between serving the longest of several terms and serving them end to end. Section 3.03(a) makes that outcome the starting point for same-episode offenses tried together, and it applies automatically, without the defendant having to ask for it. That automatic protection is precisely what a defendant risks giving up when he moves to sever, which is why the concurrency default belongs at the center of the severance decision.

How Severance Changes the Sentencing Math (Section 3.04(b))

Here is the tradeoff that makes severance a double-edged tool. The same statute that lets a defendant pull his offenses into separate trials also removes the concurrency protection those offenses would have enjoyed in a joint trial. Securing severance can mean trading a lower prejudice risk for a higher sentencing ceiling.

Section 3.04(b) is explicit: “In the event of severance under this section, the provisions of Section 3.03 do not apply, and the court in its discretion may order the sentences to run either concurrently or consecutively.” Once the offenses are severed and tried separately, they are no longer offenses from one criminal episode prosecuted in a single action, so the concurrency mandate switches off and the court’s general stacking discretion switches on. The table maps the outcomes by posture.

The lesson is that severance and sentencing cannot be decided separately. A defendant who secures separate trials to avoid a spillover conviction may expose himself to consecutive terms he would never have faced in a single, concurrent-by-default proceeding. That is a calculation, not a reflex.

Who Decides Consecutive vs. Concurrent?

When stacking is on the table, a natural question is whether the jury — which may have set the individual sentences — also decides whether they run consecutively. In Texas, it does not. The cumulation decision belongs to the judge, and that allocation has survived constitutional challenge.

In Barrow v. State, the Court of Criminal Appeals held that the decision whether to cumulate sentences is “a normative, discretionary function that does not turn on discrete findings of fact.” Because it is not fact-finding, placing that decision with the trial court rather than the jury does not violate the Sixth Amendment right to a jury trial, even when the defendant elected to have the jury assess punishment. The Court reaffirmed the point in Alameda v. State, holding flatly that “the Apprendi line of cases does not apply to a trial court’s decision to cumulate jury-imposed sentences.”

For the defense, this means the stacking fight is a fight with the judge, made on the record at sentencing, not a jury question to be argued in closing. The court’s discretion is broad and is not tethered to any specific finding, so mitigation aimed at the cumulation decision — the defendant’s history, the relationship among the offenses, the total exposure — is directed to the bench. Barrow also rejected a due-process attack on that discretion, so the argument against stacking is practical and equitable, not a claim that the judge lacks the power to decide.

Because the decision is discretionary and not reviewable as fact-finding, the practical defense move is to give the court affirmative reasons to run the sentences concurrently — the unity of the episode, the defendant’s role and background, and the aggregate exposure — framed as a request the court has full authority to grant. The judge’s broad power cuts both ways: it permits stacking, but it equally permits concurrency, and a persuasive sentencing presentation is aimed at that choice.

When a Stacking Order Is Unlawful

The judge’s discretion has a hard edge: it stops where Section 3.03 begins. A cumulation order entered where the statute requires concurrency is not merely an abuse of discretion — it is unauthorized, and Texas treats it as a defect that can be corrected even if no one objected at the time.

LaPorte holds that an improper cumulation order is “in essence, a void sentence,” that such error cannot be waived, and that a contemporaneous objection is not necessary to preserve it for appeal. The Court of Criminal Appeals reinforced the point in Bonilla v. State, explaining that a cumulation order in a case with “no evidence” to support the statutory predicate is unauthorized, results in an illegal sentence not subject to forfeiture, and — like a double-jeopardy violation apparent on the face of the record — may be raised for the first time on appeal or collateral attack. The usual remedy is not a new trial but reformation: the appellate court reforms the judgment to delete the cumulation order and lets the sentences run concurrently.

Bonilla also draws an important line for preservation. Where there is “some evidence” supporting the trial court’s authority to stack — for example, some evidence that a listed offense occurred within the statutory period — the defendant must make a specific objection at trial to complain about the order on appeal. The rule that an unauthorized cumulation may be raised any time applies to genuinely unauthorized orders, not to a merely debatable one. Counsel should object specifically to any stacking order at sentencing while preserving the separate argument that, on this record, the order is void.

The Section 3.03(b) Exceptions: Stacking Without Severance

The concurrency default has a carve-out that mirrors the severance exception. For a defined set of offenses, the court may stack sentences even in a single joint trial — no severance required. The same roster that strips the automatic severance right also unlocks consecutive sentencing.

Section 3.03(b) lists the offenses for which, notwithstanding a single criminal action, the sentences “may run concurrently or consecutively” in the court’s discretion. The roster includes intoxication assault and intoxication manslaughter, sexual offenses against children, sexual assault and aggravated sexual assault, trafficking and compelling prostitution, and certain aggravated injury offenses. For those cases, a defendant tried on multiple counts in one proceeding faces potential stacking that a non-listed defendant would not. Bonilla v. State illustrates the mechanics for child sexual-abuse counts: the trial judge has discretion to stack the sentences as long as there is “some evidence” that the offenses occurred after the statute’s effective date, and the offense date on the indictment is not controlling — the evidence is.

This carve-out is why the sentencing analysis and the severance analysis converge for listed offenses. A defendant charged with Section 3.03(b) offenses gets neither the automatic severance right, discussed on the sibling page about the Section 3.04(c) exception, nor the concurrency default. Both protections are removed by the same statutory list, which raises the stakes of every strategic decision in those cases.

Weighing the Severance-Versus-Stacking Tradeoff

Put the pieces together and a genuine dilemma emerges for non-listed offenses. A joint trial risks the propensity and “bad man” prejudice that severance is designed to prevent, but it locks in concurrent sentences under Section 3.03. Severance removes the prejudice but hands the judge the power to stack. Neither path is free.

The right answer is case-specific and cannot be reduced to a rule. When the counts share little evidence and a joint trial would let a weak charge ride on a strong one, the prejudice savings from severance may outweigh the sentencing risk — especially if the individual sentences are likely to be modest. When the counts overlap heavily, so a joint trial adds little prejudice, keeping the offenses together preserves the concurrency default and avoids handing the court a stacking decision. The individual punishment ranges matter enormously: stacking two short sentences is very different from stacking two long ones. So does the defendant’s realistic exposure on each count and the tenor of the particular court. Because severance is a right the defendant can invoke, and stacking is a discretion the judge may exercise, the choice of whether to sever is one of the most consequential strategic decisions in a multi-count case — and it should be made only after weighing both the trial risk and the sentence exposure with counsel who has assessed the whole record. This discussion describes how the law generally operates and is not a prediction about any particular case.

Concurrency Applies to Plea Proceedings, Too

The concurrency rule is not just a trial doctrine. It applies with equal force when a defendant resolves multiple offenses by plea, which makes it a live consideration at the negotiating table, not only in the courtroom. A defendant weighing a package plea needs to know how the sentences on the several counts will run.

LaPorte v. State defined a “single criminal action” to include a “single trial or plea proceeding,” and Baker v. State restated the point: a defendant is prosecuted in a single criminal action when allegations and evidence of more than one offense from the same criminal episode are presented in one trial or plea proceeding. So when a defendant pleads guilty to several same-episode, non-listed offenses in one proceeding, Section 3.03 requires the sentences to run concurrently, just as it would after a joint trial. The court cannot stack them, and a plea agreement that purports to do so runs into the same statutory limit.

This shapes plea strategy in concrete ways. If the offenses are not on the Section 3.03(b) list, a global plea in a single proceeding locks in concurrency, which can make consolidating the cases attractive to the defense. The State, for its part, can preserve the option of consecutive sentences by declining to resolve the cases in one action — Baker observed that to avoid concurrent sentencing the State need only proceed through separate, sequential actions. For listed Section 3.03(b) offenses, the court retains discretion to stack even within a single plea proceeding. Understanding which posture applies before signing a plea agreement prevents an unwelcome surprise at sentencing.

Where This Fits

This guide is one of four situations that arise under the Motion to Sever Offenses. Start with the parent motion for the overall framework, or move to a related fact pattern:

What the Case Law Says

These decisions—verified against primary sources—control how this issue is litigated. Every case still turns on its own facts.

• LaPorte v. State, 840 S.W.2d 412 (Tex. Crim. App. 1992) — Section 3.03 limits Article 42.08 stacking; offenses tried in one proceeding are a single criminal action, and an improper cumulation order is void.
• Barrow v. State, 207 S.W.3d 377 (Tex. Crim. App. 2006) — Deciding whether to cumulate sentences is the trial court's discretionary function; it needs no jury fact-finding and does not violate Apprendi.
• Alameda v. State, 235 S.W.3d 218 (Tex. Crim. App. 2007) — The Apprendi line of cases does not apply to a trial court's decision to cumulate jury-imposed sentences.
• Bonilla v. State, 452 S.W.3d 811 (Tex. Crim. App. 2014) — A cumulation order with no evidence supporting it is an illegal sentence that may be challenged for the first time on appeal.

General summaries of published opinions for information only — not predictions about any specific case.