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 IS Intelligence Specialist — overview, pay, training, civilian translation, reviews
ISE4

Intelligence Specialist

E-4 (Specialist/Corporal) · Coast Guard

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

You are now a producing IS — a rated intelligence petty officer with a Dam Neck schoolhouse credential and a TS/SCI clearance that most of the people at your command do not hold. The gap between what the non-rate IS did and what the IS3 does is not incremental — it is the gap between handling other people's products and putting your own name on finished intelligence that goes to the Sector Commander's brief. ICD 203 analytic standards and ICD 206 sourcing requirements are not background concepts — they are the production standard your IS2 applies every time your name is on a product. Get there before the first review note, not after.

The Honest MOS Read
IS3 is the first production rank in the IS rating. You graduated from IS A-School at NAS Dam Neck (verify current school assignment against ALCGPSC) with the tradecraft vocabulary, the classification framework, the JWICS and SIPRNet operational procedures, and the basics of all-source analysis — and now you are back at a unit working under an IS2 who expects you to produce, not just process. The IS3 seat at a Sector intelligence element, a District Intelligence Branch, or a joint intelligence center billet is where the distance between A-school instruction and operational production becomes real. The products you produce at IS3 level are the foundational IS products: port security threat assessments, vessel-of-interest analysis packages, drug and migrant flow pattern summaries, counterterrorism threat products for Sector Commanders, and OSINT-anchored maritime intelligence reports that the IS2 reviews before they go anywhere. The ICD 203 standard — proper sourcing, appropriate analytic confidence language (the difference between 'likely,' 'probably,' 'assess,' and 'confirm' is not style preference, it is tradecraft), evidence-versus-assumption discipline, the 'so what' framing that makes the product useful to a commander — is applied every time you produce, and the IS2's product review comments are the primary training loop in this billet. The IS3 who treats review comments as correction rather than instruction grows into the IS2 seat. The IS3 who treats the same comments as criticism stays in the revision cycle longer than necessary. The systems you operate at IS3 level — JWICS, SIPRNet, the DHS Intelligence Enterprise dissemination platforms, the USCG Intelligence Dashboard (verify current platform designations with your IS1 or ISC) — require a discipline that extends beyond session procedures. Cross-domain protocol — what stays on JWICS, what can go to SIPRNet, what can go to NIPRNET — is not a procedural inconvenience, it is the classification boundary that keeps the IS section out of a spillage investigation. The IS3 who develops the cross-domain habit in the first production billet is the IS3 whose clearance is clean at the IS2 promotion board. The IS rating's maritime intelligence mission set is where your production work lives. JIATF South (the joint interagency task force for counter-narcotics in the Caribbean and Eastern Pacific, headquartered at Key West, FL) draws on Coast Guard intelligence products and employs Coast Guard IS members at the joint production level — the IS3 who understands JIATF South's mission and operational framework is ready for a joint billet request when it opens. The National Maritime Intelligence-Integration Office (NMIO) produces the national-level maritime domain awareness picture that the CG feeds into. The DHS Intelligence Enterprise connects CG intelligence output to CBP, ICE, TSA, and DHS I&A on shared maritime and border threat topics. These are the consumers your products reach — not just the Sector Commander's brief, but the broader DHS intelligence community that reads your section's output. The classified material accountability program at the IS3 level is yours to run when the IS2 directs it. This is not peripheral work — it is the evidentiary chain for the section's TS/SCI handling compliance, and the IS3 who runs the accountability log accurately and completely is the IS3 who gets the IS2's recommendation for independent production authority. Every SWE cycle, every EER period, every IS1 endorsement for the IS2 advancement slate reflects whether the IS3 who ran the accountability log kept it clean or created gaps. The IS2 Servicewide Exam bibliography is not a short list. The IS SWE covers rating-specific knowledge, IC-wide doctrine, military requirements, and leadership topics — and in a small community, the SWE cutting score is visible. Pull the current bibliography from the Coast Guard Institute the week you graduate from A-school, build the study schedule before your first EER period closes, and do not wait for the IS1 to ask you about it.
Career Arc
  • 01IS A-School graduation at NAS Dam Neck, VA area — rated IS3 at E-4.
  • 02First production billet — Sector intel element, DIB, or CGIS support; IS2 review of all products.
  • 03Classified material accountability program ownership under IS2 direction.
  • 04First ICD 203/206 production cycle — port security assessments, vessel-of-interest reports, maritime threat products.
  • 05JWICS and SIPRNet session management, DHS Intelligence Enterprise operational access.
  • 06Non-rate IS striker PQS supervision — first time your signature is on someone else's training record.
  • 07IS2 SWE bibliography pulled and study schedule built; first advancement cycle.
  • 08Joint billet request consideration — JIATF South, NMIO, or NSA billet if IS2 eligible.
Common Screwups
  • ×Producing an intelligence assessment that states a conclusion without sourcing it — 'The vessel is likely being used for drug trafficking' with no collection basis is an unsourced assertion, not analysis. The IS2 returns it for rewrite and the Sector Commander reads the version the IS2 submitted, not yours. ICD 203 is the standard; treating it as a writing style preference rather than a tradecraft requirement marks the analyst who is not ready for independent production authority.
  • ×Cross-domain violations — posting a product to a network at a classification level the underlying sources do not support, transferring a JWICS product to SIPRNet without proper sanitization and downgrade documentation, or leaving a classified session open when you step away from the terminal. These are not close calls; they are the events that trigger security investigations and clearance reviews in a small-community environment where every incident is visible.
  • ×Verbal-only product review corrections from the IS2, taken without written notes. The IS2's review comments are your primary tradecraft training loop at IS3 — if they are not documented in a way you can reference on the next product, you will reproduce the same error on the next draft. Take notes during the review session.
  • ×Letting the SWE bibliography slide because 'the IS community is small and the cutoff is usually reachable.' In a small community, one missed advancement cycle is one missed cycle — there is no depth of IS3 peers to average against. The current ALCGENL publishes the cutting score; pull it and compare it to your multiple before the exam, not after.
  • ×NJP, DUI, or financial mismanagement as a rated IS. The security manager writes the adverse action documentation the same day; the periodic reinvestigation catches financial deterioration in the continuous evaluation program. In the IS rating, a security concern that surfaces as a rated petty officer is not a recoverable career event the way it might be in a larger, clearance-light rating.

A Day in the Life

  • 0530Wake. Coffee. No classified system access before the SCIF or STE space opens. Review the overnight intelligence traffic summary if available on the section's unclassified read board.
  • 0545-0630Section morning muster. IS2 or IS1 briefs the daily intelligence tasking — incoming RFIs, product deadlines, any classified material actions from overnight. IS3 notes assignments for the day.
  • 0630-0730Unit PT with the command or IS section, depending on unit structure. At a Sector or DIB, the IS section may run PT as a separate element from the deck force.
  • 0730-0800Hygiene, uniform, breakfast. Colors at 0800 at commands with a formal colors formation.
  • 0800-1000SCIF/STE space open. Log in to JWICS and SIPRNet per unit session procedures. Clear the overnight classified message traffic queue — log receipts, verify distribution, route to IS1 or IS2 as required. Begin primary product tasking: open the day's port security or vessel-of-interest assessment, pull current source material from SIPRNet and JWICS, structure the outline.
  • 1000-1200Primary product drafting. Source research — JWICS pull of overnight SIGINT summary products, SIPRNet for current vessel movement data, OSINT (public maritime databases, USCG MSIB, DHS I&A unclassified products) for open-source contribution. Draft the product in the current IS production template; annotate sourcing in the margin as each claim is written, not in a cleanup pass after the fact.
  • 1200-1300Lunch. Out of the SCIF space — session locked, classified material accounted for and secured. Chow with the section.
  • 1300-1500Product completion and IS2 review submission. Final classification derivation check, ICD 203 confidence language review, ICD 206 source citation review. Submit to IS2 for review. While the IS2 is reviewing, run the PQS session with the non-rate striker — one item per day, formal demonstration, signature in the qual book.
  • 1500-1600IS2 product review return. Work through comments — this is the primary tradecraft training loop. Every comment gets a written note in a personal product review log (not in the classified system — a personal training notebook). Revise and resubmit if required.
  • 1600-1630End-of-day secure. Classified material accountability log — all actions from the day logged, receipts closed, transfers documented. JWICS and SIPRNet sessions properly terminated. SCIF / STE space secured per physical security procedures.
  • 1630Liberty call for off-duty section. Duty section covers evening classified traffic queue and physical security checks.
  • 1800-2100Personal time. SWE bibliography study — one chapter per evening on a consistent schedule. The IS SWE is not passable by cramming the week before the exam; the bibliography is too long and too doctrine-heavy. Physical fitness training.
  • 2200Lights out.
  • Surge tempo (RFI response day)When a major MLE operation or a JIATF South RFI lands, the product schedule collapses and the IS section operates as a watch rotation. The IS3 on the production watch works an 8-12 hour analytical production cycle — pulling collection, building the all-source picture, running the product through the IS2 review in real-time, and posting the finished product to the joint consumer on the same day. This is the operational reality the non-rate phase was supposed to prepare you for.

Weekly Cadence

The IS3's week is structured around the intelligence production cycle at the unit, not a maintenance schedule. Monday is the heaviest planning day: the IS1 or IS2 puts out the week's tasking — standing product requirements, incoming RFIs from the Sector Commander or District Commander, collection requirements that need OSINT support or JWICS follow-up, and any classified material accountability actions outstanding. The IS3's Monday production target is the initial draft of the week's primary product; the IS2 review happens before the product is disseminated, not after. Tuesday through Thursday is the production body of the week. Products move through the IS2 review cycle — draft, comments, revise, resubmit — and the IS3 learns the tradecraft through the review loop more than through any formal training event. The collection requirements process runs in parallel: the IS3 who manages the unit's OSINT contributions to the DHS Intelligence Enterprise or the JIATF South intelligence sharing channel is also the IS3 who understands where the gaps in the all-source picture are and which collection assets the CG can task versus which require a higher-level RFI. Wednesday or Thursday usually includes a joint coordination action — a product handoff to CGIS for intelligence-to-law-enforcement coordination, or a contribution to a District-level maritime threat product — that requires the IS3 to operate outside the section and apply the tradecraft under external review. Friday includes command-level administrative events and the EER documentation cycle. The IS3 who treats Friday's end-of-week as the SWE study session gets ahead of the bibliography without sacrificing the production week. The duty section over the weekend covers overnight classified traffic and physical security checks; the IS3 on duty maintains the accountability log through the weekend with the same standard as the weekday.

Key Skills — How to Drill Each

  1. 01
    Produce a port security or maritime threat assessment at the IS3 level — source-cited, properly classified, formatted to Coast Guard Intelligence Product Standards, reviewed by the IS2 before release.
    Before the first product leaves your hands, read two or three of the IS2's finished products in the same format and mark every source citation, every analytic confidence qualifier, and every classification derivation. Then write your first product in that format, annotating every line with your own derivation notes before you submit for review. The IS2 who reads a draft with clear sourcing and appropriate confidence language writes shorter review notes — and shorter review notes mean faster progression to independent production authority.
  2. 02
    Access JWICS and SIPRNet for collection requirements, incoming intelligence products, and finished intelligence dissemination — proper session security, no unauthorized cross-domain transfers.
    Print the unit's cross-domain protocol and keep it at your workstation for the first 90 days — not because you do not know the rules, but because the habit of checking before acting is what prevents the 3 PM mistake when you are tired and the product is due. Every session starts with a security check: right terminal, right network for this product, right classification level for the destination compartment, session locked when you step away. The IS2 who does not have to remind you of this stops watching you for it.
  3. 03
    Apply ICD 203 analytical standards — proper sourcing, appropriate analytic confidence language, evidence versus assumption discipline — on every product you produce or support.
    The six ICD 203 analytic standards (proper sourcing, analytic objectivity, independence of analysis, transparency of sources and methods, distinguishing information from assumptions, and presenting the 'so what') are not abstract principles — they are checklist items. Before submitting a product, run every paragraph against the standard: what is the source for this claim, is the confidence language accurate relative to the source quality, is this conclusion derived from evidence or from an assumption that I have stated as fact? The IS2 runs the same checklist on your draft; the IS3 who runs it first gets cleaner review notes.
  4. 04
    Maintain the section's classified material accountability log — receipt, storage, transfer, and destruction of classified material documented without gaps.
    The log is a real-time audit trail, not a retrospective record. Log every action at the moment it happens, not at end-of-day when the day's events are reconstructed from memory. The entry format is specific: date-time group, item description, classification level, action taken, person who performed the action, person who witnessed or authorized it (if required). The annual classified material inventory is when every gap in this log becomes visible; the IS3 who runs the log clean never has to explain a gap during the inventory.
  5. 05
    Operate the USCG intelligence dissemination tools at the IS3 access level — posting products to the right compartments, distributing to the right recipients, not posting above your classification authorization.
    Know your unit's approved dissemination list for each product type before you post a single product. The compartment structure for SCI material is not intuitive; the IS2 walks you through the first five postings and then expects you to run it. The authorized recipients list lives in the product standards documentation — do not post based on assumption. An over-disseminated product triggers a mandatory incident report; an under-disseminated product is a missed requirement. Both get the IS1's attention.
  6. 06
    Train the non-rate below you on PQS items and classified material handling — your signature on a non-rate's qual sheet is the first time your name is on a training accountability record.
    The first time you sign a non-rate's PQS item, you are certifying that you observed the non-rate perform the task to the standard. Read the task description before you observe the performance; sign after you have observed it, not after you have been told it was demonstrated. The IS1 will check the PQS books of the non-rates in the section during the EER cycle; the IS3 whose training records are signed accurately is the IS3 whose recommendation to the IS2 advancement board the IS1 can support without qualification.

Manuals & References — What Chapters Matter

  • COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual.
    Own every chapter at the IS3 level, not just the ones A-school covered. The classification management chapter, the collection management chapter, the product standards chapter, and the dissemination requirements chapter are the reference points your IS2 uses when reviewing your products. The version number matters — verify against the CG Directives System (dcms.uscg.mil).
  • ICD 203 — Analytical Standards, ODNI.
    The IC-wide analytic tradecraft standard your products are evaluated against. This is available unclassified at the ODNI website. Every IS3 who does not have this memorized before the first product review is the IS3 whose review notes say 'unsourced conclusion' and 'confidence language does not match source quality.' Read it before A-school graduation if you have not already.
  • ICD 206 — Sourcing Requirements for Disseminated Analytical Products, ODNI.
    The standard for how sources are cited and described in finished intelligence products. Every IS3 who does not know ICD 206 produces products the IS2 has to rewrite before dissemination. The source citation is not a footnote — it is the chain of evidence that connects your analytic conclusion to a verifiable collection artifact.
  • JP 2-01 — Joint and National Intelligence Support to Military Operations, JCS doctrine library.
    The joint doctrine for intelligence support in the operational environment the IS rating feeds into. The CG operates in joint intelligence environments (JIATF South, NMIO, and DHS multi-agency operations) where this is the shared operating framework. Read Chapter III (intelligence support to joint operations) before the first joint product handoff.
  • COMDTINST M1000-series — Personnel Manual, specifically the advancement chapter and EER sections.
    The Servicewide Examination process for IS2 advancement and the EER cycle that feeds the final multiple are both documented here. The IS community's small advancement pool means the SWE math is tight; the IS3 who pulls the current advancement criteria and models the multiple early understands what the IS2 advancement actually requires.
  • IS Rating Knowledge bibliography for the Servicewide Exam — current edition from the Coast Guard Institute.
    The IS SWE bibliography is IC-doctrine heavy — heavier than most enlisted CG rating bibliographies. Pull the current list from the Institute the week you graduate from A-school. The bibliography covers rating-specific doctrine, IC-wide ICDs, military requirements manuals, and leadership material. One year of consistent weekly study is how the IS3 arrives at the SWE window with a competitive multiple.

Standards — How to Hit Each

  • TS/SCI maintained with no incidents; periodic reinvestigation window tracked and self-reporting current.
    Track your periodic reinvestigation (PR) eligibility date from the day your initial adjudication finalizes. The PR cycle for TS/SCI is five years; the investigation opens before the prior adjudication expires. Keep a running record of every foreign contact, every foreign travel occurrence, every financial event that could surface in the PR — the security manager wants the file ready, not assembled from memory under deadline. Continuous evaluation (CE) under the federal personnel security framework means the adjudicator is not waiting for the PR cycle to see your financial picture; the CE program monitors it in near-real-time.
  • Qualified intelligence analyst or watch section contributor on the primary IS3-level product lane at your unit.
    The qualification is the IS2's formal determination that you can produce at the IS3 level without initial review — not that your products are reviewed, but that you can identify the right format, source appropriately, apply ICD 203 confidence language correctly, and post to the right distribution without being walked through it. The IS2 makes this determination based on observed production, not time-in-seat. Produce early and often; request review feedback actively; document the progression of your product quality.
  • IS2 SWE preparation in motion — bibliography pulled, study schedule built, rate training chapters worked.
    The IS community is small enough that a missed advancement cycle is visible to the ISC at your District. The current ALCGENL / CGPSC advancement message for IS2 publishes the cutting score and the examination date window — pull it before your first EER period closes, not the month before the exam. Three to four hours of weekly SWE study from A-school graduation to the exam window is the pace that builds a competitive multiple without destroying the operational routine.
  • EER blocks trending up; zero classified handling incidents or security violations on your record since IS3 designation.
    The EER is the IS community's promotion signal. In a small community, a flat EER trend is visible to the IS chief network and the District intelligence officer who writes the endorsement for the IS2 advancement slate. Every EER period, read your draft inputs with the IS2 before submission — not to negotiate the marks, but to confirm that the work you believe you did is the work that appears in the record.
  • Coast Guard PFT passed every cycle; weight and body composition compliant.
    The same standard as every other CG rate. In the intelligence billet environment, the physical fitness standard is less immediately operationally visible than in a boat crew rating — which means the IS3 who lets it slip is the IS3 the ISC notices. The PFT failure that surfaces during the clearance reinvestigation window is one more data point the adjudicator reads.

Technical Mistakes — Concrete Consequences

  • Producing an intelligence product that states a conclusion as fact without sourcing it — an unsourced assessment submitted to the IS2 as a finished product.
    The IS2 returns it for complete rewrite with comments that will appear in your training record. The Sector Commander does not read the version the IS2 sent back — the IS2 submitted a placeholder or a prior-cycle product instead. Two returned products in one quarter and the IS1 is watching your production quality, the ISC is asking the IS2 whether this IS3 is tracking toward independent production authority on schedule.
  • Cross-posting an intelligence product at a higher classification than the underlying sources support.
    This is an ICD 206 violation and a potential spillage event in the same action. The IS2 who finds the over-classified product before it leaves the section writes the correction; the IS2 who finds it after it reaches the consumer files the incident report. The incident report goes to the District security officer. The District security officer notifies the IS1 and the ISC. The IS3's clearance review opens.
  • Leaving a JWICS or SIPRNet session open and unattended when stepping away from the terminal.
    The classified network session policy is session lock on step-away — not a best practice, a requirement. The IS2 who finds an open session with your credentials is writing the security violation report that afternoon. In a small community, a security violation report is not an anonymous administrative event — it is a named finding in your EER record for that period.
  • Coasting on SWE preparation because 'the IS community is small and the cutoff is usually manageable.'
    In a small community, one missed advancement cycle is visible to the entire IS chief network at your District. The IS3 who misses IS2 advancement sits at IS3 for another full SWE cycle; the IS rating does not have the manpower depth for the Coast Guard to advance IS3s on board-and-fill vice competitive SWE. Pull the current cutting score from the ALCGENL before the exam window, not after.
  • Discussing current intelligence products, vessel-of-interest identities, or ongoing operational targets with unit personnel not cleared into the relevant compartment.
    Need-to-know is separate from clearance level — a SECRET clearance does not authorize access to every SECRET product, and a TS/SCI clearance does not authorize access to every compartment. The IS3 who shared a vessel-of-interest package with an uncleared BM officer conducting the boarding 'because he was the lead boarder' is the IS3 in the CGIS investigation. The need-to-know determination belongs to the IS1, not to the IS3's judgment in the field.

Career Decisions at This Rank

  • Request a joint intelligence center billet (JIATF South, NMIO, or NSA-adjacent) at the IS3 level versus staying at the first production billet through IS2 advancement.
    Joint billets at JIATF South in Key West or at NMIO are available to IS3s in the right window, and the exposure is professionally exceptional — you are producing alongside DIA, DEA, CBP, and NSA analysts on active maritime intelligence problems. The downside: the joint billet environment has higher product standards and less IS2 supervision, which means the IS3 who has not yet built independent production capability can struggle. The right timing for a joint billet is after the first IS2 product review cycle establishes your independent production authority at the IS3 level, not before. Talk to the IS1 about the timing; the ISC has specific views on which IS3s are ready for a joint billet versus which ones need another year of supervised production.
  • IS2 Servicewide Exam first attempt — competitive or conserve and retest.
    The IS SWE bibliography is long and the IS community is small. The IS3 who sits the exam without a study schedule built from A-school graduation is the IS3 who discovers on results day that the multiple was below the cutting score by three points. The SWE multiple includes the exam score, EER marks, performance evaluations, and time-in-rate factors — all of which the IS3 controls. Pull the current ALCGENL advancement message for IS2, model your multiple using the published formula, and decide whether the study schedule you have built is sufficient to produce a competitive score before committing to the exam window. Missing the cut costs a full SWE cycle in a small community where every missed advancement cycle is visible.
  • First reenlistment / EAOS decision — stay in the IS rating through IS2 and beyond, or separate at the IS3 level.
    The IS3 who exits the CG with a TS/SCI, a documented analytic production record, and ICD 203/206 tradecraft has post-service options that are genuinely strong: DHS I&A entry-level analyst, NMIO support contractor, federal GS-0132 (Intelligence Analyst) entry, cleared defense contractor positions (Leidos, Booz Allen, SAIC, CACI, Peraton, and others with maritime intelligence work). The IS3 who exits without advancing to IS2 and without a full production billet record has the clearance but a thin tradecraft portfolio — the civilian hiring interview will probe the analytical production experience, and 'I ran the classified accountability log and supported IS2 products' is a weaker answer than 'I was the primary IS3 analyst on the Sector Commander's port security assessment for 18 months.' Make the reenlistment decision knowing what the post-service market actually reads.
  • Pursue the SWE-competitive IS2 track versus lateral transfer to a broader platform rating.
    The IS rating is one of the most specialized and clearance-dependent ratings in the Coast Guard. If the nature of the work — closed, analytical, SCIF-resident, largely invisible to the operational community — does not match what you came in expecting, the IS3 advancement window is the honest decision point. A lateral transfer to OS (Operations Specialist), IT (Information Systems Technician), or another rating requires the ISC's endorsement and CGPSC approval — verify current lateral transfer availability — and is more achievable at IS3 than at IS2 after you have committed the clearance investment to the rating. If you love the analytical work, the intelligence community access, and the mission set, the IS3 SWE is the path; stay, study, and pin IS2 on schedule.

How the Seat Varies by Unit Type

  • Sector intelligence element
    The IS3 at a Sector works directly under one or two senior ISes on a production cycle tied directly to the Sector Commander's operational tempo. Products go to a named commander and get used in real MLE and port security operations — the feedback loop is short and the stakes are operational. The work is tactically focused, the clearance environment is well-established, and the IS2 review is hands-on. Smaller team means more accountability on every product and every classified material action.
  • District Intelligence Branch (DIB)
    The IS3 at a DIB works in a more substantial IS workforce — more ISes at multiple grades, longer-form products, higher-echelon consumers (District Commander level), and more formal product review standards. The tradecraft training environment is richer and the product exposure broader. The IS2 review is still present, but the bureaucratic product cycle is longer and the feedback loop less immediate than at a Sector. Good for building depth; less good for building operational urgency.
  • JIATF South (Key West, FL)
    The joint interagency task force for counter-narcotics in the Caribbean and Eastern Pacific. CG IS3 billets at JIATF South work alongside DIA, DEA, NSA, CBP, and other IC members on active counter-drug intelligence problems. The product standards are IC-level, the consumer is the joint operations cell running active interdiction operations, and the IS3 who performs well here becomes known outside the CG IS community. The IS3 who struggles here without supervision creates an external reputation problem in a community that does not forget.
  • NMIO (National Maritime Intelligence-Integration Office)
    NMIO integrates national-level maritime domain awareness from all IC contributors. A CG IS3 billet at NMIO works at the intersection of CG intelligence and the broader maritime IC community. The work is more analytical and less tactically operational than JIATF South; the consumer is the national-level picture, not the specific interdiction operation. NMIO exposure builds the broader IC awareness and the senior-level analytical tradecraft that accelerates the IS2 and IS1 career trajectory.
  • Coast Guard Investigative Service (CGIS) support billet
    The IS3 at a CGIS element is working intelligence-to-law-enforcement handoff, counterintelligence support, and criminal intelligence analysis rather than the maritime threat assessment production at a Sector or DIB. The product standard is chain-of-custody-ready and AUSA-readable; the analytic tradecraft serves the criminal case, not the commander's brief. The experience is directly applicable to post-service federal law enforcement intelligence roles.

What Good Looks Like at This Rank

The good IS3 is the petty officer the IS2 puts on the morning port security assessment because the product comes back sourced to ICD 206, assessed to ICD 203, classification derived correctly, and formatted in the standard the Sector Commander's watch officer can read without opening the style guide. It is not flashy. It is disciplined, and disciplined is the IS2's highest professional compliment at this level. The non-rates learn the classified accountability procedures by watching this IS3 run the log — not because the IS3 explains it at length, but because the actions are visible, deliberate, and consistent every single day. The log entry happens when the document is in hand, not at end-of-day. The JWICS session closes when the terminal is stepped away from, not when the IS2 mentions it. The classification derivation notation appears in the margin of the draft product, not only in the header of the final version. The habit is present before it is required. The SWE bibliography is not sitting on the desk — it is marked, sectioned, and on a weekly study rotation that was built before the first EER period closed. The IS1 does not have to ask about SWE preparation because the IS3 has already briefed the IS1 on the study schedule. The advancement cycle for IS2 is treated as a professional target with a plan, not an event that happens if the cutting score cooperates. When this IS3 departs the billet for a joint intelligence center assignment or the IS2 advancement slate, the IS1 is writing an endorsement from a record that reads as an analyst — not as a petty officer who processed intelligence products, but as one who produced them, improved under review, and left the section's classified accountability program cleaner than it arrived.

Preview — The Next Rank

IS2 (E-5) is the first time the IS rating expects you to operate independently and to review other people's work. At IS3, the IS2 reviewed yours. At IS2, you review the IS3's. The ICD 203 and ICD 206 standards you learned how to apply in your own products become the standards you apply to someone else's — and the IS3 who submitted for your review is learning tradecraft by reading your comments the way you learned by reading the IS2's comments on yours. The quality of your review is the quality of the IS3 who comes up behind you. At IS2, the production complexity increases: all-source assessments (not just OSINT-supported reports), collection requirements management through DHS and ODNI channels, intelligence-to-law-enforcement handoff coordination with CGIS, joint intelligence center billets that put you alongside DIA, NGA, and NSA analysts on active maritime problems. The ICD 208 collection management standard becomes operational, not just doctrinal. The Sector Commander's intelligence brief is yours to own, not to support. The SWE bibliography for IS1 starts the day you advance to IS2. The IS community's advancement math does not allow for rest cycles between grades — the IS2 who waits to build the study schedule until the IS1 SWE window opens is the IS2 who misses the IS1 cut in a small community that notices. The IS2 who builds the habit from IS3 advancement arrives at the IS1 SWE with a full bibliography complete and a competitive multiple already modeled.
FAQ

IS E4 — Frequently Asked Questions

Q01What does a E4 IS (Intelligence Specialist) actually do?
You came back from IS A-School at NAS Dam Neck with the IS rating badge and you reported to a Sector intelligence element, a District Intelligence Branch (DIB), an Area Intelligence Coordination Cell, CGIS, or a joint intelligence center on a Coast Guard billet as a working IS3.
Q02What's the most important thing to know as a E4 IS?
You are now a producing IS — a rated intelligence petty officer with a Dam Neck schoolhouse credential and a TS/SCI clearance that most of the people at your command do not hold.
Q03What does a typical day look like for a E4 IS?
Time-blocked day at the E4 IS rank tier: 0530 Wake. Coffee. No classified system access before the SCIF or STE space opens. Review the overnight intelligence traffic summary if available on the section's unclassified read board, 0545-0630 Section morning muster. IS2 or IS1 briefs the daily intelligence tasking — incoming RFIs, product deadlines, any classified material actions from overnight. IS3 notes assignments for the day, 0630-0730 Unit PT with the command or IS section, depending on unit structure. At a Sector or DIB, the IS section may run PT as a separate element from the deck force,…
Q04What mistakes get E4 IS soldiers fired or relieved?
Producing an intelligence assessment that states a conclusion without sourcing it — 'The vessel is likely being used for drug trafficking' with no collection basis is an unsourced assertion, not analysis. The IS2 returns it for rewrite and the Sector Commander reads the version the IS2 submitted, not yours. ICD 203 is the standard; treating it as a writing style preference rather than a tradecraft requirement marks the analyst who is not ready for independent production authority;…
Q05What career decisions matter most at the E4 IS rank tier?
Request a joint intelligence center billet (JIATF South, NMIO, or NSA-adjacent) at the IS3 level versus staying at the first production billet through IS2 advancement — Joint billets at JIATF South in Key West or at NMIO are available to IS3s in the right window, and the exposure is professionally exceptional — you are producing alongside DIA, DEA, CBP, and NSA analysts on active maritime intelligence problems. The downside: the joint billet environment has higher product standards and less IS2 supervision,…
Q06What's next after E4 for a IS (Intelligence Specialist) in the Coast Guard?
IS2 (E-5) is the first time the IS rating expects you to operate independently and to review other people's work.
Q07What manuals and regulations does a E4 IS need to know cold?
COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual; own every chapter at the IS3 level.; ICD 203 — Analytical Standards (the IC-wide analytic tradecraft standard your products are evaluated against — read it before your first finished product leaves the section).; ICD 206 — Sourcing Requirements for Disseminated Analytical Products (the standard for how sources are cited and described in finished intelligence;…

Based on 14 tips from 0 contributors

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