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 38B Civil Affairs Specialist — overview, pay, training, civilian translation, reviews
38BE6

Civil Affairs Specialist

E-6 (Staff Sergeant) · Army

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

You are the team sergeant of a CAT-A. The officer commands; you run the operators, the assessment quality, and the reporting that flows up to the CMOC. Everything that leaves this team with the team's number on it has passed through your quality filter — or it should have. The team sergeant who lets a junior soldier push a CIR to the CMOC without review owns that CIR when the BCT S5 briefs it wrong to the brigade commander.

The Honest MOS Read
Team sergeant is the seat the 38B career was designed around. The SSG who earns the team sergeant role owns the CAT-A's operational performance end-to-end: the assessment schedule, the CMOC reporting posture, the KLE relationship portfolio assigned to the team, the jump currency and language training of the soldiers below, the property accountability, and the counselings on the 14th. On a SOCOM-aligned deployment, you are the senior NCO embedded with an SF or SOTF element, coordinating the CA task schedule with the JSOTF J9 and interfacing with interagency partners that your team has spent months building access to. The USAID field officer who returns your calls because the previous team managed the relationship correctly is a strategic asset. The one who stopped returning calls because the previous team sergeant burned the access is an eighteen-month rebuild project. The assessment work at SSG is no longer individual — it is supervision and quality control. You review every CIR before it leaves the team. You sign off on every KLE package before the team officer briefs the supported commander. You know what the CMOC data quality looks like for your section not because the CMOC OIC told you but because you ran the gap analysis yourself this week. The team sergeant who waits for someone else to surface a data quality problem in their section has already failed the quality-control function. You write three to four NCOERs per cycle. Those NCOERs are the most consequential personnel documents in the 38B enlisted community because the community is small enough that the CMOC OIC, the battalion S3, and the brigade senior NCO read them alongside the performance record they have personally observed. An inflated NCOER for a SGT who could not build a sourced CIR package is found out by the next rater, and the SSG who inflated it is the one who answers for it at the E-7 board. The interagency coordination at SSG moves up a level. You are not just participating in the sector coordination meeting — you are running the CA team's coordination with the DOS program officer, the USAID field director, and the senior NGO cluster coordinator at the team-to-program level. You understand their mandates, you protect source relationships, and you extract civil information without burning the access. The team officer does not hold your elbow in that room. You walk in knowing what the team needs and walk out with a concrete next step or with an honest read on why the next step is not available right now. The ALC-to-SLC window matters at this rank. ALC is behind you; SLC is the gate for E-7 competitiveness. The Advanced Civil Affairs Tactics Course (ACATC) and JFKSWCS senior NCO programs are the CA-specific differentiators that distinguish the SSG who is competitive for the SLC slate and the CMOC NCOIC development track from the SSG who is generically qualified. The team sergeant who completes the CA institutional education pipeline on schedule and stays in the JFKSWCS community's sight line is the one on the short list for the battalion-level senior NCO positions that define the E-7 tour.
Career Arc
  • 01ALC graduate; Advanced Civil Affairs Tactics Course (ACATC) consideration as the CA-specific differentiator.
  • 02Team sergeant of a CAT-A: CMOC discipline, assessment quality, KLE portfolio, team readiness metrics all owned.
  • 03First full NCOER cycle as the senior rater — three to four NCOERs, every bullet in action-result-impact format.
  • 04SOCOM-aligned deployment or major CTC rotation as team sergeant — civil situation brief quality the supported command names.
  • 05SLC packet built and submitted — the STEP gate for E-7 competitiveness.
  • 06CMOC NCOIC development track consideration — battalion-level senior NCO positions that define the SFC career arc.
  • 07E-7 board: SLC complete + competitive NCOER profile + chain recommendation + team assessment quality record.
Common Screwups
  • ×Letting a junior soldier push a CIR or KLE report to the CMOC without your review. You signed for the team's reporting; you own every product that leaves it — and the CMOC OIC will trace every bad entry back to the team number.
  • ×Writing an NCOER as a wish list. The CMOC OIC and the brigade S5 know your team's assessment output; the NCOER that inflates a SGT who could not build a sourced CIR package is found out, and the SSG who inflated it answers for it at the next board.
  • ×Burning an interagency relationship by treating a USAID or DOS counterpart as a subordinate in a joint planning event. The CO learns about it from the Embassy, not from you — and the recovery timeline is longer than your current assignment.
  • ×Letting the team's language training lapse because the deployment schedule is busy. Language credibility opens access a translator cannot replicate; once the access is lost, the KLE relationship is degraded for the team that follows you.
  • ×Confusing tactical coordination with strategic-level civil-political engagement. Your team's interagency partners operate on a different authority structure; a misstep at that level goes to the Ambassador, not the brigade commander.

A Day in the Life

  • 0500Formation accountability for the team. Know the status of every soldier on the roster before the team officer shows up for PT.
  • 0530-0630Team PT. Team sergeant leads or co-leads based on the unit's structure. Your physical standard is visible to the team — if you are not competitive on the ACFT, the junior soldiers notice before you do.
  • 0700-0800Pre-work window: CMOC gap analysis check from the previous day's entries, any outstanding CIR corrections to review before the team officer arrives.
  • 0800Team formation. Brief the day's schedule and any operational or administrative changes. Assign daily tasks to the assessment NCOs.
  • 0830-1100Assessment cycle management: review CIR drafts for the team's reporting section, coordinate KLE schedule with the team officer, interface with the CMOC OIC on data quality posture and reporting priorities.
  • 1100-1300Chow and administrative period. NCOER input review if in cycle. Counseling sessions on the 14th.
  • 1300-1600Interagency coordination events if scheduled: sector coordination meetings with NGO cluster leads, DOS program coordination, USAID field director updates. Or: doctrine review, training plan development, SLC packet coordination.
  • 1600-1700Afternoon formation. Review the day's assessment products before close-of-business. Identify any CIRs that need same-day corrections before they hit the CMOC.
  • 1700-1800Soldier check-in. Know where the team is going this evening. The team sergeant who knows about the problem before the first sergeant does is the one who manages it as a leadership event, not a command event.
  • 1800-2000Personal and family time. Team sergeant workload does not stop at 1700 in a deployment cycle; in garrison, protect this window.
  • 2000-2100NCOER drafts, CMO estimate work, country study and AOR reading. The team sergeant whose civil situation knowledge stays current through open-source reading produces a better CMOC brief than the one who only reads from the CMOC database.
  • 2100-2200Personal maintenance and rack. The team sergeant who is perpetually exhausted is not managing the workload — they are letting the workload manage them.

Weekly Cadence

Monday is the quality-control day. Review the previous week's CMOC production from the team's section: source attribution check on every entry, gap analysis update, KLE commitment status review. Brief the team officer on the civil situation posture and any data quality issues before the CMOC OIC runs the weekly update brief to the supported command. Tuesday through Thursday are the execution and coordination days. Assessment fieldwork, KLE execution, interagency coordination events, and CIR production peak in this window. The team sergeant is not in every meeting — the SGTs are running the sector engagements and you are managing the quality of the output and the coordination with the supported command's planning cycle. In a deployment environment this window is continuous and the CMOC hours match the supported command's operations tempo. Friday is the administrative and development close. NCOER input review for rated soldiers, SLC packet status check, ALC nomination tracking for the E-5 soldiers on the development track. Pre-deployment windows replace the Friday admin close with mission-specific rehearsals, property accountability, and the team's CMOC data quality pre-deployment baseline.

Key Skills — How to Drill Each

  1. 01
    Plan and execute a full CAT-A assessment cycle during a SOCOM-supported mission or CTC rotation — ASCOPE-PMESII framework, KLE schedule, sector coverage plan, CMOC reporting posture, gap analysis — without losing reporting discipline.
    The team sergeant's assessment cycle plan is the product that the JSOTF J9 or BCT S5 evaluates at the start of a rotation to determine whether the team is going to be a productive source of civil information or a liability. Build the plan before the rotation starts: what sectors the team will cover, which KLE relationships are active vs. need to be re-established, what the CMOC data currency looks like coming in, and what the priority civil information gaps are from the supported command's planning requirements. Brief the team officer on the plan and brief the CMOC OIC on the data quality posture. The team that shows up with a plan is the team the J9 integrates into the planning cycle.
  2. 02
    Interface with USAID, DOS, and NGO counterparts at the team-to-program level — understand their mandates, protect source relationships, extract civil information without burning access.
    The program-level relationship is different from the field-level coordination your SGTs are running. The USAID field director and the DOS political officer have organizational authorities and reporting chains that are independent of the military chain of command. Understand what they are funded to do, what constraints they operate under (visibility, security, reporting requirements to their own chains), and what the exchange value is for both sides of the coordination. A USAID program director who trusts the CA team with program information does so because the previous team sergeant protected that information and did not route it outside the civil information system without coordination. Guard that trust the way you guard the team's sensitive items accountability.
  3. 03
    Build a team-level training plan that produces two assessment-qualified SGTs and a fully current CMOC database within a 12-month cycle.
    Assessment qualification does not happen by osmosis — it happens through a deliberate training plan that includes doctrine study, practical exercises, observed assessment execution with feedback, and CIR production cycles reviewed by the team sergeant. Build the 12-month training plan at the start of the cycle, identify the two SGTs on the team sergeant development track, and assign them progressively more independent assessment work until they are running full assessment cycles with minimal guidance. The CMOC database is a trailing indicator of the training quality — if the gap analysis currency is slipping, the training plan is not working.
  4. 04
    Write the CMO estimate for the supported commander's OPORD — civil situation, civil considerations, CA tasks recommended, interagency synchronization points — to CAQC-graduate standard.
    The CMO estimate is the team sergeant's signature product for the supported command. It needs to go beyond what the CMOC database shows to what the civil situation means for the mission — the civil vulnerabilities, the population-dynamics pressure points, the interagency partner activities that affect the operating environment, and the CA task recommendations that would address the priority gaps. Work from FM 3-57 Chapter 5 and JP 3-57 Chapter III for the planning framework; work from the team's current ASCOPE-PMESII assessment for the content. The officer reviews it and signs it; make sure they can defend every line in it.
  5. 05
    Mentor your SGTs on team-sergeant development, NCOER writing, and the CW3 (180A or CA-adjacent warrant officer) path honestly.
    Mentorship at the team sergeant level is not cheerleading — it is an honest read on whether the SGT has the profile for the next assignment, the next school, and the next rank. The SGT asking about the 180A pipeline deserves to hear whether their SFAS profile is realistic, not a 'go for it, all you have to do is try' response that sends them to selection unprepared. The NCOER conversation is equally important: teach the SGTs under you to write action-result-impact bullets by reviewing their input drafts and explaining what was wrong with the ones that did not make the cut.

Manuals & References — What Chapters Matter

  • FM 3-57 — Civil Affairs Operations and JP 3-57 — Civil-Military Operations
    You teach both at this rank. The team sergeant who cannot walk a new SGT through Chapter 4 (CA tasks) or explain the interagency authority relationships in JP 3-57 Chapter II without opening the book has a credibility gap with the team. Own the doctrine before you expect the team to execute from it.
  • JP 3-08 — Interorganizational Cooperation
    The joint doctrine for DOS and USAID coordination that governs what you can and cannot ask of civilian partners at the program level. Read Chapters II and III before you walk into your first coordination meeting with a senior USAID program officer — the authority relationships are more complex than the field-level interactions your SGTs are running.
  • ADP 3-07 — Stability and ATP 3-57.10 — Civil Affairs Support to Nation Assistance
    ADP 3-07 is the strategic doctrinal framework your CMO planning is nested inside; ATP 3-57.10 governs the FHA and nation-assistance task execution that most SOCOM-aligned CA teams spend the majority of their deployment executing. Read them together — the ATP tells you what to do; the ADP tells you why it matters.
  • AR 623-3 and DA PAM 623-3 — Evaluation Reporting System and AR 600-8-19 — Enlisted Promotions
    You write NCOERs that directly affect E-5-to-E-6 promotion math in a small community where the rated NCOs are visible to multiple senior raters. The NCOER system's rules on senior rater profiles, the potential block, and the performance narrative are not bureaucratic details — they are the mechanics of the document you are writing.
  • SWCS-published CA doctrine supplements and JFKSWCS operational supplements
    The schoolhouse-current doctrine your team certifies against. The JFK Special Warfare Center publishes operational supplements and training supplements that are the living version of FM 3-57 and the ATPs — more current, more tactically specific, and directly relevant to the CAQC qualification standard your team operates against. Know what the current supplements say; the JFKSWCS assessors who evaluate your unit's CA training posture are grading against them.

Standards — How to Hit Each

  • ALC graduate; SLC packet built; ACATC or JFKSWCS senior NCO programs as the CA-specific differentiator.
    SLC is the E-7 board gate. Build the packet early and coordinate with the unit S1 on the timeline. ACATC and the JFKSWCS senior NCO programs are the CA-community credentials that distinguish the SSG who is competitive for CMOC NCOIC and battalion staff NCO positions from the SSG who is generically qualified.
  • Team CMOC data quality at or above CMOC OIC standard — no orphaned records, gap analysis current, CIR throughput on schedule.
    Run the gap analysis yourself weekly, not through a junior soldier relay. The team sergeant who knows the data quality picture firsthand is the one who can brief the CMOC OIC on the posture without waiting for a report. The team's CMOC section should pass an unannounced QC review by the CMOC OIC at any point during the rotation — build your section to that standard.
  • NCOER bullets in real action-result-impact format — concrete numbers, named rotations, verified outcomes.
    Before you write a bullet, ask: what did the soldier do specifically, what was the result of that action specifically, and what impact did that result have on the mission or the unit specifically. 'Team produced 47 sourced CIRs supporting BCT civil considerations planning at JRTC Rotation 25-05' is a bullet. 'Supported CMO objectives throughout the training year' is not — and the brigade S5 who watched the team's JRTC output knows the difference.
  • Airborne and language requirements maintained for the team as a whole.
    Track the team's airborne currency and language program status on a running document the team sergeant updates monthly. Escalate shortfalls to the team officer and the CMOC OIC before they become a readiness problem — the team sergeant who walks into the pre-deployment readiness review with known currency gaps that were not escalated owns those gaps.
  • Team assessment packages surviving QC at the CMOC and BCT S5 levels without rework.
    The standard is not 'passes QC after corrections' — it is 'passes QC without requiring the CMOC OIC to send it back.' Build the QC review into the team's production workflow so that the team sergeant's review catches what the CMOC would otherwise return. A team whose products routinely require rework has a team sergeant with a quality-control gap, not a junior soldier problem.

Technical Mistakes — Concrete Consequences

  • Letting a junior soldier push a CIR or KLE report to the CMOC without review.
    The CMOC OIC will trace every bad entry back to the team number; in a small community where the team sergeant is identified with the team's reporting quality, a pattern of unreviewed CIRs entering the CMOC is a readiness problem the CMOC OIC raises with the battalion S3 — and your name is on the team's CMOC section.
  • Burning an interagency relationship by treating a USAID or DOS counterpart as subordinate in a joint planning event.
    The Embassy hears about it before you brief the team officer; the JSOTF J9 hears about it from the Embassy; the access degradation affects the team's civil information production for the remainder of the rotation and potentially for the follow-on team.
  • Writing an NCOER as a wish list rather than an honest performance record.
    The CMOC OIC and the brigade S5 have direct knowledge of the team's assessment output; an inflated NCOER for a SGT whose products required constant rework is found out at the next rating cycle, and the SSG who inflated it is identified as a rater whose senior rater cannot trust the performance narrative.
  • Letting the team's language training lapse because the deployment schedule is busy.
    The KLE access the team loses when language credibility lapses is not recoverable on a short timeline — the partner-nation official who was willing to extend trust to a team member with working conversational competence is not automatically willing to extend the same trust to the translation-app version of the engagement.
  • Confusing tactical coordination with strategic-level civil-political engagement.
    A team sergeant who treats a DOS political officer's program coordination meeting as a military briefing event creates a report from the Embassy to the JSOTF commander that starts with 'your CA team sergeant does not understand the interorganizational coordination framework' — and that report does not stay at the JSOTF level.

Career Decisions at This Rank

  • CMOC NCOIC track vs. continued team sergeant assignments — which path develops the senior NCO career faster?
    The CMOC NCOIC position at a CA battalion or brigade is the SSG-to-SFC transition assignment that produces the senior NCOs the JSOTF J9 and the BCT S5 trust with the civil situation brief. It develops management skills (multi-team QC, CMOC database governance, civil situation synthesis) that the team sergeant role does not. The continued team sergeant path keeps you in operational deployments and builds the KLE and interagency experience that the institutional track does not replace. The honest answer is that the best senior NCOs in the CA community have done both, in whatever sequence the assignment system allows — and the team sergeant who cannot tell the difference between the two types of experience is the one who gets passed over for the CMOC NCOIC position by the SFC who came off three team sergeant tours.
  • SLC timing — push immediately or take the additional operational tour first?
    SLC is a gate, not a development opportunity with an optimal timing window — the earlier you complete it in the SSG career, the longer your SLC-complete record works for you. The CA schoolhouse and the JFKSWCS community track SLC completion as a readiness indicator for senior NCO development assignments. An SSG who is SLC-complete and operationally experienced from three team-sergeant deployments is on the CMOC NCOIC development slate; an SSG who is still SLC-pending is watching that slate from outside the room.
  • Extended active service vs. transition at the peak civilian market value of the 38B skill set.
    The SSG 38B with three operational deployments, a current security clearance, current interagency coordination experience, and a DLPT score in a high-demand language has peak civilian market value at this career point. USAID contractor roles, NGO program management, foreign service officer pipeline, and civil affairs advisory positions with allied military forces all have direct pathways from this background. The question is whether the senior NCO career trajectory (SLC, CMOC NCOIC, battalion staff NCO, SFC) offers better long-term outcomes than the civilian conversion. There is no universal answer — run the math against your family situation, your civilian credentials, and the specific civilian opportunities you have researched, not the abstract ones you imagine.

How the Seat Varies by Unit Type

  • 95th CA Brigade (Airborne) — SOCOM-aligned, active duty, JSOTF or SF Group support
    The team sergeant at the 95th is running a CAT-A in an operational SOF environment where the interagency partners are real USAID and DOS contacts with real program stakes and real reporting chains. The airborne requirement is enforced operationally. The physical and professional standards are set by the surrounding SOF community, not by the CA community in isolation. The JSOTF J9 who names the team sergeant by name in the planning cycle is the professional validation the 95th team sergeant is working toward.
  • RC CA Brigade (38th, 91st, 489th) — Army Reserve, mobilization and training cycles
    The RC team sergeant brings professional civilian expertise that is the structural force multiplier of the CA mission and often has civilian professional credentials (licensed engineer, attorney, accountant, public health official) that the active-duty force cannot replicate. Mobilization cycles can run six to eighteen months. Between deployments, maintaining team readiness — CMOC currency, language program compliance, jump currency, assessment methodology sharpness — through the drill weekend calendar requires planning and team-sergeant leadership that the active-duty daily schedule provides automatically.
  • CMOC NCOIC or CA Battalion Staff NCO — institutional and staff CA role
    The CMOC NCOIC or battalion staff NCO role is the team sergeant who moved up from running a single CAT-A to managing the civil information enterprise for a battalion or brigade. The scope of the quality-control function expands: multiple teams' CMOC sections, multiple assessment cycles running simultaneously, and the civil situation brief to the battalion commander or the JSOTF J9. This role is the most direct development track toward SFC and toward the senior CA NCO positions that define the E-7 career.

What Good Looks Like at This Rank

The good SSG 38B runs a CAT-A the CMOC OIC and the supported BCT S5 name by team number — because the assessment products are sourced, the KLE reports are in the database, and the interagency partners return the team's calls. The USAID field director who returns the call is not doing it because the Army is the Army. They are doing it because the previous team sergeant managed the relationship correctly and the current team sergeant has not degraded it. Their SGTs are SLC-board ready. Not on paper — in reality: their NCOERs have concrete bullets, their ALC completion is documented, and the team sergeant has had the honest E-6 conversation with each one about whether they are on track or behind the curve. The soldiers who are behind the curve know it from the team sergeant, not from the E-6 board cutoff score. The team officer writes the team sergeant's performance narrative without having to ask for a self-assessment because the team sergeant's performance is visible in the CMOC data quality, the CIR throughput, the interagency partner relationships, and the junior NCO development that produced an SLC-board-ready SGT during the tour. The team sergeant who delivers those outcomes does not need to advocate for the good NCOER — the evidence advocates for them.

Preview — The Next Rank

At SFC, you run the CMOC's enlisted CA workforce — team sergeants, assessment NCOs, CIM section — across a deployment or multi-month exercise rotation. You do not own one team's assessment quality; you own the quality standard for the entire CMOC section. The team sergeants who work for you are learning team sergeant craft from watching you manage the CMOC posture and the interagency coordination at the civil situation level. The NCOER workload scales significantly. Four to five rated NCOs per cycle, each with a performance record the CMOC OIC and the brigade S5 can evaluate independently from your written narrative. The SFC's NCOER profile at the brigade level reflects not just the work done but the quality of the NCOs developed — a SFC who produced two SLC-board-ready SSGs during the tour is demonstrating a leadership output that is visible in the community. The warrant officer conversation at SFC shifts from 'should I do this?' to 'am I still in the window?' The 180A pipeline has age and physical standards that make the SFC the last viable entry point for most soldiers. If the warrant path is something you have been considering, SFC pin-on is the decision deadline, not a planning horizon.
FAQ

38B E6 — Frequently Asked Questions

Q01What does a E6 38B (Civil Affairs Specialist) actually do?
You own the CAT-A's operational performance end-to-end.
Q02What's the most important thing to know as a E6 38B?
You are the team sergeant of a CAT-A.
Q03What does a typical day look like for a E6 38B?
Time-blocked day at the E6 38B rank tier: 0500 Formation accountability for the team. Know the status of every soldier on the roster before the team officer shows up for PT, 0530-0630 Team PT. Team sergeant leads or co-leads based on the unit's structure. Your physical standard is visible to the team — if you are not competitive on the ACFT, the junior soldiers notice before you do, 0700-0800 Pre-work window: CMOC gap analysis check from the previous day's entries, any outstanding CIR corrections to review before the team officer arrives, 0800 Team formation.…
Q04What mistakes get E6 38B soldiers fired or relieved?
Letting a junior soldier push a CIR or KLE report to the CMOC without your review. You signed for the team's reporting; you own every product that leaves it — and the CMOC OIC will trace every bad entry back to the team number; Writing an NCOER as a wish list. The CMOC OIC and the brigade S5 know your team's assessment output; the NCOER that inflates a SGT who could not build a sourced CIR package is found out, and the SSG who inflated it answers for it at the next board;…
Q05What career decisions matter most at the E6 38B rank tier?
CMOC NCOIC track vs. continued team sergeant assignments — which path develops the senior NCO career faster? — The CMOC NCOIC position at a CA battalion or brigade is the SSG-to-SFC transition assignment that produces the senior NCOs the JSOTF J9 and the BCT S5 trust with the civil situation brief. It develops management skills (multi-team QC, CMOC database governance, civil situation synthesis) that the team sergeant role does not.…
Q06What's next after E6 for a 38B (Civil Affairs Specialist) in the Army?
At SFC, you run the CMOC's enlisted CA workforce — team sergeants, assessment NCOs, CIM section — across a deployment or multi-month exercise rotation.
Q07What manuals and regulations does a E6 38B need to know cold?
FM 3-57 — Civil Affairs Operations; JP 3-57 — Civil-Military Operations.; ATP 3-57.10 — Nation Assistance; ATP 3-57.60 — CA Planning; ATP 3-57.50 — Civil Information Management.; ADP 3-07 — Stability; ATP 3-07.6 — Protection of Civilians.

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