The Unit Deployment Manager keeps a unit ready to project people and equipment forward. The UDM lives at the intersection of personnel readiness, mobility processing, equipment posturing, and the training events that wring the rust out of all of it. The job is steady-state coordination most days, then a sprint when a tasking lands.
UDM is an additional duty in most units, usually filled by a senior NCO with previous deployment experience. The role wears a few different hats over a typical AEF cycle.
One sentence version: the UDM owns whatever stands between an individual airman or piece of equipment and being usable forward. Training shortfalls, expired medical, missing UTC components, paperwork gaps. If it would stop someone at the deployment line, the UDM is supposed to have caught it months earlier.
Units rotate through phases that drive what the UDM is focused on at any given moment. Specific names and durations vary by service and posture model, but the rhythm is the same.
Just back from a rotation. People are on leave, equipment is being recovered, and the unit is rebuilding. UDM work here is administrative cleanup: closing out mobility folders, reconciling equipment accounts, capturing lessons learned, documenting any individual who came back non-deployable.
The longest phase and the one that defines whether the unit will be ready. Training currencies get refreshed, the mobility folder gets rebuilt, exercises run, and any deployable shortfalls get worked. The UDM should be heads-down on the readiness rosters during this phase.
The unit is on the bench. Taskings can land at any time. The UDM is watching the FAM's taskings inbox, keeping the unit's deployable roster current, and coordinating short-notice mobility processing if a name gets pulled.
The forward element is downrange. The home-station UDM is supporting the rear detachment, processing replacements if they're needed, and beginning to plan the reception cycle.
The unit is coming home. Reintegration briefings, customs and agriculture inspections, equipment turn-in, medical screenings, and the start of the reset paperwork pile.
A Unit Type Code, or UTC, is a five-character code that describes a deployable capability the unit owes the joint force. Each UTC has a Mission Capability statement, a list of personnel positions with required skills and ranks, and a list of equipment that travels with it.
UTCs are the link between abstract joint planning and the specific names and serial numbers a UDM has to produce on tasking day.
The deployment processing line is the choreography that turns a tasked airman into a manifested passenger. The UDM runs the unit's portion and coordinates with the installation-level functions.
Every deployable individual has a mobility folder, paper or electronic, that documents currency on training, medical screening, dental, immunizations, weapons qualification, fitness, ancillary training, and any country-specific requirements. The UDM builds it, keeps it current, and brings it to the line on processing day.
A member who fails any station is non-deployable until the issue is resolved. The UDM's job in the weeks before the line is to ensure no one fails on the day.
Once the people are processed and the equipment is staged, it has to move. The UDM coordinates with LRS and the Aerial Port to make that happen.
Readiness is built in training, not in the deployment line. The UDM owns or supports several training events that exercise the system before it has to work under real pressure.
Computer-based training, weapons qualification, self-aid and buddy care, chemical defense, anti-terrorism, and ancillary training. The UDM tracks the currency dates and prods members and supervisors before items expire.
Mobility exercises (MOBEXs), Phase II exercises, and command post exercises stress-test the deployment process. The UDM helps build the scenarios, run the events, and capture findings.
For roles that require capstone training, the UDM is often the one who builds the realistic environment around the exercise. For a Contingency Contracting Officer (CCO) Capstone, that means setting up a fictional contracting office complete with prior workload that the trainee can walk into and react to.
That is what the CCO Training Tools section below is for.
A growing toolkit of builders that produce realistic supporting contract documents (Form 9, 1449, 1442, BPA, IDIQ) for CCO Capstone exercises. Generate a stack of fictional prior workload, drop it in a folder, and hand the folder to the trainee on day one.
Capstone Builder Hub CCO Training Tools Form 9 builder is live. 1449 Section Builder is live. 1442, BPA, and IDIQ builders are on deck. Each one generates a downloadable PDF locally in the browser, so nothing sensitive ever lives on the site. Open the toolkit →The exact directive numbers shift over time as services issue new guidance. Verify the current version with your installation's Logistics Plans office or Functional Area Manager before citing.