Intergovernmental Personnel Agreement Structure Authority
On paper it promotes cooperation. In practice, it blurs the very lines it was supposed to leave clear.
Intergovernmental personnel agreement programs are among the least understood — yet 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 — allowing 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 — letting expertise move faster than traditional hiring can permit.
Eligible organizations include:
- State and local governments - Universities and academic institutions - Tribal governments - Federally funded research centers - Nonprofit organizations with qualifying status
- 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
These authorities define limits — but they do not eliminate complexity.
“5 U.S.C. §§ 3371–3376 — establishes the program.”
How IPA assignments function in real operations:
An agreement is negotiated between two entities; an individual assignee is selected; a Statement of Work defines duties; funding responsibilities are assigned; 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.
- IPA Mobility Agreement — core contract - Statement of Work (SOW) — defines duties - Funding agreement — money moves with the assignment - SF-50 — for federal personnel
In theory, these documents provide clarity. In practice, they determine control — who signs, who reports, who budgets, who can be contradicted, and who retires before review.
IPA vs IGA vs MOU — the three mechanisms confused on purpose:
- IPA — moves personnel - IGA — moves funding and services - MOU / MOA — defines cooperation without direct exchange
The operational reality — where the paper doesn't match the floor:
The operational reality is that IPA assignments live in limbo between two bureaucracies — every line of authority is one email away from someone whose name isn't on the chart.
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.
- Public health response systems - Federal research initiatives - Law enforcement coordination - Detention and administrative systems
Operational reality — why the complexity isn't accidental:
Accountability is easier to dodge when the chain crosses two address books. The entire IPA architecture is engineered around that distance — and once the geometry is exposed, the purpose becomes legible.
Transparency, FOIA, and traceability:
IPA agreements are not invisible — they create a paper trail accessible through federal records requests: executed agreements, Statements of Work, funding structures, assigned personnel records, and interagency communications — because of this, IPA programs are traceable. Once analyzed, they reveal how coordination actually functions — not just how it is described.
What the Record Shows:
The agreements look administrative — underneath, they define how systems connect. Once those connections are mapped, the structure becomes visible — and visibility is where accountability begins.