Security Executive Agent Directive 3 runs eleven pages. Not one of them gives you a deadline for reporting a foreign contact. The “five business days” figure on nearly every clearance blog is real, but it attaches to travel itinerary deviations, not to people. If you have been counting days since a foreign national asked for your number, you have been counting against a rule that does not exist.

What does SEAD 3 actually require you to report?

Short answer: Two triggers. A continuing association involving bonds of affection, personal obligation, or intimate contact. And, separately, any contact involving an exchange of personal information. Limited or casual public contact is exempt.

The operative text is paragraph F.2.b.2 of SEAD 3, and the trigger and the exemption sit in the same block: “Continuing association with known foreign nationals that involve bonds of affection, personal obligation, or intimate contact; or any contact with a foreign national that involves the exchange of personal information.” Then, two sentences later: “The reporting of limited or casual public contact with foreign nationals is not required absent any other reporting requirement in this directive.”

The directive adds that the requirement turns on the nature of the relationship “regardless of how or where the foreign national contact was made.” A friendship conducted over Signal counts the same as one conducted over dinner.

A second trigger sits one line above, in ¶ F.2.b.1, and carries none of those qualifiers: “Unofficial contact with a known or suspected foreign intelligence entity.” No affection requirement. No continuing-relationship requirement. No casual-contact exemption. One interaction is enough, and the definition reaches non-state actors and “international terrorists.”

One definition catches people off guard. Paragraph D.8 defines a foreign national as “any person who is not a U.S. citizen or a U.S. national.” A green card holder qualifies. So does a colleague who has held a work visa for twenty years.

Is there really a five-day clock for reporting a contact?

Short answer: No. Paragraph E.2 requires reporting “prior to participation in such activities or otherwise as soon as possible following the start of their involvement.” The five-business-day deadline applies to travel itinerary deviations under ¶ F.1.b.1.

Every numeric figure was checked. SEAD 3 contains five business days (travel deviations and unplanned border day trips), 30 calendar days (foreign national roommate), 120 days (delinquent debt), $10,000 (unusual asset infusion), and 180 days, the gap between its signature on 14 December 2016 and its effective date. None attaches to a contact. The travel text is explicit: “All deviations from approved travel itineraries shall be reported within five business days of return.”

The absence of a number is not permission to wait. “As soon as possible” is harder to satisfy than a fixed deadline, because you cannot point at a calendar and claim compliance. An adjudicator reads it backwards, already knowing what happened next. The difference between continuous vetting and continuous evaluation is worth understanding before you decide something is too small to mention.

When does an “exchange of personal information” become reportable?

Short answer: Under DCSA guidance, three conditions must all be met: you know the person’s name and nationality, the information you gave is not reasonably expected to be public, and the contact recurs. Miss one and it is not reportable on that basis.

DCSA Industrial Security Letter 2021-02, a document no competing article cites, says a reportable exchange meets all of the following: “1. The name and nationality of the foreign national are known by the covered individual during or after the exchange of personal information, and 2. The nature of the personal information provided by the covered individual to the foreign national is not reasonably expected to be accessible by the general public, nor to be willingly released to the general public by the covered individual, and 3. Contact with the foreign national is re-occurring or expected to re-occur.”

Run a scenario through it. You are on a joint program with an engineer seconded from a partner nation. You know her name and citizenship, so condition one is met. Contact recurs weekly, so does condition three. If all you have shared is your work role and your opinion of a subsystem, condition two fails, because none of that is information you would withhold from the public. Add your home address or your children’s school and the threshold has been crossed.

The ISL then removes the ambiguity about official duty: “Contact with foreign nationals occurring solely as part of a covered individual’s official duties, and absent any bonds of affection or obligation, is not required to be reported.” Foreign ownership of your employer does not move the line.

Which reportables depend on your clearance level?

Short answer: SEAD 3 is tiered. Section F binds everyone. Section G adds items for Secret, Confidential and “L” access. Section H adds more for Top Secret and “Q.” Marriage, cohabitants and foreign roommates appear in Section H only.

Most write-ups present every reportable as universal. They are not. Sections G and H each open with “In addition to the reporting requirements in Section F.” The contact rule in F.2 is the floor; the rest scales with access.

Read the table with one caveat. Paragraph E.7 lets agency heads “require additional or more detailed reporting and approval procedures,” so the directive is a floor and not a ceiling. Plenty of programs require Secret holders to report a foreign spouse anyway. Your program’s guidance beats the general rule. The thresholds in that last row are covered in how much debt is actually too much for a clearance, and the Section H foreign-asset row in what you must report about foreign property, foreign bank accounts, and inherited assets.

Why does the answer change depending on who cleared you?

Short answer: Because agencies implement SEAD 3 differently. DoD, through DCSA, applies the “exchange of personal information” prong. The State Department expressly switches it off in 12 FAM 273.4(a). Same directive, opposite answer, identical facts.

12 FAM 273.4(a) reproduces SEAD 3’s language nearly word for word, then adds a sentence the directive does not contain: “Reporting of foreign unofficial contacts is not required when there is only an exchange of personal information.”

The lesson for anyone moving between agencies, or between a government billet and industry: the rule you learned at your last job is not portable. The clearance crossover process moves your eligibility, not your reporting habits.

For cleared contractors the binding authority is regulatory. 32 CFR 117.8(a) incorporates SEAD 3 by name and by URL, and § 117.8(c)(2)(ii) adds a duty to report “efforts by any individual, regardless of nationality, to elicit information.” The wider rule set is covered in our piece on 32 CFR Part 117, and the person who receives your report in FSO requirements for a cleared contractor.

How is this different from what the SF-86 already asked?

Short answer: The form is broader on its face. Section 19 of the SF-86 asks about contact bound by “affection, influence, common interests, and/or obligation” over seven years. SEAD 3 says “bonds of affection, personal obligation, or intimate contact” with no lookback period.

Two words on the Standard Form 86 do not appear in the directive: influence and common interests. A shared hobby could satisfy “common interests” while falling short of the directive’s language, a boundary worked through line by line in decoding the SF-86 close-and-continuing test. The form also imposes a seven-year window the directive lacks.

These obligations stack rather than substitute. State’s FAM notes its requirements “are in addition to the reporting required by the ‘Questionnaire for National Security Positions,’ Standard Form 86.” Answering Section 19 completely in 2023 does nothing for a relationship that changed in 2026.

When you file, Appendix A of SEAD 3 lists what a continuing-association report contains: name, citizenship, occupation, nature of the relationship, duration and frequency of contacts, and current status.

What actually happens if you do not report?

Short answer: The non-report becomes its own security concern. SEAD 4 lists “failure to report or fully disclose, when required, association with a foreign person” as a disqualifying condition under Guideline B, independent of whatever the relationship itself raises.

That is the structural point most cleared professionals miss. The contact and the failure to report it are two separate charges, and the second is often the fatal one. SEAD 4, effective 08 June 2017, frames Guideline B around risk rather than nationality: foreign contacts are a concern “if they result in divided allegiance” or create circumstances in which someone “may be manipulated or induced to help a foreign person, group, organization, or government” in a way inconsistent with U.S. interests.

The mitigating conditions run the other way. AG ¶ 8(e) credits anyone who “has promptly complied with existing agency requirements regarding the reporting of contacts, requests, or threats” from a foreign country. AG ¶ 8(c) credits contact “so casual and infrequent that there is little likelihood that it could create a risk for foreign influence or exploitation.” How those weights get balanced is the whole-person concept.

The worked example is ISCR Case No. 23-00544, decided by the DoD Defense Office of Hearings and Appeals Appeal Board on September 11, 2024. The Statement of Reasons charged Guideline B and Guideline E together. Two holdings are worth memorizing.

The first matters if you change jobs: “the FBI was not his employer and not his ‘company.’ His initial reports to his defense contractor employer in California in 2018 in no way discharged his obligation to inform his new employer in Virginia…” Cooperating with a federal investigation is not a report. A report to your old FSO is not a report to your new one.

The second is the only authoritative gloss that exists on “significant change in the nature of the contact.” The applicant had ended the relationship in December 2018 on an FBI agent’s recommendation, so it was “inarguably a ‘significant change'” for him to fly cross-country to meet her and resume intimate relations. If a report produces an adverse action, responding is covered in our explainer on the Statement of Reasons, and where the determination is recorded in Scattered Castles vs. DISS.

Frequently Asked Questions

Do I have to report a foreign national coworker on a joint program?

Not on the work relationship alone. DCSA ISL 2021-02 states that contact “occurring solely as part of a covered individual’s official duties, and absent any bonds of affection or obligation, is not required to be reported.” The line moves once the relationship turns personal, or once recurring non-public personal information has passed between you.

How soon do I actually have to file?

Paragraph E.2 requires reporting “prior to participation in such activities or otherwise as soon as possible following the start of their involvement.” There is no numeric deadline for contacts in SEAD 3. Any source promising five business days is applying the travel rule from ¶ F.1.b.1 to the wrong category.

Does reporting to the FBI satisfy my obligation?

No. The Appeal Board addressed this in 2024: “the FBI was not his employer and not his ‘company.'” Under ¶ E.8 you report to the agency that sponsors your clearance. For cleared industry that is your FSO, who enters a Customer Service Report in DISS.

Once I report a relationship, do I keep updating it?

Only on a significant change. Paragraph F.2.b.2 says updates “shall occur only if and when there is a significant change in the nature of the contact.” The 2024 decision treated resuming a terminated relationship as inarguably significant.

The rule to actually operate on

The directive gives you a two-prong test with one exemption. DCSA gives you three conditions that make the harder prong testable. Where those run out, the State Department wrote the tie-breaker down: “If in doubt as to whether information is required to be reported, covered individuals should err on the side of caution and report.”

The asymmetry makes that cheap to follow. A reported contact that turns out to be casual costs you a form and a conversation, and under ¶ 8(e) it becomes a mitigating fact if the relationship is ever questioned. An unreported one that turns out to matter costs you a disqualifying condition under ¶ 7(c). Find out this week whether your program office has invoked ¶ E.7 to add requirements beyond the directive. That answer, not SEAD 3, is the rule you are held to.