Employee Referrals for Cleared Hiring:
Protect Privacy and Verify Access Later
Build a cleared-hiring referral program that earns participation, protects candidate privacy, and leaves eligibility and access checks to authorized staff.
Updated October 26, 2026
Recruiting
To encourage employee referrals in cleared hiring, make the employee’s task small and safe: introduce a willing candidate, name the relevant skills, and stop there. A referrer should not verify clearance eligibility, collect security documents, or explain a person’s history. Those checks belong in the normal hiring and security workflows.
- Define the handoff: a referral is an introduction, not a clearance attestation.
- Get permission: the candidate should know what will be submitted and choose how to respond.
- Minimize the data: accept job-relevant evidence, not personal history or security files.
- Use one process: referred candidates complete the same application and qualification review as everyone else.
- Separate verification: recruiters screen for role fit; authorized security staff verify official records when appropriate.
How can you encourage employee referrals without creating privacy risk?
Reduce the favor you are asking employees to perform. Give them a specific opening, a short explanation they can forward, and a referral form that accepts only information they personally know. Keep the action clear and quick without turning a colleague into an investigator.
Employees can credibly describe work they witnessed: a candidate configured a particular platform, led a migration, wrote usable incident reports, or coordinated well across teams. They usually cannot credibly determine what a government system currently shows, whether another agency will accept an adjudication, or whether a program will grant access.
Program language should draw that boundary plainly: “Refer someone whose work you know. Do not ask for clearance paperwork or sensitive personal details.” Pair that direction with a concise role card containing duties, work location, employment type, and the stated clearance requirement. An employee can then make a useful introduction without improvising a security interview.
If participation is the immediate problem, the operational ideas in how recruiters can make employee referrals work help with awareness and internal promotion. Add the privacy boundary to those tactics so increased volume does not create ungoverned data collection.
What is a referral in cleared hiring?
A referral is a traceable introduction to the employer’s application process. It may carry job-relevant context from someone who knows the candidate’s work. It is not proof of eligibility, current access, polygraph status, suitability, program acceptance, citizenship, or any other formal decision.
That definition protects all three parties. The candidate does not have to disclose sensitive details to a friend. The employee is not accountable for a government decision outside the employee’s role. The employer receives a useful lead without mistaking workplace familiarity for verified security information.
The current NISPOM rule at 32 CFR 117.10 assigns the eligibility decision to the Cognizant Security Agency and the job-and-contract need determination to the cleared contractor. It separately requires favorable eligibility, need-to-know, and a signed nondisclosure agreement for access. A referral label cannot settle those issues.
Use careful internal statuses such as “employee-introduced,” “candidate applied,” and “security review pending.” Avoid labels such as “verified cleared” when the only evidence is a referrer’s statement or an old résumé. The status name should describe what actually occurred.
What should the referral form ask?
Ask for the opening, the candidate’s chosen contact information, the working relationship, and concise evidence of relevant skills. Include a confirmation that the candidate agreed to be contacted. Everything else should flow through the candidate-facing application or an authorized security channel.
| Referral field | Why it belongs | What should stay out |
|---|---|---|
| Specific opening | Connects the introduction to real duties | Guesses about other programs or billets |
| Candidate’s preferred contact | Lets the candidate control the next conversation | Personal identifiers unrelated to contact |
| How the employee knows the work | Gives recruiters context for the endorsement | Client, mission, or classified details |
| Observed skills and results | Supports job-related review | Rumors about personal or security history |
| Permission to contact | Records an informed introduction | A résumé uploaded without the candidate’s knowledge |
A free-text box needs a warning beside it, not buried in policy: exclude classified information, program names not present in the public posting, clearance documents, government-system screenshots, polygraph details, medical or financial history, and personal identifiers. If a referral contains something that may be classified, the recruiter should stop handling it, not forward or delete it, and notify the Facility Security Officer (FSO) immediately. At a cleared contractor, 32 CFR 117.8(d) requires the contractor to begin a preliminary inquiry immediately on a security violation report involving classified information and, if the inquiry confirms a loss, compromise, or suspected compromise, to promptly submit an initial report to the Cognizant Security Agency. Other unneeded personal data follows the company’s privacy procedure.
The broader mechanics of communicating rules, recognizing contributors, and keeping a program visible are covered in these employee referral program practices. Use the referral form to enforce those boundaries instead of relying on informal email.
How should you give the candidate notice and choice?
Require the employee to contact the candidate before entering personal information. The message should identify the employer, the opening, the limited information the employee plans to share, and where the candidate can review the privacy notice. The candidate should be able to decline without the employee guessing why.
A practical forwardable message is: “I saw an opening that may match your experience. If you want an introduction, I will submit your name, preferred contact, the role, and how I know your work. You will receive the application link and decide whether to continue.” Keep clearance claims out of that script.
Offer a candidate-led path as well. The employee sends a referral link or code, and the candidate enters their own details. That method reduces transcription errors, prevents surprise outreach, and lets the person decide what appears on the application. The employee can add job evidence in a separate, bounded field.
Limit the notice to the defined exchange and collect only the stated information. If the candidate starts sharing security-processing details, the employee should redirect the person to recruiting or the security office rather than copying the account into the referral form.
Which sensitive information should stay out?
Keep clearance certificates, system screenshots, access rosters, polygraph reports, investigative forms, personal adjudicative history, financial records, medical information, and identity documents out of the referral channel. The referral team does not need that material to decide whether to invite a candidate into the application process.
The FTC’s October 2016 data-security guidance for businesses advises against collecting sensitive personally identifying information without a legitimate business need. When information is needed, the FTC says to retain it only as long as necessary and limit employee access according to the person’s job.
Apply that principle to the workflow itself. A bonus administrator needs the referral source and payment status, not an explanation of security processing. A hiring manager needs evidence against job criteria, not a candidate’s investigative history. A referrer needs acknowledgement that the introduction was received, not the reason a candidate left the process.
Written retention and access rules should cover referral records just as they cover direct applications. Identify the system of record, who can see free text and attachments, when duplicates are removed, and how an employee reports information that should not have been submitted.
Why should every referral enter the standard application workflow?
The referral should change the source field, not the selection standard. Send the candidate the same job description, application, required disclosures, qualification review, interview structure, and disposition process used for other applicants. Record the employee’s job evidence as context, not as a substitute for assessment.
Uniform treatment also makes the program easier to audit. Recruiters can compare referred and non-referred applicants at equivalent stages, identify exceptions, and explain decisions using the same evidence. Side-channel résumés in inboxes make response time, candidate consent, duplicate ownership, and retention much harder to control.
EEOC guidance recommends hiring based on job-related ability through uniform and consistently applied standards. Its April 19, 2006 race-and-color guidance says word-of-mouth recruiting in a racially diverse workforce can promote diversity, while the same method in a non-diverse workforce can impede equal opportunity if the applicant pool does not reflect diversity in the qualified labor market.
Referrals therefore should supplement broader sourcing, not quietly replace it. Publish openings through the organization’s normal channels, monitor who hears about them, and prohibit managers from treating “known by an employee” as an unwritten minimum qualification.
When should recruiters screen and security staff verify?
Recruiters should first establish ordinary fit: interest, experience, work conditions, and the requirement stated in the posting. When the candidate reaches the employer’s defined stage, authorized security personnel can verify official eligibility and access information through approved systems and procedures.
The candidate may provide a careful, self-reported description during recruiting, but the record should still distinguish “candidate stated” from “security verified.” The public-facing recruiter does not need screenshots or supporting investigation records to preserve that distinction. A field can simply show that verification has not yet occurred.
At a cleared contractor, 32 CFR 117.10(d) has the SF 86 reviewed by the FSO or another contractor employee the contractor has specifically designated for that work. The FSO or designee must not share information from the employee’s SF 86 within the entity or use it for any purpose other than determining the form’s adequacy and completeness. A referrer and ordinary recruiting workflow do not belong in that review.
Under 32 CFR 117.10(f), a cleared contractor may ask for an investigation before the start date if the new hire needs classified access immediately upon starting, provided the contractor has made a written employment commitment and the candidate has accepted the offer in writing. The commitment must indicate that employment will begin within 45 days of the employee being granted the needed eligibility for access. That sequence is another reason not to make the referral form behave like a security package.
Give recruiting and security separate permissions, fields, and handoff criteria. For a fuller treatment of what recruiters may collect and what an FSO should confirm, use the operational distinctions in verifying a candidate’s security clearance.
How can you pay referral bonuses without exposing outcomes?
Publish bonus eligibility around employment milestones and program rules that the referrer is entitled to know. The referrer can see that a submission was received, whether it met the published ownership rules, and whether a payment-triggering milestone occurred. Security-processing details should not appear in that portal or explanation.
Use generic dispositions such as “not selected,” “candidate withdrew,” or “bonus not earned under program terms.” Do not tell the referrer that the candidate failed a polygraph, received an unfavorable determination, could not obtain program access, or disclosed a personal issue. Even if the two people are friends, the employer should communicate a candidate’s information to the candidate.
Define duplicate-referral, prior-applicant, rehiring, contractor, and manager-eligibility rules before launching. Clear rules prevent recruiters from resolving disputes by revealing dates or events that belong in the candidate record. Give candidates their own contact for questions about their process.
What should you audit besides referral volume?
Audit participation, quality, process consistency, privacy complaints, and concentration. Raw submission volume can rise while the program sends poor matches, delays non-referred applicants, exposes sensitive data, or draws repeatedly from the same network. The review should test the system, not rank employees by social reach.
Useful measures include participation by function and location, completion of the candidate-consent step, job-related qualification rate, time to first recruiter review, movement through equivalent stages, source concentration, inappropriate-data reports, and requests to bypass the normal process. Analyze aggregate patterns with HR, privacy, legal, and security stakeholders as appropriate.
Read qualitative evidence too. Candidates may report surprise contact, pressure to disclose clearance details, or uncertainty about who can see a résumé. Referrers may report that the form is too long or that status messages invite uncomfortable questions. Recruiters may identify free-text fields that repeatedly attract material they should not receive.
Use the findings to tighten fields, permissions, training, and sourcing. If a team relies almost entirely on its own network, broaden outreach and keep selection criteria constant. If sensitive attachments recur, remove the attachment capability rather than relying on another reminder.
Frequently Asked Questions
Should an employee confirm a candidate’s clearance level?
No. The employee may say why the person’s work appears relevant, but official eligibility and access information should be verified by authorized security staff through approved procedures. Label any candidate statement as unverified until that check occurs.
Can a referred candidate skip the normal application?
A referral may help a recruiter find the person, but the candidate should enter the same controlled application and qualification workflow. That preserves notices, records, consistent standards, and a clear security handoff.
May a referrer upload the candidate’s résumé?
Only when the candidate has agreed and the program provides a controlled way to do it. A candidate-led referral link is cleaner because the candidate submits the current document and sees the employer’s notices directly.
What status should the employee receive?
Provide only what is needed to administer the program: receipt, ownership under published rules, and whether the bonus milestone was met. Send interview feedback, withdrawal reasons, and security-processing information to the candidate, not the referrer.
What is the first program change to make?
Open the referral form and remove every field that asks the employee to attest to clearance or access. Replace those fields with candidate permission, the specific opening, the working relationship, and observed evidence of job-related skill.