Human Intelligence Collection Technician

You are the collection technician the unit just pinned a bar on. You know the doctrine cold, you ran sources as an enlisted 35M, and now every new operation order hands you a requirement you own — but the senior warrant in the section is still the one commanders call first.

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. Your daily work is running and managing collection assets — HUMINT sources, liaison contacts, detainee and document exploitation requirements — against intelligence collection requirements (ICR) assigned to your element. You build and maintain the source registry, conduct source validation interviews, draft debriefings and interrogation reports to the IIR/HUMINT Report standard, and produce HUMINT support plans that feed the unit's collection strategy. In garrison you maintain the operations security posture around source identities under AR 381-10 and AR 381-102 requirements, write the collection annex inputs, and carry the administrative load (access rosters, controlled-source files, counterintelligence referrals) that keeps the program legally clean. On deployment or in a forward environment you are also advising the supported maneuver commander on what HUMINT can and cannot do for his priority intelligence requirements — and managing the expectations gap between what a lieutenant colonel wants to know and what a source can safely be asked.

• 01Assess, validate, and document a HUMINT source to FM 2-22.3 and ATP 2-22.3 standards — access, motivation, reliability history, production potential, and security risk — before the source files a single report.
• 02Conduct a structured elicitation or debriefing that produces an IIR graded HUMINT Report without coaching responses or leading the subject — the report grades are how you and your program are measured.
• 03Write a HUMINT Support Plan that maps collection assets to priority intelligence requirements, with tasking sequences, reporting timelines, and a gap analysis briefed to the G2X or MI Battalion S3.
• 04Manage the controlled-source file system under AR 381-10 and AR 381-102 — access logs, identity protection protocols, source validation review cycles — with zero administrative misses.
• 05Conduct a site exploitation or DOCEX follow-on questioning sequence in support of a cordon-and-search or SSE mission under ATP 2-22.3 Appendix B procedures.
• 06Brief the supported commander on HUMINT collection results: what was collected, what it means for current PIRs, and what collection gaps remain — in five slides or less and without classified specifics that shouldn't leave the SCIF.

• —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).
• —AR 381-102 — U.S. Army Human Intelligence Collection Programs (source registration, validation, and program management requirements).
• —ICD 304 — Human Intelligence (the Intelligence Community directive governing HUMINT standards across the IC — know how your Army program connects to the broader IC framework).
• —ADP 2-0 — Intelligence (the capstone doctrine; brief the commander in this language).

• —TS/SCI clearance adjudicated and current — no CI referral, no lifestyle polygraph lapse, no financial or foreign-contact issues that create access problems for the controlled-source environment.
• —HUMINT Warrant Officer Basic Course graduate (Fort Huachuca, MI School) — the entry credential that gates the assignment.
• —IIR/HUMINT Report production rate and quality grades tracked by the supporting DIA/J2X element — reports graded "2" (reliable source, probably true) or better are the operational floor.
• —Source file currency under AR 381-102 — validation reviews on cycle, no lapsed approvals, no missing counterintelligence referrals on derogatory assessments.
• —ACFT pass at the officer/warrant standard — HUMINT warrants are not exempt from the fitness requirement regardless of garrison assignment.

• —Running a source operation that outpaces your legal authority under AR 381-10. The approval chain for different collection activities has specific echelons and thresholds — skipping the G2X or the MSC legal advisor review puts the operation and your career in jeopardy.
• —Letting a source file IIRs before you have completed the validation interview and documented the access, motivation, and reliability assessment. The report grades later mean nothing if the baseline is undocumented.
• —Mixing HUMINT source identity information into a product that goes outside the controlled distribution channel. Source protection is not a form check — it is the operational continuity of the program.
• —Briefing a commander's PIR as "answered" when the HUMINT is single-source and uncorroborated. Single-source is a data point; it tells the commander "we have reporting" not "this is confirmed." Name the confidence level.
• —Failing to write the counterintelligence referral when a source contact raises CI indicators. AR 381-102 and the local SOP have the referral threshold — the CI special agent who reviews it will tell you if it's nothing. You do not get to make that call alone.

The solid WO1/CW2 HUMINT warrant has a clean source file for every asset he runs, produces IIRs that grade on the first submission, and never lets his G2X get surprised by a problem that should have been flagged two weeks earlier. The MI Battalion S2 and the supported commander both describe him the same way: "he knows exactly what his sources can do and he doesn't oversell it."

You are the HUMINT program. Commanders have stopped asking your rank because they know your name. You manage the collection architecture, advise at the O-6 and general-officer level, and develop the WO1s and CW2s who will carry the program forward — or fail it if you don't do your job.

At CW3 and above you have moved off the collection floor and onto the collection management level — or you are the senior collector in a unit where both seats are yours. In a Theater MI Brigade, an INSCOM production cell, or a division G2X, you are the HUMINT staff officer equivalent: you manage the collection requirements cycle from ICR to IIR, you coordinate cross-agency HUMINT production with DIA, CIA, and service MI partners, and you advise the G2 or MI Battalion commander on collection strategy, program health, and legal compliance posture. You brief general officers when the collection report has implications the O-6 cannot translate alone. You review and quality-control every IIR your WO1s and CW2s produce before it goes to the DIA station, and you write the analytical support requests when an IIR produces a thread that needs production exploitation. In a deployed joint environment you are often the senior HUMINT presence in the Joint Intelligence Support Element (JISE), coordinating with CIA DO components, the DIA theater element, and FBI HIG elements on deconfliction. You carry the administrative program management load: source registry currency, AR 381-10 compliance reviews, the Inspector General coordination for any adverse collection finding, and the HUMINT officer professional development pipeline for the junior warrants in your shop.

• 01Manage a theater-level or division HUMINT collection requirements cycle — prioritize ICRs against available assets, identify gaps, task collection, track IIR production, and feed the gap analysis back to the G2 collection manager weekly.
• 02Advise a general officer or senior commander on HUMINT program status and capability limitations in plain language — what the program can access, what the legal authorities permit, what the current threat to sources requires.
• 03Coordinate HUMINT deconfliction with IC partners (DIA theater element, CIA DO station, FBI HIG) in a joint or interagency environment — managing source boundary agreements and reporting channel assignments without burning relationships.
• 04Develop, mentor, and correct junior HUMINT warrants (WO1 to CW2) on source validation, IIR production quality, AR 381-10 / AR 381-102 compliance, and collection planning — their program problems become your program problems the moment you sign the review.
• 05Write or review a HUMINT Appendix to the Intelligence Annex (Annex B) of an OPORD — collection strategy, asset tasking matrix, reporting timeline, and legal authority citation — that survives the G3 read and the division SJA review.
• 06Conduct a program compliance review against AR 381-10 and AR 381-102 standards and brief the findings — including adverse findings — to the MI Battalion commander without softening the assessment.

• —FM 2-22.3 — Human Intelligence Collector Operations (still the program foundation — you are now also responsible for teaching it, not just applying it).
• —ATP 2-22.3 — Human Intelligence Collector Operations Techniques (the technical standard your junior warrants are graded against; you own the QC function).
• —AR 381-10 — U.S. Army Intelligence Activities (at this tier you are advising on legal authority sufficiency, not just compliance — know the approval thresholds by echelon).
• —AR 381-102 — U.S. Army Human Intelligence Collection Programs (program management; you are the accountable officer for the registry and the validation cycle).
• —ICD 304 — Human Intelligence (IC integration standard; in joint or interagency environments this governs the reporting and coordination framework above the Army lane).
• —ATP 2-91.8 — Supporting Human Intelligence Operations (the support-to-operations integration piece that connects HUMINT collection to targeting and assessments at the battalion and brigade level).

• —TS/SCI with polygraph (CI or Full Scope, as the billet requires) — at CW3 and above most joint or IC-adjacent billets gate on the poly; flag any adjudication lag to your chain immediately.
• —IIR program quality grade tracked across the shop — the DIA/J2X station grades IIRs; a senior warrant who cannot tell you his shop's rolling grade average is not managing the program.
• —AR 381-10 compliance review clean — no open adverse findings older than 90 days, no lapsed source validation approvals, no counterintelligence referral backlog.
• —HUMINT Warrant Advanced Course (Fort Huachuca, MI School) completed before CW3 billet assumption — the formal credential for the collection management and program oversight functions.
• —Recognized as the supporting commander's HUMINT advisor of record — the test is whether the G2 calls you first when a collection operation hits a legal ambiguity.

• —Allowing a junior warrant to run a source operation at a collection technique authority level he hasn't been delegated. AR 381-10 assigns approval authority by echelon and technique — the senior warrant's signature on the delegation paperwork is what makes the operation legal.
• —Carrying an unvalidated source on the registry past the revalidation cycle because the operational tempo made scheduling hard. The IG and the MSC G2X will not accept operational tempo as an explanation for a lapsed validation cycle.
• —Burying an adverse HUMINT finding — a source who may be doubling, a collection report that looks fabricated, a CI indicator that should have generated a referral — because the commander has equities in the program result. The report gets worse, not better, when you delay it.
• —Competing with IC partners (CIA DO, DIA theater, FBI HIG) for source access instead of deconflicting. Boundary agreements exist because source collisions damage both programs and occasionally the source. The senior warrant in the room coordinates; he does not territorialize.
• —Letting the HUMINT program's profile exceed its utility. A HUMINT cell that promises more than the legal authorities and available assets can deliver will eventually fail a commander publicly — and the senior warrant who did not manage those expectations is the one who signs the relief memo.

The CW4 or CW5 HUMINT warrant is the person the division G2 calls before the brief, not during it. His program is clean on paper and effective in production — the IIRs grade, the source registry is current, and the compliance posture survives the IG. He has developed at least two WO1s or CW2s who can run operations he is not in the room for, and the supported commander says "I trust what the HUMINT shop tells me" without being asked. When the joint or interagency deconfliction call gets hard, he is the Army voice in the room who does not have to read from a slide to explain what the program can and cannot do.