Re-Onboarding a Returning Cleared Employee Under Clearance Reciprocity

The Decision Point Most Contractors Miss

A cleared employee separates from one contractor, sits on the bench for seven months, then accepts a position with your firm on a new task order. The hiring manager assumes the active clearance transfers cleanly and tells HR to skip the usual security coordination steps. That assumption is where re-onboarding breaks down.

Clearance reciprocity is real and codified. Intelligence Community Directive 704 and the Security Executive Agent Directive (SEAD) framework both require agencies to accept a current, in-scope investigation from another agency rather than restart the process. But reciprocity is not automatic, and it does not eliminate the contractor's onboarding obligations. Understanding what reciprocity covers, and what it does not, is the operational core of re-onboarding a returning cleared employee correctly.

What Reciprocity Actually Covers

Reciprocity applies to the investigation, not the access determination. A Secret clearance granted by DoD is based on a Tier 3 investigation. If that investigation is current (within scope, meaning within the reinvestigation period) and no adverse information has been reported, a receiving agency or contractor facility is expected to accept it rather than sponsor a new investigation. The same principle applies to Top Secret and SCI eligibility, though SCI access requires a separate access determination by the granting agency regardless of reciprocity.

Three conditions must be true for reciprocity to apply cleanly:

• The investigation is current and in-scope. For Secret (Tier 3), the reinvestigation period is ten years. For Top Secret (Tier 5), it is five years. A lapse does not automatically break reciprocity, but a gap in employment or a reportable life event during that gap may trigger a new investigation requirement.
• No break in access exceeding 24 months. Under SEAD 7, a break in access of more than 24 months generally requires a new investigation before access is re-granted. Seven months, as in the example above, falls well inside that window, but the FSO must document the break and confirm the date of last access explicitly.
• No derogatory information has been reported or is pending. The FSO must query DISS (Defense Information System for Security) or the applicable system to confirm the clearance status is active and not under review.

The FSO's Verification Checklist Before Day One

Reciprocity does not mean the FSO steps aside. It means the FSO substitutes a verification workflow for a sponsorship workflow. The steps below apply to a DoD contractor environment using DISS, but the logic translates to other agency systems.

1. Pull the DISS record immediately upon offer acceptance. Confirm eligibility level, investigation type, investigation close date, and access status. Do not rely on the employee's verbal representation or a prior employer's letter.
2. Verify the break-in-access date. Ask the employee for the date their last facility clearance (FCL) access was terminated. Cross-reference against DISS. If the break exceeds 24 months, stop and contact your Cognizant Security Agency (CSA) before proceeding.
3. Check for open continuous evaluation (CE) flags. Continuous evaluation replaced periodic reinvestigation for most clearance holders. A flag in CE does not mean the clearance is revoked, but it does mean an adjudicative action may be pending. Granting access while an action is pending creates liability for the contractor.
4. Issue a new visit authorization request (VAR) or in-processing action. Even under reciprocity, the employee must be formally in-processed at your facility. This ties their clearance record to your FCL and establishes the chain of custody for access decisions.
5. Collect and re-execute all facility-specific agreements. Non-disclosure agreements (SF-312 for classified information), acceptable use policies, and any program-specific security briefings do not transfer from the prior employer. These must be re-executed at your facility.

Employment Eligibility and I-9: Not Optional Even for Returning Employees

A cleared employee who previously worked for your firm and is rehired within three years of the original I-9 completion date may qualify for a re-verification rather than a full new I-9, provided the original I-9 is on file and unexpired. If the original I-9 is missing, expired, or the employee's work authorization document has since expired, a full new I-9 is required.

This is a common failure point. FSOs and security coordinators focus on DISS and clearance paperwork, and the I-9 falls to HR, which may assume a returning employee is already covered. The I-9 obligation is independent of clearance status. A Top Secret clearance does not establish work authorization for I-9 purposes. The two compliance streams run in parallel and must both be closed before the employee begins work.

If your firm uses E-Verify, a rehire does not automatically require a new E-Verify case if the employee was previously verified and is returning within three years. However, if any document presented for re-verification is a List A or List C document with a new expiration date, you must update Section 3 of the I-9 and may need to run a new E-Verify case depending on your MOU terms. Confirm with your E-Verify program administrator before assuming the prior case covers the rehire.

Offer Letter and Contractor Agreement Considerations

A returning employee is a new hire for contract purposes. The prior offer letter, compensation terms, and any contractor agreement from the previous engagement are not operative. Issue a new offer letter that references the specific task order or contract, the applicable labor category, and any clearance-contingent conditions of employment. If the position requires a specific clearance level as a condition of continued employment, that condition must be stated explicitly in the offer letter, not assumed.

If the employee is a subcontractor rather than a direct hire, the prime-sub agreement and any flow-down clauses from the prime contract govern what security documentation the sub must provide to the prime's FSO. Winrove supports subcontractor and key-personnel onboarding for awarded contracts, which is particularly relevant when a prime must collect and track security documentation across multiple returning personnel on a single task order.

HSPD-12 and PIV Credential Re-Issuance

If the task order requires HSPD-12 PIV credentials for physical or logical access to federal facilities or systems, the employee's prior PIV card from another agency or contractor is not valid at your facility. PIV credentials are issuer-specific. The employee must enroll in your sponsoring agency's identity management system and complete a new PIV issuance process, including identity proofing and biometric capture, even if they hold a current PIV from a prior engagement. The clearance reciprocity determination and the PIV issuance are separate processes with separate timelines. Do not promise a start date that depends on PIV issuance unless you have confirmed the issuing agency's current enrollment queue.

Takeaway

Clearance reciprocity reduces investigation timelines, not compliance workload. The FSO still owns DISS verification, break-in-access confirmation, and facility in-processing. HR still owns the I-9 and E-Verify determination. Contracts still owns the offer letter and agreement execution. PIV issuance runs on the agency's schedule, not yours. Treat re-onboarding a returning cleared employee as a parallel-track process where each stream has its own close condition, and do not grant access until every track is closed.

If your team is working through the documentation requirements for cleared personnel on an awarded contract and wants a structured way to track each compliance step, visit the IT Custom Solution contact page to start a brief conversation about how to organize the process.