One of the great temptations of American Civil War wargaming is to go big. Gettysburg, Antietam, Shiloh, Chickamauga — these battles dominate the imagination, and for good reason. They offer sweeping lines of infantry, massed artillery, desperate assaults, famous commanders, and dramatic turning points.
But they also demand a lot from the wargamer: many figures, a large table, careful preparation, and several hours of play. Sometimes what we really need is not the whole second day at Gettysburg, but a sharp, tense action that can be fought in a single evening.
Fortunately, the ACW is full of exactly that kind of engagement.
Raids, rearguard actions, bridge defenses, river crossings, cavalry clashes, and meeting engagements all offer excellent tabletop situations. They are smaller than the famous set-piece battles, but they often contain more drama per regiment. The objectives are clear. The time pressure is obvious. Both sides have difficult choices. Best of all, they are easy to adapt to almost any ruleset and figure collection.
Why Small ACW Battles Work So Well
Small ACW scenarios have several advantages.
First, they give every unit a role. In a huge battle, one regiment may simply be part of a long firing line. In a smaller game, that same regiment might be the key to holding a bridge, delaying an enemy column, or breaking through before reinforcements arrive.
Second, small scenarios are easier to balance without making them symmetrical. Historical battles were rarely fair contests. One side might have better troops, more artillery, or a stronger position. The trick is not to make both sides equal, but to give both sides a realistic chance of achieving their own objectives.
Third, they make command decisions matter. With fewer units, every order is important. Do you hold the stone wall or fall back to the next ridge? Do you commit the cavalry now or wait? Do you press the attack before your opponent’s reinforcements appear?
Finally, small battles are ideal for campaign play. A raid can affect supply. A bridge defense can delay a larger army. A rearguard action can save a division from destruction. Even a minor cavalry skirmish can decide who has better intelligence before the next battle.
Below are several ACW scenario types that can be played in an evening, each with ideas for forces, terrain, objectives, and tabletop drama.
1. The Raid
A raid is one of the easiest ACW scenarios to set up and one of the most exciting to play. One side must move fast, destroy or capture something valuable, and escape before the defender can react.
The raiding force might be cavalry, mounted infantry, or a mixed detachment of cavalry and light artillery. Their target could be a supply depot, railroad bridge, ammunition wagon, telegraph station, headquarters, or river landing.
The defender begins with only a small guard force on the table. Reinforcements arrive gradually, perhaps from random roads or after a fixed number of turns.
Tabletop setup:
Use a road running across the table, with a small settlement, depot, bridge, or station near the center. Add fences, woods, and fields to break up lines of sight. The raiders enter from one edge and must reach the target quickly.
Attacker’s objective:
Destroy the target and exit with as much of the raiding force as possible.
Defender’s objective:
Prevent the destruction of the target or cut off the raiders before they escape.
Scenario twist:
The raiders may not know exactly where the target is. Place three possible objective markers on the table. The real target is revealed only when a raiding unit reaches it.
This type of game rewards speed and nerve. The attacker cannot afford to get bogged down in a firefight, while the defender must decide whether to hold the target, block the escape route, or wait for reinforcements.
2. The Rearguard Action
A rearguard action is perfect for an evening game because the story is immediately clear. One force is retreating. The other is pursuing. The defender does not need to win in the conventional sense; they only need to buy time.
This is especially suitable for ACW games because so many campaigns involved marches, retreats, and pursuit. A rearguard might be defending a crossroads, a ridge, a creek line, or a narrow road through woods.
Tabletop setup:
The defending force begins deployed across a road or ridge. Behind them is the exit route for the retreating army. The attacking force enters from the opposite side in columns or staggered formations.
Defender’s objective:
Delay the attacker for a fixed number of turns while withdrawing at least part of the force.
Attacker’s objective:
Break through quickly and prevent the defender from escaping in good order.
Scenario twist:
The defender scores points for each turn they prevent the attacker from exiting the table, but loses points for every unit destroyed or captured. This creates the classic rearguard dilemma: stand too long and be overwhelmed, retreat too soon and fail the mission.
A good rearguard scenario should not encourage the defender to fight to the last man. The aim is controlled withdrawal. Give the defender several fallback positions — a fence line, a hill, a stream, a patch of woods — and watch the tension build as each one is abandoned.
3. The Bridge Defense
Few objectives are more satisfying on the tabletop than a bridge. It gives both players a clear focal point and creates instant tactical problems.
The attacker must cross a narrow point, often under fire. The defender must hold long enough to deny passage but may be vulnerable to flanking movements, artillery, or a second crossing point.
Tabletop setup:
Place a river or creek across the table with one main bridge. Add a ford if you want to make the game more mobile. The defender deploys near the crossing. The attacker enters from the opposite side.
Attacker’s objective:
Capture the bridge and move a set number of units across it.
Defender’s objective:
Hold the bridge or destroy it before the attacker can cross.
Scenario twist:
Allow engineers or pioneers to prepare the bridge for demolition. Each turn a defending unit remains next to the bridge without being disrupted, it gains a demolition point. Once enough points are accumulated, the defender may attempt to blow the bridge.
This scenario works particularly well with limited artillery. Too much artillery can make the crossing impossible; too little can make the defender too comfortable. One or two batteries are usually enough to create drama without turning the game into target practice.
For added tension, let the attacker receive reinforcements faster than the defender. The defender must hold against growing pressure, while the attacker must decide whether to launch an early assault or wait until enough troops have arrived.
4. The River Crossing
A river crossing is similar to a bridge defense, but broader and more uncertain. Instead of one obvious objective, the attacker may have several possible crossing points. The defender must guess where the main effort will fall.
This kind of scenario is excellent when you want a game of maneuver rather than a simple frontal assault.
Tabletop setup:
Run a river or wide creek across the table. Include one bridge, one ford, and perhaps one hidden or difficult crossing point. The defender deploys after the terrain is placed but before the attacker chooses their main crossing force.
Attacker’s objective:
Get troops across the river and establish a bridgehead.
Defender’s objective:
Contain or destroy the bridgehead before it expands.
Scenario twist:
The attacker secretly chooses one crossing point as the “main effort.” Units crossing there gain a morale or movement bonus for the first few turns. This represents prepared boats, guides, or local intelligence.
The drama of a river crossing comes from timing. The first attacking units across the water are vulnerable, but if they survive long enough, the defender may suddenly find the position collapsing. The defender must counterattack at the right moment, not too early and not too late.
A small river crossing scenario also gives skirmishers and light troops a useful role. They can screen the crossing, occupy woods near the bank, or harass enemy artillery.
5. The Cavalry Clash
ACW cavalry actions are often overlooked by players who prefer infantry battles, but they make excellent short games. Cavalry scenarios are mobile, unpredictable, and full of sudden reversals.
By the middle and later years of the war, cavalry was not simply a matter of sabres and charges. Dismounted firepower, horse artillery, carbines, scouting, and raiding all mattered. This makes ACW cavalry games more varied than many players expect.
Tabletop setup:
Use open terrain broken by fences, woods, low hills, and roads. Add one or two objectives such as a crossroads, farm, signal station, or supply wagon.
Objective options:
The cavalry may be trying to seize a crossroads, capture prisoners, screen a march, escort wagons, or discover the location of the enemy.
Scenario twist:
Use hidden movement or dummy markers for the first few turns. Cavalry battles are often about information. The players should not know exactly what they are facing at the start.
A good cavalry clash should avoid becoming just two lines shooting at each other. Encourage movement by making objectives matter more than casualties. Award points for scouting locations, exiting the table, capturing wagons, or delaying the enemy.
A particularly fun version is the “wrong road” scenario. Both cavalry forces are searching for the same enemy supply column, but neither knows exactly where it is. The supply wagons enter randomly later in the game, forcing both players to react.
6. The Meeting Engagement
A meeting engagement occurs when both sides arrive on the battlefield at roughly the same time. Neither army is fully deployed. Both commanders must fight for position before the enemy does.
This is one of the best formats for a balanced ACW evening game because it avoids the problem of one side sitting in prepared defenses while the other makes repeated frontal attacks.
Tabletop setup:
Place an important terrain feature near the center: a ridge, crossroads, church, farm, bridge, or hill. Both sides enter from opposite corners or along roads.
Objective:
Control the central feature by the end of the game.
Scenario twist:
Both armies arrive in marching order. Units must enter in columns along roads, with commanders deciding whether to deploy early or rush forward. Reinforcements arrive turn by turn.
This scenario immediately creates interesting decisions. Should you send cavalry ahead to seize the crossroads? Should the artillery unlimber early or push forward? Should infantry deploy into line now, losing time, or march closer to the enemy first?
Meeting engagements also create natural narrative. The first unit to reach the fence line becomes famous. The battery that unlimbers on the hill may dominate the field. A single regiment arriving at the right moment can decide the game.
Making Small Scenarios Feel Bigger
Small games do not have to feel small. The key is to give them context.
Before the game begins, explain why the action matters. The bridge is not just a bridge; it is the escape route for an entire corps. The depot is not just a building; it contains ammunition needed for tomorrow’s battle. The cavalry clash is not just a skirmish; it will determine whether the army knows where the enemy is.
You can also connect several evening games into a mini-campaign. For example:
- Game 1: Cavalry clash to determine scouting advantage.
- Game 2: Raid on a supply depot.
- Game 3: Rearguard action after the raid.
- Game 4: Bridge defense as the raiders try to escape.
The result is a campaign that can be played over several club nights without requiring hundreds of figures or a massive map.
Balancing Without Symmetry
The most important design principle for small historical scenarios is this: balance the objectives, not the armies.
A rearguard force can be weaker than the attacker if it only needs to delay. A raiding force can be smaller if it has speed and surprise. A bridge defender can be outnumbered if the terrain favors them. A cavalry screen can “win” by escaping with information, even if it loses the field.
Instead of asking, “Do both sides have equal points?” ask:
- Can both players make meaningful decisions?
- Can both sides plausibly win?
- Does each side have a reason to move?
- Is there a time limit?
- Are casualties only one part of victory?
Time limits are especially important. Many small scenarios fail because the attacker has unlimited time to organize a perfect assault. In real operations, time was usually the enemy. Add a turn limit, arriving reinforcements, sunset, ammunition shortages, or orders that force action.
Forces for an Evening Game
For most ACW rulesets, a good evening scenario might involve:
- 3–6 infantry regiments per side
- 1–2 artillery batteries per side
- 1–3 cavalry units, if appropriate
- 1–3 commanders
For a cavalry-focused game, replace most infantry with mounted or dismounted cavalry and add horse artillery if your rules allow it.
Avoid overcrowding the table. A smaller number of units with room to maneuver usually produces a better game than a cramped miniature version of a major battle.
Final Thoughts
The American Civil War offers far more than the famous grand battles. Some of the best tabletop games come from smaller actions where the stakes are immediate and the choices are sharp.
A bridge must be held. A depot must be burned. A road must be blocked. A ford must be forced. A column must escape.
These are simple situations, but they create excellent games. They give both players clear objectives, encourage movement, and produce memorable moments. In an evening, you can fight a complete action with a beginning, middle, and end — and perhaps create a story your players will remember longer than yet another frontal assault against Cemetery Ridge.
Small battles may not decide the war. But on the tabletop, they can deliver all the drama you need.
