Beyond the Muster Roll: Every Battle, Every Soldier

Readers write to me the same way, again and again. They find an ancestor in the Muster Roll search. A private in a Pennsylvania regiment. A cavalryman from Mississippi. Once they see the name, they ask the next question. Where did he fight?

For a long time, the app could not answer that question well. The battle record sat inside the same database that powers Muster Roll, but no page showed it to readers. This summer, that changed. I built a new part of the site. Now every reader who finds a name can also find the ground that name stood on.

Why I built this

I built Muster Roll first, as a way for readers to search real Civil War service records and find their own ancestors. It grew out of the same research I do for the Steel and Honor novels themselves. Readers already know the shape of the war through Nathaniel McAllister, Andrew McAllister, and James Tanner. But Muster Roll opened a second door. It let real families search for real ancestors, and that search kept turning up the same gap.

A name and a regiment number tell you where a soldier served. They do not tell you what happened there. They do not tell you who else stood beside him. And they do not tell you whether the fight is one your own family already reads about in the books.

So I built a Battles archive. It sits next to Muster Roll, built from the same underlying records, and it answers the question readers keep asking.

How the app works

The Battles app opens the same way Muster Roll does. One email address, nothing more, so I can keep you posted when new battles or new records go up. After that, you can search by name. Type Antietam, Vicksburg, or Shiloh. Or leave the search blank and browse the full list of 382 principal battles fought between 1861 and 1865.

Click on any battle, and you land on its record.

Search that forgives you

I rebuilt the search this month after readers found real gaps in it. Type “Sharpsburg” and you will land on Antietam, since the two armies called that fight by different names and the app now knows both. Misspell a battle, drop an apostrophe, or type a state name alongside the battle, and the search still finds the right answer. You should not need to spell a battle exactly right, or know which side named it what, to find the record you are looking for.

That last point matters more than it might sound. Union and Confederate reports often gave the same fight two different names. Antietam and Sharpsburg. Bull Run and Manassas. Nineteen battles in the app now carry both names side by side, right on the page. It is a small detail, but it says something true about the whole war: two sides, standing on the same ground, telling two different stories about what happened there.

What each battle page shows you

Every page starts with the basics. The dates the fighting happened. The campaign it belonged to. Who won. From there, a plain summary tells you what happened, drawn from the National Park Service’s own account of the engagement.

Below that sits the part I am proudest of: the order of battle. This is the list of regiments that fought on each side, grouped by state. If you know your ancestor’s regiment, you can see it standing beside every other unit that fought that day.

I want to be honest about a real gap here. Union order-of-battle records survive for far more engagements than Confederate ones. Many Confederate unit records were lost, scattered, or never centrally filed the way the U.S. Army’s records were. That is a hole in the historical record. It is not a hole I chose to leave in the app. I would rather tell you that plainly than pretend the coverage is even on both sides.

Many battle pages now also carry a Technology card, alongside the summary. It answers one question plainly: did new weapons, fortifications, or equipment shape how this fight came out? Sometimes the answer is yes, and the page names the rifle, the ironclad, or the railroad line that mattered, with the real numbers behind the claim. Sometimes the honest answer is no, that maneuver or ground or timing decided the day instead, and the page says that instead of reaching for a claim the record does not support.

Where a map exists, you will find it on the page too. Where the National Park Service publishes its own account of the battle, you will find a direct link to it. And every battle page now links out to the Library of Congress as well, so you can go past my summary and into the primary sources yourself: letters, photographs, and maps drawn during and just after the war.

A small number of battles appear directly in the Steel and Honor novels. Those battle pages carry a badge marking which book, along with a line about what happens there. Gettysburg carries one. So does Antietam. So does the siege of Vicksburg. Beyond that small group, dozens of other battle pages now carry a reading list too, two or three books apiece, written by historians whose work I trust. Every book on those lists now carries a button straight to Amazon or Google Books, so if a page sends you looking for more, you are one click from actually finding it.

The two families, on real ground

Steel and Honor follows the McAllisters and the Tanners from their West Point years through the war itself. I did not invent the ground they stand on. When Nathaniel McAllister holds the signal line at Burnside’s Bridge, that bridge and that creek are real, and now you can open the Antietam battle page and read the official account of that same morning, under whichever name you learned it by. When James Tanner marches into the Wheatfield at Gettysburg, you can read what regiments from both armies fought that same ground, state by state.

I hope readers use this both ways. Come from the books to the record, or come from your own family’s record to the books. Either direction, the history underneath is the same history.

Who this is for

I built this with a few readers in mind. Most of you probably belong to more than one group.

Family historians researching an ancestor’s service will find the most direct use for it. If you already know a regiment number, you can now see the larger fight it belonged to. You can read what that day looked like for both armies.

Readers of the Steel and Honor series will find the ground under the fiction. When Nathaniel McAllister stands at Burnside’s Bridge, you can open the real record of that battle. When James Tanner marches into the Wheatfield at Gettysburg, you can read what the men on both sides faced.

Teachers and students should find real use here too. The National Park Service summaries write for a general reader, not a specialist. The order of battle turns an abstract date into a list of real regiments, real states, and real men. A single search box can carry a classroom a long way.

And if you are simply curious about the war, the search bar sits right there waiting. Type in a name you half remember from a school lesson, and see what comes back, even if you do not remember it exactly right.

A word on where the information comes from

None of this is invented, and I want to be plain about where every piece of it comes from.

The foundation of every battle record comes from one source: the National Park Service’s Civil War Sites Advisory Commission report. That includes the dates, the campaign, the summary, and the result. It is a public record, built from decades of federal battlefield study.

The battlefield maps come from Hal Jespersen’s cwmaps.com. It is a collection of more than two hundred free Civil War maps. Jespersen drew them originally for Wikipedia, then released them for public use under a Creative Commons license. Every map on the site carries his name and his site address, as his license asks.

The primary-source links on every battle page point to the Library of Congress. Its Civil War collections hold the letters, photographs, and period maps behind every National Park Service summary. Over fifty battles now link straight to the specific Library of Congress item, not just a search page, and that number keeps growing.

The reading lists cover several dozen battles now, not just a handful, and I am still adding more. Many titles come from the Emerging Civil War Series, published by Savas Beatie, a house built around single-battle histories written for general readers, not just scholars. The rest lean on established historians like Stephen Sears, James McPherson, and Harry Pfanz. I checked every title against the record myself before it went on the page.

What is still growing

This is a living project, not a finished one. Every one of the 382 battles is now individually researched for its tactical story and its technology story, so that part of the record is complete, not a handful of samples. What is still growing is the reference material around that record: only a slice of the 382 battles carries a dedicated map so far, and the reading lists, while much larger than when this app launched, still leave plenty of smaller battles without a book of their own. I would rather grow slowly and get it right than rush and get a name or a date wrong. Anything I write myself about tactics, technology, or strategy goes through a review step before it reaches this page. That is the same standard I hold the novels to.