SORNA Relocation and International Travel: A Registry Handoff Guide

Moves are where registry records most often break down. A registrant leaves one county or state, the sending agency closes its file, and the receiving agency never hears about the move or hears about it weeks later. In the gap, nobody is tracking the person and nobody can say with confidence whether a violation occurred.

This article walks through what federal SORNA requires when a registrant relocates, changes jobs or schools across jurisdiction lines, or plans international travel. It also covers how sending and receiving agencies can coordinate, and where handoffs commonly fail. Federal SORNA sets minimum standards, and state law may be stricter or different, so check your state statute and agency policy.

Where registration is required

Under the Sex Offender Registration and Notification Act (SORNA, 34 U.S.C. § 20901 et seq.), a registrant must register, and keep the registration current, in each jurisdiction where they reside, where they are employed, and where they are a student. Federal SORNA also requires initial registration in the jurisdiction of conviction if it differs from the jurisdiction of residence.

That means a single registrant can have obligations in more than one place at once. Someone who lives in one state and works across the border in another may be registered in both. Every move, job change, or school enrollment can add or remove a jurisdiction from that list.

The 3-business-day rule

Federal SORNA requires a registrant, within 3 business days of a change of name, residence, employment, or student status, to appear in person in at least one jurisdiction where they are required to register and report the change. That jurisdiction must then share the updated information with the other jurisdictions where the registrant is required to register.

In practice, this rule creates two duties:

• The registrant's duty to appear and report within the deadline.
• The agency's duty to pass the information along promptly so other jurisdictions can act on it.

Many states set their own deadlines, require advance notice before a move, or require registrants to report to both the old and new agency. Check your state statute and agency policy for the exact requirement.

Coordinating sending and receiving jurisdictions

A clean interstate or intercounty transfer depends on both sides doing their part. The table below outlines typical responsibilities.

Two points deserve emphasis. First, the receiving jurisdiction applies its own law, so tier, registration period, and verification schedule may change. Second, the sending agency should not consider the case finished until it has confirmation that the registrant registered in the new location.

When a registrant fails to register after a move, the case may become a federal matter. The U.S. Marshals Service is the lead federal agency for investigating SORNA registration violations, including failure to register under 18 U.S.C. § 2250. Agencies should follow their state's procedures for referring these cases. Our article on absconder response workflows covers that process in more depth.

The 21-day international travel notice

Federal SORNA minimums require registrants to report intended international travel at least 21 days in advance. The National Guidelines and later federal rules, including 28 CFR Part 72, describe the information jurisdictions should collect and share.

A useful intake for international travel captures:

• Departure and return dates
• Destination countries and addresses where the registrant will stay
• Purpose of travel
• Carrier and itinerary details, where available
• Passport or travel document information, recorded in the restricted record and not on the public website

Jurisdictions are expected to share international travel information with federal partners, including the U.S. Marshals Service, according to their state's procedures. A registrant who plans to leave the United States to live abroad also has reporting obligations. State law may set additional requirements, so confirm local rules and document every notification you send.

Documentation and handoff checklist

Use this checklist for every relocation, cross-jurisdiction job or school change, and international trip.

1. Record the date the registrant reported the change and the method of reporting.
2. Confirm the report met the 3-business-day or 21-day requirement, and document any late report.
3. Capture the full destination address, employer, or school, plus expected start or travel dates.
4. Identify every jurisdiction affected, including those where the registrant works or attends school.
5. Send notice and current registration information to each affected jurisdiction.
6. Log each notification with the date, recipient agency, and method.
7. Update NSOPW and NCIC records according to your submission procedures.
8. Set a follow-up date to confirm registration in the receiving jurisdiction or the registrant's return from travel.
9. Close or update the local record only after confirmation is received.
10. If confirmation does not arrive, escalate per agency policy and document each attempt.

Common failure points

Most relocation problems come from a small set of gaps:

• Closing the file too early. The sending agency marks the record inactive before the receiving agency confirms registration.
• Missing secondary jurisdictions. A move is reported, but the jurisdiction where the registrant works is never notified.
• Incomplete transfer packages. Photos, tier basis, or offense details are missing, so the receiving agency has to start over.
• No follow-up date. Nobody owns the task of confirming arrival.
• Travel recorded but not shared. International travel is logged locally but never sent to federal partners.

To measure how your unit is doing, review the last twelve months of outgoing moves and count how many have documented confirmation from the receiving agency, and how many days each confirmation took.

Next steps for your unit

Relocation and travel work is mostly about closing loops. Write down who owns each step, set follow-up dates for every handoff, and review open transfers weekly so none slip through.

Justice Compliance includes interstate transfer and agency transfer workflows, along with file exports for NSOPW and NCIC submission. You can explore the operational use scenarios or download the complete guide to SORNA compliance for more on federal requirements.