The Invisible Transfer: How IPAs Move Authority

The Intergovernmental Personnel Agreement framework, created under the Intergovernmental Personnel Act of 1970 (5 U.S.C. §§ 3371–3376), enables personnel assignments between federal and non-federal entities. An employee who accepts such an assignment never leaves the original agency. They operate elsewhere, answer to a different chain of command, and on paper nothing changes at all. The result is mobility without separation, a transfer of presence rather than of employment.

The IPA framework — 6-month to 2-year assignments:

Assignments typically run from six months to two years. They move personnel between federal and state counterparts in both operational and administrative roles, and they do so without the ceremony of a transfer order or a change of badge.

Where intergovernmental systems appear — rarely in print:

IPA rarely appears in print, yet its effects surface everywhere. Joint investigative task forces, regional intelligence centers, detention system coordination, and federal-local enforcement overlap all rest on the same quiet machinery of borrowed personnel. This is where authority becomes difficult to trace. The questions of who is in charge, who carries liability, and whose authority is being exercised often go unanswered, and that ambiguity is a feature rather than a flaw of the design.

“The result: mobility without separation.”

Why the person never changes at the boundary:

Every intergovernmental move preserves the person while changing the paper. The same hands, the same eyes, the same training, and the same loyalty contacts arrive inside a county jail instead of a federal building. Legal power travels with them without needing to change a nameplate, which is why the boundary feels invisible to the people working it.

U.S. Marshals Service integration — the central node:

The U.S. Marshals Service sits at the center of federal enforcement logistics: warrant execution, detainee transport, pretrial detention logistics, and judicial protection. Its effectiveness depends on integration with local agencies, task forces, and intergovernmental systems, and in many cases personnel operate through intergovernmental personnel agreement structures rather than through direct employment.

IPA vs IGSA vs task force — the three-lane system:

Three systems share the load at different altitudes. An IPA moves personnel. An IGSA contracts services, such as a county jail housing federal detainees. A task force coordinates operations, such as joint federal investigations. These systems form a distributed network that is not centralized but tightly connected, and each one decides who owns the decision, who owns the liability, and who owns the excuse afterward.

How the structure behaves in court:

Defense attorneys trying to depose the right signatory find that the signatory signed on someone else's behalf, who signed on contract terms they never authored, under a named federal reading, under a county order, under a task force agreement. Each layer can produce documents that support a different version of who authorized the assignment, and the resulting confusion is the point.

Why the structure matters:

This is not administrative design but operational architecture. Who acts, who authorizes, who is accountable, and sometimes who is not. Intergovernmental personnel agreement systems define how authority moves without appearing to move, and they do it by leaving almost no trace for outsiders to follow.

What the Record Shows:

Authority moving through an IPA leaves almost no trace for outsiders to follow: one statute, invisible in print, invisible in courtrooms, visible only when it surfaces in a filing. Everything about the intergovernmental architecture, from the mobility to the six-to-two-year window to the Marshals Service integration layer to the distributed network, is designed to create mirrors at every boundary so accountability loses focus at the hand-off.