---
name: sponsor-fulfillment-report
description: Writes post-event sponsor fulfillment and ROI reports for each sponsor of an owned conference, summit or event series. Builds a promised vs delivered table with proof, separates event-wide from sponsor-specific metrics, summarizes leads and session engagement, adds attendee feedback mentions, notes misses honestly and drafts a renewal recommendation and email. Use for sponsor recaps, sponsor ROI reports, fulfillment reports, sponsor lead summaries or sponsor renewals.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: sponsorship
  source: https://eventmarketingsoftware.com/skills/sponsor-fulfillment-report
---

# Sponsor Fulfillment Report

Turns a sponsor deliverables sheet, lead exports and event metrics into one report per sponsor that proves what was delivered, shows what it produced, and sets up the renewal conversation. Sponsors renew on proof. A raw scan file doesn't help a sponsor justify spend to their CMO; a clear report does.

## Intake

If the user has an `event-context.md` file, read it first and don't ask for anything it already answers.

Ask for whatever is missing in ONE message:

1. Event name, dates, format (in-person, hybrid, virtual) and total registered vs attended.
2. The sponsor deliverables list: sponsor, tier, each promised item and quantity (from contracts or the prospectus).
3. What was delivered, with proof where it exists (photo file names, session recording links, email send stats, app impressions).
4. Lead or engagement exports per sponsor (badge scans, session attendees, meeting bookings, booth visits, content downloads).
5. Any attendee survey results that mention sponsors, and the sponsor survey if one ran.
6. Report audience and tone: the sponsor's event lead, or something they can forward to their CMO.
7. Renewal context: next year's dates, whether pricing changes, any early-renewal offer.

Work with partial data. Mark anything missing as "Not provided" instead of guessing.

## Data sources (connectors optional)

- If a Google Sheets connector is available, read the deliverables sheet and exports from it and offer to write the fulfillment table back to a new tab.
- If a Slack connector is available, you may draft an internal summary for the sponsorship channel.
- Otherwise, work from pasted tables, uploaded CSV or XLSX files, or plain text, and return Markdown plus a downloadable CSV of the fulfillment table.
- Never require a paid service. Never fetch URLs.

Sample inputs: [assets/sample-deliverables.csv](assets/sample-deliverables.csv) and [assets/sample-sponsor-leads.csv](assets/sample-sponsor-leads.csv).

## Method

1. **Normalize the deliverables.** One row per sponsor per promised item. Standardize item names (e.g. "logo on lanyard", "Lanyard logo" become "Lanyard branding"). Keep the contract wording in a notes column if it differs.
2. **Match delivery to promise.** For each row set status:
   - `Delivered` (met or exceeded, proof exists)
   - `Delivered, no proof` (team says yes, nothing to show; ask for proof before sending)
   - `Partial` (delivered less than promised, e.g. 2 of 3 social posts)
   - `Missed` (not delivered)
   - `Make-good` (missed but replaced with something agreed)
   Never mark `Delivered` without a quantity or proof reference.
3. **Split metrics into two groups.** Event-wide metrics (total attendees, sessions, app users, total email reach) are context. Sponsor-specific metrics (their scans, their session attendance, their meetings, clicks on their links, their logo impressions if tracked) are the proof. Never present an event-wide number as if the sponsor earned it.
4. **Summarize leads.** From the sponsor's lead export: total unique leads (dedupe on email, then name plus company), split by source (booth scan, session scan, meeting, content download), top companies, seniority mix (C-level, VP, Director, Manager, Individual contributor, Unknown) and job function, and how many match the sponsor's stated target if they gave one. Don't score or tier leads for the sponsor unless they asked; that's their job. Exclude your own staff and other sponsors' staff and say how many you removed.
5. **Pull feedback mentions.** Quote short attendee comments that mention the sponsor, their session or their activation (max 3, anonymized). Include sponsor survey scores if available.
6. **Be honest about misses.** List every `Partial` or `Missed` item with a one-line cause and the make-good offered or proposed. A report that hides a miss loses the renewal when the sponsor notices.
7. **Recommend the renewal.** Based on what performed: keep, upgrade, swap items, or downgrade. Tie each recommendation to a number in the report. Suggest one specific package and why. Don't invent next year's prices; use the user's prices or leave a placeholder.
8. **Draft the renewal email** (draft only) that links the report, names the two strongest results, acknowledges any miss, and proposes a call.

Domain rules that matter:
- Lead counts are unique people, not raw scans. Report raw scans separately if the sponsor cares about traffic.
- Session attendance for a sponsored session should be checked-in attendees, not registrations. Say which one you have.
- Don't share attendee personal data with a sponsor unless the attendee consented to sharing (typically a checkbox at registration or the act of scanning a badge at their booth, depending on your privacy notice). If consent status is missing, give aggregates only and flag it.
- Pipeline and revenue belong to the sponsor's CRM. You can report leads and meetings; you can't claim sourced or influenced pipeline for them. Offer a follow-up field: "Ask the sponsor for 90-day pipeline from these leads."

## Output templates

Full headings and a worked example: [references/report-template.md](references/report-template.md).

Per sponsor report headings:
1. Summary (3 bullets: biggest result, delivery rate, renewal suggestion)
2. Deliverables: promised vs delivered
3. Your results (sponsor-specific metrics)
4. Event context (event-wide metrics, labeled as such)
5. Lead summary
6. What attendees said
7. What we missed and how we made it right
8. Recommendation for next year

Deliverables table columns:

| Deliverable | Promised | Delivered | Status | Proof | Notes |
|---|---|---|---|---|---|

Lead summary table columns:

| Source | Raw scans | Unique leads | Director and above | Matches your target | Top companies |
|---|---|---|---|---|---|

Portfolio view (when there are several sponsors):

| Sponsor | Tier | Items promised | Delivered | Partial | Missed | Unique leads | Renewal suggestion | Proof gaps |
|---|---|---|---|---|---|---|---|---|

## Validation checklist

Copy and run before you hand over the reports:

- [ ] Every promised item from the input appears in exactly one row; count of items in equals items out.
- [ ] No `Delivered` status without a quantity or proof reference.
- [ ] Event-wide and sponsor-specific metrics are in separate sections.
- [ ] Lead counts are unique people; staff and other sponsors removed, with counts stated.
- [ ] Every miss has a cause and a make-good line.
- [ ] No personal data in the report unless consent to share is confirmed.
- [ ] Renewal suggestion cites at least one number from the report.
- [ ] House style: plain words, no hype, no superlatives you can't prove.

## Approval gates

- Show each report and the renewal email as drafts. Never send email, post to Slack or write to a sheet or CRM without showing a preview and getting a clear yes.
- If any row is `Delivered, no proof`, list those rows first and ask the user to confirm or supply proof before finalizing.

## Privacy

- Keep lead files inside the user's own tools. Give sponsors only the fields your privacy notice allows.
- Flag EU and UK attendees in lead files. Under GDPR and the UK GDPR, sharing them with a sponsor needs a lawful basis your notice covers. If unsure, share aggregates and let the sponsor follow up through the opt-in route.
- Anonymize survey quotes.
