Resource groups often do significant work that leadership never fully sees because it gets reported in a way that doesn’t connect. A list of events and attendance numbers tells leadership what happened. It rarely tells them why it mattered or what they should do about it.

Presenting impact effectively is a different skill from running a good group. Here’s how to do it.

Lead with Outcomes, Not Activity

The most common mistake in impact reporting is leading with what the group did rather than what it produced.

“We hosted six events with 240 total attendees” is activity. “240 employees participated in programming that generated measurable improvements in peer connection and cross-functional relationships, based on post-event feedback” is closer to impact.

The distinction matters because leadership isn’t evaluating how busy your group was. They’re evaluating whether the investment in volunteer time, organizational resources, and leadership attention is producing something worth sustaining.

Before you report anything, ask: what changed because this group exists? What did members gain that they wouldn’t have had otherwise? That’s what you’re trying to communicate.

Connect Explicitly to Organizational Priorities

Resource groups that frame their work in terms of organizational goals get more support than ones that report in isolation. A group that demonstrably contributes to employee engagement, retention, leadership development, or cross-functional collaboration is contributing to things the organization is already trying to solve.

Look at what your organization has publicly committed to (engagement survey priorities, retention goals, development initiatives, etc.) and draw the explicit lines between your group’s work and those priorities. Don’t make leadership do the connecting themselves. They won’t.

Build Your Case with Both Data and Stories

Data shows scale. Stories show meaning. You need both.

On the data side, track what you can consistently: membership growth, event attendance, volunteer hours, newsletter open rates, survey response rates. You don’t need sophisticated measurement — you need enough to show trajectory and reach over time.

On the story side, collect specific examples: a member who found a mentor through the group and recently got promoted, a cross-functional relationship that formed at a networking event and led to a collaboration, a first-generation professional who said a career panel changed how they thought about their trajectory. One specific story told well does more for an impact report than a page of statistics.

The combination – here’s our reach and here’s what it actually meant to someone – is what makes a report memorable rather than just informative.

Keep It Short and Structured

Leadership teams are time-constrained and reading a lot. A two-page summary with clear sections will get more attention than a ten-page report that requires excavation.

A strong impact report covers five things:

1. What the group accomplished this period
2. What the numbers show
3. What members are saying
4. How this connects to organizational priorities
5. What support or resources would help the group do more

That’s it. If something doesn’t fit one of those categories, cut it.

Lead with the most important finding, not with background context. Assume the reader knows what the group is, don’t use the first page to re-explain your mission.

Be Honest About Challenges

Groups that only report successes gradually lose credibility with leadership. Everyone knows nothing goes perfectly, and a report that reads like a highlights reel signals that the group isn’t being straight with you.

Naming challenges directly – “member retention between events has been harder than we expected, and here’s what we’re doing about it” – builds trust and often opens conversations about support the group actually needs. It also positions you as a thoughtful leader rather than someone managing optics.

Use the Report to Make Specific Asks

Impact reporting isn’t just retrospective. It’s one of your best opportunities to ask for what you need going forward.

Be specific. “We’d like additional budget for one external speaker per quarter” is an ask leadership can evaluate. “Continued support would be appreciated” is not. Connect the ask to the impact you’ve just demonstrated – “our speaker series has been our highest-attended programming, and expanding it would let us reach more of the organization” – and make it easy to say yes.

The groups that consistently get what they need from leadership are the ones that consistently show their work and ask clearly. Neither alone is enough.