Readiness, Reporting, and Training That Counts
Most of what a Unit Deployment Manager does is invisible until a tasking lands, and then all of it shows at once. This module covers the tracking that fills those quiet months, why a skill level is a bigger claim than it looks, and what the readiness reporting on top of it is actually for.
01What a UDM tracks
The core artifact is a current, honest picture of every deployable member in the squadron. Not a headcount. A picture detailed enough that when a tasking arrives asking for a specific skill level with specific currencies, the answer takes minutes rather than a week of phone calls.
Six things make up that picture.
Medical and dental status
Immunizations, periodic health assessments, dental classification, profiles, and anything with an expiration date attached. A member can be perfect on paper everywhere else and still be stopped by a dental class or a lapsed assessment.
Medical owns the content and the decisions. A UDM owns knowing where each member stands and when something is about to lapse, because medical is not going to call the squadron about it.
Deployment availability codes
These flag a member as unavailable to deploy and record the reason, whether medical, legal, administrative, or something else. Air Force Personnel Center owns the program, and the entries are managed on the personnel side rather than by the squadron.
What a UDM owns is accuracy. A code that should have come off months ago quietly shrinks the pool the squadron can source from, and a code that should be on and is not sets up a member to be tasked for something they cannot do. Reviewing them on a rhythm, rather than when a tasking forces it, is the whole discipline.
Skill level by member
Who holds a three level, a five level, a seven level, and where each person sits in upgrade training. This is the field that gets matched against a tasking most directly, since manpower requirements are written in skill levels rather than in names. Section 02 covers what that match actually claims.
Rank and grade
Requirements are often written for a grade as well as a skill level, and the two do not always travel together. A squadron can hold the right skill levels and still be unable to fill a slot that calls for a particular grade, which is the kind of gap worth finding early rather than during sourcing.
Experience
Previous deployments, time in the career field, and how many force generation cycles a member has been through. This is not just useful context for the commander when deciding who to send.
It also has a direct mechanical effect: readiness training requirements are tiered by experience, and a member with fewer than two force generation cycles completed carries a heavier training load than one with more. Tracking experience is what tells a UDM which training tier a member falls into.
Training currencies
Readiness training, weapons qualification, chemical defense, and the rest of the recurring requirements. This is the field a UDM shares most closely with the unit training manager, which section 03 covers.
02Skill levels are a promise
The job qualification standard for unit deployment managers grades every task on a GO or NO GO basis. GO means the person can perform the task without assistance, using the applicable guidance. There is no partial credit and no category for performing it with somebody looking over a shoulder.
That definition is not unique to deployment managers. It is the standard running underneath skill levels across the Air Force. A five level is expected to perform five level tasks unassisted. That is what the skill level asserts.
Follow the chain
A mission capability statement tells a commander what a capability can do. The manpower element underneath it lists the positions that deliver that capability, written in specialty codes, grades, and skill levels. The squadron fills those positions with names.
So the chain runs: a commander is promised a capability, the capability is defined by positions, the positions are defined by skill levels, and the skill levels are certified by supervisors inside a squadron. Every link is somebody's signature.
What happens when the certification is not real
When a member is signed off on tasks they cannot actually perform unassisted, nothing improves. The squadron's readiness looks better on paper while the underlying capability stays exactly where it was, and the discovery gets moved to a much worse place to make it.
At home station, a member who hits something beyond their training has a shop full of people to ask. A deployed contracting presence is frequently one or two people supporting a location that needs things bought immediately. There is no one down the hall. The member absorbs a problem they were never prepared for, and the capability the commander was promised is not there.
This is the argument for treating an upgrade signature as a real assessment rather than a scheduling milestone, and for a UDM to raise it when the training record and the demonstrated ability do not match. That conversation is easier during a preparation phase than during a tasking, and much easier at home than by email to somebody downrange.
Rather than asking whether a member is signed off, ask whether they could run the task alone tomorrow with the guidance in front of them and nobody to check their work. That is the same question the GO standard asks, and it produces a different answer often enough to be worth asking.
03Lock step with the unit training manager
The unit training manager and the unit deployment manager are tracking overlapping data for different reasons, and a squadron gets much better readiness reporting when the two work as a pair rather than maintaining separate versions of the truth.
The training manager watches
- Upgrade training progress and career development course completion.
- Skill level awards and the training records behind them.
- Ancillary and recurring training currencies.
- Whether the squadron's training program is producing qualified people on schedule.
The deployment manager watches
- Whether each member can actually be sent somewhere right now.
- Medical, dental, availability coding, and deployment specific requirements.
- How the squadron's people map against the capabilities it is postured to provide.
- Readiness training tied to deployment rather than to the career field.
The overlap is the interesting part. A member's skill level lives in the training manager's world and determines what the deployment manager can offer against a tasking. A currency that lapses shows up in both. When the two are working from different spreadsheets, the commander gets two readiness answers and has to guess which one is right.
A standing rhythm between the two, even an informal monthly look at the same roster, removes most of that. It also means a member who is drifting gets noticed twice rather than falling between two people who each assumed the other was watching.
Both roles exist so a commander can answer a question honestly: can this squadron do what it is postured to do, and with whom. The commander signs that assessment. The training manager and the deployment manager between them supply almost everything behind it.
04Ready Airman Training
Ready Airman Training is the Air Force's baseline readiness training for anyone who might deploy or support a contingency. It covers cross functional skills rather than career field skills, on the theory that a contracting specialist at a bare base needs some of the same things as everybody else there.
How it is organized
- Ready training areas. Twelve areas covering the knowledge and skills needed to survive and operate across the range of military operations, at home station or deployed. Delivery leans toward in person instruction from qualified instructors, supported by computer based training and hands on practice.
- Readiness categories. Requirements are tiered. A foundational tier applies to institutional and employed in place members. A second tier applies to members with fewer than two force generation cycles behind them and carries more frequent training. A third tier applies to more experienced members and carries less. This is the mechanical reason tracking experience matters.
- Timing. Training events are spread across the phases of the force generation cycle rather than stacked into one push, and currencies reset at the end of the available phase.
- Advanced Ready Training. Additional preparation for members facing higher threat environments, with prerequisites that have to be completed first. Usually scheduled during the preparation or certification phases, delivered in residence or by mobile training teams.
Ready Airman Training guidance puts documentation of training completion on the unit deployment manager or a designated representative, recorded in the approved learning management system. Scheduling coordination and verifying that members meet the prerequisites for advanced training sit there too. Of everything in this module, this is the piece most clearly owned rather than tracked.
Exemptions and waivers
Members who maintain equivalent proficiency through their actual job duties can be exempted from a matching requirement, though that runs through career field managers rather than through a squadron. Commanders have some latitude to waive requirements down to the foundational tier, while still meeting theater specific and department level requirements. Waivers for advanced training route higher and need documented evidence behind them.
Worth knowing these exist. Worth confirming the current process with the readiness cell before assuming any of them apply, since this program has already been restructured once.
Where the training lives
Members complete assigned training through the Air Force learning management system, with the joint training network carrying some department level requirements. A separate readiness information system provides supplementary tracking and is where things like weapons and chemical defense course scheduling tend to be coordinated. Access and local procedure for all of it comes through the readiness cell.
05Reporting readiness
Everything tracked so far eventually becomes a report. Readiness reporting is the most consequential thing a UDM touches, because it is what planners read when they decide where a real requirement gets sourced from.
DCAPES
The Deliberate and Crisis Action Planning and Execution Segments, usually just called DCAPES, is where unit type code readiness gets reported. A planner deciding where a contracting requirement should land is reading what units said about themselves. A squadron that overstates gets tasked for something it cannot deliver. A squadron that understates watches the requirement go elsewhere and gets asked about it later.
Where the data comes from
Most of what DCAPES holds about a squadron's people arrives automatically from the Military Personnel Data System. A UDM does not type it and cannot correct it directly. When something is wrong, a skill level that never posted or an assignment that has not caught up, the fix runs through the Commander's Support Staff and squadron leadership rather than through the deployment manager.
Knowing that in advance saves time hunting for an edit field that does not exist. It also means the relationship with the Commander's Support Staff matters more than it looks like it should, since they are the ones who can actually move a record.
What a UDM supplies
On top of the automatic feed, the system asks readiness specific questions that a personnel record cannot answer on its own. That is the part a UDM fills in. The Installation Deployment Readiness Cell (IDRC) may want particular language each month, and using what they ask for is fine. The numbers underneath that language are a different matter.
Red is red
A squadron that cannot fill what it is postured for reports that it cannot. Softening a rating to avoid an uncomfortable conversation does not make the capability appear. It moves the discovery downstream, toward whoever gets sourced against a capability that was never there.
Reporting an accurate red is the job working correctly. The rating exists to carry information to a planner, and a rating that has been managed for appearances carries none.
What a unit actually reports is protected, so no page on the open internet can walk through it line by line, and one that tried would be wrong as well as inappropriate. Reporting mechanics, current business rules, and access come from the IDRC. What this module can offer is why accuracy matters, which does not change when the screens do.
Mission essential task lists
A mission essential task list is the set of tasks a unit must be able to perform to accomplish its mission. It answers the question sitting underneath all readiness reporting, which is whether a unit is ready to do specific things rather than ready in the abstract. Reporting without that reference point is just numbers.
The readiness reporting system and the commander's assessment
The defense readiness reporting system is where a unit's readiness assessment lives. It captures resource readiness, meaning whether the unit has the people, equipment, and training it needs, and capability readiness, meaning whether it can actually perform its essential tasks. Commanders add summary statements that explain the numbers, since a rating without context tells a reader very little.
A UDM does not own this assessment. A UDM supplies a large share of what goes into it, which amounts to the same responsibility from a different direction.
06Living in the yellow
Contracting runs on cross trainees. People arrive from other career fields at every rank, which means a squadron can hold a technical sergeant working a three level, and that is an ordinary situation rather than a broken one.
The pressure that creates is real. Upgrade numbers look thin, readiness reporting reflects it, and the natural instinct is to move people through upgrade training as fast as the paperwork allows.
The arithmetic does not reward rushing
An upgrade signed before someone can do the work unassisted buys a better number and leaves the same capability sitting underneath it. The squadron then reports green while fielding yellow, which is worse than reporting yellow, because now nobody outside the squadron knows.
The timeline works against it too. By the time a cross trainee is genuinely competent, they are often close to a permanent change of station, and the replacement arrives undertrained. The cycle does not end. A squadron that treats every yellow as an emergency is spending itself against something structural.
The more useful posture is to get comfortable in the yellow. Report it accurately, explain it in the narrative where the narrative exists, and put the effort into making people genuinely capable rather than into making the chart look better. Speed of upgrade matters much less than whether the person can do the job when there is nobody around to ask.
A commander who understands why the squadron sits where it sits can plan around it, ask for help, or push back on a tasking with something concrete to point at. A commander who finds out during execution has none of those options.
07Working with the IDRC
Readiness is the area where a UDM has the most independent work and still cannot verify their own answers. The squadron holds the facts. The installation holds the standard those facts get measured against.
- A current roster with medical status, availability coding, skill levels, grades, and experience that reflects reality rather than the last time somebody updated it.
- Documented readiness training completions, recorded as they happen rather than reconstructed later.
- Early flags when a member is drifting toward non deployable, while it is still a scheduling problem.
- An honest account of gaps between what the squadron reports and what it could actually field tomorrow, including the ones that are structural rather than fixable this quarter.
- The reporting mechanics, the current business rules, and system access.
- The local standard for what counts as ready at this installation.
- Verification that required readiness training actually happened.
- Interpretation when a member's situation does not fit any clean category, which happens more often than the categories suggest.