Attendance is an output. What people can do afterward is the test.

Use this system for a community gathering, alumni program, volunteer event, or mission-focused convening. Start before the event when possible. If it has already happened, reconstruct only the commitments you can verify. The goal is not a longer contact list or more messages; it is useful follow-through that people have actually agreed to.

01

Define the change the gathering should make possible

Write one outcome for the people the event serves. 'Host a successful panel' describes delivery. 'Help interested participants complete a first, supported volunteer contribution' describes a change to work toward. Ask community members whether that outcome matters to them before optimizing for donor or organizer preferences.

Separate inputs, outputs, and outcomes. Staff hours and budget are inputs; attendance and recordings are outputs; a completed contribution or a useful new relationship may be an early outcome. A 90-day signal is not proof of long-term impact or proof that the event caused it.

02

Design the next step before asking for enthusiasm

Offer a specific, bounded contribution: a two-hour project, an introduction with permission, a small working group, or a feedback conversation. State the time, support, owner, and completion condition. Interest is not commitment. A commitment exists when the person accepts the next step and the receiving owner has capacity.

Keep the operational contact list in the organization's approved system. The downloadable tracker is for non-sensitive role labels and status. Do not reproduce donor histories, beneficiary stories, or personal contact details in a shared working copy.

03

Day 7: close the immediate promises

  • Reconcile promises made by speakers, organizers, staff, and attendees. Give each promise one accountable owner and a due date.
  • Thank people with a specific acknowledgment. Send the materials or introduction promised, not a generic sequence of solicitations.
  • Ask permission before introductions, adding people to ongoing communications, or reusing recordings and quotations.
  • Offer one relevant next step. Make declining or changing capacity easy.
  • Confirm who will receive new volunteers and what happens if the original coordinator is unavailable.

04

Day 30: test contribution, not message volume

Review accepted commitments, completed first actions, unresolved handoffs, and reasons people did not proceed. Keep 'no response', 'declined', 'not a fit', and 'blocked by our process' separate. The last category is an operating problem, not a motivation problem.

Ask a small, appropriate sample what was useful and what cost them unnecessary time. Compare the experience of first-time participants with established insiders. If contribution requires knowing the right person, the pathway may be rewarding access rather than willingness to help.

05

Day 90: decide what deserves to continue

Review what persisted without constant prompting: useful relationships, completed service, volunteer retention, repeat participation, or work adopted by the organization. Record staff and volunteer effort as well as benefits. Retire a follow-up ritual that consumes capacity without advancing the mission.

Reuse only content whose permissions and context support reuse. A recording may become an annotated resource or a short recap, but private discussion and community stories are not automatically public assets. Give contributors appropriate credit and preserve the nuance of what they said.

06

Illustrative example: the alumni panel

A hypothetical alumni panel attracts 80 attendees. Twenty ask about mentoring, twelve explicitly accept a short orientation, and eight complete a first matched conversation. The useful question is not whether 80 people were converted. It is where interested people met friction, whether matches helped participants, and whether staff could sustain the support.

The next experiment offers a clear role description and a named matching coordinator before orientation. The day-30 review examines completed first conversations and participant feedback, not just reminder emails. At day 90 the organization can continue, revise, or stop the format based on mission value and capacity.

07

What not to do

  • Do not treat every attendee as a donor prospect or volunteer lead.
  • Do not confuse a pledge with received support, or a sign-up with completed service.
  • Do not count the same person repeatedly without explaining what the count measures.
  • Do not assign more work to a reliable volunteer merely because they keep saying yes.
  • Do not claim durable impact from a satisfaction score or a well-attended room.

Put it to work

7/30/90-Day Follow-Through Tracker

Choose one event and one desired outcome. Assign a follow-through owner, schedule the three reviews, and record the first five accepted commitments.

Download the fillable PDF

Three working pages. Type into the fields and save a personal copy, or print and write by hand. A PDF reader may work better than an embedded browser viewer. Do not enter sensitive information.

The 7/30/90-day checkpoints are a suggested operating cadence, not an evidence-based universal timetable. Adapt to the mission, capacity, and participant preferences.

Continue with a related resource

Browse resources for nonprofits & communities →

The distinction between measurement and useful management draws on performance-based management work by Patria de Lancer Julnes and colleagues. The service and capacity lens is informed by SEO's 2025 Leadership Voices discussion on board service. The tracker is an original VMBARS tool.