Tool · Sponsor intake

Land a partner in the sponsor pipeline.

Pick the tier (national, regional, or local), name the partner brand, drop the contact email, and capture the region or geo match string staff needs to flip status and bake the credit line into post templates.

Internal intake — gated by a shared header secret rather than a login, so an upstream CRM / staff script can post straight to the same endpoint without an operator at a browser.

1 · Tier

Where in the pipeline this partner sits. Drives the credit-line format and whether staff needs to collect a region / geo match string.

Required

2 · Partner + contact

The brand that will be credited and the staff contact the partner sends contracts / payment questions to.

Required

The name baked into the credit line verbatim.

Staff only — never published.

4 · Match pledge

Optional. When this partner commits to matching donations on a rescue drive, capture it here. Leave all three blank for “no pledge” — the row lands with pledge columns NULL. Pledge fields are staff-only and never visible on the public sponsor list.

Optional
Pledge state

No pledge attached. The sponsor row will land with matchAmount, matchKind, and matchActiveUntil set to NULL. Staff can attach a pledge later (slice 2 — admin editing UI is out of scope here).

Submitting adds a Sponsor row with status pending. Staff flips it to active after contracts / payment clears, then past when the agreement ends. The exact credit line below is what slice 2/3 of the pipeline will bake into every matching platform draft.