When Federal Staff Can Travel Again

Season one closes with Director of Public Policy Simone Radcliffe explaining how federal employee travel limits, tightened for several years, eased this March after a coalition letter NANA helped organize — and what that shift means for the associations whose conferences depend on federal attendees showing up.

• Simone Radcliffe — Director of Public Policy, NANA. Runs advocacy; led the coalition letter on federal conference-travel limits.

• 00:00 Intro

• 01:30 Why federal travel limits mattered to associations

• 07:00 What the restrictions actually looked like

• 12:40 Building the coalition letter

• 18:15 What eased in March, and what didn't

• 22:00 What this means for NANA's own Fall Policy Forum

• 25:15 What this means for conference attendance broadly

• 29:30 A member story: a canceled trip

• 33:00 Timing versus coalition effort

• 36:15 What Simone would do differently

• 38:15 Looking back on season one

• 40:20 Outro

Host: Simone, this is a policy story that a lot of our members felt directly without necessarily knowing why. Start with the basic problem.

Simone Radcliffe: For several years, federal agencies operated under tightened restrictions on employee travel to conferences — a legacy of budget-scrutiny rules meant to prevent the kind of lavish-conference headlines that make for bad press. The restrictions were reasonable in their original intent, but they'd calcified into something much broader: a federal employee whose actual job was, say, transit planning or building codes, needed layers of approval just to attend a professional conference in their own field, even a low-cost one with clear public-service value.

Host: Which of NANA's members felt this most directly?

Simone Radcliffe: Anyone whose conference draws federal attendees as a meaningful share of the room. The Council of Municipal Transit Planners is a good example — a lot of their members work for city and regional transit agencies, some of which receive federal funding and therefore have federal-adjacent approval requirements layered on top. When travel approval gets harder, attendance drops, and that's not just a headcount problem — it's the peer-learning and cross-agency coordination that conference exists for, not happening.

Host: How did NANA get involved in something that's really about federal personnel policy, not association membership directly?

Simone Radcliffe: Because it was showing up across our member base as the same complaint from different sectors — building officials, transit planners, water utility engineers, all telling us the same thing, that a genuinely useful professional-development trip was getting blocked by a rule built for a different problem. When we hear the same complaint from enough different corners, that's usually a sign it's bigger than any one association can fix alone, which is when a coalition makes sense.

Host: Tell me about the coalition letter itself. Who signed it, and what did it actually ask for?

Simone Radcliffe: We organized it with several of our member associations whose sectors intersect with federal agencies, and the ask was narrow and specific — not "eliminate the rule," but "distinguish between a lavish, discretionary trip and a low-cost professional conference tied directly to the employee's actual job function." Narrow asks travel better in this environment than broad ones. Nobody in government wants to be seen rolling back travel oversight generally. Distinguishing a $400 registration fee at a sector conference from what the original rule was actually written to stop is a much easier ask to say yes to.

Host: And that worked. What actually eased in March?

Simone Radcliffe: The relevant guidance now allows a streamlined approval path for conference travel under a defined cost threshold, tied to an employee's professional field, without it needing to climb as many approval layers as before. It's not a full repeal of the oversight regime, and I want to be careful not to overstate it — it's a carve-out for exactly the category of travel our members were describing.

Host: Is there a risk this gets reversed, the way these policy changes sometimes do?

Simone Radcliffe: There's always some risk with guidance rather than statute — a future administration or a future budget fight could tighten it back up. What I'd say is that a narrow, well-documented carve-out with a clear public-service rationale tends to survive longer than a broad loosening would have, because it's harder to point to it as an example of waste. We'll keep watching it, the same way we watch every other file, and if it starts to slip we'll go back to the same coalition rather than starting over from nothing.

Host: Does this change anything about how NANA itself plans events with a federal attendee base, like the Fall Policy Forum?

Simone Radcliffe: A little, yes. We'll likely see fewer last-minute cancellations from federal attendees who'd already registered for the Fall Policy Forum, which historically draws government relations staff working alongside federal counterparts. It won't change how we plan the event itself, but it should mean the registration numbers we see closer to the date hold up better than they have in recent years, when late travel denials were a real source of no-shows.

Host: What does this actually mean for a conference happening later this year?

Simone Radcliffe: For an association whose attendee mix includes a meaningful share of federal employees, I'd expect a modest uptick in approved travel starting with events later this spring, since the guidance took effect in March and agencies need a beat to actually apply it. It won't be dramatic — this was never the only reason attendance dipped — but it removes one specific obstacle that members had been telling us about consistently.

Host: Was there a specific member story that made this fight feel real to you personally, versus an abstract policy problem?

Simone Radcliffe: Ravi Deshpande-Cole, who does technology work for the Council of Municipal Transit Planners, told me about a colleague at a city transit agency who had a conference registration approved, a hotel booked, and then had the trip cancelled at the last minute over a travel-approval review that had nothing to do with the conference's cost or relevance — just paperwork timing. That employee lost the chance to present research they'd been working on for a year. Stories like that are what actually move a coalition letter from a policy talking point to something with a face attached to it.

Host: How much of this success do you attribute to the coalition itself, versus just good timing on the policy calendar?

Simone Radcliffe: I'd give real credit to timing, and I don't think that's false modesty. Budget-scrutiny pressure that originally produced the restrictive rules had eased somewhat by the time we sent the letter, which made a distinguishing carve-out an easier ask than it would have been two years earlier. A good coalition letter still has to land at a moment when the door is even slightly open — the same letter sent at the peak of the original scrutiny probably goes nowhere no matter how well it's argued.

Host: This is also the last episode of season one. Any reflection on the run, looking back?

Simone Radcliffe: Just that the range of topics — this is governance, finance, membership, digital, now travel policy — says something true about what running an association actually involves day to day. It's not one skill. It's a dozen different competencies that happen to sit under one executive director's title, and I think the season made that visible in a way a single conference session never quite does. I also think it's a good sign for the sector that all of these problems have people actively working them, rather than sitting unaddressed — that's not something a listener necessarily sees from outside any one association.

Host: If you had to name one thing you'd do differently, knowing what you know now, on this specific campaign?

Simone Radcliffe: I'd have brought in member stories like Ravi's example earlier in the process rather than mostly at the end. We spent the first stretch of this building the letter around the general policy argument, and only added specific member experiences closer to when we sent it. In hindsight, leading with the concrete story and backing it with the policy argument, rather than the reverse, probably would have moved faster, because a specific canceled trip is a more persuasive opening than an abstract description of an approval bottleneck.

Host: Simone, thanks for closing out the season with us.

Simone Radcliffe: Thanks for having me. See everyone back for season two — and for anyone at an association still fighting a similar travel-approval fight, reach out. We're happy to share what worked.