Special Forces

You are an 18A — the most junior officer in the Army with a direct-action-capable, twelve-man team running against a geographic combatant command's campaign plan. The ODA runs on the Team Sergeant's experience; your job is to command from the top, plan at the level the Group needs, and not confuse being the commander with being the smartest man in the room.

Most 18A officers come through one of two pipelines: direct commission through Officer Candidate School or ROTC / USMA followed by the Special Forces Assessment and Selection (SFAS) and the SF Officer Course (SFOC) at SWCS, Fort Liberty; or branch-detail where the officer serves an initial KD tour as a conventional officer (11A, 13A, or similar) and then passes SFAS and the SFOC. Either way, after SFAS and SFOC you are the Detachment Commander — the 18A — on a 12-man ODA with a 180A warrant as your assistant. The Team Sergeant (18Z) is the senior NCO who runs team operations; your sergeant majors across weapons (18B), engineer (18C), medical (18D), and communications (18E) pairs are the subject-matter depth the team lives on. You plan at the group and company level — translating the company's campaign plan into a team-level OPORD for ISOFAC and for the mission — you command during execution, and you write the NCOERs on the junior enlisted pair in each section through the Team Sergeant. Your week in garrison alternates between team-room work (weapons sustainment, language training, dive or MFF currency, partner-nation coordination), company-level training meetings, ISOFAC planning cycles, and the administrative load that command brings regardless of component. In pre-deployment work-up the pace compresses into 12-18 hour planning days and the cumulative pressure to execute ISOFAC to standard. Deployed, you are the team commander on the ground, the face of the United States to the partner-force commander, and the 18A signature on every mission report that goes to the SOTF and GCC.

• 01Plan and brief an ODA-level OPORD through a full ISOFAC cycle — concept of the operation, scheme of maneuver, fires and JTAC integration, PACE plan, sustainment, C2 architecture — to the standard the SOTF can validate without rewriting.
• 02Translate the GCC campaign plan and the Special Operations Task Force (SOTF) order into a team mission plan your Team Sergeant and specialty sections can execute — METT-TC applied to UW, FID, DA, or SR mission sets per FM 3-18.
• 03Command the ODA during execution — decision-authority on the objective, ROE application, abort criteria, CASEVAC, and EXFIL — without leaning on the Team Sergeant to make the command decision for you.
• 04Run the team's partner-force relationship at the country-team level — embassy country team coordination, security cooperation office synchronization, partner-force commander rapport — the relational foundation FID and UW rest on.
• 05Write and defend NCOERs on the enlisted junior MOS pairs (18B, 18C, 18D, 18E junior soldiers) through the Team Sergeant's recommendations — your NCOER on the team's soldiers is the document the centralized sergeant board reads.
• 06Build a pre-deployment work-up training plan with the Team Sergeant that resources language sustainment, dive / MFF currency, partner-force pre-mission training, JTAC integration, and specialty-section sustainment through the 12-18 months before isolation.

• —FM 3-18 — Special Forces Operations (the operational-level SF doctrine; read it before SFOC and again before every deployment cycle).
• —TC 18-01 — Special Forces Unconventional Warfare (the UW doctrine the entire regiment teaches from; relevant chapters differ by mission set).
• —ADP 3-05 — Army Special Operations (the ARSOF doctrinal anchor; frames the SF, Ranger, PSYOP, Civil Affairs, and SOAR relationships).
• —JP 3-05 — Special Operations (joint doctrine; the GCC and COCOM planners brief from this, and the 18A who can hold the joint conversation is the 18A the SOTF trusts with the harder missions).
• —ADP 5-0 — The Operations Process; ADP 6-0 — Mission Command (the planning-and-command spine the SFOC teaches from).
• —AR 623-3 + DA PAM 623-3 — Evaluation Reporting System; DA PAM 600-3 — Officer Professional Development (the OER side of your career and the career-arc mathematics).

• —SFAS pass and SFOC graduate (SF Officer Course at SWCS, Fort Liberty) — the gate. No SFAS, no team.
• —SFQC-equivalent individual qualification for 18A — the qualification pipeline teaches small-unit tactics, unconventional warfare planning, language, and SERE before the team assignment.
• —ACFT pass at the officer floor — the ODA does not carry a commander who cannot meet the fitness standard the enlisted soldiers are held to.
• —ISOFAC completion to standard for each deployment cycle — the SOTF validates the team's mission plan through isolation; your ISOFAC product is the first OER input for the deployment cycle.
• —O-1 to O-2 is automatic at 18 months commissioned under DOPMA / AR 600-8-29; O-2 to O-3 board at ~4 years commissioned with historically high selection rates for fully-qualified competitive-zone officers — pull the current HRC board release for the specific FY rate.

• —Treating ISOFAC as a product-generation event instead of a command-decision process. The SOTF reads your mission plan as the evidence of whether you understand the operational environment and the team's limitations — a sloppy isolation brief is the first visible read the SOTF has on the 18A.
• —Confusing "commander" with "most competent technician in the room." The Team Sergeant and the specialty sections carry technical depth you will never match. Your job is to command the team, not to out-brief the senior 18B on foreign weapons or the senior 18E on SATCOM. LTs who try lose the formation inside the first field rotation.
• —Bypassing the Team Sergeant to manage enlisted soldiers directly. The chain runs through the 18Z; the 18A who goes direct to enlisted soldiers on operational or disciplinary matters ends the team's functional trust architecture in one conversation.
• —Skipping the country-team coordination early in the pre-deployment cycle. Embassy country-team relationships, security cooperation office alignment, and host-nation legal status take months to build; the 18A who shows up in-country and meets the country team for the first time is the 18A whose FID program runs six weeks behind.
• —Letting language proficiency atrophy. Group alignment — JBLM / Indo-Pacific, Fort Liberty / Africa or SOUTHCOM, Fort Campbell / CENTCOM, Fort Carson / EUCOM — determines the language requirement. A commander whose language proficiency dropped below the group floor between deployment cycles is a commander the SOTF is quietly working around.

The good 18A lieutenant is the team commander whose ISOFAC brief the SOTF commander reads and says "this team knows what it's doing." His NCOERs on the enlisted soldiers are clean, on-time, and rated honestly through the Team Sergeant's input. His partner-force commander knows him by name before the deployment begins. His 180A warrant is running the technical coordination; his Team Sergeant is running the floor; the 18A is running the mission. By his second deployment cycle the Group S-3 is already naming him as the 18A who should get the harder mission sets.

You are the experienced SF captain or early-major — the 18A who commands the ODA through the career-defining deployment cycle, then transitions to the ODB (Operational Detachment Bravo / SF company) as the company commander or to the group staff. The SF community is small enough that every senior officer in the regiment knows what your ODAs did and what you didn't have the nerve to recommend.

After your lieutenant tour on an ODA you return to SWCS, Fort Liberty for the Special Forces Captains Career Course (SFCCC) — the SF branch equivalent of the Maneuver / Signal / FA Captains Career Course, focused on company-grade SF operations, SOTF staff integration, UW and FID at the company level, joint enabler integration, and the planning math that the Group S-3 expects an experienced 18A to handle without hand-holding. From SFCCC you slate back to a KD as either an ODA commander (senior captain returning to team command — the most common and most valued KD in the SF career field), an ODB commander (command of a six-ODA SF company, the B-team, responsible for operational synchronization of six 12-man teams against the SOTF's campaign plan), or a Group staff billet (S-3, J-3 equivalent, SOTF staff, JSOC staff). Post-command, the path to major runs through ILE / CGSC at Fort Leavenworth (resident or non-resident) and a field-grade staff tour at Group, USASOC, SOCOM, a COCOM J-3 or SOC-J, or a joint special operations task force. The SF branch progression to lieutenant colonel command (battalion / group) is built on two things: the depth of the operational record on your deployment cycles and the relationship the senior officers in the regiment have with your name. Neither can be faked. The ARSOF talent management community is small — four numbered groups, two National Guard groups, USASOC, JSOC — and reputations travel without email.

• 01Command an ODA through a full deployment cycle — ISOFAC, deployment, redeployment — executing UW, FID, DA, or SR mission sets at the SOTF-directed pace and integrating JTAC, partner aviation, enabler packages, and interagency coordination without losing either the mission or the team.
• 02Command an ODB (B-team) — synchronize six ODAs against the SOTF's campaign plan, allocate enablers across teams, run operational and administrative command of a 60-80 person company, write the company OPORD, and brief the SOTF commander on the company's six concurrent team operations.
• 03Run a Group or SOTF staff billet at a level the Group S-3 or SOTF chief of staff counts as a strategic asset — campaign-plan synchronization, CONOP staffing, GCC coordination, interagency deconfliction, the staff product the COCOM planners take seriously.
• 04Mentor and write OERs on ODA-commander-track lieutenants and on the team's warrant officer (180A) — the OER system is how you build the regiment's next generation, and an 18A who writes lazy OERs on his subordinates is an 18A the senior officers are watching.
• 05Translate operational lessons from the deployment cycle into planning adjustments and training modifications for the next work-up — the continuous self-improvement loop that keeps the team competitive across cycles.
• 06Make the branch / FA / joint-tour decision honestly — DA PAM 600-3 SF branch chapter, USASOC talent management guidance, and the realistic post-command billet options (Group S-3, JSOC staff, COCOM SOC-J, joint tour, SAASS / SAMS / Senior Service College) shape the career trajectory after command.

• —FM 3-18 — Special Forces Operations; TC 18-01 — Special Forces Unconventional Warfare; ADP 3-05 — Army Special Operations (the operational triad; read them cold before every deployment cycle briefing).
• —JP 3-05 — Special Operations; JP 3-05.1 — Joint Special Operations Task Force Operations (the joint doctrine that COCOM planners use; the 18A briefing a GCC staff needs to hold the joint conversation).
• —ADP 3-0 — Operations; ADP 5-0 — The Operations Process; ADP 6-0 — Mission Command (the field-grade planning and command spine).
• —AR 600-8-29 — Officer Promotions; DA PAM 600-3 — Officer Professional Development, SF branch chapter (the career-arc math — KD timing, FA designation window, CGSC sequencing, command-board demographics).
• —AR 600-20 — Army Command Policy (you wield UCMJ authority over the company as ODB commander; the procedural side under AR 27-10 is the detail that saves you when a disciplinary action gets appealed).
• —AR 623-3 + DA PAM 623-3 — Evaluation Reporting System (you write OERs on ODA commanders and NCOERs on warrant officers; the quality of your evaluation writing is the visible career-management act the senior officers read).

• —SFCCC (Special Forces Captains Career Course) graduate at SWCS, Fort Liberty — the branch-essential school that gates return to KD command.
• —ODA command tour completion — the career-defining KD for the SF officer. The operational depth of the deployment cycle (what mission sets, what theater, what partner forces, what SOTF) is the read the promotion board weights.
• —ODB command or SOTF staff tour — the company-command equivalent for the field-grade track; the billet that the Group commander reads as "this officer can synchronize multiple teams against a campaign plan."
• —ILE / CGSC at Fort Leavenworth — resident or non-resident — gated by HRC slating. The resident program is the field-grade credential and a visible signal to the promotion board.
• —O-4 board at the IPZ window — approximately 10-11 years commissioned under current AR 600-8-29 cycles. SF-branch selection rates are published in each board release; pull the current HRC release before drawing conclusions from rumored numbers.
• —Joint duty (JDAL billet) credit on the field-grade path — JSOC, SOCOM, COCOM J-3 / SOC-J, CJSOTF staff — valued visibly in ARSOF career management and on the SF lieutenant-colonel promotion board.

• —Treating ODB command as a management tour instead of an operational command. The six ODA commanders you command are watching whether you can lead from the front — resource them honestly, advocate for them with the SOTF, and make the hard operational calls without waiting for the SOTF to make them for you.
• —Letting the Group staff billet become an administrative holding pattern. The SF officers who treat a Group S-3 or USASOC staff tour as a box-check produce staff product that the senior officers route around; the SF officers who treat the same billet as an operational opportunity to shape the Group's campaign plan get named in the next command-slate conversation.
• —Skipping the honest talent-management conversation with the Group S-1 and the USASOC human capital office. The SF branch is small and the command-slate process operates on relationship capital built across deployment cycles — the 18A who is invisible in the talent-management conversation until the board is six months away is the 18A the board surprises.
• —Writing OERs that inflate subordinate ODA commanders. The promotion board reads the senior-rater profile; an inflated OER on a marginal ODA commander produces a distorted cohort and the senior officer who signed it is remembered for it.
• —Confusing operational depth with staff depth. The SF officer who is brilliant on an ODA but cannot produce a defensible CONOP, campaign synchronization matrix, or GCC staff package at the Group level is visible on the field-grade staff immediately — and the transition from tactical executor to operational planner is the career-shaping test of the SFCCC and first staff tour.

The good SF captain commands an ODA whose operational record the SOTF commander names in the campaign-plan AAR — the team ran the mission set it was assigned, built the partner-force relationship it was supposed to build, and came back with an after-action review that shaped the next rotation's planning. His ODB command synchronizes six teams against the campaign plan without the SOTF having to manage the ODB's bandwidth problems for him. His warrant officer (180A) is on the group-staff track or the SFAUC pipeline. His ODA commanders are getting the KD OERs that the O-4 board can defend. As a major on staff, the Group S-3 or SOTF chief of staff is putting the hardest planning problem on his desk because the product will come back at the right level, on time, and defensible to the GCC. His ILE is complete; his joint-tour credit is on the record; and the USASOC talent-management office has his name in the command-slate conversation before the board convenes.