How to Review Membership Benefits With a Small Team

To review membership benefits with a small team, list what you promise, check how members access each benefit, combine usage information with member feedback, and choose one manageable improvement. Give every action an owner and a review date. Start with a small selection of benefits so you can complete the review and act on what you learn.

You do not need to redesign your entire membership program. You need a clearer picture of which promises are being delivered, where members encounter difficulty and what your team can realistically improve.

What is a membership benefits review?

A membership benefits review checks whether the value you promise is available, useful and sustainable to deliver.

It brings together four questions:

• Can eligible members find and use the benefit?
• What evidence shows whether members value it?
• What does it take to deliver and support it?
• What should the team keep, improve, test or consider retiring?

The outcome should be a small set of decisions with clear reasons. A longer list of possible perks can come later.

If your organization needs new ideas, our membership perks guide covers that question. This guide focuses on assessing the benefits you already offer.

Start with a review your team can finish

Choose three to five benefits for your first review. That is a suggested working limit, not an industry benchmark.

Pick a mix: one core reason people join, one benefit members often ask about, and one that takes noticeable staff or volunteer time.

Choose a review period that fits each benefit. A monthly online session and an annual conference need different windows. Record the dates so another person can understand the comparison.

With two people, divide the work:

• Review coordinator: gathers the promises, records and feedback.
• Delivery owner: checks access, partner arrangements and the work involved.

If one person has both roles, ask a committee colleague to sense-check the proposed actions. Schedule one decision meeting once the information is ready.

Step 1: Write down the promises members actually see

Collect your membership page, joining emails, renewal messages and any welcome materials. Look for differences between the benefits described in each place.

A benefit may have changed without every page being updated. A partner discount might still appear in a renewal email after the arrangement has ended.

For each benefit, record:

• The promise in plain language.
• Who is eligible and any limits.
• Where the member finds it.
• Who delivers it.
• What the member must do to use it.

Be specific. “Access to learning” is difficult to assess. “Members can attend one online workshop each month at no additional charge” gives your team something to check.

Also record benefits that support the organization's wider purpose, such as representation or advocacy. Their value may not be reflected in individual redemptions or attendance.

Step 2: Try accessing the benefit as a member

Walk through the process using an appropriate test account or a colleague's supervised test. Start from the same email or webpage that a member would see.

Check the journey on a phone:

1. Can you find the benefit without knowing where it is hidden?
2. Is the eligibility clear?
3. Does the link, code or booking process work?
4. Does the member understand what happens next?
5. Is help available if something goes wrong?

Record the point of difficulty. “Members do not use the workshop benefit” is a broad observation. “The booking link in the welcome email points to last year's calendar” is a problem your team can fix.

For partner benefits, ask the partner to confirm the current offer, redemption process and contact person. Record when that confirmation was received.

Step 3: Gather enough evidence to make a decision

Use the records you already have before commissioning a large survey. Depending on the benefit, those could include registrations, attendance, redemptions, support requests or a partner's aggregate report.

Distinguish each stage of use. Opening an email is different from clicking through, registering or attending.

Where reliable data is available, calculate:

Benefit usage rate = unique eligible members who used the benefit ÷ eligible members in the review group × 100.

Use the same defined group and time period in both parts of the calculation. If you cannot identify the number of eligible members reliably, report the count and the limitation instead.

For example, suppose an illustrative workshop was available to a defined group of 120 members and 18 of those members attended. The usage rate for that group and workshop is 15%. That figure does not show whether the workshop was valuable, whether the timing suited everyone or whether non-attendees still value having access.

For small groups, show the actual count alongside the percentage. A change from two people to four may deserve attention, but it needs context.

Separate low use from low value

A benefit may have limited use because members cannot find it, because it serves a specialist need or because it is only relevant at particular times.

Representation, emergency support or access to expertise may matter even when individual members rarely use them. Look at the purpose of the benefit before judging it solely by activity.

Equally, high usage is not the whole decision. A popular benefit might create a workload your team cannot sustain. Record both the value to members and the delivery requirement.

Step 4: Ask members a few focused questions

A short feedback exercise can help explain the records. Invite responses from people who have used the benefit and people who have not.

For each selected benefit, adapt these questions:

1. Before today, did you know this benefit was included in your membership?
2. Have you used it during the stated review period?
3. If you used it, how useful was it to you?
4. If you wanted to use it but did not, what got in the way?
5. What one change would make it more useful or easier to access?

Use a clear period, such as “between April and September,” rather than “recently.” Provide options such as “not aware of this benefit,” “not needed” and “not applicable” where they make sense.

Pew Research Center's guidance on survey questions recommends asking about one concept at a time and using clear language. Ask about usefulness and ease of access separately, because a member may have different answers to each.

Our membership survey questions can help you adapt the wording for your organization.

Read responses in context

Record how many people were invited and how many replied. Look for differences between newer members, long-standing members and the people who actively use the benefit.

A handful of responses can identify a problem worth checking. They do not establish what every member thinks. If a significant group is missing, follow up before making a decision that affects them.

Summarize the themes without attaching unnecessary personal information. Keep individual comments accessible only to the people who need them for the review.

Step 5: Use a simple benefits review worksheet

Use one row per benefit. Link each row to the supporting records so the next committee can understand why a decision was made.

These rows are examples to adapt, rather than findings about your organization.

Alongside the table, record cash costs, estimated staff or volunteer time, the action owner and the review date. Keep measured costs separate from estimates.

Avoid combining everything into a single score unless your team agrees what the score means. A simple traffic-light label can hide the reason a benefit matters to a small but important group.

Step 6: Choose one action your team can deliver

Use four practical decisions:

• Keep: the benefit has a clear purpose and the delivery process is working.
• Improve: the benefit appears useful, but access, communication or delivery needs attention.
• Test: the evidence is incomplete, so try a limited change and decide what to measure.
• Consider retiring: the benefit no longer appears to meet a need or cannot be delivered sustainably, subject to further checks.

Before changing an existing promise, check what members were told, which members would be affected, and whether there are partner arrangements or internal approvals to resolve. Explain the decision before the change takes effect.

Example: a useful benefit with a broken access process

Imagine a small professional association offers a monthly online workshop. Attendance is low, but several respondents say they would attend if they could find the booking details.

The team checks the journey and discovers an outdated welcome-email link. Instead of immediately replacing the workshop, it updates the link and adds a clear booking instruction to the member information page.

The coordinator records the next workshop's registrations, attendance and access questions. The team reviews those alongside feedback after the next two sessions.

This is an illustrative example. Its purpose is to show how a review can lead to a specific, testable action without assuming the benefit itself is wrong.

Step 7: Tell members what changed and check the result

Close the loop with a brief update:

“We heard that workshop booking was difficult to find. The booking link is now in your welcome email and member information page. Please tell us if you still have trouble accessing it.”

Name the change and the route to help. Avoid announcing a broad improvement in value before you have evidence.

Set a follow-up date that fits the benefit's delivery cycle. Compare the same measures and note other changes that could affect the result, such as timing, seasonality or a different event topic.

Do not assume that a change in renewals was caused by one benefits adjustment. Use renewal information alongside participation and feedback to understand what may be happening.

Where membership software can support the review

A shared member database can help your team identify eligible members, keep membership types and status organized, and export information for analysis.

Join It's Eventbrite-related member benefits workflow can connect member discounts, event orders and check-ins with member records. That can be useful when event participation forms part of the review.

The review worksheet still has a separate job. Your team needs to assess purpose, interpret feedback, estimate delivery effort and decide what to change. A payment record does not tell you whether a member values a particular benefit.

Frequently asked questions

How often should we review membership benefits?

Choose a rhythm that fits your program. A broader review before annual planning, with smaller checks after a change or delivery problem, is a practical starting point. Match the review window to when members can actually use the benefit.

What if we have very little usage data?

Begin with an access check and focused feedback. Record the gaps, then choose a simple measure for the next delivery cycle. Do not treat missing records as proof that nobody used or valued the benefit.

Should we remove a benefit that few members use?

Investigate why usage is low and who values it. A specialist benefit may serve a legitimate purpose for a small group. Consider access, awareness, timing, workload and member promises before deciding.

Can one volunteer run the review?

Yes. Limit the first review to a few benefits, use existing records and ask another committee member to review the proposed actions. The most useful output is a decision someone can carry out and assess.

Make the next improvement clear

Start with three benefits, one worksheet and one decision meeting. Finish with a named owner, a specific change and a date to check the result.

If scattered records make it difficult to establish who is eligible or when memberships renew, explore Join It in a trial. Use the review to identify the membership information your team needs to keep organized.