Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to 18F Special Forces Intelligence Sergeant — overview, pay, training, civilian translation, reviews
18FE5

Special Forces Intelligence Sergeant

E-5 (Sergeant) · Army

E1–E3E-4E-5E-6E-7E8–E9
HEADS UP

You are the only 18F on the ODA — no senior intelligence sergeant to defer to, no partner to split the work. The area assessment, the collection plan, the intelligence annex to every CONOP, and the daily PIR updates are yours. The team commander stops reviewing your products before they go up the chain when he trusts your analytical judgment — and that trust is built or lost in the first 90 days.

The Honest MOS Read
You have the tab, the flash, the group patch, and the TS/SCI. You are a Sergeant and the intelligence sergeant on a 12-man ODA — one of the billets in the SF team structure that has no redundancy. The team has two weapons sergeants, two engineer sergeants, two medical sergeants, and two communications sergeants. It has one intelligence sergeant. That asymmetry means you are the intelligence advisor, the collection manager, the area-assessment author, the targeting officer, the partner-force intelligence trainer, and the S2 shop rolled into one person. The team warrant and the team commander have their own lanes; the intelligence lane is yours. In garrison at your group — 1st SFG at Joint Base Lewis-McChord, 3rd SFG at Fort Liberty, 5th SFG at Fort Campbell, 7th SFG at Fort Liberty, 10th SFG at Fort Carson, or the National Guard groups — your week is shaped by the company training schedule and the group's intelligence cycle. The area assessment is the living document that the team's entire pre-deployment planning rests on. It covers the target country or region: political situation, military order of battle, terrain and infrastructure, culture and human geography, threat assessment, partner-force assessment, and the collection gaps that need to be closed before the team can execute. You wrote the first version of it at SFQC Phase 4; the real one is 10 times that. You update it when new reporting arrives, when the group's intelligence shop sends new products, and before every isolation period. Deployed — whether the mission set is Foreign Internal Defense (FID), Unconventional Warfare (UW), Direct Action (DA), Special Reconnaissance (SR), or counter-terrorism (CT) — you are the team's S2. The PIR list is the intelligence engine that drives the collection plan. The collection plan assigns collection tasks to the team's organic collectors (the 18Fs and any HUMINT-capable team members), to supporting collection assets the group or JSOTF can allocate, and to partner-force intelligence elements the team is working alongside. You track the open PIRs, push taskings, receive reporting, process it through the all-source analysis framework, and update the intelligence picture. In a FID mission, you are also training the partner force's intelligence personnel — teaching basic collection, reporting formats, intelligence cycle fundamentals — at the partner's level of capability, not the US standard. The TS/SCI environment means the OPSEC discipline is not an administrative checklist — it is the operational context you live in. The collection picture you maintain represents what the team knows, and what the team knows is what the adversary cannot know you know. The intelligence sergeant who treats OPSEC as a mandatory online course has already failed the most fundamental aspect of the billet.
Career Arc
  • 01Report to the group and patch in — the team assignment process happens through the group G1 and the company operations sergeant; your first day on the team, meet the Team Sergeant and receive the area-assessment folder.
  • 02First pre-deployment train-up cycle — isolation, pre-deployment intelligence production, country clearance briefs, team-level rehearsals with the intelligence annex integrated.
  • 03First deployment — FID, UW, DA, SR, or CT depending on group alignment and mission assignment; intelligence production and collection management in the operational environment.
  • 04Language sustainment cycle — DLPT retests at the group language-sustainment schedule; the team expects you to maintain or improve the language rating you left SFQC with.
  • 05BLC (Basic Leader Course) if not already complete — required for the SSG board; most 18Fs complete BLC during or immediately after the SFQC pipeline.
  • 06Schools: CDQC (Combat Diver Qualification Course), MFF (Military Free Fall), Mountain Warfare, or other team-profile schools as the Team Sergeant allocates slots.
  • 07ALC packet building — required for SSG board competitiveness; NCOER cycle begins with first annual evaluation by the Team Warrant (180A) or Team Sergeant (18Z).
Common Screwups
  • ×Letting the area assessment go stale between reporting cycles. The team commander who briefs the company with an outdated area assessment is embarrassed; the intelligence sergeant who let it age is the one the Team Sergeant has a private conversation with afterward.
  • ×TS/SCI mishandling — classified product on an unclassified system, classified discussion in an unsecured space, classified portable media without proper handling. One incident triggers the SF security manager, the group G2, and the counterintelligence function simultaneously.
  • ×Over-promising collection timelines to the team commander. The intelligence sergeant who says 'I will have the targeting package tomorrow' when the collection gap is two weeks away builds the wrong kind of reputation. Honest intelligence timelines, with honest confidence levels, build the right one.
  • ×Treating partner-force intelligence engagement as a briefing opportunity rather than a collection opportunity. The partner-force intelligence officer who trusts the 18F enough to share his reporting network is the most valuable intelligence asset on the team's campaign.
  • ×Going to the company S2 or group G2 without first bringing the problem to the Team Sergeant. The 18F who bypasses the team structure on intelligence matters is the 18F the Team Sergeant cannot trust to represent the team accurately upward.

A Day in the Life

  • 0500Wake. Kit check — if there is a morning range or field movement, the kit is already packed from the night before.
  • 0530PT formation. Garrison: team PT under the Team Sergeant's schedule — cardio days (team run), strength days (gym), recovery days. Intelligence sustainment does not exempt you from the team's physical standard.
  • 0700-0900Hygiene, change, DFAC or team room. Morning intelligence read: check the incoming traffic from higher S2/G2, the theater intelligence center, and any national products that arrived overnight. Flag anything that changes the running estimate and update accordingly.
  • 0900Team formation. Team Sergeant reads the day's tasks. Intelligence tasks: area assessment update cycle, PIR status brief to the Team Warrant, preparation for the company intelligence update brief if scheduled.
  • 0915-1200Morning work: intelligence production (area assessment update, targeting package development, CONOP intelligence annex), language sustainment (20-30 minutes of target-language study or a scheduled conversation session with the group's language program), coordination with the company S2 on collection requirements.
  • 1200-1300Chow. Use the time for passive language immersion if target-language media is available.
  • 1300-1600Afternoon work: PIR tracking and collection management, partner-force intelligence liaison (if deployed or pre-deployment preparation), SFQC-follow-on school prep if a CDQC or MFF slot is upcoming, team-level OPSEC and counterintelligence refresher if a deployment window is approaching.
  • 1600Final formation. Sensitive item check-in. Team Sergeant's brief for next day. Update the intelligence running estimate with the afternoon's reporting before end of day.
  • 1700-1900Personal admin, gym, or family time. Language study if not completed during work hours. The 18F who goes home and does not look at the evening intelligence traffic is the one who shows up to the 0900 brief without knowing what changed overnight.
  • 1900-2100Evening intelligence traffic review. Quick check of the reporting from higher that arrived after close of business. Update the PIR tracking log. Prep the next-morning brief if needed.
  • Isolation periodThe clock compresses. Isolation is the pre-deployment window where the team plans the mission in a controlled environment. The 18F's isolation output is the intelligence annex, the final area assessment, the updated targeting package, and the PIR list for the deployment. The isolation intelligence production timeline is set by the Team Sergeant; the 18F who cannot meet that timeline in isolation is the one who gets the most intrusive pre-deployment oversight from the team warrant.
  • Deployed (garrison/FOB equivalent)Intelligence reporting cycle replaces the garrison schedule. Morning read, PIR update, collection follow-up, partner liaison, CONOP intelligence input. The rhythm is driven by the operational reporting cycle and the team's daily planning meeting.

Weekly Cadence

The garrison week for an 18F on an ODA in a non-deployed, non-train-up window is shaped by the company training schedule and the intelligence production cycle. Monday is the heaviest administrative day — intelligence traffic review, area assessment update, PIR tracking meeting with the Team Warrant. Tuesday and Wednesday are training days — the team's Sergeant's Time Training (STT) cycle, which for an 18F includes analytical drills (IPB practical exercises, collection management scenarios) alongside the small-unit tactics, weapons maintenance, and medical sustainment events the rest of the team runs. Thursday is often ranges, language sustainment events, or the group's intelligence professional development block. Friday is team administration, award write-ups, NCOER input collection, and the safety brief before release. The week's intelligence rhythm overlays the training schedule. The area assessment update cycle runs monthly regardless of the training calendar. The PIR tracking log is updated every day there is incoming reporting. The language sustainment window — 20 minutes minimum — is a daily habit, not a weekly event. The 18F who treats language sustainment as an occasional training requirement is the one whose DLPT degrades between tests. The week changes dramatically during pre-deployment train-up. The training calendar compresses into ranges, mobility training, language intensives, partner-force read-in, and the intelligence work-up that feeds the isolation planning. The 18F who enters the train-up with the area assessment already current and the PIR list already drafted is the one whose isolation period is productive; the one who arrives with an outdated assessment is spending isolation producing the product he should have built six months earlier.

Key Skills — How to Drill Each

  1. 01
    Execute the IPB process (ATP 2-01.3) for the ODA's operational environment — terrain, weather, threat COA development, SITEMP — and brief the team commander on changes as the situation develops.
    The area assessment and the IPB are related but distinct products. The area assessment is the enduring background document; the IPB is the mission-specific analytical product. For a DA mission, step four of IPB (determine threat COAs and develop the SITEMP) is the product the team commander reads to understand what the objective area looks like from the threat's perspective. Drill the four IPB steps until you can execute them under time pressure in an isolation environment without referencing ATP 2-01.3 — the team commander who needs you in an isolation is not waiting for you to look up the format.
  2. 02
    Manage the team's collection requirements — PIRs, collection plan, tasking of organic and supporting assets, gap analysis.
    The collection plan is a living document, not a pre-deployment checklist. Write the PIRs in SFAC format (Specific, Factual, Answerable, Concise): 'What is the disposition and composition of [threat element] within [grid reference area] as of [time window]?' Not: 'What is the threat doing?' Assign each PIR to the collection asset most likely to answer it. Track open PIRs at every update cycle and push the team to close gaps before the mission window.
  3. 03
    Produce ODA-level all-source intelligence products — area assessments, country studies, threat assessments, targeting products.
    The area assessment format is: situation (political, military, economic, social, infrastructure, information — PMESII), threat assessment (order of battle, capabilities, intentions, COAs), terrain analysis, infrastructure, cultural analysis, and collection gaps. Write every section at the BLUF level — what does the team commander need to know to make a decision, in two paragraphs or less. The collection gap section is the most important: it tells the team what intelligence it needs before the mission can be planned confidently.
  4. 04
    Conduct and supervise basic HUMINT engagement per FM 2-22.3 within SF-specific authorities.
    The 18F's HUMINT authority in a deployed environment is defined by the Joint Intelligence Support Element (JISE) and the group's intelligence standing orders. Know your authority before you conduct any source development activity. Within those authorities, the approach technique from FM 2-22.3 Chapter 4 applies: establish rapport through genuine interest in the source's perspective; ask open-ended questions; listen more than you speak; document everything.
  5. 05
    Train partner-force intelligence personnel in collection, reporting, and the intelligence cycle.
    The partner-force intelligence training program has to be calibrated to the partner's starting point, not the US standard. Start with collection reporting format — teach the partner what a usable source report looks like (who, what, where, when, reliability assessment). Do not start with the US intelligence cycle framework — it is a model, not a requirement. The sustainable partner capability is what the partner can do without the 18F present; build toward that standard from week one.
  6. 06
    Maintain connectivity to higher S2/G2, theater intel centers, and national intelligence products.
    The group's intelligence shop and the supporting JSOTF or combatant command intelligence elements push products on a regular schedule. Build a read routine — every morning, check the incoming intelligence traffic from higher, update the running estimate, and flag anything that changes the PIR list or the area assessment. The team commander should never hear about a significant intelligence development from someone other than the 18F.

Manuals & References — What Chapters Matter

  • ADP 2-0 — Intelligence.
    The intelligence warfighting function chapter and the intelligence synchronization chapter explain how intelligence integrates with planning at the operational and tactical level. The 18F who understands the framework the team commander is thinking in produces better intelligence products — because the product speaks to the decision, not to the collection.
  • ATP 2-01.3 — Intelligence Preparation of the Battlefield.
    Chapters 2-5 are the daily operating framework. Chapter 5 (determine threat COAs and develop the SITEMP) is the product the team commander briefs from in isolation and in the field. Know it well enough to execute it under time pressure without reference.
  • FM 2-22.3 — Human Intelligence Collector Operations.
    The HUMINT source operations framework — approach, development, handling, debriefing — is the methodology behind every partner-force intelligence engagement and every direct-source collection activity the team runs. Chapter 4 (source operations) and Chapter 9 (tactical questioning) are the operational references.
  • FM 3-18 — Special Forces Operations.
    The SF mission-set framework. The intelligence requirements for a FID mission are different from the requirements for a DA mission, which are different from a UW mission. The 18F who understands the mission set the ODA is operating in writes intelligence products that serve the mission, not a generic template.
  • TC 18-01 — Special Forces Unconventional Warfare.
    The UW mission framework the 18F operates inside on UW-coded deployments. The area assessment methodology in TC 18-01 aligns with the 18F's production requirements for a UW campaign — population analysis, resistance movement assessment, and the operational environment assessment that the ODA's campaign plan rests on.
  • Joint Publication 2-0 — Joint Intelligence.
    The joint intelligence framework that connects the ODA's intelligence picture to the JSOTF, the combatant command's intelligence architecture, and the national intelligence community. The 18F who understands JP 2-0 can articulate the team's collection requirements in a format the JSOTF J2 will respond to.

Standards — How to Hit Each

  • Area assessment updated and current before every isolation window.
    Build a personal update cycle: every Monday morning, review the previous week's intelligence traffic and flag any reporting that changes a section of the area assessment. Run an update to the document every 30 days at minimum, and before every isolation period regardless of the calendar. The team commander should never read a date stamp on the area assessment that is older than 45 days.
  • TS/SCI clearance current with SSBI periodic reinvestigation on schedule.
    The periodic reinvestigation for TS/SCI runs on a cycle determined by the clearance authority. Know when yours is due. Report any changes to your personal situation — financial, foreign contact, foreign travel, legal — to the security manager proactively. The 18F who self-reports a foreign contact is in a manageable situation; the one who does not report and the SSBI finds it is in a career-ending situation.
  • Language DLPT at or above 1+/1+ in the team language; working toward 2/2 before the first reset cycle.
    The language is not a credential on the ERB — it is a functional tool the mission depends on. Build a daily language sustainment routine: 20 minutes of reading in the target language, 20 minutes of listening to target-language media, and a weekly conversation session with a native speaker if available through the group's language program. The DLPT retest is annual or biennial depending on your group's sustainment policy; do not let the language regress between tests.
  • BLC complete; ALC packet under construction.
    BLC (Basic Leader Course) is typically completed during or shortly after the SFQC pipeline for most 18F candidates. If not yet complete, it is the first school priority. ALC (Advanced Leader Course) is required for the SSG board; the ALC packet needs to be in the system before your window opens. Talk to the company operations sergeant about the timeline and the group's school-slot allocation process.

Technical Mistakes — Concrete Consequences

  • Letting the area assessment age without update.
    The team that deploys with a stale area assessment — political analysis from eight months ago, threat OOB that predates the last election cycle, infrastructure data that does not reflect the current access routes — makes decisions based on an obsolete picture. The team commander briefs that picture to the company, the company briefs it to the battalion, and the eventual correction is traced back to the intelligence product. The 18F's credibility is the casualty.
  • Treating collection requirements as administrative forms rather than the engine of answering PIR.
    A collection plan that is filed and forgotten produces no intelligence. The PIRs that are not tracked, not assigned to specific collectors with specific timelines, and not followed up on become open gaps that the team briefs around rather than through. The intelligence picture that develops from poorly managed collection is the one the team commander stops trusting — which means he stops bringing the 18F into the planning process as early as the mission demands.
  • Bypassing the Team Sergeant to take an intelligence concern directly to the company S2 or group G2.
    The Team Sergeant runs the ODA. The 18F who bypasses him to route an intelligence concern upward creates a command-and-information friction that the Team Sergeant then has to manage with the company. Bring every significant intelligence issue to the Team Sergeant first. He decides what goes up and in what form. The 18F who operates within that structure builds the trust that eventually gets him into the conversation before the Team Sergeant, not after.
  • OPSEC failure — classified product in an unclassified space, or classified discussion in an unsecured environment.
    A single classified-information incident on the ODA triggers the group security manager, the counterintelligence function, and depending on the nature of the product, the Defense Intelligence Agency and the originating collection community. The investigation delays the team's next deployment pending a damage assessment. The 18F involved is relieved from the intelligence billet and possibly the SF career field. There is no minor OPSEC incident at the TS/SCI level.
  • Training partner-force intelligence personnel to the US standard when the partner's system cannot sustain that standard.
    The partner-force intelligence program that is built to US reporting standards, US intelligence cycle processes, and US equipment produces a capability that exists only while the ODA is present. The day the team redeploys, the partner reverts. The sustainable product is built to the partner's system, the partner's reporting chain, and the partner's ability to maintain it independently. The 18F who trains to the US standard is training for the debrief, not for the campaign.

Career Decisions at This Rank

  • Re-enlist vs. ETS at the first window.
    The first re-enlistment window for an 18F typically opens 12-18 months before the end of the initial contract. The decision is layered: the SF community is a re-enlistment incentive environment (SRBs exist for 18-series), and the return on the SFQC investment — in terms of career development, operational experience, and post-service employment value — is highest when the contract runs long enough to include a second deployment cycle and an advanced school. The honest counter-argument: the 18F who ETS after a single deployment cycle with a TS/SCI and SF tab has significant options in the IC contractor and defense intelligence labor markets. The question is whether the remaining career value is more in the Army (senior 18F slots, team sergeant progression, language and regional expertise deepening) or outside it.
  • Advanced school priority: CDQC, MFF, Mountain Warfare, or Ranger.
    The SF community's school-slot allocation is competitive. The Team Sergeant allocates slots based on mission profile, individual performance, and the team's needs. CDQC (Combat Diver Qualification Course at Key West) is the most consistently available for teams with dive requirements; MFF (Military Free Fall at Yuma) is the most competitively allocated because every team wants MFF-qualified members. For the 18F, the question is which school adds operational capability to the team's mission profile — and the answer varies by group. Talk to the Team Sergeant about what the team's next deployment profile requires before requesting a specific school slot.
  • Language deepening vs. breadth — second-language investment.
    The SF community values language depth in the primary group language over breadth across multiple languages. The 18F who reaches 2/2 in Arabic is more operationally valuable to 5th SFG than the 18F who reaches 1+/1+ in Arabic and 1+/1+ in French. The group's language sustainment program is built around the primary language; the second-language investment is typically self-directed. The exception: if the 18F is considering a transfer to a different group alignment (or is assigned to a multi-region team), a second language creates a specific competitive advantage in the assignment process.
  • Regimental intelligence professional pathway vs. team sergeant track.
    The 18F career field has two senior paths. The first is the intelligence-specialized pathway: senior team 18F → company S2 → group G2 intelligence NCO → USASOC or theater SOC intelligence assignment. This path produces the deep intelligence expertise that the SF community's analytical capability depends on. The second is the team sergeant track: the 18F who cross-trains sufficiently to compete for the 18Z slot and run an ODA as Team Sergeant. Both paths produce E-8/E-9 senior NCOs; the Team Sergeant track is more commonly recognized within the regiment but is not inherently superior for an 18F with deep regional and analytical credentials.
  • IC agency or defense intelligence employment (post-ETS planning).
    The 18F post-service employment picture is strong — CIA, DIA, NSA, NGA, and the defense intelligence contractor ecosystem all recruit actively from the SF 18F community. The TS/SCI, the SF tab, the language qualification, and the operational intelligence experience are the combination those organizations cannot generate internally. The most significant variable is timing: the TS/SCI periodic reinvestigation must be current at separation; a lapsed clearance creates a re-investigation delay that pushes the start date six to eighteen months. The 18F who plans the separation timeline around the clearance cycle makes the transition smoother.

How the Seat Varies by Unit Type

  • Active duty group, CENTCOM-aligned (5th SFG — Fort Campbell)
    5th SFG is the most continuously deployed group in the SF regiment, with the longest operational history in CENTCOM. The 18F at 5th SFG operates in an Arabic, Pashto, and Dari language environment and against an intelligence architecture that includes multiple partner-nation intelligence services and a dense JSOTF intelligence support structure. The area assessment production volume is high; the targeting work is constant. The language requirement is the most demanding in the SF community for a junior 18F.
  • Active duty group, EUCOM-aligned (10th SFG — Fort Carson)
    10th SFG operates in the European theater with Russian, German, and Eastern European language requirements. The intelligence architecture connects to NATO intelligence sharing frameworks and partner-nation intelligence services with significant institutional capacity. The 18F at 10th SFG in the current environment operates in a high-intensity intelligence production tempo driven by the European security situation.
  • Active duty group, INDOPACOM-aligned (1st SFG — Joint Base Lewis-McChord)
    1st SFG operates in the Indo-Pacific theater with Korean, Japanese, Tagalog, and Mandarin language requirements depending on team alignment. The intelligence architecture connects to Five Eyes partner intelligence services and several regional defense partnerships. The theater intelligence picture is complex and multi-domain; the 18F at 1st SFG operates in an environment where the distinction between tactical and strategic intelligence is particularly thin.
  • National Guard SF group (19th SFG — Utah, 20th SFG — Alabama)
    The NG 18F operates at the same standards as the active-component 18F during deployments and activations. The difference is the between-deployment window: NG 18Fs frequently hold civilian careers in intelligence-adjacent fields (federal law enforcement, IC agencies, state fusion centers, defense contractors), and those careers reinforce the analytical skill set in ways the active component's training schedule cannot replicate. The DLPT sustainment requirement and the clearance reinvestigation cycle apply identically to NG 18Fs; the administrative load of managing them without a full-time S1 shop is higher.

What Good Looks Like at This Rank

The good junior 18F is the intelligence sergeant the Team Sergeant trusts enough to brief the company intelligence update without review. The Team Warrant has read enough of the products to know they are consistently BLUF-first, sourced, and analytically honest about the gaps — and that last part matters as much as the first two. An intelligence product that tells the team commander 'we do not know X and here is why' is more valuable than one that fills the gap with an assumption labeled as analysis. His area assessment is updated before the isolation window opens, not during it. His PIR list is tied to specific collection tasks with specific owners and specific timelines. When the team commander asks 'what do we know about the objective area,' he gets a 90-second answer that covers the ground truth, the confidence level, and the open gaps — and then the 18F hands over the area assessment folder for the deeper read. He does not brief the folder; he briefs the conclusion. By the second deployment cycle, the group's intelligence shop is pulling the ODA's area assessment as the regional format bar for similar teams deploying to the same area. The team commander is bringing the 18F into the mission planning process at the COA development stage, not just the intelligence annex stage — because the commander has learned that the 18F's read of the intelligence picture changes the COA, not just the annex. The Team Sergeant is already coaching him toward the SSG board and the senior-intelligence track at E-6.

Preview — The Next Rank

The SSG window is the senior-18F billet — either a higher-OPTEMPO ODA in a senior intelligence sergeant seat, or the company-level S2 role managing intelligence for multiple ODAs. Either way, the individual production responsibility expands to institutional intelligence leadership responsibility. The SSG 18F who moves to company S2 is no longer accountable only for the quality of one team's intelligence picture; he is accountable for the quality of every team's intelligence picture under the company's command. The technical transition is from being the best intelligence producer on the ODA to being the person who makes all the 18Fs in the company better intelligence producers. That is a different skill — it requires the ability to evaluate a product, identify the analytical failure mode, and explain the correction in a way the junior 18F can apply tomorrow, not just understand abstractly. The NCOER cycle becomes a management tool at SSG — the senior-18F NCOER bullet that picks the next company S2 is written by the SSG, not the Team Sergeant. The quality of that bullet determines the junior 18F's career trajectory as surely as the quality of his area assessment determined the team's operational confidence. The SSG 18F who writes NCOERs with the same analytical discipline he applies to intelligence products is the one the group senior rater can defend at board.
FAQ

18F E5 — Frequently Asked Questions

Q01What does a E5 18F (Special Forces Intelligence Sergeant) actually do?
Most 18F soldiers patch into a Special Forces Group as a SGT after SFQC.
Q02What's the most important thing to know as a E5 18F?
You are the only 18F on the ODA — no senior intelligence sergeant to defer to, no partner to split the work.
Q03What does a typical day look like for a E5 18F?
Time-blocked day at the E5 18F rank tier: 0500 Wake. Kit check — if there is a morning range or field movement, the kit is already packed from the night before, 0530 PT formation. Garrison: team PT under the Team Sergeant's schedule — cardio days (team run), strength days (gym), recovery days. Intelligence sustainment does not exempt you from the team's physical standard, 0700-0900 Hygiene, change, DFAC or team room. Morning intelligence read: check the incoming traffic from higher S2/G2, the theater intelligence center, and any national products that arrived overnight.…
Q04What mistakes get E5 18F soldiers fired or relieved?
Letting the area assessment go stale between reporting cycles. The team commander who briefs the company with an outdated area assessment is embarrassed; the intelligence sergeant who let it age is the one the Team Sergeant has a private conversation with afterward; TS/SCI mishandling — classified product on an unclassified system, classified discussion in an unsecured space, classified portable media without proper handling. One incident triggers the SF security manager, the group G2,…
Q05What career decisions matter most at the E5 18F rank tier?
Re-enlist vs. ETS at the first window — The first re-enlistment window for an 18F typically opens 12-18 months before the end of the initial contract. The decision is layered: the SF community is a re-enlistment incentive environment (SRBs exist for 18-series), and the return on the SFQC investment — in terms of career development, operational experience, and post-service employment value — is highest when the contract runs long enough to include a second deployment cycle and an advanced school.…
Q06What's next after E5 for a 18F (Special Forces Intelligence Sergeant) in the Army?
The SSG window is the senior-18F billet — either a higher-OPTEMPO ODA in a senior intelligence sergeant seat, or the company-level S2 role managing intelligence for multiple ODAs.
Q07What manuals and regulations does a E5 18F need to know cold?
ADP 2-0 — Intelligence (the doctrinal anchor for every analytic and collection decision you make on the ODA).; ATP 2-01.3 — Intelligence Preparation of the Battlefield (the IPB process the team commander expects you to run cold).; FM 2-22.3 — Human Intelligence Collector Operations.

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