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 351M Human Intelligence Collection Technician — overview, pay, training, civilian translation, reviews
351MWO1-CW2

Human Intelligence Collection Technician

WO1 to CW2 (Junior Warrant) · Army

WO1–CW2CW3–CW5
HEADS UP

WO1 to CW2 is the window where you prove the warrant bar on your collar isn't just a promotion from 35M — it's a different kind of accountability. You are now legally responsible for what your sources produce and what you report. The collection operation that wasn't quite authorized is YOUR operation, and 'I thought it was approved' is not a defense that survives an AR 381-10 review.

The Honest MOS Read
The warrant bar changes what you own. As a 35M you executed collection and handed reports up the chain. As a WO1 or CW2 351M, you plan collection, you manage sources, and you sign the documentation that establishes whether an operation was legal, appropriately approved, and properly protected. That is a different weight class, and the first six months in the seat make that clear in ways the HUMINT Warrant Basic Course at Fort Huachuca prepares you for intellectually and the field clarifies experientially. Your billet will be in a Military Intelligence Battalion (organic to a division or corps), an INSCOM unit (potentially 66th MIB, 470th MIB, 500th MIB, 513th MIB, or the 902nd MI Group depending on the assignment), a division G2X HUMINT element, or a Theater MI Brigade HUMINT cell. The day-to-day at WO1/CW2 is grounded work: building and maintaining the source registry under AR 381-102, conducting source validation interviews and documenting access-motivation-reliability-security assessments, running debriefings and structured questioning sessions, producing IIRs to the format and classification procedures that the supporting DIA station grades, and managing the administrative files that keep the program legally clean and audit-ready. The IIR grade is how you are measured. The DIA station or J2X element that reviews your reports grades them on source reliability and information accuracy — grades run from 1 (completely reliable, confirmed by other sources) through 6 (reliability cannot be judged) for the source and from 1 (confirmed) through 6 (truth cannot be judged) for the information. A warrant whose shop produces IIRs that consistently grade low is a warrant whose program the chain of command stops trusting. You do not control what sources know. You absolutely control whether you validate sources properly, conduct structured debriefings that distinguish confirmed access from speculation, and note the confidence limits in every report you sign. The hardest adjustment for most new HUMINT warrants is managing the gap between commander expectations and collection reality. Commanders want answers. HUMINT provides reporting that contributes to answers. A CW2 who tells a battalion commander 'my source says X is true' without naming the reliability grade, the single-source limitation, and the corroboration requirement is doing his commander a disservice. The warrant who delivers 'we have HUMINT reporting suggesting X; source reliability is uncertain, no corroboration yet, here's what would confirm it' looks less decisive and is dramatically more useful. Building that communication habit early is the technical skill that separates the warrants who advise commanders from the ones who mislead them. Fort Huachuca is your schoolhouse, your career management home (via HRC Warrant Officer Branch), and the institutional center of MI doctrine. The HUMINT Warrant Basic Course wires the doctrinal framework. Your follow-on assignment wires the operational reality. The warrants who develop fastest are the ones who read FM 2-22.3 and ATP 2-22.3 not as school requirements but as field references — the doctrine describes what right looks like, and every debrief you run is a chance to measure the distance between your technique and the standard.
Career Arc
  • 01HUMINT Warrant Officer Basic Course completion at Fort Huachuca, MI School — credential gates the WO1 assignment.
  • 02First assignment: MI Battalion, INSCOM unit, or division G2X — source registry management, source validation, IIR production cycle.
  • 03First major collection operation: independently planned and executed, approved at the appropriate echelon, IIR results graded.
  • 04CW2 promotion milestone: source file current, IIR production record solid, AR 381-102 compliance clean.
  • 05Advanced Course consideration (HUMINT Warrant Advanced Course, Fort Huachuca) and joint or interagency exposure billet (DIA, CIA, FBI HIG coordination element).
  • 06CW3 promotion window: program management responsibilities expand; collection management and junior warrant mentoring role begins.
  • 07Decision point: operational HUMINT (theater-level collection environments, INSCOM assignments, joint SOF MI support) vs. institutional (MI School instructor, TRADOC, doctrinal development) — shapes the CW4/CW5 trajectory.
Common Screwups
  • ×Running a collection technique that requires a higher approval authority than you have without getting written approval first. AR 381-10 Table 3-1 is explicit about which techniques need what echelon authority. 'We were deployed and the timeline was short' is the line investigators hear most often.
  • ×Filing an IIR on a source who hasn't been formally validated. The report grades mean nothing if the source baseline isn't documented. The program unravels under audit when every IIR traces back to a source with no complete validation file.
  • ×Source identity compromise through administrative carelessness — a controlled-source file in a shared folder, a name in a product that goes outside the distribution channel, a brief that names a source to an audience with no need to know. Compromised sources don't get to be un-compromised.
  • ×DUI or Article 15 — access revocation risk on a TS/SCI program kills your career in a MOS where the clearance is the job. The 351M who loses his clearance at CW2 is no longer a 351M.
  • ×Not filing the counterintelligence referral when a source contact raises CI indicators because you don't want the collection program disrupted. The CI agent will tell you if it's nothing. You do not get to make that risk decision unilaterally.

A Day in the Life

  • 0530-0630PT with the MI Battalion or individual PT — warrant officers in MI units typically train with the battalion staff or their section, not with an infantry company. Garrison default.
  • 0630-0730Shower, breakfast, commute or transit to SCIF. Badging in, safe-opening, terminal log-on. Read overnight traffic: any IIR responses or grader feedback from the DIA station, any new ICRs from the G2X, any changed security status from the unit security manager.
  • 0730-0830Section stand-up or G2X coordination call — collection status, overnight developments, new PIRs or modified collection requirements. In a deployed environment this is the collection managers' sync that connects your element to the broader collection effort.
  • 0830-1130Primary collection work: drafting IIRs from yesterday's debriefing notes, writing contact reports, updating source files, or preparing a validation interview for a source meeting scheduled this week. If a debriefing is scheduled, this block is preparation — reviewing the current collection requirements, building the question set against PIRs, reviewing what the source has produced before and where the gaps are.
  • 1130-1230Lunch. In garrison this is the break from the SCIF. In a deployed environment the lunch block often shrinks to 20 minutes.
  • 1230-1530Afternoon collection work: source meeting or debriefing (if scheduled and the security protocol for the meeting site allows), IIR finalization and submission through the proper reporting channel, or HUMINT Support Plan development for an upcoming operation. Administrative work: AR 381-102 review cycle check, access roster updates, correspondence with HRC Warrant Officer Branch on any career management item.
  • 1530-1630G2X or MI Battalion staff coordination: collection update brief to the S2, deconfliction coordination with the CI element if there are overlapping operational interests, sync with the 35F intelligence analysts who are the downstream customers of your IIRs.
  • 1630-1700End-of-day file security: safe secured, classified material properly stored, SCIF access log complete, no classified remaining on open desktops. In a shared SCIF this is the daily ritual that keeps the program legally clean.
  • 1700-1800Administrative catch-up that doesn't happen inside the SCIF — HRC correspondence, unit leave roster, upcoming school coordination with the MI Battalion S1 if you are approaching the HUMINT Warrant Advanced Course application window.
  • 1700-onwardGarrison end of duty day. In a deployed or high-tempo environment the SCIF stays open and you stay with the work until the operation is done.

Weekly Cadence

Monday is the collection planning day — the G2X weekly ICR cycle drops new or updated collection requirements, and the start of the week is when you map your assets and scheduled meetings against the priority intelligence requirements for the week. By Tuesday afternoon you should have a clear picture of what collection is scheduled, what gaps exist, and what's going to require a new source approach or a coordination call to a higher echelon. Mid-week is typically the heaviest IIR production block — source meetings that happened over the weekend or early in the week generate debriefing notes that need to become IIRs before the collection value goes cold. The IIR that comes out of a Tuesday debriefing and hits the grader on Friday is worth significantly more than the same report submitted the following Monday. Freshness of reporting is a real factor in how commanders use intelligence. Friday is program health day — source file review, validation cycle status, any CI referrals that need to be in the queue before the weekend. In garrison units, Friday afternoon often generates the administrative work (counselings, leave approvals, Soldier Readiness Processing if the unit is in a deployment cycle) that doesn't happen when the week is full. The warrant who stays current on his administrative files during the week doesn't lose Friday afternoon to them.

Key Skills — How to Drill Each

  1. 01
    Assess, validate, and document a HUMINT source to FM 2-22.3 and ATP 2-22.3 standards.
    Run the validation interview as a structured conversation with a specific sequence: access first (what does this person actually have access to, not what do they claim), then motivation (why are they talking, and is that motivation stable), then reliability history (what have they provided before and how did it check out), then security risk (what indicators make this person a CI concern). Document every assessment in the source file immediately after the meeting — not the next day. The validation interview is the legal and operational foundation; anything you do with that source afterward rests on it.
  2. 02
    Conduct a structured debriefing that produces an IIR graded HUMINT Report without leading the subject.
    The IIR grade is your operational report card. Practice free recall first — ask the source what happened, what they observed, what they heard, without steering. Only after free recall do you follow up with targeted questions against your collection requirements. The errors that tank IIR grades are almost always traceable to the debriefing technique: compound questions that blend the source's answer with your assumptions, or leading questions that get the source agreeing with your framework rather than reporting their own. ATP 2-22.3 Appendix C has the structured questioning matrix — run it honestly.
  3. 03
    Write a HUMINT Support Plan that maps collection assets to priority intelligence requirements.
    The HUMINT Support Plan is the document that shows the G2X you can think at the operations level, not just the collection level. Start with the unit's PIRs. Map each PIR to the sources with plausible access. Identify which PIRs have no plausible HUMINT collection avenue — that gap analysis is as important as the tasking plan, because it tells the commander where he needs different collection means. Brief the plan before executing it; a HUMINT Support Plan that changes mid-collection because you didn't think through the access problem before the first meeting is a plan that wasn't actually a plan.
  4. 04
    Manage the controlled-source file system under AR 381-10 and AR 381-102 with zero administrative misses.
    Build the file management habit from day one of the assignment: every meeting gets a contact report, every validation review gets dated and signed, every counterintelligence referral gets logged. The AR 381-102 validation review cycle has specific timelines by source category — calendar them out when you assume the program. The MI Battalion's next IG inspection will find whatever you didn't calendar. Source files that are administratively complete are also operationally defensible; files with gaps are liabilities that get programs suspended.
  5. 05
    Brief the supported commander on HUMINT collection results with appropriate confidence caveats.
    The brief that earns commander trust names the IIR grade, the source reliability history, and the corroboration status — every time, without being asked. 'My source reported X' is the opening sentence; 'here is what we know about the reliability of that report and what would confirm it' is the closing one. Commanders who receive HUMINT reporting without confidence framing make decisions on intelligence that is softer than they think it is. The HUMINT warrant who names the limits of his own reporting is the one the G2 eventually calls first.

Manuals & References — What Chapters Matter

  • FM 2-22.3 — Human Intelligence Collector Operations
    Chapter 8 (Source Operations) and Chapter 9 (Debriefing) are the two you will return to most. Chapter 8 establishes the source development cycle — spotting, assessing, developing, recruiting, handling — and the legal boundaries around each phase. Chapter 9 describes the structured debriefing approach that the IIR graders are evaluating your output against. Read them before your first operation and after your first bad IIR grade.
  • ATP 2-22.3 — Human Intelligence Collector Operations Techniques
    The technical companion to FM 2-22.3. Appendix B (Site Exploitation) and Appendix C (Questioning Techniques) are the operational specifics the field manual leaves at a high level. If you're planning a DOCEX support mission or a follow-on questioning sequence after a search operation, ATP 2-22.3 is the how.
  • AR 381-10 — U.S. Army Intelligence Activities
    Table 3-1 is the one you need to know without looking it up: collection techniques, approval authorities, required echelons, and legal limitations. Every HUMINT collection activity you plan maps to one of those technique categories and one of those approval echelons. The operations that create IG findings are almost always ones where the warrant believed the activity fell under a lesser authority.
  • AR 381-102 — U.S. Army Human Intelligence Collection Programs
    Source registration, validation cycles, and program management requirements. The procedural guide for what goes in the file, when it gets reviewed, and who approves each step. Your source file management system should be built directly from this regulation.
  • ICD 304 — Human Intelligence
    The Intelligence Community directive that governs HUMINT standards across all IC components. In joint or interagency environments — working alongside DIA, CIA, or FBI HIG elements — this is the shared framework. Knowing how Army HUMINT collection connects to and is bounded by IC-level standards is what lets you coordinate instead of conflict in those environments.

Standards — How to Hit Each

  • TS/SCI clearance adjudicated and current with no CI referral, lifestyle polygraph lapse, or access-affecting adverse information.
    Report foreign contacts, financial changes, and personal conduct issues to your security manager promptly — not when the periodic reinvestigation lands. The 351M who self-reports a foreign contact gets a review. The 351M who doesn't and the issue surfaces in the SSBI reinvestigation gets a suspension. The clearance is the MOS; treat access decisions accordingly.
  • HUMINT Warrant Officer Basic Course graduate (Fort Huachuca, MI School).
    The course covers doctrine, law, collection techniques, source operations, and IIR production. Treat it as the floor, not the ceiling. The warrants who do best at first unit are the ones who read FM 2-22.3 and ATP 2-22.3 during the course not just to pass tests but to map the doctrine onto operational scenarios. The scenarios become real fast.
  • IIR production record with grades that trend toward reliability — source grade 1-3 and information grade 1-3 on the majority of reports.
    The grade comes from the DIA station or J2X reviewer, not from you — but you influence it through technique. Validate sources properly, conduct structured debriefings, write the confidence level into the report honestly, and don't attribute to the source what you actually inferred from the context. The IIR that comes back graded low is a training event; the warrant who studies the grade feedback and adjusts technique improves. The one who blames the grader doesn't.

Technical Mistakes — Concrete Consequences

  • Running a source operation that outpaces your legal authority under AR 381-10.
    An operation executed at the wrong approval authority level is an unauthorized intelligence activity. AR 381-10 requires reporting of those to DAIG. The G2X gets involved, the MI Battalion commander gets a phone call, and the warrant who planned it writes the adverse finding report. This is not a career speed bump — it is a career stopper at WO1/CW2.
  • Filing IIRs before the source validation interview is complete and documented.
    The program appears to be producing when the foundation is missing. The IG audit that finds IIRs without corresponding validation files triggers a program review, and the warrants who submitted those reports are the ones who explain the gap in writing. The collection record means nothing if the program can't survive review.
  • Briefing a single-source, uncorroborated HUMINT report to a commander as a confirmed finding.
    The commander makes a decision — potentially a targeting, a patrol route, a resource commitment — on intelligence confidence he doesn't understand. When the decision proves wrong, the HUMINT warrant who called it certain is the one the G2 remembers. Name the confidence level every time.
  • Source identity information placed in a product that goes outside the controlled distribution channel.
    Once a source identity is outside the controlled channel, you cannot control where it goes. Source compromise can mean loss of collection, legal exposure for the Army, and physical danger for the source. The review process for a source compromise investigation is thorough, and it traces back to who handled the file. The 'it was an inadvertent email mistake' explanation does not make the investigation go away.

Career Decisions at This Rank

  • INSCOM operational billet vs. divisional MI Battalion — which sharpens the warrant faster?
    INSCOM units (66th MIB in Europe, 470th MIB at JBLM, 500th MIB in Hawaii/Pacific, 513th MIB at Fort Huachuca) tend to run more varied and higher-stakes HUMINT collection programs than a divisional MI Battalion. The collection access is often broader, the interagency coordination more routine, and the operational tempo more consistently demanding. The divisional MI Battalion gives you the supported-commander relationship that INSCOM units sometimes lack — your collection directly feeds a commander you know by face. Both are legitimate; the right answer depends on whether you want to maximize collection breadth (INSCOM) or develop the advisor-to-commander relationship (division MI Bn) earlier in the warrant career.
  • HUMINT Advanced Course now or after another operational assignment?
    The HUMINT Warrant Advanced Course at Fort Huachuca is the credential that opens the collection management and program oversight billets at CW3. If you're approaching the CW3 window, the Advanced Course is the next required step — plan it before the board rather than after. The warrants who go to the Advanced Course having already run a full collection program at WO1/CW2 get significantly more out of the instruction; the concepts that were abstract during the Basic Course have field experience attached to them now.
  • Joint or interagency billet (DIA element, CIA coordination, FBI HIG) — worth the assignment disruption?
    Joint and interagency exposure is the career differentiator that operational HUMINT assignments inside Army MI alone don't provide. Working alongside DIA theater elements, CIA officers in deployed environments, or FBI HIG in detention operations adds the IC framework and the deconfliction skillset that makes a CW3 or CW4 warrant genuinely useful in the senior billets — Theater MI Brigade HUMINT chief, INSCOM collection management officer, JISE HUMINT element. The assignment disruption is real; so is the long-term career value. The warrants who get considered for the top HUMINT warrant positions in the Army have almost all had IC integration time.
  • Stay in operational HUMINT or move toward warrant instructor / doctrine roles at Fort Huachuca?
    MI School instructor tours at Fort Huachuca are how HUMINT doctrine gets written and how the next generation of 351Ms gets trained. The warrants who go to instructor tours as CW3 or CW4 shape the HUMINT Warrant Basic and Advanced Courses, sometimes contribute to FM and ATP revision cycles, and build a professional network across the HUMINT community. The operational warrant who never instructs sometimes finds himself working for a program shaped by warrants with less operational experience than he has. Both paths produce CW5s — the institutional path shapes the MOS more durably.

How the Seat Varies by Unit Type

  • Divisional MI Battalion (G2X HUMINT Element)
    You are the direct HUMINT support to a maneuver commander — division or brigade — and the proximity is both the value and the pressure. The commander knows your name, knows your collection schedule, and will ask questions in the TOC that you need to answer without a script. The operational relationship with the supported unit is close; the collection program often has to adapt to the maneuver unit's operational tempo rather than the other way around. The training environment (NTC, JRTC) is where the program gets stress-tested in garrison before it deploys for real.
  • INSCOM MI Brigade (Theater HUMINT Element)
    The collection programs are more complex, the access more varied, and the interagency coordination more routine. You will work across a larger geographic area of responsibility, often without the close supported-commander relationship of a divisional assignment. The administrative and compliance demands are higher because the program operates at a higher visibility level — MSC-level program reviews, more frequent coordination with national-level consumers, and potentially direct interface with DIA and CIA theater elements. The HUMINT warrant who gets good at INSCOM becomes the model for theater-level collection management.
  • Special Operations Support (SOF MI Element, JSOC-Adjacent)
    HUMINT collection in support of SOF operations is compressed in timeline and elevated in consequence. Source meetings happen faster, IIRs need to be useful within hours not days, and the operational security requirements around source identity are more rigorous than in conventional environments because the consequences of source compromise in SOF operations are potentially lethal. Access to this work requires specific unit assignments — the 528th Sustainment Brigade G2, JSOTF intelligence cells, or direct support assignments — and the evaluation bar is higher. The 351Ms who go this direction early are usually ones with a strong operational record and a sponsoring senior warrant.
  • Reserve Component MI Unit
    Reserve 351Ms run programs that are continuous with Active Component doctrine but operate under different resource and tempo constraints. Weekend drill cycles compress the collection management and administrative work that an Active Component warrant does daily. The strengths: Reserve 351Ms often bring civilian-sector expertise (law enforcement, federal agency backgrounds, language skills) that augments the collection program in specific collection niches. The challenge: maintaining source file currency and training certification on a part-time schedule requires more self-directed discipline than the full-time operational environment.

What Good Looks Like at This Rank

The high-performing WO1 or CW2 HUMINT warrant has a source file that survives the next MI Battalion IG inspection without a finding — every source validation current, every contact report filed, every counterintelligence referral documented. The G2X can pull his program folder on any day of the year and brief the MSC commander on the program status without a single 'we need to check on that.' His IIRs are clean on the first submission — structured debriefings, honest confidence framing, no leading of sources. The DIA or J2X grader sees a warrant who knows the difference between what a source told him and what he inferred from the conversation, and the grade reflects it. He doesn't over-represent his collection program to the supported commander; he builds the commander's understanding of what HUMINT can and cannot access, and the commander's trust grows because the warrant's limitations are always as accurate as his reporting. By the end of the CW2 window the well-performing warrant is the one the MI Battalion S2 sends to the G2X coordination meeting without a minder, and the division G2 has started asking if he's available for the next rotation.

Preview — The Next Rank

CW3 is when the collection floor becomes the collection management floor. You are no longer primarily a collector — you are the warrant who is responsible for whether the collection program as a whole is producing, legal, and properly managed. The WO1s and CW2s in your section are now your responsibility, and their IIR quality grades and AR 381-102 compliance posture are your grade. The senior warrant territory — CW3 through CW5 — is also where the advisory function expands from the MI Battalion level to the G2, the division commander's staff, and joint environments. You will be in rooms with people making significant decisions based in part on what your collection program reports, and the communication skill that separates the effective senior warrant from the technically proficient one is the ability to give decision-makers an honest picture of collection confidence and collection limits — not just collection outputs. Start now: document your source programs thoroughly enough that a CW3 could pick them up and run them without a handover conversation, develop the junior warrants in your section as if their success is your evaluation metric, and build the G2X relationship that lets you tell a collection truth to a colonel who doesn't want to hear it.
FAQ

351M WO1-CW2 — Frequently Asked Questions

Q01What does a WO1-CW2 351M (Human Intelligence Collection Technician) actually do?
You are fresh out of the HUMINT Warrant Officer Basic Course at Fort Huachuca and slated into a Military Intelligence Battalion, an INSCOM unit, a division G2X, or a Theater MI Brigade HUMINT cell.
Q02What's the most important thing to know as a WO1-CW2 351M?
WO1 to CW2 is the window where you prove the warrant bar on your collar isn't just a promotion from 35M — it's a different kind of accountability.
Q03What does a typical day look like for a WO1-CW2 351M?
Time-blocked day at the WO1-CW2 351M rank tier: 0530-0630 PT with the MI Battalion or individual PT — warrant officers in MI units typically train with the battalion staff or their section, not with an infantry company. Garrison default, 0630-0730 Shower, breakfast, commute or transit to SCIF. Badging in, safe-opening, terminal log-on. Read overnight traffic: any IIR responses or grader feedback from the DIA station, any new ICRs from the G2X, any changed security status from the unit security manager, 0730-0830 Section stand-up or G2X coordination call — collection status,…
Q04What mistakes get WO1-CW2 351M soldiers fired or relieved?
Running a collection technique that requires a higher approval authority than you have without getting written approval first. AR 381-10 Table 3-1 is explicit about which techniques need what echelon authority. 'We were deployed and the timeline was short' is the line investigators hear most often; Filing an IIR on a source who hasn't been formally validated. The report grades mean nothing if the source baseline isn't documented.…
Q05What career decisions matter most at the WO1-CW2 351M rank tier?
INSCOM operational billet vs. divisional MI Battalion — which sharpens the warrant faster? — INSCOM units (66th MIB in Europe, 470th MIB at JBLM, 500th MIB in Hawaii/Pacific, 513th MIB at Fort Huachuca) tend to run more varied and higher-stakes HUMINT collection programs than a divisional MI Battalion. The collection access is often broader, the interagency coordination more routine, and the operational tempo more consistently demanding.…
Q06What's next after WO1-CW2 for a 351M (Human Intelligence Collection Technician) in the Army?
CW3 is when the collection floor becomes the collection management floor.
Q07What manuals and regulations does a WO1-CW2 351M need to know cold?
FM 2-22.3 — Human Intelligence Collector Operations (the source doctrine for every collection technique, reporting standard, and legal boundary you work inside).; ATP 2-22.3 — Human Intelligence Collector Operations Techniques (the technical companion — interrogation, debriefing, source operations, DOCEX procedures, HUMINT support planning).; AR 381-10 — U.S. Army Intelligence Activities (the legal authority framework; every collection operation you run is grounded here).

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