Cryptologic Technician (Technical)

You are a pipeline Sailor on the SIGINT technical track. The clearance investigation owns your timeline more than you do, and the technical training pipeline will show you — fast — whether you actually want to think about signals for a living.

After RTC Great Lakes you head to CTT A-School at the Center for Information Warfare Training (CIVT), Corry Station NAS Pensacola. A-School covers foundational SIGINT concepts, electronic warfare theory, signal characterization, and the IC tradecraft framework your whole career will sit on. The clearance investigation — TS/SCI with a CI polygraph — is running in parallel and gates every operational billet you will ever hold; anything that contaminates the SF-86 delays everything downstream. Before the clearance adjudicates and before you complete the follow-on training pipeline (verify the current follow-on course structure with CIVT before quoting specific course names or lengths), you are a student before you are an operator. You attend class, you study signals theory and the analytic standards in ICD 203 and 206, you keep your security paperwork clean, and you do PT on the school's schedule. Your first operational billet will be at a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, a joint SIGINT site, or an NSA-affiliated command depending on community needs and your NEC assignment — say goodbye to the deckplate-at-sea picture and get used to a SCIF and a workstation.

• 01Live inside clearance hygiene from day one: proper handling of classified spaces, materials, and conversations, nothing outside the SCIF, foreign contacts reported on the timeline the security officer sets.
• 02Absorb the foundational signals theory the A-School curriculum builds on — frequency, modulation, waveform characteristics, EW spectrum basics — because the CTT community does not re-teach what the schoolhouse assumed you retained.
• 03Study the IC analytic standards framework: ICD 203 (Analytic Standards), ICD 206 (Sourcing), ICD 208 (Reporting) — you will produce against all three from the first day at an operational billet.
• 04Knock out PQS and foundational quals on the LPO's timeline once you check in; the slow CTTSN becomes the slow CTT3 candidate.
• 05Earn the baseline DoD 8140 cyber/intelligence-workforce certification your billet requires before the team lets you sit the position — Navy COOL funds the voucher; do not leave it on the table.
• 06Keep a clean CAC, clearance-paperwork, and administrative record from day one — the CTT community is small, the investigation is long, and a single unexplained gap turns into a six-month adjudication delay.

• —CIVT / NETC — Center for Information Warfare Training catalog (netc.navy.mil); verify the current CTT A-School and follow-on course structures before quoting them.
• —ICD 203 — Analytic Standards (ODNI) — the IC tradecraft standard your analysis will be measured against.
• —ICD 206 — Sourcing Requirements for Disseminated Analytic Products.
• —ICD 208 — Intelligence Community Reporting.
• —OPNAVINST 2201.3 — Navy Signals Intelligence / Electronic Warfare coordination instruction.
• —NAVPERS 18068 Vol II — Manual of Navy Enlisted Manpower and Personnel Classifications (NEC catalog; pull the CTT-series NEC entries and the current source-rating NAVADMIN before talking to the career counselor).

• —TS/SCI clearance adjudicated with CI polygraph completed — no clearance, no seat, no career in this rating. Anything that delays the investigation delays everything.
• —A-School completion and follow-on pipeline qualification on the timeline CIVT and your command set — the student who recycles or disenrolls is visible in the community and the LPO at the first operational command will know.
• —Baseline DoD 8140 cyber/intelligence-workforce certification earned before the operational billet requires you to sit the position.
• —PRT Good Low or higher; BCA in standard. Technical intelligence is a SCIF-and-workstation career, but the Navy still runs the test.
• —Annual security awareness and cybersecurity training completed before every deadline — in a TS/SCI community a careless lapse is a reportable incident, not a paperwork miss.

• —Treating the A-School schedule as relaxed because the classroom is air-conditioned. The technical content accelerates fast and the community's senior operators know within the first deployment rotation which CTTs actually built the foundation.
• —Letting the clearance investigation develop surprises — undisclosed foreign contacts, undisclosed financial issues, social media that contradicts the SF-86. The investigators will find it; the lie kills the clearance faster than the underlying fact.
• —Discussing the pipeline content, the assignment track, or anything signals-related on personal devices or social media. OPSEC is the product in this community; one sentence is the negligent discharge.
• —Plugging unauthorized media into a school or training system. The incident-response ticket lands on the instructor's desk that afternoon and your name is on the report up the chain.
• —Coasting on "I scored well on the ASVAB." Technical aptitude gets you into A-School; daily work keeps you there.

The good CTTSN is the student whose clearance paperwork never delays the team, whose security officer knows the name because foreign-contact reports were timely — not because of a problem — and whose A-School performance sets a baseline the LPO at the first operational billet can build on. The technical foundation is solid, the OPSEC discipline is already habit, and the assignment to the first fleet billet arrives without any administrative flags waiting in the file.

You are a petty officer now, and the signals are real — real collection, real analysis, real reporting deadlines, and a senior CTT who is about to find out how well the schoolhouse actually prepared you for working traffic.

You have completed A-School, the follow-on pipeline, and you have checked aboard your first operational billet — a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, an NSA-affiliated site, or a deployed SIGINT support element depending on your NEC assignment and community priorities at the time of orders. The work is signals technical analysis: you characterize electronic emissions, identify emitter types, apply parametric analysis techniques, and contribute to ELINT and SIGINT reports that go up the chain and into joint IC products. The difference between the classroom and the operational billet is immediate — the collection environment is messier, the reporting standard is tighter than the student version, and the senior CTT reviewing your work products will tell you in the first week whether your analysis is defensible. You study for the next NWAE cycle, you execute the LPO's qual plan, you keep your clearance posture clean, and you learn quickly that producing at the pace the section runs requires discipline the schoolhouse did not fully simulate.

• 01Characterize and analyze electronic emissions using the parametric analysis techniques the platform employs — frequency, pulse characteristics, scan patterns, waveform parameters — to the accuracy level the senior CTT can sign off without rework.
• 02Write a SIGINT or ELINT technical report that meets ICD 203 Analytic Standards and ICD 208 reporting format — source-cited, analytically honest about uncertainty, formatted for dissemination.
• 03Operate the section's collection and analysis tools to the proficiency level your work-role qualification requires — tool-specific training is command-dependent, but the principle is consistent: you do not sit a position until you are qualified on it.
• 04Run a clean SCIF watch: proper handling of classified material and system access, no unauthorized output, end-of-shift cleanup to the command SOP standard without the LPO checking the space.
• 05Study for the CTT2 NWAE on the LCPO's study schedule — the BIB is published by NETC / MyNavyHR; pull it and own it from the first watch cycle.
• 06Report foreign contacts, financial changes, and continuous-evaluation events to the security officer on time and on record — at CTT3, clearance hygiene is no longer someone else's job.

• —ICD 203 — Analytic Standards; ICD 206 — Sourcing; ICD 208 — Reporting (your analysis product is evaluated against all three from day one at the operational billet).
• —OPNAVINST 2201.3 — Navy SIGINT / EW coordination; the instruction the command-level SIGINT reporting chain operates under.
• —NAVPERS 18068 Vol II + the current CTT NEC source-rating NAVADMIN — pull it before talking to the career counselor; CTT NEC codes reflect technical specialization and assignment paths.
• —DoDD 8140 / DoDM 8140.03 — Cyberspace Workforce Qualification (the work-role chart your billet may be mapped to; verify the current mapping for CTT billets with your command).
• —NWAE Bibliography for Advancement (BIB) for CTT2 — pull from MyNavyHR / NETC; the BIB is the test and the test is the BIB.
• —SECNAVINST 5239 series — DON Cybersecurity / IA Program (the umbrella your system access and clearance live under).

• —Qualified on at least one operational position at the section and standing it without the senior CTT reworking the watch turnover.
• —NWAE for CTT2 prep documented on the LCPO's timeline; BIB study log defensible before the exam window opens.
• —Analysis products meeting the section's production quota without the senior CTT editing for analytic completeness on every submission.
• —PRT Good Medium or better; BCA in standard.
• —Clearance and continuous-evaluation status clean — periodic-reinvestigation paperwork submitted on time, no security flags waiting in the security officer's inbox.

• —Submitting an analysis product with gaps you papered over to hit the production quota. In the IC, a report that looks complete but omits a critical uncertainty is worse than an honest "analyst note: insufficient data to characterize." Your senior CTT and the customer both notice.
• —Touching a system or running an analytic tool you have not been qualified and authorized on. In this community there is no "I was exploring" — unauthorized access to a mission system is a security incident, not initiative.
• —Letting the clearance investigation develop surprises at the periodic-reinvestigation cycle. At CTT3 the initial investigation is behind you; the continuous-evaluation framework is now the regime, and a foreign contact or financial event not reported on time does not look like an oversight.
• —Treating the NWAE study schedule as optional because the community is small. The slate spots are real and the senior CTTs know exactly which CTT3 is coasting on the assumption that small-community competition means low bar.
• —Discussing the technical work — emitter types, collection techniques, assignment details — in common areas, off the watch floor, or on personal communications. The OPSEC officer reads the sweep reports.

The good CTT3 is the petty officer the LPO puts on the harder collection because the write-ups come back analytically honest, the watch turnover needs no editing, and the clearance has never generated a 0300 call to the security officer. The BIB study log is real, the work-role certification is current, and the LCPO is already mentioning the name when the CTT2 NWAE slate comes around.

You are the working senior technical analyst — the section LPO in fact even when the billet title does not say it yet. The CTT3s measure their standard against yours, and the chief is already thinking about anchors.

You run a section or an analytic cell on a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, or an NSA-affiliated site. You own a portion of the section's production output, you train and qualification-sign two-to-four CTT3s, you build the section's training plan and execute the LPO's schedule instead of just attending it, and you write the shift-handoff brief the senior CTT and the duty officer read without rewriting. The analytic work deepens: you are producing finished ELINT and SIGINT technical reports that go to the IC customer chain, you are the section's secondary expert on at least one emitter family or signal type, and you are being asked to QA junior products before they route up. The NEC conversation is real now — technical specialization within the CTT community, the career-path choices that come with it (community assignment, joint-duty options, NSA technical staff, the path toward senior technical expert billets), and the honest CTT1 NWAE prep that the LCPO is tracking. eEVAL ranking against your peer CTT2s starts to matter for the next slate.

• 01Lead a section shift — production quota, QA review of CTT3 analytic products, escalation of significant intelligence to the senior CTT and the reporting chain, clean handoff without the LCPO rewriting the turnover.
• 02Produce finished ELINT and SIGINT technical reports to ICD 203/206/208 standards at a quality level your senior CTT signs without analytic revision — source-cited, uncertainty characterized, dissemination controls applied correctly.
• 03QA a CTT3 product for analytic completeness and format compliance — identifying the gap in a junior's analysis constructively is a technical skill, not just a supervisory one.
• 04Build and run a section training plan: qualification timelines, NWAE study accountability for CTT3s, DoD 8140 certification tracking, and the clearance and continuous-evaluation posture for your juniors.
• 05Write CTT3 eEVAL inputs that name observable behavior, production metrics, analytic contribution, and collection posture — specific enough that the senior rater can defend them without generalizing.
• 06Counsel a CTT3 honestly on career-path choices: NEC specialization, re-up vs ETS, joint-duty options, the technical expert track vs the leadership track, and what the CTI/CTR community crossover looks like if that conversation comes up.

• —ICD 203, 206, 208 — you are producing finished product to these standards and QA-reviewing CTT3 products against them.
• —OPNAVINST 2201.3 — Navy SIGINT / EW coordination; fluent in the reporting and coordination chain that governs your section's output.
• —NAVPERS 18068 Vol II + the current CTT NEC source-rating NAVADMIN — build career counseling off the current edition.
• —DoDM 8140.03 — Cyberspace Workforce Qualification (verify which work-role the CTT community maps to in your command's billet structure; the mapping is evolving).
• —NWAE Bibliography for Advancement (BIB) for CTT1 — pull from MyNavyHR / NETC; own it on a study plan with milestones.
• —SECNAVINST 5239 series and your command's SCI compartment access management policies — you are responsible for the section's access posture now, not just your own.

• —Section production quota met at or above command average without the senior CTT reworking the shift handoff.
• —NWAE for CTT1 prep on the LCPO's timeline; eEVAL trait average and ranking that supports an EP or MP recommendation — the LCPO knows your number before the EVAL board reads it.
• —At least one DoD 8140 work-role certification maintained and the next one identified — the CTT2 who stopped qualifying is the CTT2 who stopped advancing.
• —PRT Good High or better; BCA in standard; warfare device pinned where the billet and platform allow.
• —Section clearance and continuous-evaluation status clean — no junior on your watch parked off a seat for a reporting lapse you could have caught.

• —Letting a CTT3's analytic gap pass unremarked in the QA review because you did not want to write the counseling. The next production review finds the pattern; the senior CTT finds the gap; the CTT2 who knew and said nothing is the one explaining it.
• —Signing off on a product with a significant analytic uncertainty you reduced or concealed to hit the production quota. In the IC an analytically incomplete product that looks complete is worse than one that says so.
• —Bypassing the LCPO to talk to the front office or an NSA liaison about a production or career issue. The CTT community is small and the goat locker is smaller; the LCPO hears about it the same day.
• —Treating the clearance posture for your juniors as the security office's problem. You are the section lead; a foreign-contact or financial-disclosure gap on your watch that you could have caught is your gap.
• —Letting DoD 8140 certification currency lapse on yourself or a junior without flagging it. The team gets pulled off positions at the worst possible time and the gap has a name on it.

The good CTT2 is the petty officer the LCPO names when the senior CTT asks who is running the hard watch — because the products will come back analytically honest, the CTT3s will be supervised, and the section's clearance posture will not move in the wrong direction while he is on watch. His eEVAL bullets are specific and defensible, his CTT3 is tracking toward a CTT1 slate, and the CTT community knows his name for the right reasons before the NWAE slate closes.

You are the LPO. The chief is editing your Chief packet; the command intelligence officer calls you by name; the CTT2s and CTT3s watch how you carry the division the way you used to watch your chief.

You are LPO of a SIGINT technical division or a senior analytic cell at a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, an NSA-affiliated site, or a deployed SIGINT support element. You write four-to-six eEVALs per cycle for CTT2s and CTT3s that pick the next NWAE slate. You build the division's training and production plan, defend the section's analytic readiness at the command intelligence sync, manage DoD 8140 compliance and clearance posture at the division level, and own the production output the front office and the IC customer chain brief. You mentor at least one Sailor a year into the next accession: a Warrant Officer path (verify current Warrant accession messages for the CT community), LDO/CWO application, NSA technical-staff competitive assignment, or the senior-NEC and specialization tracks that open at CTT1. The Chief board packet conversation is no longer abstract — your LCPO is editing your record, your eEVAL profile is being built across the year, and how you carry the analytic standard every day in front of the division matters more than any single technical qualification you have earned.

• 01Run a division-level production and readiness conversation: who is qualified on which position, where the analytic gaps are, how you close them — presented to the command intelligence officer without the senior chief rewriting the brief.
• 02Defend the division's analytic output, DoD 8140 compliance, and clearance posture at command-level sync — own the gap, present the closure plan, hit the milestone.
• 03Build and execute a training and certification plan that produces technically capable CTT2s and CTT3s — not just bodies covering positions, but operators whose products survive IC-customer scrutiny.
• 04Operate as the senior technical analyst voice during a real-world collection event or a higher-echelon assessment — including the honest call up the chain when the analytic picture has actually shifted.
• 05Translate IC analytic standards — ICD 203/206/208 — into the daily production standard the section runs to, and brief gaps honestly to the front office when the collection environment does not support the standard.
• 06Mentor a CTT2's NWAE / NEC / Warrant / LDO packet from idea to selection — and counsel honestly when the path is wrong for the Sailor.

• —ICD 203, 206, 208 — you defend the division's production against these standards at every IC customer review.
• —OPNAVINST 2201.3 — Navy SIGINT / EW coordination instruction; you are the technical voice the command intelligence officer cites.
• —DoDI 8500.01 — Cybersecurity; DoDM 8140.03 — Cyberspace Workforce Qualification (you audit the division's compliance against the current work-role mapping).
• —SECNAVINST 5239 series; the current OPNAV Navy cybersecurity / IA program instruction — pull the current version; you are quoted from it more often than you quote it.
• —NAVPERS 18068 Vol II + the current CTT NEC source-rating NAVADMIN and the current Warrant / LDO accession messages — you build career pipelines off the live cycle.
• —MILPERSMAN — the articles governing advancement, retention, separation, and NJP at CTT1-level visibility; fluency here is what separates the LPO from the senior petty officer.

• —Chief board packet under construction with the LCPO's eye on every line; eEVAL profile defensible at the command level.
• —Division production and analytic readiness defensible at the command intelligence officer and CO level — every cycle, no caveats.
• —DoD 8140 work-role compliance across the division clean; no position uncovered because a certification lapsed on your watch.
• —Pipeline output — Warrant, LDO/CWO, senior NEC, NWAE — producing at least one selectee per year from your division.
• —Clearance posture across the division clean — no junior parked off a seat because a reinvestigation or continuous-evaluation flag was left to rot.

• —Briefing production or readiness numbers you have not personally validated. The command intelligence officer catches it once and your Chief packet feels it permanently.
• —Letting a senior CTT2 carry the DoD 8140 compliance tracking because "he is your guy." When he transfers the gap surfaces and the LPO's name is on the finding.
• —Confusing seniority with current technical depth. The CTT2 may know the newest collection tool or the updated analytic technique better than you do — let him brief it and stand by him; the LCPO sees who is honest about the gap.
• —Going around the LCPO to the front office, the command intelligence officer, or the NSA technical liaisons. The CT community is small and the goat locker is smaller; the Chief board sees the pattern.
• —Treating clearance posture as the security office's problem. You own enlisted execution; a division that loses a position to a preventable clearance lapse is a readiness gap with your name on it.

The good CTT1 is the LPO the LCPO trusts to run the division for a week without daily check-ins. His production numbers brief without caveat; his eEVALs pick operators above expectation; his pipeline produces Warrant, LDO, and senior-NEC packets the command signs without rewriting; and his division never goes short a qualified operator because a clearance or certification was neglected. He sits the Chief selection board with a record that reads itself.

You are a Chief. The gold-fouled anchors mean the goat locker is yours, the command intelligence officer asks you by name, and the entire division reads the analytic standard off how you stand at the watch floor. Making Chief in the CT community is the milestone the whole enlisted pipeline is organized around.

The job changes more between CTT1 and CTTC than at any other promotion in the rating. As LCPO of a SIGINT technical division at a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR element, an NSA-affiliated site, or a deployed SIGINT support element, you run the analysts and own enlisted execution from the watch floor up. You write Chief-quality eEVALs that pick the next CTT1 and CTTC slate. You sit at command intelligence sync as the senior enlisted SIGINT technical voice. You walk the space during a real-world collection event or a higher-echelon IC assessment and identify the analytic or process gap before the assessor does. You own the DoD 8140 compliance picture, the clearance and OPSEC climate, and the production standard the IC customer chain holds the command accountable for. You build the next LPO. You mentor the next Warrant Officer, LDO/CWO, and senior-NEC candidate. You enforce the analytic and security standard, in the space, every day, while the division watches whether your watch-floor posture matches your liberty habits — because in a TS/SCI community, the Chief whose judgment is questioned is the Chief whose team cannot hold the standard.

• 01Run an LCPO's mess of SIGINT technical analysts — accountability, training, qualification, readiness, discipline, family, finance, and clearance health — with weekly cadence the command intelligence officer and the CO can predict.
• 02Defend the division's production output, DoD 8140 compliance, analytic readiness, and IC assessment posture at command-level sync without your numbers being rewritten.
• 03Walk a real-world collection event or a higher-echelon IC assessment as the senior enlisted SIGINT technical voice on scene — your AAR is what the command briefs up to NAVIFOR, Fleet Cyber, and the NSA technical chain.
• 04Mentor four-to-six CTT1s into Chief-board-competitive candidates; produce at least one Warrant, LDO/CWO, or senior-NEC selectee per year from your division.
• 05Own the clearance and OPSEC climate of the division — set the standard that makes mishandling unthinkable, and have the hard security conversation before it becomes a reportable incident.
• 06Translate NSA technical doctrine, Fleet Cyber Command direction, and NAVIFOR guidance into watch-floor decisions the analysts execute without rewording the message.

• —ICD 203, 206, 208 — you defend the division's analytic production against the full IC standard every assessment cycle.
• —OPNAVINST 2201.3 — Navy SIGINT / EW coordination; you are the senior enlisted technical voice on the command's compliance posture.
• —DoDM 8140.03 — Cyberspace Workforce Qualification; DoDI 8500.01 — Cybersecurity; DoDI 8510.01 — Risk Management Framework for DoD IT.
• —SECNAVINST 5239 series; the current OPNAV Navy cybersecurity / IA program instruction — you are the officer the security officer quotes, not the one reading the brief for the first time.
• —MILPERSMAN — fluent in the articles governing advancement, retention, separation, NJP, and security-clearance / suitability actions at CTTC-level visibility.
• —CPO 365 / CPO Initiation guidance and the Senior Enlisted Academy reading list — the wardroom and the goat locker hold you to it after the anchors go on.

• —CPO Academy / Chiefs Mess transition complete; standing as a Chief in the mess at the watch-floor level — not a Chief in title alone.
• —Division production output, DoD 8140 compliance, and IC assessment findings defensible at command, NAVIFOR, and NSA technical chain levels during your tenure as LCPO.
• —A senior or advanced technical qualification maintained — the SIGINT landscape changes quarterly; the Chief who stopped studying is the Chief whose division falls behind the IC standard.
• —Pipeline producing 1+ Warrant, LDO/CWO, or senior-NEC selectee per year — and the command intelligence officer can name them.
• —Zero Chief-level integrity incidents — security mishandling, OPSEC breach, fraternization, financial. In a TS/SCI community one ends the career permanently and pulls the clearance with it.

• —Mistaking the goat locker for a private club. The mess is a working leadership platform; chiefs who treat it as social are the ones the division reads as off-mission inside the same assessment cycle.
• —Stopping personal technical study because "I am a Chief now." In the SIGINT technical community the threat, the technology, and the IC analytic standards all move; the Chief who stopped reading is the Chief whose AAR the NSA technical staff rewrites.
• —Letting a CTT1 LPO run a bad division because he is "your guy" or "almost a Chief." The command intelligence officer and the CMC see the analytic climate before the slate is read.
• —Going public with disagreement with the command intelligence officer or the CO. The disagreement happens in the office; you walk out aligned. The goat locker enforces this without the wardroom having to ask.
• —Treating the clearance and OPSEC climate as a brief you give at quarters once a year. The Chief sets the daily tone that makes mishandling unthinkable; let it drift and the security incident is on your watch.

The good CTTC is the LCPO the command intelligence officer calls by name and the goat locker defends in the mess. His division's production briefs without caveats, his CTT1s pick up Chief, his IC assessment findings are closed before the assessor asks, and his watch-floor posture matches his liberty posture. The clearance and OPSEC climate is so squared away that mishandling is unthinkable — and he is on the Senior Chief slate before the CMC has to ask.

You are the senior enlisted SIGINT technical voice in a command, staff, or the broader IC enterprise. The CO names you in the slide. NSA, Fleet Cyber Command, and NAVIFOR know your name on the slate. The division watches whether you still walk the analytic standard.

As CTTCS or CTTCM you run the senior enlisted SIGINT technical posture for a NAVSECGRU command, a Fleet Cyber Command / NAVIFOR directorate, an NSA-affiliated senior staff element, or a joint IC command — or you sit as Command Master Chief where that path opens. You write fewer eEVALs but they are the ones that pick the next Chief and Senior Chief slate. You sit at command-team sync as the senior enlisted voice on every enlisted CTT decision — accession, NEC assignment, technical development, retention, credentialing, discipline, Warrant and commissioning pipeline, and the clearance and suitability dimension that shadows every personnel action in this community. You translate NSA technical doctrine, Fleet Cyber Command strategy, and NAVIFOR direction into command-level talent decisions. You build the next CMC / SEA selectee. You start the post-Navy market plan 24-36 months out — because a CTTCM with a clean TS/SCI record and a career of SIGINT technical production is among the most hireable senior enlisted the Navy produces, and the cleared contractor and federal civilian world (NSA, DISA, the major IC integrators) already has your name on a list. The bench you leave behind decides whether the goat locker and the IC community remember your name for the right reason.

• 01Run a senior-enlisted command climate across a SIGINT technical division or directorate that produces qualified analysts, Warrant and commissioning selectees, and retention above the type-command average — in a community where every loss is a cleared, trained analyst the Navy cannot replace on a short timeline.
• 02Brief the CO, the command intelligence officer, NAVIFOR, Fleet Cyber Command, or the joint IC senior staff on enlisted SIGINT technical readiness and risk in language the flag officer can defend at the next echelon without rewriting.
• 03Sit on Chief selection boards, CMC command slates, Warrant accession panels, and senior credentialing reviews with the discipline and confidentiality the convening authority requires.
• 04Translate NSA technical analysis doctrine, IC analytic standards, and NAVIFOR / Fleet Cyber Command strategy into enlisted talent-management decisions that shape the CTT community's bench for the next ten years.
• 05Own the command's clearance, suitability, and OPSEC climate at the senior-enlisted roll-up — the standard that keeps a TS/SCI SIGINT force trustworthy is set at your level.
• 06Run a Red Cross / casualty notification or serious-incident response with the dignity it requires. You are the face the family and the command see.

• —ICD 203, 206, 208 — the IC analytic standards your community produces against; you defend the command's production posture at IC senior-staff level.
• —OPNAVINST 2201.3 — Navy SIGINT / EW coordination; you are the senior technical policy voice the wardroom cites.
• —DoDM 8140.03 — Cyberspace Workforce Qualification; DoDI 8500.01 / 8510.01 — Cybersecurity and RMF (you shape the command's workforce-compliance posture at the TYCOM / joint-staff level).
• —SECNAVINST 5239 series; the current OPNAV Navy cybersecurity / IA program instruction — you are the policy, not the student reading it.
• —MILPERSMAN — the full enlisted personnel-action catalog, including security clearance and suitability articles that matter uniquely in the CT community at every NJP, separation, and retention decision.
• —Senior Enlisted Academy reading list; CPO 365 doctrine — you are the standard the entire Chiefs Mess in your command is measured against.

• —Senior Enlisted Academy / Master Chief transition complete; standing as the senior enlisted voice the wardroom and the IC community treat as authoritative.
• —Command-level SIGINT technical readiness, DoD 8140 compliance, and IC assessment posture defensible at TYCOM and NSA senior-staff level during your tenure.
• —Pipeline producing 1+ Warrant, LDO/CWO, or senior-NEC selectee per year — the command intelligence officer and the CO can name them without looking at a list.
• —A current technical orientation maintained — intelligence technology and analytic tradecraft change; the CTTCM who stopped studying is the CTTCM whose AAR gets rewritten by a GS-15 with less time in the community.
• —Zero integrity incidents — security, OPSEC, clearance mishandling, fraternization, financial. The standard at this rank does not allow for a second-chance conversation in a TS/SCI community.

• —Treating the role as primarily ceremonial. The CTTCM who shows up for the change-of-command and disappears from the watch floor is the senior enlisted voice the IC senior staff stops calling.
• —Confusing institutional knowledge with current technical accuracy. The SIGINT and IC analytic landscape changes faster than any career cycle; the Master Chief who speaks to current production with outdated knowledge is a liability at the NSA senior-staff table.
• —Allowing the clearance and OPSEC climate at command level to become a "human resources problem" rather than a command culture problem. At CTTCM, the clearance climate you set or tolerate is the one the IC IG visits.
• —Going public with disagreement with the CO, the TYCOM, or the IC senior staff. The disagreement happens in the office; you walk out aligned. The goat locker at your level is the IC enterprise.
• —Treating the run-up to retirement as the standard winding down. Until the ceremony is over, the analytic and security standard is your job — and the CTTSN watching from the back of the compartment is learning what the standard looks like from you.

The good CTT Master Chief is the senior enlisted SIGINT technical voice the CO, the command intelligence officer, and the NSA senior staff name without hesitation when the IC community needs someone in the room. His command's CTT slate is the one cited in the next NAVADMIN as the production-readiness and compliance benchmark. His Warrant and commissioning pipeline is producing. His rated chiefs pin Senior Chief and Master Chief on schedule. When he retires the IC community has already made the next call — and every CTT who served under him knows what the analytic standard felt like when someone was actually holding it.