Module 05

Out the Door and Back Home

Unit Deployment Manager

Between a name being committed to a tasking and that person stepping onto an aircraft sits a list of requirements owned by a dozen different offices. The back end has its own list, and it gets forgotten more often. Neither list belongs to a Unit Deployment Manager, and keeping track of both does.

← Back to the UDM hub

01Who owns what

Medical owns medical. Finance owns pay. Legal owns wills and powers of attorney. Security owns clearances. Personnel owns records. Each of those offices is competent at its own piece and has no visibility into the others.

Nobody in that list owns the list itself. That is the UDM's part of this phase: not performing the requirements, but knowing where each one stands for each member, and noticing when one is drifting while there is still room to fix it.

The shape of the work

Most of what follows is somebody else's process that a UDM has to be able to see into. The useful skill is knowing which office to call, what a normal timeline looks like, and which requirements have long enough lead times that they have to be started immediately rather than worked in order.

02Medical clearance

Medical is the requirement most likely to stop a member, and the one where a UDM has the clearest assigned role.

Individual medical readiness

Individual medical readiness is the baseline: immunizations, examinations, dental classification, and the rest, maintained continuously rather than assembled when a tasking arrives. A squadron that lets this drift discovers the cost at the worst moment, because medical requirements have appointment queues in front of them and cannot be compressed by urgency alone.

The system a UDM actually uses

The Aeromedical Services Information Management System, usually called ASIMS, is the system of record for deployment medical clearance and individual medical readiness. Air Force health guidance puts monitoring deployer status through its deployment medical clearance function on the unit deployment manager, including assigning individual deployment taskings in the system, tracking compliance, and confirming that clearance requirements are complete before a member departs. Real time readiness reporting is available there, which makes it the practical place to watch status rather than chasing individuals.

The health assessment cycle

Three assessments bracket a deployment. Knowing all three up front is useful, because the last one lands long after most people have stopped thinking about the deployment at all.

BEFORE
Pre-deployment assessment

The member records health information and concerns before leaving. A certified provider reviews it and makes the deployability determination, with public health initiating the clearance process.

Within 120 days prior
RETURN
Post-deployment assessment

Screens health status and concerns at redeployment and documents what happened during the deployment. A trained provider conducts the encounter and reviews it for referrals.

30 days before or after return
LATER
Post-deployment reassessment

A second look several months out, conducted person to person, which can be by phone or video. Section 06 covers why this one matters and why it gets missed.

90 to 180 days after return
The line worth holding

Medical owns the content, the examinations, and the deployability determination. A UDM owns knowing where every member stands in the process and when something is about to lapse. Those are different jobs, and confusing them either wastes a UDM's time or puts them in the middle of a decision that is not theirs.

Waivers exist for some conditions that would otherwise block a deployment, and they route through medical authorities rather than through the squadron. As with everything on a timeline, a waiver question raised early has options that the same question raised late does not.

03Travel and clearances

The routine parts

A government travel card in good standing and a functioning Defense Travel System profile are ordinary requirements that become urgent when they are missing. Both are worth confirming early rather than assuming, particularly for a member who has not traveled recently.

Country requirements

The Department of Defense Foreign Clearance Guide states what each country requires of arriving personnel: entry documents, immunizations, visas, passport type, and country specific restrictions. It is the authoritative reference for that question, and requirements differ enough between destinations that assuming based on a previous deployment is a poor bet.

Clearance requests

The Aircraft and Personnel Automated Clearance System, usually called APACS, is where theater and country clearance requests are submitted and tracked. A member traveling to or through a foreign location generally needs an approved clearance before movement, and approval is somebody else's decision on somebody else's timeline.

This is the long lead item

Clearances, visas, and passport actions run on external timelines measured in weeks, and occasionally longer. They do not accelerate because a ready to load date is close.

Which means these get started in the first days after a name is committed, not in the order they appear on a checklist. A member who is otherwise perfectly prepared and lacks an approved clearance is not going anywhere.

04Outprocessing

The final stretch runs through a set of tools and folders. These are named here at the level of what they do, since screens and procedures change and the readiness cell holds the current version of both.

  • AFFORGEN Connect. The force generation reporting environment, hosted on Envision, along with the force generation reporting instructions that explain what units are expected to report and when.
  • The Commander's Toolkit. Commonly abbreviated CCTK. The collection point for deployment preparation resources at unit level.
  • The electronic Air Force deployment folder. Where a deploying member's documents are uploaded and held, replacing the paper folder that used to travel with them.
  • The electronic deployment readiness checklist. Where the requirements for a specific member and tasking get determined and tracked to completion.
  • Personnel action requests. The mechanism for personnel actions tied to a deployment, which the readiness cell may route through a UDM.
  • Tasking maintenance worksheets. Used to correct or update information on a tasking line after it has been issued.
Deliberately shallow

No walkthrough of any of these appears here. Access, current procedure, and local business rules come from the Installation Deployment Readiness Cell (IDRC), and a written walkthrough would be stale before it was useful. What is worth carrying is the names, so that a conversation with the readiness cell starts from recognition rather than from scratch.

05Security housekeeping

Security shows up in this job in a few small, unglamorous ways that are much easier handled in advance.

  • Clearance and classified network access. A fair amount of tasking detail lives on the classified side, so having a current clearance and working access at appointment beats sorting it out during a tasking. Module 04 makes the same point from the tasking direction.
  • Knowing what should not be discussed. Operations have critical information lists identifying the details that would be useful to somebody watching. Dates, numbers, locations, and unit movements are the usual categories. A UDM handles all of them routinely, which makes it worth knowing where the line sits.
  • Handling classified material correctly. Marking, storing, transmitting, and destroying classified information each have rules. The security education courses named on the hub cover marking and derivative classification, and the unit security manager handles anything beyond that.

This is not a classification course, and a UDM does not need to become a security specialist. Knowing which questions belong to the security manager is sufficient.

06Coming home

Deployment support has a back end, and it gets less attention than the front end because nothing is on a countdown. A member landing at home station is not finished, and neither is the UDM.

Reintegration

Returning members have in-processing actions, briefings, and appointments waiting. Handled well, that is a short organized sequence. Handled by nobody in particular, it becomes a scattered set of things a member chases down between catching up on leave and returning to a full workload, which is how items get missed entirely.

Treating reintegration as a planned sequence rather than as paperwork that will sort itself out is most of the difference, and it costs a UDM very little to have that plan ready before the member lands.

The health assessments on the back end

The post-deployment assessment happens close to return, within a window that spans the last thirty days in theater and the first thirty days home. The reassessment comes considerably later, between ninety and one hundred eighty days after return, and involves an actual conversation with a provider rather than a form alone.

That gap is deliberate. Some things do not surface in the first weeks back, when a member is focused on catching up. The reassessment exists to catch what the first look could not, which is exactly why it is the one most likely to slip when nobody is tracking it. Putting it on a calendar the day a member returns is a small piece of work that matters more than its size suggests.

Leave, downtime, and getting square

Post-deployment leave and downtime policies exist and vary. A UDM who knows the current version can answer a returning member's questions instead of adding to the list of things they have to run down themselves.

Accounting for what went out

Weapons, classified material, and issued equipment all have to come back and be accounted for. Government travel card reconciliation and voucher settlement belong to the same category of things that are simple immediately and complicated six months later.

Worth capturing while it is fresh

A returning member knows things nobody at home station does: what the location actually needed, what the preparation missed, what would have helped. A short conversation shortly after return is the cheapest source of improvement a UDM has, and the information decays quickly.

07Working with the IDRC

This phase is the installation's process end to end. The readiness cell runs it, and a UDM works inside it on behalf of the squadron's people.

What you bring
  • Status on every requirement for every committed member, current enough to be worth reporting without checking first.
  • Long lead items started immediately rather than in checklist order, particularly clearances and anything with an appointment queue.
  • Early warning when a requirement is not going to make the date, while alternatives still exist.
  • The member's own situation: leave already approved, family circumstances, anything that changes what a normal timeline looks like for this person.
What the IDRC owns
  • The outprocessing schedule and the workcenters that run it on execution day.
  • Access to the deployment tools and folders, and the current procedure inside each.
  • Coordination with medical, personnel, travel, and security at installation level.
  • The local standard for what complete looks like before a member is released to travel.