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
ISE5

Intelligence Specialist

E-5 (Sergeant) · Coast Guard

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

IS2 is the rank where the IS rating's standards become your responsibility to enforce, not just your obligation to meet. The IS3 below you is learning tradecraft by reading your product review comments; the Sector Commander's morning brief is built on analysis you produced, not analysis you supported. The ICD 203 and ICD 206 standards you applied to your own work at IS3 are now the standards you apply to someone else's work — and you are accountable for the quality that leaves the section under your name. In a small community with a long institutional memory, the IS2 whose product review is lax produces IS3s whose tradecraft is weak, and the IS community notices the pattern before the IS2 reaches IS1 advancement.

The Honest MOS Read
IS2 is the working analyst and technical backbone of the IS section. At the Sector intelligence element, you are typically the senior producing IS — the petty officer who owns the primary product lane, runs the classified material accountability program, reviews the IS3's work before it leaves the section, and provides the Sector Commander's morning intelligence brief. At the District Intelligence Branch (DIB), you are a mid-grade analyst working under an IS1 on longer-form District-level assessments, coordinating collection requirements, and developing the IS3s below you into independent producers. At a joint intelligence center — JIATF South, NMIO, or an NSA/DIA-adjacent CG billet — you are working alongside IC-level analysts on active maritime intelligence problems where the product standard is national-level and the consumer is an operational cell running real interdiction operations. The all-source assessment is the IS2's primary production mode. You integrate SIGINT summary products, IMINT reports from NGA (or partner-sourced imagery), HUMINT reporting from FBI or DHS I&A hand-off channels, OSINT from government and commercial maritime databases, and CG-organic collection (boarding team reports, vessel inspection findings, port security surveillance) into finished intelligence products that meet ICD 203 analytical standards and ICD 206 sourcing requirements on every disseminated product. You know the difference between a collection report and a finished intelligence product. You know when the evidence base supports a 'likely' assessment versus an 'assess' assessment versus a factual statement. You know which product formats go to which consumers on which networks. These are not things the IS2 is still learning — they are things the IS2 already knows and is teaching to the IS3. The DHS Intelligence Enterprise connects your section's products to the broader DHS intelligence community. The USCG Intelligence Dashboard (verify current platform designations with your IS1 or ISC) is the primary dissemination mechanism for CG intelligence products within the DHS network. JIATF South (headquartered at Key West, FL) is the joint interagency task force for counter-narcotics in the Caribbean and Eastern Pacific — the primary joint intelligence partnership the IS rating feeds directly and the joint billet environment where IS2s with strong production records are most likely to deploy. The National Maritime Intelligence-Integration Office (NMIO) integrates maritime domain awareness from the full IC contributor base. USCYBERCOM and NSA have CG IS billets in maritime intelligence contexts that represent both joint billet opportunities and post-service credential builders. The intelligence-to-law-enforcement handoff is a critical IS2 production function at units with CGIS coordination requirements. The sanitized reporting package, chain-of-custody-ready source documentation, and the product format the AUSA can receive without triggering a classified material handling issue are the IS2's responsibility — not the IS3's, not the IS1's unless the IS1 is writing the endorse. You coordinate the CGIS hand-off package, you verify that the classification and compartment markings on the sanitized version do not reveal source methods the case cannot afford to disclose, and you maintain the written coordination record because the AUSA will ask for it during discovery. The IS1 Servicewide Exam bibliography is long. The IS community advancement pool is small. The IS2 who treats the IS1 SWE as something to prepare for after the IS2 advancement is settled is the IS2 who misses the IS1 cut by two points in a community where missing the IS1 cut is visible to the District IS chief network. Build the study schedule from the IS2 advancement date and run it consistently — three to four hours weekly, structured against the IS Institute bibliography, modeled against the current published multiple formula — so that the IS1 SWE window is a confirmation of preparation, not a discovery of how much there is to study. The joint billet request — JIATF South, NMIO, NSA-adjacent, or DHS I&A — becomes realistic and strategically important at the IS2 level. The IS community's career progression rewards broadening assignments; the IS2 who goes directly from IS3 production billet to IS1 career track without a joint billet or a DIB rotation has a thinner record at the IS1 advancement board than the IS2 who brings joint intelligence center experience and IC-level production credentials. Talk to the ISC about the joint billet sequencing in the IS2 window before the IS1 SWE cycle comes up.
Career Arc
  • 01IS2 advancement via Servicewide Exam — first independent production authority and review responsibility.
  • 02Primary product lane ownership at Sector or DIB: port security threat assessments, drug/migrant flow analysis, counterterrorism products for Sector/District Commander.
  • 03IS3 product review and mentorship — tradecraft review comments, PQS supervision, EER input writing.
  • 04Collection requirements management through DHS and ODNI channels for identified intelligence gaps.
  • 05CGIS intelligence-to-law-enforcement handoff coordination — sanitized reporting packages, AUSA-ready documentation.
  • 06Joint intelligence center billet request or assignment — JIATF South, NMIO, or NSA/DIA-adjacent CG billet.
  • 07IS1 SWE bibliography study begins from IS2 advancement date; competitive multiple modeled early.
  • 08ISC (Chief Petty Officer) preparation conversation starts — EER trajectory, leadership C-school requirements per CGPSC, joint billet that fills the remaining record gap.
Common Screwups
  • ×Allowing a JWICS product's source references to be removed or generalized before handoff to the IS3 as a 'training simplification.' The IS3 learns ICD 206 sourcing discipline by working with fully sourced products; removing or generalizing the sources to make the product 'easier to work with' produces an analyst who cannot source independently. The IS2's job is to teach the tradecraft, not to protect the IS3 from its difficulty.
  • ×Submitting a maritime threat assessment that conflates open-source vessel movement data with a classified source report without distinguishing the two in the sourcing notation. A product that mixes classification levels without proper handling instructions is an ICD 206 violation and a potential spillage event — the IS1 who finds the error before dissemination writes the correction; the IS1 who finds it after the product reaches JIATF South writes the incident report.
  • ×Verbal product review corrections on the IS3 instead of written review notes that go into the training record. The ISC and the District intelligence officer read the EER and the training record to determine whether the IS2 is developing analysts. Verbal-only guidance is invisible at the board; the IS2 who coached the IS3 verbally but never documented it produced a training record that looks like the IS3 was never coached.
  • ×Skipping the written coordination record on a CGIS or joint partner intelligence handoff because 'we handled it verbally.' The AUSA reads every coordination document in the case file; a hand-off that exists only as a conversation does not exist in the case record. The CGIS case agent who has to reconstruct the coordination from memory at discovery is in the IS2's office the next morning asking for the documentation.
  • ×Missing the IS1 SWE window because the preparation plan started too late. The IS community is small and the IS2 who misses the IS1 SWE cut is visible to the District IS chief network and the CGPSC community manager. The correct preparation timeline is study-from-IS2-advancement; the correct planning tool is the current published IS1 advancement message with the multiple formula. Run the math early.

A Day in the Life

  • 0530Wake. Coffee. Review the CG intelligence summary or unclassified maritime traffic report if available — the morning section brief starts with a picture that was built overnight, and the IS2 who walked into the brief cold wastes the first 15 minutes of the IS1's production window.
  • 0545-0630Section morning brief. IS1 or ISC puts out the day's product tasking — standing requirements, incoming RFIs, any JIATF South or NMIO contributions due, any classified material accountability actions outstanding. IS2 confirms assignments and flags any resource gaps — missing collection, unresolved classification questions, IS3 production bandwidth.
  • 0630-0730Unit PT with the IS section or the command. At a District or joint billet, the PT schedule may be separate from a ship's deck force rhythm.
  • 0730-0800Hygiene, uniform, breakfast. Colors at 0800.
  • 0800-0900SCIF/STE open. Log in to JWICS and SIPRNet. Clear the overnight queue — incoming intelligence summaries, collection reports, RFI responses, and message traffic — log all receipts, route to IS1 as required. Flag any collection that feeds today's primary product.
  • 0900-1100Primary product drafting. All-source pull: SIGINT summary products from JWICS, IMINT reports from the overnight NGA feed, HUMINT reporting from DHS I&A or FBI pass-through on SIPRNet, OSINT from government maritime databases. Build the analytic line, source each claim in the margin annotation, apply ICD 203 confidence language. This is the production window — no meetings, no interruptions unless the IS1 calls in an RFI.
  • 1100-1130IS3 product review. The IS3 submits the draft port security assessment or vessel-of-interest report. IS2 runs the ICD 203/206 review: sourcing completeness, confidence language accuracy, classification derivation, format compliance. Write specific comments — not grades, training inputs. Return to IS3 with a deadline for the revised version.
  • 1130-1230Lunch. Out of the classified space. Chow with the section — the IS2 whose relationship with the IS1 and IS3s is built over lunch does not have to manage the afternoon's production issues in the SCIF.
  • 1230-1400Primary product completion and IS1 review submission. Final ICD 203/206 check, classification derivation block complete, product formatted for the designated consumer. Submit to IS1. While IS1 reviews, work the collection requirements pipeline — open requirements checked against incoming collection, new requirement drafted if a named gap has not been addressed.
  • 1400-1500IS3 revised product review. IS3 returns the port security assessment with revisions. IS2 checks whether the comments were addressed specifically — not whether the product is clean, but whether the IS3 fixed what the comment said to fix. If the revision is clean: approve for IS1 submission. If not: return with a tighter comment. The loop is training; the goal is that the third draft is not necessary.
  • 1500-1600Section administrative actions. EER input drafting for the IS3 if an EER period is closing. CGIS coordination documentation — if a hand-off package was worked this week, write the coordination record before liberty call, not the morning of the submission. Classified material accountability log end-of-day close — all actions logged, no gaps.
  • 1600-1630End-of-day secure. JWICS and SIPRNet sessions terminated. Classified material accounted for and secured. SCIF physical security check. Hand off to duty section.
  • 1630Liberty call for off-duty section.
  • 1800-2100Personal time. IS1 SWE bibliography study — one to two hours of structured chapter reading three nights per week. This is not optional; the IS community's SWE math rewards consistent preparation, not crammed preparation. Physical fitness training.
  • 2200Lights out.
  • RFI response surgeWhen JIATF South or the Sector Commander drops an RFI with a 4-hour turnaround, the day's production schedule collapses into a focused collection and drafting sprint. The IS2 runs the all-source pull, builds the analytic line under time pressure, and submits directly to the IS1 for expedited review. No PQS sessions, no SWE study, no administrative actions until the product is posted. This is the tempo the IS2 is being paid for — disciplined production under operational pressure.

Weekly Cadence

The IS2's week at a Sector or DIB is anchored to the intelligence production cycle — the standing product requirements that recur weekly (port security assessment, vessel-of-interest update, maritime domain awareness contribution), the RFIs that arrive on irregular rhythms from JIATF South or the Sector Commander, and the collection requirements process that runs in parallel to production. Monday is the planning day: the IS1 puts out the week's tasking, the IS2 maps the production schedule against the week's RFI timeline, and the IS3's product assignments are distributed based on the IS3's current production capability and the IS2's assessment of what requires review before dissemination. Tuesday through Thursday is the production body of the week. The all-source assessment drafts, the IS3 review loop, the collection requirements updates, and the CGIS coordination actions all run in these three days. The IS2 who manages the production schedule proactively — who knows on Monday morning which day each product is due and has the IS3's draft arriving two days before the dissemination deadline, not the morning of — is the IS2 whose products do not miss the Sector Commander's brief window. The IS1 who has to ask the IS2 on Thursday afternoon where the Friday product is has already learned something about how this IS2 manages the production floor. Friday is the administrative and training day. EER documentation actions, SWE study planning review, the IS1 coordination debrief on the week's products and the IS3's development trajectory. At joint billets like JIATF South, the weekly rhythm is tighter and more operationally driven — the joint operations cell does not have a 'slow Friday' concept when active counter-drug operations are running. The IS2 at a joint billet who is managing the administrative cycle from a deployed production environment learns to compress the administrative actions into the smaller windows that operational tempo allows.

Key Skills — How to Drill Each

  1. 01
    Produce an all-source maritime threat assessment using SIGINT, IMINT, HUMINT, and OSINT source products — source all claims per ICD 206, apply ICD 203 analytic confidence language correctly, deliver a product the Sector Commander can brief at his morning standup without the IS1 adding corrections.
    Before the final draft is submitted to the IS1 for dissemination authorization, run a two-pass check: first pass is ICD 206 sourcing — every claim mapped to a source artifact that is cited, dated, and at the correct classification level. Second pass is ICD 203 analytic language — every analytic judgment uses the appropriate confidence qualifier, no factual statements in analytic judgments, the 'so what' framing is explicit. The IS1 who reads the first-pass check notes in the margin knows the IS2 ran the standard before submitting. The IS1 who has to apply the standard during review is the IS1 who writes 'return for rework' on the cover sheet.
  2. 02
    Review and edit IS3 intelligence products for ICD 203 and ICD 206 compliance before release — identify unsourced conclusions, misapplied analytic language, and classification errors; return with comments specific enough that the IS3 knows exactly what to fix.
    The review comment is not a grade — it is a training input. Write 'unsourced conclusion — identify the SIGINT or HUMINT collection artifact that supports this assessment and cite it per ICD 206 format' instead of 'needs source.' Write 'confidence language does not match source quality — this OSINT contribution supports an 'assess' qualifier, not a confirmation' instead of 'wrong word.' The IS3 who reads the specific comment can fix the specific problem; the IS3 who reads the vague comment rewrites randomly and produces a product that has different problems than the original.
  3. 03
    Draft a collection requirement through the appropriate Coast Guard or DHS collection management process for a named intelligence gap affecting your Sector or District's operations.
    Know the difference between a collection request (asking a collection asset to acquire against a specific target) and a production request (asking a finished intelligence organization to produce a product). Know which gaps the CG's organic collection assets can address (boarding team reports, port security surveillance, SIPRNet holdings) and which require a collection management request through the DHS or ODNI framework. ICD 208 (verify current title and number against the ODNI Directives Library) governs collection requirements at the IC level — read the relevant chapters before drafting the first formal collection requirement.
  4. 04
    Coordinate an intelligence-to-law-enforcement handoff package with CGIS — sanitized reporting, chain-of-custody-ready sourcing documentation, and the product format the AUSA can receive without triggering a classified material handling issue.
    The CGIS hand-off package has two consumers: the case agent who runs the investigation and the AUSA who prosecutes the case. The case agent needs the actionable intelligence picture; the AUSA needs the chain-of-custody documentation that establishes how the intelligence was collected, by whom, under what legal authority, and what information was sanitized and why. Build the sanitized version first, then the coordination record, then the transmittal documentation. The written record is the hand-off — not the conversation.
  5. 05
    Operate JWICS and the DHS Intelligence Enterprise at the IS2 access level — post, retrieve, coordinate, and disseminate without cross-domain violations; train the IS3 on the discipline the system requires.
    When training the IS3 on JWICS or SIPRNet procedures, do not demonstrate with a real product in the production environment — use a training example or an archived product that can be handled as a training artifact. The IS3 who learns session security on a training product develops the habit before it costs anything. The IS3 who learns it on a real product by watching the IS2 make a live cross-domain call has learned by example, but the IS2 was already inside the operational risk envelope during the training.
  6. 06
    Write clean EER inputs on the IS3s and non-rates below you — observable behavior, measurable output, no inflation, no generic intelligence-community filler.
    The EER input is a professional record, not a performance trophy. Every bullet must be: specific behavior, specific product or action, specific outcome. 'Produced 23 maritime threat assessments meeting ICD 203/206 standards with zero IS1 rework' is a real bullet. 'Demonstrated outstanding analytic capability and professional excellence' is filler that the ISC discounts. Count the products. Name the training events you ran. Quantify the accountability actions. The ISC who reads the IS3's EER input will know whether the IS2 was watching or was filling squares.

Manuals & References — What Chapters Matter

  • COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual.
    You run the section's product compliance against this publication at IS2 level. Verify the current revision number against the CG Directives System (dcms.uscg.mil); the version number determines which classification management procedures and product standards are currently in force at your command.
  • ICD 203 — Analytical Standards; ICD 206 — Sourcing Requirements for Disseminated Analytical Products; ICD 208 — Collection Requirements (verify ICD 208 current title and number against the ODNI Directives Library, dni.gov).
    You apply all three on every finished product you produce or review. ICD 203 is the tradecraft standard; ICD 206 is the sourcing discipline; ICD 208 is the collection requirements framework you use when you draft a formal collection request. These are available unclassified at the ODNI website and are the IC-wide standards your joint consumers evaluate your products against.
  • JP 2-01 — Joint and National Intelligence Support to Military Operations, JCS doctrine library (jcs.mil/doctrine).
    For joint billet assignments — JIATF South, NMIO, NSA-adjacent CG billets — this is the shared operating framework. Chapter III (intelligence support to joint operations) and Chapter IV (intelligence functions in joint operations) are the reference points the DIA, DEA, CBP, and NSA analysts you work alongside use to frame the joint intelligence problem.
  • COMDTINST M5520.12 (current revision) — Coast Guard Counterintelligence Manual.
    CI reporting requirements at the IS2 level are more than awareness — you advise IS3s on what to report and how, and you brief the ISC on CI-relevant contacts or events in your section's operational environment. Verify the current publication number against the CG Directives System before quoting it.
  • COMDTINST M1000-series — Personnel Manual, specifically the EER sections and the Servicewide Exam advancement process for IS1.
    You write the bulk of inputs for IS3s and non-rates below you, and you read the IS1's draft of your own. The EER chapter explains how the marks, bullets, and narrative feed the final multiple. The advancement chapter governs the IS1 SWE process that your preparation plan is aimed at.
  • CIM 1610-series — Enlisted Employee Review (EER) system guidance.
    The specific formatting and scoring standards for the EER are in the CIM 1610-series. At IS2, you are writing EER inputs for IS3s and sometimes for non-rates; the EER you write is read by the ISC and the District intelligence officer when the IS3 sits the IS2 advancement board. Know the system well enough to use it precisely.

Standards — How to Hit Each

  • TS/SCI maintained; all periodic reinvestigation and continuous evaluation requirements met; zero incidents in your clearance history since IS3 designation.
    Track your PR eligibility date and brief the ISC before the investigator opens the case, not after. In the continuous evaluation framework, the adjudicator is monitoring financial, criminal, and foreign contact indicators between PR cycles — the IS2 who encounters a financial hardship, a foreign contact, or a foreign travel event immediately briefs the security manager and does not wait to see if it surfaces on its own. The IS2 clearance history feeds the IS1 advancement board through the security officer's certification; a deferred or suspended clearance during the IS1 SWE cycle is a board-disqualifying event in this community.
  • Primary intelligence product lane qualified at your unit; secondary qualification (collection management, CI reporting, or joint intel center watch position) in motion before the IS1 SWE.
    The primary production qualification is demonstrated through documented product quality — the IS1 can review your production history and confirm that your products meet ICD 203/206 standards without rework. The secondary qualification requires active pursuit: the collection management course through the DIA or the IC's collection management training program, the CI reporting brief from the CGIS field office, or the watch position qualification at a joint intelligence center if the billet supports it. The IS1 SWE bibliography includes collection management and CI as topic areas; the IS2 who has lived both areas produces better exam scores than one who studied them from the Institute materials alone.
  • EER marks at or near the top of the unit's IS2 cohort across multiple periods.
    In a small community, the IS2 EER cohort may be two or three people at a given command. The relative ranking of the cohort is visible in the EER mark, and the narrative bullets are read against each other by the ISC and the District intelligence officer when the IS2 advancement to IS1 is under consideration. Consistency across multiple periods is more valuable than a single high-mark period — the IS1 advancement board reads the trend, not the peak.
  • IS1 Servicewide Exam taken on cycle with a bibliography-driven study plan; current ALCGENL cutting score modeled against your projected multiple.
    The IS SWE multiple formula includes the examination score, EER marks, performance evaluations, and time-in-rate factors. Pull the current IS1 advancement message from CGPSC ALCGENL and run the formula against your current EER trajectory before the exam window opens. The IS2 who discovers on results day that the EER multiple was two points below the cutting score is the IS2 who regrets not running the math six months earlier.
  • PFT passed; body composition compliant; zero security violations.
    The security violation standard is absolute in this community — at IS2 level, a single violation triggers an IS1-level review by the ISC and the security officer and is documented in the clearance record that the IS1 advancement board sees. The physical fitness standard is the floor; the IS2 in a SCIF-based billet who lets fitness drift is the IS2 the ISC notices during the annual command inspection.

Technical Mistakes — Concrete Consequences

  • Allowing a JWICS product's source references to be removed or generalized when handing off to the IS3 as a training product.
    The IS3 who works a de-sourced product produces an IS3 whose ICD 206 habit never develops. When this IS3 sits down to source an independent product, the sourcing framework is not automatic because the training products were never fully sourced. The IS1 who reads the IS3's first independent product and finds unsourced conclusions is asking the IS2 whether the IS3 was actually trained or whether the IS2 was protecting the IS3 from the work.
  • Submitting a maritime threat assessment that conflates open-source and classified source material in the same sourcing notation without proper classification derivation.
    The ICD 206 sourcing requirement distinguishes source types and classification levels in the derivation notation for exactly this reason — a product that mixes OSINT and TS/SCI collection without distinguishing them is a spillage vector when the product is disseminated to a consumer who holds OSINT-accessible information but not the SCI compartment. The IS1 who finds the conflation before dissemination corrects it; the IS1 who finds it after the product reaches a lower-cleared consumer files the incident report. In a small community, the incident report is a named finding.
  • Giving verbal product review corrections on the IS3 without writing the comments into a training record entry.
    At the IS2 advancement board for the IS3, the ISC reads the EER inputs and the training record to determine whether the IS2 developed the analyst. A training record with no documented review comments and a verbal 'yeah, I coached him' from the IS2 is not evidence of development — it is the absence of evidence. The IS2 who coached verbally and documented nothing produced an EER record that looks like the IS3 developed independently, which understates the IS2's supervisory contribution and overstates the IS3's independence.
  • Skipping the ICS documentation on a multi-agency maritime intelligence coordination because the operational tempo made the paperwork feel secondary.
    CGIS case agent and the AUSA read every coordination document. The multi-agency intelligence operation that was coordinated verbally without written records is the operation that the defense counsel challenges at discovery. The IS2 who maintained the written record is the IS2 the AUSA calls as a documentation witness; the IS2 who did not is the IS2 the AUSA calls as a hostile witness about why the records do not exist.
  • Letting your JWICS or SIPRNet account go dormant because TDY, leave, or deployment interrupted the access routine.
    A classified network account that goes dormant for a defined period (the period is specified in the system's access policy — verify with the command's ISSO) triggers an automatic account audit. The ISSO notifies the security manager; the security manager notifies the IS1 and the unit security officer. In the IS rating, an account management finding is a clearance management finding — the IS2 who let the account lapse looks less attentive to the classified environment than the rating's standards require.

Career Decisions at This Rank

  • Request a joint intelligence center billet (JIATF South, NMIO, or NSA-adjacent) in the IS2 window versus staying in the primary production track through IS1.
    The joint billet is the IS community's broadening assignment — the experience that differentiates the IS2 who has worked only in CG-organic environments from the IS2 who has worked alongside DIA, DEA, NSA, and NGA analysts on active national-security problems. JIATF South is operationally intense and professionally exceptional; NMIO is analytically deep and nationally visible; NSA-adjacent billets are technically demanding and community-building in the IC sense. The timing question is whether the IS2 has enough independent production authority at the IS3/IS2 level to perform in the joint environment without a supervision structure that does not exist there. The ISC has a view on this and it is worth asking directly: 'Am I ready for a joint billet in this window, or does the record benefit more from another production cycle at [current unit] first?' The ISC's answer is the one that goes in the assignment preference.
  • IS1 Servicewide Exam timing — first available window or build the multiple first.
    The IS1 SWE multiple formula includes exam score, EER marks, performance evaluations, and time-in-rate factors. The IS2 who sits the exam in the first available window with a strong EER profile and a bibliography-complete study plan may have the highest-probability path to IS1 advancement. The IS2 who sits the exam before the EER profile is competitive is betting that the exam score will carry the multiple — and in a small community where the EER mark variance is narrow, that is a risky bet. Model the current multiple against the published cutting score before committing to an exam window.
  • Pursue the ISC (Chief Petty Officer) track versus lateral to a different career path at the IS2 window.
    The ISC selection in the IS community requires a strong multi-period EER profile, a joint billet or senior intelligence center assignment, a leadership C-school completion per CGPSC requirements, and the ISC's active endorsement. The IS2 who is on track for all four is the IS2 who should stay and compete for ISC. The IS2 who has a strong analytic record but does not want the senior leadership responsibilities that come with the anchor — the section culture ownership, the four EER cycles per year, the joint partner relationship management, the District Commander briefings — has a genuinely strong civilian intelligence market at IS2 with TS/SCI maintained, and the IS2-level credential is the right separation point for that path. Know which track you are on and plan accordingly.
  • Post-service planning as a rated IS2 with TS/SCI — start the civilian intelligence market conversation now or defer.
    The IS2 with a TS/SCI, a documented all-source analytic production record (not just clearance maintenance, but ICD 203/206-compliant finished intelligence products with named consumers), and JWICS/SIPRNet operational proficiency has a specific and strong market: DHS I&A entry-level to mid-level analyst, NMIO civilian intelligence officer, DIA or NGA contractor (maritime or general all-source), NSA mission partner support, and federal civilian GS-0132 series positions. The IS2 who begins the civilian market research at IS2 — understanding what each hiring pathway requires, what the clearance portability window looks like after separation (typically 24 months for TS, less for SCI compartments depending on program), what the GS-0132 qualification requirements include — can plan the separation timing to maximize the market options. The IS2 who defers this research to the last six months of a contract is making a lower-information decision under time pressure.

How the Seat Varies by Unit Type

  • Sector intelligence element (IS2 as senior analyst or section lead)
    At the Sector, the IS2 is typically the most senior producing IS at the command — the IS1 may be elsewhere or the billet may be IS2-topped. The Sector Commander reads your products daily. The feedback loop is direct and operational: when the morning brief is sharp, the Sector Commander notices; when it is not, the Sector Commander also notices. The production autonomy is real and the operational stakes are real. The IS3 who works under you at the Sector is learning the rating directly from your production standard, not from a more senior IS who can model a higher level. The weight of the section's analytic quality sits on the IS2.
  • District Intelligence Branch (IS2 as mid-grade analyst under IS1)
    The DIB gives the IS2 a more structured analytic environment — the IS1 and possibly an IS1 or ISC above them, longer-form District-level products with more formal review cycles, and exposure to the District Commander's intelligence requirements rather than just the Sector's tactical picture. The IS2 at a DIB is learning from a senior IS as well as teaching the IS3, and the production depth is richer. The consumer is more distant (the District staff, the DHS Enterprise) and the product review cycle is longer, but the tradecraft development environment is superior.
  • JIATF South (Key West, FL)
    The operational intelligence environment of the IS rating's primary joint assignment. JIATF South integrates DIA, DEA, NSA, CBP, and partner-nation intelligence on active counter-narcotics operations in the Caribbean and Eastern Pacific. CG IS2 billets here work in a production environment where the standard is IC-level, the consumer is an active operations cell, and the products directly support running interdiction cases. The IS2 who performs well at JIATF South builds a reputation that extends beyond the CG IS community into the broader maritime IC — which matters at both the ISC advancement board and the post-service market.
  • NMIO (National Maritime Intelligence-Integration Office)
    NMIO integrates maritime domain awareness from the full IC contributor base and produces the national-level maritime intelligence picture. CG IS2 billets at NMIO work at the intersection of CG intelligence and the broader IC maritime analysis community. The analytical work is longer-form, the consumers are senior IC and policy-level, and the production standard is national-level. NMIO builds the IS2's analytical depth and IC credibility faster than a Sector billet — at the cost of the direct-operational feedback that makes JIATF South work feel urgently consequential.
  • DHS Intelligence Fusion Center (CG liaison billet)
    Fusion center billets connect CG intelligence to state, local, tribal, and territorial (SLTT) law enforcement through the DHS Intelligence Enterprise. The IS2 at a fusion center works on a broader threat picture (maritime and non-maritime, depending on the center's scope), coordinates with a wider range of intelligence consumers, and develops the multi-agency liaison skills that CGIS and joint billet environments also require. The analytical community is broader and less specialized than at JIATF South or NMIO, but the interagency relationship-building is a distinct professional skill that the IS rating's most senior members need.

What Good Looks Like at This Rank

The good IS2 is the analyst the IS1 puts on the JIATF South Request for Information because the product will come back sourced to ICD 206, assessed to ICD 203, and formatted for a joint consumer without needing a rewrite before it crosses from the CG's SIPRNet compartment into the joint intelligence center's network. The IS1 does not edit the final product — the IS2's version is the version that goes out, because over time the IS1 has learned that this IS2's products do not require last-minute intervention. The IS3s below this IS2 are getting product review notes they can act on — not vague 'needs work' marks, but specific 'unsourced conclusion on paragraph three, cite the SIGINT summary product that supports this assessment per ICD 206 format' comments that teach the IS3 to source independently rather than to depend on the IS2 to source correctly in a follow-up pass. The IS3s' products are improving measurably period over period because the review loop is working as training, not just as quality control. When the IS3 advances to IS2, the review notes are in the training record and the IS2's contribution to that development is documented. The collection requirements pipeline at this IS2's unit is running without backlog because the IS2 tracks every open requirement against the unit's intelligence gaps, knows which gaps have been addressed by incoming collection and which require a new request, and drafts the formal requirement before the IS1 asks why the gap is still open. The CGIS hand-off package for the standing MLE operation has a written coordination record that the AUSA can review without calling the IS2 to reconstruct it from memory. The SWE bibliography is not a list on the desk — it is a completed reading program with chapter notes that started the week IS2 advancement was posted. The IS1 is already talking to the ISC about which joint billet fills the remaining career gap before the IS1 SWE window opens, because the IS2's EER trajectory is strong enough that the ISC is looking at the IS2's assignment sequencing, not at whether the IS2 is on track. This IS2 is on track — the conversation has moved to what shape the senior track takes.

Preview — The Next Rank

IS1 (E-6) is the first rank in the IS rating where the analytic product quality of the entire section is your responsibility to enforce, not just your own product lane to maintain. At IS2, you reviewed the IS3's work and submitted to the IS1 for dissemination authorization. At IS1, you are the final IS review before the product goes to the Sector Commander or the District Commander — the IS1 whose name is on the section's product quality. When the joint consumer comes back with a sourcing question on a product from three months ago, the call comes to the IS1, not the IS2 who drafted it. At IS1, the production complexity increases again: all-source intelligence assessments at the District Commander or Area Commander level, intelligence support plans for major MLE operations (not just daily products), joint intelligence center senior analyst assignments, and the senior CG IS liaison role in multi-agency federal cases. You are also running the section's ICD compliance program — not just applying ICD 203/206 on your own products, but auditing the IS2s' and IS3s' products and establishing the product quality standard the section runs against. The collection requirements management process becomes fully yours to own. The ISC preparation conversation begins at IS1. The EER profile over multiple assignments, the awards stack, the leadership C-school completion per CGPSC requirements, the joint billet that rounds out the record, and the ISC's active sponsorship — these are not IS1-level things to do eventually. They are IS1-level things to build from the first EER period. The IS community is small enough that the ISC slate sees everyone's record; the IS1 who starts the chief preparation at IS1 is the IS1 whose ISC packet is competitive when the selection window opens.
FAQ

IS E5 — Frequently Asked Questions

Q01What does a E5 IS (Intelligence Specialist) actually do?
You are typically the senior analyst at a Sector intelligence element or a mid-grade analyst at a District Intelligence Branch, a joint intelligence center billet, or an Area command.
Q02What's the most important thing to know as a E5 IS?
IS2 is the rank where the IS rating's standards become your responsibility to enforce, not just your obligation to meet.
Q03What does a typical day look like for a E5 IS?
Time-blocked day at the E5 IS rank tier: 0530 Wake. Coffee. Review the CG intelligence summary or unclassified maritime traffic report if available — the morning section brief starts with a picture that was built overnight, and the IS2 who walked into the brief cold wastes the first 15 minutes of the IS1's production window, 0545-0630 Section morning brief. IS1 or ISC puts out the day's product tasking — standing requirements, incoming RFIs, any JIATF South or NMIO contributions due, any classified material accountability actions outstanding.…
Q04What mistakes get E5 IS soldiers fired or relieved?
Allowing a JWICS product's source references to be removed or generalized before handoff to the IS3 as a 'training simplification.' The IS3 learns ICD 206 sourcing discipline by working with fully sourced products; removing or generalizing the sources to make the product 'easier to work with' produces an analyst who cannot source independently. The IS2's job is to teach the tradecraft, not to protect the IS3 from its difficulty;…
Q05What career decisions matter most at the E5 IS rank tier?
Request a joint intelligence center billet (JIATF South, NMIO, or NSA-adjacent) in the IS2 window versus staying in the primary production track through IS1 — The joint billet is the IS community's broadening assignment — the experience that differentiates the IS2 who has worked only in CG-organic environments from the IS2 who has worked alongside DIA, DEA, NSA, and NGA analysts on active national-security problems. JIATF South is operationally intense and professionally exceptional; NMIO is analytically deep and nationally visible;…
Q06What's next after E5 for a IS (Intelligence Specialist) in the Coast Guard?
IS1 (E-6) is the first rank in the IS rating where the analytic product quality of the entire section is your responsibility to enforce, not just your own product lane to maintain.
Q07What manuals and regulations does a E5 IS need to know cold?
COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual; you run the section's product compliance against this publication.; ICD 203 — Analytical Standards; ICD 206 — Sourcing Requirements for Disseminated Analytical Products; ICD 208 — Collection Requirements (verify ICD 208 current title and number against the ODNI Directives Library); you apply all three on every finished product you produce or review.; JP 2-01 — Joint and National Intelligence Support to Military Operations;…

Based on 14 tips from 0 contributors

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