The Team and the Orders
Almost nothing a Unit Deployment Manager does happens alone. Taskings arrive from one direction, readiness data flows back the other way, and a dozen offices each hold one piece of whether a member can actually get on an aircraft. Knowing who holds which piece turns most of this job into a phone call to the right person.
01The players
Deployment work is a chain. It starts with a commander somewhere who needs a capability and ends with a specific person carrying a specific skill set onto a specific aircraft. A Unit Deployment Manager (UDM) sits near the end of that chain and talks to most of it.
These are the roles worth knowing by function rather than by name, since the people rotate and the functions do not.
The commander of a geographic or functional combatant command, who owns a mission and identifies the capabilities needed to do it. Demand starts here. A UDM will likely never speak to one, but every tasking that lands in the squadron traces back to a requirement somebody at this level validated.
Sits between Air Force headquarters and the wing, and translates broad requirements into sourcing decisions for the units underneath. Supplements to Air Force instructions often come from this level, which is why the local version of a rule can differ from the one published service wide.
Contracting's own manager for deployment purposes, responsible for matching contracting requirements to contracting people across the enterprise, and the office that holds the career field's unit type codes. Contracting is small and frequently deploys individuals and small teams rather than large formed units, so this office works at the level of specific names and skill levels more often than it would in a bigger career field.
A UDM talks to this office directly. The readiness cell handles the installation, and the Functional Area Manager handles the career field, and neither one substitutes for the other.
Owns the squadron's readiness and signs what goes out the door. The commander answers for the accuracy of what the squadron reports and for decisions about who fills a tasking. A UDM builds the picture the commander signs, which is a good reason to keep that picture honest.
The installation's deployment engine and the single most useful phone number a UDM has. The cell sets the local standard, runs the timeline, trains the unit deployment managers across the base, and is accountable for getting members out the door. Most questions in this section end with "ask the IDRC," and that is the intended answer rather than a dodge.
The officer accountable for the installation's deployment process end to end, including the installation deployment plan and the execution day machinery. Where the readiness cell is the working level, this is the level that owns the process itself.
Owns the personnel side of deployment eligibility: records, availability coding, and the accuracy of what the personnel systems say about a member. When a member's status on paper disagrees with reality, this office is usually part of the fix.
The squadron's translator and tracker. The UDM turns installation level requirements into squadron level action, keeps the readiness picture current, and surfaces problems while they are still small enough to fix. In a contracting squadron this is an additional duty carried alongside a full contracting workload.
Owns their own readiness. Appointments, currencies, family care arrangements, and personal affairs belong to the member. A UDM tracks, reminds, and clears obstacles, and cannot substitute for a member who does not engage.
Medical, dental, finance, legal, security, the chaplain, and logistics readiness each own a piece of whether a member is deployable. A UDM tracks the status of those pieces without owning the content of any of them. Knowing which office to call is most of the skill.
02Execution day workcenters
When a deployment actually executes, the installation stands up a set of workcenters. These are the stations a member physically moves through, and each one checks something different. Knowing what happens at each stop is how a UDM prepares people for a day that otherwise feels like being processed by strangers.
The installation's command node for the operation. Tracks the overall timeline, resolves problems that cross unit lines, and reports status upward.
The squadron's own cell during execution. This is where a UDM usually lives on a deployment day, feeding status to the installation and chasing down the squadron's own loose ends.
Where people get processed. Identity and records verification, remaining briefings, final eligibility checks, and manifesting. For a contracting squadron this is the station that matters most.
Where unit equipment is received, inspected, and prepared for movement. Contracting squadrons deploy people rather than equipment packages, so this station is usually somebody else's concern.
The last stop. Baggage, weigh in, show times, and the aircraft. Once a member is here, anything unresolved is a much bigger problem than it was a week earlier.
A member who arrives at the personnel processing station missing a currency, a document, or a signature does not usually get waved through. They get pulled aside, and somebody spends the next several hours fixing on the day what could have been fixed in a ten minute conversation two months earlier. The value a UDM adds sits almost entirely in those two months, not on execution day.
03Where the rules live
Deployment guidance stacks in layers, and the layer that answers a given question is usually the most local one.
The service level
Air Force instructions cover deployment planning and execution, personnel readiness, and the training programs that feed both. The job qualification standard for unit deployment managers points at a stack of them, including Air Force Instruction 10-403 on deployment planning and execution, which is the closest thing to a parent document for this work. These are worth knowing exist. Reading them cover to cover is a poor use of a first month.
The supplement
Major commands and wings publish supplements that tighten or localize the service level rule. When published guidance and local practice disagree, a supplement is often the reason, and it is a fair question to put to the readiness cell.
The installation deployment plan
The local plan is where the answers a UDM actually needs tend to live: how this installation runs its deployment process, what the local standard looks like, and who does what during execution. Getting a current copy from the Installation Deployment Readiness Cell (IDRC) early is one of the higher value things a new UDM can do, because it converts a lot of guesswork into reading.
When guidance is wrong
Air Force Form 847 is the mechanism for recommending a change to a publication. It comes up rarely, and it is worth knowing about for the case where a published procedure genuinely does not work at the installation level.
Deployment guidance changes often, and force generation guidance changes faster than most. Anything read here, or anywhere else that is not the current publication and the current installation deployment plan, is orientation rather than authority. Confirm specifics with the IDRC before acting on them.
04Types of orders
Military orders have names that sound interchangeable and are not. A UDM rarely reads these documents directly, since what reaches a squadron is usually the effect of an order passed down through the readiness cell and the Functional Area Manager. Recognizing the names still matters, because it tells a UDM how firm a thing is and how much time is left.
Something may be coming. Start thinking about it.
The earliest formal heads up. Nothing is committed and details will change. For a UDM this is the moment to look at the readiness picture with fresh eyes rather than to alarm the squadron.
Be ready to move within a set window.
This one has teeth. It puts named forces on a readiness posture with a clock attached. Currencies that were merely expiring become urgent, and gaps that could be worked slowly cannot be.
These forces are moving.
Directs the actual movement of specified forces to a location. By the time this reaches a squadron, the question has shifted from whether someone goes to whether everything is in place for the person who is going.
Begin the operation.
Directs execution of an operation, typically carrying the authority and timing behind it. Deployment and execute orders often travel close together, which is why the two names get used loosely in conversation.
Here is the detailed plan.
The full order for an operation: mission, tasks, coordinating instructions, and the supporting detail. Large, mostly aimed at planners and operators rather than at unit deployment managers, though the requirements that flow down to a squadron often originate in one.
Part of the previous order just changed.
A change to an order already issued, sent instead of rewriting the whole thing. Practically, this is the mechanism by which dates slip, numbers change, and requirements get added. A tasking that looked settled last week can move because of one of these.
Warning order means something may happen. Prepare to deploy order means get ready now. Deployment and execute orders mean it is happening. Operation orders carry the detail, and fragmentary orders change what was already sent.
05Working with the IDRC
The Installation Deployment Readiness Cell is accountable for getting members out the door, which puts them in the driver's seat and makes a UDM their reach into the squadron. That relationship works best when the traffic runs both directions early and often. Being new is a reason to call them more, not less.
- An accurate picture of who is in the squadron and what condition each person is in.
- Early warning when something is drifting, while it is still a scheduling problem rather than a shortfall.
- The squadron's questions consolidated into one voice instead of ten people calling separately.
- Context the readiness cell does not have: who is about to go on leave, who is mid permanent change of station, which member is already carrying three other additional duties.
- The installation deployment plan and the local standard for what ready means here.
- The tasking flow coming down from above and the timeline attached to it.
- The execution day schedule and the workcenters that run it.
- Training and guidance for the unit deployment managers across the installation, including this one.