Intergovernmental Personnel Agreement (IPA) — Structure, Authority, and Operational Reality

Intergovernmental personnel agreement programs are one of the least understood—but most widely used—mechanisms in federal operations. On paper, they exist to promote cooperation and knowledge sharing. In practice, they create a layered system where authority, supervision, and accountability can span multiple jurisdictions at once.

This is where coordination happens. This is also where lines begin to blur.

What an intergovernmental personnel agreement actually is

An intergovernmental personnel agreement (IPA) is authorized under the Intergovernmental Personnel Act of 1970 (5 U.S.C. §§ 3371–3376). It allows personnel to move between federal agencies and eligible non-federal entities without changing their underlying employment status.

Instead of hiring new employees, agencies temporarily embed existing personnel into different environments. This allows expertise to move faster than traditional hiring processes would permit.

Eligible organizations include:

• State and local governments
• Universities and academic institutions
• Tribal governments
• Federally funded research centers
• Nonprofit organizations with qualifying status

The result is a hybrid role—legally anchored in one organization, operationally active in another.

Legal authority and regulatory structure

The IPA system is not informal. It is built on layered federal authority:

• 5 U.S.C. §§ 3371–3376 — establishes the program
• 5 CFR Part 334 — defines how it operates
• Office of Personnel Management (OPM) — administers and oversees implementation

Reference: OPM IPA Guidance

These authorities define limits, but they do not eliminate complexity.

How IPA assignments function in real operations

On paper, the process is structured. In practice, execution depends heavily on how the agreement is written.

1. An agreement is negotiated between two entities
2. The individual assignee is selected
3. A statement of work defines duties
4. Funding responsibilities are assigned
5. Supervision and reporting chains are established

Assignments typically last between two and four years. However, the operational impact begins immediately.

The individual now operates inside a system where:

• They may follow policies from two entities
• They may report to supervisors outside their employer
• They may access systems not normally available to their home organization

That overlap is where the system becomes powerful—and complicated.

Documentation and structural control

Every IPA assignment is backed by documentation. These records define how the assignment operates and where authority sits.

• IPA Mobility Agreement (core contract)
• Statement of Work (SOW)
• Funding agreement
• SF-50 (for federal personnel)

In theory, these documents provide clarity. In practice, they determine control.

IPA vs IGA vs MOU — understanding the system layers

Different agreements serve different purposes, and confusing them leads to misunderstanding how systems operate.

• IPA — moves personnel
• IGA — moves funding and services
• MOU/MOA — defines cooperation without direct exchange

Personnel, money, and authority each move through different channels.

Understanding which channel is active matters.

Where the system becomes complex

At a surface level, IPA agreements improve efficiency. However, complexity emerges when authority overlaps.

• Supervision may not match employment
• Policy enforcement may vary between agencies
• Accountability may be distributed across entities

This creates environments where responsibility can become difficult to trace without documentation.

Operational implications in sensitive systems

IPA assignments often appear in high-impact environments:

• Public health response systems
• Federal research initiatives
• Law enforcement coordination
• Detention and administrative systems

In these environments, authority matters. Oversight matters more.

When personnel operate across systems, the structure behind that movement determines how decisions are made and who is responsible for them.

Transparency, FOIA, and traceability

IPA agreements are not invisible. They create a paper trail that can be accessed through federal records requests.

• Executed agreements
• Statements of work
• Funding structures
• Assigned personnel records
• Interagency communications

Because of this, IPA programs are traceable.

Once analyzed, those records reveal how coordination actually functions—not just how it is described.

For related structural analysis, see the intergovernmental contract agreements overview.

At a glance, these agreements look administrative.

Underneath, they define how systems connect.

And once those connections are mapped, the structure becomes visible.

That visibility is where understanding begins.