←Back to 3F1X1 Services — overview, pay, training, civilian translation, reviews
3F1X1E1-E3
Services
E-1 to E-3 (Junior Enlisted) · Air Force
HEADS UP
Tech school at Maxwell-Gunter Annex (Ft. Skill) is short — roughly 6 weeks — and deceptively academic. You will spend your first assignment learning that MPES is not intuitive, that manpower documents are load-bearing legal instruments, and that everyone in your unit thinks they deserve more people than the Air Force allocated. You are the person who tells them why that allocation is what it is. Start building your data logic now.
The Honest MOS Read
You enlisted into 3F1X1 Manpower, a career field that most Airmen could not find on a map and that shapes every unit in the Air Force. The Manpower Analyst is responsible for validating and maintaining Unit Manpower Documents — the official, AF-HQ-approved records of how many authorizations a unit has, in what grades, in what AFSCs, and against what requirements. The UMD is not a suggestion. It is the legal basis for billets, promotions, and manpower programming. If a unit's UMD is wrong, everything downstream is wrong: the unit can't fill positions, can't promote people into the right grade, and can't argue for more people at the next Program Objective Memorandum cycle.
At E-1 through E-3, your job is to absorb the job. You are learning the Manpower Programming and Execution System — MPES — which is the Air Force's authoritative system of record for manpower data. You will learn to navigate MPES to pull UMDs, check authorization counts, identify mismatches between what is on the document and what is on the ground, and flag discrepancies to your NCOs and the unit POCs you support. You will learn the difference between an authorization (what the Air Force says a unit is allowed to have) and an assignment (what AFPC actually fills). That gap between authorizations and assignments is the engine of most of the manpower frustration you will encounter.
The formal references you are being introduced to are AFPD 38-2 (Manpower Policy) and AFI 38-201 (Manpower and Organization — Management of Air Force Manpower), plus the MPES User's Guide that lives on the AF Manpower Analysis Agency's portal. You will also become familiar with how funded versus unfunded authorizations work, what a man-year is versus a position, and how the Air Force Manpower Standard program is supposed to relate to the UMDs your unit maintains.
The reality check at this tier: you are going to spend time doing data entry, running queries you don't fully understand yet, and supporting senior analysts on studies you aren't leading. That is the correct order of operations. The Airmen who flame out early in this career field are the ones who dismiss the administrative rigor as busywork. It is not busywork. It is audit-defensible record-keeping that commanders rely on when they go to the MAJCOM to argue for resources. Learn it cold now, before you are the one briefing it.
Career Arc
BMT at Lackland (~8.5 weeks). Tech school at Maxwell-Gunter Annex — approximately 6 weeks of classroom instruction on MPES, UMD structure, manpower methodology, and AF organizational constructs. First-duty assignment as a junior analyst supporting a base Manpower and Organization (M&O) office, typically under an NCO or senior Airman. First tasks: UMD maintenance actions, MPES queries, status-of-personnel reconciliations, and supporting senior analyst studies. Airman of the Quarter/Year board preparation and community involvement. Building the supervisor relationship that generates the EPR bullets for the SSgt board.
Common Screwups
Making UMD changes in MPES without getting the change request approved through the proper chain — even a well-intentioned correction can trigger audit findings and require manual rollback. Treating the UMD validation as a one-time action instead of a continuous reconciliation cycle — mismatches compound over months and become a unit readiness problem. Going directly to a unit POC to 'fix' a discrepancy without routing it through your senior NCO — this breaks the accountability chain and exposes you to blame when the fix creates a downstream problem. Skipping the MPES change log — every significant query or data action should be documented; when an auditor comes back six months later, you need the history. Letting upgrade training slip past milestones — the 3F1X1 CDCs and qualification tasks are supervisor-graded; a missed milestone follows you into the EPR.
A Day in the Life
0530 — PT with the unit or individual session; 3F1X1 offices are typically small and PT accountability is close. 0700 — arrive at the M&O office, check email for MAJCOM suspenses or unit POC inquiries that came in overnight. 0730 — morning standup with the NCOIC; get task assignments for the day, clarify any open change requests. 0800 — MPES reconciliation work: pull current UMD data for assigned units, compare against AFPC assignment roster, document deltas. 0930 — work on assigned change request packages: draft justification memos, pull required data extracts, format per template. 1100 — respond to unit POC questions; most are 'why does my UMD say X' questions that require pulling the history in MPES and explaining it plainly. 1130 — lunch. 1230 — continue change request work or transition to study support tasks if assigned to an ongoing study. 1400 — upgrade training tasks: read CDC material, complete qualification task checklist items with supervisor sign-off. 1530 — weekly suspense check: confirm nothing is due tomorrow that hasn't been started. 1600 — wrap up MPES documentation for the day's actions. 1630 — out, unless a suspense is tight.
Weekly Cadence
Monday is the reset: check the MAJCOM manpower portal for new suspenses, confirm the week's reconciliation cycle status, and update the task tracker. The first half of the week is data work — reconciliations, change request drafts, study support queries. Mid-week is typically when unit POCs surface their questions, so expect a surge of 'can you check my UMD' emails Wednesday and Thursday. Friday is documentation and close-out: complete the week's MPES action log, file change request packages, and identify anything that needs to carry into next week with a note to the NCOIC.
The rhythm for junior analysts is heavily shaped by the MAJCOM suspense calendar — when the MAJCOM publishes a manpower action window, the office shifts into execution mode and individual study work pauses. Learn the suspense calendar early so you are not caught mid-study when an action window opens. The small M&O office means there is no slack in the bench; everyone's task list is real.
Key Skills — How to Drill Each
MPES navigation and data accuracy: MPES is the AF system of record for manpower and you are directly accountable for data quality. Drill it by running reconciliation queries weekly — compare MPES authorizations against AFPC assignment data and resolve every delta with a paper trail. UMD interpretation: a UMD entry has grade, AFSC, position number, PASCODE, and several coded fields that carry legal weight. Drill it by reading every UMD field definition in the MPES User's Guide and then pulling a real UMD and annotating each field. Manpower study methodology: studies use AF Manpower Standards or activity-based costing to determine how many people a function actually requires. Drill it by reviewing a completed study in your office's archive and tracing each step from workload data to authorization recommendation. Briefing and stakeholder communication: you will brief unit commanders and first sergeants who do not speak MPES. Drill it by writing a one-page summary of every study or major UMD action and having your supervisor red-pen it. Technical writing for official records: every change action, study finding, and discrepancy resolution must be written in a way that withstands a DAF IG audit. Drill it by studying the memo and staff summary sheet formats in DAFI 33-322.
Manuals & References — What Chapters Matter
AFPD 38-2 (Manpower Policy) — the capstone policy that establishes why manpower documents are authoritative and how manpower standards are derived; read the whole thing in your first month. AFI 38-201 (Management of Air Force Manpower) — the primary implementing instruction; chapter 2 covers UMD management and chapter 4 covers manpower studies; these two chapters are your daily operating law. MPES User's Guide (AF Manpower Analysis Agency portal) — the procedural reference for every system action; bookmark it and read the change log when updates post. DAFI 38-101 (Air Force Organization) — explains the organizational constructs (wings, groups, squadrons, flights) that UMDs map to; understanding the org structure prevents category errors in your studies. DAFI 36-2618 (The Enlisted Force Structure) — manpower authorizations are tied to grade and AFSC; understanding how the AF manages grades informs why UMD grade distributions matter.
Standards — How to Hit Each
UMD reconciliation completed on the unit's documented cycle (typically monthly or quarterly) with all deltas documented and actioned — the standard is zero unresolved discrepancies at each cycle close. MPES data actions completed within the suspense window provided by the MAJCOM manpower office — late actions delay unit readiness reporting. Study products (worksheets, briefings, final reports) formatted to the AFMAA study template and reviewed by the NCOIC before routing — non-conforming products get returned and eat your suspense. Change requests submitted with all required documentation (justification memo, UMD extract, affected position list) — incomplete packages are rejected by the MAJCOM and restage the clock. EPR bullets for supported units reviewed for accuracy before the rater submits — 3F1X1 analysts sometimes ghost-write or advise on manpower-specific EPR content; a factual error traces back to you.
Technical Mistakes — Concrete Consequences
Editing a position in MPES with the wrong PASCODE — the PASCODE ties the position to the unit's funding line; a wrong PASCODE moves a billet to the wrong unit in the data and triggers a cascade of downstream reporting errors that can take weeks to unwind. Confusing an authorization with a requirement — a requirement is what a study says the unit needs; an authorization is what HQ approved; a position may be authorized but unfunded, which means it shows on the UMD but AFPC will not fill it; conflating these when briefing a commander creates false expectations and trust erosion. Running a manpower study off outdated workload data — workload is the denominator in every standard-based calculation; stale data produces a wrong answer that will be contested by the unit and may be overturned at MAJCOM review, wasting months of work. Submitting a UMD change request without verifying the receiving grade's promotion cycle impact — some UMD grade changes affect whether incumbents can be promoted in place; an unconsidered grade change can strand an Airman below their eligible promotion grade for a full WAPS cycle. Using unofficial MPES exports for briefing products — MPES data exports must be marked as of a specific pull date; unofficial or cached data in a briefing can contradict the system of record in the room if someone pulls a live query during the brief.
Career Decisions at This Rank
Upgrade training completion and CDC mastery — this is not a decision so much as a forcing function: complete your 5-level CDCs and qualification tasks on schedule. The analysts who are slow on upgrade training are the ones whose EPRs read flat at the SSgt board. Cert or study track early — some 3F1X1 analysts pursue project management or data analysis credentials (PMP, CompTIA Data+) on their own time; this is not required but it signals cross-functional depth that matters at the mid-career gate. Assignment preferences at first RNLTD — your first assignment largely picks you based on needs, but start building your case for the second assignment early; AFMA, Air Staff, or MAJCOM manpower billets at E-4 are competitive and go to analysts whose EPRs are clearly above the line.
How the Seat Varies by Unit Type
Large base M&O office (wing-level): you support dozens of units, the workload is high-volume, and you develop breadth fast but may not go deep on any single unit's study work for months. MAJCOM manpower division: faster operational tempo, more policy exposure, and direct visibility to major programming decisions — competitive to get into as a junior enlisted but transformative if you land it. AETC or training base: manpower studies for training units have unique workload metrics (student throughput, instructor ratios) that are methodologically different from operational units; good for analysts who like technical depth. Deployed or AEF context: contingency manpower support means validating theater UMDs and assisting commanders who have never seen a UMD in their lives; the pace is high and the political pressure to 'just add people' is constant — hold the methodology.
What Good Looks Like at This Rank
A good junior 3F1X1 is the analyst the unit POCs trust to give them a straight answer. You don't tell them what they want to hear about their manning picture; you tell them what the data says and what options exist within the system. That reputation for accuracy — built by sweating the small data fields that most people gloss over — is the foundation of every good thing that happens to you later in this career.
Good at this tier means your UMDs are clean at every reconciliation cycle, your change requests go through approved the first time, your MPES actions are documented, and your upgrade training milestones are met without your supervisor having to chase you. It also means you are reading the AFIs instead of waiting for someone to tell you what they say. Most junior analysts in this career field have never opened AFI 38-201 voluntarily. The ones who have are identifiable within a year.
The longer-term signal good looks like: you are the junior analyst your senior NCO sends to work directly with a unit's superintendent on a sensitive study, because you have demonstrated that you can give unpleasant news without making it personal and can hold your position when a commander pushes back on a methodology. That is the skill set that makes a good E-4 and a great NCO.
Preview — The Next Rank
At SrA, you are expected to own a portfolio of units without daily supervision on every action. Your NCOIC will assign you a set of units and you are responsible for their UMD health from reconciliation to change request to study support. The jump from AB/Amn/A1C to SrA is a jump from executing tasks to owning outcomes — your UMDs are your UMDs, and when the MAJCOM audits them, your name is in the action log.
ALS is the EPME gate for SSgt. Start thinking about your WAPS position now: SKT score is the only component you fully control in the short term, and the 3F1X1 SKT is drawn from the AFSC CDC material and the core AFIs. Airmen who have read AFI 38-201 cold before they sit the SKT consistently score higher. The SSgt board in this career field is competitive in years when the AF is growing manpower functions and soft in years when it is cutting them — you do not control the macro, but you control your SKT prep and your EPR bullet quality.
FAQ
3F1X1 E1-E3 — Frequently Asked Questions
Q01What does a E1-E3 3F1X1 (Services) actually do?
Complete 3F1X1 initial skills training.
Q02What's the most important thing to know as a E1-E3 3F1X1?
Tech school at Maxwell-Gunter Annex (Ft.
Q03What mistakes get E1-E3 3F1X1 soldiers fired or relieved?
Making UMD changes in MPES without getting the change request approved through the proper chain — even a well-intentioned correction can trigger audit findings and require manual rollback. Treating the UMD validation as a one-time action instead of a continuous reconciliation cycle — mismatches compound over months and become a unit readiness problem.…
Q04What's next after E1-E3 for a 3F1X1 (Services) in the Air Force?
At SrA, you are expected to own a portfolio of units without daily supervision on every action.
Q05What manuals and regulations does a E1-E3 3F1X1 need to know cold?
AFI 38-201 (Determining Manpower Requirements), AFI 38-204 (Programming USAF Manpower), AFMAN 38-208 (Management Engineering Analysis), MPES user documentation
This playbook has no tips yet. Be the first to share what you know.
Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards