Intelligence Specialist

A Dam Neck grad learning to turn raw intelligence into something a commander can use.

You are in "A" school or freshly graduated, learning the tradecraft that underpins every intelligence product the Navy produces. At FLETRACEN Virginia Beach (NIOC Dam Neck) you drill the all-source analysis process, learn to write Intelligence Information Reports (IIRs), navigate JWICS, SIPRNet, and NIPRNet, and get familiar with DIA and NGA product standards. At your first command you stand watch in the intelligence department, process incoming traffic, file and track Requests for Information (RFIs), and start building the institutional knowledge of your ship's or squadron's Area of Responsibility. Nobody trusts a brand-new analyst to brief the CO. You earn that by getting every detail right at the working level first.

• 01JWICS, SIPRNet, and NIPRNet navigation and account management
• 02All-source analysis process — collection, processing, exploitation, dissemination
• 03IIR writing and intelligence reporting standards (OPNAVINST 3811.1)
• 04DIA and NGA product types and how to read them
• 05COMSEC and classified handling — need-to-know, need-to-share, classification marking
• 06Watch standing and intelligence department file management

• —OPNAVINST 3811.1 — Naval Intelligence
• —DIA DI 6000 series — Intelligence production standards
• —SECNAVINST 5510.36 — Security requirements
• —ICD 206 — Sourcing requirements for disseminated analytic products

• —Maintain TS/SCI clearance with full-scope polygraph — any lapse stops your career cold
• —Process all incoming intelligence traffic within watch shift; nothing sits unlogged
• —All IIRs and intelligence products marked correctly per IC marking standards before leaving the division
• —COMSEC violations are career-ending — handle classified material like it matters every single time

• —Filing an incoming intelligence report without flagging it to the watch officer because you assumed someone else already saw it — the report that falls through the cracks is always the one that mattered.

You show up to watch already familiar with the overnight traffic. You know the difference between a SIGINT report and a finished product, and you don't treat them as equivalent. When you write your first IIR, it goes through two rewrites before you're satisfied with the sourcing attribution. You ask questions — not to look smart, but because you genuinely want to understand why the commander needs this specific piece of information by this specific time. Senior IS sailors notice analysts who think about the customer, not just the data.

A qualified analyst in the intelligence division, owning production and keeping the daily brief honest.

You are a working analyst in a carrier strike group N2, a ship's intelligence department, an aviation squadron, or a shore intelligence command. You prepare the Commanding Officer's Intelligence Brief (COIB) — the single most visible product your division produces — and you are responsible for its accuracy, timeliness, and analytical integrity. You process intelligence requirements, support targeting, track maritime order of battle updates for your AOR, and respond to RFIs from the command. You may support HUMINT collection debriefs or SIGINT exploitation depending on your billet. You are also the person who briefs junior IS sailors on tradecraft standards. The officer N2 is the department head, but you are the one who actually knows where everything is and how it was produced.

• 01COIB preparation and presentation — briefing the CO with zero errors
• 02All-source fusion — integrating HUMINT, SIGINT, IMINT, and OSINT into a coherent picture
• 03Targeting support — preparing nominations and supporting strike packages
• 04Maritime order of battle tracking and indications and warning analysis
• 05RFI processing and collection management coordination
• 06Mentoring IS3s on IIR writing and analytic standards

• —OPNAVINST 3811.1 — Naval Intelligence
• —ICD 203 — Analytic standards (confidence levels, source citations)
• —ICD 206 — Sourcing requirements
• —Fleet intelligence directives and strike group N2 SOPs
• —DIA Maritime Intelligence publications

• —COIB delivered on time with accurate order of battle, indications and warning updates, and sourced assessments
• —Every analytic product states confidence level and identifies key intelligence gaps
• —Targeting support products reviewed against ROE and law of armed conflict standards before leaving the division
• —All personnel handling classified materials supervised and accountable — no unsupervised IS3 access to SCI compartments they are not read into

• —Briefing the CO with an assessment presented as higher-confidence than the underlying sources warrant — because the picture looks clean and you didn't want to undercut the product with caveats. The commander acts on confidence you didn't actually have, and the gap in sourcing only surfaces after the decision is made.

The N2 can hand you an RFI at 0600 and trust that by 0900 you've worked every available system, flagged what you found, and written a product that leads with what we know, what we don't, and why the gap matters. Your COIB has never been caught with a stale order of battle entry. When junior analysts ask why you source everything to the primary report instead of secondary products, you explain it in terms they remember. You manage your own sea/shore rotation timeline so a clearance administrative hold never blindsides you or the command.

A senior analyst and section supervisor — the person the N2 officer relies on to make the intelligence division run.

You supervise IS2s and IS3s, own specific intelligence production programs — maritime order of battle for an AOR, an indications and warning watch for a specific threat — and advise the N2 officer on collection priorities and intelligence gaps. You are the institutional memory of the intelligence department. When a new N2 officer reports aboard, you spend the first two weeks making sure they understand the command's current intelligence picture, the established source relationships, and the production timelines that cannot slip. You are also the enlisted leader responsible for the professional development of your analysts — making sure they understand that every product they produce has a human decision on the other end of it. You may serve as the NCIS or DIA liaison coordinator, managing source reporting channels and coordinating sensitive collection activities.

• 01Intelligence production program ownership and quality control
• 02Collection management — writing requirements, coordinating with national and theater collection assets
• 03Indications and warning analysis for an assigned AOR
• 04Supervising and developing junior IS analysts
• 05N2 officer advisory — translating commander's intelligence requirements (PIRs) into actionable collection tasks
• 06Coordination with NCIS, DIA, and theater intelligence nodes

• —OPNAVINST 3811.1 — Naval Intelligence
• —ICD 203 and ICD 206 — Analytic and sourcing standards
• —SECNAVINST 5510.36 — Security policy
• —Fleet and CCMD intelligence directives (PACOM, EUCOM, CENTCOM intel annexes)
• —NAVADMIN and ALNAV messages on IS rating advancement and program requirements

• —Intelligence production programs documented, current, and reviewed quarterly
• —All IS2 and IS3 products reviewed for analytic standards compliance before dissemination
• —Commander's critical information requirements (CCIRs) and PIRs published and updated with each operational cycle
• —Clearance and polygraph renewal timelines tracked for every member of the division — no lapses
• —IS2 advancement and development plans written and reviewed semi-annually

• —Letting a production program drift because the threat is quiet — stopping the daily indications and warning update because nothing has changed in three weeks, then scrambling when the picture shifts overnight and the commander asks why the division didn't see it coming.

When the N2 officer is TAD, the division produces at the same standard. Your analysts know their analytic lines, understand the confidence language they are required to use, and don't pad assessments with false certainty. You've already war-gamed the next operational cycle's intelligence requirements and written the collection plan before the ops officer asks for it. Junior IS sailors in your division know exactly what they need to do to make E-6, because you told them six months ago and check in on it monthly.

The intelligence department's senior enlisted — the quality standard the N2 officer enforces through you.

You own the intelligence department or division at a ship, aviation squadron, or shore intelligence command. The N2 officer is your department head, but the production quality, analyst development, and daily operational integrity of the intelligence program belong to you. You advise the N2 on what the collection picture looks like, what gaps exist, and where the command is flying blind. You brief flag-level officers when required and represent the intelligence department in battle rhythm events. You manage the division's classified material accountability program, oversee compartmented program access, and ensure that every sensitive activity your department conducts is properly documented and reported through the right channels. You are also the chief who stands in front of junior sailors and explains why this work matters — why the standard is non-negotiable even at 0300 on a slow watch.

• 01Intelligence department management — production, personnel, and classified material accountability
• 02Flag-level intelligence briefing — preparing and presenting finished intelligence to O-6 and above
• 03Compartmented program management and access control
• 04Collection management at the command and strike group level
• 05Senior enlisted leadership — mentoring IS1s and managing advancement pipelines
• 06Liaison with theater and national intelligence agencies (DIA, NGA, NSA, CIA)

• —OPNAVINST 3811.1 — Naval Intelligence
• —SECNAVINST 5510.36 — Security and SCI management
• —ICD 203, 206 — Analytic and sourcing standards
• —Fleet intelligence SOPs and strike group N2 directives
• —CPO leadership doctrine — NWP 1-03.1 and fleet policy

• —Zero classified material accountability failures — every item logged, every access tracked
• —Briefings to commanding officers and flag officers sourced and confidence-leveled with zero ambiguity
• —Every IS1 and below in the department has a documented development plan
• —Compartmented program accesses reviewed and reported on schedule — no overdue reviews
• —Battle rhythm intelligence products delivered on time across every operational cycle

• —Allowing the intelligence department to become a service desk for the ops officer — processing requests without pushing back on poorly framed requirements, so the command never understands the difference between a specific answerable intelligence requirement and a vague wish list. Good intelligence starts with a good question; the ISC is the one who enforces that standard.

The N2 officer trusts you to run the department without supervision and tells their relief that. You have a working relationship with the DIA and NSA representatives at the theater level that gets your command's collection requirements prioritized. When an analyst writes a product that overreaches the source data, you catch it before it leaves the division — and you explain exactly why, in terms the analyst will remember. The command's intelligence program is considered among the top in the strike group, and the strike group N2 knows your name.

The senior intelligence enlisted advisor for a strike group, submarine force, or major shore command.

You advise the strike group N2 and the commodore on the health and capacity of the intelligence enterprise across the entire command — not just one ship's intelligence division, but every IS sailor and every intelligence program in the formation. You identify gaps in analytic coverage, flag when collection requirements are not being met, and push back when the command's intelligence requirements exceed the reachable capacity of available assets. You mentor ISCs across the formation, ensure production standards are consistent across commands, and represent the intelligence community's equities in battle group operational planning. You are also the person who coordinates with national intelligence agencies when the formation's requirements require elevation above the fleet level. Your word on the health of the intelligence enterprise carries weight at the commodore level.

• 01Strike group or submarine force intelligence enterprise oversight
• 02Collection management at the theater level — coordinating national and theater assets for formation requirements
• 03Senior leadership advisory — advising O-6 and O-7 officers on intelligence capacity and gaps
• 04Cross-command ISC mentorship and production standard enforcement
• 05National agency liaison — DIA, NGA, NSA coordination for elevated requirements
• 06Operational planning support — intelligence annex review and threat assessment for major operations

• —OPNAVINST 3811.1 — Naval Intelligence
• —Fleet and CCMD intelligence annexes and operational planning documents
• —ICD 203, 206 — IC-wide analytic and sourcing standards
• —SECNAVINST 5510.36 — SCI program management
• —Senior Enlisted Joint Professional Military Education (SEJPME) doctrine

• —Intelligence production standards consistent across all commands in the formation
• —Collection requirements from all commands aggregated and prioritized before submission to theater collection management
• —Every ISC in the formation has a development plan that targets the command master chief pipeline
• —Compartmented program oversight — all formation SCI programs reviewed and compliant
• —Operational intelligence annexes reviewed and accurate before each major exercise or deployment

• —Letting the strike group operate on a single-point-of-failure collection picture during high-tempo operations — not identifying that two ships' intelligence divisions are relying on the same source stream with no redundancy, so when access drops, the formation has a blind spot no one anticipated.

The commodore asks you what the intelligence enterprise can and cannot support before committing to an operational requirement — because you've trained the staff to ask that question early. ISCs across the formation call you before they have a problem, not after. You've identified two analysts in the formation who are exceptional and put them in front of NGA and DIA representatives during the last exercise because you know what's good for the community isn't just what's good for your command. The formation's intelligence program scores at the top of the fleet inspection cycle.

Fleet-level or OPNAV intelligence enterprise leader — the senior enlisted voice for Navy intelligence.

You serve as the Fleet Master Chief intelligence advisor, a senior enlisted leader at OPNAV, an OSD intelligence office, or a major joint command. You do not run a watch section. You shape the policy, training, manpower, and standards that every IS sailor in the Navy operates under. You advise flag officers on the enlisted intelligence workforce — what they can do, what they need, and where the system is failing them. You represent Navy IS equities in joint intelligence community forums, coordinate with senior enlisted advisors from DIA, NSA, and NGA, and provide input to the Intelligence Community's enlisted career development programs. When Congress or OSD proposes a change to how Navy tactical intelligence is organized, your analysis shapes the Navy's position. You also mentor the most talented ISCSs to prepare them for the small number of master chief billets the community has.

• 01Fleet or OPNAV intelligence enterprise policy and workforce management
• 02Flag officer advisory — advising CNO, fleet commanders, and combatant command J2s on IS workforce capacity
• 03Joint IC engagement — representing Navy IS equities in DIA, NSA, NGA, and ODNI forums
• 04IS rating health management — advancement rates, clearance pipeline, retention, billet alignment
• 05Senior leader development — identifying and developing the next generation of ISCSs and ISCMs
• 06Congressional and OSD intelligence policy engagement — providing the operational reality behind policy proposals

• —OPNAVINST 3811.1 — Naval Intelligence (owner-level)
• —ODNI IC directives — ICD 200 series (management and authorities)
• —SECDEF and SECNAV intelligence policy directives
• —CJCSI intelligence and joint doctrine publications
• —Congressional intelligence authorization act oversight

• —IS rating advancement and retention rates tracked and flagged to fleet leadership when trends indicate a pipeline problem
• —All ISCM billets filled by officers of the appropriate experience; no gaps in senior enlisted advisory coverage at fleet commands
• —Navy IS interests represented in every IC workforce policy reform — no change that affects IS sailors passes without the ISCM on record
• —Every ISCS with command master chief potential identified and in a deliberate development pipeline
• —The next National Intelligence Strategy's implications for tactical naval intelligence are assessed and briefed to the N2 staff before implementation

• —Allowing the IS clearance pipeline backlog to become a normalized "cost of doing business" — accepting chronic 18-month processing times as inevitable rather than pressing OSD and ODNI for systemic fixes, so the community quietly loses a generation of promising analysts who can't wait out the process.

Fleet commanders know your name and call you before submitting intelligence billet reform proposals — because the last time they didn't, the proposal had to be rewritten. The IS rating's advancement rates are the best they've been in a decade because you identified the broken training pipeline two years ago and fixed it. ISCS mentees you've developed are now running strike group intelligence enterprises, and they still call you. When the IC goes through a major reorganization, the Navy's tactical intelligence equities are protected because you were in the room during the drafting.