A Breach in the Army’s Engineer Priorities

Abstract

Army engineers must open routes, protect forces, analyze terrain, and sustain operations under enemy observation and fire. Recent changes in force design and new capability experiments raise questions about how Army leaders rank those requirements when resources are limited. Public guidance explains the missions and capabilities but offers limited insight into the choices among them. The Army Engineer Regiment should define an operational problem for a stated planning period, test competing investments against campaign scenarios, and explain the risks accepted when one capability receives priority. Clear guidance would help commanders prepare and employ engineer forces in line with those choices.

During Ukraine’s 2023 counteroffensive, breaching a Russian minefield meant more than clearing mines. Ukrainian forces had to find a route, protect the breach force from observation and fire, keep the lane open, and move follow-on forces through. Russian forces used drones, artillery, and renewed mining to attack Ukraine’s effort. During the operation, Russia damaged or destroyed roughly 60 percent of Ukraine’s breaching equipment in the initial effort. The fight showed how quickly an engineer mission becomes a contest for time, equipment, and people.

The US Army Engineer Regiment faces choices across a similar range of requirements. It must prepare to breach defended obstacles, deny routes to an enemy, protect friendly forces, analyze terrain, and sustain operations. When personnel, funding, and training time cannot cover every need, commanders must know which missions take priority. The Army should state those priorities and explain the risk accepted when it funds one capability over another. The Regiment needs an explicit account of those choices, so commanders and units know what to prepare for first.

The Army should define the operational problem guiding engineer investments for a stated planning period, test competing capabilities against campaign scenarios, and explain the risk accepted when one receives priority. Explicit guidance would connect force design, doctrine, and experiments such as autonomous breaching to decisions the Regiment and the Army can act on.

Strategic Guidance and Engineer Priorities

The 2026 National Defense Strategy sets national priorities, but the Army must decide what those priorities require of its engineers. The strategy calls for defense of the homeland, deterrence of China along the First Island Chain, greater allied responsibility for regional security, and stronger domestic production. Army leaders must translate those aims into choices about engineer forces and capabilities.

Future combat will require simultaneous engineer support for movement and protection. Army assessments of the operational environment describe widespread sensors, uncrewed systems, precision strikes, and massed fires that make movement and protection more difficult. A study of Russian minefield tactics shows how deep obstacles, drone surveillance, and artillery can work together to slow an attacking force. Engineers must prepare to open routes through defended terrain while helping friendly forces survive and sustain operations.

When campaign requirements change, the Regiment needs priorities to match the defined planning period. Operations across dispersed islands may require airfield and port repair, terrain analysis, and support for forces working with limited infrastructure. A ground campaign against defended obstacles may place greater weight on breaching and counter-mobility. Army leaders need a way to explain which requirements take precedence for a given planning period and what capacity they accept less of as a result.

The Chief of Engineers has named urgent concerns, but the Regiment needs to know how they rank. In March 2025, the Chief identified equipment readiness, autonomous breaching, and counter-mobility as his three Engineer Regiment priorities. Each addresses a need in future combat. The Chief can collaborate with the Army staff, commanders, force developers, and acquisition leaders to explain how they weigh those needs against one another and against other engineer missions.

Equipment readiness, autonomous breaching, and counter-mobility are concrete needs, but the list does not explain how engineer priorities follow from the National Defense Strategy. A defense along the First Island Chain may place heavy demands on ports, airfields, dispersed bases, and allied infrastructure. A campaign against defended ground positions may place greater weight on breaching and counter-mobility. The Regiment needs to say which campaign requirements drive its choices, why these three concerns rise above competing needs, and what engineer capacity the Army will accept less of as a result. Deliberate choices become concrete in force design, where the Army decides which engineer units commanders receive and what those units can do.

Force Design and Mission Priorities

Moving engineer battalions to divisions gave commanders greater control over scarce engineer capacity. The Army’s 2024 Force Structure Transformation White Paper describes the move from brigade combat teams to divisions. Division commanders can direct those battalions where the fight requires them. The Army also adjusted its force structure to fit available personnel, making choices about engineer support more consequential.

Division commanders may have to choose among engineer missions that are urgent at the same time. A division may need engineers to open a route through obstacles, prepare defensive positions, and repair main supply routes. The commander must decide which work begins first, how long each task can wait, and whether available engineers can support all three simultaneously. Clear priorities would help the staff make those choices before competing requests arise during an operation.

The Army should test how divisions make those choices with the engineer forces they have. The white paper explains the organizational change but gives limited public details on how divisions should weigh competing engineer missions. Realistic scenarios can show where capacity falls short, which mission takes precedence, and what risk the division accepts when another task waits. Force design determines which engineer forces a division has; doctrine explains how commanders use those forces together.

Doctrine and Investment Priorities

Engineer doctrine shows how the three engineer disciplines contribute to an operation. The Army’s field manual on engineer operations describes combat, general, and geospatial engineering as disciplines that support one another. Combat engineers help forces move through obstacles and build protective positions. General engineers construct and repair facilities and infrastructure. Geospatial engineers provide terrain information that helps commanders plan and direct operations.

A division may need all three disciplines to keep a force moving. Geospatial analysis can help identify a route through difficult terrain. Combat engineers can open the route, while general engineers repair the roads and facilities needed to sustain movement. Doctrine gives commanders a common understanding of how those efforts fit together.

Knowing how the disciplines work together does not tell Army leaders where to invest first. Leaders must decide which units, equipment, and skills need added capacity for the campaigns they expect to fight. A planning scenario might show that defended obstacles require more breaching equipment, while another might place greater requirements on port repair or terrain analysis. Tested scenarios can help leaders explain where they will invest first and what work will receive less support.

Major Initiatives and Requirements Definition

Autonomous breaching may reduce soldiers’ exposure, but the Army needs evidence of how much capability these systems add. An Army study of Russian minefield tactics describes how drones, artillery, and deep obstacles work together to slow an attack and expose the breach force. The Army is experimenting based on the results of the Russia-Ukraine war.

Project Sandhills 2.0 lets the Army test autonomous breaching under field conditions. The Engineer Autonomous Breaching Capability initiative adds a path from prototype testing to a production decision. The Army selected four companies in July 2026 and plans demonstrations followed by a unit assessment in early 2027. Unit feedback will inform the production decision. The Army has yet to decide whether these systems will enter production or reach units.

A production decision should weigh the systems’ performance as well as manning, maintenance, and training costs against competing engineer requirements. If the Army fields autonomous breaching, commanders should understand what capabilities the systems provide, what support they require, and which other engineer requirements may receive fewer resources.

Organizational Priorities: Connecting Choices to Purpose

Force design determines where engineer capacity sits. Doctrine explains how the disciplines work together. Experimentation tests new ways to perform specific missions. Each informs a different decision, but Army leaders have yet to explain how they weigh those decisions against campaign requirements.

The Regiment needs one standard for judging choices about forces, skills, and equipment. Army leaders should state the operational problem each choice addresses, the capability receiving priority, and the risk accepted elsewhere. A standard would help commanders understand how decisions across force design, doctrine, and experimentation serve the same purpose.

Commanders need priorities before they plan and train. Clear guidance would show units which engineer capabilities to emphasize, which missions must rely on existing capacity, and where they should expect a shortfall. The next section sets out how Army leaders can develop and communicate that guidance.

What the Engineer Regiment Should Do

Army leaders should give the Regiment a stated operational problem and use it to rank competing engineer needs. The Chief of Engineers can bring the Regiment’s needs into this focused work. Leaders responsible for requirements, force design, and resources can then make decisions within their authority. Five steps would make those choices clear to commanders and units.

First, Army leaders should define the operational problem that will guide engineer investments for a stated planning period: helping friendly forces gain and preserve access to terrain while denying the enemy the same access. They should identify the campaigns that drive planning, the engineer capacity available, and the missions competing for that capacity. Leaders should rank added capabilities by how much each one would protect campaign objectives, tempo, and force survivability.

Second, Army leaders should test investment choices against operational campaign scenarios. A ground campaign against layered defenses may place breaching capacity first. An island campaign that depends on damaged ports may place port repair first. For each scenario, leaders should identify the shortfall that poses the greatest risk to the campaign, assign priority to the capability that addresses that shortfall, and state the risk accepted in other engineer missions. They should repeat the analysis across the campaigns the Army expects to fight.

Third, Army leaders should tell commanders which capabilities receive priority and where capacity will be limited. Guidance for a defined planning period should state the operational problem, the capabilities receiving emphasis, and the missions expected to rely on existing capacity. Commanders can use that guidance to plan training and prepare requests. Doctrine can show how the three engineer disciplines support the stated priority.

Fourth, Army leaders should test whether force structure can support those priorities. Exercises and planning scenarios can show whether divisions have enough engineers to meet simultaneous requirements for mobility, protection, terrain analysis, and infrastructure repair. Where capacity falls short, leaders should identify which task takes precedence, how commanders can shift available forces, and what work must wait.

Finally, Army leaders should use the same standard to decide whether to field new capabilities. Sandhills offers a test case. A fielding review can compare the demonstrated gains from autonomous breaching with the personnel, training, and funding required to sustain the systems. Army leaders can then explain how the decision addresses the stated operational problem and which other engineer need receives less support.

Conclusion

The Army cannot give every engineer mission added capacity at once. Leaders should define the operational problem for a stated planning period, test competing needs against campaign scenarios, and identify the risks behind their choices. Deliberate decisions would guide force design, training, and equipment investments.

The Chief of Engineers should lead the Regiment in stating the operational problem that will guide engineer priorities. He should bring force developers, commanders, and resource leaders together to test competing needs against campaign scenarios. Then he should tell the Regiment which capabilities receive priority, which missions will rely on existing capacity, and what risks the Army accepts. Explicit guidance would give commanders a basis for force design, training, and equipment decisions.