SEAD-3 Foreign Travel & Contact Reporting
Cleared employees file foreign travel and contacts in-app; your FSO gets a dated queue with an audit trail instead of a mailbox.
Continuous vetting turned clearance holding into an ongoing reporting obligation, not a one-time investigation. Under SEAD-3 cleared personnel report foreign travel — normally before departure — and foreign contacts as they arise. Most contractors run that on email, a SharePoint form, or a spreadsheet, which means no dated record, no review trail, and no way to show what was reported when. This puts the whole loop in the system that already holds your clearances.
What you get
Built to solve the actual problems hiring teams hit every day.
Employees self-report in two clicks
A cleared employee picks Foreign travel or Foreign contact, fills a short form — destination and dates, or contact name, country and nature — and files it. The timestamp is the record.
Pre-departure is the default path
The travel form leads with departure date because that is what SEAD-3 expects. A report filed after departure is accepted and flagged as such for the FSO rather than rejected — late is far better than never.
FSO queue ordered by what needs action
Unresolved reports come first, oldest first, so nothing quietly ages out of sight. Tiles show what is awaiting review and how many unresolved travel reports still have a departure date ahead of them.
Real adjudication, not just an inbox
Acknowledge a report, request more information with a note explaining what is missing, or close it. The employee is notified of the outcome every time.
Closed reports are immutable
A closed self-report is part of the audit trail and cannot be reopened or rewritten — a follow-up is a new report. That is what makes the history worth anything in a review.
Sensitive by default
Row-level security scopes reports to the employee who filed them plus admins in their own organization. Peers can never read them, and there is no anonymous access.
How it works
Four steps from setup to value.
Employee opens Foreign Reporting
Under Security → Foreign Reporting, they choose Foreign travel or Foreign contact.
File the report
Travel takes destination country and departure date (return date and purpose optional). A contact takes name, country, and the nature of the association. Both accept free-text details.
FSO is notified
Admins in the organization get an in-app and email notification that a report is waiting — on by default, because travel reporting is time-sensitive.
Review it
In Admin → Foreign Reports, the FSO acknowledges, requests more information (a note is required so the employee knows what to provide), or closes the report.
Employee hears back
The person who filed it is notified of the outcome, and a request for more information shows inline on their own report list.
FAQ
Quick answers to common questions.
Does this make us SEAD-3 compliant?
No. It is a system of record that supports your self-reporting program — collecting, timestamping, and adjudicating reports with an audit trail. It does not certify compliance, does not transmit anything to any government system, and does not replace your FSO's own reporting duties or guidance.
Does it send reports to DCSA or any government system?
No. Reports stay in your instance. The FSO reviews them here and handles any onward reporting through their normal channels.
Can an employee file a report on someone else's behalf?
No. The filer is always taken from the authenticated session, never from the request, so a report is always attributable to the person who submitted it.
Can a closed report be reopened?
No — deliberately. Closed reports are part of the audit trail, and reopening one would rewrite history. If something changes, the employee files a new report and the original stays intact.
Who can see a report?
The employee who filed it and admins in their organization. Row-level security enforces this at the database, not just in the UI, and peers have no access at all.
What if someone reports travel after they get back?
It is accepted and stored, and the FSO queue marks it "filed after departure" so your security office can see the pattern. The tool never blocks a late report.