Brand-Deal Deliverables Tracker: Brief, Approval, Post and Payment

A brand-deal deliverables tracker separates agreed scope, approvals, publication proof, payment and usage-rights follow-up. Give every asset a versioned record, then log dated observations and renewal decisions against the signed agreement. This editable worksheet helps you ask precise questions; it does not prove unauthorized use or replace legal advice.

This guide provides an editable text record, not a spreadsheet integration or legal contract. Use it alongside the actual agreement, your review process and your accounting records.

Separate the deal from its deliverables

Create one deal record for the commercial relationship and one deliverable record for each item you owe. A package containing one Reel and two Story frames is not a single “posted” checkbox if those items have different approval or publication requirements.

The deal record should identify the brand, project, agreed scope, authorized contact and agreement location. The deliverable record should identify the format, brief version, draft deadline, approver, publication window and required proof.

Keep proposals separate from confirmed work. A quoted package is not an agreed package, and an enthusiastic message is not necessarily approval of the full scope. Record the point at which both sides confirmed the deliverables and preserve that confirmation.

This separation answers two different questions: “What did we agree to do?” and “What remains to be done?” Neither requires placing private client information in a public resource or sharing your entire account history with a collaborator.

Use statuses that describe evidence

A useful status should tell the next person what happened and what they need to do. Avoid one overloaded field called done.

You can simplify these for a small project. Keep the distinctions that affect decisions. “Awaiting approval” should have a named owner and next follow-up date, otherwise it becomes a polite label for forgotten work.

Do not use silence as automatic acceptance unless the parties have validly agreed to that process. If approval is unclear, ask the authorized person rather than guessing from an emoji reaction.

Work through a fictional partnership

Imagine a fictional ceramics brand commissioning a product demonstration Reel and two Story frames. This example illustrates organization; the dates and terms are invented, not recommended commercial conditions.

The agreed publication window is October 8–10. The first draft is due October 3. One consolidated review round is included. The brand contact must confirm the final version before publication.

The Reel record might look like this:

Deal: CL-DEMO-07 — fictional ceramics launch
Deliverable: R01 — product demonstration Reel
Brief: brief-v02, confirmed September 29
Draft: reel-v03, review link stored privately
Approval: awaiting named brand approver
Publication window: October 8–10
Disclosure check: wording and placement awaiting review
Next action: request consolidated notes on October 4
Publication proof: not yet available

The Stories receive separate records, S01 and S02. If the Reel is approved but the Story price card is not, only the Reel's approval changes. This prevents one green status from concealing an unfinished asset.

After publication, record the actual link and date. If the agreed proof is time-sensitive, capture it while it remains available. Keep private screenshots in the project folder, not in a publicly accessible tracker.

Make disclosure a real review item

Add fields for the relationship being disclosed, the intended disclosure wording, its location and the platform's applicable disclosure controls. Review the final published experience, not just a line in the brief.

For U.S.-relevant endorsements, the FTC's influencer disclosure guidance says disclosures should be clear and hard to miss, and warns against assuming a platform tool alone is sufficient. Other jurisdictions can impose additional requirements; this operational checklist is not legal advice.

If the package also includes YouTube, its branded-content disclosure guidance explains its own platform controls and responsibilities. Those instructions concern YouTube, not Instagram. Keep the platform field explicit instead of copying one checkbox across every channel.

The tracker should document what was checked and by whom. It should not declare a post compliant simply because a field contains “yes.” When a material question remains, resolve it with the responsible brand contact or qualified adviser before posting.

Record usage terms without inventing them

Add the agreed channels, organic or paid use, territory if specified, start date, duration, editing permissions and any source-file obligation. Link each summary to the relevant agreement section.

Do not infer advertising permission from permission to repost organically. Do not infer source-footage delivery from an agreement to publish a finished Reel. If a term is ambiguous, label it “needs clarification” rather than filling in a convenient assumption.

A reminder before an agreed usage period ends gives both sides time to discuss the next step. It does not automatically remove ads, extend rights or establish a legal deadline. Record the actual agreement and any later written change.

Use the project handoff checklist if files need to be transferred. That process should respect third-party music, font and stock permissions as well as the brand agreement.

Build a usage register for each asset, not just each deal

A deliverable ID tells you what you made. An asset version tells you which export was approved. An ad ID, when available, identifies an observed advertisement. Keep all three: the same Reel may appear in several ads, while one campaign may contain several edits.

Create one usage record per asset and distinct permission scope. Record the approved filename or version, agreement version and section, permitted advertiser or account where specified, channels, placement, territory, organic or paid use, and the agreed start and end. Do not silently replace old terms when a new email arrives. Link the proposed change to the original record, identify who can authorize it, and record whether it was actually agreed.

For a Reel with licensed music, an extension of the brand's permission may not extend the music permission. Use the music for sponsored Reels checklist to separate the creator post, paid distribution and any off-platform use. Record unresolved third-party rights before promising a renewal.

Keep a separate observation log. Its job is to record what you saw, not to determine what the agreement legally permits:

Avoid copying a whole private contract into a shared production board. A restricted document link and the relevant section reference are usually enough for the teammate who only needs to know the next action.

Use Meta Ad Library as an observation tool

Meta Ad Library lets you search ads, with current ads and certain archived categories available depending on the library's coverage. Check the country, category and advertiser before interpreting a result. Meta's library information was checked on September 20, 2026.

A result can help you identify a creative and an ad reference. It is not a license register: it does not show your complete agreement, amendments or every permission held by the advertiser. A displayed start date is not automatically the start of your contractual usage period.

A missing result is not proof that an asset has never been used, that an ad has stopped everywhere, or that no renewal is needed. Record the search and its limits as “no matching result observed.” Do not turn it into “no use.” Equally, a visible result is a reason to check the facts, not proof of a breach. If the creative is cropped or changed, first establish whether it is actually your asset.

Fictional example: October usage, October 31 observation

This is a separate invented scenario, not a finding about a real brand. Assume the written agreement for asset U-DEMO-01 allows a specified Meta paid use from October 1 through October 30, 2026. The team must read the actual end-time and timezone wording before applying that rule to a real deal.

Before contacting anyone, compare the creative with the approved export, check whether the result is active or archival as displayed, and look for later written permission in the restricted project record. Preserve the dated observation without describing it as a confirmed violation.

Then send a neutral clarification:

Subject: Usage check for [asset / project]

Hi [name], I am reviewing the usage record for [asset/version].
Our record points to [agreement version/section] and [agreed period].
On [date/time/timezone], I observed [plain description] at [link],
with [ad ID if available].

Could you confirm the current use and whether an agreed amendment
or renewal applies? I may be missing a later record. Please share
the relevant confirmation, or let us agree the appropriate next step.

Thanks,
[name]

Keep the observation date separate from the response date. A reply proposing a renewal is still a proposal until the required parties agree. Log the decision, revised scope, effective dates, fees if agreed, authorizer and evidence; then schedule a follow-up. If the question remains disputed or legally significant, use qualified advice rather than treating this tracker as a legal conclusion.

Keep payment records accurate and private

An invoice reference belongs in the tracker; full banking details generally do not. Keep sensitive financial documents in the restricted system intended for them.

Record invoice issue date, agreed due date, amount and currency if appropriate for the audience using the tracker. Use the actual agreed terms, not a universal payment period taken from a template.

Mark a payment settled only after checking the receipt in your accounting or payment records. If a partial payment arrives, record the outstanding amount in the authorized financial system and summarize its status here. An email saying “processed” is useful correspondence, not the same thing as reconciled receipt.

Keep disagreements factual: disputed item, date raised, owner and next action. The tracker is a coordination tool, not a debt-collection script or substitute for professional accounting advice.

Review by next action, not by brand name

At a regular interval, scan for the next action and deadline: missing brief detail, approval request, publication proof, invoice follow-up or usage clarification. Assign one owner to each action.

After the project closes, preserve the approved version, publication evidence and relevant correspondence according to your agreement and retention needs. Remove access that collaborators no longer require.

A useful tracker lets you explain the state of a deal in one sentence: “The Reel is approved, the Story revision is due tomorrow, and invoicing follows the agreed delivery milestone.” That is much more actionable than “mostly done.”

BRAND-DEAL DELIVERY TRACKER
Keep this record private. Link to restricted agreements and invoices; do not paste passwords or banking details.

DEAL RECORD
Deal ID / project:
Brand:
Authorized contact:
Agreement location / version:
Scope confirmed on:
Deliverables:
Included review process:
Usage summary and agreement section:
Outstanding questions:
Next review date:

DELIVERABLE RECORD — duplicate per item
Deliverable ID:
Format / channel:
Brief version:
Draft due:
Exact review file / version:
Approver:
Approval status / date / evidence:
Publication window:
Actual publication date:
Public link / agreed proof location:
Disclosure wording / placement / controls checked:
Disclosure reviewer:
Usage start / end / reminder date:
Source-file obligation:
Next action / owner / due date:

PAYMENT SUMMARY
Invoice reference:
Issue date:
Agreed due date:
Status: not issued / issued / disputed / partly received / settled
Receipt reconciliation date:
Restricted accounting record:
Next action:

FICTIONAL FILLED EXAMPLE
Deal: CL-DEMO-07, ceramics launch
Deliverable: R01, Instagram product Reel
Brief: v02 confirmed September 29
Draft: v03 sent October 3
Approval: awaiting named brand approver
Publication: October 8–10, not yet live
Disclosure: final wording and placement awaiting review
Proof: pending publication
Usage: see agreed section; do not infer paid-use permission
Next action: request consolidated notes October 4
Payment: not yet invoiced; follow agreed milestone

USAGE REGISTER — duplicate per asset and distinct scope
Usage record ID:
Deliverable ID:
Approved asset filename / export version:
Agreement location / version / section:
Authorized amendment location / version:
Advertiser or account permitted by agreement:
Channels / placements / territory as agreed:
Organic use / paid use / other scope:
Agreed start / end:
End-time / timezone wording confirmed?:
Editing / source-file permissions:
Third-party music, font or stock restrictions:
Reminder date / owner:
Unknown terms requiring clarification:

DATED OBSERVATION LOG — append, do not overwrite
Observation date / time / timezone:
Source URL:
Country / category / other filters:
Search wording / advertiser or page:
Displayed ad ID, if available:
Creative match: confirmed / uncertain / not this asset
Displayed status and dates, exactly as seen:
Private evidence location / capture date:
What was observed:
What remains unknown:
No matching result? Record only that observation, not proof of non-use.
Agreement / amendment checked:
Next action / owner / due date:

RENEWAL OR CLOSEOUT DECISION
Decision status: not reviewed / clarification requested / proposal / agreed / declined / unresolved
Response date / responding person:
Authority to approve confirmed?:
Confirmed decision and evidence:
Revised channels / placements / territory:
Revised start / end / timezone:
Agreed fee or restricted record reference, if applicable:
Third-party permissions reviewed:
Follow-up observation date / owner:
Closeout basis and remaining uncertainty:
A proposal is not a renewal. A reminder does not remove ads or change rights.

FICTIONAL USAGE REVIEW — no real brand, ad or violation
Asset: U-DEMO-01 / approved-export-v04
Permission: demo-agreement-v02, usage section; October 1–30, 2026
End-time / timezone: check the agreement before drawing a conclusion
Observation: October 31, 2026, 10:00 IST
Source: a hypothetical Meta Ad Library result
Ad ID: DEMO-AD-01 (invented placeholder)
Observed: matching-looking creative displayed; verify status and asset match
Initial status: needs verification and clarification
Amendment / renewal: not recorded; check authorized correspondence
Next action: ask the brand to confirm current use and any later agreement
Conclusion: none; an observation alone does not establish unauthorized use

CLARIFICATION EMAIL — adapt to the actual evidence
Subject: Usage check for [asset / project]
Hi [name], I am reviewing [asset/version]. Our record points to [agreement version/section] and [agreed period].
On [date/time/timezone], I observed [plain description] at [link], with [ad ID if available].
Could you confirm the current use and whether an agreed amendment or renewal applies? I may be missing a later record.
Please share the relevant confirmation, or let us agree the appropriate next step.
Thanks, [name]

AD LIBRARY CHECK LIMITS
https://www.facebook.com/ads/library/
Library information checked September 20, 2026.
Search coverage and filters affect what you see. Current ads and certain archives are not a complete usage or licensing history.
No result is not proof of non-use. A visible result is not proof of a breach.
Keep personal, agreement and invoice details in restricted storage.
Music rights checklist: https://creatorlanehq.com/blog/music-for-sponsored-reels

CLOSEOUT
Every item approved and delivered:
Publication proof retained:
Invoice reconciled:
Usage questions resolved:
Archive / retention agreed:
Unneeded collaborator access removed: