Intelligence Specialist

You are the non-rate with a clearance in progress and an intel career on the horizon. The IS rating is one of the smallest and most clearance-dependent in the service — and right now your only job is to stay clean, stay curious, and not say anything on social media that kills your adjudication before it starts.

You came out of TRACEN Cape May after eight weeks and reported to a Sector command, a District intelligence staff, or a Coast Guard Investigative Service (CGIS) support element as a non-rated Coastie striking for IS. The work right now is mostly administrative groundwork and observation: logging watch entries for the IS2 or IS1, running analytical products through the secure printer, updating contact databases under direct supervision, and sitting in on every intelligence briefing you are cleared to attend so the terminology stops sounding foreign. The IS A-School pipeline — currently operated at NAS Dam Neck, Virginia Beach, VA, verify current assignment via ALCGPSC — is the gate, and the path runs through your SSBI (Single Scope Background Investigation) or TS/SCI adjudication, your EER blocks, and the IS chief's endorsement. In the meantime you are completing the IS striker PQS, learning the classification markings cold (CONFIDENTIAL, SECRET, TOP SECRET, SCI handling rules, the difference between FOUO and CUI), and reading whatever unclassified intelligence doctrine your supervisor directs — JP 2-0 is the joint doc that makes the vocabulary make sense. You also handle the unglamorous parts that keep the intel section running: classified material accountability logs, destruction certificates, cleared-personnel visitor logs, and the physical security checks that keep the space in compliance with the applicable SCG.

• 01Handle classified material at the level of your current access — receipt, storage, accountability log entry, and destruction — without creating a spillage, a mishandled classified event, or an accountability discrepancy that triggers a security investigation.
• 02Maintain proper classification markings awareness: distinguish between SECRET, TOP SECRET, SCI material, and CUI (Controlled Unclassified Information); know the handling rules for each before you touch a document in the section.
• 03Log a SIPRNET or JWICS message traffic receipt accurately — date-time group, classification, subject line, originator, routing, and disposition — in the format the IS2 specifies; the audit trail on classified traffic is not optional.
• 04Conduct basic open-source research using government and publicly available databases and present a clean summary to the supervising IS on the format they specify — source cited, date verified, no fabricated or extrapolated information.
• 05Operate the section's secure communication equipment and classified IT systems at the level your clearance and training authorize — no workarounds, no shared credentials, no bringing personal devices into the SCIF or STE-equipped space.
• 06Complete the IS striker PQS lines your IS1 or ISC points you toward — the qual book is how the chain of command gauges whether you are ready for A-school designation.

• —COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual; the doctrinal foundation for every intelligence function the IS rating executes. Verify the current publication number against the Coast Guard Directives System before quoting it.
• —JP 2-0 — Joint Intelligence (the joint doctrine publication that establishes the framework all-source intelligence analysis operates inside; read Chapter I and II in your first 30 days to understand where the IS rating fits in the larger intelligence community).
• —Intelligence Community Directive (ICD) 203 — Analytical Standards (the ODNI-published standard for analytic tradecraft; every IS in the rating is expected to produce analysis that meets or exceeds these standards — read it before A-school).
• —COMDTINST M1000-series — Coast Guard Personnel Manual (the umbrella for leave, liberty, advancement, conduct, and everything on you as a member).
• —COMDTINST M1020.8 (current revision) — Coast Guard Weight and Body Fat Standards.
• —IS Rating Performance Qualification Standard (PQS) — the qual book from non-rate to IS3; do not wait for someone to hand it to you.

• —TS/SCI adjudication complete or in active processing — the IS rating requires a Top Secret clearance with SCI access; no class date at Dam Neck without it. Report any foreign travel, foreign contacts, or financial issues to your security manager proactively; hiding them is how adjudications fail after the fact.
• —IS A-school designation and a class date at NAS Dam Neck, VA (verify current school assignment via ALCGPSC); your EER blocks, PQS progress, and ISC endorsement are the inputs.
• —Zero classified handling incidents on your record — one spillage, one misrouted SECRET document, or one unauthorized disclosure removes you from the pipeline faster than anything else in the rating.
• —Coast Guard PFT passed every cycle per the current personnel manual standards; weight and body composition compliant with COMDTINST M1020.8.
• —IS striker PQS lines signed consistently; classified material accountability logs completed accurately on every shift the IS2 assigns you.

• —Handling a classified document outside of its authorized handling environment — even "just to show someone" — creates a spillage event. The security manager writes the report and the adjudicator reads it during your periodic reinvestigation.
• —Using a personal device, personal email, or unclassified network to transmit, photograph, or reference any classified information. One photo of a SECRET document on a personal phone is a federal crime, not an administrative mistake.
• —Self-reporting a foreign contact or foreign travel late because you were not sure it mattered. The security manager always wants to know; they decide what is reportable, not you. Late self-reporting looks intentional; intentional looks like a counterintelligence flag.
• —Updating an intelligence log entry after the fact to fix an error without flagging the correction to the supervising IS. Corrected entries in classified logs are documented as corrections — an un-noted alteration is an integrity finding.
• —Posting anything on social media that references your unit, your assignment to an intelligence billet, or your clearance status. The IS rating community is small and the DI/CI community reads social media; a post that compromises your cover assignment or your clearance program is a problem that cannot be walked back.

The good IS striker is the non-rate the IS2 trusts with the classified accountability log when the section is short-handed — because the entries are accurate, the classification markings are correct, the material is where it is supposed to be, and nothing has moved without a signature. By the time the A-school designation posts, the TS/SCI is in adjudication, the PQS is signed deep, and the ISC is writing the endorsement that gets this seaman a Dam Neck class date.

You are a rated intelligence petty officer. The crow says you completed the Dam Neck schoolhouse and you can produce an intelligence product — and a non-rate is watching every step you take in the SCIF to understand what the rating actually looks like.

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. You are producing or supporting intelligence products — port security threat assessments, maritime vessel-of-interest reports, drug/migrant flow analysis, counterterrorism threat products for a Sector Commander — under the IS2's review. You access JWICS and SIPRNet for collection tasking and product delivery, you post and retrieve from DHS Intelligence Enterprise systems and the USCG Intelligence Dashboard, and you learn the source types the IS rating works with: signals intelligence (SIGINT) summary products, imagery analysis (IMINT) reports from NGA, human reporting (HUMINT) passed from FBI or DHS I&A, and open source intelligence (OSINT) from government feeds. In garrison you run the classified material accountability program for your section, you write up port security or vessel threat assessments at the IS3 level under IS2 review, and you start the IS2 Servicewide Exam bibliography. The SWE is the gate to IS2 and the bibliography is not light — pull the current list from the Coast Guard Institute now, not three months before the exam.

• 01Produce a port security or maritime threat assessment product at the IS3 level — relevant, source-cited, properly classified, formatted to the current Coast Guard Intelligence Product Standards, and reviewed by the IS2 before release.
• 02Access JWICS and SIPRNet for collection requirements, incoming intelligence products, and finished intelligence dissemination — proper login and session security, no unauthorized cross-domain transfers, no personal-device bridge to the classified network.
• 03Apply ICD 203 analytical standards to your work — proper sourcing, appropriate analytic confidence language ("likely," "probably," "assess"), and no cherry-picking evidence to support a conclusion already reached.
• 04Maintain the section's classified material accountability log — receipt, storage, transfer, and destruction of classified material documented without gaps, because the annual classified material inventory is when every gap surfaces.
• 05Operate the USCG intelligence dissemination tools (verify current platform designations with your IS1 or ISC) at the IS3 access level — posting products to the right compartments, distributing to the right recipients, and not posting above your classification authorization.
• 06Train 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.

• —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; every IS3 who does not know ICD 206 produces products the IS2 has to rewrite).
• —JP 2-01 — Joint and National Intelligence Support to Military Operations (the joint doctrine for intelligence support in the operational environment the IS rating feeds into).
• —COMDTINST M1000-series — Personnel Manual sections on advancement, EER, and the Servicewide Exam process for IS2.
• —Coast Guard Rating Knowledge for IS (the rating-specific bibliography for the Servicewide Exam) — pull the current list from the Coast Guard Institute; the IS SWE bibliography covers IC-wide doctrine and is longer than most enlisted rating bibliographies.

• —TS/SCI maintained with no incidents; periodic reinvestigation window tracked and self-reporting current — foreign contacts, foreign travel, financial changes reported proactively to the security manager.
• —Qualified intelligence analyst or watch section contributor on at least the primary IS3-level product lane at your unit; secondary work in motion (vessel threat assessment, port security analysis, or collection tasking support depending on billet).
• —Coast Guard PFT passed every cycle; weight and body composition compliant with COMDTINST M1020.8.
• —Servicewide Exam preparation for IS2 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 every IS in the District network.
• —EER blocks clean and trending up; zero classified handling incidents or security violations on your record since designation.

• —Producing an intelligence product that states a conclusion as fact without sourcing it — "The vessel is likely being used for drug trafficking" with no collection basis is an unsourced assessment, not analysis. The IS2 returns it for rewrite and the Sector commander reads why.
• —Cross-posting an intelligence product at a higher classification than the underlying sources support. The product's classification is derived from its sources; fabricating a higher-classification shortcut to get a product disseminated faster is a violation.
• —Leaving a JWICS or SIPRNet session open and unattended when you step away from the terminal. The classified network session policy is lockout on exit — the IS2 who finds an open session with your username is writing the security violation report that afternoon.
• —Coasting on SWE preparation because "the IS community is small and the cutoff is usually reachable." Pull the current ALCGENL — in a small community, one missed study cycle translates directly to a missed advancement cycle, and the IS community does not have the depth to carry it.
• —Discussing current intelligence products, vessel-of-interest identities, or ongoing case subjects with unit personnel who are not cleared into the relevant compartment. Need-to-know is separate from clearance level; the IS2 who shared a TDP report with an uncleared BM because "he was on the boarding" is the IS2 in the CGIS investigation.

The good IS3 is the petty officer the IS2 puts on the morning port security assessment because the product will come back sourced, properly classified, and formatted right — not because it is flashy but because it is disciplined. The non-rates learn the accountability procedures by watching this petty officer. SWE study plan is on the desk, classified material log is current to the minute, and the IS1 is already talking to the ISC about which duty station broadens the record for the IS2 cutoff.

You are the working analyst and the watch floor's technical backbone. The IS3s learn the tradecraft by watching you apply it — and in a small rating, the standard you set now is the one your unit's intelligence products carry into federal prosecutions, Sector Commander briefings, and joint operation planning cells.

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. You produce and review finished intelligence products — maritime threat assessments, drug flow analysis, migrant route analysis, vessel-of-interest packages, counterterrorism briefings for Sector Commanders — at the IS2 level, and you review the IS3's products before they go out. You operate across JWICS, SIPRNet, and the DHS Intelligence Enterprise, pulling from SIGINT, IMINT, HUMINT, and OSINT sources to build all-source assessments. You run collection requirements through the appropriate channels, you coordinate with CGIS on intelligence-to-law-enforcement hand-off products, and you draft intelligence support plans for Sector or District operations. In garrison you write EER inputs on the IS3s and non-rates below you, you run the section's ICD 203/206 product quality standard, and you start the Servicewide Exam for IS1 in earnest. Joint intelligence center assignments — JIATF South (drug/migrant), the National Maritime Intelligence-Integration Office (NMIO), or USCYBERCOM/NSA billet — become realistic at this rank and are worth requesting if the career arc supports it.

• 01Produce 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, and deliver a product the Sector Commander can brief at his morning standup without the IS1 having to add corrections.
• 02Review 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.
• 03Draft 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 — understand the difference between a collection request and a finished product request.
• 04Coordinate 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.
• 05Operate JWICS and the DHS Intelligence Enterprise tools at the IS2 access level — post, retrieve, coordinate, and disseminate without cross-domain violations, and train the IS3 on the discipline the system requires.
• 06Write clean EER inputs on the IS3s and non-rates below you — observable behavior, measurable output, no inflation, no generic intel-community filler.

• —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; for joint billet assignments (JIATF South, NMIO, etc.) this is the operating framework.
• —COMDTINST M5520.12 (current revision) — Coast Guard Counterintelligence Manual; verify current pub number against the Directives System; know the CI reporting requirements that apply to IS rating billets.
• —COMDTINST M1000-series — Personnel Manual sections on advancement, EER, and the Servicewide Exam process for IS1.
• —CIM 1610-series — Enlisted Employee Review (EER); you write inputs now and need to understand how the EER mark and supervisor narrative drive the SWE final multiple.

• —TS/SCI maintained; all periodic reinvestigation and continuous evaluation requirements met; zero incidents in your clearance history since designation.
• —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.
• —EER marks at or near the unit average; inputs from the IS1 and ISC are the variable, and the IS rating writes EERs that the Intel community can read alongside DIA/NGA products.
• —Servicewide Exam for IS1 taken on cycle with a bibliography-driven study plan; pull the current ALCGENL / CGPSC promotion message for the IS SWE cutoff.
• —PFT passed; body composition compliant; zero security violations — the IS community is small and the ISC slate sees everything.

• —Allowing a JWICS product's source references to be removed or generalized before handoff to the IS3 as a "training shortcut." The IS3 learns analytic tradecraft by working with real sourcing; removing it to simplify the exercise produces an analyst who cannot source independently.
• —Submitting a maritime threat assessment that conflates open-source vessel movement data with a classified source report without distinguishing the two in the sourcing. A product that mixes classification levels without proper handling instructions is a spillage waiting to happen and an ICD 206 violation.
• —Verbal corrections on IS3 product quality instead of written product review notes and EER inputs. The ISC and the District intelligence officer need documented evidence of your supervisory role in the product review chain — verbal-only guidance is invisible at the promotion board.
• —Skipping the ICS documentation on a multi-agency maritime intelligence operation because "we handled the coordination verbally." The CGIS hand-off and the joint operation record both trace back to the written coordination package.
• —Letting your JWICS or SIPRNet account go inactive because TDY or deployment interrupted your access routine. An account that goes dormant triggers an automatic audit; the security manager notifies the IS1 and the unit security officer.

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 the NIPR/SIPR boundary. The IS3s are getting product review notes they can act on, the SWE bibliography is not a list but a schedule, and the IS1 is already talking to the ISC about which joint intel billet fills the career gap before the IS1 cutoff.

You are the senior analyst and the unit's walking intelligence tradecraft authority. The ISC holds the people; you run the product — the assessments, the collection requirements, the joint coordination, and the IS2s who put the Sector Commander's briefing together every morning.

You are typically the senior analyst at a District Intelligence Branch, the senior IS at a Sector intelligence element managing IS2s and IS3s, the senior IS at a joint intelligence center billet (JIATF South, NMIO, NSA-adjacent), or the senior Coast Guard IS at a DHS Intelligence Fusion Center. You produce the most complex products your unit runs — all-source assessments for District Commander or Area Commander level, intelligence support plans for major MLE operations, threat packages for port-security infrastructure assessments — and you review everything the IS2s produce before it goes to the consumer. You run the unit's ICD compliance program, manage the collection requirements process, and coordinate intelligence product handoffs with CGIS, FBI, DEA, CBP, and NSA as the senior enlisted liaison. You sign IS2 qualification recommendations to the ISC and you write the bulk of the EER inputs for the IS2s and IS3s below you. The ISC preparation is now a real conversation: EER profile, awards stack, leadership C-school per CGPSC requirements, the broadening assignment that rounds out the record, and the chiefs' mess sponsorship conversation.

• 01Produce and deliver an all-source intelligence assessment to the District Commander or Area Commander level — all-source integration across SIGINT, IMINT, HUMINT, and OSINT, sourced to ICD 206, assessed to ICD 203, formatted and delivered in a brief the commander can present to a joint operations center without the IS1 in the room.
• 02Run the unit's ICD 203/206/208 product compliance program — establish product review standards, audit IS2 and IS3 products before external dissemination, and brief the ISC on quality trends without waiting for a consumer complaint.
• 03Manage a collection requirements package through DHS and ODNI channels for a named intelligence gap affecting your District or Area's MLE, counterterrorism, or port security mission — know the difference between what CG can task and what requires a higher-level RFI.
• 04Coordinate a joint intelligence operation or multi-agency MLE intelligence support package with CGIS, FBI, DEA, and CBP as the senior IS liaison — the evidence-handling discipline, the classification coordination, and the product delivery that keeps a federal case intact.
• 05Mentor two-to-three IS2s into IS1-SWE-competitive candidates — study plans, EER blocks, joint billet recommendations, and the clearance reinvestigation timeline that needs to be managed proactively.
• 06Brief the ISC and the District intelligence officer on the unit's product output, collection gaps, and personnel readiness honestly — including the gaps — before those gaps surface in a District inspection or a joint partner complaint.

• —COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual; you are the unit's walking authority on this publication at the IS1 level.
• —ICD 203, ICD 206, ICD 208 — you run the section's compliance against all three; verify current ICD numbering and titles against the ODNI Directives Library before quoting them in a product.
• —COMDTINST M5520.12 (current revision) — Coast Guard Counterintelligence Manual; CI reporting requirements at the IS1 level are more than awareness — you advise IS2s and IS3s on what to report and how.
• —JP 2-01 — Joint and National Intelligence Support to Military Operations; at joint billet level or District IS1 level, this is the operating framework for multi-agency intelligence support.
• —CIM 1610-series — Enlisted Employee Review (EER); you write the bulk of inputs for IS2s and IS3s and you read the ISC's draft of your own.
• —COMDTINST M1000-series — Personnel Manual sections on advancement, the Servicewide Exam, and the Service-Wide Personnel Board process for E-7 selection.

• —TS/SCI maintained with continuous evaluation requirements met; CI reporting posture current for your billet type; zero clearance incidents — at the IS1 level a security incident is career-defining, not just career-complicating.
• —Qualified primary analyst or senior IS at your unit's main product lane; joint intelligence center qualification or NMIO/JIATF South-equivalent exposure on the record or on the calendar.
• —IS1 EER profile at the top of the unit's IS1 cohort across multiple periods; the ISC board reads the trend across assignments, not just the most recent mark.
• —Service-Wide Personnel Board / ISC selection competitive — pull the current CGPSC ALCGENL for the ISC slate cycle; the IS community is small enough that the messages name the composition of the slate openly.
• —Leadership C-school completed per CGPSC requirements for the ISC selection slate — verify current requirements against the active ALCGENL before quoting a specific course.

• —Signing an IS2 product review clearance because the product "looks right" without checking the ICD 206 sourcing and ICD 203 analytic language line by line. The federal attorney and the joint partner consumer both read the sourcing; the IS1 who cleared a product with an unsourced key judgment is the IS1 the ISC calls when the complaint arrives.
• —Letting an intelligence product go to a joint consumer at a classification level not supported by the sources cited, because the operational tempo was high and the IS2 seemed confident. Classification is not an operational variable — it is either supportable or it is not.
• —Carrying verbal-only coordination with CGIS or a federal LE partner on an intelligence hand-off. The AUSA reads every coordination document; if the hand-off exists only as a conversation, the hand-off does not exist in the case record.
• —Confusing being the senior technical IS with being aligned with the ISC. The District needs you to push back in the office — on a product quality call, a collection requirement that exceeds authority, a billet decision that leaves the unit understaffed — before the problem surfaces publicly, not after.
• —Skipping the leadership C-school because the operational tempo makes the absence feel impossible to justify. The ISC slate reads the record; the leadership education block is one of the blocks, and the IS community is small enough that a gap there is a gap the slate notices.

The good IS1 is the senior analyst the District intelligence officer puts on the most complex joint product — the all-source maritime threat assessment that has to hold up under JIATF South scrutiny and brief cleanly to the Area Commander — because the sourcing will be right, the analytic language will meet ICD 203 standards, and the classification coordination will be clean. The IS2s under this first class produce products without constant supervision. The collection requirements process runs on time. The ISC is sponsoring the chief packet because the record reads as a senior intelligence leader, not just a disciplined analyst.

You are an anchor in a rating that most of the Coast Guard has never met. The Chiefs Mess is a brotherhood and a sisterhood, and the intelligence posture of the District reads by what you hold as the non-negotiable standard on product quality and clearance integrity.

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. You went to the Chief Petty Officer Academy (CPOA) at TRACEN Petaluma, CA when your initiation cycle pinned you, and the job changed more between IS1 and ISC than at any other transition in the rating — you are now responsible for the intelligence section's culture, product quality, clearance integrity program, and the senior-enlisted interface with the District Commander, not just the analysis. You write EERs on the IS1s and IS2s below you, you advise the District intelligence officer on every enlisted IS-workforce decision, and you sit in the IS chief network — small enough that every ISC at your paygrade knows every other ISC by name and by the quality of the products coming out of their section. You manage the unit's relationship with the DHS Intelligence Enterprise, NMIO, and the joint partners (FBI, DIA, NSA) that require sustained trust to produce real product. You also start senior chief preparation in earnest: the Senior Enlisted Leadership Course (SELC), the broader senior billet tracks (ISCS at Area or CG HQ, joint senior intelligence billet), and the 36-48 month post-Coast Guard credential conversation — DHS I&A civilian analyst, DIA contractor, NGA mission partner role, or federal civilian intelligence officer pipeline.

• 01Run 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.
• 02Mentor three-to-four IS1s into ISC-board-competitive candidates — EER trajectory, joint billet recommendations, clearance reinvestigation timeline, leadership C-school, awards profile, and the chiefs' mess sponsorship conversation that decides whether the chief packet is competitive.
• 03Brief 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.
• 04Coordinate the unit's intelligence support to major CG operations — MLE surge, counterterrorism port security operation, joint drug interdiction — at the senior enlisted planning cell level, with the product delivery and collection coordination documented to a standard the joint partner trusts.
• 05Sit in the Chiefs Mess on the unit's discipline cases, the climate posture, and the EO/sexual assault prevention picture, and translate those into actions the District Commander will fund and the IS1s will execute.
• 06Walk 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 the archived product, the JWICS account that has not been audited — before the District security officer finds it.

• —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.
• —CIM 1610-series — Enlisted Employee Review (EER); your bullets pick the next slate at the District.
• —COMDTINST M1000-series — Personnel Manual; you and the District intelligence officer own the enlisted IS-workforce compliance together.
• —Coast Guard Administrative Investigations Manual (verify current pub) — security investigations, product mishandling events, and clearance-related administrative actions at the unit level run through the ISC and the District security officer.

• —Chief Petty Officer Academy (CPOA) at TRACEN Petaluma, CA completed; Senior Enlisted Leadership Course (SELC) on the calendar if competitive for senior chief.
• —TS/SCI maintained; CI awareness program posture current; annual product accountability and classification review clean — no TS/SCI handling findings attributable to your section during your tenure.
• —Section EER profile clean — IS1s and IS2s under you are advancing on schedule and your bullets are consistent with what the District IS chief network knows about the section.
• —Joint intelligence center qualification or NMIO-equivalent on the record or recently completed; the ISCS board reads breadth of assignment, not just depth at one Sector.
• —Zero senior-enlisted integrity incidents — financial, fraternization, clearance mishandling, product fabrication. The IS rating is small and one incident ends the career and the clearance simultaneously.

• —Letting the classified material accountability program drift during a sustained operational tempo because "we'll catch up after the operation." The TS/SCI annual inventory is not a negotiable deadline; the gap that surfaces on the inspection was created during the tempo, not after it.
• —Going public with disagreement with the District intelligence officer or the Area intel staff. You take it in the office; you walk out aligned, and the rating reads alignment from the anchor.
• —Inflating EER blocks on a technically strong IS1 whose analytic judgment is thin under pressure. The ISCS board and the joint intel community partners read those evaluations — inflated bullets on a one-dimensional record are identified and discounted.
• —Stopping your personal analytic tradecraft currency because "I'm a chief now." The IS section respects the ISC who can still review an ICD 203-compliant all-source product and identify the sourcing weakness — not just one who managed people who used to do it.
• —Treating the joint partner relationships with JIATF, DIA, NSA, and FBI as purely operational. The relationship management — the debrief after a successful joint product, the proactive notification when a classification or sourcing issue surfaces in an archived product — is what keeps those partnerships functional when you need them at 0200.

The good ISC is the chief the District intelligence officer calls when the Area Commander wants to know what disciplined maritime intelligence analysis looks like — because the products hold up under NMIO and DIA review, the IS1s produce all-source assessments the joint partner reads without corrections, and the classified accountability posture would survive an unannounced CI inspection. The IS1s pin ISC; the IS2s pin IS1; the ISCS is sponsoring the next chief packet. When this ISC leaves the District, the ICD compliance standard does not leave with them — it stays because they built it into the people.

You are the standard for the rating. Every ISC knows your name; every IS2 is reading your career to decide whether this small, clearance-dependent, barely-visible rating is worth making a career — and every intelligence failure or success that the Coast Guard produces traces back to the analytical culture you built.

As ISCS you are typically the senior IS chief at an Area intelligence coordination cell, the senior CG IS at NMIO (National Maritime Intelligence-Integration Office), a senior IS presence at a joint intelligence command (JIATF South, NSA, or DIA-adjacent CG billet), or the senior IS enlisted advisor at Force Readiness Command or Coast Guard headquarters intelligence staff. As ISCM you are on the Command Master Chief track — at a major District headquarters, FORCECOM, the CG Intelligence and Criminal Investigations Command (CGICICOM), Atlantic Area or Pacific Area command, or Coast Guard headquarters — and your name is on the slate the service reads at the senior-enlisted council. You advise the Area Commander, the District Commander, or the Commandant's intelligence staff on every enlisted IS-workforce decision, and you set the standard for the rating by what you hold as non-negotiable in product quality, clearance integrity, and analytic tradecraft. You sit in the ISCS/ISCM network, the Senior Enlisted Council, and the slate-board preparation that picks the next ISCS and ISCM cohort. You are also planning the post-Coast Guard market explicitly — 24-36 months out — because the ISCS/ISCM credential translates cleanly into DHS I&A senior analyst, NMIO civilian intelligence officer, DIA mission partner support role, NGA maritime-domain analyst, NSA maritime intelligence contractor, or federal civilian GS-0132 (Intelligence Analyst) series roles, and the senior enlisted who plan it land in senior positions rather than starting over.

• 01Run the IS enlisted workforce program at Area or Coast Guard headquarters scope — product quality standards, ICD compliance posture, TS/SCI accountability, collection requirements management, joint partner relationship health, and the senior-enlisted interface with the Area Commander or the Commandant's intelligence staff on every workforce decision.
• 02Mentor four-to-six ISCs into ISCS-board-competitive candidates — EER trajectory, joint billet sequencing, clearance reinvestigation timeline management, broadening assignments (NMIO, JIATF South, DIA billet, CGICICOM), and family stability across the billets that build competitive records.
• 03Sit on an IS rating community-manager board or advise the CGPSC community manager on IS-specific workforce issues — billet distribution, joint assignment pipeline, clearance throughput, retention incentive targets — and translate community needs into slate decisions the rating lives with for years.
• 04Brief the Area Commander, District Commander, or Commandant's intelligence staff on IS enlisted product posture, analytical quality trends, clearance status of the force, and the things they cannot see from the senior staff conference room — the collection gap being papered over by open-source substitution, the joint partner complaint that has not reached the flag yet, the IS1 retention problem driven by clearance reinvestigation delays at a specific command.
• 05Walk the product archive of a subordinate IS section during a joint inspection or TS/SCI review and identify the systemic analytical error — the sourcing pattern that shows the IS2 is not actually applying ICD 206, the classification marking error buried in 40 products, the collection requirement that has been re-submitted three times without a response because nobody owns the follow-up.
• 06Sit in the senior-enlisted community-manager and post-service credential conversation with junior ISCs honestly — the DHS I&A civilian analyst path, the NMIO civilian position, the DIA/NGA contractor route, the federal GS-0132 intelligence officer pipeline — because the IS rating loses senior talent who do not plan, and the ISCM is the one who models the transition.

• —COMDTINST M3100.4 (current revision) — Coast Guard Intelligence Manual; you are the rating's senior authority on this publication at command scope.
• —ICD 203, ICD 206, ICD 208 (verify current ICD titles and numbers against the ODNI Directives Library) — you set the compliance standard at Area or headquarters scope.
• —COMDTINST M5520.12 (current revision) — Coast Guard Counterintelligence Manual; CI program posture at your command runs through you.
• —CGPSC ALCGENL and ALSPO messages — pull the current IS slate composition and community-manager guidance; the IS community is small enough that the messages reflect the entire senior-enlisted picture.
• —CIM 1610-series — Enlisted Employee Review (EER); your bullets pick the next ISC and ISCS slate.
• —The Senior Enlisted Leadership Course (SELC) reading list and the Command Master Chief professional development curriculum from TRACEN Petaluma, CA — continuing development as a senior Coast Guard leader, not only as an intelligence professional.

• —Senior Enlisted Leadership Course (SELC) graduate; Command Master Chief at a District headquarters, FORCECOM, CGICICOM, or Area command — the visible senior-enlisted track for the rating's most senior seats.
• —TS/SCI maintained; CI awareness and reporting posture current at command scope; zero clearance incidents under your tenure at any billet.
• —Command IS product quality and ICD compliance posture — TS/SCI inspection and joint-partner-equivalent review findings effectively zero during your tenure; documented corrective action when process gaps surface.
• —Command EER profile clean; ISCs and IS1s advancing on schedule; bullets consistent across multiple periods and consistent with what the NMIO/DIA/JIATF partner network knows about the section's product quality.
• —Zero senior-enlisted integrity incidents — financial, fraternization, clearance mishandling, product fabrication. The IS community is too small and too closely watched by joint intelligence community partners to absorb a senior-enlisted integrity failure.

• —Going public with disagreement with the Area Commander, the District intelligence officer, or the Commandant's intelligence staff on a product call or a workforce decision. You take it in the office, make the case clearly, document the recommendation, and walk out aligned. The rating reads what the senior chief tolerates at this paygrade.
• —Confusing seniority with analytic authority. The ICD standards, the classification system, and the collection management process change as the IC evolves. The IS2 who completed the most recent NMIO joint assignment knows that corner of the analytic tradecraft better than you do. Let them brief it and stand behind them; the joint partner network sees who is honest about the gap.
• —Stopping active engagement with the IS workforce's product quality because "I'm at headquarters now." The Area ISCS and the ISCM who cannot still review an all-source product for ICD 203 compliance and identify a sourcing weakness lose the ability to identify the broken process before the joint partner complaint arrives.
• —Letting an ISC run a degraded ICD compliance posture at a subordinate unit because "the ISC has it handled." The NMIO or DIA partner reads every product the section disseminates; the first product that generates a joint-community sourcing complaint traces to the senior enlisted who accepted the standard that produced it.
• —Treating the warm-up to retirement as if the job is over. Until you walk out of formation for the last time, the rating is still your job — and the rating reads what you tolerated in your last two years more than what you built in your first twenty.

The good ISCS and ISCM is the senior enlisted every IS in the service knows by face and reputation — not for the clearance stack but for the analytic standard the products carry. The joint intelligence community partners trust the products coming out of Coast Guard intelligence because this senior chief built the ICD compliance culture that made them trustworthy. The ISCs pin ISCS; the ISCSs pin ISCM. The Area Commander and the District Commander trust the ISCM with the hardest intelligence product problem at 0200 and the most sensitive workforce decision at 0900. When the anchor walks out of formation for the last time, the IS2 who writes next week's all-source maritime threat assessment sources it correctly, assesses it honestly, and delivers it clean — because someone built the section that way.