Forging an Engineer Regiment for Large-Scale Combat Operations
Lt. Col. Michael P. Carvelli, US Army
Download the PDF 
In large-scale combat operations (LSCO), maneuver commanders depend on timely, decisive engineer support to create and exploit tactical advantage. Yet today’s Engineer Regiment carries a portfolio so broad that it dilutes attention, personnel, and materiel away from its doctrinal core of mobility, countermobility, and survivability (M/CM/S), the functions maneuver forces need most on the battlefield. This misalignment imposes avoidable friction on divisions preparing to fight peer and near-peer opponents.
The regiment’s current mission set encompasses doctrinal combat engineering (M/CM/S) as well as general and geospatial engineering, diving, firefighting, and strategic power support—capabilities often described as “sappers, mappers, builders, bridgers, divers, fire fighters, and power providers.”1 While technically proficient in each discipline, the regiment is stretched across tasks with competing priorities and resource demands. The result is organizational drag, readiness shortfalls, and allocation of scarce engineers to missions that do not directly enable maneuver commanders to close with and destroy the enemy.
Army doctrine clearly identifies “mobility, countermobility, and survivability” as the essential functions of combat engineers operating with maneuver forces.2 However, in practice, specialized engineering missions are consuming personnel and equipment that maneuver formations need focused on terrain shaping, obstacle development and reduction, breaching operations, and survivability works under enemy fires.
To support the maneuver commander’s warfighting imperative, the Engineer Regiment must recommit to its combat engineering core. This is necessary rebalancing that ensures the regiment’s most lethal and deployable capabilities are aligned to the decisive engagements of LSCO. By divesting missions that do not support maneuver, simplifying force design, and reallocating combat power to M/CM/S tasks, the regiment can increase its reliability and responsiveness for divisional maneuver forces.3
In LSCO against a capable peer, division and corps echelons cannot tolerate diluted engineer focus. A disciplined realignment of the Engineer Regiment toward its doctrinal combat engineering core will expand maneuver options, accelerate tempo, and strengthen decisive action at the point of contact.4 The maneuver commander does not need more tasks assigned to engineers; he needs engineers optimized for the fight that matters.
The Operational Cost of the Current Engineer Force Design
Sustaining the Engineer Regiment’s diverse capabilities requires focused investment across doctrine, organization, training, materiel, leadership and education, personnel, and facilities elements. The regiment must relegate peripheral missions to the shadows to refocus that investment on ensuring the primary objective—supporting maneuver—remains the sole occupant of the spotlight. The following data points illustrate readiness deficits, personnel overhead, and organizational drag that challenge the regiment’s ability to support the maneuver commander due to its broad portfolio.
The readiness deficit. Current equipment readiness data reveals significant challenges.5 Army brigades starting their intense training rotation at the National Training Center enter the main training portion with vehicle readiness well below the Army’s readiness target.6 The Government Accountability Office surveyed eighteen ground vehicle classes finding that since fiscal year 2015, mission capable rates declined for sixteen of them.7 Low equipment readiness in construction assets directly translates to increased vulnerability for the maneuver force commander. It means critical supply routes remain impassable longer, survivability positions take twice as long to build, and operational tempo slows to a crawl, giving the enemy time to regroup and strike.
Such a deficit in equipment readiness negatively affects the Army in training environments and in combat. Soldiers cannot train on broken equipment, leaving them less capable if called upon in conflict. In combat, unreliable engineer equipment makes it difficult for maneuver commanders to treat engineer support as a dependable planning assumption, especially when the scheme of maneuver depends on timely M/CM/S effects. This would not bode well for a tactical plan reliant on engineering capabilities. Low readiness rates threaten to marginalize engineer assets, as maneuver commanders may stop factoring unreliable support into their operational planning. Aside from the equipment readiness rate, there are personnel and training costs to be considered.
Personnel and training overhead. The Engineer Regiment encompasses thirteen military occupational specialties across seven functional areas. Each of these specialties, encompassing one sapper, one mapper, one bridger, six builders, one diver, one firefighter, and two power providers, demands dedicated personnel, materiel, and facilities for initial entry training and subsequent skill sustainment.8 As the regiment’s initial entry training footprint is geographically dispersed, spanning facilities in Missouri, Florida, Mississippi, and Texas, a vast training complex must be resourced to keep the diverse portfolio of personnel trained. Maintaining these skills requires training institutions, senior personnel, and supporting infrastructure.
This institutional complexity strains the Army’s training base and dilutes focus. For every dollar and training seat spent on a niche capability like firefighting, a seat for a combat-critical skill like robotic breaching or battlefield obscuration goes unfunded, creating a direct opportunity cost against the regiment’s primary role to support maneuver.9 Maintaining these occupational specialties with this training footprint provides a risk to the regiment’s core tasks. In addition, the array of organizations that these personnel support displays another strategic burden.
Organizational drag. The Engineer Regiment’s organizational structure reflects its broad range of capabilities. Engineer vertical construction companies, engineer construction companies, and engineer support companies field overlapping personnel and equipment. Although each company is slightly different, there remain redundancies that complicate acquisition, sustainment, and deployment. Whether it is heavy versus light horizontal construction, or the ratio of vertical to horizontal squads, these organizational distinctions offer more nuance than tangible operational impact.
This redundancy creates an unnecessary logistical burden and complicates force packaging for corps- and theater-level planners. Deploying and sustaining three different types of construction units, each with unique equipment and maintenance chains, is inherently less efficient and agile than fielding a single, standardized, and more capable formation. To alleviate this organizational drag, the regiment must apply a framework of simplification, starting with its most basic tools.
Beyond the organization of these construction companies, the Engineer Regiment owns an array of concrete, quarry, firefighting, prime power, and other style companies and detachments that go in and out of favor over time. Other distinctions, such as a rough terrain airborne company, dilute the regiment’s focus even more.
Considering the readiness deficit, personnel and training overhead, and organizational drag, the regiment must focus on mission set that directly supports the maneuver commander during LSCO with a peer or near-peer adversary. Focused capability on decisive tasks outweighs generalized breadth.
These problems are not separate inefficiencies. Together, they show that the regiment’s breadth creates a force-design penalty. A regiment spread across diverse niche missions must sustain more equipment variants, more training pipelines, more organizational forms, and more specialized leaders than a combat-focused engineer force. That dispersion reduces standardization, weakens readiness, and makes engineer support less predictable for maneuver commanders at the point where tempo matters most. In LSCO, the issue is not whether each specialty has value; the issue is whether the regiment can provide commanders dependable M/CM/S effects at the speed and scale that LSCO demands.
A Targeted Framework for Divestment and Realignment
To meet the needs of LSCO and continually incorporate lessons from other conflicts, the regiment must focus on its core mission of supporting maneuver. Three principles will guide this focus.
Principle 1: Simplify to accelerate. From a materiel lens, the Engineer Regiment could reduce the variety of equipment available. For example, the Army maintains at least seven types of bulldozers.10 These require different repair parts, specialty tools, and manuals. Reducing equipment variety such as fielding a single bulldozer type would streamline logistics and reduce sustainment complexity. Although the nuance of each style of bulldozer is lost, the benefits of simplifying should be weighed when the Army is ensconced in a full mobilization against a peer threat.
Organizationally, the Army should simplify the various styles of construction companies into one. This company should focus on M/CM/S. Merging three company types into one modular formation would streamline the force generation process, allowing a division to deploy with a more predictable and potent engineering capability. Although general engineering supports sustainment and protection, the needs of maneuver commanders should be the priority to win decisively in LSCO.
If the regiment were to simplify its equipment and organization, it could save the sustainment and planning enterprises effort. For example, there would be fewer parts needed in bench and shop stock, a reduction in the number of specialty tools, and elimination of technical manuals. Planners would have fewer decisions to recommend such as the placement of each style of construction company for their respective echelons. These are time and resource saving measures that could save maneuver commanders and their staffs effort.
Principle 2: Transfer to specialize. To maintain a focus on LSCO, the Engineer Regiment could divest capability with Army headquarters approval. Although fraught with personal attachment, divestment to other branches could afford the regiment the ability to focus. Other regiments could benefit with the consolidation of related capabilities into their organizations. Three examples are transferring diving to transportation/sustainment, mappers to military intelligence, and firefighters to aviation.
Diving generally supports seaports and the movement of equipment and personnel ashore. This function aligns with existing transportation brigades (expeditionary) that are experts on water terminal operations.11 Because diving operations principally support seaport and beach terminal throughput, they align more directly with transportation brigades’ mission sets and would sharpen both branches’ focus if reassigned. The Transportation Corps gains a critical enabler for its core seaport mission, creating powerful synergy.12 More importantly, the Engineer Regiment sheds a significant institutional burden, freeing up leadership, training dollars, and personnel billets to reinvest directly into its primary function: enabling maneuver with enhanced M/CM/S capabilities. Moving geospatial efforts to another regiment could provide similar benefits.
Most geospatial teams that house the Engineer Regiment’s mapping capability coexist with military intelligence specialties. The Military Intelligence Corps has similar personnel, geospatial intelligence imagery analysts. Although engineer mappers and intelligence analysts differ in function, economies of scale could exist to incorporate them both into the Military Intelligence Corps. Collocating geospatial technicians with intelligence analysts would create a single, integrated production cell for all-source terrain analysis, directly benefiting maneuver planners. It would break down information silos and accelerate the delivery of a common operational picture. Creating new doctrine that formalizes intelligence support requirements to mobility and countermobility planning mitigates the risk of losing “engineer focus.” Consolidation of mapping and intelligence could reduce the training costs associated with disparate functions and locations.
Last, moving firefighters to the Aviation Branch places these enablers in the same functional area where they typically operate. As firefighters are typically associated with fixed infrastructure, and airfields have a continual need for firefighting capability, this shift enables consolidation based on location. Firefighting detachments would be better aligned with aviation units as they tend to gravitate toward established locations whereas Engineer Regiment forces span the operational environment.
Although doctrine shows that engineer units perform geospatial and general engineering functions in support of maneuver and sustainment operations, these functions often align more directly with sustainment, intelligence, and aviation mission threads in LSCO. By transferring these capabilities to organizations optimized for those mission threads, the regiment can commit more of its engineers to M/CM/S tasks.
Principle 3: Remove to prioritize. While transferring capabilities to other regiments solves the problem of ownership, it does not resolve the burden of “heavy” logistics. To truly dominate in LSCO, the Engineer Regiment must move beyond shedding niche roles and begin divesting logistically intensive missions that do not directly enable the close fight. Expeditionary (initial) construction would remain. However, uniformed engineers would no longer support temporary, semipermanent, or permanent construction including medium and high voltage power.13 Divesting this capability rids the regiment of its most logistically demanding and least mobile equipment sets, which are a drag on the Army’s ability to deploy rapidly.14 Divesting would also remove several of the builder and prime power occupational specialties. By removing these infrastructure and strategic power requirements from the uniformed force, the regiment can transform from a slow-moving construction corps into an agile, focused enabler.
The recommendations below are example applications of a broader force-design principle: the uniformed Engineer Regiment should prioritize capabilities that directly deliver M/CM/S effects for maneuver commanders in large-scale combat operations.
One application of this principle is divesting heavy road construction, major concrete, and strategic power generation capabilities from the uniformed Engineer Regiment. These missions impose some of the regiment’s most logistically demanding equipment, niche training requirements, and sustainment burdens, yet they contribute least directly to the maneuver commander’s immediate needs in the close fight. In high-intensity conflict, such capabilities risk slowing deployment, diverting command attention, and preserving force structure for functions that do not consistently deliver M/CM/S effects at the point of decision. Removing them from the regiment would allow uniformed engineers to concentrate on tactical and operational tasks that must keep pace with maneuver forces.
The same principle applies to the 249th Prime Power Battalion. Although prime power remains a necessary Army capability, it performs a strategic support function rather than a tactical combat engineering one. Whether that capability remains in a civilian organization, an Army-managed institutional structure, or another support arrangement is less important than the underlying point: it need not remain inside a combat-focused Engineer Regiment. Moving it outside the regiment would recover personnel spaces, reduce niche equipment and training burdens, and allow the Army to redirect end strength and resources toward capabilities that more directly support large-scale combat operations, including tactical breaching, bridging, and emerging M/CM/S technologies.
One illustrative institutional option is a civilian construction corps (CCC), or a similar alternative, for heavy construction, sustainment infrastructure, and strategic power functions that do not need to remain inside uniformed engineer formations. The value of such an arrangement lies less in its exact administrative form than in the force-design principle it reflects: missions that do not directly enable maneuver in the close fight should not consume disproportionate Engineer Regiment capacity. Preserving those functions outside the regiment would retain essential Army engineering capability while allowing uniformed engineer battalions and companies to remain focused on delivering dependable M/CM/S effects in LSCO. These recommendations are summarized in the figure.
The first step in this prioritization is the removal of heavy road construction and major concrete capabilities. These assets represent the regiment’s most logistically demanding and least mobile equipment sets. In a high-intensity conflict, these anchors slow deployment and divert command attention toward long-term sustainment projects. Divesting them ensures that every uniformed engineer focuses at or below the operational level, allowing them to keep pace with an advancing maneuver force.
Counterarguments
Some might argue that general and geospatial engineering are not peripheral but integral to Army operations across levels of war, and that divesting them from the Engineer Regiment could create seams in supported operations. Army doctrine identifies the three interdependent engineer disciplines—combat engineering, general engineering, and geospatial engineering.15 Each contributes to the commander’s freedom of action. General engineering supports infrastructure development, base construction, and sustainment efforts, while geospatial engineering provides essential terrain analysis and visualization that influence command decisions at tactical, operational, and strategic levels. These disciplines are designed to operate in concert to support assured mobility, protection, sustainment, and infrastructure development.
However, this article’s recommendation is not a doctrinal rejection of these roles but a force-design alignment for LSCO. In high-intensity conflict, the most critical requirements for maneuver commanders are M/CM/S tasks that doctrine emphasizes as the core focus of combat engineering units. By reallocating general and geospatial engineering capabilities to organizations whose primary missions align more naturally with transportation, intelligence, and aviation, and integrating their effects into synchronized operational planning, the force preserves these capabilities while enabling the regiment to concentrate on its most decisive battlefield contributions. This approach respects doctrinal roles while optimizing force packaging for the specific demands of LSCO.
Others might argue that removing capabilities like diving, prime power, and heavy construction from the uniformed Engineer Regiment could create operational gaps or dependence on external organizations that might not be as responsive to maneuver commanders. Army doctrine and historical precedent, however, show that many specialized engineer functions are effectively integrated through unified action with other services, agencies, and civilian partners while combat engineers remain focused on M/CM/S for maneuver forces. Doctrine articulates that engineer support is executed across the joint operations area by units from all three disciplines, and that tasks are assigned based on mission requirements at appropriate levels of command.
Some might argue that divesting the 249th Engineer Battalion would create unacceptable risk because it is the Army’s only prime power organization and routinely supports federal disaster response, including relief operations for civil authorities. The battalion’s mission includes providing commercial-level power to military units and federal relief organizations, making it a unique national capability rather than simply another engineer niche. However, that argument reinforces the point more than it refutes it. The 249th’s mission is highly specialized, strategic, and often applied domestically. Those characteristics distinguish it from the expeditionary M/CM/S tasks that maneuver commanders need from the Engineer Regiment in LSCO. Preserving the capability may remain necessary but retaining it inside the uniformed Engineer Regiment is a force-design choice, not a doctrinal requirement. The Army could preserve prime-power support through another institutional arrangement, such as the CCC, while freeing the regiment to concentrate on combat engineering tasks that directly enable maneuver.
Transferring or realigning nontactical functions does not diminish these capabilities; instead, it creates shared ownership and responsiveness across organizational boundaries while preserving uniformed engineer units’ focus. Although uncomfortable to some, simplifying, transferring, and removing some of the range of Engineer Regiment capabilities will enable the focus the regiment sorely needs to support maneuver.
Conclusion: An Engineer Regiment Forged for the Combined-Arms Fight
The US Army Engineer Regiment must evolve to meet the demands of LSCO against peer adversaries by refocusing on its doctrinal core of M/CM/S, the functions that directly enable maneuver and decisive action on the battlefield. Doctrine affirms these engineer functions as central to freedom of maneuver and force protection in combined arms operations.
Sustaining a broad portfolio of general engineering, geospatial, diving, and strategic support missions within the uniformed force diffuses institutional focus, complicates training pipelines, and detracts from readiness for combat engineering tasks that matter most in LSCO. Streamlining the regiment’s mission set through simplification of equipment and organizations, transfer of highly specialized capabilities to more doctrinally aligned regiments, and divestiture of burdensome missions will strengthen the regiment’s ability to mass engineer effects where and when they are decisive.16
By narrowing its focus to combat engineering core competencies, the regiment enhances its operational readiness and predictability for maneuver commanders, enabling more reliable M/CM/S support. Additionally, preserving heavy construction, sustainment infrastructure, and power generation through complementary institutional arrangements would retain needed Army capacity without burdening combat-focused forces.
Ultimately, the question is not whether every engineer capability has value. The question is whether the uniformed Engineer Regiment is organized to give maneuver commanders reliable M/CM/S effects when the fight begins. A regiment that tries to preserve every specialty risks fighting LSCO with too much institutional breadth and too little combat focus. A regiment forged around combat engineering core competencies will give commanders a more dependable planning partner and the Army a more lethal combined-arms team.
Notes 
- US Army Engineer School Senior Leaders, “U.S. Army Engineers: 250 Years of Building Strong,” Engineer, 17 June 2025, https://www.lineofdeparture.army.mil/Journals/Engineer/Engineer-2025-E-Edition/250-Years-of-Building-Strong/.
- Field Manual (FM) 3-34, Engineer Operations (US Government Publishing Office [GPO], December 2025), 2.
- Uwe Beyer and Oliver Ullrich. “Organizational Complexity as a Contributing Factor to Underperformance,” Businesses 2, no. 1 (2022): 93, https://doi.org/10.3390/businesses2010005.
- FM 3-34, Engineer Operations, 1.
- US Government Accountability Office (GAO), Weapon System Sustainment: Various Challenges Affect Ground Vehicles’ Availability for Missions, GAO-25-108679 (US GAO, September 2025), 13–27, https://www.gao.gov/products/gao-25-108679.
- Michael Mai, “The Army Is Mispricing Readiness, and Additive Manufacturing Exposes the Problem,” Breaking Defense, 17 February 2026, https://breakingdefense.com/2026/02/the-army-is-mispricing-readiness-and-additive-manufacturing-exposes-the-problem/.
- US GAO, Weapon System Sustainment, 10.
- FM 3-34, Engineer Operations, 63. The thirteen military occupational specialties identified for this article include 12B, combat engineer; 12C, bridge crewmember; 12D, diver; 12G, quarrying specialist; 12H, construction engineering supervisor; 12K, plumber; 12M, firefighter; 12N, horizontal construction engineer; 12P, prime power production specialist; 12Q, power distribution specialist; 12R, interior electrician; 12W, carpentry and masonry specialist; 12Y, geospatial engineer. This list does not include officer, warrant officer, senior noncommissioned officer, or maintenance specialties.
- See, for example, Michael Carvelli, “Invest in Battlefield Obscuration to Win During Large-Scale Combat Operations,” Military Review 105, no. 2 (March–April 2025): 101–7, https://www.armyupress.army.mil/Journals/Military-Review/English-Edition-Archives/March-April-2025/Battlefield-Obscuration/.
- The seven types of bulldozers include two D6 and four D7 bulldozer variants and the M105 Deployable Universal Combat Earthmover.
- FM 4-0, Sustainment (US GPO, August 2024), 28.
- Matias K. Sejersen, “Operation Turning Point,” Engineer, 1 January 2024, https://www.lineofdeparture.army.mil/Journals/Engineer/July-24-Engineer/Operation-Turning-Point/.
- Unified Facilities Criteria 1-201-01, Non-Permanent DOD Facilities in Support of Military Operations (Department of Defense, 8 August 2023), 8, https://www.wbdg.org/FFC/DOD/UFC/ufc_1_201_01_2022_c4.pdf. Temporary construction is defined as structures having an expected use of five years or less. Semipermanent construction aims at a life expectancy of less than ten years. Permanent construction is ten or more years.
- Thomas A. Johnson, “The Earthmoving Syndrome,” Army Sustainment Professional Bulletin 3, no. 1 (January-February 1971): 20–23, https://www.army.mil/article/286636/the_earthmoving_syndrome.
- FM 3-34, Engineer Operations, 1–3.
- Gerald Law, “Incorporating the Five Breaching Tenets,” Engineer 44, no. 1 (January–April 2014), 35.
Lt. Col. Michael P. Carvelli, US Army, is an assistant division operations officer in Division East, First Army, at Fort Knox, Kentucky. He holds a BS in civil engineering technology from the Rochester Institute of Technology; an MS in operations management from the University of Arkansas; an MS in civil engineering from the University of Florida; an MA in defense and strategic studies from the US Naval War College; and an MA in military operations from the School of Advanced Military Studies, US Army Command and General Staff College. He is a registered professional engineer in the state of Pennsylvania and is a certified project management professional.
Back to Top