For cleared industry under DoD cognizance, DCSA’s NISPOM Rule guidance says an initially reported continuing unofficial association needs an update only if a significant change in the nature of the contact meets the SEAD 3 criteria as clarified in ISL 2021-02. Document a breakup, job change, long silence, or renewed message factually and check it against your security office’s instructions.

When does reporting foreign contacts require an update?

After the initial report, compare the new facts with the original relationship and your governing instructions. Under DCSA’s stated standard, update a continuing unofficial association only when the change is significant and meets the SEAD 3 criteria. Your agency may impose stricter requirements.

The controlling policy is Security Executive Agent Directive 3. It addresses covered individuals with access to classified information or who hold a sensitive position, and it allows department or agency heads to set more stringent standards and issue clarifying instructions. It is not a universal command to report every interaction with every non-US citizen.

For cleared contractors, 32 CFR 117.8(a) says contractors and their cleared employees must report the events identified by the rule, SEAD 3, and supplemental cognizant security agency guidance. The contractor must establish procedures so employees with access eligibility know their responsibility to report pertinent information to the facility security officer.

Begin with the instructions supplied by your FSO, security manager, or agency program. Ask a narrow question: “Does this change require an update under the requirements that apply to me, and how should I submit it?” Keep the response with the original report.

Does an ended relationship erase the reporting history?

No. Ending a relationship changes its timeline; it does not change what occurred. Keep the prior report, the approximate final contact date, how the relationship ended, and any later communication so that a future questionnaire or security interview can be answered consistently.

The distinction becomes clear on the OPM Standard Form 86, revised November 2016. Section 19 asks whether, within the last 7 years, you have had close or continuing contact with a foreign national to whom you, your spouse, legally recognized partner, or cohabitant are bound by affection, influence, common interests, or obligation. For each responsive contact, it requests approximate first and last contact dates, methods, frequency, and the nature of the relationship.

Those questionnaire fields do not by themselves establish a continuous-reporting trigger. The SF-86 is asking for a history. SEAD 3, agency instructions, and the applicable security program determine whether a change needs a current update, so treat those purposes as separate.

A clean record can show that you reported the relationship, that its nature later changed, and that contact ended around an approximate point. If you were instructed that no update was required, retain that instruction. The objective is a reconstructable timeline, not a claim that memory is exact.

How should I handle a breakup or estrangement?

Record what changed and when, then ask whether the change is significant under your instructions. Avoid turning an emotional account into a character judgment. Security needs relationship facts, continuing obligations, contact patterns, and any security-relevant event.

Note the approximate date the personal or intimate relationship ended, the last direct contact, whether shared residence or finances ended, whether any continuing obligation remains, and whether future contact is expected. If there was coercion, a threat, attempted elicitation, unusual interest in your work, or another suspicious interaction, say so plainly.

A period of estrangement is not always the same as a final end. If communication is paused but obligations, affection, shared property, or expected contact remain, describe that rather than choosing a cleaner label. DCSA describes a continuing unofficial association as an ongoing relationship involving deeper personal connections, such as bonds of affection, personal obligation, or intimate contact, maintained over time regardless of how the contact is established or maintained.

Preserve earlier evidence instead of deleting it to make the relationship appear over. Keep the reporting acknowledgment and relevant timeline records under your approved storage practices. The practical background on close and continuing contact on the SF-86 can help separate the form’s wording from casual contact.

What if contact simply fades without a clear last conversation?

Use an approximate date and explain the basis. “Last direct message around late spring; no planned contact; relationship gradually became inactive” is more useful than inventing a precise endpoint. Preserve the last ordinary exchange if your information-handling rules allow it.

Silence alone does not prove that every bond or obligation disappeared. Look at the whole relationship: whether either person expects to reconnect, whether money or property remains shared, whether family or professional ties continue, and whether indirect communication persists. Present those facts to security if you need a determination.

A message sent solely to manufacture a definitive last-contact date creates a new contact and may misrepresent the relationship’s natural course. Use the best information you already have and label estimates honestly.

DCSA’s NISPOM Rule guidance also states that limited or casual public contact is not reportable absent another SEAD 3 requirement. That prevents ordinary, incidental encounters from being treated as continuing relationships, but it does not cancel stricter agency or program instructions.

What if a foreign coworker or client changes roles?

A title change is not automatically a reportable relationship change. Document what you actually know: the person’s new role or affiliation, how you learned it, whether your contact continues, whether the nature of communication changed, and whether personal information or obligations are involved.

Official contact and unofficial association are not interchangeable. A relationship can begin through authorized work and later become personal, or a personal contact can acquire a new professional dimension. If that shift changes the nature of the relationship in a way that meets the governing criteria, use the prescribed update route.

Provide known facts and identify uncertainty rather than investigating the person, accessing restricted systems, or asking probing questions to complete a report. Your security office can tell you what further information is required and what collection method is appropriate.

If the new conduct suggests attempted exploitation, unauthorized access, or elicitation, treat it as a separate security concern. The NISPOM reporting rule requires contractors to report specified suspicious contacts involving those behaviors, including certain efforts by a person regardless of nationality.

What should I do when contact resumes after a long gap?

Add a new entry to the chronology and reassess the current relationship. Record the date, method, initiator, stated reason, content at a safe factual level, and whether further contact is expected. Then compare the renewed pattern with your earlier report and present instructions.

One ordinary message may remain limited or casual. Under ISL 2021-02, the separate personal-information trigger requires all 3 conditions: you know the foreign national’s name and nationality; the information you provided is not reasonably expected to be public or willingly released to the public; and contact recurs or is expected to recur. Revived affection, a renewed obligation, or suspicious interest can present different grounds for review. An old report does not answer what the new contact means now.

Report promptly when your instructions direct; do not wait for a pattern if the interaction itself is suspicious. If it is benign but the update standard is unclear, ask the FSO or security manager before deciding that the old report covers everything.

The detailed boundaries for initial and continuing reports are discussed in SEAD 3 foreign-contact reporting. The useful move after renewed contact is to supply the delta: what changed from the facts already on record.

Which dates, messages, and records should I retain?

Keep a compact change log rather than an indiscriminate archive. The log should let you reconstruct the relationship, the reports you made, the security office’s response, and the basis for approximate dates without retaining more personal content than necessary.

Keep classified information, protected system screenshots, and another person’s sensitive records out of a personal file. Ask where acknowledgments and supporting material may be stored. A personal chronology can use neutral wording and refer to the official submission without copying protected content.

If a questionnaire later asks for a current address, employer, or affiliation you do not know, follow the form’s instructions rather than searching intrusively. “Unknown” and an honest explanation are different from a guess presented as fact.

How do I write a short factual update to security?

Identify the prior report, state the change, give approximate dates, explain the current contact pattern, and flag any continuing obligation or security concern. Close by asking whether any additional fields or documentation are required under the rules that apply to you.

A concise structure is: previously reported relationship; event that changed it; date or estimated period; last or renewed contact; current frequency and methods; continuing personal, financial, residential, or professional connection; known new affiliation; and any suspicious behavior. Use neutral verbs.

Avoid conclusions such as “not a risk,” “completely harmless,” or “definitely no longer reportable.” Those are not facts you need to adjudicate. Likewise, do not diagnose the other person’s motives. State what happened and let the authorized office apply its standard.

The broader continuing obligation is explained in security-clearance foreign-contact reporting obligations. Open your prior acknowledgment now and add one dated line stating the latest actual contact and the relationship’s current status.

Frequently Asked Questions

Must I report every foreign contact again when it ends?

Not as a universal rule. DCSA states a significant-change standard after initial reporting, while SEAD 3 permits stricter department or agency requirements. Ask your assigned security office how that standard applies to the change.

Is a social-media connection a continuing relationship?

Not by itself. DCSA says reporting limited or casual public contact with foreign nationals is not required absent another SEAD 3 reporting requirement. A continuing association with bonds of affection, personal obligation, or intimate contact, or contact that involves an exchange of personal information and recurs or is expected to recur, is judged on the nature of the relationship, regardless of how the contact is established or maintained, social media included. Your security office can tell you how your agency applies this.

What if I cannot remember the exact last-contact date?

Use an honest approximation and explain its basis. The SF-86 expressly asks for approximate contact dates. Do not fabricate precision or restart contact merely to create an endpoint.

Does an old report cover renewed contact forever?

Do not assume it does. Document what resumed and compare the current facts with the original report and governing instructions. Ask security whether the renewal is a significant change requiring an update.

Where should a cleared contractor employee send an update?

Use the contractor’s established security channel, ordinarily the FSO or assigned designee, unless your program instructions specify another route. Do not submit sensitive details through an unapproved channel.