Speculative Fiction Writers Guide to War, part 15: Combat Support Training
Travis P here. Our last two posts have discussed training, the last one on the topic of combat arms training and the one before that on high-end capabilities, which are particular types of weapons that require a team (usually a large one) working together in a complex way to make an individual weapons system operate. This week we will discuss the training of combat support specialists, people who wear military uniforms and are trained in the basics of combat, but whose primary job is to support the war fighters rather than fight themselves. (Note that modern military studies distinguish between “combat support” and “combat service support”–I’m rolling both those terms together under the name of “combat support.”)
The earliest imaginable form of combat support would stem from ancient tribal warfare in which warriors (let’s be honest, they were almost always men) went out to battle and the wounded among those who survived to return home would be bandaged and given herbal remedies by village healers (who were, again, simply telling the truth, usually women). This generic type of scenario that played itself out throughout tribal societies across most of the globe is based on non-professional warriors, what I’ve previously called “barbarian” warriors (with no insult intended).
Early human literate civilization, the Mesopotamians, were the first to specifically train warriors to fight as a full-time profession. There’s no direct evidence I know of that they also incorporated combat support specialist into their military. Yes, by the time of the Neo-Assyrian Empire, a military we know a great deal about, it’s evident the Assyrian Army marched with various types of combat support personnel, to name only some of them: cooks, baggage handlers, chariot wheelwrights, healers, scribes who managed supplies and record keeping. But these activities were handled mainly by slaves or free non-military personnel. It wasn’t soldiers in combat armor, with combat training, performing these tasks, with one likely exception.
Military engineers, who were responsible for building ramps and bridges and various other instruments to breach enemy defenses may have been wearing armor and trained in combat. After all, their construction projects, such as the ramp leading to the wall of the Israelite city of Lachish, allowing access to siege engines that would destroy the wall (one of the high-end weapons systems of their day), was built under enemy arrow attack. It’s at least possible the engineers supervising the build represented a specific branch of the Assyrian military, military engineers. But not enough Assyrian history has been preserved to be certain of that.
By the time of the Roman Empire, there’s no longer any doubt. While the Roman army also employed non-military combat support personal (especially slaves/enemy POWs), Romans made use of military engineers, men in armor who were trained both in fighting and also what we can think of as the non-military profession of engineering, to support ongoing combat by building various kinds of structures. (Note that combat engineering, which is essentially blowing things up or otherwise destroying them, wasn’t its own specialty yet. Roman military engineers generally constructed devices rather than destroyed them–devices with war-related purposes, but still.)
The advantage of having your combat support personnel receive military training themselves is based on the fact it didn’t take ancient people long to figure out you can ruin an army by attacking its supplies, or baggage train, i.e. its combat support. The ancient solution to this problem was to divert combat troops to guard duty, protecting the supplies and support personnel.
Over a long period of time, militaries came to realize it’s actually more efficient to train the support personnel to defend themselves and to give them a common background with the combat arms personnel, allowing them to be integrated into combat units, where their early intervention is much more efficient than keeping military and civilian worlds entirely separate. The “early intervention” phrase especially applies to combat medics (a.k.a. corpsmen). A medical person in uniform in a combat formation can provide immediate life-saving help much more effectively than hoping a warrior survives wounds until the battle is over or he can be taken to the rear, when he can finally see a healer. But this also applies to a wide variety of other specialties–if it’s better to have your engineers or cooks or logistician or whomever nearby than far away in many situations. Which means it’s better to have them in uniform. (By the way, the person responsible for putting medics in combat units for the first time was Dominique Jean Larrey, a surgeon who served in Napoleon’s army.)
A military member with a non-combat job can be ordered into danger where civilians would be hesitant to go–and where they might have no idea what to do if they came under attack. In the Twentieth Century, the idea of training combat support troops really took off, modern militaries increasingly embracing the notion than they should be able to provide for themselves with support personnel in uniform. In World War I, roughly two-thirds of US troops were in combat specialties, only one-third support. By WWII, the support outnumbered the combat troops by 60% to 40%. In Korea and Vietnam, the WWI proportions flipped, so that only one third were combat forces and two thirds combat support. For the Cold War military in Germany, only 25% of the troops in uniform were combat arms specialists–75% were combat support.
The post-911 conflicts have hired more on-site civilian contractors to do jobs that belonged to combat personnel in the 20th Century militaries, so that in Iraq as of 2005, 40% of the US military forces in the country were in combat specialities, but if you take the civilian contractors into account, combat specialties accounted for only 28% of all United States military personnel in Iraq in 2005. (The source for the numbers quoted here are from a study for the US Army by John McGrath.)
It could be that the trend to reduce the number of combat support personnel increases over time. Though it could be that militaries of the future will turn both combat and non-combat roles over to robots and automated systems, in certain jobs, non-combat specialists are unlikely to ever be replaced (e.g. troop transport pilots), whereas in other jobs (e.g. cargo truck drivers), robots will likely take human jobs as soon as it’s feasible to do so. All things considered, he proportions of combat to combat support personnel should stay about the same for the foreseeable future.
Why do I bring all of this up?
First of all, I want the readers of this series to be aware of the existence of combat support military personnel. Many readers of this site are fantasy writers and fantasy worlds usually parallel medieval or ancient models of warfare. So your stories may not include non-combat specialists who are part of military organizations, i.e. personnel who receive military training. Yet the things the combat support specialists do need to be done by someone else. You need to keep that in mind.
Second, you should be aware of how already-existing speculative fiction has a times focused on combat support specialties. Star Trek has done so extensively, as Travis C will mention.
Third, this article intends to make you aware of the challenges of training someone to be fully proficient in a job that is essentially a non-combat profession, such as the military version of being a paramedic, but at the same time being proficient at warrior skills. It isn’t easy and for certain combat support specialties training can last much longer than combat arms training–usually, of course, the combat support troops are not as good at combat. But still, they can and do engage in combat as needed–and while they are in general in not as much danger as combat specialties, they can and do get wounded and killed in action. (Note Hollywood has produced at least one major movie that focused on the actions in combat and training of a combat support soldier–Hacksaw Ridge.)
Fourth, I want story makers to be aware that stories can be told from the point of view of combat support troops–and such stories are not necessarily less interesting than hearing about the most elite troops fighting as consummate professionals. This especially relates to the fact many groups in the history of Christianity have been pacifists–but as combat support soldiers, they could be thrust into a combat situation nonetheless (as per Hacksaw Ridge and my own science fiction short novella on Amazon, Unknown Biologic).
Travis C here with some helpful illustrations of our combat support topic. To highlight Travis P’s last point, my favorite series in recent years is Glen Cook’s The Black Company, which is told through via point of view of the mercenary company’s doctor, who happens to function as the Annalist or historian. In this role, Croaker has first-hand knowledge and a legitimate reason to describe the deeds of the Company, and I feel the series is better because of that unique viewpoint.
If you’re in the world-building phase, it’s worth spending a little bit of time thinking through what combat support functions need to be identified and further worked out before the story progresses. Readers will tell if you’ve created a military juggernaut of combat capability that has little support structure and would never actually last a day in the field. That said, you also don’t need to develop detailed doctrine about supply depot procedures for turnips (unless that supports the story, of course!) A few things to consider:
- What functions need to get accomplished? Travis P mentioned several: medical, logistics of moving troops and supplies, the supplies themselves, quarters for troops, repair and maintenance of equipment, other engineering needs, etc.
- Who is going to accomplish those functions? Regular troopers, trained but non-fighting personnel, volunteers, families, slaves?
- Does the success of, or lack/failure of, one of those functions become a necessary plot element in the story?
- If so, what additional detail should be developed to add color to the picture?
If you answered “Yes” to question 3, then there’s lots of great examples in literature and media demonstrating unique ways to include this information, weave it into the story world, and really impact the audience. Here are 3 that come to mind:
Make It Easy To Identify Combat Support
In particular during The Next Generation, Star Trek used color to train its viewers to identify the various roles found across the Federation’s Starfleet. Three primary colors: red, blue, and gold, were an easy way to distinguish between Command, Sciences (including medical), and Operations. Red and Gold uniforms kept the ships running and may and may not have been directly related to combat, but blue uniforms were a clear sign of a combat support specialist.
As an audience, we had expectations for any character depending on the color of their uniform. Red represented leadership and tactical training, blue an intellectual mind and appreciation for research and exploration, and gold the detail-oriented mind of an planner and engineering expertise to run a warp core. As expected, the writers of successive iterations of the Star Trek universe then flipped those expectations on their heads. The interplay between divisions yields great plot lines to explore ethics and relationships among characters.
Every George R.R. Martin reader knows the Night’s Watch has its own maester to perform record keeping and healing. The clink of their maester’s chain identifies those trained by the Citadel.
There’s probably a unique way you can easily help readers identify with the combat support functions, understand how they are different from the combat arms characters, and help build structure in your world.
Understand the Tension Between Combat Arms and Combat Support
That’s probably not a surprise, but I think it’s safe to say even the “barbarian” form of combat support garnered no small amount of tension. One party is doing the fighting, right in harm’s way, and subjecting themselves to imminent danger. The other side is waiting in the wings, perceived as being away from danger, but likely at more risk since the enemy knows how critical these roles are. Grunts are just dumb killers. Support are just scared weaklings incapable of doing more. You likely know these tropes already.
We’ve used Brandon Sanderson’s Stormlight Archives several times already, but here’s an example of the use of bridge crews (manned by slaves, unprotected from enemy fire, yet vital to movement of the armies across the Shattered Plains) to meet a critical support function with significant contrast to the armies and Brightlords conducting combat. Sanderson not only uses Kaladin as one of his main characters, but also uses the tension between organizations to drive the plot forward.
David Farland’s second book of the Runelords series, Brotherhood of the Wolf (not to be confused with a film with the same name), does an excellent job of using the connection between Runelords who take endowments of power to those who give up those powers ( called Dedicates) to drive the story forward. The military cannot function without the enhanced abilities of strength, metabolism, wit, and senses that the Dedicates give up. At the same time, these Dedicates are ideal targets for military action since killing a Dedicate will immediately remove that attribute from the bearer. The Dedicates require significant protection, at the cost of military flexibility. Farland excellently uses this interplay to develop characters and add tension to the plot.
Change Your Point of View
Lastly, and in line with my shared favorite, consider if you should add a different point of view to your story. We’ve all heard stories told from the perspective of the knight, the lord, the king, the starship captain, the great-grand-poobah. We’ve also watched the unlikely hero become a military mastermind (and as we’ve discussed earlier in the series, just how unlikely that is). What about the war told through the eyes of the frontline surgeon? The sapper digging under the castle walls? The cook hearing everyone’s stories at the end of the fight? The engineer keeping the hypercore going on that rust-bucket starfrigate? It may not be the primary point of view or main character you develop a story around, but these secondary characters can add a lot of detail in interesting ways as interludes, prologues and epilogues, or even just scenes spread through the story.
Just like the combat arms functions, combat support has its own training needs that can add even more detail to your worlds. Maybe as backstory, maybe as a source of tension between combat functions, maybe just for fun. Being honest about how the military works in the context of your world is vital to building meaningful engagement with a reader. Plus, it’ll help you when you’ve got a few more chapters to fill and want a way to show, not tell, what’s happening in your military stories.
Travis C made a point about tension between combat arms and combat support. Instead of altering his observation in the text of our article itself, I left it as is and decided to comment on it here.
My experience on that tension is “often but not always.” Support guys who do their jobs very well, in a way that directly helps combat troops, especially medics/corpsmen, but also to a lesser degree mechanics, chaplains, and some others, are often treated VERY well by combat arms guys. Because if someone is saving your buddies’ lives in tough times–or performing near-miraculous repairs of your equipment–or risking their life to provide religious support in a danger zone, etc, it’s not normal to resent such a person. So in peacetime, there’s more potential for tension than during war. Unless of course if the combat support types are clearly shirking their duties, which happens sometimes, or have jobs that don’t directly affect the lives of combat arms guys, which happens frequently.
Note there also can be tension between different types of combat arms, whether between different branches (say tankers and infantrymen), or between elite and non-elite troops (e.g. special forces don’t always get along with regular infantry). When I was an artillery officer, our branch generally thought infantry guys were dumb–and also glory hounds. Whereas infantry saw us as fat and lazy (and I’d say there was a partial kernel of truth to both accusations).
Though Travis C, as a US Navy officer, inhabits an inherently different world than I do as an Army guy.
But anyway, FYI. 🙂
That is a great point; no intention on my part to paint it as more than a difference that can exist, but certainly doesn’t need to. I think it’s important to recognize there are differences (like in so many other ways we can make them), and that you as a writer get to choose what to do about it:
– There’s a difference and it’s painted positively. Thank goodness we have that support from the rear; they do awesome work; they kept my buddy alive.
– There’s a difference and it’s neutral: either not recognized at all, or at least not impacting the story. Much of the time we’re so focused on our mission and role we don’t dwell on the other folks.
– There’s a difference and it’s painted negatively (maybe warranted, maybe unwarranted). This is a possible way to introduce some tension in a storyline.
In my experience, >90% of the time, there was more likely to be tension between folks over matters of performance/quality than with what role they performed. Do a great job and support the team and mission, and folks appreciate that (even if it’s just a head nod). Do a bad job or fail at a critical time and judgment begins. Many folks have short memories. Some do not.
Lastly, there’s also a difference between talking smack and internal beliefs. Again, from my experience, there’s a lot of smack talk between communities of practice, but fewer experiences where deep-seated tensions existed that impacted mission accomplishment. Aviators might all be “hotshots”, but when an aircraft is the right tool for the job, you use it. because it’s all one team.
The impression I get when it comes to how much fighter training and roles a combat support person can have will often depend on how large the group they work in is, where they’re stationed, and how ‘advanced’ the army is.
With group size, I’m talking about circumstances like in Naruto. Some ninja might do solo missions, but often enough they work in groups of 3-10. On those missions, they could get attacked at any time, and although they might try to protect their medics, the medics will still get killed if they aren’t formidable fighters themselves. In some ways, that’s probably why there’s medics like Sakura, Tsunade and Kabuto that are dangerous fighters, but pretty able to also fill other capacities. They have no choice but to be competent in multiple areas. They aren’t necessarily as powerful as ninja that solely focus on combat (like Naruto and Sasuke) but they’re far from helpless. In a situation where there are huge armies of ninja fighting each other, though, some of the medics could probably get by with less combat training because they can stay in makeshift hospitals within bases well guarded by large numbers of their comrades.
As for how advanced an army is…some of that has to do with technology, but probably other things as well. In Star Trek, people would probably have to specialize a lot because maintaining, say, a warp core competently probably takes a lot more time, knowledge and dedication than certain parts of a more primitive army.
One of the chars in my current WIP ends up in a lot of roles throughout his life partly because the armies he’s in are more primitive. He starts off learning to fight, and does so competently, but then he is put under circumstances where he has to learn how to be a medic so he can infiltrate another faction. After he goes back to his birth faction, he does everything to climb the ranks and eventually takes on a more tactical and advisory role, which he has the experience for by then. But he still puts his medic skills to use when need be, and is also the closest thing the faction has to a priest and historian. He’s not exactly an expert at any one thing, but he can apply what skills he has to a variety of roles.
To him, this isn’t impressive, because as he points out, the things he’s learned can be applied to a lot of areas. He’s educated as a medic, so he can help patch up his comrades when the other medics in the faction are too busy. He knows how to read and write, so he chooses to record some historical things in the faction during his free time. His role as priest is as simple as passing on some things he learned from his father during childhood, as well as offering advice when his comrades ask for it. He can shift gears and do these things because their army isn’t complicated enough that he has to only focus on one of these things. But if his faction was advanced enough to deal with large war machines, he would probably not be involved in the daily aspects of running them because that kind of specialization would take a lot more time to learn and take him away from areas he is needed in more.
Or for Japanese Star Trek with a much more sensible bridge design, there’s Space Battleship Yamato 2199. Okay, having a WWII-era battleship as the basis for a starship design is pretty dumb when you think about it, but it definitely has a dieselpunk charm. I think this show gives a better sense of just how many frikkin people it takes to run a ship than Star Trek generally does, with easily two dozen recognizable recurring characters rather than the token-ish sort of thing that Star Trek tends to do, where on a detailed episode you maybe get a secondary engineer/security dude/pilot with a name and more than one line.
Opening theme: https://youtu.be/w6LFkMniuTk
I like the discussion of sci-fi going on. It’s interesting for me to see how various storytellers portray the future: have we moved away from people, or have we actually just make things bigger so there’s an even bigger need for them? I think we’ll see more stories like Passengers that explore over-reliance on AI and automation, as well as examples of reduced crews like in Star Trek: Into Darkness. I know several industries in the US related to defense & security that are actively advocating for reduced crews of operators in their system/machine/function. That’s one version of the future.
I also certainly see the evolution of cross-training becoming greater and greater. I thought the premise of the Netflix Lost In Space series to be kind of interesting: to earn a spot on a colonization mission, you have to pass rigorous testing and be training in multiple skills, even the kids. There were some neat plotlines resulting from that premise, many of which cross genres.
Have you seen the new Netflix Godzilla movies yet? They’re pretty good, and now that I think about it exemplify some of the things you guys talk about here.
I haven’t, so thanks for the recommendation! I got caught up watching All Monsters Attack the other day and had kaiju on my mind
Have you gentlemen considered issuing these blogs as an ebook? (Not sure what SpecFaith’s rules about republishing posts is.) I’ve been trying to save up the blogs for more in-depth reading when I have time, but a single ebook might be better formatted than what I have been doing. I just find these absolutely fascinating.
Actually, once we are finished, we plan to produce this series as a book. Speculative Faith is totally cool about this, too.
Thank you for your interest!
Very Important off-topic news: I repotted my cape primrose, and so far it does not look dead. This is momentous news, after I split some baby crowns off my African violet and, despite my encouragements to GROW, D*MMIT, within two weeks they were stone dead.
I don’t know much about African violets, but we’ve had other plants that look dead for a long while after being transplanted, but end up living/growing back later as long as they get watered now and then.
As a guy with waaaayyy too many succulents, I salute you!