Why clearances trip up otherwise-good recruiters

Most recruiters can run a clean commercial pipeline and still lose a cleared req, because the clearance layer has its own vocabulary, its own timeline, and its own failure modes that have nothing to do with whether the candidate can do the job. A great engineer who is "clearable" is not the same hire as one who is "active TS/SCI" — and treating them as interchangeable is how a 30-day fill turns into a 9-month one. This is the part of cleared staffing that generic ATS tools don't model, so the knowledge lives in tribal memory and gets lost the moment your FSO is out of office.

This is a recruiter's working guide, not legal advice. The goal is to make you fluent enough to qualify candidates correctly, set honest expectations, and stop reqs from stalling in places that were entirely predictable.

The levels, in plain terms

There are three baseline clearance levels, defined by the damage to national security that unauthorized disclosure could cause:

  • Confidential — could cause damage. Reinvestigated every 15 years.
  • Secret — could cause serious damage. Reinvestigated every 10 years.
  • Top Secret (TS) — could cause exceptionally grave damage. Reinvestigated every 5 years (increasingly via continuous evaluation instead).

On top of TS sit access caveats that recruiters say in the same breath but that are not clearance levels:

  • SCI (Sensitive Compartmented Information) — access to specific intelligence "compartments," granted program by program.
  • SAP (Special Access Programs) — even tighter, need-to-know programs.
  • Poly — a polygraph (CI, or the more invasive Full-Scope/Lifestyle). "TS/SCI with Full-Scope Poly" is the highest-friction, highest-premium combination in the market.

There is also Public Trust, which is a suitability determination rather than a security clearance. It gates many federal civilian and contractor roles and confuses everyone because it sounds like a clearance and isn't one. In Hosting HR we model the whole ladder — Public Trust → Confidential → Secret → TS → TS/SCI → Poly — as a single ordered field precisely so a req for "Secret or above" can match correctly without a recruiter eyeballing it.

"Cleared," "clearable," "active," "current": the words that decide your timeline

The single most expensive mistake in cleared recruiting is misreading a candidate's status. Four terms do almost all the work:

  • Active — the clearance is in scope and the person is in an access bucket right now (they're working a contract that uses it). This is the gold standard. They can often start in days.
  • Current — the investigation is in scope but the person isn't currently in access (they left the contract). Reinstating is usually fast, but it isn't instant and it isn't guaranteed.
  • Expired / lapsed — outside the reinvestigation window. Reinstatement may require a new investigation. Treat as "uncleared for timeline purposes."
  • Clearable — no clearance, but no obvious disqualifier (US citizen, no recent foreign issues). A sponsor can put them through. Budget 6–18 months and a sponsoring contract.

If a job req says "active Secret" and you submit a "clearable" candidate, you haven't sourced a near-fit — you've sourced for a different timeline entirely. Tracking the exact status, not just the level, is the difference between a forecast and a guess; it's the same discipline that makes a cleared talent bench actually usable.

SF-86 and the investigation, end to end

When a candidate needs a clearance (or a reinvestigation), the mechanism is the SF-86, the Questionnaire for National Security Positions — a long, detailed form covering 10 years of residences, employment, foreign contacts, finances, and more. Here's the flow recruiters should be able to narrate:

  1. Sponsorship. A candidate cannot clear themselves. A government contract sponsors the investigation. No sponsoring contract, no clearance — full stop.
  2. e-QIP / eApp submission. The candidate completes the SF-86 electronically. Incomplete or inconsistent answers are the number-one cause of delay, so the kickoff matters.
  3. Investigation. Run today largely by the DCSA. Tiered: T3 for Secret, T5 for Top Secret. It includes records checks, interviews, and (for TS) subject and reference interviews.
  4. Adjudication. A government adjudicator weighs the findings against the 13 adjudicative guidelines (foreign influence, financial considerations, personal conduct, drug involvement, and so on) using a "whole-person" judgment.
  5. Grant, then access. A granted clearance still has to be paired with an access need on a specific program before the person can actually do classified work.

The honest expectation to set with a hiring manager: a fresh Secret commonly runs a few months; a TS/SCI with poly can run a year or more. Continuous Vetting has shortened periodic reinvestigations, but initial investigations are still slow. The fastest path to a fast start is always a candidate who is already active.

Where cleared reqs stall (and how to prevent it)

The same handful of failure modes recur. Build your process so they surface early instead of at week eight:

  • No sponsoring contract for a "clearable" hire. Confirm sponsorship exists before you make the offer, not after.
  • Crossover assumptions. A DoD Secret does not automatically grant DOE "Q" or an IC agency's access. Agency crossover is real work; never promise it.
  • Foreign-contact and financial flags. Recent foreign travel, foreign family, or delinquent debt can extend adjudication. You don't adjudicate — but you can set expectations and flag for the FSO early.
  • The SF-86 sitting unstarted. Every day the form isn't submitted is a day added to the start date. Make initiation an owned, dated task, the same way a good onboarding checklist makes equipment an owned task.

What to actually capture in your ATS

For every cleared candidate, capture four fields, not one: level, status (active / current / expired / clearable), investigation date or scope, and poly type if any. With those four, you can answer the only question a program manager really asks — "can this person start, and when?" — without a phone call. The clearance-aware fields and SF-86 initiation tasks in Hosting HR exist for exactly that, and they feed the same pipeline and onboarding workflow as every other hire, so a cleared start doesn't fall out of your normal process the moment it gets complicated.