Job search
Job Offer Requires a Security Clearance Transfer: Confirm Sponsorship and Reciprocity Before Your Start Date
Track who confirms each security and hiring dependency without assuming clearance transfer authorizes access or guarantees a start date.
An offer says your security clearance must “transfer” before you start. You previously worked in a cleared position, so you expect the new employer to confirm the record and give you a date. Instead, the recruiter says security is reviewing it, and nobody has explained what remains open.
Ask the new employer’s security office to separate five items: existing eligibility, sponsorship, reciprocity review, access for the new assignment, and the employment start decision. A favorable answer about one item does not complete the others. This guide concerns that post-offer handoff; it cannot determine your clearance status or authorize access. While those conditions remain open, browse recent roles on LandOffer.ai to maintain an appropriate shortlist.

What “transfer” leaves unexplained
The DCSA Facility Security Officer FAQ describes a personnel security clearance as an administrative determination of eligibility. It says individuals cannot apply independently, government authorities make clearance decisions, and a company’s Facility Security Officer, or FSO, should be the first contact for package assistance or status questions. These are different responsibilities from a recruiter scheduling onboarding. DCSA FSO FAQ
In conversation, “transfer” might mean that someone has located an existing record, established the new organization’s relationship, requested reciprocal recognition, or confirmed that the person can perform a particular assignment. Ask which action the receiving office has actually completed. Record the answer in the employer’s words rather than translating every encouraging update into “cleared to start.”
Keep a short, private process note. Its purpose is to track who owes the next confirmation. It should not reproduce investigative records or become a second security database. A recruiter can explain an offer condition without receiving your background questionnaire or a screenshot from a restricted system.
If you are still deciding whether a vacancy involves Public Trust or classified access, first read Public Trust vs. Security Clearance. Here, the question is narrower: what does the receiving organization need to resolve after making an offer?
Separate recognition from access to the new work
For contractor employees, 32 CFR 117.10 assigns eligibility determinations to the cognizant security agency. It separately addresses contractor access, including a valid need-to-know, favorable government eligibility at the appropriate level, and a signed nondisclosure agreement. Access to SCI, SAP, RD and FRD has its own granting-authority boundary. A prior eligibility statement therefore cannot, by itself, establish permission for every new task. 32 CFR 117.10(a)
Think about the actual work you would do on the first day. Is the offer for an unclassified orientation period, or must you immediately enter an assignment requiring classified access? Do not assume an orientation option exists. Ask HR to confirm the permitted duties and ask security to confirm the access dependency.
Nor should you describe yourself as having authorization that the receiving office has not confirmed. “I previously held eligibility; your security office is reviewing the applicable record” distinguishes your account from the employer’s verification. Keep any permitted resume wording consistent with instructions from the appropriate security office, without adding sensitive program or customer details.
Reciprocity is a review process, not a personal shortcut
Security Executive Agent Directive 7 establishes reciprocal acceptance rules for background investigations and national security eligibility adjudications. It calls for agency record review, addresses acceptance at the same or higher level, and specifies exceptions, including interim eligibility and certain new information. The published directive is effective November 9, 2018; its older database names should not be treated as instructions to access those systems yourself. SEAD 7, sections E–F
Ask whether the receiving security office has identified the applicable route and the next action it needs from you. It is not whether you can declare reciprocity for yourself. Avoid deciding that a gap in employment, a remembered investigation date, or an old access status settles the result. Give requested information through the authorized process, accurately and completely.
The contractor regulation also distinguishes a break in access from a break in employment. Where a break resulted in loss of eligibility, it requires a new agency eligibility determination before the contractor provides access. That is another reason to ask the responsible office rather than apply a generic “clearances last this long” rule. 32 CFR 117.10(h)–(j)
A completed handoff matrix: Celia’s platform role
Celia Arden and the employer Harbor Signal Analytics are fictional. For this planning exercise, Celia has accepted a platform-engineering offer with a proposed November 16, 2026 start. She reports previously holding eligibility; no real security record has been reviewed. The invented offer makes the start subject to employer confirmation. These assumptions demonstrate ownership and unresolved states, not a clearance outcome.
Her completed matrix records six separate dependencies:
| Item | Responsible owner | Evidence in this fictional case | Current state | Next confirmation |
|---|---|---|---|---|
| Prior eligibility | Receiving FSO verifies through authorized channels | Candidate’s statement only | Unverified by receiving office | FSO confirms whether the relevant record has been located |
| Sponsorship relationship | New employer’s security office | Security intake contact identified | Intake route identified; establishment not confirmed | Security confirms its applicable relationship/action |
| Reciprocity | Receiving security office and appropriate government authority | No determination received | Pending review, not approved | Security identifies the applicable review and outstanding dependency |
| Assignment access | Security and assignment owner | Offer names platform work, not authorized access | Not confirmed | Confirm required level and assignment-specific authorization |
| Employment start | HR/recruiter | November 16 is proposed and conditional | Not released as final | HR confirms date after its stated conditions are resolved |
| Initial duties | Hiring manager, coordinated with HR/security | No orientation-only plan provided | Unknown | Ask whether any permitted initial duties are available |
Celia’s decision is to leave the start date conditional. She has not concluded that the employer rejected her, that her prior eligibility disappeared, or that she may enter the assignment. The fictional record supports none of those conclusions.
The matrix also prevents a common ownership mistake. The hiring manager can describe the intended platform responsibilities but cannot substitute that description for a government eligibility determination. HR can confirm employment logistics but should identify when its answer depends on security. Celia’s own action is to supply requested information through the confirmed channel, not mark those organizations’ work complete.
For a later update, she would preserve the original conditional date and add the exact update, its date and the office that supplied it. If security says the record was located, only the first row changes. If HR confirms an orientation start, she records the allowed duties and remaining access limitation. Neither update silently closes the whole table.
The accompanying local asset contains this filled matrix, its fictional assumptions and a status-change example. It contains no case number, clearance-system screenshot, government identifier or operational detail. The completed artifact is a planning document; no external handoff occurred.

Why a reciprocity target does not promise your start date
SEAD 7 section G specifies five business days for a reciprocity determination after receipt by the agency’s personnel security program. It excludes employment, suitability or fitness processing and identifies other excluded processing time, including authorized additional checks, polygraph processing and obtaining investigative records when review is authorized. It is not an offer-to-onboarding clock. SEAD 7, section G
Do not calculate your resignation or travel date by adding five weekdays to the day you accepted an offer. Those dates do not establish when the relevant program received a review or what other employment conditions remain. Instead, ask which milestone the employer is reporting and who will provide the next update.
A useful answer might distinguish “intake received” from “review submitted” and “determination received” from “start approved.” Those are example labels for a conversation, not universal DCSA workflow statuses. Use the actual labels your employer provides and preserve any unresolved qualification attached to them.
If the proposed date approaches without confirmation, ask HR whether it remains tentative and what happens if the dependency is unresolved. Record the answer before arranging a change you cannot easily reverse. Use that answer to identify the unresolved employer decision; it does not settle your personal employment or financial choices.
A separate unsent inquiry: Ren’s receiving-office questions
Ren Bell and Alder Meridian Systems are a second fictional case, independent of Celia’s matrix. Ren has an offer for a data-integration role with a proposed December 7 start. The recruiter has provided a new FSO contact, but Ren has received neither secure intake instructions nor confirmation of the first-day access requirement. This completed message remains unsent and includes no attachments.
To: FSO contact identified by the new employer
Subject: Process questions for conditional December 7 start
Hello,
The recruiting team directed me to your office regarding the security dependency for my data-integration offer. December 7 is currently the proposed start date. I previously held national security eligibility, but I understand your office must verify the applicable record and determine the required processing with the appropriate authority.
Could you confirm the approved intake channel and what information or documents you need from me? Please let me know how to provide requested sensitive information securely; I have not attached background forms, identification or security-record images to this inquiry.
Has your office identified whether reciprocity review or another action is required for this assignment? I am asking about the process and outstanding dependency, rather than assuming my prior eligibility automatically establishes current access.
Please also confirm who will tell me when the security condition relevant to starting work has been resolved. Should HR confirm the employment date separately, and is any permitted orientation period available before assignment access is authorized? I understand that such an arrangement may not be available.
If the dependency remains open near December 7, whom should I coordinate with about the proposed date, and when should I request the next update?
Thank you,
Ren Bell
Ren’s companion record has four filled states: inquiry drafted but unsent; secure channel not yet received; documents not provided; start confirmation outstanding. The next action is to verify and use the employer-provided contact, not forward the message to several agencies hoping one will resolve the case.
Keep the document request and the intake channel separate. Knowing that an office needs information does not tell you where to transmit it. Conversely, receiving a secure intake invitation does not mean the requested review has finished. After any real action, update only the step actually completed.
Keep the hiring conversation useful and appropriately limited
Bring HR a process question it can answer: “Is my date final, and which condition remains open?” Bring the FSO the security-process question: “What do you need from me, through which channel, and who confirms the next milestone?” Avoid asking a recruiter to adjudicate an unexplained security status or asking a security office to decide compensation and notice arrangements.
Keep a private record of the offer condition, responsible contact, latest confirmed milestone and next agreed follow-up. Leave investigative details in the authorized process. The DCSA FAQ’s statement that a clearance does not guarantee employment is relevant here: eligibility and the employer’s hiring decision have distinct purposes. DCSA FSO FAQ
For the wider job search, browse recent roles on LandOffer.ai and keep an appropriate shortlist while the employer resolves its process. Keep security-sensitive history outside general job-search notes. Your reviewable next step is a clear dependency record and an appropriate process inquiry; the receiving employer and responsible authorities must provide the actual confirmations.
Sources and Further Reading
- DCSA: FAQs – Facility Security Officers — relevant answers expanded and read in the ordinary public browser; direct web retrieval returned 403.
- eCFR: 32 CFR 117.10 — current display as of October 22, 2026; contractor eligibility, access and reciprocity responsibilities.
- ODNI: SEAD 7 — full six-page directive, effective November 9, 2018; reciprocal recognition, exceptions and the scope of timing requirements.
Public sources checked October 23, 2026. All employers, candidates, dates and case states in the worked examples are invented. No security account, private record, clearance status, application or employer communication was accessed or changed.


