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 35M Human Intelligence Collector — overview, pay, training, civilian translation, reviews
35ME4

Human Intelligence Collector

E-4 (Specialist/Corporal) · Army

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

Specialist is where the shadow phase ends and the report has your name on it. You run your own screenings and debriefs now, and two things decide whether you pin SGT: an IIR rework rate trending toward zero and a security file with zero friction. Get on the BLC roster early — STEP requires it before you pin sergeant — and start the 351M technician conversation with the warrant, because the collectors he picks out at E-4 are the ones who complete the packet later.

The Honest MOS Read
You made E-4 Specialist — or E-4 Corporal, if your team needed you in a leadership slot before BLC and the company gave you the lateral. Either way, the shadow phase is over. You are the working HUMINT collector now: you run the screening, you conduct the debrief, you control the interpreter, and you own the Intelligence Information Report that comes out the other end. The new collectors copy how you ask a question and how you write it up, which means your habits are now the team's habits. The Army's tolerance for figuring-it-out drops sharply at this rank, and in this MOS the figuring-it-out you are no longer allowed has two parts: the craft and the line. The craft at E-4 is the full cycle. You screen to sort placement and access. You build a questioning plan against the requirement. You run the approach — entirely within ATP 2-22.3, because that is the only approved standard and there is nothing outside it — you exploit, and you terminate. You sustain rapport across multiple sessions. You manage the terp as a tool, not a co-collector: brief him, control the pace, debrief him afterward. And then you write the IIR: bottom-line up front, source evaluated honestly, no editorializing, no sourcing detail that exposes how you got it, written for a consumer who never met the source. The report is the product. Your rework rate — how often the team NCO sends it back versus signs it through — is the most honest scorecard you have, and at this rank it should be trending toward zero. The line at E-4 is no longer a recitation; it is a load you carry under pressure. When a requirement is hot and the room wants more, the legal ceiling does not move one inch. ATP 2-22.3 is the floor and the ceiling; the law of war and the Geneva Conventions are the hard limit above it; coercion is illegal and there is no 'creative license' on an approach. The collectors who get relieved in this MOS get relieved here — for improvising an approach they cannot map to the doctrine, for an allegation they cannot rebut with documentation, for overstating a source's reliability because the reporting looked good. Document that you stayed in bounds. The documentation is not bureaucracy; it is the thing that protects you when an allegation comes — and in HUMINT, an allegation you cannot answer with paper is a 15-6 at best and a federal problem at worst. Promotion to E-5 Sergeant runs through the semi-centralized system under AR 600-8-19: 36 months TIS / 8 months TIG (waivable to 18/6), the chain's recommendation via the promotion-point worksheet (DA Form 3355), and a cumulative point score. The STEP (Select-Train-Educate-Promote) model means you cannot pin sergeant until you graduate the Basic Leader Course (BLC) at a regional NCO Academy. Slots are unit-allocated and they compress when the brigade pins a class of new E-5s. Talk to your section sergeant about the BLC roster in your first 30 days at E-4 — do not wait until you are max-points-eligible. The MOS-specific monthly cutoff is published by HRC and 35M moves cycle to cycle with the Army's HUMINT inventory; check the current SELCONT message before assuming a number. Your promotion points come from schools, awards, weapons qual, college credit, and — if you hold a language — your DLPT score, which pays FLPB and stacks points at the same time. The security file becomes a competitive differentiator at this rank, not just a requirement. The CI-scope polygraph and SCI access are table stakes; what separates you is being the collector with zero security friction — no late TARP report, no Continuous Vetting flag CI had to chase, no foreign-contact gap. Self-report everything under AR 381-12 and SEAD 3 inside the windows. And keep the source-administrative files audit-clean, because the S2X and CI both inspect them and a gap is a finding with your name on it. The warrant has started watching the SPCs whose reporting gets cited at echelons above the unit and whose files never generate a finding — those are the names that come up first when the 351M technician conversation starts.
Career Arc
  • 01E-4 pin-on: automatic at 24 mo TIS / 6 mo TIG (both waivable for visible performers).
  • 02Shadow phase ends — you run your own screenings and debriefs and own the IIRs that come out of them.
  • 03BLC roster conversation with your section sergeant — get on early; STEP requires BLC before you pin sergeant.
  • 04Promotion-point worksheet (DA Form 3355) build — schools, awards, weapons qual, college credit, and DLPT if you hold a language.
  • 05IIR rework rate driven toward zero; reporting starts getting cited above the unit instead of returned.
  • 06First 351M (HUMINT Collection Technician) conversation with the warrant for the collectors he has picked out.
  • 07BLC graduation, then E-5 pin-on once the cutoff hits and the chain releases the promotion.
Common Screwups
  • ×Improvising an approach you cannot map to ATP 2-22.3 because the requirement is hot. There is no creative license on the legal line — an allegation you cannot rebut with documentation is a 15-6 at best, a federal problem and a law-of-war referral at worst, and it can suspend the unit's authority to collect.
  • ×Waiting until promotion-eligible to start the BLC roster conversation. Slots compress when the brigade pins a class; by then you are watching peers pin sergeant first.
  • ×Lying to the polygrapher or the security investigator — a debt, a foreign contact, a mistake you think you buried. The lie burns you, not the thing itself. Self-report under TARP / SEAD 3 first, every time.
  • ×Article 15 / DUI / off-post incident with a TS/SCI on the line — promotion-point flag, AR 635-200 separation risk, and the clearance suspension runs in parallel. You leave the SCIF the same afternoon.
  • ×Sleeping on college credit and language sustainment. CCAF / CLEP / DSST credits and a maintained DLPT score move the promotion-point needle materially under the current system — and a lapsed language costs the team a capability and you the pay.

A Day in the Life

  • 0500Wake. Coffee. No phone in the SCIF, so no overnight alerts. PT uniform on, badge in pocket. Run today's sessions in your head — which source, which requirement, which approach, where the legal lines sit.
  • 0530-0700Unit PT. You are at formation early because the cherry collector you mentor needs to see you there. ACFT prep is real for you — the shop's reputation rides on it. Then hygiene, OCPs, breakfast.
  • 0700-0730In-process the SCIF. Badge in, SF 702 past your container, reporting systems up, pull what came in against your sources and requirements overnight. The team NCO confirms the day's collection plan.
  • 0730-0900Morning huddle and session planning. You build the questioning plan for your debrief — objective, approved approach, ICD-206 sourcing in mind, termination criteria — and brief it to the team NCO before you run it. If you are corporal-pinned, you are also confirming the cherry's plan for the session he is shadowing you on.
  • 0900-1130Run your screening or debrief. You drive, the terp translates, you control the pace and stay inside ATP 2-22.3. A cherry collector shadows you and drafts the IIR off your session afterward. You terminate cleanly and write your in-bounds session documentation while it is fresh.
  • 1130-1300Chow. You eat with the team. Conversation drifts to the BLC roster, the next school, the 351M path, and which source on the line is worth the team's time this week.
  • 1300-1500Reporting and QC cycle. You write your IIR to ICD 203 / 206, self-edit against your rework log, and submit it. You QC the cherry's draft off the session he shadowed — red ink that teaches, not just corrects. Source-administrative file closeout for the day's contacts; two-person integrity on what needs it.
  • 1500-1600Development and additional duty. Promotion-point worksheet update with your section sergeant, BLC packet status, DLPT sustainment reading if you carry a language, or the additional duty (reporting-system account NCO, training NCO) that the team cannot live without.
  • 1600-1700Final huddle. The team NCO briefs the next day; you brief the reporting that has to clear tonight. SF 702 walk-around and SF 701 end-of-day checklist run; classified material, source files, and containers all accounted for before anyone leaves.
  • 1700Released — most garrison days. Corporal-pinned SPCs may stay to write a counseling; collectors with hot reporting may stay to clear it through the gate. Watch shifts and field cycles change this by hours.
  • 1700-2000Personal time. Gym (ACFT prep), study (CLEP / DSST / college for points, DLPT prep), schools-packet build. The disciplined SPC builds the SGT-board case here; the comfortable one drifts.
  • 2000-2200Counseling or technician-track prep. If you are corporal-pinned, you may have a DA 4856 to write on a cherry. If the warrant has started the 351M conversation, you are reading the packet requirements. Tomorrow starts at 0500.
  • CTC rotation (NTC, JRTC, JMRC) / real-world contingencyYou move to the field SCIF / S2X cell. The watch runs 24/7, the OC/T grades every product that leaves the cell, and you run real screenings and debriefs under time pressure — inside the lines, with the higher echelon watching the lines as hard as you are. A 14-day rotation is your visibility window to the warrant and the S2X.

Weekly Cadence

The Mon-Fri rhythm at SPC level runs on the same S2X battle rhythm the cherry follows, but your role is the opposite — you are running the sessions the cherry shadows. Monday is the heaviest planning day: the team triages the week's requirements against the sources you can actually reach, and you build your session plans for the week. You start Monday clearing the weekend reporting queue and prioritizing which sources are worth your limited collection time against the brigade's requirements. The discipline you are demonstrating now is the one you learned to recognize at E-3 — placement and access drive the plan, not curiosity. Tuesday and Wednesday are the heavy collection days — you run screenings and debriefs, you write the IIRs, and you QC the cherry's reporting off the sessions he shadowed on you. This is where your reputation gets built or stalled: the rework rate the team NCO sees, the in-bounds documentation you produce without being asked, the source evaluation you grade honestly even when the reporting is hot. It is also where you do the team-leader work if you are corporal-pinned — counseling the cherry, walking his session plan, and saying 'I am not approving this approach' when it does not map to the doctrine. Thursday is the staff-process and compliance day: the S2X huddle, the source-file audits, the intelligence-oversight documentation, and the inspection prep. Friday is the company-level event day and release. The week's second rhythm is the SGT-board machinery and the security file, and both run continuously. Your section sergeant updates your promotion-point worksheet (DA Form 3355) on a cycle — weapons qual, college credit, awards, DLPT score, structured self-development — and the BLC slot conversation is a standing item until you graduate. The compliance machinery never stops: TARP / SAEDA, OPSEC, and intelligence-oversight trainings on the brigade's published schedule, Continuous Vetting in the background, and self-reporting under AR 381-12 / SEAD 3 inside the windows. The SPC who tracks the worksheet quarterly, keeps the file friction-free, and drives the rework rate down is the SPC who hits the SGT cutoff on the first eligible cycle. Field rotations collapse all of it into a 24/7 watch, and the garrison cadence rebuilds on the other side.

Key Skills — How to Drill Each

  1. 01
    Run a full debrief cycle — approach, questioning plan, rapport, exploitation, termination — entirely within ATP 2-22.3, and document that you stayed in bounds.
    Plan the session before you walk in: objective, the approved approach you will use and why, your questioning plan against the requirement, your termination criteria. Map every move to a chapter-and-section of ATP 2-22.3 in your head before you make it. Write the session summary and the in-bounds documentation immediately afterward while it is fresh — the documentation is what protects you and the team if an allegation ever surfaces. The collector who can hand the warrant a clean session plan AND clean in-bounds documentation is the collector who gets the hard source.
  2. 02
    Produce IIRs that need no rework — BLUF, accurate source evaluation, no spillage of how you got it, written for a consumer who never met the source.
    Lead with the so-what. Evaluate the source's reliability and the information's credibility honestly per ICD 206 — do not inflate either because the reporting looks good. Strip every line that exposes the source, the place, or the method; a consumer two echelons up needs the information, not the operational detail. Self-edit against your own rework log before you submit. The SPC whose IIRs come back cited instead of returned is the SPC the team NCO stops double-checking — and the warrant starts noticing.
  3. 03
    Manage interpreter-supported collection so the terp is a tool, not a co-collector — brief, control the pace, debrief afterward.
    Brief the terp before the session: translate exactly, both directions, no summarizing, no editorializing, no answering for the source. Run short questions and demand full translation; watch the source, not the terp. Debrief the terp afterward for cultural read and demeanor. The gap between what the source said and what the terp thinks the source meant is where reporting goes wrong — close it every session. A collector who lets the terp run the conversation is reporting the terp's opinion, and that is the kind of error that surfaces in a consumer's bad decision.
  4. 04
    Apply IC analytic and sourcing standards (ICD 203, ICD 206) to your reporting so it survives the next echelon up.
    ICD 203 is the analytic-standards rubric (objectivity, sourcing, expressing uncertainty); ICD 206 is the sourcing-requirements standard for disseminated products. Read both and write your IIRs against them deliberately — name your confidence honestly, cite your sourcing correctly, and express uncertainty where the reporting warrants it. The product that meets ICD 203 / 206 at the SPC level is the product that gets cited at theater instead of kicked back; the collector who writes to that standard early is the collector the analyst at the next echelon learns to trust.
  5. 05
    Keep source-administrative and operational files audit-clean — the S2X and CI both inspect them, and a gap is a finding with your name on it.
    Treat the file as a legal record, because it is. Every contact, every session, every disposition logged contemporaneously, two-person integrity on what requires it, no floating pages, no backfilled lines. Build a habit: close the file the same day you ran the session. The S2X audit and the CI inspection both grade on this, and in HUMINT a file gap is not just an admin ding — a hole in a source's documentation can become a CI investigation. The collector with the cleanest files is the collector the warrant trusts with the sensitive source.
  6. 06
    Recognize and report a counterintelligence indicator — a source feeding you, a foreign-contact red flag, an OPSEC compromise — through AR 381-20 / TARP channels, not the rumor mill.
    Know the indicators: a source whose information is too clean and too consistent with what an adversary would want you to believe, an elicitation attempt, a foreign contact that does not add up, an OPSEC compromise. AR 381-20 and AR 381-12 (TARP) define what you report, when, and to whom — and they do not give you the discretion to sit on it because 'it is probably nothing.' Report it through the supporting CI element and let them work it. The boundary between HUMINT collection and CI investigation is a hard line; your job is to flag, not to investigate.

Manuals & References — What Chapters Matter

  • ATP 2-22.3 — Human Intelligence Collector Operations.
    Own it cover-to-cover now, not just the approach chapters. At E-4 you are running full cycles and the doctrine is the standard you are graded against on every session and every report. The approach chapters keep you legal; the screening, planning, and reporting chapters make you good. The warrant redlines your session plans against it chapter-and-section.
  • AR 381-10 — U.S. Army Intelligence Activities; AR 381-20 — The Army Counterintelligence Program.
    381-10 governs what you can collect, on whom, and under what authority — the regulation you operate inside every session. 381-20 governs the CI relationship and the hard boundary you do not cross from collection into investigation, plus the channel to report a CI indicator. At E-4 you are no longer just complying with these; you are the collector who recognizes when one of them is about to be violated.
  • ICD 203 — Analytic Standards; ICD 206 — Sourcing Requirements for Disseminated Analytic Products.
    These are the IC-wide standards your reporting is read against once it leaves the unit. ICD 203 covers objectivity, sourcing, and expressing uncertainty; ICD 206 covers how you source a disseminated product. Write your IIRs to them deliberately — the product that meets them is the product that gets cited up instead of kicked back.
  • DoDD 3115.09 — DoD Intelligence Interrogations, Detainee Debriefings, and Tactical Questioning.
    The DoD policy that bridges the law of war and ATP 2-22.3 and that your unit SOP flows from. Know it so you understand the standard you operate under is national policy, not a local interpretation — and so you can tell the difference when someone proposes 'how we do it here' that does not match what DoD actually authorizes.
  • FM 2-0 — Intelligence; AR 380-5 — Department of the Army Information Security Program.
    FM 2-0 places HUMINT in the all-source picture so you understand where your IIR goes and why the consumer needs it written the way they need it. AR 380-5 is the daily classified-handling discipline — storage, accountability, SF 700/701/702/153 — that the SSO, IG, and CI all inspect. At E-4 you enforce these on the newer collectors, so you have to know them better than they do.
  • AR 381-12 — Threat Awareness and Reporting Program (TARP).
    What you report, when, to whom — foreign contacts, foreign travel, unexplained affluence, attempted elicitation, suspicious cyber activity — for your own clearance and as the channel for a CI indicator you spot in your collection. The reporting windows are non-negotiable, and at this rank you are also the collector who reminds the newer ones to self-report before Continuous Vetting finds it.

Standards — How to Hit Each

  • IIR rework rate trending toward zero — your reporting comes back from the S2X cited, not 'send it back to the collector.'
    Keep the rework log you started at E-3 and act on the categories, not the individual fixes. Self-edit every IIR against ICD 203 / 206 and your own past redlines before you submit. Ask the team NCO once a month: what is the one thing my reporting still does that costs the consumer time? Fix that. The collector whose rework rate hits near-zero is the collector whose name the analyst at the next echelon starts trusting — and that trust is what the warrant reads when he picks the 351M bench.
  • BLC graduate; promotion points stacked through schools, DLPT, ACFT, and college credit.
    BLC is 22 academic days at a regional NCO Academy and STEP requires it before you pin sergeant. Get the slot on your section sergeant's radar in your first 30 days at E-4. Stack points in parallel: max your weapons qual, finish college credit through TA / CLEP / DSST, keep your DLPT current if you hold a language (points and FLPB at once), and keep the ACFT high. The SPC who locks the BLC slot and the point stack by month 12 of E-4 is the SPC who pins SGT on the first eligible cycle.
  • ACFT 540+ floor — senior collectors notice the SPC who brings the same intensity to PT that he brings to the screening line.
    540 is above the intel-shop average and it kills the 'soft' stereotype the senior NCOs work against. Build it with deadlift and push-up volume, interval running (the 2-mile is the score-killer), and grip/core work. The collector whose 540-plus makes the supported line unit say 'the HUMINT guys are squared away' is the collector who gets the next school slot and the benefit of the doubt at the board.
  • SCI access and CI-scope polygraph clean — the differentiator at this rank is not just skill, it is being the collector with zero security friction.
    Self-report everything under AR 381-12 and SEAD 3 inside the windows — before Continuous Vetting surfaces it. Keep your finances stable, document your foreign contacts and travel, and never carry an unreported anything into a reinvestigation or a poly. The collector with a friction-free file is the one the warrant slots into the sensitive source and the one the chain promotes without a second conversation; the collector who generates a flag a quarter is the one whose career stalls while CI works the file.
  • DLPT maintained if assigned a language — a proficiency lapse costs the team a capability and costs you the pay.
    If you hold a controlled language, your DLPT score is both a capability and a paycheck (FLPB per DoDI 1340.27). Schedule sustainment reading and listening into your week — an hour a day of band-level material is the cheapest FLPB you will ever earn. Re-test before the score lapses, not after. A team that loses its language readiness loses missions; the collector who lets his score drop is the one explaining to the warrant why the team can no longer cover a requirement.

Technical Mistakes — Concrete Consequences

  • Improvising an approach you cannot map to ATP 2-22.3.
    There is no creative license on the legal line. An allegation you cannot rebut with documentation is a 15-6 at best and a federal problem with a law-of-war referral at worst, and it can suspend the unit's authority to collect. The information you might have gotten is worthless; the precedent is poison. The warrant who learns you improvised stops trusting you with anything sensitive, and the senior rater remembers it longer than any award.
  • Overstating source reliability because the reporting looks good.
    A fabricator you graded 'reliable' steers a commander into a bad decision, and when it unravels the burn-notice has your name on it. Source evaluation is a discipline, not a vibe — grade reliability on track record and corroboration, not on how badly you want the reporting to be true. The collector who inflates a source once loses the analyst's trust in everything he submits afterward.
  • Letting the interpreter editorialize or summarize.
    You report what the source said, not what the terp thinks the source meant — and that gap is how reporting goes wrong. A summarized session is an unreliable session; if it surfaces in a consumer's decision and turns out wrong, the failure traces to the collector who lost control of the conversation. Brief and control the terp every time, or do not run the session.
  • Sloppy tear-lines or sourcing detail that exposes how you collected it.
    One disclosure can burn a source's safety, not just a method — and that is permanent. ICD 206 governs sourcing at the IC level and the consumer two echelons up needs the information without the operational detail. The collector who exposes a source in a report learns that the people who read his product cannot un-know what he should never have written, and the source may pay for it with more than a method.
  • Sitting on a CI indicator because 'it is probably nothing.'
    AR 381-20 does not give you that call. A source feeding you, an elicitation attempt, a foreign-contact red flag — you report it through the supporting CI element and let them work it. The collector who sits on an indicator and is wrong about 'probably nothing' is the collector who let a double work the team, and that failure is not an admin finding — it is a compromise, and it lands on the collector who saw it first and stayed quiet.

Career Decisions at This Rank

  • BLC slot timing (the STEP gate to SGT).
    BLC is mandatory before sergeant pin-on under STEP. Regional NCO Academies pin classes every few weeks; brigades push BLC packets in promotion-cycle waves. The decision is whether to push for the earliest slot — which gets you on the board fast but risks overlap with a CTC rotation or a real-world mission your team cannot run without you — or wait for a quieter quarter. Talk to the team NCO and the section sergeant about the unit's operational calendar before locking the slot. The trap is waiting too long: the SPC who delays watches peers pin first when the brigade pins a class and his packet is not ready.
  • 351M (HUMINT Collection Technician) candidacy — start building it now or not.
    The 351M warrant is the most consequential technical career in the MOS — the deep-expertise path that keeps you collecting and mentoring collection instead of moving into the broad-NCO track. The warrant starts the conversation at E-4 with the collectors he has picked out, and the SPC who builds the candidacy at E-4 is the SGT who completes the packet later. Building it means: near-zero rework reporting, a friction-free security file, the right schools, and a warrant willing to sponsor you. The honest test: do you want to stay a master of the craft (technician) or lead and develop the broader formation (NCO track to SSG / SFC)? Both are real careers. Start the technician conversation now if the craft is the thing you love; you can still take the NCO track if you decide later.
  • Re-enlistment with bonus (SRB) before SGT pin.
    The first re-enlistment window opens 12-18 months before contract end. The SRB for 35M per the current HRC SRB MILPER varies by zone and shortage indicator — 35M is often on the schedule because it is hard to fill and harder to keep, but pull the current message before assuming a number. The Critical Skills Retention Bonus runs in cycles for specific skill identifiers (language, technician-track) — check what your skills qualify for. The trap: signing while still SPC may lock you in at SPC contract terms; signing after SGT pin can open different zone math. Talk to the career counselor and the warrant before signing; the math may favor delaying the re-up by 60-90 days.
  • Language program (DLI) at the E-4 window.
    If you do not hold a language and your assignment path could use one, the E-4 window is a reasonable time to volunteer for DLI before the NCO load makes it impractical. The trade-off is months out of the seat (roughly 6 months for the easiest categories through over a year for the hardest — Arabic, Korean, Mandarin) against a capability that opens theater-HUMINT and national-detail seats, pays FLPB, and stacks promotion points. The harder it gets to leave the team — and once you pin SGT and own collectors, it gets much harder — the more the E-4 window is the one to use. Talk to the brigade language program manager and the warrant.
  • Corporal pin-on (lateral appointment) versus staying SPC.
    If the team needs a collection-team leader before you finish BLC, the company commander can laterally appoint you to E-4 Corporal. The pay is the same; the responsibility is leading collectors and owning the reporting and legal standard for a small team. The decision is whether to accept the lateral — visibility, NCO duties, an NCOER that describes team leadership — or stay SPC and wait for SGT via BLC. Corporal-pinned SPCs who perform get strong NCOERs and pin SGT on time; in HUMINT the lateral is also a test of whether you can hold the legal line for other people, not just yourself. Talk to the collector who held the billet before you accept.

How the Seat Varies by Unit Type

  • BCT / division MI company HUMINT element SPC
    The working collector in a tactical element runs screenings and debriefs against brigade or division requirements and lives by the CTC cycle. The reps are frequent and the feedback is fast because the element is small. The SPC who masters the full debrief cycle here and keeps a clean file is the one the team NCO hands the hard source to and the warrant starts watching. The trade-off: the analytic problem is tactical, and the strategic-HUMINT reporting standards come later in the career arc.
  • Brigade / division S2X cell SPC
    Close to the S2X, the working collector learns the requirements-management and deconfliction side earlier — triaging requirements against placement and access, coordinating with CI, and seeing how a tasking is born and managed. More staff visibility, more exposure to the warrant and the S2X OIC, and an earlier education in the operational-management element (OMT) skills that matter at SSG. The trade-off is fewer raw collection reps than a pure tactical seat.
  • Theater / MI battalion HUMINT element SPC
    Working theater-level problems for a CCMD means the reporting standards (ICD 203 / 206) are applied more rigorously because the product moves toward the national IC. The SPC here writes for a more demanding consumer and gets a harder education in source evaluation and analytic discipline. The OPTEMPO is less tactical and more deliberate; the pinning rhythm can be slower, but the analytic and reporting credibility built here travels well into the technician track and the cleared-civilian world.
  • INSCOM unit / closed-access HUMINT formation SPC
    The working collector in an INSCOM or closed-access formation operates in a more compartmented environment with tighter access controls. The craft and the legal discipline are identical; the difference is the closed-access culture and the early career-arc differentiation. Seats are often by name-request and come with specific access requirements, so the SPC who lands one already has a reputation worth requesting — clean reporting, clean file, knows the line.
  • Joint / supported-staff HUMINT SPC (JTF, task-organized element)
    On a joint or task-organized staff, the working collector has to speak the supported staff's language, not just the home-unit one, and the reporting feeds consumers who may not be Army. The deconfliction picture is more crowded and the OPSEC and authorities discipline gets more scrutiny because more elements are watching. It is a stretch seat for an SPC, usually given to the collector whose reporting and file are already trusted — and it builds the cross-organizational fluency that pays off at SSG on an OMT.

What Good Looks Like at This Rank

The good Specialist 35M is the collector the team NCO hands the hard source to, because the screening is sharp, the session stays inside ATP 2-22.3 without anyone having to remind him, and the IIR comes back clean and consumable. His rework rate is near zero. His reporting gets cited at echelons above his unit — the analyst at theater reads his product and acts on it without a follow-up question, because the source evaluation is honest, the BLUF earns its space, and there is not a line in it that exposes how he got it. He controls the interpreter so completely that the terp is invisible in the product. He does not improvise on the legal line and he never has to, because his planning is good enough that he does not need a shortcut. He is also the collector with zero security friction. His CI-scope poly is clean because he self-reported everything before anyone asked. His source-administrative files survive the S2X audit and the CI inspection without a comment. His name is not on the brigade non-compliance roll-up. He keeps his language score current, so the team never loses a capability on his account, and he keeps his ACFT high, so the supported unit never calls the HUMINT shop soft. The new collectors learn the rules by watching him refuse to bend them — he is the one who says 'we don't do that' in front of the cherry and means it, which is how the standard propagates without a class. The SPC being groomed for SGT looks different from the SPC who is comfortable at SPC. The grooming SPC has the BLC slot locked by month 12, the point stack built, the college credit finished, and the warrant already talking to him about the 351M path. He volunteers to QC the newer collector's reporting and to mentor the cherry through his first independent screening. The comfortable SPC runs good sessions and writes good reports but never builds the packet, never asks for the school, never takes the team-leader rep — and stalls at the 4-year mark because the chain has not seen the next-level work. In HUMINT the difference is sharpened by the security file: the grooming SPC is clean AND good, and the warrant only puts the technician conversation on the table for collectors who are both.

Preview — The Next Rank

E-5 Sergeant is the next rank, and it changes the question you answer every day from 'is my report clean' to 'is my team's report clean.' You become the collection team NCO — you lead a few collectors and their interpreters, and you are the quality-control gate on everything the team reports. The IIRs that leave your team carry your name as much as theirs; the legal and oversight discipline of the team is your signature. You still run sessions yourself, because the day you stop collecting is the day you stop being able to coach it, but the weight shifts from doing the craft to owning the standard. The new load at E-5 is leadership of people and enforcement of the line. You counsel your soldiers on the 14th and after every reporting cycle, and you write the DA 4856 that documents both a technical slip and a development plan — specific and measurable, not 'collector will improve reporting.' You quality-control every IIR to ICD 203 / 206 and to ATP 2-22.3 legal compliance before it leaves the team, because you are the last gate. You mentor a junior collector through his first independent source contact, which includes the 'I am not approving this approach' conversation — and meaning it, for someone else's session, is harder than holding the line for your own. You coordinate with the supporting CI element and the S2X on indicators and deconfliction, and you own the hard boundary between collection and investigation for the whole team. The differentiator at the next board and beyond is whether the chain trusts you to own a team's reporting and a team's legal discipline. That means BLC behind you and an ALC slot built and ready, an NCOER profile that describes measurable team performance, an ACFT high enough that your collectors respect it, and a team whose language readiness and security files you keep clean. The 351M technician conversation sharpens here — the SGT the warrant has on the short list is the one whose team's IIRs get cited up the chain and whose oversight files survive any audit. Pin SGT, own the gate, hold the line for other people, and the next conversation is whether you run a section — or whether the technician path the warrant has been talking about becomes the packet you build.
FAQ

35M E4 — Frequently Asked Questions

Q01What does a E4 35M (Human Intelligence Collector) actually do?
You run screenings and debriefs of your own and you own the IIRs that come out of them.
Q02What's the most important thing to know as a E4 35M?
Specialist is where the shadow phase ends and the report has your name on it.
Q03What does a typical day look like for a E4 35M?
Time-blocked day at the E4 35M rank tier: 0500 Wake. Coffee. No phone in the SCIF, so no overnight alerts. PT uniform on, badge in pocket. Run today's sessions in your head — which source, which requirement, which approach, where the legal lines sit, 0530-0700 Unit PT. You are at formation early because the cherry collector you mentor needs to see you there. ACFT prep is real for you — the shop's reputation rides on it. Then hygiene, OCPs, breakfast, 0700-0730 In-process the SCIF. Badge in, SF 702 past your container, reporting systems up,…
Q04What mistakes get E4 35M soldiers fired or relieved?
Improvising an approach you cannot map to ATP 2-22.3 because the requirement is hot. There is no creative license on the legal line — an allegation you cannot rebut with documentation is a 15-6 at best, a federal problem and a law-of-war referral at worst, and it can suspend the unit's authority to collect; Waiting until promotion-eligible to start the BLC roster conversation. Slots compress when the brigade pins a class; by then you are watching peers pin sergeant first;…
Q05What career decisions matter most at the E4 35M rank tier?
BLC slot timing (the STEP gate to SGT) — BLC is mandatory before sergeant pin-on under STEP. Regional NCO Academies pin classes every few weeks; brigades push BLC packets in promotion-cycle waves. The decision is whether to push for the earliest slot — which gets you on the board fast but risks overlap with a CTC rotation or a real-world mission your team cannot run without you — or wait for a quieter quarter. Talk to the team NCO and the section sergeant about the unit's operational calendar before locking the slot.…
Q06What's next after E4 for a 35M (Human Intelligence Collector) in the Army?
E-5 Sergeant is the next rank, and it changes the question you answer every day from 'is my report clean' to 'is my team's report clean.' You become the collection team NCO — you lead a few collectors and their interpreters, and you are the quality-control gate on everything the team reports.
Q07What manuals and regulations does a E4 35M need to know cold?
ATP 2-22.3 — Human Intelligence Collector Operations (own it cover-to-cover, not just the approach chapters).; AR 381-10 — U.S. Army Intelligence Activities; AR 381-20 — The Army Counterintelligence Program.; ICD 203 — Analytic Standards; ICD 206 — Sourcing Requirements for Disseminated Analytic Products.

Based on 18 tips from 0 contributors

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards