Skip to main content

Fulfill Sponsorship Benefits

Goal: Deliver every benefit promised to every sponsor — logos placed, signage produced, recognition given, tickets honored — and track that fulfillment so you don't lose a renewal because something fell through.

Why fulfillment matters​

The fastest way to lose a sponsor next year is to fail to deliver what you promised this year. Sponsors notice — and remember — when their logo wasn't where it was supposed to be, when the recognition mention happened to someone else, when the program ad never ran.

Tracking fulfillment turns "we'll get to it" into a queue with statuses, owners, and deadlines.

How fulfillment is structured​

When a sponsor signs up at a package level, Ayuna creates a benefit fulfillment record for each benefit in that package. Each fulfillment carries:

  • The benefit name (e.g., "Logo on event signage")
  • The associated sponsor and event
  • A status: Pending, In Progress, Completed, or Waived
  • An optional assignee (the staff member responsible)
  • An optional deadline

These records live in the sponsorship dashboard under the Pending Benefits tab — your team's working queue.

The queue​

The Pending Benefits tab is the home for fulfillment work. From here you can:

  • See every outstanding benefit across all sponsors
  • Filter by event, sponsor, deadline, or status
  • Assign benefits to specific staff members
  • Mark a benefit in progress as the work begins
  • Mark a benefit complete when done
  • Waive a benefit if the sponsor declined it

Treat this like a project board — review weekly, make sure no benefit goes uncompleted.

Status transitions​

  • Pending — committed, no work started yet
  • In Progress — work has started (logo file received, signage ordered, ad copy written)
  • Completed — fully delivered (signage installed, ad ran, recognition mentioned)
  • Waived — sponsor declined the benefit (e.g., chose not to use logo placement)

The transitions are explicit moves; the audit log captures who moved which benefit when.

Assigning ownership​

For events with many benefits across many sponsors, assign each fulfillment to a staff member. The dashboard's My Tasks view (filtered by assignee) becomes their personal queue.

When the assigned person leaves the affiliate, reassign their open benefits — don't let them silently drift unowned.

Bulk completion​

For events where many sponsors share a benefit (e.g., "Logo on event signage"), once you've installed the actual signage, you can bulk-complete that benefit for every sponsor at once.

Benefits with deadlines​

Some benefits are time-sensitive:

  • "Logo on event program" — must be done by print deadline (usually 2–3 weeks before event)
  • "Ad in event program" — same deadline
  • "Recognition from podium" — must happen at the event itself
  • "Logo on website event page" — must be live by event launch

Set deadlines on these and use the queue's deadline filter to surface what's urgent.

Post-event reporting​

After the event, run a fulfillment report by sponsor. For each:

  • What was promised
  • What was delivered
  • Anything outstanding (rare, but happens — a delayed website update, a thank-you that hasn't gone out)

Share this with each sponsor as part of stewardship — a brief "here's everything we delivered, thank you" note. It reinforces the value of the sponsorship and makes the renewal conversation natural.

Sponsors see benefit status on their public dashboard. They know what's pending, in progress, and complete. This transparency is part of the trust model — they don't have to email asking "is my logo up yet?"

When something can't be delivered​

If a benefit can't be delivered as promised:

  • Communicate proactively (don't wait for the sponsor to ask)
  • Offer a substitute of equal or greater value
  • Document the substitution and the sponsor's acceptance
  • Mark the original waived and create a record of the substitute