There is no single office. Requirements flow from a mix of warfighter demand, strategic force design, and capability development sponsors—ultimately coordinated through Air Force Requirements Oversight Council (AFROC) and budgeted via Air Staff (AF/A5/8).
Formal Requirements Process
AFROC (Air Force Requirements Oversight Council)
Role: Final approval authority for validated requirements documents (ICDs, CDDs, CPDs).
Notes: Chaired by AF/A5. If your tech makes it here, it's real.r
AF/A5R – Requirements Directorate
Role: Day-to-day sponsor for requirements process. Helps MAJCOMs and CFLs write/validate documents.
Notes: Your capability's path to program of record status goes through here.​
AF/A8 – Strategic Plans & Programs
Role: Controls integration of requirements into the POM/budget.
Notes: This is where validated need meets dollars. Connect here to make sure you're resourced.
Upstream – Concept & Capability Drivers
These actors influence the "what" and "why" before a formal requirement is written:
Air Combat Command (ACC)
Role: Lead Core Function Lead (CFL) for most conventional Air Force missions.
Defines warfighter capability needs for C2, ISR, fighters, bombers, EW, counter-UAS, etc.
Notes: If you're building anything for kinetic, autonomy, or comms: start here. They own the "demand signal."
Air Force Futures (AF/A5/7)
Role: Leads strategic force design. Shapes long-term concepts like JADC2, ABMS, and collaborative combat aircraft (CCA).
Notes: Think of them as the future force architects. Engage early to shape the sandbox.
Air Force Research Lab (AFRL)
Role: Does the S&T and prototyping work that seeds requirements. Especially influential in autonomy, AI, ISR, and advanced munitions.
Notes: Get AFRL to love you → ACC writes a requirement → PEO funds it. Classic path.
Major Commands (MAJCOMs)
Role: ACC is dominant, but also:
- AFSOC: for SOF needs
- AMC: for logistics, mobility
- AFGSC: for nukes
- PACAF/USAFE: for theater-specific operational gaps
Notes: Each MAJCOM can push a Mission Need Statement or JUON, especially for theater-specific gaps.
Downstream – Acquisition & Transition
These actors turn requirements into funded programs and fielded capabilities:
Program Executive Offices (PEOs)
Role: Key ones for USVs/UAVs/Autonomy:
- PEO Fighter/Bomber
- PEO ISR & SOF
- PEO Digital
- PEO C3I & Networks
- PEO Weapons
Notes: They don't write requirements, but own the money to build and field. Essential for OTAs, SBIR Phase III, and TRL acceleration.
AFWERX / RCO / DIU
Role: Bridge innovation to transition. Fund experiments, prototypes, and rapid fielding.
Notes: Good wedge for non-traditional tech. But still need MAJCOM or CFL pull to scale.
Operational Test & Evaluation (AFOTEC)
Role: Validates that a system meets its requirement in the real world.
Notes: A poorly scoped requirement can get killed here. Get testability right early.
BD & GTM Implications
Start with the warfighter
ACC (or AFSOC/AMC/etc.) must want your tech before a requirement will exist.
Shape with AFRL + A5
If it aligns to a future concept (JADC2, ABMS, CCA), you're more likely to stick.
Resource through A8
Requirement ≠funding. A8 turns validated needs into real dollars.
Bridge via AFWERX, RCO, or DIU
These give you the initial runway. But they won't carry you into the POM alone.
Air Force Requirements-101