Two minutes here, once, and you can use these tools for the rest of your transition with complete
confidence.
You already know this material better than most people will ever need to. The only thing that is
new is the setting — a chat window instead of a phone line or a shared drive — and the same
judgment you have applied for years applies here.
Classified or controlled information. Anything marked CONFIDENTIAL, SECRET, TOP SECRET, SCI,
SAP, NOFORN, or handled under a classification guide. This includes information that is unclassified
on its own but classified in aggregate. Pasting it into a commercial tool is a spillage, full stop,
with the reporting and consequences that follow.
CUI and export-controlled material. Controlled Unclassified Information, FOUO, ITAR- or
EAR-controlled technical data, and anything under a DD Form 254 on a contract.
Operational detail. Unit locations, movements, deployment schedules, force strength, tactics,
techniques and procedures, system vulnerabilities, or anything that would help someone target your
unit or your former unit.
Other people’s information. Names, contact details, medical conditions, or personnel actions
involving anyone other than you — subordinates, peers, or leadership.
Credentials and identifiers. Your SSN, DoD ID, passwords, bank details, or full date of birth.
If someone would need a clearance, a need-to-know, or a signed agreement to read it, it stays
out of the chat window.
That single question resolves almost every case in a couple of seconds.
For anything that sits close to the line, your security manager is the right person to ask, and
asking is always the correct call. Describe the question in general terms rather than pasting the
text you are unsure about, and you have handled it properly.
Here is the good news, and it is worth sitting with: you can describe cleared work honestly, fully
and persuasively at an unclassified level. Recruiters in this space expect exactly that and know
how to read it.
What a hiring manager needs from you is scope, scale, duration, team size, budget and the kind of
outcome you produced — and all of that is almost always unclassified. The specifics that stay
behind are rarely the parts that would have won you the job anyway.
“TS/SCI with CI polygraph, current as of [MONTH YEAR]”
Notice what survives the translation. Every line still conveys real responsibility, real scale and
a real result. You lose the specifics that were never yours to share, and you keep everything that
makes a hiring manager want to talk to you.
Handled this way, your cleared background reads as an asset and your discretion reads as
professionalism. In this market, both are noticed.
Review the text below as if you were a security manager doing an OPSEC review before
public release.
Flag anything that could be:
- classified, CUI, FOUO, or export-controlled
- operationally sensitive (locations, movements, unit strength, TTPs, system names, vulnerabilities)
- personally identifiable information about me or anyone else
- specific enough to identify a unit, a mission, or a partner organization
For each flag, tell me: (1) what the concern is, and (2) a rewritten version that keeps the
professional value — scope, scale, leadership, outcome — without the sensitive detail.
Do not rewrite anything that is fine. Just list the problems and the fixes.
TEXT:
[PASTE YOUR RESUME BULLET, PROFILE, OR DRAFT HERE]
Important: this is a second pair of eyes, not an authority. An AI tool cannot make a classification determination. If something is genuinely borderline, ask your security manager — and do not paste the borderline text in to ask.
Your own information is worth the same care you would give anyone else’s. A few habits cover it
comfortably.
Use a personal email for AI accounts, not your .mil or work address. You want the account
after you separate.
Redact before pasting a resume. Replace your home address and phone number with
[ADDRESS] and [PHONE]. The tool does not need them to write good bullets.
Turn off data-training settings where the provider offers them. Look under Settings →
Privacy, Data Controls, or similar.
Do not paste a VA disability rating, diagnosis, or medical record. You are not required to
disclose a disability to an employer before an offer, and you should not be putting your medical
history into a chat log.
Be careful with employer accounts. If your employer or a contractor gives you an AI tool,
assume the organization can see your usage. Do not job-search on it.
Follow your organization’s AI policy. Many have an approved tool and a prohibition on everything
else.
Do not install AI browser extensions on a government system.
Do not use a personal AI account on a government device.
Do your job searching on your own device, on your own time, on your own network.
Following your organization’s policy here protects your career and your clearance, and both are
worth far more than the convenience of any shortcut. When you are unsure what the policy says, your
security manager or your contract’s security officer will tell you in a five-minute conversation.
Now the wide-open part, which is most of it. Everything below is entirely safe to share, and it is
more than enough raw material for every prompt on this site:
Your rank, branch, years of service, and job title
Team sizes, budget figures, and equipment values that appear on your evaluations
Unclassified awards, decorations, and the citations that came with them
Your education, certifications, and training courses
Public job descriptions you are applying to
Your resume, once you have stripped the contact details and any sensitive specifics
Your career questions, doubts, and goals
Work within that boundary and you can use every tool and every prompt here with complete
confidence. The boundary is generous, and the discipline you already have makes staying inside it
effortless.
