sponsor_deal_delivery_tracking v1.0.0

name: sponsor_deal_delivery_tracking description: "Track a signed sponsor or brand deal through delivery to final payment: agreed deliverables and deadlines, draft approvals and revision rounds, live URLs, disclosure checks, measurement windows and reports, usage rights and exclusivity start and expiry dates, and invoice and payment status, all in one tracker with a weekly check that flags slipped deliverables and rights about to expire. Use when a deal is already signed and work has started, when a sponsored post is live and its usage window needs watching, when a brand is still using content after a campaign, or when payment is due. For negotiating a deal use brand-deal-negotiation, for structuring one use creator-collab-deals, for invoicing and chasing in depth use invoice-runner."

Sponsor Deal Delivery Tracking

Purpose

Run a signed deal from signature to final payment without losing a deadline, a rights window, or an invoice in an email thread. This skill starts where the negotiation ends. The signed memo is the source. One tracker holds every deliverable, approval, live link, measurement window, rights window, and payment date, and a weekly check turns that tracker into a short list of actions.

Workflow

1. Open the tracker at signature. On the day the deal is signed, create one row per deliverable in a copy of assets/tracker-template.csv. Copy every term from the signed memo: deliverables, formats, draft and live dates, revision cap, approval window, stay live date, measurement window, usage type and channels, usage start and end, exclusivity category and end, fee and payment trigger. A term that is missing from the memo is a question to raise that week, while the deal is fresh, not a blank to guess at later. Field definitions are in references/tracker-fields.md.

1. Log drafts and approvals as they happen. Fill draft_sent_date the day a draft goes out. Count revision rounds as they are used, against the cap in the memo. When a draft has waited longer than the agreed approval window, chase it in writing, name the window from the memo, and keep a record of the chase in the weekly check. Work past the revision cap is a priced extra agreed in writing before it starts.

1. Record the live post from the post itself. When a deliverable goes live, paste live_url from the public post, set live_date, and check the disclosure on the live post before marking disclosure_checked as yes. A draft can look compliant and the live caption can still lose the disclosure in an edit. Under the FTC Endorsement Guides, 16 CFR Part 255, a material connection such as payment or free product must be disclosed clearly and conspicuously, difficult to miss and easy to understand, in the same medium as the endorsement. Plain labels at the start, such as Ad or Sponsored, do the job. Abbreviations such as sp, spon, or collab, a lone thanks, or a label buried in hashtags do not. A platform paid partnership label helps and does not replace the in-content disclosure.

1. Run the measurement window on the dates in the memo. Set measurement_start and measurement_end when the post goes live, and report_due from the memo. Send the report by live link, per platform, with the metrics that platform reports: reach, impressions, views, engagements, clicks, and tracked sales or code use where the deal supplied tracking. Platforms count differently, so report each platform on its own numbers and never merge platforms into one total you cannot show the working for. Capture ephemeral formats such as Stories inside their window, before they disappear.

1. Watch the rights clocks every week. Run the weekly check:

python3 bin/tracker.py check --tracker deals.csv --as-of 2026-11-15 --warn-days 14

Work the flags in this order: slipped deliverables, approvals waiting past their window, reports overdue, invoices overdue, rights expired, rights expiring. For rights expiring inside the warn window, ask the brand in writing whether it wants a renewal, with the expiry date in the message. For rights already expired, check whether the brand is still using the content. Use after the end date needs a paid renewal or a removal, and the tracker row is the record of the agreed date. Run python3 bin/tracker.py summary --tracker deals.csv for open status counts and money totals. The summary counts each invoice once, even when it is repeated across deliverable rows.

1. Track the invoice from the invoice, not from memory. When an invoice is issued, copy invoice_id, amount, invoice_date, and the printed invoice_due into every row it covers. Payment terms such as Net 30 run from the trigger the contract names, usually the invoice date, so the printed due date is the date that matters. When payment lands, record payment_status and payment_date from the bank record. A partial payment keeps the row open with the balance named. For the reminder ladder, aging buckets, and payment matching, hand the chase to the invoice-runner skill and keep this tracker as the deal level record.

1. Close the deal in writing. A deal closes when every deliverable is live or formally cancelled, every report is sent, payment is recorded in full or a balance is agreed in writing, and every rights window has either renewed with a new end date or expired. Fill assets/closeout-template.md, set each row to closed, and keep the tracker and closeout with the signed memo. Use assets/weekly-check-template.md for the weekly note. A worked deal, followed from signature to payment to rights expiry, is in references/worked-deal.md, with its tracker rows in assets/example-deal.csv.

Output Contract

A deal under this skill produces:

• One tracker file with a row per deliverable, every field from the signed memo filled, and status current within the last seven days
• A weekly check note built from the tool output, with an owner and a date for every flag it raised
• A measurement report per deliverable, sent by its report_due date, built on live URLs and per platform numbers
• A renewal or removal message for every rights window that expires, sent before the expiry date where the warn window allowed it
• A closeout note that states what was delivered, what was reported, what was paid, and the rights state at close

Operating Rules

• The signed memo and the issued invoice are the only sources for terms, dates, and amounts. If a value is not in one of them, ask or leave it blank. Never invent a date, a fee, a rights window, or a metric.
• One row per deliverable, one tracker per operation. Scattered notes, inboxes, and chat threads are not a tracker.
• Update the tracker when the event happens. A live URL pasted a week later, from memory, is how links and dates go wrong.
• Disclosure is checked on the live post, every time, even when the draft was checked. The advertiser and the endorser both carry responsibility under 16 CFR Part 255, and the brand duty includes giving guidance and monitoring compliance.
• Usage, whitelisting, and exclusivity are separate clocks. A post can be fully delivered and paid while its paid usage has already expired. Track each window on its own dates.
• Expired rights are a written conversation, not an accusation. Send the agreed dates, ask for renewal or removal, and keep the reply with the deal file.
• Keep deal money and brand contact details in the tracker and the deal file. Do not copy them into public posts, reports shared outside the deal, or unrelated documents.
• This skill is deal operations, not legal advice. A dispute over rights, exclusivity, or a large unpaid balance goes to a qualified lawyer with the tracker and the signed memo as the evidence pack.