# Sponsor Promises

> Track everything a signed event sponsor was promised, from the countersigned agreement to the post-event report,
> then write the team's status memo or the next message to one sponsor. Enter the event dates, the tiers, each signed
> sponsor with payment status and liaison, every perk their agreement promised, the hard print deadlines and the
> published caps. Built on the SkillSafe skill @samber/event-sponsor-fulfillment (samber/dev-event-organizer-skills, MIT).

https://sponsor-promises.skillsafe.ai/

## What is free
- One column per sponsor, every perk with its state (promised, scheduled, delivered, evidenced, partial, missed), due date, owner, evidence and make-good; late, unowned, unproven and missed-without-make-good cells flagged; perks taken from the prospectus instead of the signed agreement flagged.
- A chase list by owner: every open perk grouped under the person who owns it (late, missed without a make-good, delivered without proof, held for payment), ready to copy into the team channel.
- The payment gate: every perk of a sponsor whose fees are open is held, and any that shipped anyway is a breach.
- The fulfillment clock from the earliest hard deadline (the printer's date, not the event's); printed surfaces past their print run; unpaid sponsors with a print run inside two weeks.
- Published caps on exclusive surfaces, with oversold surfaces flagged.
- Lead capture: aggregate demographics by default, a consented raffle where sold, bulk attendee lists and badge scanning deleted at a community-run event.
- Per sponsor: the onboarding instrument (checklist email, intake form, kickoff call) and the report depth (recap only, short form, full metrics report, shortened by an early budget lock).
- The two-stage report clock: a recap inside 72 hours and the stage-2 report inside 10 business days, with late reports flagged.
- Matrix CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (status or sponsor), `event`, `matrix` and `facts`.
- `status` replies with `summary`, `clock`, `payment`, `sponsors`, `caps`, `leads`, `measurement`, `signals` and `caveats`; the page holds every payment status, hold and breach, closed and total counts, onboarding and report picks, caps, lead rungs and gates to its own.
- `sponsor` replies with `mode`, `to`, `subject`, `body`, `held`, `misses` and `note`; the page requires its mode and focus sponsor, every held perk or miss by name, misses before thanks, and no other sponsor's name, reach estimate or media value.

## Links
- API tutorial: https://sponsor-promises.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-sponsor-fulfillment