How to Build Effective Federal-State Partnerships in Public Administration

Nearly 60 percent of statutory directives in the U.S. Code involve federal-state partnerships, according to a full-text analysis of over 3.7 million sentences conducted by Pamela Clouser McCann and Jennifer L. Selin for the Administrative Conference of the United States.¹ That proportion makes intergovernmental collaboration less of a special case and more of a baseline condition for how American governance actually operates.

Yet these partnerships remain surprisingly poorly understood. Communication breakdowns, perfunctory engagement, and tacit practices that never get documented create persistent gaps in trust and accountability. When relationships depend on informal norms rather than deliberate cultivation, public policy making suffers alongside program outcomes.

ACUS Recommendation 2026-4, adopted January 21, 2026, offers a framework for addressing these deficiencies, one that treats partnership-building as a core administrative competency rather than an afterthought.

Why Federal-State Partnerships Are the Norm, Not the Exception

The conventional wisdom among many public administration students and practitioners is that federal-state partnerships are exceptional arrangements, activated only for specific programs or crises. Yet a groundbreaking analysis for the Administrative Conference of the United States (ACUS) reveals a very different picture. The study, led by Pamela Clouser McCann and Jennifer L. Selin, constitutes the most comprehensive mapping of intergovernmental mandates ever conducted, and its findings challenge the way we think about public administration vs public policy and administrative collaboration.

A Landmark Analysis of the U.S. Code

The researchers performed a full-text analysis of over 3.7 million sentences across all 53 titles of the U.S. Code. This unprecedented scan was not a sampling exercise; it examined every single sentence in the federal statutes to identify provisions requiring or authorizing engagement with state, tribal, local, and territorial governments (SLTTGs). The result, adopted as ACUS Recommendation 2026-4 on January 21, 2026,¹ provides the first systematic accounting of just how deeply cooperative federalism is woven into the legal fabric of American governance.

The Partnership Distribution: Who's Really Involved

The numbers are striking. About 60% of the identified statutory provisions involve federal-state partnerships.² An additional 30% concern localities, 12% reference tribal governments, and the remaining provisions address territories. This means that for every purely federal administrative process, there are at least two that require direct engagement with state or local counterparts. For a student of public administration, this distribution signals that managing multi-level relationships is not a niche skill; it is the default operating environment for nearly every federal agency.

From Text to Practice: A Multi-Method Approach

Recognizing that statutory text alone cannot capture the reality of implementation, McCann and Selin supplemented their code analysis with robust qualitative and quantitative methods. They conducted more than 60 interviews with federal agency officials and SLTTG representatives, administered a survey of agency personnel, hosted a dedicated listening session for tribal governments, and published a request for information in the Federal Register.¹ This triangulation of data sources ensures that the recommendations are grounded not only in legal analysis but also in the lived experience of practitioners navigating these partnerships daily.

For current and future public administrators, the takeaway is clear: treating intergovernmental collaboration as an ad hoc or peripheral function is a fundamental misreading of the legal and operational landscape. Cooperative federalism is the baseline, not the exception. The ACUS framework offers a path toward moving from perfunctory compliance to intentional, well-managed partnership practices that can enhance policy outcomes across the entire administrative state.

Federal-State Partnerships at a Glance

A landmark study prepared for the Administrative Conference of the United States (ACUS) reveals just how deeply intergovernmental collaboration is woven into the fabric of federal law. For MPA and MPP students, these figures frame the sheer scale of the research and the partnerships it uncovered.

Key Success Factors for Effective Federal-State Collaboration

Compliance-driven partnerships and relationship-driven partnerships may both rest on the same statutory foundation, yet they produce vastly different outcomes in practice. The first treats legal mandates as an endpoint; the second treats them as a starting point. Research conducted for the Administrative Conference of the United States, drawing on more than 60 interviews with federal agencies, state and local officials, tribal representatives, and other stakeholders, points consistently to five factors that separate high-functioning intergovernmental partnerships from ones that merely fulfill a paperwork requirement.¹

Shared Objectives and Joint Planning

Partnerships that perform well begin with a deliberate effort to align on what success actually looks like. When the Army Corps of Engineers coordinates with state environmental agencies on water navigation projects, for example, both sides bring different statutory authorities to the table. Getting those authorities to pull in the same direction requires explicit conversations about shared goals before implementation begins, not after a disagreement surfaces.

Structured Communication

Frequency and format of communication matter as much as the willingness to communicate. High-functioning partnerships build in regular touchpoints, designated contacts, and agreed-upon escalation paths. Interviewees described the difference between agencies that exchange formal reports and those that maintain ongoing dialogue as the difference between knowing about a problem and actually solving one. A standing working group, a shared data platform, or even a reliable monthly call can institutionalize the kind of contact that prevents misunderstandings from hardening into conflict.

Clear Role Delineation

Statutes assign responsibilities, but they rarely specify who calls the meeting, who documents the decision, or who owns the relationship when personnel turn over. The FDIC's supervision of state-chartered banks under the Federal Deposit Insurance Act illustrates this: the statute creates a shared oversight framework, but the operational details of which agency leads on a given examination require negotiation and documented agreement outside the statute itself.

Trust and Relationship-Building

Of all five factors, trust was cited most frequently across interviews as the variable that distinguishes genuinely productive partnerships from perfunctory ones. Trust is not a personality trait; it is built through consistent follow-through, transparency about constraints, and a track record of honoring informal commitments as well as formal ones. DEA task forces that work alongside state and local law enforcement under the Controlled Substances Act succeed or fail in large part based on whether field-level relationships have been cultivated over time.

A Practical Takeaway for MPA and MPP Students

These competencies are learnable. Intergovernmental negotiation, stakeholder communication, and relationship management are skills that can be developed through coursework, simulation exercises, and supervised practice, just as budget analysis or policy writing can be. Advancing federal administration best practices requires graduate programs to treat intergovernmental relations as a practical skill set rather than a theoretical backdrop, so that future administrators are not underprepared for work environments where multi-level coordination is routine. The gap between what a statute requires and how agencies actually collaborate is precisely where administrative competence matters most, and it is precisely where deliberate professional preparation pays off.

Questions to Ask Yourself

Governance Models and Structures That Work

Selecting a governance model for interagency collaboration involves a fundamental tradeoff: centralized control for consistency, or decentralized autonomy for responsiveness. The right structure depends on the complexity of the partnership, the sensitivity of shared data, and the need for uniform accountability across multiple jurisdictions.

Centralized Governance: Consistency at Scale

In a centralized data governance model, decision authority rests with a Chief Data Officer (CDO) or a central governance office.¹ This structure excels when standardization and policy enforcement are non-negotiable, as in cross-state program eligibility or uniform reporting on federal grants. Centralization delivers high accountability because one entity owns the rules, but it limits flexibility; local implementers may struggle to adapt to unique conditions without lengthy approvals.

• Decision authority: CDO or central governance office
• Typical use case: Standardization and consistency enforcement across the enterprise
• Accountability: High
• Flexibility: Low

Decentralized Governance: Speed and Local Adaptation

Decentralized governance pushes decision-making to individual business units, in the federal-state context, to state agencies or regional offices.¹ It enables fast, context-sensitive responses, which is critical when local conditions vary widely. However, this speed often comes at the cost of accountability, as fragmented policies and inconsistent data practices can undermine program integrity.

• Decision authority: Individual business units
• Typical use case: Local autonomy and fast decision-making for business units
• Accountability: Low
• Flexibility: High

Federated Governance: The Middle Ground

Federated governance balances the extremes by establishing a central body that sets high-level policies, while domain-level teams (such as state or program offices) handle implementation.¹ This model suits large, diverse enterprises, including federal-state partnerships where common standards are essential but local innovation is also valued. Accountability is moderate and flexibility is balanced, making it a practical choice for intergovernmental data sharing and joint program administration. Public affairs specialists working across jurisdictions often navigate exactly these tradeoffs in daily practice.

• Decision authority: Central body for policies, domains for implementation
• Typical use case: Large diverse enterprises needing balance between central standards and local flexibility
• Accountability: Moderate
• Flexibility: Balanced

Governance for AI Systems: The EU AI Act Model

Regulatory frameworks add another governance layer. The EU AI Act prescribes mandatory compliance rules for high-risk AI applications, with enforcement overseen by the European Commission and member state authorities.² Its high accountability and low flexibility mirror centralized governance, making it a useful reference for intergovernmental AI projects where public trust is paramount. ACUS Recommendation 2026-4 underscores the need for similarly clear, enforceable structures when federal and state partners deploy automated decision tools.

• Decision authority: European Commission and member state authorities
• Typical use case: High-risk AI applications in the European Union
• Accountability: High (mandatory compliance)
• Flexibility: Low (prescriptive rules)

These models are not mutually exclusive. Practitioners often combine elements, for instance, using a federated data governance structure while adhering to centralized regulatory requirements for AI. The key is to explicitly design the governance architecture, rather than letting it emerge haphazardly, to ensure that federal-state partnerships are both effective and accountable.

Performance Metrics and Accountability Tools for Federal-State Programs

Too many federal-state initiatives mistake activity for achievement: meetings are convened and reports get filed, yet without standardized performance metrics it is impossible to tell whether collaboration produces value or merely goes through the motions. The 2026 ACUS report on federal-SLTTG partnerships confirmed what many public administrators already suspect: most intergovernmental efforts lack a common yardstick for success. That gap not only undermines accountability but also erodes the trust essential for long-term cooperation.

The Measurement Gap

Statutory mandates establish the legal architecture for federal-state partnerships, yet they rarely prescribe how performance should be tracked. As a result, agencies often default to counting inputs, such as grants disbursed and compliance letters sent, while neglecting outcomes that matter to citizens. The Government Performance and Results Act (GPRA) Modernization Act of 2010 pushed for cross-agency priority goals,¹ but its application to state-level collaborations remains uneven. Without a deliberate measurement strategy, even well-intentioned partnerships risk becoming tick-box exercises.

Four Practical KPI Categories

Drawing on frameworks from OMB Circular A-11 and GAO guidance, practitioners can structure metrics across four dimensions:

• Process metrics track administrative engagement, such as meeting frequency, joint planning timelines, and response rates to intergovernmental inquiries.
• Outcome metrics measure whether shared objectives are met: reductions in program backlogs, expanded beneficiary reach, or improved service delivery times.
• Relationship metrics assess partner satisfaction and trust, often gathered through periodic surveys or tracked via dispute frequency, exactly the kind of data the ACUS authors found lacking in most federal-state programs.
• Equity metrics examine how resources and benefits are distributed among partner types, an emerging priority in federal performance guidance.

These categories align with OMB's logic model guidance (August 2021),³ which helps agencies map inputs, activities, outputs, and outcomes, a model that can be adapted for multi-level governance.

Performance Agreements and Dispute-Resolution Protocols

A robust accountability system must also include formal agreements that define mutual expectations. Performance agreements typically specify joint goals, data-sharing responsibilities, reporting frequencies, and, critically, an escalation pathway for disputes. The ACUS research revealed that many partnerships rely on tacit understanding and personal relationships, which, while valuable, are fragile when personnel change. Codifying protocols, as underscored by the Agency Performance Act of 2024's requirement for annual strategic reviews,¹ ensures continuity and fairness. Dispute-resolution clauses, often modeled on alternative dispute resolution techniques, can prevent minor disagreements from derailing entire programs.

Guidance Documents to Start With

Agencies do not need to invent measurement systems from scratch. the Federal Performance Framework (OMB Circular A-11, 2024) offers a blueprint for program improvement, while the GAO's 2021 report on cross-agency priority goals and performance management provides concrete recommendations that remain relevant.² The federal approach, embodied in four-year Cross-Agency Priority Goals and two-year Agency Priority Goals, demonstrates how multi-level targets can align effort.¹ Performance.gov aggregates agency performance plans and results, offering real-world examples. Yet administrators should note that as of 2025, GAO tallied 18 open recommendations on cross-agency goal implementation,⁴ a sign that even the federal level is still refining its approach. Starting with a few well-chosen KPIs and building incrementally is a pragmatic path that respects this complexity.

Cross-Sector Case Studies: What Practitioners Can Learn

Examining partnership structures across sectors reveals transferable strategies that transcend any single agency's mandate. The three examples documented in the ACUS research demonstrate how different regulatory contexts require distinct governance approaches, yet all depend on sustained relationship-building and role clarity to succeed.

Water Navigation: Army Corps and State Environmental Agencies

The Army Corps of Engineers coordinates with state and local environmental regulators on waterway permitting and flood control, balancing federal navigation interests with local habitat protection. This partnership operates through formal inter-agency agreements that specify review timelines and joint field inspections. Practitioners can replicate two core practices: establishing standardized documentation protocols that satisfy both federal and state legal requirements, and creating standing technical working groups that meet quarterly rather than convening only when disputes arise. The predictability of engagement reduces delays and builds institutional memory across staff transitions.

Banking Supervision: FDIC and State-Chartered Banks

Under the Federal Deposit Insurance Act, the FDIC supervises state-chartered banks through a shared examination regime with state banking departments. This model assigns primary examination authority based on institutional risk profiles and alternates exam cycles between federal and state examiners. Replicable elements include risk-based tiering that concentrates federal oversight where systemic exposure warrants it while allowing state regulators autonomy over community institutions, and unified reporting platforms that eliminate duplicative data requests from financial institutions. The structure reduces compliance burden while maintaining safety-and-soundness standards.

Law Enforcement: DEA and State Task Forces

DEA task forces under the Controlled Substances Act embed federal agents with state and local narcotics units, pooling resources and legal authorities. Participating state officers receive federal deputization, enabling them to enforce federal statutes while maintaining state investigative roles. Two practices stand out: cross-training programs that familiarize state officers with federal evidentiary standards before joint operations begin, and shared asset forfeiture protocols that distribute seized funds according to pre-negotiated formulas. Clarity on financial incentives and procedural expectations reduces friction when investigations span multiple jurisdictions.

Health: Oregon Medicaid Coordinated Care Organizations

The Oregon Health Authority partnered with community-based Coordinated Care Organizations (CCOs) to integrate physical, behavioral, and dental care for Medicaid beneficiaries. This federal-state-local collaboration reduced adult Medicaid readmissions by 33 percent¹, increased adolescent well-care visits by 38 percent¹, and cut diabetes-related admissions by 29 percent within four years.¹ Replicable practices include capitated payment models that incentivize prevention over episodic treatment, and governance boards with mandatory seats for enrollees and community representatives. The structure aligns financial incentives with population health outcomes rather than service volume, a principle applicable to defining public policy goals in workforce development and education partnerships.

Health: New York Medicaid Delivery System Reform

New York's Medicaid Reform Team secured a federal 1115 waiver to reinvest 8 billion dollars in projected savings, allocating 6.42 billion dollars through the Delivery System Reform Incentive Payment (DSRIP) program.² The partnership between the New York State Medicaid agency and federal CMS yielded 17.1 billion dollars in federal Medicaid savings over five years by restructuring payment models and reducing avoidable hospitalizations.² The state's Healthy Neighborhoods Program, a parallel initiative, serves 7,000 homes annually by addressing asthma triggers through coordinated Medicaid and public health interventions.² Practitioners can adapt the waiver negotiation process, which involved multi-year stakeholder engagement and iterative federal feedback cycles, and the performance-based payment structure that required measurable clinical and financial outcomes before releasing incentive funds.

Across all five cases, measurable outcomes followed from three shared practices: multi-year funding commitments that allowed partners to hire dedicated staff rather than relying on temporary assignments, transparent data-sharing agreements that specified permitted uses and security protocols, and formal dispute resolution mechanisms established before conflicts emerged rather than during crises.

Common Pitfalls and How to Overcome Them

More than 60 interviews conducted for the ACUS research project revealed a consistent pattern: federal-state partnerships frequently stumble not from bad policy design but from preventable operational failures. Understanding these failure modes, and having concrete responses ready, separates administrators who manage intergovernmental programs well from those who simply manage them.

Perfunctory Engagement

One of the most common complaints from state and local officials is that federal agencies consult them on paper but not in practice. Comment periods open and close with no visible effect on decisions. Listening sessions become performances rather than genuine exchanges. The corrective is structural: agencies should establish written feedback loops that document how state input was considered and, when it was not incorporated, explain why. Closing that loop in writing transforms consultation from a ritual into a meaningful exchange.

Tacit Practices That Freeze Out New Partners

Long-running partnerships accumulate informal norms that experienced participants understand intuitively but newcomers never learn. A new state liaison can spend months performing tasks incorrectly simply because no one explained that certain processes work differently in practice than they do on paper. Formal onboarding protocols, updated at least annually, and a designated federal point of contact for relationship questions (not just technical ones) can close this gap quickly.

Asymmetric Information and Power

Federal agencies typically hold more data, more legal authority, and more resources than their state counterparts. That asymmetry can quietly distort collaboration: states may defer to federal preferences rather than flag concerns, or withhold information they fear will trigger enforcement. Joint training programs, where federal and state staff learn alongside each other, help redistribute status and build the informal trust that makes candid communication possible. Shared data dashboards, where both parties see the same figures at the same time, reduce the information gap directly. For administrators building these skills, professional development in public policy offers structured frameworks for navigating exactly these intergovernmental dynamics.

Underfunded Mandates and Capacity Gaps

When federal law assigns states new administrative responsibilities without corresponding resources, compliance becomes superficial. Agencies should conduct realistic capacity assessments before rolling out new requirements, and where funding gaps exist, phase-in timelines or technical assistance programs can prevent early failures from hardening into permanent dysfunction.

Turnover and Lost Institutional Knowledge

High staff turnover at both federal and state levels erases the relationship capital that makes partnerships function. Structured knowledge-transfer protocols, including documented relationship histories, named successor contacts, and transition briefings, preserve what experienced staff carry in their heads. This is especially important when civil service reform efforts change agency leadership and reset informal working relationships overnight.

Some structural problems resist full resolution. Political misalignment between a federal administration and a state government can freeze cooperation for years. In those cases, the practical workaround is to maintain working-level relationships below the political layer, keeping program staff connected even when leadership is at odds, so that collaboration can resume quickly when conditions change.

Building Capacity: Training, Data Sharing, and Equity in Multi-Level Partnerships

Federal agencies are increasingly confronting a stark reality: statutory partnership mandates alone do not guarantee equitable participation by tribal and territorial governments. Long-standing capacity gaps, inadequate consultation protocols, and asymmetric access to data continue to undermine collaboration, even as agencies adopt new equity action plans and listening session models. The 2026 ACUS tribal listening session in Reno, Nevada, documented these challenges firsthand, revealing persistent barriers that public administration careers and degrees must address through systemic capacity-building, not just procedural compliance.

Documented Barriers to Tribal and Territorial Participation

Federal-tribal and federal-territorial partnerships face distinct structural obstacles. GAO reports and tribal advocacy organizations consistently cite insufficient funding, short consultation windows, and fragmented communication as core problems. The National Congress of American Indians (NCAI) has identified funding interruptions during federal shutdowns as particularly destabilizing: Indian Housing Block Grants, Section 184 home loan guarantees, HUD-VASH assistance, and community development block grants all halt during lapses, leaving tribal governments without critical revenue streams.¹ A 2026 NCAI webinar titled "Understanding Federal Government Shutdown Impacts on Tribal Governments" underscored these dependencies, noting that tribal administrators often lack the discretionary reserves to weather prolonged closures.¹ Territorial governments face parallel challenges, compounded by geographic isolation and limited representation in federal decision-making forums.

Data-sharing agreements remain another friction point. Tribal governments frequently lack real-time access to federal datasets on employment, health, and infrastructure, even when those data inform funding allocations. Without co-located data systems or shared dashboards, tribal administrators operate with incomplete information, making it difficult to align local priorities with federal timelines.

Successful Equity Mechanisms in Practice

Several federal agencies have pioneered inclusion practices that practitioners can adapt. The Environmental Protection Agency established its Indian Policy in 1984, recognizing tribes as sovereign partners in environmental regulation. More recently, the National Tribal Water Council released its 2026-2028 Tribal Water Priorities Document, developed through iterative consultation with the Institute for Tribal Environmental Professionals.² This model, centered on multi-year planning cycles and transparent priority-setting, offers a blueprint for sustained partnership.

The U.S. Department of the Treasury has institutionalized tribal consultation protocols that extend beyond notice-and-comment rulemaking. Treasury's tribal consultation page details standing mechanisms for tribal input on tax policy, including implementation of the Tribal General Welfare Exclusion Act, for which regulations were finalized in 2026.³ These protocols include pre-draft engagement, technical assistance webinars, and follow-up briefings after regulatory changes, steps that reduce information asymmetry and build trust over time.

The Bureau of Indian Affairs hosted the 2026 Tribal Self-Governance Conference, convening tribal leaders and federal officials to discuss contract support cost management and program design.⁴ Events like these, coupled with ongoing technical assistance through NAFOA's Tribal Tax and Accounting Conference (held in 2026 with a public listening session in Reno),⁵ create forums for peer learning and relationship-building outside the transactional rhythms of grant cycles.

Training and Data-Sharing Frameworks

Capacity-building requires dedicated investment in workforce development and interoperable data systems. The Department of Education announced the State Tribal Education Partnerships Program competition in 2026, funding cross-jurisdictional teams to improve educational outcomes for Native students.⁶ Programs like these combine financial support with technical assistance, helping state and tribal administrators navigate overlapping authorities and share performance data in real time.

Professional associations such as NCAI and the Native Governance Center have published guidance on tribal economic development policy priorities in 2026, offering case studies that illustrate successful partnership models.⁷ Public administrators preparing for federal-tribal collaboration should engage these resources early, understanding that equity in multi-level partnerships depends on sustained relationship-building, not one-time compliance exercises.

What ACUS Recommendation 2026-4 Means for Future Public Administrators

ACUS Recommendation 2026-4 is the federal government's most explicit directive yet to institutionalize intergovernmental partnerships, moving them from behind-the-scenes practices into formal, accountable systems.

What the Recommendation Requires

Adopted January 21, 2026, ACUS Recommendation 2026-4 calls on agencies to treat partnerships as core administrative functions. It asks each agency to formally assess its intergovernmental landscape, develop written partnership agreements, establish regular communication channels, integrate intergovernmental coordination into strategic planning, and create accountability mechanisms that include joint performance metrics. Staff training on intergovernmental collaboration should become standard practice. The directive stems from an exhaustive ACUS-commissioned study that found about 60 percent of U.S. Code provisions involve federal-state partnerships, yet many agencies rely on informal, unexamined methods to manage these relationships.

Competencies for Tomorrow's Public Leaders

For MPA and MPP students and early-career practitioners, the recommendation translates directly into a skill stack. Mastering intergovernmental negotiation, cross-jurisdictional performance measurement, stakeholder mapping, and collaborative program design will become essential. The field is moving away from administrators who simply follow legal mandates and toward those who actively build trust, document tacit knowledge, and construct governance frameworks that span federalism's layers. Graduates who can facilitate structured dialogue between federal agencies and SLTTGs will find their expertise in high demand, particularly as equity and data-sharing expectations intensify across programs. A strong grounding in public administration careers and degrees provides the foundation for developing these intergovernmental competencies.

Why This Is a Career Signal

ACUS recommendations frequently influence agency practice even without congressional action. The Office of Management and Budget, departmental general counsels, and inspector general reviews often cite them as benchmarks. Agencies that adopt Recommendation 2026-4's framework early will set the standard for what robust intergovernmental collaboration looks like, and their employees will gain a reputation for cutting-edge administrative practice. For those in government program management roles, positioning oneself as an early adopter of partnership systematization signals foresight and operational sophistication , qualities that accelerate career advancement.

Next Steps

Public administrators can act on the recommendation immediately:

• Study the source: Access ACUS Recommendation 2026-4 and the full Clouser McCann and Selin report on the ACUS website to understand the evidence base and detailed guidance.
• Audit your agency's practices: Use the recommendation's checklist to evaluate how your organization currently manages intergovernmental partnerships, identifying gaps in documentation, communication frequency, and accountability.
• Pilot a new approach: Choose one existing partnership and implement a written agreement or a joint performance metric dashboard. Document the process and results to build a case for broader adoption.

Frequently Asked Questions About Federal-State Partnerships

Federal-state partnerships shape nearly every area of domestic policy, yet practitioners often have foundational questions about how these relationships work in practice. The answers below address the most common questions and point to deeper discussion throughout this guide.

Related Articles