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
ISE7

Intelligence Specialist

E-7 (Sergeant First Class) · Coast Guard

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

ISC is not a bigger IS1 seat — it is a different job. The product quality of the Coast Guard's intelligence enterprise, the clearance integrity of every IS in your District, and the career arc of every IS1 and IS2 who will anchor the rating for the next decade are all yours to own. Get to CPOA at Petaluma as soon as the initiation cycle sends you, complete the Senior Enlisted Leadership Course, and start the ISCS broadening conversation before you have been an ISC for eighteen months. The community is too small and the ISCS billets too few for any ISC to coast between pin and selection.

The Honest MOS Read
The ISC pin is the most significant transition in the IS rating's career ladder — more significant than the IS1 pin, more significant than the IS2 SWE, more significant than the jump from A-school to first assignment. At IS1 you were the unit's senior technical analyst. At ISC you are the unit's intelligence culture owner. The distinction matters in ways that are not immediately obvious when the anchor goes on the collar device, and the ISC who misses it spends two years managing analysts when they should be building analysts. Your primary accountability at ISC is the intelligence section's product quality — not as the reviewer of last resort, but as the standard-setter whose expectations make the IS1's review the definitive quality check. The ISC who reviews every product personally because the IS1's product review standard is not reliable has not built an IS1 — they have built a production assistant. The ISC who trusts the IS1's product review because they built the standard the IS1 enforces — that ISC has time for the work that only an ISC can do: the joint partner relationship management, the senior-enlisted interface with the District Commander, the IS workforce advocacy at the command level, and the mentoring of IS1s into ISC-competitive candidates. Chief Petty Officer Academy at TRACEN Petaluma is the institutional frame of the seat. CPOA is not management training — it is an introduction to the Chiefs Mess as an institution, and the Mess is a different kind of accountability structure than the IS section. The ISC who walks out of CPOA understanding the Mess's obligations — the responsibility to the non-rates, the relationship to the XO and CO as the senior enlisted voice, the internal accountability culture of the Mess itself — is the ISC who runs a section differently than the one who treated CPOA as a course to check off. The interagency dimension of the ISC seat is where the real operational weight lives. You are not only managing Coast Guard IS members and Coast Guard intelligence products — you are the senior CG IS at the table with FBI, DIA, NSA, DHS I&A, NMIO, and JIATF South. Every joint coordination action your section produces, every intelligence-to-law-enforcement handoff your unit runs, every collection requirement your District files through ODNI channels has your name on it at the senior enlisted coordination level. The DIA partner at NMIO who calls your desk when a product has a sourcing question is not calling the IS1 — they are calling the ISC. How you handle that call, what you know cold, and whether you have maintained your own analytic tradecraft currency shapes whether the partnership is productive or merely polite. The ISCS preparation is a present-tense activity, not a future plan. The ISCS board reads the ISC record across every billet, and the community is small enough that the board knows the products coming out of your section, the IS1s your EER bullets have built, and the joint partner reputation your unit has earned. The Senior Enlisted Leadership Course (SELC) at Petaluma is the formal education gate. The CGICICOM billet, the Area intelligence staff senior IS seat, or the CG headquarters intelligence staff assignment is the broadening billet. The joint intel center experience — JIATF South or NMIO at the ISC level — is the assignment that demonstrates senior-leader-level IC performance. Start planning all three before you have been an ISC for eighteen months, because the pipeline for ISCS-competitive billets runs years ahead.
Career Arc
  • 01Chief Petty Officer Academy (CPOA) at TRACEN Petaluma, CA — completion is the first accountability of the ISC career; understand the Chiefs Mess as an institution, not just a milestone.
  • 02Senior Enlisted Leadership Course (SELC) at TRACEN Petaluma — the formal education gate for the ISCS slate; verify current CGPSC requirement against the active ALCGENL before quoting the specific course requirement.
  • 03Joint intelligence center billet at ISC level — JIATF South (Key West), NMIO (Suitland), or an NSA/DIA-adjacent CG IS chief seat — the ISCS-broadening assignment the board reads as IC-level senior-leader performance.
  • 04CGICICOM or Area / CG HQ intelligence staff senior IS chief billet — the other broadening track, with CI operations, classified source management, and DHS Intelligence Enterprise coordination at the senior enlisted level.
  • 05IS1 mentorship pipeline: four IS1s on individual mentoring plans with EER trajectory mapping, joint billet sequencing, and ISC-competitive record-gap analysis — the ISC board reads the candidates you build as part of your record.
  • 06ISCS Service-Wide Personnel Board preparation: EER trend across multiple billet types, CPOA/SELC complete, joint exposure documented, IS community network behind the packet, and the senior-enlisted leadership reputation the ISCS board knows before the packet arrives.
  • 07Post-Coast Guard credential planning: DHS I&A senior analyst, NMIO civilian intelligence officer, DIA maritime-domain mission partner, NGA maritime analyst, NSA maritime intelligence contractor, or federal GS-0132 intelligence officer pipeline — start planning 36 months out.
Common Screwups
  • ×Treating the ISC seat as a larger IS1 seat — continuing to review every product personally rather than building the IS1's product review standard into a reliable function. The ISC who does the IS1's job because the IS1's standard is insufficient has failed to build an IS1, and that failure is visible to the District intelligence officer and to the ISCS board as a leadership gap.
  • ×Going public with disagreement with the District intelligence officer, the Area intel staff, or the command's product call on a classification or sourcing question. The ISC takes it in the office, makes the case with evidence, documents the recommendation if it is overruled, and walks out aligned. The rating reads what the anchor tolerates and what the anchor disputes, and both have to be handled correctly.
  • ×Letting the classified material accountability program drift during a sustained operational tempo because the operation is the priority. The TS/SCI annual inventory finding that surfaces after a surge operation was created during the surge — the ISC who 'catches up after' has already lost the clean-record standard the ISCS board looks for.
  • ×Inflating EER blocks on a technically strong IS1 whose analytic judgment is thin under pressure, because the IS1 is a likable teammate. The ISCS board and the joint intelligence community both read those evaluations; inflated bullets that do not survive contact with the IS1's actual performance record are identified and discounted, and the ISC who wrote them loses credibility on every future evaluation.
  • ×Stopping personal analytic tradecraft currency because 'I'm a chief now.' The IS section respects the ISC who can still walk through an ICD 203-compliant all-source product and identify the sourcing weakness in the second paragraph. The ISC who cannot do that technically has outsourced the quality-control standard to the IS1 — and has no floor when the IS1's standard is wrong.

A Day in the Life

  • 0530-0630PT. Personal — most ISC billets at District or Area do not run a formation PT program the BM station way. Accountability is individual. Know your PFT score and the annual test window; physical fitness is the most visible standard the ISC models for the section.
  • 0630-0700SIPR/JWICS open. Pull the overnight classified message traffic — NMIO maritime domain awareness summary, DHS I&A morning brief, any JIATF South operational reporting relevant to the District AOR. Log receipt. Flag anything for the IS1's morning product review or for direct ISC action.
  • 0700-0730IS1 product review audit. Pull the IS1's product review notes from yesterday's batch. Spot-check two or three products against ICD 203/206 standards — not full review, but enough to confirm the IS1's standard is running correctly. If a product review note is too thin, return it with the specific question the IS1 needs to answer.
  • 0730-0830Morning intelligence update brief or standup with the District intelligence officer. The ISC is the senior IS voice at this brief. Workforce readiness, product posture, collection requirements status, any joint partner coordination required — these items come from the ISC, not the IS1.
  • 0830-1000Joint partner coordination or senior IS-staff work. Collection requirement submissions through DHS/ODNI channels, CGIS intelligence-to-law-enforcement handoff package review at the ISC level, any NMIO or JIATF South coordination action requiring the senior CG IS at the District. This is the ISC's work — the IS1 produces products; the ISC works the relationships that make the products consequential.
  • 1000-1100IS workforce management. EER input drafting for IS1s and IS2s. Clearance reinvestigation status check on the section calendar — any member whose window is opening in the next six months gets a proactive mentoring conversation this week. Awards nomination review for IS2s coming up on the cycle. Joint billet pipeline check — are the IS1s' assignment preference requests filed?
  • 1100-1200ISC direct product work — complex assessments the ISC is personally authoring for the District Commander or Area intelligence staff. This block is protected. The ISC who stops producing intelligence personally loses analytic currency; the standard cannot be enforced from abstraction.
  • 1200-1300Lunch and Chiefs Mess business. Unit climate, discipline cases in the section, EO posture. The Mess business is not optional and not secondary — it is the institutional accountability of the seat.
  • 1300-1500Mentoring one-on-ones. Two 30-minute sessions with IS1s on individual record development plans. Record-gap mapping against current ISC competitive profile, joint billet sequencing, EER strategy, leadership C-school timing. This time is protected — the mentoring conversation is work.
  • 1500-1600Classified material accountability program management. Section material log review, JWICS account audit status, any ICD compliance findings from the IS1's product review that require ISC-level corrective action. Annual review documentation if in the review window.
  • 1600-1630District intelligence officer end-of-day coordination. Product status update, any emerging operational intelligence requirements from the operations center, workforce status for overnight duty sections if the District runs them.
  • After-hours — joint billet (JIATF South / NMIO / Area)At a joint intel center the schedule is the watch bill's schedule, not this one. The ISC at JIATF South is working the J2 staff, the partner-nation liaison coordination, and the drug-interdiction operational intelligence cycle on the joint command's timeline. The standard is the same — ICD compliance, classified accountability, workforce management — but the pace and the consumer profile are materially different from a District-level assignment.

Weekly Cadence

The ISC's week at a District Intelligence Branch or Area intelligence coordination cell is structured around the intelligence production cycle, the joint partner coordination calendar, and the IS-workforce management rhythm that the IS1 level cannot see from below. Monday sets the week: product assignments finalized for the IS1s and IS2s, classified message traffic from the weekend triaged, joint coordination requirements from the operations center assessed. The ISC's own product work — the assessments the District Commander or Area staff is reading — is concentrated in Tuesday and Thursday morning blocks, protected from administrative interruption. Wednesday is typically the joint partner day: CGIS case-support coordination, collection requirement status calls with the DHS collection management office, any NMIO or JIATF South action item from the prior week's product dissemination. The ISC IS the CG IS on these calls — the IS1 may be on the line, but the CG senior IS voice in the joint coordination is the ISC's responsibility. Friday is the administrative and people-management close: EER inputs finalized for the cycle, classified material accountability review completed, IS workforce status summary prepared for the District intelligence officer, and the ISC's own professional development calendar updated for the following week. The cadence shifts completely during a major operational surge — an MLE surge operation, a counterterrorism port security event, a significant vessel-of-interest case that involves FBI, DEA, and DHS I&A simultaneously. During a surge the ISC is in the operational planning cell, the product review cycle runs at double speed, the joint coordination actions multiply, and the classified material log is more active than it is during garrison tempo. The ISC who has built the classified accountability habit as a daily practice does not fall behind during a surge. The ISC who relies on the quarterly catch-up is buried when the surge hits.

Key Skills — How to Drill Each

  1. 01
    Run the intelligence section's product quality program as the senior IS — ICD 203/206/208 compliance, classified material accountability, collection requirements management, and the senior-enlisted interface with the District intelligence officer on every IS-workforce and product-quality decision.
    Build the product quality program as a documented standard, not a personal review habit. Create a standing product review checklist against the current ICD standards, train the IS1 to run it, and audit the IS1's output quarterly rather than daily. The ISC who reviews every product personally is the bottleneck; the ISC who built the standard the IS1 enforces has time to do the work that only an ISC can do — the joint partner engagement, the workforce advocacy, and the ISCS preparation.
  2. 02
    Mentor three-to-four IS1s into ISC-board-competitive candidates — EER trajectory, joint billet recommendations, clearance reinvestigation timeline, leadership C-school completion, awards profile, and the chiefs' mess sponsorship conversation.
    Have the mentoring conversation with each IS1 at their six-month-in-billet mark: map their record gaps against the current ISC competitive profile (pull the last two ISC selection messages from CGPSC and map the fields), give them a specific plan with specific timelines, and track the plan at each quarterly EER review. The IS1 who is told 'your record looks thin' in the year before the ISC packet is submitted got that feedback nine years too late; give it the year they pin IS1.
  3. 03
    Brief the District Commander or Area intelligence staff on intelligence product posture, collection gaps, and IS-workforce readiness honestly — including the shortfalls — before those shortfalls surface in a joint partner complaint or a TS/SCI inspection finding.
    Prepare a monthly IS-section status brief for the District intelligence officer and the ISC's chain of command: products delivered and consumer feedback received, collection requirements open and overdue response, clearance reinvestigation status for every IS member, ICD compliance posture, and billet-fill readiness. The ISC who reports the gap internally first is never the ISC explaining a gap to a joint partner complaint; the one who waits is.
  4. 04
    Coordinate the unit's intelligence support to major CG operations — MLE surge, counterterrorism port security, joint drug interdiction — at the senior enlisted planning cell level, with product delivery and collection coordination documented to a standard the joint partner trusts.
    Insert yourself into the operational planning cell at the concept-of-operations phase, not after the operation has been ordered. The IS section's collection support requirements need to be in the intelligence support annex before the operation launches, not retrofitted after the first C2 report comes in. The joint partner — FBI, DEA, CBP, JIATF South — trusts the IS section that shows up with a documented collection and product delivery plan before the first boarding, not the one improvising during the surge.
  5. 05
    Sit in the Chiefs Mess on the unit's discipline cases, climate posture, and EO/sexual assault prevention picture, and translate those into actions the District Commander will fund and the IS1s will execute.
    The IS rating's technical identity can make the senior IS chief a specialist in the Mess who defers on the people-management dimensions. Do not allow that. The Chiefs Mess's discipline and climate accountabilities apply to the IS section as much as to the BM deck force or the MK engineering division. The ISC who is informed on the section's EO posture, who knows which IS2 is struggling financially and is the potential counterintelligence vulnerability, and who is present for the morale problem before it becomes a headline is the ISC who keeps the clearance record clean.
  6. 06
    Walk the section's classified material accountability and ICD compliance posture during an annual or CI-driven review and identify the gap — the unsigned destruction certificate, the ICD 206 sourcing error in an archived product, the JWICS account that has not been audited — before the District security officer finds it.
    Conduct a personal annual walkthrough of the classified material log, the JWICS account audit report, and a sample of 10 recent archived products against ICD 206 sourcing standards — not as a spot check but as a documented ISC-initiated internal review. The gap the ISC identifies and corrects before the inspection is the gap that does not go in the inspection finding report. The gap the inspection team finds first goes in the report with the ISC's name on the responsible-senior-enlisted line.

Manuals & References — What Chapters Matter

  • COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual.
    The doctrinal authority for everything the IS section does at your command. At ISC you are the senior enlisted authority on this document — not just conversant with the sections relevant to the current product lane, but fluent across every chapter, including the CI reporting requirements, the collection management authorities, and the classified material handling standards that apply to your billet's TS/SCI accountability.
  • ICD 203 — Analytical Standards; ICD 206 — Sourcing Requirements for Disseminated Analytical Products; ICD 208 — Collection Requirements (verify current ICD titles and numbers against the ODNI Directives Library).
    You set the section's compliance posture against all three. The ISC who briefs the IS1 on product quality against the ICD standards without personally knowing the standards is enforcing a standard by reputation, not by knowledge. Know each ICD chapter-level — what the sourcing requirement says, what analytic confidence language means in the IC context, and what the collection management process actually allows the IS rating to request at the District level.
  • COMDTINST M5520.12 (current revision) — Coast Guard Counterintelligence Manual.
    CI reporting requirements and the ISC's role in the unit's CI awareness program are not awareness-level obligations at this rank — they are operational ones. The ISC who identifies the IS member with an undisclosed foreign contact before the periodic reinvestigation surfaces it has protected the section's clearance integrity and the member's career. Know the reporting triggers, the reporting chain, and the ISC's role in the preliminary inquiry process.
  • CIM 1610-series — Enlisted Employee Review (EER).
    Your bullets pick the next ISC slate. The ISC who writes EER inputs that document observable analytic output, named operational contributions, and measurable mentorship results — rather than generic 'dedicated professional' filler — is the ISC whose IS1s' packets are competitive when the selection cycle opens. The EER is not a formality; it is the four-year record you are building for every IS1 in your section.
  • JP 2-01 — Joint and National Intelligence Support to Military Operations.
    At joint billet level — JIATF South, NMIO, or the Area intelligence coordination cell — this is the operating framework the joint consumer uses to evaluate your section's contributions. The ISC who knows JP 2-01 at the chapter level can position the IS section's collection and product capabilities in the joint planning cell language the joint partner recognizes, rather than translating between CG and joint doctrine in real time.
  • Coast Guard Administrative Investigations Manual (verify current pub designation against the CG Directives System).
    Security investigations, classified material mishandling events, and clearance-related administrative actions at the unit level run through the ISC and the District security officer. The ISC who has never read the AIM is the ISC who makes procedural errors in the investigation stage that complicate the case record. Know the initial inquiry procedures, the preliminary inquiry standards, and the ISC's role in forwarding findings before the investigation is initiated — not after.

Standards — How to Hit Each

  • Chief Petty Officer Academy (CPOA) at TRACEN Petaluma, CA completed early in the ISC career; Senior Enlisted Leadership Course (SELC) completed per current CGPSC requirements for the ISCS selection slate.
    CPOA is not the kind of professional development you schedule when the operational calendar allows — it is the first institutional gate of the ISC career and the CG schedules it for you at the initiation cycle. Show up. Complete it. SELC is the gate the ISCS board reads as the formal leadership education requirement; verify the current CGPSC requirement against the active ALCGENL before planning your timeline, because the requirement has shifted between selection cycles.
  • TS/SCI maintained with CI awareness program posture current at your command scope — no TS/SCI handling findings attributable to your section during your tenure as ISC.
    Build the clearance accountability posture as a documented program, not a personal awareness effort. Track every IS member's reinvestigation window, self-reporting posture, and CI contact report on a section-level clearance calendar. The ISC who knows six months in advance that IS2 Smith's periodic reinvestigation window is opening has time to prepare the member — the ISC who learns at the JPAS audit that the window passed without action has an administrative problem and a potential clearance gap at the same time.
  • IS section EER profile clean across IS1 and IS2 cohorts — members advancing on schedule and EER bullets consistent with what the District IS chief network knows about the section's product quality.
    Read back the last three years of your IS1s' EER narratives before you write a new one. The consistency of the record — does the written record match the reputation of the section in the IS chief network? — is what the ISCS board audits. An EER that claims analytic production quality above what the NMIO partner knows about the section's products is an inconsistency the board's IS community advisor identifies.
  • Zero senior-enlisted integrity incidents — financial, fraternization, clearance mishandling, product fabrication — during ISC tenure.
    This standard requires active management, not passive compliance. The ISC who knows the financial posture of the IS section, who is aware of the relationship boundaries within the section, and who models the clearance reporting standard by self-reporting their own contacts and changes proactively is the ISC whose section does not generate the incident. The incident that happens on your watch is the incident the investigation names you on.
  • Joint intelligence center qualification or NMIO-equivalent on the record or in the current assignment cycle — the ISCS board reads breadth of assignment, not depth at one command.
    If the joint billet is not yet on the record at the time of the ISC pin, request it in the first assignment preference window. The ISCS board cycle runs long enough that a joint billet requested at the ISC pin timeline can complete before the ISCS selection package is due. The ISC who waits until the second assignment preference window to request the joint billet is running the timeline to the edge.

Technical Mistakes — Concrete Consequences

  • Letting the classified material accountability program drift during an operational tempo surge because 'we'll catch up after the operation.'
    The TS/SCI annual inventory is not a negotiable deadline, and the gap that surfaces on the CI-driven inspection was created during the surge. The ISC whose section has accountability gaps on the annual review is the ISC answering the District security officer's inquiry, the District Commander's information paper, and the CGICICOM's preliminary inquiry simultaneously — all of which trace to the period the ISC accepted a 'we'll catch up later' standard.
  • Going public with disagreement with the District intelligence officer or the Area intel staff on a product call, a collection management decision, or a workforce allocation.
    The IS rating — and the broader CG intelligence enterprise — reads the ISC's public posture as the section's posture. An ISC who expresses disagreement with command guidance outside the office creates a perception of instability in the section's senior leadership that the District Commander and the joint partners notice. Take the disagreement in the office, document the recommendation if overruled, and walk out aligned. The rating reads alignment from the anchor; the anchor is you.
  • Inflating EER blocks on a technically strong IS1 whose analytic judgment under pressure or leadership of the section is weaker than the technical capability suggests.
    The ISCS board — which has at minimum one IS community advisor — identifies inflated EER bullets against the IS1's actual performance reputation in the IS chief network. An inflated IS1 block discredits the ISC who wrote it on every subsequent evaluation, and the IS1 who is promoted to ISC on an inflated record performs below expectations in a seat where weak analytic judgment has IC-level consequences.
  • Stopping personal engagement with analytic tradecraft because 'I'm a chief now and I manage people who do analysis.'
    The IS section's product quality standard depends on the ISC knowing what the standard actually looks like — not just being able to articulate the ICD 203 paragraph. The ISC who cannot personally walk through an all-source assessment and identify a sourcing error in the second paragraph has outsourced the quality floor to the IS1. When the IS1's standard is wrong, the ISC has no backstop.
  • Treating joint partner relationships with JIATF, DIA, NSA, and FBI as purely operational rather than sustained professional relationships requiring active maintenance.
    The joint partner who has not heard from the CG ISC except on an active case request is a partner who has a polite professional relationship, not a trusted one. The 0200 request for information that gets a real response comes from a relationship built across multiple non-crisis interactions — the debrief after a successful joint product, the proactive notification when a classification issue surfaces in an archived product, the professional conference where the ISC introduced the IS1 to the DIA counterpart. The operational response at 0200 is the dividend of the relationship built on a Tuesday afternoon.

Career Decisions at This Rank

  • Request the ISCS-broadening joint billet — JIATF South at ISC level, NMIO senior IS seat, or an NSA/DIA-adjacent CG chief billet — now, or defer until the current District assignment is complete.
    The ISCS board reads the ISC record against the community's expectations for senior-leader IC performance. In a rating this small — where there may be fewer than a dozen active-duty ISCs in the service at any given time — every ISCS selection is visible to the whole community. The ISC who arrives at the selection cycle without a joint billet on the record is the ISC who has chosen the narrow path, and the board makes that judgment with full awareness of the assignment pipeline that was available. If the family situation, the operational tempo, or the unit's billet-fill reality genuinely prevents the joint billet request right now, have the explicit conversation with your ISCS and the IS community manager — not to find an excuse, but to build the alternative broadening plan that substitutes.
  • ISCS packet this cycle, or defer to the next cycle for a stronger record.
    The IS community is too small for an ISC who is ISCS-ready to defer without cost. Every deferral is a year where the community's most senior seats are filled by someone else, and the ISC who defers because 'I want one more broadening assignment' is gambling on the assignment pipeline delivering in time for the next cycle. The honest read: if the record has the joint billet, the CPOA/SELC, the EER trend, and the IS community network behind it, submit. If the record has a real gap — not a perceived one — close the gap first. The ISC who submits a marginally competitive packet and does not make the cut in the same community everyone knows faces an institutional read that is harder to recover from in a rating this small.
  • CGICICOM senior IS billet vs. Area/CG HQ intelligence staff — which broadening track fills the ISCS record gap better?
    Both tracks build the record, but they build different parts of it. The CGICICOM billet builds the CI operations, classified source management, and DHS Intelligence Enterprise coordination dimensions that the Area intelligence staff does not — it is the specific broadening assignment for the ISC whose record is strong on all-source analysis but thin on counterintelligence and IC enterprise coordination. The Area or CG HQ intelligence staff billet builds the senior-command advisory dimension — the ISC who has been the senior IS voice at an Area Commander's morning brief is the ISC who can brief the Commandant's staff without preparation. Talk to your ISCS about which gap the record actually has and request accordingly.
  • Post-service planning: start the DHS I&A, NMIO civilian, or IC contractor track now — 36 months out — or wait until the separation window is clear.
    The ISC who starts the post-service planning at 36 months out is the ISC who retires into a senior civilian position rather than starting over. DHS I&A's maritime domain intelligence analyst pipeline specifically values former CG IS chiefs for the Coast Guard mission-integration expertise. NMIO civilian positions have a CG-to-civilian conversion track. The federal GS-0132 Intelligence Analyst series and the IC contractor market (Booz Allen, Leidos, SAIC, CACI, MITRE) value the TS/SCI clearance with an adjudicated record and the analytic tradecraft background. The ISC who begins cultivating these relationships — attending the INSA or AFCEA maritime intelligence events, maintaining the NMIO and DIA professional relationships, staying current on the IC hiring landscape — arrives at the separation window with options, not applications.

How the Seat Varies by Unit Type

  • District Intelligence Branch (DIB) — District Commander staff
    The canonical ISC assignment. You are the senior IS at the DIB, running a section of IS1s and IS2s producing all-source intelligence for the District Commander's MLE, counterterrorism, and port-security operations. The District intelligence officer is the officer you work for; the Area intelligence staff is the consumer above that. This is where the ISC builds the product quality standard and the workforce management habits that the ISCS board reads.
  • Area intelligence coordination cell — Atlantic Area or Pacific Area
    A broader and more senior assignment than the DIB. You are coordinating intelligence support across multiple Districts, producing assessments for the Area Commander, and interfacing with the DHS intelligence enterprise and the NSC maritime domain awareness community at the Area staff level. The product lane is wider, the consumer is more senior, and the joint coordination is more complex. A strong Area ISC billet reading is a meaningful step toward the ISCS seat.
  • Joint intelligence center — JIATF South (Key West) or NMIO (Suitland, MD)
    The ISC-level IC performance billet. At JIATF South you are sitting in the Joint Task Force J2 staff alongside DoD analysts, DEA embedded intelligence officers, and partner-nation liaison officers — producing and coordinating intelligence that drives active drug-interdiction and migrant-flow interdiction operations. At NMIO you are contributing to national-level maritime domain awareness products read by the NSC and partner-nation equivalents. Both billets are schedule-intensive and deployment-adjacent. Both billets demonstrate performance at a consumer level the District billet cannot replicate.
  • CGICICOM — CG Intelligence and Criminal Investigations Command
    The CI-operations and classified source management track. The CGICICOM senior IS billet involves CI investigations, source development coordination with FBI and DIA, classified source handling at a standard above the DIB's collection management work, and DHS Intelligence Enterprise operational integration. The CGICICOM ISC is the most operationally sensitive IS position in the service below the headquarters level, and the clearance accountability standard is correspondingly unforgiving.
  • CG headquarters intelligence staff (Washington, DC)
    The most senior non-ISCS/ISCM IS chief billet in the service. The CG headquarters IS staff provides intelligence support to the Commandant, interfaces with the ODNI and senior IC community at the national-level, and represents the Coast Guard IS community in IC enterprise forums. The billet requires a record that is already demonstrating senior-leader-level IC performance — it is not a broadening assignment, it is a validation assignment. The ISC who is selected for the headquarters IS staff is already ISCS-competitive.

What Good Looks Like at This Rank

The good ISC is the senior enlisted the District intelligence officer calls not when a product has a problem, but when the District Commander is about to brief an intelligence picture to the Area Commander and the intelligence officer wants to know whether the analytic foundation will hold under scrutiny. The ISC who gets that call gets it because the products have been right consistently — sourced to ICD 206, assessed to ICD 203, classified correctly, and formatted for a consumer who does not need an explanation. The joint partners at NMIO and JIATF South know this section's products by their quality, not just by their origin. The IS1s below this ISC are being built, not managed. Each IS1 has a mentoring conversation on the calendar, a record-gap analysis on paper, a joint billet request filed in the assignment preference system, and an EER trend that reads upward across the last three evaluation periods. The section's classified material accountability log is current to the day. The JWICS account audit report is clean. The ICD compliance posture would survive an unannounced CI-driven review because the ISC built it as a daily habit, not a pre-inspection sprint. In the Chiefs Mess, this ISC carries both dimensions: the analytic authority of the rating's senior IS and the institutional accountability of a Chief Petty Officer. The discipline cases in the section are handled in the Mess, the EO posture is visible and current, and the morale problem the XO does not know about yet is the one the ISC is already addressing. The ISCS sponsorship conversation has been happening for two years. The SELC is complete. The joint billet that rounded out the record is in the past. When the ISCS selection message posts and this ISC's name is on it, the other ISCs in the network nod — because they already knew.

Preview — The Next Rank

The ISCS seat is a different kind of senior — not more of the ISC, but a different relationship to the IS rating itself. The ISC is the standard-setter at the District; the ISCS is the standard-setter for the rating. The ISC who becomes ISCS is no longer managing the intelligence section's culture — they are managing the IS rating's culture across every District and Area where IS members are assigned. The analytic tradecraft standard that the ISCS enforces through EER bullets, billet decisions, and community-manager advisory inputs is the standard the junior IS3 at the Sector intelligence element is learning without knowing it. The ISCM track — for the ISCS who makes it — is the most senior enlisted seat in the service at the command level. The ISCM sits on the Senior Enlisted Council, advises the Area Commander or the Commandant on IS-workforce decisions, and is the anchor the entire IS rating navigates by. In a rating with fewer ISCMs than you can count on one hand at any given time, the ISCM seat is genuinely the top of the pyramid. Post-Coast Guard planning is a present-tense item at ISCS, not a someday conversation. The DHS I&A senior analyst pipeline, the NMIO civilian intelligence officer track, the NGA maritime domain analyst pathway, and the federal GS-0132 intelligence officer series all value the ISCS credential — the TS/SCI clearance, the IC-level analytic tradecraft, the senior-leadership record, and the joint partner network that the ISCS brings from 20+ years of IS service. The ISCS who retires with a transition plan already in execution, relationships already cultivated at the DHS and IC agencies, and the federal hiring process already in progress does not have a gap between uniform and meaningful work. Start the planning now, before the senior enlisted service is more than half over.
FAQ

IS E7 — Frequently Asked Questions

Q01What does a E7 IS (Intelligence Specialist) actually do?
You are typically the senior IS chief at a District Intelligence Branch, the senior IS at an Area intelligence coordination cell, the senior CG IS at a joint intelligence center (JIATF South, NMIO, or an NSA/DIA-adjacent billet), or the senior IS presence at Force Readiness Command (FORCECOM) or Coast Guard headquarters.
Q02What's the most important thing to know as a E7 IS?
ISC is not a bigger IS1 seat — it is a different job.
Q03What does a typical day look like for a E7 IS?
Time-blocked day at the E7 IS rank tier: 0530-0630 PT. Personal — most ISC billets at District or Area do not run a formation PT program the BM station way. Accountability is individual. Know your PFT score and the annual test window; physical fitness is the most visible standard the ISC models for the section, 0630-0700 SIPR/JWICS open. Pull the overnight classified message traffic — NMIO maritime domain awareness summary, DHS I&A morning brief, any JIATF South operational reporting relevant to the District AOR. Log receipt.…
Q04What mistakes get E7 IS soldiers fired or relieved?
Treating the ISC seat as a larger IS1 seat — continuing to review every product personally rather than building the IS1's product review standard into a reliable function. The ISC who does the IS1's job because the IS1's standard is insufficient has failed to build an IS1, and that failure is visible to the District intelligence officer and to the ISCS board as a leadership gap; Going public with disagreement with the District intelligence officer, the Area intel staff,…
Q05What career decisions matter most at the E7 IS rank tier?
Request the ISCS-broadening joint billet — JIATF South at ISC level, NMIO senior IS seat, or an NSA/DIA-adjacent CG chief billet — now, or defer until the current District assignment is complete — The ISCS board reads the ISC record against the community's expectations for senior-leader IC performance. In a rating this small — where there may be fewer than a dozen active-duty ISCs in the service at any given time — every ISCS selection is visible to the whole community. The ISC who arrives at the selection cycle without a joint billet on the record is the ISC who has chosen the narrow path,…
Q06What's next after E7 for a IS (Intelligence Specialist) in the Coast Guard?
The ISCS seat is a different kind of senior — not more of the ISC, but a different relationship to the IS rating itself.
Q07What manuals and regulations does a E7 IS need to know cold?
COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual; you are the senior enlisted authority on this publication at your command.; ICD 203, ICD 206, ICD 208 — you own the section's compliance posture against all three; verify current ICD titles and numbers against the ODNI Directives Library.; COMDTINST M5520.12 (current revision) — Coast Guard Counterintelligence Manual; CI reporting requirements and the ISC's role in the unit's CI awareness program.

Based on 14 tips from 0 contributors

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